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:

http://www.nacha.org

Supported SEC Codes

For ACH, Oracle Self-Service E-Billling supports the following SEC Codes (Standard Entry Class Codes):

• Web. Internet initiated entry (default for Oracle Self-Service E-Billling).

  Debit entries are originated (either single or recurring) from a customer's account using web based authorization.

• PPD. Pre Arranged Payment and Deposit Entry. Under PPD the following types are included:
  • Direct Deposit: The credit application transfers funds into the customer's account.
  • Preauthorized Bill Payment: This is a debit application, where billers transfer electronic bill payment entries through the ACH network.
• CTX. Corporate Trade Exchange

  Supports multiple Addenda record based on ANSI ASC X12 standards. Can be used either with the credit or debit application.

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 Codes

Table 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:

http://www.nacha.org/

NOC Transactions

When 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

• NOC_CODE is the three-character code returned.
• NEW_ADDENDA_INFO is the NOC information returned from ACH, which can include the corrected account number, routing and account type.
• OLD_ADDENDA_INFO is the existing addenda information.

ACH Effective Date

The 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 Date

The 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 Records

Payment 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.