Bookshelf Home | Contents | Index | PDF |
Implementation Guide for Oracle Self-Service E-Billing > About Payment Processing > About Check Processing > Automated Clearing House (ACH)This topic describes the codes and other data used with Automated Clearing House (ACH) Network fund transfers. Additional information about ACH and change codes are available at: Supported SEC CodesFor ACH, Oracle Self-Service E-Billling supports the following SEC Codes (Standard Entry Class Codes):
ACH Change Codes (NOC)Table 54 lists some of the ACH change codes (also known as NOC codes) that might appear in the returns file after running the pmtCheckUpdate job if previously valid payment information is now incorrect or out-of-date.
ACH Return CodesTable 55 lists some of the ACH return codes that might appear in the returns file after running the pmtCheckUpdate job.
Additional information about these and additional ACH return codes are available from the following URL: NOC TransactionsWhen a prenote is returned with a NOC, TXN_MESSAGE is populated with NOC information formatted as NOC_CODE::NEW_ADDENDA_INFO::OLD_ADDENDA_INFO, where
ACH Effective DateThe Skip non-business days for batch effective entry date field on the Payment Settings page for an ACH check payment gateway controls how the effective entry date is calculated when the ACH batch file is created by pmtCheckSubmit. If the field is set to Yes, then non-business days are not taken into consideration. The effective entry date is set to the payment date that the customer specified when scheduling the payment. If the field is set to No, then non-business days are skipped, and the effective entry date is the next business day following the computed date. Payment checks the scheduled payment date to see if it is on or before the end of today. If it is, the computed date is the customer-scheduled date plus one. If it is not, then the computed date is the customer-scheduled date. Non-business days are weekend days, plus the U.S. Federal holidays. ACH Settlement DateThe ACH settlement date is not written to the ACH batch file by pmtCheckSubmit. That date is added by the ACH Operator when the payment is settled. ACH Addenda RecordsPayment supports ACH addenda records, which means you can append a list of addenda records after an entry detail record in an ACH file. Addenda records are biller-specific, so customization is required to support this feature. Theoretically, you can put any information into an addenda record, such as the invoices of a payment. To add addenda records, you must write a plug-in for the pmtCheckSubmit job. For more information about supporting ACH addenda records, contact My Oracle Support. |
Implementation Guide for Oracle Self-Service E-Billing | Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |