Outbound Payment Order / Remittance Advice (820 / PAYORD, REMADV) (Oracle EDI Gateway Help)


	Previous	Next		Contents	Index	Navigation	Glossary	Library

Outbound Payment Order / Remittance Advice (820 / PAYORD, REMADV)

Use this transaction to electronically make a payment, or make a payment and send a remittance advice to your creditors.

The payment portion of this transaction is a request to your financial institution to perform cash application to relieve your account and to pay your payee's account.

The remittance advice portion of this transaction contains the payment distribution by invoice. It may be sent directly to the payee, through a financial institution, or through a third party. In addition, you may use Oracle Payables to print your remittance advice.

Payments made using electronic funds transfer (EFT) may be processed via EDI if your EDI translator has the means to download the payment data from Payables to tape for delivery to the payee's bank.

Application(s) accessed Oracle Payables

ASC X12 Transaction 820

EDIFACT Messages PAYORD / REMADV

PAYEXT / REMADV

Prerequisite Set Up in Oracle Payables

Use Payables to enable the payer and payee site. Indicate for the payer and payee site the payment method, payment format, remittance method, remittance instruction, and transaction handling instructions.

Use the Invoice Workbench to enter and approve invoices, and to release invoice holds.

Use the Payment Workbench to select invoices for payment, create a payment batch, and to submit the EDI payment transaction. This transaction is event-driven and integrated with the standard Payables payment process. It cannot be initiated through the EDI Gateway. However, you must use the EDI Gateway to set up the trading partner and enable the transaction.

Interface Table, Extension Table, and View Names

The following tables and views appear in the Interface File Definition window for this transaction. See: Changing the Data File.

Interface Tables

ECE_AP_CHECKS_INTERFACE

ECE_AP_INVOICES_INTERFACE

Extension Tables

Each extension table shares its name with a base interface table, except for the trailing "_X". You must define the columns for the extension tables if you choose to use them. See: Extensible EDI Gateway Architecture.

ECE_AP_CHECKS_INTERFACE_X

ECE_AP_INVOICES_INTERFACE_X

Views

The following views appear in the Assign Categories window, under View Name, for this transaction. Columns within these views are identified as candidates for code conversion. See: Code Conversion.

ECE_PYO_INVOICE_V

ECE_PYO_PAYMENT_V