TForce Freight
/
Payment Order/Remittance Advice
  • Specification
  • EDI Inspector
Import guide into your account
Stedi maintains this guide based on public documentation from TForce Freight. Contact TForce Freight for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
TForce Freight logo

X12 820 Payment Order/Remittance Advice

X12 Release 4010

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.

---

Use this mapping layout if the Remittance is sent to the bank along with EFT payment.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI sample
  • sample
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/t-force-freight/payment-orderremittance-advice/01GYCWQ9G98KEZ4Q4X22HB5RE3
Powered by
Build EDI implementation guides at stedi.com
Overview
ISA
-
Interchange Control Header
Max use 1
Required
GS
-
Functional Group Header
Max use 1
Required
heading
ST
010
Transaction Set Header
Max use 1
Required
BPR
020
Beginning Segment for Payment Order/Remittance Advice
Max use 1
Required
REF
050
Reference Identification
Max use 1
Optional
DTM
060
Date/Time Reference
Max use 1
Optional
N1 Loop
GE
-
Functional Group Trailer
Max use 1
Required
IEA
-
Interchange Control Trailer
Max use 1
Required
ISA

Interchange Control Header

RequiredMax use 1

To start and identify an interchange of zero or more functional groups and interchange-related control segments

Example
ISA-01
I01
Authorization Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Authorization Information

00
No Authorization Information Present (No Meaningful Information in I02)
ISA-02
I02
Authorization Information
Required
String (AN)
Min 10Max 10

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)

ISA-03
I03
Security Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Security Information

00
No Security Information Present (No Meaningful Information in I04)
ISA-04
I04
Security Information
Required
String (AN)
Min 10Max 10

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)

ISA-05
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-06
I06
Interchange Sender ID
Required
String (AN)
Min 15Max 15

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

ISA-07
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-08
I07
Interchange Receiver ID
Required
String (AN)
Min 15Max 15

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

ISA-09
I08
Interchange Date
Required
Date (DT)
YYMMDD format

Date of the interchange

ISA-10
I09
Interchange Time
Required
Time (TM)
HHMM format

Time of the interchange

ISA-11
I10
Interchange Control Standards Identifier
Required
Identifier (ID)

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
ISA-12
I11
Interchange Control Version Number
Required
Identifier (ID)

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
ISA-13
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

ISA-14
I13
Acknowledgment Requested
Required
Identifier (ID)
Min 1Max 1

Code sent by the sender to request an interchange acknowledgment (TA1)

0
No Acknowledgment Requested
1
Interchange Acknowledgment Requested
ISA-15
I14
Usage Indicator
Required
Identifier (ID)
Min 1Max 1

Code to indicate whether data enclosed by this interchange envelope is test, production or information

I
Information
P
Production Data
T
Test Data
ISA-16
I15
Component Element Separator
Required
String (AN)
Min 1Max 1

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

RequiredMax use 1

To indicate the beginning of a functional group and to provide control information

Example
GS-01
479
Functional Identifier Code
Required
Identifier (ID)

Code identifying a group of application related transaction sets

RA
Payment Order/Remittance Advice (820)
GS-02
142
Application Sender's Code
Required
String (AN)
Min 2Max 15

Code identifying party sending transmission; codes agreed to by trading partners

GS-03
124
Application Receiver's Code
Required
String (AN)
Min 2Max 15

Code identifying party receiving transmission. Codes agreed to by trading partners

GS-04
373
Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

GS-05
337
Time
Required
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

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)

GS-06
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

GS-07
455
Responsible Agency Code
Required
Identifier (ID)
Min 1Max 2

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
GS-08
480
Version / Release / Industry Identifier Code
Required
String (AN)

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

ST
010
Heading > ST

Transaction Set Header

RequiredMax use 1

To indicate the start of a transaction set and to assign a control number

Example
ST-01
143
Transaction Set Identifier Code
Required
Identifier (ID)

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
ST-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

BPR
020
Heading > BPR

Beginning Segment for Payment Order/Remittance Advice

RequiredMax use 1

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
BPR-01
305
Transaction Handling Code
Required
Identifier (ID)

Code designating the action to be taken by all parties

C
Payment Accompanies Remittance Advice
BPR-02
782
Monetary Amount
Required
Decimal number (R)
Min 1Max 15

Monetary amount

  • BPR02 specifies the payment amount.
BPR-03
478
Credit/Debit Flag Code
Required
Identifier (ID)

Code indicating whether amount is a credit or debit

C
Credit
BPR-04
591
Payment Method Code
Required
Identifier (ID)

Code identifying the method for the movement of payment instructions

ACH
Automated Clearing House (ACH)
BPR-07
507
(DFI) Identification Number
Optional
String (AN)
Min 3Max 12

Depository Financial Institution (DFI) identification number

Usage notes

Originating Financial Institute

BPR-09
508
Account Number
Required
String (AN)
Min 1Max 35

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.
Usage notes

Bank Acct

REF
050
Heading > REF

