Addenda records will be used by the Originator to sup0ply additional information about Entry Detail Records which will be passed from the ODFI through the ACH Operator to the RDFI. Addenda records associated with the original Entry Detail Record or Corporate Entry Detail Record will not be included with any Entry Detail Record being returned. Only NACHA sanctioned formats will be permitted, as specified by the Addenda Type Code.
In this application dealing only with “PPD” applications, there can be at most 1 addenda record. Even then the addenda record is optional in this case.
Position |
Size |
Contents |
Data Element Description |
Required |
|---|---|---|---|---|
01-01 |
1 |
‘7’ |
Record Type Code - entry detail record format |
X |
02-03 |
2 |
‘05’ = Addenda Records (Applies to PPD Entries) |
Addenda Type Code |
X |
04-83 |
80 |
Customer’s Order No. from the Membership Record |
Payment Related Information (lpad with zeros - 14 characters in order number plus line number. Lpad the line number with zeros also so that it has a length of 3) Order_detail.order_no + ‘-‘ + order_detail.line_no + receipt_no (lpad 0s to cover 12 positions) (This information would be returned back from bank in the return addenda record, based on this information we should be able to identify the receipt that we created as part of the EFT). This information will be returned in position 36:79 as defined in EFT0002 process. Addenda Record (Right click on Addend record and click on open link to go to EFT681 specs of addenda record) |
X |
84-87 |
4 |
Consecutively assigned to each Addenda Record following a Detail Record Numeric = ‘0001’ |
Addenda Sequence Number - ‘0001’ There will only be one per PPD Entry Detail Record for this application. |
X |
88-94 |
7 |
The last 7 digits of the trace number of the related Entry Detail Record |
Entry Detail Sequence Number |
X |
Also in this section:
· Company/Batch Header Record Format
· Entry Detail Record, Corporate Entry Detail Record Format
· Company/Batch Control Record Format