X12 820 Payment Order/Remittance Advice
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.
- ~ Segment
- * Element
- > Component
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code to identify the type of information in the Authorization Information
- 00
- No Authorization Information Present (No Meaningful Information in I02)
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)
Code to identify the type of information in the Security Information
- 00
- No Security Information Present (No Meaningful Information in I04)
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)
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
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
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
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
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
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
A control number assigned by the interchange sender
Code sent by the sender to request an interchange acknowledgment (TA1)
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code to indicate whether data enclosed by this interchange envelope is test, production or information
- I
- Information
- P
- Production Data
- T
- Test Data
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
To indicate the beginning of a functional group and to provide control information
Code identifying a group of application related transaction sets
- RA
- Payment Order/Remittance Advice (820)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission. Codes agreed to by trading partners
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)
Assigned number originated and maintained by the sender
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
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
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
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
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning Segment for Payment Order/Remittance Advice
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
Elements BPR-6 through BPR15 are used for electronic funds transfers.
Example: BPRI329600CCHKPBC320237722220200115
Code designating the action to be taken by all parties
- I
- Remittance Information Only
Monetary amount
- BPR02 specifies the payment amount.
Code indicating whether amount is a credit or debit
- C
- Credit
Code identifying the method for the movement of payment instructions
- CHK
- Check
Code identifying the payment format to be used
- PBC
- Commercial/Corporate Check
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).
Depository Financial Institution (DFI) identification number
Code indicating the type of account
- BPR08 is a code identifying the type of bank account or other financial asset.
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.
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
- 3200091189
- 3200091189
- 3202377222
- 3202377222
A code defined between the originating company and the originating depository financial institution (ODFI) that uniquely identifies the company initiating the transfer instructions
Code identifying the type of identification number of Depository Financial Institution (DFI)
- BPR12 and BPR13 relate to the receiving depository financial institution (RDFI).
Depository Financial Institution (DFI) identification number
Code indicating the type of account
- BPR14 is a code identifying the type of bank account or other financial asset.
Account number assigned
- BPR15 is the account number of the receiving company to be debited or credited with the payment order.
Date expressed as CCYYMMDD
- BPR16 is the date the originating company intends for the transaction to be settled (i.e., Payment Effective Date).
Check Number
To specify identifying information
To identify the Originator’s trace number.
Example: REFCK0496872
Code qualifying the Reference Identification
- CK
- Check Number
- EF
- Electronic Funds Transfer ID Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Detail
Entity
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*1
Number assigned for differentiation within a transaction set
Adjustment
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: ADX58.38ZZDBVC1158019B
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.
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
Code qualifying the Reference Identification
- ADX03 and ADX04 specify the identification of the adjustment.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Reference Identification
To specify identifying information
Example: REFCMLLSLONG-TERM LICENSEE ADVANCE
Code qualifying the Reference Identification
- CM
- Buyer's Credit Memo
- DB
- Buyer's Debit Memo
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Date/Time Reference
To specify pertinent dates and times
Example: DTM09720200111
Remittance Advice Accounts Receivable Open Item Reference
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.
RMR Segment is repeated for each PO associated with ASN or each Store associated with the Consignment or SBT payment.
The reference identification will match one of the following: ASN# or vendor REF# on the corresponding ASN, the Consignment or Scan Based Trading (SBT) invoice #, or the Vendor Reference Invoice#.
RMR04 amount will include HST/GST. RMR05 amount excludes HST/GST - will be different if there are any discrepancies.
Example: RMRIV4312884M21285259999999PO2255.48*2255.48
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
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
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
- PO
- Payment on Account
Monetary amount
- RMR04 is the amount paid.
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.
Monetary amount
- RMR06 is the amount of discount taken.
Regular Merchandise Only
Bill of Lading Number or Shipper's Identifying Number for Shipment (SID)
To specify identifying information
Segment is used to provide relevant PO reference or store number for consignment of SBT. The second occurrence is provided to reference shipment or BOL number from the ASN.
Example: REFSIM212852
Code qualifying the Reference Identification
- BM
- Bill of Lading Number
- SI
- Shipper's Identifying Number for Shipment (SID)
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Purchase Order Number or Store Number
To specify identifying information
Segment is used to provide relevant PO reference or store number for consignment of SBT. The second occurrence is provided to reference shipment or BOL number from the ASN.
Example: REFPO43128840591
Code qualifying the Reference Identification
- PO
- Purchase Order Number
- ST
- Store Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Date/Time Reference
To specify pertinent dates and times
Example: DTM09720191203
Baseline Item Data (Invoice)
To specify the basic and most frequently used line item data for the invoice and related transactions
- Loop IT1 within the RMR loop is the remittance line item detail loop.
Example: IT111EA1996*UP999905418038IN90541803ITAB8371BOBLUEIZS
Alphanumeric characters assigned for differentiation within a transaction set
- IT101 is the purchase order line item identification.
Number of units invoiced (supplier units)
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Price per unit of product, service, commodity, etc.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IT106 through IT125 provide for ten different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
- EN
- European Article Number (EAN) (2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IN
- Buyer's Item Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IT
- Buyer's Style Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- BO
- Buyers Color
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IZ
- Buyer's Size Code
Identifying number for a product or service
Adjustment
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).
For GST, QST, discounts, and surcharges, the message “GST PAYABLE”, or “QST PAYABLE”, or ‘DISCOUNT’ or ‘SURCHARGE’ will appear in the NTE segment.
Example: ADX259.48BC
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.
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.
- BA
- Canadian Goods and Services Tax
- BB
- Quebec Goods and Services Tax
- BC
- Canadian Harmonized Goods and Services Tax
- L2
- Discount
- L3
- Penalty
Charger or Penalty
- L7
- Miscellaneous Deductions
Credit
- L8
- Miscellaneous Credits
Debit
Note/Special Instruction
To transmit information in a free-form format, if necessary, for comment or special instruction
Example: NTE**HST PAYABLE
A free-form description to clarify the related data elements and their content
Baseline Item Data (Invoice)
To specify the basic and most frequently used line item data for the invoice and related transactions
- Loop IT1 within the ADX loop is the adjustment line item detail loop.
This will only be included if preceded by ADX with L7 (credit) or L8 (Debit).
Example:
IT111EA1996*UP999905418038IN90541803ITAB8371BOBLUEIZS
Alphanumeric characters assigned for differentiation within a transaction set
- IT101 is the purchase order line item identification.
Number of units invoiced (supplier units)
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Price per unit of product, service, commodity, etc.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IT106 through IT125 provide for ten different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
- EN
- European Article Number (EAN) (2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IN
- Buyer's Item Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IT
- Buyer's Style Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- BO
- Buyers Color
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IZ
- Buyer's Size Code
Identifying number for a product or service
Summary
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Total number of segments included in a transaction set including ST and SE segments
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Functional Group Trailer
To indicate the end of a functional group and to provide control information
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element
Assigned number originated and maintained by the sender
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Sample 1
GS*RA*SENDERGS*RECEIVERGS*20231101*015424*000000001*X*004010
ST*820*401046831
BPR*I*1134*C*CHK*PBC*****3200091189******20200115
REF*CK*0062088
ENT*1
RMR*IV*7877299000001187663*PO*1134*1134
REF*PO*37247500504
REF*SI*M253744
DTM*097*20200113
IT1*1*1*EA*1080**UP*999999391977*IN*88690656*IT*788602*BO*BLACK*IZ*32
ADX*54*BA
NTE**GST PAYABLE
SE*12*401046831
GE*1*000000001
IEA*1*000000001
Sample 2
GS*RA*SENDERGS*RECEIVERGS*20231101*015433*000000001*X*004010
ST*820*304001075
BPR*I*329600*C*CHK*PBC*****3202377222******20200115
REF*CK*0496872
ENT*1
ADX*329600*ZZ*CM*SGP12011120OLS
REF*CM*LLSLONG-TERM LICENSEE ADVANCE
REF*CM*ATEMENT
DTM*097*20200111
SE*9*304001075
GE*1*000000001
IEA*1*000000001
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.