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 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
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
Example:
BPRI700.00CACHCCP**041111111DA2222222333333333304444444444DA55555555519980702
or
BPRI700.00CACHCCD**01111111111DA2222222223333333333014444444444DA5555555551998
0702\
Code designating the action to be taken by all parties
If vendor receives 820 directly from Lowe's the BPR01 will always contain an I.
- C
- Payment Accompanies Remittance Advice
- D
- Make Payment Only
- I
- Remittance Information Only
Monetary amount
- BPR02 specifies the payment amount.
Total amount of remittance.
Code indicating whether amount is a credit or debit
- C
- Credit
Code identifying the method for the movement of payment instructions
- ACH
- Automated Clearing House (ACH)
- DXC
- ACH Demand Corporate Trade Exchange (CTX) Credit
Code identifying the payment format to be used
Will be used for US Payments Only.
- CCD
- Cash Concentration/Disbursement (CCD) (ACH)
- CCP
- Cash Concentration/Disbursement plus Addenda (CCD+) (ACH)
- CTX
- Corporate Trade Exchange (CTX) (ACH)
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)
- 04
- Canadian Bank Branch and Institution Number
Depository Financial Institution (DFI) identification number
Originating Bank ABA Transit/Routing Number.
Code indicating the type of account
- BPR08 is a code identifying the type of bank account or other financial asset.
- DA
- Demand Deposit
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.
Sending account number.
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
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)
- 04
- Canadian Bank Branch and Institution Number
Depository Financial Institution (DFI) identification number
Receiving bank ABA Routing/Transit ID.
Code indicating the type of account
- BPR14 is a code identifying the type of bank account or other financial asset.
- DA
- Demand Deposit
Account number assigned
- BPR15 is the account number of the receiving company to be debited or credited with the payment order.
Payee's account number.
Trace
To uniquely identify a transaction to an application
- The TRN segment is used to uniquely identify a payment order/remittance advice.
TRN10000201
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.
Trace Number - Will be the same as the Lowe's Check Number.
Currency
To specify the currency (dollars, pounds, francs, etc.) used in a transaction
- The CUR segment does not initiate a foreign exchange transaction.
The currency code used is the three letter ISO 4217 international standard code (USD/CAD).
Example:
CURPRUSD\
Code identifying an organizational entity, a physical location, property or an individual
- PR
- Payer
Reference Identification
To specify identifying information
Example:
REFCK0000201\
Code qualifying the Reference Identification
- CK
- Check Number
Date/Time Reference
To specify pertinent dates and times
Example:
DTM09719980702\
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.
N1PEABC COMPANY
N1PRLOWE'S
N1RBEI TEST BANK
N1RI**9312345\
Code identifying an organizational entity, a physical location, property or an individual
- PE
- Payee
- PR
- Payer
- RB
- Receiving Bank
- RI
- Remit To
Free-form name
Name of entity type identified in N101.
Code designating the system/method of code structure used for Identification Code (67)
- 93
- Code assigned by the organization originating the transaction set
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.
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\
Individual or Organizational Name
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:
NM1AO2*ABC COMPANY\
Code identifying an organizational entity, a physical location, property or an individual
- AO
- Account Of
Code qualifying the type of entity
- NM102 qualifies NM103.
- 2
- Non-Person Entity
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.
Example:
RMRIV1932017*450451*1\
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
Your invoice number or Lowe's debit memo number if debit is issued (DM12345). Lowe's Payables system can only handle a 10 digit invoice number. If you send more than 10 digits the invoice number will be truncated.
Monetary amount
- RMR04 is the amount paid.
Net amount being remitted for this invoice.
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.
Total amount of invoice before any applicable discounts.
Note/Special Instruction
To transmit information in a free-form format, if necessary, for comment or special instruction
Example:
NTEZZZDESCRIPTION ADJUSTMENTS TO INVOICE
Code identifying the functional area or purpose for which the note applies
- ZZZ
- Mutually Defined
Reference Identification
To specify identifying information
Example:
REFPO74949
REFVVD33097\
Code qualifying the Reference Identification
- PO
- Purchase Order Number
- VV
- Voucher
Date/Time Reference
To specify pertinent dates and times
Example:
DTM00319980602\
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
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
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
sample
GS*RA*SENDERGS*RECEIVERGS*20231101*012237*000000001*X*004010
ST*820*2275
BPR*I*700.00*C*ACH*CCP*04*1111111*DA*2222222*3333333333**04*444444444*DA*555555555*19980702
TRN*1*0000201
CUR*PR*USD
REF*CK*0000201
DTM*097*19980702
N1*PE*ABC COMPANY
N1*PR*LOWE'S
N1*RB*EI TEST BANK
N1*RI**93*12345
ENT*1
NM1*AO*2*ABC COMPANY
RMR*IV*1932017**450*451*1
NTE*ZZZ*DESCRIPTION ADJUSTMENTS TO INVOICE
REF*PO*74949
REF*VV*D33097
DTM*003*19980602
SE*18*2275
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.