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
Data Elements BPR06, BPR07, BPR09, BPR12, BPR13, BPR15 are Mandatory when Transmitting Payment Order to a Banking Institution.
Example: BPRI1625.04CCHK
Code designating the action to be taken by all parties
- C
- Payment Accompanies Remittance Advice
- D
- Make Payment Only
- I
- Remittance Information Only
- X
- Handling Party's Option to Split Payment and Remittance
Code identifying the method for the movement of payment instructions
- ACH
- Automated Clearing House (ACH)
- CHK
- Check
- NON
- Non-Payment Data
- X12
- X12
- ZZZ
- $CDN EFT Payments
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)
$US Payments
- 04
- Canadian Bank Branch and Institution Number
$C Payments
Depository Financial Institution (DFI) identification number
Payer Bank Number (Transit).
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.
Payor Bank Account Number.
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)
$US Payments
- 04
- Canadian Bank Branch and Institution Number
$C Payments
Depository Financial Institution (DFI) identification number
CN Bank Number (Transit).
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.
CN Account Number.
Date expressed as CCYYMMDD
- BPR16 is the date the originating company intends for the transaction to be settled (i.e., Payment Effective Date).
Effective Payment Date.
Trace
To uniquely identify a transaction to an application
- The TRN segment is used to uniquely identify a payment order/remittance advice.
Example: TRN1PAYMENT REFERENCE NUMBER
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.
Transaction Trace Number.
Currency
To specify the currency (dollars, pounds, francs, etc.) used in a transaction
- The CUR segment does not initiate a foreign exchange transaction.
Example: CURPRCAD
Reference Identification
To specify identifying information
Example:
REFCK001970
REFEQCNRU123456
REFEQGATX123456
REFEQCN649332
Code qualifying the Reference Identification
For Non-Payment 820
- BM
- Bill of Lading Number
- CK
- Check Number
- EM
- Electronic Payment Reference Number
- EQ
- Equipment Number
- RR
- Payer's Financial Institution Transit Routing Number for Check, Draft or Wire Payments. Originating Depository Financial Institution Routing Number for ACH Transfers
- TN
- Transaction Reference Number
- WY
- Waybill Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Transaction Creation
To specify pertinent dates and times
Example: DTM09720180524
Code specifying type of date or time, or both date and time
- 097
- Transaction Creation
Code indicating the date format, time format, or date and time format
Shipped
To specify pertinent dates and times
Example: DTM01120180411
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.
Example: N1PRCOMPANY ABC
Code identifying an organizational entity, a physical location, property or an individual
- PR
- Payer
Free-form name
When N101 = PR Payor Name should be consistent in every 820 transmission from the customer to CN.
Code designating the system/method of code structure used for Identification Code (67)
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.
DUNS number.
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.
Example: N1PECANADIAN NATIONAL RAILWAY
Code identifying an organizational entity, a physical location, property or an individual
- PE
- Payee
Code designating the system/method of code structure used for Identification Code (67)
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.
DUNS number.
Additional Name Information
To specify additional names or those longer than 35 characters in length
Address Information
To specify the location of the named party
Example: N3*PO BOX 12345
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
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.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
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
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:
RMRIV12345678509.24509.240
RMRIV12345679614.8614.80
RMRIV12345680*501501*0
Code qualifying the Reference Identification
- Parties using this segment should agree on the content of RMR01 and RMR02 prior to initiating communication.
- BM
- Bill of Lading Number
- CM
- Buyer's Credit Memo
- CN
- Carrier's Reference Number (PRO/Invoice)
CN Invoice Number
- EQ
- Equipment Number
- FR
- Freight Bill Number
CN Invoice Number
- IV
- Seller's Invoice Number
CN Invoice Number
- OI
- Original Invoice Number
CN Invoice Number
- WY
- Waybill Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Can use CN Credit Note Number in this field.
Monetary amount
- RMR04 is the amount paid.
Credit amounts must be negative unless CM qualifier used.
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.
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
ACH CTX
BPR*C*12674.24*C*ACH*CTX*01*111111**PAYOR BANK ACCOUNT NUMBER***01*222222*DA*CN ACCOUNT NUMBER*20060527
TRN*1*PAYMENT REFERENCE NUMBER
CUR*PR*USD
REF*RR*0002200605260652249300024
N1*PR*COMPANY ABC
N1*PE*CANADIAN NATIONAL RAILWAY
ENT*1
RMR*IV*012345681**1938.13*1938.13
DTM*003*20180516
ENT*2
RMR*IV*012345682**1938.13*1938.13
DTM*003*20180516
ENT*3
RMR*IV*012345683**2932.66*2932.66
DTM*003*20180517
ENT*4
RMR*IV*012345684**2932.66*2932.66
DTM*003*20180519
ENT*5
RMR*IV*012345685**2932.66*2932.66
DTM*003*20060522
SE*23*000000044
Cheque with Separate Payment Details
BPR*I*1625.04*C*CHK
TRN*1*PAYMENT REFERENCE NUMBER
CUR*PR*CAD
REF*CK*001970
DTM*097*20180524
N1*PE*CANADIAN NATIONAL RAILWAY
N1*PR*COMPANY ABC
N3*PO BOX 12345
ENT*1
RMR*IV*12345678**509.24*509.24*0
REF*EQ*CNRU123456
DTM*011*20180411
ENT*1
RMR*IV*12345679**614.8*614.8*0
REF*EQ*GATX123456
DTM*011*20180410
ENT*1
RMR*IV*12345680**501*501*0
REF*EQ*CN649332
DTM*011*20180328
SE*22*0372
Payment Only
BPR*D*123701.52*C*X12**04*111111**PAYOR BANK ACCOUNT NUMBER***04*222222*DA*CN ACCOUNT NUMBER*20060523
TRN*1*PAYMENT REFERENCE NUMBER
REF*RR*12345678901253
N1*PR*COMPANY ABC
N1*PE*CANADIAN NATIONAL RAILWAYS
N2*FINANCE DEPT.
N3*PO BOX 8100
N4*MONTREAL*QC
SE*10*000000007
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.