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
- None included
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
Code designating the action to be taken by all parties
- C
- Payment Accompanies Remittance Advice
- D
- Make Payment Only
- I
- Remittance Information Only
- P
- Prenotification of Future Transfers
Monetary amount
- BPR02 specifies the payment amount.
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)
Code identifying the payment format to be used
- 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)
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.
- 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.
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)
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.
- DA
- Demand Deposit
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).
Intended settlement date assigned by Sears.
For ACH payments, this is the date for all other credits: the date the originator (the payer) intends to provide good funds to the receiver (the payee), or the date for all other debits: the date the originator (the payee) intends to receive good funds from the receiver (the payer).
Trace
To uniquely identify a transaction to an application
- The TRN segment is used to uniquely identify a payment order/remittance advice.
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.
When N101 contains code PE, then N103 will contain code 92 and N104 will contain the Sears-assigned Remit-To vendor number for the receiver. N102 is not used.
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, property or an individual
- PE
- Payee
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
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.
When N101 contains code PR, then N102 will contain the literal 'SEARS HOLDINGS MANAGEMENT CORP.' and N103 and N104 are not used.
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, property or an individual
- PR
- Payer
Free-form name
Literal ‘SEARS HOLDINGS MANAGEMENT CORP.’
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
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.
Number assigned for differentiation within a transaction set
4 - 4 ENT sequence number
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).
This segment is used to further define the entities within the payer, e.g., location numbers (store numbers).
Code identifying an organizational entity, a physical location, property or an individual
- BY
- Buying Party (Purchaser)
Code qualifying the type of entity
- NM102 qualifies NM103.
- 2
- Non-Person Entity
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
Code identifying a party or other code
4 - 7 Sears-assigned unit number or account number.
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.
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.
- 01
- Pricing Error
- 06
- Quantity Contested
- 12
- Returns - Quality
- 16
- Non-Invoice Related Allowance/Charge
Code qualifying the Reference Identification
- ADX03 and ADX04 specify the identification of the adjustment.
- CL
- Seller's Credit Memo
- CM
- Buyer's Credit Memo
- DB
- Buyer's Debit Memo
- DL
- Seller's Debit Memo
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Reference number from an 812 transaction
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
- BT
- Batch Number
- DP
- Department Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
8 - 16 Batch Number
3 - 6 Department Number
Date/Time Reference
To specify pertinent dates and times
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.
This segment identifies specific remittance details for invoices that are being paid.
RMR04 will be signed if the amount is negative. If the value is negative, it has reduced the BPR payment amount. If the value is positive, it has increased the BPR payment amount.
If RMR01 contains code Value AA, the payment is for scan based trading (SBT) merchandise. RMR02 will contain SBT concatenated with the date from the 852 tha is being remitted.
Example: RMRAASBT20130513
Code qualifying the Reference Identification
- Parties using this segment should agree on the content of RMR01 and RMR02 prior to initiating communication.
- AA
- Accounts Receivable Statement Number
- IV
- Seller's Invoice Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
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.
Reference Identification
To specify identifying information
This segment contains ancillary reference numbers relating to the previous RMR segment.
The meter number will be referenced only on utility bill payments.
Code qualifying the Reference Identification
- BT
- Batch Number
- DP
- Department Number
- MG
- Meter Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
8 - 16 Batch number
3 - 6 Department number
1 - 30 Meter number
Date/Time Reference
To specify pertinent dates and times
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
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.