EDI 828 Debit Authorization

Functional Group DA

X12F Finance Subcommittee

This Draft Standard for Trial Use contains the format and establishes the data contents of the Debit Authorization Transaction Set (828) within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to provide information from the Paying Entity to the Financial Institution regarding debits that the Paying Entity has authorized against its account. The Financial Institution would hold this information then match it against incoming debits to determine whether those debits have been authorized by the account holder. This transaction set can be used to add new authorizations or cancel existing authorizations. With regard to electronic debits, this would be used for ACH debit processing only. This transaction set can also be used for paper-based debits (i.e. checks). In the paper-based world, this transaction set would serve the purpose of the "issuance file" or "check register"used in account reconciliation applications. Either one time or recurring debits can be authorized with this transaction set. One transaction set can be used to identify multiple debit authorization details against one bank account.

Heading

1. 010 · ST · Transaction Set Header · Max 1 · Mandatory

   To indicate the start of a transaction set and to assign a control number

2. 020 · BAU · Beginning Segment for the Debit Authorization · Max 1 · Mandatory

   To identify the beginning of the Debit Authorization transaction set. The BAU segment is used to identify the Financial Institution and Account of the Payer (i.e. the party authorizing the debit against its account)

   The BAU segment contains information about the account being debited.

3. 030 · PER · Administrative Communications Contact · Max 3 · Optional

   To identify a person or office to whom administrative communications should be directed

   The PER segment contents shall identify the party to be contacted for resolution of debit authorization errors, and must have signing authority on the account, if used.

4. 040 · DAD · Debit Authorization Detail · Max 999990 · Mandatory

   To provide detail information about the Debit Authorization

   The DAD segment contains detail information regarding individual debit authorizations. The content refers to the originator of the debit, where as the BAU refers to the holder of the account being debited.

5. N1 Loop Optional Repeat 1

   1. 050 · N1 · Name · Max 1 · Mandatory

      To identify a party by type of organization, name and code

      The N1 through N4 information shall refer to the originator of the Debit Authorization, if it is used.

   2. 060 · N2 · Additional Name Information · Max 2 · Optional

      To specify additional names or those longer than 35 characters in length

   3. 070 · N3 · Address Information · Max 2 · Optional

      To specify the location of the named party

   4. 080 · N4 · Geographic Location · Max 1 · Optional

      To specify the geographic place of the named party

Detail

1. 010 · CTT · Transaction Totals · Max 1 · Mandatory

   To transmit a hash total for a specific element in the transaction set

   The CTT segment shall contain a count of the number of DAD segments in CTT01. Other data elements of the CTT segment should not be used.

2. 020 · AMT · Monetary Amount · Max 1 · Optional

   To indicate the total monetary amount.

   AMT segment is used to reflect the sum of Debit Authorization Detail monetary amounts (DAD08). The total amount shall appear in AMT02, with a qualifier of "TT" in AMT01.

3. 030 · SE · Transaction Set Trailer · Max 1 · Mandatory

   To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments).