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) for use 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

Position
Segment
Name
Max use
  1. To indicate the start of a transaction set and to assign a control number

  2. 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. 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.
  4. To specify additional names

  5. To specify the location of the named party

  6. To specify the geographic place of the named party

  7. To specify identifying information

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

Detail

Position
Segment
Name
Max use
  1. DAD Loop Mandatory
    Repeat >1
    1. To provide detail information about the debit authorization

      The DAD segment contains detail information regarding the 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.
    2. To supply the full name of an individual or organizational entity

      If used, the NM1, N3, N4, REF and PER segments shall refer to the payee of the authorization detailed in the DAD segment.
    3. To specify additional names

    4. To specify the location of the named party

    5. To specify the geographic place of the named party

    6. To specify identifying information

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

Summary

Position
Segment
Name
Max use
  1. 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. To indicate the total monetary amount

    The 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. To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Stedi is a registered trademark of Stedi, Inc. Stedi's EDI Reference is provided for marketing purposes and is free of charge. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.