Reference Identification

OptionalMax use >1

To specify identifying information

Example
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

EF
Electronic Funds Transfer ID Number
REF-02
127
Reference Identification
Optional
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Usage notes

Reference to Disbursement or Accts Payable System

DTM
060
Heading > DTM

Date/Time Reference

OptionalMax use >1

To specify pertinent dates and times

Example
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

Code specifying type of date or time, or both date and time

003
Invoice
DTM-02
373
Date
Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

Usage notes

Invoice Creation Date

N1 Loop
OptionalMax >1
N1
070
Heading > N1 Loop > N1

Name

RequiredMax use 1

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
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

PR
Payer
N1-02
93
Name
Optional
String (AN)
Min 1Max 60

Free-form name

N3
090
Heading > N1 Loop > N3

Address Information

OptionalMax use >1

To specify the location of the named party

Example
N3-01
166
Address Information
Required
String (AN)
Min 1Max 55

Address information

N4
100
Heading > N1 Loop > N4

Geographic Location

OptionalMax use 1

To specify the geographic place of the named party

Example
N4-01
19
City Name
Optional
String (AN)
Min 2Max 30

Free-form text for city name

  • A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
N4-02
156
State or Province Code
Optional
Identifier (ID)
Min 2Max 2

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.
N4-03
116
Postal Code
Optional
Identifier (ID)
Min 3Max 15

Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

N1 Loop end
Heading end

Detail

ENT Loop
OptionalMax >1
ENT
010
Detail > ENT Loop > ENT

Entity

RequiredMax use 1

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-01
554
Assigned Number
Optional
Numeric (N0)
Min 1Max 6

Number assigned for differentiation within a transaction set

RMR Loop
OptionalMax >1
RMR
150
Detail > ENT Loop > RMR Loop > RMR

Remittance Advice Accounts Receivable Open Item Reference

RequiredMax use 1

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
If either Reference Identification Qualifier (RMR-01) or Reference Identification (RMR-02) is present, then the other is required
RMR-01
128
Reference Identification Qualifier
Optional
Identifier (ID)

Code qualifying the Reference Identification

  • Parties using this segment should agree on the content of RMR01 and RMR02 prior to initiating communication.
Usage notes

Prefer to receive only the Pro #

BM
Bill of Lading Number
CN
Carrier's Reference Number (PRO/Invoice)
RMR-02
127
Reference Identification
Optional
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

RMR-04
782
Monetary Amount
Required
Decimal number (R)
Min 1Max 15

Monetary amount

  • RMR04 is the amount paid.
ADX Loop
OptionalMax >1
ADX
210
Detail > ENT Loop > RMR Loop > ADX Loop > ADX

Adjustment

RequiredMax use 1

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).
Example
If either Reference Identification Qualifier (ADX-03) or Reference Identification (ADX-04) is present, then the other is required
ADX-01
782
Monetary Amount
Required
Decimal number (R)
Min 1Max 15

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.
ADX-02
426
Adjustment Reason Code
Required
Identifier (ID)

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
03
Extension Error
09
Terms of Sale Error
19
Duplicate Billing
21
Shipment Method of Payment Incorrect
39
Shipper/Consignee Ref. Number Missing
ADX-03
128
Reference Identification Qualifier
Optional
Identifier (ID)

Code qualifying the Reference Identification

  • ADX03 and ADX04 specify the identification of the adjustment.
CN
Carrier's Reference Number (PRO/Invoice)
ADX-04
127
Reference Identification
Optional
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

ADX Loop end
RMR Loop end
ENT Loop end
Detail end

Summary

SE
010
Summary > SE

Transaction Set Trailer

RequiredMax use 1

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Example
SE-01
96
Number of Included Segments
Required
Numeric (N0)
Min 1Max 10

Total number of segments included in a transaction set including ST and SE segments

SE-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

Summary end

Functional Group Trailer

RequiredMax use 1

To indicate the end of a functional group and to provide control information

Example
GE-01
97
Number of Transaction Sets Included
Required
Numeric (N0)
Min 1Max 6

Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

GE-02
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

Interchange Control Trailer

RequiredMax use 1

To define the end of an interchange of zero or more functional groups and interchange-related control segments

Example
IEA-01
I16
Number of Included Functional Groups
Required
Numeric (N0)
Min 1Max 5

A count of the number of functional groups included in an interchange

IEA-02
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

EDI Samples

sample

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *231101*0208*U*00401*000000001*0*T*>
GS*RA*SENDERGS*RECEIVERGS*20231101*020841*000000001*X*004010
ST*820*0001
BPR*C*197.68*C*ACH***101035485**005467845
REF*EF*1001
DTM*003*20001025
N1*PR*XYZ CORPORATION
N3*1000 MAIN STREET
N4*RICHMOND*VA*23223
ENT*1
RMR*CN*103432291**48.64
RMR*CN*107565894**92.25
RMR*CN*107565905**56.79
ADX*5.28*01*CN*103432291
SE*13*0001
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.