X12 820 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 one 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 sender or the data in the interchange. The type of information is set by the Authorization Information Qualifier.
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 sender or the data in the interchange. The type of information is set by the Security Information Qualifier.
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 number 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.
- 00304
- Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1993
This number uniquely identifies the interchange data to the sender. It is assigned by the sender. Together with the sender ID it uniquely identifies the interchange data to the receiver. It is suggested that the sender, receiver, and all third parties be able to maintain an audit trail of interchanges using this number.
Code sent by the sender to request an interchange acknowledgment.
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code to indicate whether data enclosed by this interchange envelope is test or production.
- P
- Production Data
- T
- Test Data
This is a field reserved for future expansion in separating data element subgroups. (In the interest of a migration to international standards, this must be different from the data element separator).
- >
- 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.
- 003040
- Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1993
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
- X12.4 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
(1) To indicate the beginning of a PaymentOrder/Remittance Advice Transaction Set and total payment amount or (2) to enable related transfer of funds and/or information from payer to payee to occur
Code designating the action to be taken by all parties.
- I
- Remittance Information Only
Monetary amount.
- BPR02 specifies the payment amount.
The total amount that TMS will pay. 2 decimals implied.
Code indicating whether amount is a credit or debit
- C
- Credit
- D
- Debit
Code identifying the method for the movement of payment instructions
- ACH
- Automated Clearing House (ACH)
- CHK
- Check
Code qualifying the Reference Number.
- IV
- Invoice Number
- SI
- Shipper's Identifying Number for Shipment (SID)
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.
Date/Time Reference
To specify pertinent dates and times
Name
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.
Code identifying an organizational entity, a physical location, or an individual
- VN
- Vendor Code
Code designating the system/method of code structure used for Identification Code (67).
- 92
- Assigned Buyer
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.
TMS assigned vendor code.
Detail
Entity
To designate the entities which are parties to a transaction and specify a reference meaningful to those entities
- ENT09 may contain the payee's accounts receivable customer number.
Number assigned for differentiation within a transaction set.
Assigned number. TMS uses a constant “999999”.
This loop is optional and will occur only in case of a price adjustment.
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.
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.
Monetary amount. Extended invoice price. 2 decimals implied.
Code indicating reason for credit memo, or adjustment to invoice, credit memo, or payment.
- ADX02 specifies the reason for claiming the adjustment.
Code qualifying the Reference Number.
- ADX03 and ADX04 specify the identification of the adjustment.
- SI
- Shipper's Identifying Number for Shipment (SID)
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.
This loop is optional. It will occur only in case of a unit price adjustment.
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.
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
- PC
- Piece
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 provides for ten (10) different product/service ID's for each item. For example: Case, Color, Drawing No., UPC No., ISBN No., Model No., SKU.
- PO
- Purchase Order Number
Identifying number for a product or service.
TMS purchase order number.
Code identifying the type/source of the descriptive number used in Product/Service ID (234).
- BP
- Buyer's Part Number
Identifying number for a product or service.
TMS part number.
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.
Code qualifying the Reference Number.
- Parties using this segment should agree on the content of RMR01 and RMR02 prior to initiating communication.
- SI
- Shipper's Identifying Number for Shipment (SID)
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.
Code specifying the type of accounts receivable open item(s) to be included in a 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
Monetary amount.
- RMR04 is the amount paid.
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.
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
- PC
- Piece
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 provides for ten (10) different product/service ID's for each item. For example: Case, Color, Drawing No., UPC No., ISBN No., Model No., SKU.
- PO
- Purchase Order Number
Identifying number for a product or service.
Code identifying the type/source of the descriptive number used in Product/Service ID (234).
- BP
- Buyer's Part Number
Identifying number for a product or service.
Allowance, Charge or Service
To specify allowances, charges or services
Code which indicates an allowance or charge for the service specified.
- If ITA01 = A-Allowance or C-Charge, then at least one of ITA06, ITA07, or ITA08 must be present.
- A
- Allowance
- C
- Charge
Code identifying the special service.
- 240
- Brokerage Charges
- 315
- Duty Charges
- C0020
- Cash Discount
- DI
- Discount
- FC
- Freight Charges
- PC
- Packaging Charge
- S0022
- Sleeving
- TX
- Special Tax
- ZZ
- Special Service Code
Code indicating method of handling for an allowance or charge.
- 02
- Off Invoice
- 06
- Charge to be Paid by Customer
Total dollar amount for the allowance or charge.
- If ITA07 is present with either ITA06 or ITA08, then ITA07 takes precedence.
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 one or more functional groups and interchange-related control segments
A count of the number of functional groups included in a transmission.
This number uniquely identifies the interchange data to the sender. It is assigned by the sender. Together with the sender ID it uniquely identifies the interchange data to the receiver. It is suggested that the sender, receiver, and all third parties be able to maintain an audit trail of interchanges using this number.
820 Sample
GS*RA*SENDERGS*RECEIVERGS*240314*194831*000000001*X*003040~
ST*820*000000021~
BPR*I*49266*C*ACH~
REF*SI*SHIPID000000001~
REF*IV*SHIPID000000001~
DTM*011*960208~
DTM*003*960210~
DTM*020*960212~
N1*VN**92*029AA~
ENT*999999~
ADX*50278*01*SI*SHIPID000000001~
IT1**25*PC*20111**PO*TS111111***BP*1234567890AAAAA~
RMR*SI*SHIPID000000001*ER*24266~
IT1**24*PC*10111**PO*TS111111***BP*1234567890AAAAA~
RMR*SI*SHIPID000000001*ER*23000~
IT1**23*PC*10000**PO*TS222222***BP*1234567890BBBBB~
ITA*A**C0020*02~
ITA*A**DI*02~
ITA*C**S0022*06~
ITA*C**PC*06***1000~
ITA*C**FC*06~
ITA*C**315*06***1000~
ITA*C**240*06~
ITA*C**ZZ*06~
ITA*C**TX*06~
SE*25*000000021~
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.