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
- I
- Remittance Information Only
Code identifying the method for the movement of payment instructions
- ACH
- Automated Clearing House (ACH)
- CHK
- Check
Date expressed as CCYYMMDD
- BPR16 is the date the originating company intends for the transaction to be settled (i.e., Payment Effective Date).
ACH Settlement Date (only send if BPR04=ACH).
Currency
To specify the currency (dollars, pounds, francs, etc.) used in a transaction
- The CUR segment does not initiate a foreign exchange transaction.
Code qualifying the Reference Identification
- CK
- Check Number
- TN
- Transaction Reference Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
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.
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
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.
The Tracking Number can be found in the 210 transaction in the "B302" element.
Code qualifying the Reference Identification
- Parties using this segment should agree on the content of RMR01 and RMR02 prior to initiating communication.
- CN
- Carrier's Reference Number (PRO/Invoice)
- FR
- Freight Bill Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Tracking Number or PRO
Monetary amount
- RMR04 is the amount paid.
This is the payment amount.
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.
This is the invoice amount
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).
Must be submitted for an adjustment.
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.
For Incorrect Pricing or Discount, please contact your FedEx Sales Executive; these reasons are not disputable by EDI.
- 01
- Pricing Error
Shipment was billed using incorrect rates. General pricing error to be researched.
- 17
- Required Data Missing
Use to indicate a specific reference could be missing, such as a GL code, etc. For missing BOL or PO numbers please use code 39.
- 18
- Not Company Bill
Billed to incorrect party, will be rebilled to the Shipper.
- 19
- Duplicate Billing
Shipment was billed twice for the same charges.
- 21
- Shipment Method of Payment Incorrect
Used to indicate the shipment method of payment was incorrect. Specify the account to be billed and/or what the method of Payment should be: i.e. Prepaid, Collect, Third Party.
- 22
- Weight Error
Used to indicate Weight Error on the shipment.
- 24
- Incorrect Discount
Shipment was billed using the incorrect discount based on the customer's contract.
- 30
- Delivery Charge Incorrect
Saturday delivery or Pick up surcharge invalid.
- 34
- Declared Value Incorrect
Tracking number was billed using the incorrect declared value. The corrected declared value per customer records will need to be supplied.
- 35
- Commodity Code Incorrect
Used to request an adjustment due to freight classification.
- 37
- Dimensions Incorrect
Used to indicate incorrect service was used. The customer would provide the service expected to be billed.
- 38
- Service Incorrect
Used to indicate incorrect service was used. The customer would provide the service expected to be billed.
- 39
- Shipper/Consignee Ref. Number Missing
Used to indicate a shipper/consignee BOL or PO number is missing.
- 44
- Required Documents Missing
Used to request missing documentation such as Re-Weigh documents. The customer would provide what document is missing.
- 46
- Transportation Charge Incorrect
Used to indicate a pricing error for the transportation or Line Haul charges.
- 51
- Interest Penalty Charge
Code should only be used when Delivery Area Surcharges have been applied in error.
- 52
- Credit for Previous Overpayment
Code should only be used when Delivery Area Surcharges have been calculated incorrectly.
- H2
- Payment Previously Sent
Code should only be used to inform FedEx that payment has been previously sent. Check number, check dater and reference number of previous payment will need to be sent.
- L7
- Miscellaneous Deductions
Used for miscellaneous adjustment requests that does not fit into categories for any other code. Customer will need to supply detail in a comment.
Note/Special Instruction
To transmit information in a free-form format, if necessary, for comment or special instruction
If ADX02 one of the following codes, the NTE02 is required.
21: Provide FedEx account number to be rebilled.
22: Provide correct weight per your records.
34: Provide correct declared value per your records.
37: Provide correct dimensions per your records (i.e. "11x15x35").
38: Provide correct service per your records (i.e. 2nd day vs. Priority).
A free-form description to clarify the related data elements and their content
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.