Toyota Motor Sales
/
Remittance Advice
  • Specification
  • EDI Inspector
Stedi maintains this guide based on public documentation from Toyota Motor Sales. Contact Toyota Motor Sales for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Toyota Motor Sales logo

X12 820 Remittance Advice

X12 Release 3040

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.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI sample
  • 820 Sample
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/toyota-motor-sales/remittance-advice/01HQ1C3MR07EQWPFE4VG3ZEWAE
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 Numbers
Max use 1
Required
DTM
060
Date/Time Reference
Max use 1
Required
N1 Loop
detail
ENT Loop
ENT
010
Entity
Max use 1
Required
ADX 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 one 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 sender or the data in the interchange. The type of information is set by the Authorization Information Qualifier.

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 sender or the data in the interchange. The type of information is set by the Security Information Qualifier.

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 number 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.

00304
Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1993
ISA-13
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

This number uniquely identifies the interchange data to the sender. It is assigned by the sender. Together with the sender ID it uniquely identifies the interchange data to the receiver. It is suggested that the sender, receiver, and all third parties be able to maintain an audit trail of interchanges using this number.

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

Code sent by the sender to request an interchange acknowledgment.

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

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

P
Production Data
T
Test Data
ISA-16
I15
Subelement Separator
Required
String (AN)
Min 1Max 1

This is a field reserved for future expansion in separating data element subgroups. (In the interest of a migration to international standards, this must be different from the data element separator).

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

Required
Date (DT)
YYMMDD format

Date (YYMMDD).

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.

003040
Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1993

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
X12.4 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

(1) To indicate the beginning of a PaymentOrder/Remittance Advice Transaction Set and total payment amount or (2) 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.

I
Remittance Information Only
BPR-02
782
Monetary Amount
Required
Decimal number (R)
Min 1Max 15

Monetary amount.

  • BPR02 specifies the payment amount.
Usage notes

The total amount that TMS will pay. 2 decimals implied.

BPR-03
478
Credit/Debit Flag Code
Required
Identifier (ID)

Code indicating whether amount is a credit or debit

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

Code identifying the method for the movement of payment instructions

ACH
Automated Clearing House (ACH)
CHK
Check
REF
050
Heading > REF

Reference Numbers

RequiredMax use >1

To specify identifying numbers.

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

Code qualifying the Reference Number.

IV
Invoice Number
SI
Shipper's Identifying Number for Shipment (SID)
REF-02
127
Reference Number
Required
String (AN)
Min 1Max 30

Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.

DTM
060
Heading > DTM

Date/Time Reference

RequiredMax 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 Date
011
Shipped Date
020
Check Date
Required
Date (DT)
YYMMDD format

Date (YYMMDD).

N1 Loop
RequiredMax >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, or an individual

VN
Vendor Code
N1-03
66
Identification Code Qualifier
Required
Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67).

92
Assigned Buyer
N1-04
67
Identification Code
Required
String (AN)
Min 2Max 17

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

TMS assigned vendor code.

N1 Loop end
Heading end

Detail

ENT Loop
RequiredMax >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

  • ENT09 may contain the payee's accounts receivable customer number.
Example
ENT-01
554
Assigned Number
Required
Numeric (N0)
Min 1Max 6

Number assigned for differentiation within a transaction set.

Usage notes

Assigned number. TMS uses a constant “999999”.

ADX Loop
OptionalMax >1
Usage notes

This loop is optional and will occur only in case of a price adjustment.

ADX
080
Detail > ENT 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 contains adjustment items which are not netted to an RMR segment in this transaction set.
Example
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.
Usage notes

Monetary amount. Extended invoice price. 2 decimals implied.

ADX-02
426
Adjustment Reason Code
Required
Identifier (ID)
Min 2Max 2

Code indicating reason for credit memo, or adjustment to invoice, credit memo, or payment.

  • ADX02 specifies the reason for claiming the adjustment.
ADX-03
128
Reference Number Qualifier
Required
Identifier (ID)

Code qualifying the Reference Number.

  • ADX03 and ADX04 specify the identification of the adjustment.
SI
Shipper's Identifying Number for Shipment (SID)
ADX-04
127
Reference Number
Required
String (AN)
Min 1Max 30

Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.

IT1 Loop
OptionalMax >1
Usage notes

This loop is optional. It will occur only in case of a unit price adjustment.

IT1
130
Detail > ENT Loop > ADX Loop > IT1 Loop > IT1

Baseline Item Data (Invoice)

RequiredMax use 1

To specify the basic and most frequently used line item data for the invoice and related transactions.

  • Loop IT1 within the ADX loop is the adjustment line item detail loop.
Example
IT1-02
358
Quantity Invoiced
Required
Decimal number (R)
Min 1Max 10

Number of units invoiced (supplier units).

IT1-03
355
Unit or Basis for Measurement Code
Required
Identifier (ID)

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

PC
Piece
IT1-04
212
Unit Price
Required
Decimal number (R)
Min 1Max 14

Price per unit of product, service, commodity, etc.

IT1-06
235
Product/Service ID Qualifier
Required
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234).

  • IT106 through IT125 provides for ten (10) different product/service ID's for each item. For example: Case, Color, Drawing No., UPC No., ISBN No., Model No., SKU.
PO
Purchase Order Number
IT1-07
234
Product/Service ID
Required
String (AN)
Min 1Max 30

Identifying number for a product or service.

Usage notes

