Kroger
/
Payment Order/Remittance Advice
  • Specification
  • EDI Inspector
Import
Stedi maintains this guide based on public documentation from Kroger. Contact Kroger for official EDI specifications. To report any errors in this guide, please contact us.
Go to EDI Guide Catalog
Kroger logo

X12 820 Payment Order/Remittance Advice

X12 Release 5010

This X12 Transaction Set 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
  • ^ Repetition
EDI sample
    View the latest version of this implementation guide as an interactive webpage
    Powered by
    Build free 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
    0100
    Transaction Set Header
    Max use 1
    Required
    BPR
    0200
    Beginning Segment for Payment Order/Remittance Advice
    Max use 1
    Required
    TRN
    0350
    Trace
    Max use 1
    Optional
    DTM
    0600
    Date/Time Reference
    Max use 1
    Optional
    Buying Party (Purchaser)
    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 identifying 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 identifying 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

    Code indicating 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

    Code indicating 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
    I65
    Repetition Separator
    Required
    Min 1Max 1

    Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator

    ^
    Repetition Separator
    ISA-12
    I11
    Interchange Control Version Number
    Required

    Code specifying the version number of the interchange control segments

    00501
    Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003
    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 indicating sender's request for an interchange acknowledgment

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

    Code indicating 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

    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 where CC represents the first two digits of the calendar year

    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 identifying the issuer of the standard; this code is used in conjunction with Data Element 480

    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

    005010
    Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003

    Heading

    ST
    0100

    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) is 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
    0200

    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

    I
    Remittance Information Only
    BPR-02
    782
    Monetary Amount
    Required
    Min 1Max 15

    Monetary amount

    • BPR02 specifies the payment amount.
    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

    CHK
    Check
    TRN
    0350

    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 50

    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

    Kroger Check Number

    DTM
    0600

    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
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

    Usage notes

    CCYYMMDD

    N1 Buying Party (Purchaser)
    OptionalMax >1
    Variants (all may be used)
    N1Payee
    N1
    0700

    Party Identification

    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

    BY
    Buying Party (Purchaser)
    N1-02
    93
    Name
    Optional
    Min 1Max 60

    Free-form name

    Usage notes

    Kroger Co.

    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
    92
    Assigned by Buyer or Buyer's Agent
    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

    '006999528'

    N3
    0900

    Party Location

    OptionalMax use >1

    To specify the location of the named party

    Example
    N3-01
    166
    Address Information
    Required
    Min 1Max 55

    Address information

    N4
    1000

    Geographic Location

    OptionalMax use 1

    To specify the geographic place of the named party

    Example
    N4-01
    19
    City Name
    Optional
    Min 2Max 30

    Free-form text for city name

    • A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
    N4-02
    156
    State or Province Code
    Optional
    Min 2Max 2

    Code (Standard State/Province) as defined by appropriate government agency

    • N402 is required only if city name (N401) is in the U.S. or Canada.
    N4-03
    116
    Postal Code
    Optional
    Min 3Max 15

    Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

    N4-04
    26
    Country Code
    Optional
    Min 2Max 3

    Code identifying the country

    N1 Payee
    OptionalMax >1
    Variants (all may be used)
    N1Buying Party (Purchaser)
    N1
    0700

    Party Identification

    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
    Optional
    Min 1Max 60

    Free-form name

    Usage notes

    Vendor 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
    92
    Assigned by Buyer or Buyer's Agent
    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

    Oracle Remit site ID

    N3
    0900

    Party Location

    OptionalMax use >1

    To specify the location of the named party

    Example
    N3-01
    166
    Address Information
    Required
    Min 1Max 55

    Address information

    N4
    1000

    Geographic Location

    OptionalMax use 1

    To specify the geographic place of the named party

    Example
    N4-01
    19
    City Name
    Optional
    Min 2Max 30

    Free-form text for city name

    • A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
    N4-02
    156
    State or Province Code
    Optional
    Min 2Max 2

    Code (Standard State/Province) as defined by appropriate government agency

    • N402 is required only if city name (N401) is in the U.S. or Canada.
    N4-03
    116
    Postal Code
    Optional
    Min 3Max 15

    Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

    N4-04
    26
    Country Code
    Optional
    Min 2Max 3

    Code identifying the country

    Detail

    ENT Loop
    OptionalMax >1
    ENT
    0100

    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
    Optional
    Min 1Max 6

    Number assigned for differentiation within a transaction set

    Usage notes

    Kroger Division Number

    NM1 Loop
    OptionalMax >1
    NM1
    0200

    Individual or Organizational Name

    RequiredMax use 1

    To supply the full name of an individual or organizational entity

    • Allowing the NM1 segment to repeat in this area allows the paying entity within a payer and the paid entity within a payee to be identified (not the payer and payee).
    Example
    If either Identification Code Qualifier (NM1-08) or Identification Code (NM1-09) is present, then the other is required
    NM1-01
    98
    Entity Identifier Code
    Required

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

    PE
    Payee
    SN
    Store
    NM1-02
    1065
    Entity Type Qualifier
    Required

    Code qualifying the type of entity

    • NM102 qualifies NM103.
    4
    Corporation
    NM1-03
    1035
    Name Last or Organization Name
    Optional
    Min 1Max 60

    Individual last name or organizational name

    Usage notes

    Kroger Division

    NM1-08
    66
    Identification Code Qualifier
    Optional

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

    92
    Assigned by Buyer or Buyer's Agent
    NM1-09
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    Usage notes

    4-digit division number + 6-digit store number + Oracle Remit site ID.

    RMR Loop
    OptionalMax >1
    RMR
    1500

    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
    If either Reference Identification Qualifier (RMR-01) or Reference Identification (RMR-02) is present, then the other is required
    RMR-01
    128
    Reference Identification Qualifier
    Optional

    Code qualifying the Reference Identification

    • Parties using this segment should agree on the content of RMR01 and RMR02 prior to initiating communication.
    AP
    Accounts Receivable Number
    CL
    Seller's Credit Memo
    CM
    Buyer's Credit Memo
    IV
    Seller's Invoice Number
    RMR-02
    127
    Reference Identification
    Optional
    Min 1Max 50

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

    Usage notes

    Invoice #

    RMR-03
    482
    Payment Action Code
    Optional

    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.
    ER
    Evaluated Receipts Settlement
    RMR-04
    782
    Monetary Amount
    Optional
    Min 1Max 15

    Monetary amount

    • RMR04 is the amount paid.
    Usage notes

    Net Invoice Amt.

    RMR-05
    782
    Monetary Amount
    Optional
    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

    Gross Invoice Amt.

    RMR-06
    782
    Monetary Amount
    Optional
    Min 1Max 15

    Monetary amount

    • RMR06 is the amount of discount taken.
    Usage notes

    Discount Amount Taken - Always a deduction.

    REF
    1700

    Data Item Description (DID) Reference

    OptionalMax use >1

    To specify identifying information

    Example
    Variants (all may be used)
    REFBatch Number
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    82
    Data Item Description (DID) Reference
    REF-02
    127
    Reference Identification
    Optional
    Min 1Max 50

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

    REF
    1700

    Batch Number

    OptionalMax use >1

    To specify identifying information

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    BT
    Batch Number
    REF-02
    127
    Reference Identification
    Optional
    Min 1Max 50

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

    DTM
    1800

    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

    003
    Invoice
    DTM-02
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

    Usage notes

    Date of Invoice - CCYYMMDD.

    ADX Loop
    OptionalMax >1
    ADX
    2100

    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 can only contain adjustment information for the immediately preceding RMR segment and affects the amount (RMR04) calculation. If this adjustment amount is not netted to the immediately preceding RMR, use the outer ADX loop (position 080).
    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

    Amount of Debit/Credit taken.

    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.
    02
    Allowance/Charge Error
    ZZ
    Mutually Defined
    NTE
    2200

    Note/Special Instruction

    OptionalMax use >1

    To transmit information in a free-form format, if necessary, for comment or special instruction

    Example
    NTE-02
    352
    Description
    Required
    Min 1Max 80

    A free-form description to clarify the related data elements and their content

    Summary

    SE
    0100

    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

    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

    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*0041~
    BPR*I*17907.54*C*CHK~
    TRN*1*500002760~
    DTM*009*20201208~
    N1*BY*KROGER*1*006999528~
    N1*PE*OLIVE MUSCO PRODUCTS INC*92*81178~
    ENT*92~
    NM1*PE*4*RASC OPERATING DIVISION*****92*009200167181178~
    RMR*IV*690383*ER*18755.2*19137.96*382.76~
    DTM*003*20201111~
    RMR*CL*TEST 01 OLIVE MUSCO*ER*-864.96*-864.96~
    DTM*003*20201116~
    SE*13*0041~

    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.