H-E-B
/
Payment Order/Remittance Advice
  • Specification
  • EDI Inspector
Import guide into your account
Stedi maintains this guide based on public documentation from H-E-B. Contact H-E-B for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
H-E-B logo

X12 820 Payment Order/Remittance Advice

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data contents of the Payment Order/Remittance Advice Transaction Set (820) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to make a payment, send a remittance advice, or make a payment and send a remittance advice.

This transaction set can be an order to a financial institution to make a payment to a payee. It can also be a remittance advice identifying the detail needed to perform cash application to the payee's accounts receivable system.
The remittance advice can go directly from payer to payee, through a financial institution, or through a third party agent.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI sample
—
    View the latest version of this implementation guide as an interactive webpage
    Powered by
    Build EDI implementation guides at stedi.com
    Overview
    ISA
    -
    Interchange Control Header
    Max use 1
    Required
    GS
    -
    Functional Group Header
    Max use 1
    Required
    heading
    ST
    010
    Transaction Set Header
    Max use 1
    Required
    BPR
    020
    Beginning Segment for Payment Order/Remittance Advice
    Max use 1
    Required
    TRN
    035
    Trace
    Max use 1
    Optional
    DTM
    060
    Date/Time Reference
    Max use 1
    Optional
    Payee
    N1
    070
    Name
    Max use 1
    Required
    Payer
    N1
    070
    Name
    Max use 1
    Required
    detail
    ENT Loop
    ENT
    010
    Entity
    Max use 1
    Required
    ADX Loop
    ADX
    080
    Adjustment
    Max use 1
    Required
    REF Loop
    REF
    110
    Reference Identification
    Max use 1
    Required
    RMR Loop
    RMR
    150
    Remittance Advice Accounts Receivable Open Item Reference
    Max use 1
    Required
    REF
    170
    Reference Identification
    Max use 1
    Required
    DTM
    180
    Date/Time Reference
    Max use 1
    Required
    summary
    SE
    010
    Transaction Set Trailer
    Max use 1
    Required
    GE
    -
    Functional Group Trailer
    Max use 1
    Required
    IEA
    -
    Interchange Control Trailer
    Max use 1
    Required
    ISA

    Interchange Control Header

    RequiredMax use 1

    To start and identify an interchange of zero or more functional groups and interchange-related control segments

    Example
    ISA-01
    I01
    Authorization Information Qualifier
    Required

    Code to identify the type of information in the Authorization Information

    00
    No Authorization Information Present (No Meaningful Information in I02)
    ISA-02
    I02
    Authorization Information
    Required
    Min 10Max 10

    Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)

    ISA-03
    I03
    Security Information Qualifier
    Required

    Code to identify the type of information in the Security Information

    00
    No Security Information Present (No Meaningful Information in I04)
    ISA-04
    I04
    Security Information
    Required
    Min 10Max 10

    This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)

    ISA-05
    I05
    Interchange ID Qualifier
    Required
    Min 2Max 2

    Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

    Codes
    ISA-06
    I06
    Interchange Sender ID
    Required
    Min 15Max 15

    Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element

    ISA-07
    I05
    Interchange ID Qualifier
    Required
    Min 2Max 2

    Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

    Codes
    ISA-08
    I07
    Interchange Receiver ID
    Required
    Min 15Max 15

    Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them

    ISA-09
    I08
    Interchange Date
    Required
    YYMMDD format

    Date of the interchange

    ISA-10
    I09
    Interchange Time
    Required
    HHMM format

    Time of the interchange

    ISA-11
    I10
    Interchange Control Standards Identifier
    Required

    Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer

    U
    U.S. EDI Community of ASC X12, TDCC, and UCS
    ISA-12
    I11
    Interchange Control Version Number
    Required

    This version number covers the interchange control segments

    00401
    Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
    ISA-13
    I12
    Interchange Control Number
    Required
    Min 9Max 9

    A control number assigned by the interchange sender

    ISA-14
    I13
    Acknowledgment Requested
    Required
    Min 1Max 1

    Code sent by the sender to request an interchange acknowledgment (TA1)

    0
    No Acknowledgment Requested
    1
    Interchange Acknowledgment Requested
    ISA-15
    I14
    Usage Indicator
    Required
    Min 1Max 1

    Code to indicate whether data enclosed by this interchange envelope is test, production or information

    I
    Information
    P
    Production Data
    T
    Test Data
    ISA-16
    I15
    Component Element Separator
    Required
    Min 1Max 1

    Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator

    >
    Component Element Separator
    GS

    Functional Group Header

    RequiredMax use 1

    To indicate the beginning of a functional group and to provide control information

    Example
    GS-01
    479
    Functional Identifier Code
    Required

    Code identifying a group of application related transaction sets

    RA
    Payment Order/Remittance Advice (820)
    GS-02
    142
    Application Sender's Code
    Required
    Min 2Max 15

    Code identifying party sending transmission; codes agreed to by trading partners

    GS-03
    124
    Application Receiver's Code
    Required
    Min 2Max 15

    Code identifying party receiving transmission. Codes agreed to by trading partners

    GS-04
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    GS-05
    337
    Time
    Required
    HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

    Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

    GS-06
    28
    Group Control Number
    Required
    Min 1Max 9

    Assigned number originated and maintained by the sender

    GS-07
    455
    Responsible Agency Code
    Required
    Min 1Max 2

    Code used in conjunction with Data Element 480 to identify the issuer of the standard

    T
    Transportation Data Coordinating Committee (TDCC)
    X
    Accredited Standards Committee X12
    GS-08
    480
    Version / Release / Industry Identifier Code
    Required

    Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed

    004010
    Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997

    Heading

    ST
    010

    Transaction Set Header

    RequiredMax use 1

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

    Example
    ST-01
    143
    Transaction Set Identifier Code
    Required

    Code uniquely identifying a Transaction Set

    • The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
    820
    Payment Order/Remittance Advice
    ST-02
    329
    Transaction Set Control Number
    Required
    Min 4Max 9

    Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

    BPR
    020

    Beginning Segment for Payment Order/Remittance Advice

    RequiredMax use 1

    To indicate the beginning of a Payment Order/Remittance Advice Transaction Set and total payment amount, or to enable related transfer of funds and/or information from payer to payee to occur

    Example
    BPR-01
    305
    Transaction Handling Code
    Required

    Code designating the action to be taken by all parties

    C
    Payment Accompanies Remittance Advice
    D
    Make Payment Only
    BPR-02
    782
    Monetary Amount
    Required
    Min 1Max 15

    Monetary amount

    • BPR02 specifies the payment amount.
    Usage notes

    Total value including the decimal point.

    BPR-03
    478
    Credit/Debit Flag Code
    Required

    Code indicating whether amount is a credit or debit

    C
    Credit
    BPR-04
    591
    Payment Method Code
    Required

    Code identifying the method for the movement of payment instructions

    ACH
    Automated Clearing House (ACH)
    BPR-05
    812
    Payment Format Code
    Required
    Min 1Max 10

    Code identifying the payment format to be used

    BPR-06
    506
    (DFI) ID Number Qualifier
    Required

    Code identifying the type of identification number of Depository Financial Institution (DFI)

    • When using this transaction set to initiate a payment, all or some of BPR06 through BPR16 may be required, depending on the conventions of the specific financial channel being used.
    • BPR06 and BPR07 relate to the originating depository financial institution (ODFI).
    01
    ABA Transit Routing Number Including Check Digits (9 digits)
    BPR-07
    507
    (DFI) Identification Number
    Required
    Min 3Max 12

    Depository Financial Institution (DFI) identification number

    Usage notes

    DFI HEB Routing Number

    BPR-08
    569
    Account Number Qualifier
    Required

    Code indicating the type of account

    • BPR08 is a code identifying the type of bank account or other financial asset.
    DA
    Demand Deposit
    BPR-09
    508
    Account Number
    Required
    Min 1Max 35

    Account number assigned

    • BPR09 is the account of the company originating the payment. This account may be debited or credited depending on the type of payment order.
    Usage notes

    HEB Accounting Number

    BPR-10
    509
    Originating Company Identifier
    Required
    Min 10Max 10

    A unique identifier designating the company initiating the funds transfer instructions. The first character is one-digit ANSI identification code designation (ICD) followed by the nine-digit identification number which may be an IRS employer identification number (EIN), data universal numbering system (DUNS), or a user assigned number; the ICD for an EIN is 1, DUNS is 3, user assigned number is 9

    Usage notes

    HEB "3" & DUNS Number

    BPR-11
    510
    Originating Company Supplemental Code
    Required
    Min 9Max 9

    A code defined between the originating company and the originating depository financial institution (ODFI) that uniquely identifies the company initiating the transfer instructions

    BPR-12
    506
    (DFI) ID Number Qualifier
    Required

    Code identifying the type of identification number of Depository Financial Institution (DFI)

    • BPR12 and BPR13 relate to the receiving depository financial institution (RDFI).
    01
    ABA Transit Routing Number Including Check Digits (9 digits)
    BPR-13
    507
    (DFI) Identification Number
    Required
    Min 3Max 12

    Depository Financial Institution (DFI) identification number

    Usage notes

    DFI Receiving Bank ABA Routing Number

    BPR-14
    569
    Account Number Qualifier
    Required

    Code indicating the type of account

    • BPR14 is a code identifying the type of bank account or other financial asset.
    DA
    Demand Deposit
    BPR-15
    508
    Account Number
    Required
    Min 1Max 35

    Account number assigned

    • BPR15 is the account number of the receiving company to be debited or credited with the payment order.
    Usage notes

    Vendor's Bank Account Number

    BPR-16
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    • BPR16 is the date the originating company intends for the transaction to be settled (i.e., Payment Effective Date).
    Usage notes

    Intended Settlement Date

    TRN
    035

    Trace

    OptionalMax use 1

    To uniquely identify a transaction to an application

    • The TRN segment is used to uniquely identify a payment order/remittance advice.
    Example
    TRN-01
    481
    Trace Type Code
    Required

    Code identifying which transaction is being referenced

    1
    Current Transaction Trace Numbers
    TRN-02
    127
    Reference Identification
    Required
    Min 1Max 30

    Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

    • TRN02 provides unique identification for the transaction.
    Usage notes

    Check Number

    TRN-03
    509
    Originating Company Identifier
    Required
    Min 10Max 10

    A unique identifier designating the company initiating the funds transfer instructions. The first character is one-digit ANSI identification code designation (ICD) followed by the nine-digit identification number which may be an IRS employer identification number (EIN), data universal numbering system (DUNS), or a user assigned number; the ICD for an EIN is 1, DUNS is 3, user assigned number is 9

    • TRN03 identifies an organization.
    Usage notes

    HEB DUNS Number

    DTM
    060

    Date/Time Reference

    OptionalMax use >1

    To specify pertinent dates and times

    Example
    DTM-01
    374
    Date/Time Qualifier
    Required

    Code specifying type of date or time, or both date and time

    009
    Process
    DTM-02
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    N1 Payee
    RequiredMax >1
    Variants (all may be used)
    N1Payer
    N1
    070

    Name

    RequiredMax use 1

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

    • The N1 loop allows for name/address information for the payer and payee which would be utilized to address remittance(s) for delivery.
    Example
    At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
    If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
    N1-01
    98
    Entity Identifier Code
    Required

    Code identifying an organizational entity, a physical location, property or an individual

    PE
    Payee
    N1-02
    93
    Name
    Required
    Min 1Max 60

    Free-form name

    Usage notes

    Organizational Name

    N1-03
    66
    Identification Code Qualifier
    Optional

    Code designating the system/method of code structure used for Identification Code (67)

    1
    D-U-N-S Number, Dun & Bradstreet
    N1-04
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    • This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
    Usage notes

    HEB DUNS Number

    N1-05
    706
    Entity Relationship Code
    Optional
    Min 2Max 2

    Code describing entity relationship

    • N105 and N106 further define the type of entity in N101.
    N1-06
    98
    Entity Identifier Code
    Optional
    Min 2Max 3

    Code identifying an organizational entity, a physical location, property or an individual

    N1 Payer
    RequiredMax >1
    Variants (all may be used)
    N1Payee
    N1
    070

    Name

    RequiredMax use 1

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

    • The N1 loop allows for name/address information for the payer and payee which would be utilized to address remittance(s) for delivery.
    Example
    At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
    If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
    N1-01
    98
    Entity Identifier Code
    Required

    Code identifying an organizational entity, a physical location, property or an individual

    PR
    Payer
    N1-02
    93
    Name
    Required
    Min 1Max 60

    Free-form name

    Usage notes

    Organizational Name

    N1-03
    66
    Identification Code Qualifier
    Optional

    Code designating the system/method of code structure used for Identification Code (67)

    1
    D-U-N-S Number, Dun & Bradstreet
    N1-04
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    • This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
    Usage notes

    HEB DUNS Number

    N1-05
    706
    Entity Relationship Code
    Optional
    Min 2Max 2

    Code describing entity relationship

    • N105 and N106 further define the type of entity in N101.
    N1-06
    98
    Entity Identifier Code
    Optional
    Min 2Max 3

    Code identifying an organizational entity, a physical location, property or an individual

    Detail

    ENT Loop
    OptionalMax >1
    ENT
    010

    Entity

    RequiredMax use 1

    To designate the entities which are parties to a transaction and specify a reference meaningful to those entities

    • The ENT loop is for vendor or consumer third party consolidated payments.
    • ENT09 may contain the payee's accounts receivable customer number.
    Example
    ENT-01
    554
    Assigned Number
    Required
    Min 1Max 6

    Number assigned for differentiation within a transaction set

    ADX Loop
    RequiredMax >1
    ADX
    080

    Adjustment

    RequiredMax use 1

    To convey accounts-payable adjustment information for the purpose of cash application, including payer-generated debit/credit memos

    • This ADX loop contains adjustment items which are not netted to an RMR segment in this transaction set.
    Example
    ADX-01
    782
    Monetary Amount
    Required
    Min 1Max 15

    Monetary amount

    • ADX01 specifies the amount of the adjustment and must be signed if negative. If negative, it reduces the payment amount; if positive, it increases the payment amount.
    Usage notes

    Signed Adjustment Value including decimal point. EG// 999999999999.99

    ADX-02
    426
    Adjustment Reason Code
    Required

    Code indicating reason for debit or credit memo or adjustment to invoice, debit or credit memo, or payment

    • ADX02 specifies the reason for claiming the adjustment.
    ZZ
    Mutually Defined
    ADX-03
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    • ADX03 and ADX04 specify the identification of the adjustment.
    CM
    Buyer's Credit Memo
    ADX-04
    127
    Reference Identification
    Required
    Min 1Max 30

    Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

    Usage notes

    Invoice Number

    REF Loop
    OptionalMax >1
    REF
    110

    Reference Identification

    RequiredMax use 1

    To specify identifying information

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    LU
    Location Number
    REF-02
    127
    Reference Identification
    Required
    Min 1Max 30

    Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

    Usage notes

    Store Number

    RMR Loop
    RequiredMax >1
    RMR
    150

    Remittance Advice Accounts Receivable Open Item Reference

    RequiredMax use 1

    To specify the accounts receivable open item(s) to be included in the cash application and to convey the appropriate detail

    • Loop RMR is for open items being referenced or for payment on account.
    Example
    RMR-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    • Parties using this segment should agree on the content of RMR01 and RMR02 prior to initiating communication.
    IV
    Seller's Invoice Number
    RMR-02
    127
    Reference Identification
    Required
    Min 1Max 30

    Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

    Usage notes

    Sellers Invoice Number

    RMR-03
    482
    Payment Action Code
    Optional
    Min 2Max 2

    Code specifying the accounts receivable open item(s), if any, to be included in the cash application.

    • If RMR03 is present, it specifies how the cash is to be applied.
    • If RMR03 is not present, this is a payment for an open item. If paying an open item, RMR02 must be present. If not paying a specific open item, RMR04 must be present.
    RMR-04
    782
    Monetary Amount
    Required
    Min 1Max 15

    Monetary amount

    • RMR04 is the amount paid.
    Usage notes

    Signed Net Value including decimal point. 999999999999.99

    RMR-05
    782
    Monetary Amount
    Required
    Min 1Max 15

    Monetary amount

    • RMR05 is the amount of invoice (including charges, less allowance) before terms discount (if discount is applicable) or debit amount or credit amount of referenced items.
    • RMR05 may be needed by some payees to distinguish between duplicate reference numbers.
    Usage notes

    Signed Adjustment Value including decimal point. 999999999999.99

    RMR-06
    782
    Monetary Amount
    Optional
    Min 1Max 15

    Monetary amount

    • RMR06 is the amount of discount taken.
    Usage notes

    Signed Discount Value including decimal point. 999999999999.99

    REF
    170

    Reference Identification

    RequiredMax use >1

    To specify identifying information

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    LU
    Location Number
    REF-02
    127
    Reference Identification
    Required
    Min 1Max 30

    Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

    Usage notes

    Store Number

    DTM
    180

    Date/Time Reference

    RequiredMax use >1

    To specify pertinent dates and times

    Example
    DTM-01
    374
    Date/Time Qualifier
    Required

    Code specifying type of date or time, or both date and time

    003
    Invoice
    DTM-02
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    Summary

    SE
    010

    Transaction Set Trailer

    RequiredMax use 1

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

    Example
    SE-01
    96
    Number of Included Segments
    Required
    Min 1Max 10

    Total number of segments included in a transaction set including ST and SE segments

    SE-02
    329
    Transaction Set Control Number
    Required
    Min 4Max 9

    Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

    GE

    Functional Group Trailer

    RequiredMax use 1

    To indicate the end of a functional group and to provide control information

    Example
    GE-01
    97
    Number of Transaction Sets Included
    Required
    Min 1Max 6

    Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

    GE-02
    28
    Group Control Number
    Required
    Min 1Max 9

    Assigned number originated and maintained by the sender

    IEA

    Interchange Control Trailer

    RequiredMax use 1

    To define the end of an interchange of zero or more functional groups and interchange-related control segments

    Example
    IEA-01
    I16
    Number of Included Functional Groups
    Required
    Min 1Max 5

    A count of the number of functional groups included in an interchange

    IEA-02
    I12
    Interchange Control Number
    Required
    Min 9Max 9

    A control number assigned by the interchange sender

    EDI Samples

    Sample

    ST*820*76210001
    BPR*C*.01*C*ACH**01*123456789*DA*HEB A/C No*AAAAAAAAAA*BBBBBBBBB*01*CCCCCCCCC*DA*VENDOR’S Bank A/c No.*20100524
    TRN*1*DDDDDDDDDDD*EEEEEEEEE
    REF*CK*0002237118
    DTM*009*20100524
    N1*PR*H.E.B.*1*007924756
    N1*PE*TRADING PARTNER NAME
    ENT*1
    RMR*IV*test00007936**.01*.01
    DTM*003*20100524
    SE*11*76210001

    Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page 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. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.