How To Create Electronic Funds Transfer (EFT) Automatic Payments For PPD, CTX and IAT Formats (R04572T1, R04572T2, R04572T3)

Overview

Overview

Electronic funds transfer (EFT) payments is the electronic exchange or transfer of money from one account to another, either within a single financial institution or across multiple institutions, through the Oracle JD Edwards EnterpriseOne Financial system. There are three EFT Payment Print Programs available within JD Edwards EnterpriseOne Accounts Payable. The formats include:

For release 8.12 and above the third format option is:

See graph below with a list of data preparation steps to create Automatic Payments.

Note - Please be aware that these are the formats we offer and Support, however, they may not meet your bank's specific requirements and you may have to consider customizing to meet your needs which Oracle Support would not be able to assist with.

Additional Resources

Additional Knowledge Resources

  • How To Setup Supplier Tax Withholding
  • How To Run Cash Requirement Report in Accounts Payable
  • Overview Of Automatic Payment Processing Within EnterpriseOne Accounts Payable

    • Product Documentation

  • List of UBEs that Must Be Run through a Single Threaded Job Queue in EnterpriseOne

    • Setup

    Setup

    Setup requirements for Electronic Funds Transfer, also known as ACH/Automatic Clearing House, include the following:

    The setup steps for each of these above are listed below.

    Supplier Master Setup (P04012)

    Supplier Master Setup (P04012)

    Populate these fields:

    Supplier Bank Account Setup (P0030A)

    Supplier Bank Account Setup (P0030A)

    Every supplier paid using EFT needs to have a corresponding bank account in the Bank Accounts by Address (P0030A).

    Bank Account Information (P0030G)

    Bank Account Information (P0030G)

    In the Work with G/L Bank Accounts (P0030G) application complete this information: , physical bank account information needs to be set up for each GL Bank Account that will be used for EFT payments. The information that is configured here includes:

    Note - To prevent unused Next Numbers (NXTC) for GL Bank Accounts (P0030G) when creating EFT payments, confirm that the Special Handling Code (data dictionary item SPHD) for the Payment Print Program (P04572T1, P04572T2 or P04572T3) is 2 in UDC table 04/PP (Produce Bank File).

    Payment Instrument Defaults (P0417)

    CTX Defaults

    CTX Defaults

    Payment Instrument (PYIN) "T" must be set up with valid Print Programs as follows:


    PPD Defaults

    PPD Defaults

    Payment Instrument (PYIN) V must be set up with valid Print Programs as follows:

    IAT Defaults

    IAT Defaults

    Payment Instrument (PYIN) '@' must be set up with valid Print Programs as follows:

    EFT Instructions

    EFT Instruciton

    Step 1: Enter Vouchers (P0411)

    Step 1: Enter Vouchers (P0411)

    After the setup is complete, vouchers can be entered into the system using any of the voucher entry programs. For more information, see knowledge Overview of Creating, Deleting or Voiding Standard Vouchers in EnterpriseOne Accounts Payable

    Step 2: Create Payment Control Groups (R04570)

    Step 2: Create Payment Control Groups (R04570)

    The Bank Tape tab in the processing options of the Create Payment Control Groups (R04570) has the following options:

    The Create Payment Control Groups (R04570) program automatically creates a separate payment control group for the vouchers with the following common information: bank account, payment instrument, currency code, business unit (optional), and company (optional). For more information, see knowledge How To Create Automatic Payment Control Groups (R04570, R04570)

    Step 3: Work with Payment Groups (P04571)

    Step 3: Work with Payment Groups (P04571)

    To complete the payment process, complete the following steps using the Work with Payment Groups (P04571) application:

    1. Highlight the desired payment control group for EFT payment.
    2. Select the Write option from the Form exit.
    3. The Next Payment Number (data dictionary item NXTC) will display from the bank account information in the Work with G/L Bank Accounts (P0030G). However, this number is not used for EFT payments. The payment number is fetched from the Check No. ACH Next Number (P0002) for Accounts Payable (system 04).
    4. After completing the Write function, records are written to the A/P Payment Tape (F04572OW) table. Each time a new payment control group is written new records are added to the F04572OW table. Each payment group is uniquely identified in F04572OW by the value in the Member ID (data dictionary item KNMID) field.
    5. Select the Update option from the Form exit for the now written payment control group. This function creates the final payment records in the AP Matching Document (F0413) and the AP Matching Document Detail (F0414) tables. The Document Type (data dictionary item DCT) assigned to EFT payments is PT.
    6. Copy Bank File to Tape (P0457) (See below section on instructions)


    After EFT payments have been written to the A/P Payment Tape (F0452OW), the records can be written to a file to be transmitted to the bank. The Copy Bank File to Tape (P0457) program allows a user to review EFT payment records, delete records, and as of release 8.9 write the records to a diskette or file.

    Step 4: Copy Payment To Diskette (P0457, P0457D)

    Step 4: Copy Payment To Diskette (P0457, P0457D)

    Starting at release 8.9 and above only, when writing payments, the Payment Instrument (PYIN) can be in an electronic format. In this case, writing payments creates bank tape tables rather than printed payments. To complete these payments, the records need to be copied to a flat file or diskette to send the information to a financial institution. Copying payments to a diskette consists of:

    Typically, your MIS department presets the detail for a tape table. This information should not be changed unless instructed to do so. However, many format specifications can be changed prior to copying the table to a diskette. The information in the bank table can be copied as long as they are not deleted from the AP Bank Tape (F0452OW) table. This might be necessary if, for example, your financial institution loses the original diskette.

    The AP Payment Tape (F04572OW) table is a multi-member table, which means that each version (payment group) is a separate table. The system does not automatically delete records in the table. Instead, they must be deleted manually using the Copy Bank Tape (P0457) program.

    Caution: Do not delete the records from the AP Bank Tape (F04572OW) until the bank verifies it received the payments.

    Additional Copy Options

    The following additional options for copying a tape table are available:

    Processing Options - Copy Bank Tape File to Tape (P0457)

    For current information on processing options, please click here to access release 9.2 online guide.

    Additional Knowledge Resources

    CTX Format

    CTX Format

    NACHA ISO 20022-to-ACH Mapping Guide & Tool (URL)

    ISO 20022-to-ACH Mapping Guide & Tool

    CTX - Corporate Trade Exchange (R04572T2)

    The Field Inclusion Requirement code in both documents indicates which fields Oracle JD Edwards EnterpriseOne populates and which are optional.

    The values are:

    Record 1 - All Entries File Header Record

    FieldDescriptionSize PositionWhere Generated in JDEField Requirement
    1Record Type101-011 indicating record typeM
    2Priority Code202-031R
    3Immediate Destination 10 04-13 Bank Transit Number(TNST) from the Supplier's Bank Account (P0030A). Please see Bug 18474387. M
    4 Immediate Origin1014-23R04572T2 Processing Option 3 Immediate Origin, tab Process. If this processing Option is left blank, the Tax ID the Tax ID for the bank account's company is used.M
    5File Creation Date624-29Date file created in YYMMDD format.M
    6File Creation Time430-33Time file created in HHMM format.O
    7File ID Modifier134-34R04572T2 Processing Option 1 File ID Modifier, tab Process.M
    8Record Size335-3794M
    9Blocking Factor238-3910M
    10Format Code140-401M
    11Immediate Destination Name2341-63Account Description (DL01) from the G/L bank Account (P0030G)O
    12Immediate Origin Name2364-86Company Name (NAME) from Company Numbers and Names (P0010).O
    13Reference Code887-94Not usedO

    Record 5: Company Batch Header

    FieldDescriptionSizePositionWhere Generated in JDEField Requirement
    1Record Type101-015 indicating record typeM
    2Service Class Code302-04200 for Debit and CreditsM
    3Company Name1605-20Company Name (NAME) from Company Numbers and Names (P0010).M
    4Co. Discretionary Data2021-40R04572T2 Processing Option 5 Discretionary Data, tab Process.O
    5Company Identification1041-50R04572T2 Processing Option 4 Identification Code Designator, tab Process. If left blank, the Tax ID for the bank account's company will be used.M
    6Standard Entry Class Code351-53CTXM
    7Company Entry Description1054-63R04572T2 Processing Option 2 Tape Payment Detail Description, Tab Process.M
    8Company Descriptive Date 664-69Date file created in YYMMDD format.O
    9Effective Entry Date670-75Check date in YYMMDD format.R
    10Settlement Date (Julian Date)376-78Not used by JDE.Inserted by ACH operator
    11Originator Status Code179-791M
    12Originating DFI ID880-87First eight digits of the Bank Transit Number(TNST) from the G/L bank Account (P0030G)M
    13 Batch Number788-94Starts at 0000001 and assigned in ascending order to each batch included in transmission.M

    Record 6: Entry Detail Record

    Note - Each Supplier will have a record 6 within the F04572OW text file.

    FieldDescriptionSizePositionWhere Generated in JDEField Requirement
    1Record Type Format101-016 indicating record type.M
    2Transaction Code202-0322 = Automated Deposit (Checking)M
    23 = Prenote for Automated Deposit (Checking)
    32 = Automated Deposit (Savings)
    33 = Prenote for Automated Deposit (Savings)
    Based on Chk/Sav field (CKSV) retrieved from the supplier bank account record (P0030A).
    3Receiving DFI Identification804-11Bank Transit Number(TNST) from the Supplier bank Account (P0030A)M
    4Check Digit112-12Control Digit (CHKD) form the Supplier Bank Account (P0030A)M
    5DFI Account Number1713-29Bank Account Number(CBNK) from the Supplier bank Account (P0030A)M
    6Total Amount1030-39Total amount of all checks in file (total amount of payment).M
    7Identification Number1540-54EFT Payment Number from the A/P Payment Header File ( F04572)O
    8Number of Addenda Records455-58Total number of 6 recordsM
    9Payee Name1659-74Payee Alpha Name (KKALPP) from the A/P Payment Header File ( F04572)M
    10Reserved275-76Not used by JDE and blank filled.NA
    11Discretionary Data277-78Not used by JDE and blank filled.O
    12Addenda Record Indicator179-79If a record 7 follows a 1 is populated otherwise it is 0.M
    13Trace Number1580-94First eight digits of the Bank Transit Number(TNST) from the G/L bank Account (P0030G) and the last seven digits of Next Number (P0002) for system 04 index 05 or Next Numbers by Company and Fiscal Year for document type PT.M

    Record 7: Addenda

    Record 7
    FieldDescriptionSizePositionWhere Generated in JDEField Requirement
    1Record Type Code101-017 indicating record type.M
    2Addenda Type Code202-035M
    3Payment Related Information8004-83

    CTX Format follows NACHA Operating Rules permit the exchange of certain EDI messages or transaction sets (e.g., 820 Payment Order/Remittance Advice) within the Addenda Records of the CTX format, but those standards are developed and maintained by other standards development organizations, such as ASC X12.

    See the following table for a breakdown of the information in these fields.

    Description of SegmentSizeWhere Generated in JDEField Requirement
    Interchange Control Header3ISA (ISA is the Interchange Control Header used to start and identify an interchange of functional groups and interchange-related control segments)M
    Authorization Information Qualifier2GL Bank Account X12 Information (P0030G)M
    Authorization Information10GL Bank Account X12 Information (P0030G)M
    Security Information Qualifier2GL Bank Account X12 Information (P0030G)M
    Security Information10GL Bank Account X12 Information (P0030G)M
    Interchange ID Qualifier2ZZM
    Interchange sender ID (your sender ID)15GL Bank Account X12 Information (P0030G)M
    Interchange ID Qualifier2ZZM
    Interchange Receiver ID15GL Bank Account X12 Information (P0030G)M
    Interchange Date6YYMMDD format.M
    Interchange Time4HHMM format.M
    Interchange Control Standards ID6UM
    Interchange Control Version Number5200M
    Interchange Control Number90M
    Test Indicator1PM
    Sub-element Separator1:M
    Functional Group Header2GS (GS is the Functional Group Header and is used to indicate the beginning of a functional group and to provide control information.)M
    Functional Identifier Code2RAM
    Application Senders Code15GL Bank Account X12 Information (P0030G)M
    Application Receiver Code15GL Bank Account X12 Information (P0030G). Note the positions for the subsequent fields vary depending on the length of the Application Sender and Application Receiver codes. The system allows up to 15 characters for each, but if you do not use them all, the file does not leave extra spaces, it uses them for the subsequent field values.M
    Date6YYMMDD formatM
    Time4HHMM format.M
    Group Control Number41M
    Responsible Agency Code1XM
    Version/Release Industry63050M
    Transaction Set Header2STM
    ST is the Transaction Set Header to indicate the state of a transaction set.
    Transaction Set Identifier Code3820M
    Transaction Set Control Number4System-assigned 4-digit number. An identifying control number that must be unique within the transaction set functional group; assigned by the originator for a transaction set.M
    Beginning Segment for Payment Order3BPR (BPR is the beginning of a payment order segment.)M
    Transaction Handling Code1CM
    Monetary Amount18$$$$$$$$$$$$$$$.00M
    Credit Flag Code1CM
    Payment Method Code 3ACHM
    Reference Identification3REF (REF is the beginning of the Reference Identification segment)M
    Reference Identification Qualifier2IVM
    Reference Identification8

    Functionality was changed under Bug 12992327 as of release 8.11SP1: the reference identification number defaults from the voucher's invoice number (VINV) in the Accounts Payable ledger (F0411)

    		M
    Entity3ENT (ENT is the Entity Segment)M
    Assigned Number6System-assigned 6-digit number. A number assigned for differentiation within a transaction set.M
    Remittance Delivery Method3RMR (RMR is the Remittance Delivery Method)M
    Reference Identification Qualifier2CKM
    Reference Identification8Document number assigned to the PT check record by the system’s Next Number table (F0002), 5th line (Check No.-ACH), where the value of the System Code field is 04.M
    Reference Identification2POM
    Monetary Amount18.00M
    Document Amount18$$$$$$$$$$$$$$$.00O
    Amount of Discount Taken18$$$$$$$$$$$$$$$.00O
    Date/Time/Reference3DTM (DTM specifies pertinent dates and times)M
    Date/Time Qualifier33M
    Date6YYMMDD format.M
    Transaction Set Trailer2SE (SE indicates the end of the transaction set. )M
    Number of Segments1-10Total number of segments included in a transaction set including ST and SE segmentsM
    Transaction Set Control Number4Same value as the corresponding field in the ST (transaction set header) segment.M
    Functional Set Trailer2GE (GE is to define the end of a functional group of related transaction sets.)M
    Number of Transaction Sets Included1-6Total number of transaction sets.M
    Group Control Number41M
    Interchange Control Trailer3IEA (IEA is to define the end of an interchange of one or more functional groups and related control.)M
    Number of included Function Groups.1-5Count of GS segments in transmission. M
    Interchange control number90M
    		O
    4Addenda Sequence Number484-87Line number incremented within payment in ascending order.M
    5Entry Detail Sequence Number788-94last seven digits of Next Number (P0002) for system 04 index 05 or Next Numbers by Company and Fiscal Year for document type PT.M

    Record 8: All Entries Company/Batch Control Record

    FieldDescriptionSizePositionWhere Generated in JDEField Requirement
    1Record Type Code101-018 indicating record typeM
    2Service Class Code302-05220 for CreditsM
    3Entry/Addenda Count505-10Total number of 6 and 7 recordsM
    4Entry Hash1011-10Sum of the first 8 digits of the Bank Transit Number(TNST) from the Supplier bank Account (P0030A) from all 6 Entry Detail Records M
    5Total Debit Entry $ amount1221-32Sum of amounts from record 6 debit transactionsM
    6Total Credit Entry $ amount1233-44Sum of amounts from record 6 transactionsM
    7Company Identification1045-54R04572T1 Processing Option 4 Identification Code Designator, tab EFT. If left blank, the Tax ID for the bank account's company will be used.R
    8Message Authentication Code1955-73Not used by JDE and blank filledO
    9Reserved674-79Not used by JDE and blank filledN/A
    10Originating DFI Identification880-87Bank Transit Number(TNST) from the G/L bank Account (P0030G)M

    Record 9: All Entire File Control Records

    FieldDescriptionSizePositionWhere Generated in JDEField Requirement
    1Record Type Code101-019 indicating record typeM
    2Batch Count602-07Total number of 5 records in the fileM
    3Block Count608-13The number of physical blocks (a block is 940 characters) in the file, which includes both the File Header and File Control records.M
    4Entry/Addenda Count814-21Total number of 6 and 7 records in the fileM
    5Entry Hash1022-31Sum of corresponding fields in the Company/Batch Control Records in the fileM
    6Total Debit Entry Dollar Amount in File1232-43Sum of amounts from record 6 transactionsM
    7Total Credit Entry Dollar Amount in File1244-55Sum of amounts from record 6 transactionsM
    8Reserved3956-94Required by ACH to be blank filledN/A

    PPD Format

    NACHA ISO 20022-to-ACH Mapping Guide & Tool (URL)

    ISO 20022-to-ACH Mapping Guide & Tool

    PPD Format PPD - Prearranged Payment and Deposits (R04572T1)

    The Field Inclusion Requirement code in both documents indicates which fields Oracle JD Edwards EnterpriseOne populates and which are optional. The values are:

    Record 1 - All Entries File Header Record

    Field Description Size Position Where Generated in JDE Field Requirement
    1Record Type101-011 indicating record typeM
    2Priority Code202-031R
    3Immediate Destination1004-13Bank Transit Number(TNST) from the G/L bank Account (P0030G)M
    4Immediate Origin1014-23R04572T1 Processing Option 3 Immediate Origin, tab EFT. If this processing Option is left blank, the Tax ID the Tax ID for the bank account's company is used.M
    5File Creation Date624-29Date file created in YYMMDD formatM
    6File Creation Time430-33Time file created in HHMM formatO
    7File ID Modifier134-34R04572T1 Processing Option 1 File ID Modifier, tab EFTM
    8Record Size335-37094M
    9Blocking Factor1038-3910M
    10Format Code 140-401M
    11Immediate Destination Name2341-63Account Description (DL01) from the G/L bank Account (P0030G)O
    12Immediate Origin Name2364-86Company Name (NAME) from Company Numbers and Names (P0010)O
    13Reference Code887-94Not usedO

    Record 5: Company Batch Header

    FieldDescriptionSizePositionWhere Generated in JDEField Requirement
    1Record Type101-015 indicating record typeM
    2Service Class Code302-04220 for CreditsM
    3Company Name1605-20Company Name (NAME) from Company Numbers and Names (P0010)M
    4Co. Discretionary Data2021-40R04572T1 Processing Option 5 Discretionary Data, tab EFTO
    5Company Identification1041-50R04572T1 Processing Option 4 Identification Code Designator, tab EFT. If left blank, the Tax ID for the bank account's company will be usedM
    6Standard Entry Class Code351-53PPDM
    7Company Entry Description1054-63R04572T1 Processing Option 2 Tape Payment Detail Description, Tab EFTM
    8Company Descriptive Date664-69Date file created in YYMMDD formatO
    9Effective Entry Date670-75Check date in YYMMDD formatR
    10Settlement Date (Julian Date)376-78Not used by JDEInserted by ACH operator
    11Originator Status Code179-791M
    12Originating DFI ID880-87First eight digits of the Bank Transit Number(TNST) from the G/L bank Account (P0030G)M
    13Batch Number788-94Starts at 0000001 and assigned in ascending order to each batch included in transmissionM

    Record 6: Entry Detail Record

    FieldDescriptionSizePositionWhere Generated in JDEField Requirement
    1Record Type Format101-016 indicating record typeM
    2Transaction Code202-0322 = Automated Deposit (Checking)M
    23 = Prenote for Automated Deposit (Checking)
    32 = Automated Deposit (Savings)
    33 = Prenote for Automated Deposit (Savings)
    Based on Chk/Sav field (CKSV) retrieved from the supplier bank account record (P0030A)
    3Receiving DFI Identification604-11Bank Transit Number(TNST) from the Supplier Bank Account (P0030A)M
    4Check Digit112-12Control Digit (CHKD) form the Supplier Bank Account (P0030A)M
    5DFI Account Number1713-29Bank Account Number (CBNK) from the Supplier Bank Account (P0030A)M
    6Total Amount1030-39Total amount of all checks in file (total amount of payment)M
    7Identification Number1540-54R04572T1 Processing Option 6 Bank Account Reference Roll Number, Tab EFT. If left blank, the Payee Address Book Number is used.O
    8 Payee Name455-76Payee Alpha Name (KKALPP) from the A/P Payment Header File ( F04572)M
    9Discretionary Data277-78Not used by JDE and blank filledO
    10Addenda Record Indicator179-79If a record 7 follows a 1 is populated otherwise it is 0M
    11Trace Number1580-94First eight digits of the Bank Transit Number(TNST) from the G/L bank Account (P0030G) and the last seven digits of Next Number (P0002) for system 04 index 05 or Next Numbers by Company and Fiscal Year for document type PT.M

    Record 7: Addenda

    FieldDescriptionSizePositionWhere Generated in JDEField Requirement
    1Record Type Code101-017 indicating record typeM
    2Addenda Type Code202-035M
    3Payment Related Information8004-83R04572T1 Processing Option 2 Tape Payment Detail Description, Tab EFTO
    4Addenda Sequence Number484-87Line number incremented within payment in ascending orderM
    5Entry Detail Sequence Number788-94last seven digits of Next Number (P0002) for system 04 index 05 or Next Numbers by Company and Fiscal Year for document type PT.M

    Record 8: All Entries Company/Batch Control Record

    FieldDescriptionSizePositionWhere Generated in JDEField Requirement
    1Record Type Code101-018 indicating record typeM
    2Service Class Code302-05220 for CreditsM
    3Entry/Addenda Count505-10Total number of 6 and 7 recordsM
    4Entry Hash1011-10Sum of the first 8 digits of the Bank Transit Number(TNST) from the Supplier bank Account (P0030A) from all 6 Entry Detail Records M
    5Total Debit Entry $ amount1221-32Sum of amounts from record 6 debit transactionsM
    6Total Credit Entry $ amount1233-44Sum of amounts from record 6 transactionsM
    7Company Identification1045-54R04572T1 Processing Option 4 Identification Code Designator, tab EFT. If left blank, the Tax ID for the bank account's company will be used.R
    8Message Authentication Code1955-73Not used by JDE and blank filledO
    9Reserved674-79Not used by JDE and blank filledN/A
    10Originating DFI Identification880-87Bank Transit Number(TNST) from the G/L bank Account (P0030G)M

    Record 9: All Entries File Control Records

    FieldDescriptionSizePositionWhere Generated in JDEField Requirement
    1Record Type Code101-019 indicating record typeM
    2Batch Count602-07Total number of 5 records in the fileM
    3Block Count608-13The number of physical blocks (a block is 940 characters) in the file, which includes both the File Header and File Control records.M
    4Entry/Addenda Count814-21Total number of 6 and 7 records in the fileM
    5Entry Hash1022-31Sum of corresponding fields in the Company/Batch Control Records in the fileM
    6Total Debit Entry Dollar Amount in File1232-43Sum of amounts from record 6 transactionsM
    7Total Credit Entry Dollar Amount in File1244-55Sum of amounts from record 6 transactionsM
    8Reserved3956-94Required by ACH to be blank filledN/A

    IAT Format

    IAT Format

    IAT Format (R04572T3) (Release 8.12 and above only)

    The Field Inclusion Requirement code in both documents indicates which fields Oracle JD Edwards EnterpriseOne populates and which are optional. The values are:

    NACHA ISO 20022-to-ACH Mapping Guide & Tool (URL)

    ISO 20022-to-ACH Mapping Guide & Tool

    IAT Format Requirements Link

    Best resource for current IAT EFT format requirements, refer to the NACHA mapping tool link above.

    Additional Knowledge Resources

    Additional knowledge resources

    Reports

    Payment Register

    Payment Register (R04576)

    The Automatic Payment Register Report R04576 and its version are defined in Work With Payment Instruments Defaults (P0417). The Automatic Payment Register Report is called when updating a payment group in the Work With Payment Groups application P04571. When a payment group is updated, the system first launches R04575 (Update Driver) and this in turn launches the Automatic Payment Register UBE R04576. There are no processing Options for the Payment Register R04576.

    Caution: Data Sequence for Payment Register R04576 has sequences that are required. Please refer to OMW and Design Aid to see those beginning 3 or 4 required items that the report depends on.

    Address Book Exception Report (R00311A)

    Address Book Exception Report (R00311A)

    The Address Book Exception Report can be accessed from the Automatic Payment Setup menu (G04411), and prints a list of address book records which:

    This report prints the address number, company name, payment instrument and search type. It uses three versions to sort customers and suppliers, just customers or just suppliers. This program does not update any information. If any records appear on the exception report, you must perform one of these actions:

    Additional Knowledge Resources