X12 820 Payment Order/Remittance Advice [4060]
This X12 Transaction Set 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
- ^ Repetition
- None included
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code identifying 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 identifying 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)
Code indicating 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
Code indicating 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
Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator
- ^
- Repetition Separator
Code specifying the version number of the interchange control segments
- 00406
- Standards Approved for Publication by ASC X12 Procedures Review Board through October 2002
A control number assigned by the interchange sender
Code indicating sender's request for an interchange acknowledgment
- 0
- No Interchange Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested (TA1)
Code indicating 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
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
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 identifying the issuer of the standard; this code is used in conjunction with Data Element 480
- 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
- 004060
- Standards Approved for Publication by ASC X12 Procedures Review Board through October 2002
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) is 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
Monetary amount
- BPR02 specifies the payment amount.
Total currency amount of all items being paid must total RMR04s
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)
- CHK
- Check
- FEW
- Federal Reserve Funds/Wire Transfer - Repetitive
- FWT
- Federal Reserve Funds/Wire Transfer - Nonrepetitive
Code identifying the payment format to be used
For ACH payments only, not used by FedEx
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).
For ACH payments only, not used by FedEx
Depository Financial Institution (DFI) identification number
For ACH payments only, not used by FedEx
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.
For ACH payments only, not used by FedEx
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
- BPR10 shall be mutually established between the originating depository financial institution (ODFI) and the company originating the payment.
Last 10 digits of ISA06
A code defined between the originating company and the originating depository financial institution (ODFI) that uniquely identifies the company initiating the transfer instructions
Not used by FedEx
Code identifying the type of identification number of Depository Financial Institution (DFI)
- BPR12 and BPR13 relate to the receiving depository financial institution (RDFI).
For ACH payments only; not used by FedEx
Depository Financial Institution (DFI) identification number
For ACH payments only; not used by FedEx
Account number assigned
- BPR15 is the account number of the receiving company to be debited or credited with the payment order.
For ACH payments only; not used by FedEx
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
- BPR16 is the date the originating company intends for the transaction to be settled (i.e., Payment Effective Date).
Provide settlement date if paying via EFT
Currency
To specify the currency (dollars, pounds, francs, etc.) used in a transaction
- The CUR segment does not initiate a foreign exchange transaction.
Code identifying an organizational entity, a physical location, property or an individual
- RM
- Party that remits payment
Code (Standard ISO) for country in whose currency the charges are specified
- USD
- US Dollar
Reference Information
To specify identifying information
Code qualifying the Reference Identification
- 14
- Master Account Number
Customer FedEx Master Account Number
- CK
- Check Number
Check # or Reference # (8 characters max
– must be unique) Required for FedEx processing - TN
- Transaction Reference Number
Check # or Reference # (8 characters max
– must be unique) Required for FedEx processing
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Date/Time Reference
To specify pertinent dates and times
Code specifying type of date or time, or both date and time
- 097
- Transaction Creation
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
Transaction Creation Date (CCYYMMDD)
Party Identification
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
Code designating the system/method of code structure used for Identification Code (67)
- ZZ
- Mutually Defined
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.
Customer FedEx Account Number
- The account number is the account number of the company billed for the FedEx service. N1 segment is limited to one occurrence.
- N1 is required if paying only one billed account per ST / SE loop.
- If multiple bill-to accounts are being paid, do not use N1 – use the NM1 segment instead. N1 or NM1 must be used. Do not use both.
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.
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).
Code identifying an organizational entity, a physical location, property or an individual
- AO
- Account Of
Code qualifying the type of entity
- NM102 qualifies NM103.
- 3
- Unknown
Individual last name or organizational name
Code designating the system/method of code structure used for Identification Code (67)
- ZZ
- Mutually Defined
Code identifying a party or other code
Customer FedEx Account Number
- N1 is required if paying only one billed account per ST / SE loop.
- If multiple bill-to accounts are being paid, do not use N1 – use the NM1 segment instead. N1 or NM1 must be used. Do not use both
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.
Code qualifying the Reference Identification
- Parties using this segment should agree on the content of RMR01 and RMR02 prior to initiating communication.
- AW
- Tracking Number
Tracking Number
- BM
- Invoice Number
- CN
- Tracking Number
- FR
- Tracking Number
- IV
- Invoice Number
- OI
- Invoice Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
NOTE: If RMR01 = ‘AW’, ‘CN’ or ‘FR’, the RMR02 is the Tracking Number that is found in the 110 Transaction Set, N902 segment, following the N901 ‘AW’ qualifier. The ‘2I’ Ground Tracking Number found in the N902 segment is for informational purposes only and should not be used in the RMR02 segment when remitting to FedEx.
Monetary amount
- RMR04 is the amount paid.
Payment Amount (MUST BE POSITIVE)
NOTE: If paying by tracking number put tracking number in this segment and put invoice information in the REF segment. Tracking number level payments are required if adjustments are requested. Repeat this segment for multiple invoices and tracking numbers.
Reference Information
To specify identifying information
Code qualifying the Reference Identification
- BM
- Invoice Number
- IV
- Invoice Number
Invoice Number
- OI
- Invoice Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
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).
Adjustment requests for service failure or no proof of delivery must be submitted through the invoice adjustment feature on fedex.com or the telephone invoice adjustment system at 800-622-1147.
For Incorrect Pricing, Discount, Dimensions, Weight, or Miscellaneous invoice adjustment support please contact your FedEx Sales Executive as these reasons cannot be submitted via EDI.
Code ‘H2’ is to be used for ‘Payment Previously Sent’ disputes only. Do not use code ‘H2’ to dispute items in process, duplicate billing, partial balances or any other adjustment reason codes.
Duty/tax disputes (air express shipments only) must be submitted in Email to dutytaxdisputes@fedex.com
No adjustment requests for Retail Sales purchases (packaging supplies) should be included. Call (800) 622-1147 for inquiries.
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.
NOTE: Adjustment requests for service failure or no proof of delivery must be submitted through the invoice adjustment feature on fedex.com or the telephone invoice adjustment system at 800-622-1147.
NOTE: Refer to the ‘ELECTRONIC INVOICE ADJUSTMENTS HELPFUL TIPS’ section following this page for more information on submitting invoice adjustment requests.
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.
NOTE: *Code ‘H2’ is to be used for ‘Payment Previously Sent’ disputes only. Do not use code ‘H2’ to dispute items in process, duplicate billing,
partial balances or any other adjustment reason codes.
NOTE: Duty/tax disputes (air express shipments only) must be submitted in writing.
NOTE: No adjustment requests for Retail Sales purchases (packaging supplies billed via paper invoice) should be included. Call (800) 622-
1147 for inquiries.
- 18
- Not Company Bill
- 19
- Duplicate Billing
- 21
- Rebill Other Account (Account Number Required)
- 30
- Saturday Delivery Surcharge Invalid
- 34
- Declared Value Incorrect
- 38
- Service Incorrect
- 40
- Address Correction Surcharge Invalid
- 51
- Delivery Area Surcharges (DAS) Applied in Error
- 53
- Pickup Fees or Weekly On-Call Fees - Not Requested
- 60
- Late Fee Applied in Error
- H2
- Payment Previously Sent
- PD
- Balance Due Requested (an inquiry, not a dispute)
Code qualifying the Reference Identification
- ADX03 and ADX04 specify the identification of the adjustment.
- AW
- Tracking Number
- FR
- Freight Bill Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Tracking Number
NOTE: If you use code ‘21’, ‘34’, ‘38’, ‘H2’ an NTE02 is required.
Note/Special Instruction
To transmit information in a free-form format, if necessary, for comment or special instruction
A free-form description to clarify the related data elements and their content
If ADX02 =
21: Provide FedEx account number to be rebilled.
34: Provide correct declared value per your records.
38: Provide correct service per your records (i.e. 2nd day vs. Priority).
H2: Provide original check number and date (i.e. ABC12345..MMDDYYYY).
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.