X12 820 Retail 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
BPRI2567.89CACH
Code designating the action to be taken by all parties
- I
- Remittance Information Only
Monetary amount
- BPR02 specifies the payment amount.
When the amount ends without cents (25.00), the .00 will not be sent. It would be sent as 25.
Code identifying the method for the movement of payment instructions
- ACH
- Automated Clearing House (ACH)
Code identifying the payment format to be used
- CCD
- Cash Concentration/Disbursement (CCD) (ACH)
Trace
To uniquely identify a transaction to an application
- The TRN segment is used to uniquely identify a payment order/remittance advice.
TRN11234567890
Code identifying which transaction is being referenced
- 1
- Current Transaction Trace Numbers
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- TRN02 provides unique identification for the transaction.
Tracer Number.
Reference Identification
To specify identifying information
REFCK1234
Code qualifying the Reference Identification
- CK
- Check Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Check Number
Date/Time Reference
To specify pertinent dates and times
DTM23420020215
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.
N1PEVendor Name
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.
N1PRTarget Corporation Operating Company Name
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.
Only one ENT segment will be sent per 820
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.
ADX*-143.33ZZAMCB-1234567 Chargeback
ADX25ZZCM*AB9843092 Credit Memo
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.
When the amount ends without cents (25.00), the .00 will not be sent. It would be sent as 25.
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.
- AM
- Adjustment Memo (Charge Back)
- CM
- Buyer's Credit Memo
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Chargeback Number or Credit memo number.
Note/Special Instruction
To transmit information in a free-form format, if necessary, for comment or special instruction
NTECARNOTE ABOUT THE CHARGEBACK OR CREDIT MEMO
Reference Identification
To specify identifying information
REF*ZZ**A032 CHARGEBACK . (Chargeback example - invoice paid in a previous transmission)
REF*ZZ**A048 CREDIT MEMO (Credit Memo example - invoice paid in a previous transmission)
Code qualifying the Reference Identification
- ZZ
- Mutually Defined
A free-form description to clarify the related data elements and their content
This field will contain the Lawson adjustment reason code and description.
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.
RMRIV987654321PI1550.001600.0050.00
RMR04 will be the net of adjustments and chargebacks.
(RMR04 = RMR05 - RMR06 + ADX01)
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
Invoice Number
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.
- PI
- Pay Item
Monetary amount
- RMR04 is the amount paid.
Net Amount
When the amount ends without cents (25.00), the .00 will not be sent. It would be sent as 25.
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.
Gross Amount
When the amount ends without cents (25.00), the .00 will not be sent. It would be sent as 25.
Monetary amount
- RMR06 is the amount of discount taken.
Discount Amount
When the amount ends without cents (25.00), the .00 will not be sent. It would be sent as 25.
Note/Special Instruction
To transmit information in a free-form format, if necessary, for comment or special instruction
NTECARNOTE REGARDING THE INVOICE
Reference Identification
To specify identifying information
NOTE: Starting in Dec 2017, Target will start phasing in a new PO format. The new format removes the 4 digit department number prefix and the purchase order number will be moving from 7 digits to 11 digits. No changes are being made to the location number. During this transition, your company needs to be able to receive both PO formats, as both may be received during transition. The same PO format received from Target will need to be returned on all EDI related documents for that PO to ensure no business interruption.
New Purchase Order Number Format:
12345678901-1234
Sample REF Segment
REFPO1234567
REFPO12345678901-1234
Code qualifying the Reference Identification
- PO
- Purchase Order Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
PO Number
Date/Time Reference
To specify pertinent dates and times
DTM00320010905
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).
ADX*-20.30ZZAM*CB-234567
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.
When the amount ends without cents (25.00), the .00 will not be sent. It would be sent as 25.
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.
- AM
- Adjustment Memo (Charge Back)
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Chargeback Number
Note/Special Instruction
To transmit information in a free-form format, if necessary, for comment or special instruction
NTECARNOTE ABOUT THE CHARGEBACK
Reference Identification
To specify identifying information
REFIV1234567*A032 CHARGEBACK - DEFECTIVE
Code qualifying the Reference Identification
- IV
- Seller's Invoice Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Invoice Number
A free-form description to clarify the related data elements and their content
Lawson adjustment reason code and description
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 820
GS*RA*SENDERGS*RECEIVERGS*20231006*021009*000000001*X*004010
ST*820*0001
BPR*I*2567.89*C*ACH
TRN*1*1234567890
REF*CK*1234
DTM*234*20020215
N1*PE*Vendor Name
N1*PR*Target Corporation Operating Company Name
ENT*1
ADX*-143.33*ZZ*AM*CB-1234567
NTE*CAR*NOTE ABOUT THE CHARGEBACK OR CREDIT MEMO
REF*ZZ**A032 CHARGEBACK
RMR*IV*987654321*PI*1550.00*1600.00*50.00
NTE*CAR*NOTE REGARDING THE INVOICE
REF*PO*12345678901-1234
DTM*003*20010905
ADX*-20.30*ZZ*AM*CB-234567
NTE*CAR*NOTE ABOUT THE CHARGEBACK
REF*IV*1234567*A032 CHARGEBACK - DEFECTIVE
SE*19*0001
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.