TMS purchase order number.

IT1-10
235
Product/Service ID Qualifier
Required
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234).

BP
Buyer's Part Number
IT1-11
234
Product/Service ID
Required
String (AN)
Min 1Max 30

Identifying number for a product or service.

Usage notes

TMS part number.

IT1 Loop end
ADX Loop end
RMR Loop
RequiredMax >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
RMR-01
128
Reference Number Qualifier
Required
Identifier (ID)

Code qualifying the Reference Number.

  • Parties using this segment should agree on the content of RMR01 and RMR02 prior to initiating communication.
SI
Shipper's Identifying Number for Shipment (SID)
RMR-02
127
Reference Number
Required
String (AN)
Min 1Max 30

Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.

RMR-03
482
Payment Action Code
Required
Identifier (ID)

Code specifying the type of accounts receivable open item(s) to be included in a cash application.

  • If RMR03 is present, it specifies how the cash is to be applied.
  • If RMR03 is not present, this is a payment for an open item. If paying an open item, RMR02 must be present. If not paying a specific open item, RMR04 must be present.
ER
Evaluated Receipts Settlement
RMR-04
782
Monetary Amount
Required
Decimal number (R)
Min 1Max 15

Monetary amount.

  • RMR04 is the amount paid.
IT1 Loop
RequiredMax >1
IT1
190
Detail > ENT Loop > RMR Loop > IT1 Loop > IT1

Baseline Item Data (Invoice)

RequiredMax use 1

To specify the basic and most frequently used line item data for the invoice and related transactions.

  • Loop IT1 within the RMR loop is the remittance line item detail loop.
Example
IT1-02
358
Quantity Invoiced
Required
Decimal number (R)
Min 1Max 10

Number of units invoiced (supplier units).

IT1-03
355
Unit or Basis for Measurement Code
Required
Identifier (ID)

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

PC
Piece
IT1-04
212
Unit Price
Required
Decimal number (R)
Min 1Max 14

Price per unit of product, service, commodity, etc.

IT1-06
235
Product/Service ID Qualifier
Required
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234).

  • IT106 through IT125 provides for ten (10) different product/service ID's for each item. For example: Case, Color, Drawing No., UPC No., ISBN No., Model No., SKU.
PO
Purchase Order Number
IT1-07
234
Product/Service ID
Required
String (AN)
Min 1Max 30

Identifying number for a product or service.

IT1-10
235
Product/Service ID Qualifier
Required
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234).

BP
Buyer's Part Number
IT1-11
234
Product/Service ID
Required
String (AN)
Min 1Max 30

Identifying number for a product or service.

ITA Loop
OptionalMax >1
ITA
202
Detail > ENT Loop > RMR Loop > IT1 Loop > ITA Loop > ITA

Allowance, Charge or Service

RequiredMax use 1

To specify allowances, charges or services

Example
ITA-01
248
Allowance or Charge Indicator
Required
Identifier (ID)

Code which indicates an allowance or charge for the service specified.

  • If ITA01 = A-Allowance or C-Charge, then at least one of ITA06, ITA07, or ITA08 must be present.
A
Allowance
C
Charge
ITA-03
560
Special Services Code
Required
Identifier (ID)

Code identifying the special service.

240
Brokerage Charges
315
Duty Charges
C0020
Cash Discount
DI
Discount
FC
Freight Charges
PC
Packaging Charge
S0022
Sleeving
TX
Special Tax
ZZ
Special Service Code
ITA-04
331
Allowance or Charge Method of Handling Code
Required
Identifier (ID)

Code indicating method of handling for an allowance or charge.

02
Off Invoice
06
Charge to be Paid by Customer
ITA-07
360
Allowance or Charge Total Amount
Optional
Numeric (N2)
Min 1Max 9

Total dollar amount for the allowance or charge.

  • If ITA07 is present with either ITA06 or ITA08, then ITA07 takes precedence.
ITA Loop end
IT1 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 one 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 a transmission.

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

This number uniquely identifies the interchange data to the sender. It is assigned by the sender. Together with the sender ID it uniquely identifies the interchange data to the receiver. It is suggested that the sender, receiver, and all third parties be able to maintain an audit trail of interchanges using this number.

EDI Samples

820 Sample

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *240314*1948*U*00304*000000001*0*T*>~
GS*RA*SENDERGS*RECEIVERGS*240314*194831*000000001*X*003040~
ST*820*000000021~
BPR*I*49266*C*ACH~
REF*SI*SHIPID000000001~
REF*IV*SHIPID000000001~
DTM*011*960208~
DTM*003*960210~
DTM*020*960212~
N1*VN**92*029AA~
ENT*999999~
ADX*50278*01*SI*SHIPID000000001~
IT1**25*PC*20111**PO*TS111111***BP*1234567890AAAAA~
RMR*SI*SHIPID000000001*ER*24266~
IT1**24*PC*10111**PO*TS111111***BP*1234567890AAAAA~
RMR*SI*SHIPID000000001*ER*23000~
IT1**23*PC*10000**PO*TS222222***BP*1234567890BBBBB~
ITA*A**C0020*02~
ITA*A**DI*02~
ITA*C**S0022*06~
ITA*C**PC*06***1000~
ITA*C**FC*06~
ITA*C**315*06***1000~
ITA*C**240*06~
ITA*C**ZZ*06~
ITA*C**TX*06~
SE*25*000000021~
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.