Toyota Motor Sales
/
Invoice
  • Specification
  • EDI Inspector
Import guide into your account
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 810 Invoice

X12 Release 3010

This standard provides the format and establishes the data contents of an invoice transaction set. The invoice transaction set provides for customary and established business and industry practice relative to the billing for goods and services provided.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI samples
  • None included
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/toyota-motor-sales/invoice/01HQ1BYHVH8MC3VEXNVHS83DX9
Powered by
Build EDI implementation guides at stedi.com
Overview
ISA
-
Max use 1
Required
GS
-
Functional Group Header
Max use 1
Required
heading
ST
010
Transaction Set Header
Max use 1
Required
BIG
020
Beginning Segment for Invoice
Max use 1
Required
REF
050
Reference Numbers
Max use 12
Required
N1 Loop
DTM
140
Date/Time Reference
Max use 10
Required
summary
TDS
010
Total Monetary Value Summary
Max use 1
Required
TXI
020
Tax Information
Max use 10
Optional
ITA Loop
CTT
070
Transaction Totals
Max use 1
Required
SE
080
Transaction Set Trailer
Max use 1
Required
GE
-
Functional Group Trailer
Max use 1
Required
IEA
-
Max use 1
Required
GS

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.

IN
Invoice Information (810,819)
GS-02
142
Application Sender's Code
Required
String (AN)
Min 2Max 12

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

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

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

GS-04
29
Group Date
Required
Date (DT)
YYMMDD format

Date sender generated a functional group of transaction sets.

GS-05
30
Group Time
Required
Time (TM)
HHMM format

Time (HHMM) when the sender generated a functional group of transaction sets (local time at sender's location).

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
Identifier (ID)

Code indicating the version, release, subrelease and industry identifier of the EDI standard being used. Positions 1-3, version number; positions 4-6, release and subrelease level of version; positions 7-12, industry or trade association identifier (optionally assigned by user).

003010
Draft Standards Approved By ASC X12 Through June 1990.

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) is intended for use by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the invoice transaction set).
810
X12.2 Invoice
ST-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number assigned by the originator for a transaction set.

BIG
020
Heading > BIG

Beginning Segment for Invoice

RequiredMax use 1

To indicate the beginning of an invoice transaction set and to transmit identifying numbers and dates.

Usage notes

Indicates start of invoice transaction. Includes invoice number and invoice date.

Example
BIG-01
245
Invoice Date
Required
Date (DT)
YYMMDD format

Invoice Issue Date.
YYMMDD.

BIG-02
76
Invoice Number
Required
String (AN)
Min 1Max 22

Identifying number assigned by issuer.

  • BIG07 is used only to further define the type of invoice when needed.
Usage notes

Vendor invoice number.

REF
050
Heading > REF

Reference Numbers

RequiredMax use 12

To specify identifying numbers.

Usage notes

Indicates reference qualifier and shipment ID, bill of lading, and packing list.

Segment with a value of “VN” is paired with the following N1 segment value of “ST” for telemarketing dealer code.

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

Code qualifying the Reference Number.

BM
Bill of Lading Number
PK
Packing List Number
SI
Shipper's Identifying Number for Shipment (SID)
VN
Vendor Reference
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.

  • Either REF02 or REF03 is required.
N1 Loop
RequiredMax >1
Usage notes

Indicates ID code and qualifier and TMS assigned vendor code.

N1
070
Heading > N1 Loop > N1

Name

RequiredMax use 1

To identify a party by type of organization, name and code

Example
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity or a physical location.

  • At least one of N102 or N103 must be present.
ST
Ship To
SU
Supplier/Manufacturer
N1-03
66
Identification Code Qualifier
Required
Identifier (ID)

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

92
Assigned by Buyer or Buyer's Agent
N1-04
67
Identification Code
Required
Identifier (ID)
Min 2Max 17

Code identifying a party.

  • 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.
N1 Loop end
DTM
140
Heading > DTM

Date/Time Reference

RequiredMax use 10

To specify pertinent dates and times

Usage notes

Indicates date/time qualifiers. Includes shipment date.

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

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

  • At least one of DTM02 or DTM03 must be present.
011
Shipped
DTM-02
373
Date
Required
Date (DT)
YYMMDD format

Date (YYMMDD).

Heading end

Detail

IT1 Loop
RequiredMax >1
Usage notes

Specifies invoice quantity, unit FOB, TMS purchase order number, line item number, TMS part number, and case numbers.

IT1
010
Detail > 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.

Example
IT1-02
358
Quantity Invoiced
Required
Decimal number (R)
Min 1Max 10

Number of units invoiced (supplier units).

  • If IT108 is present, then IT109 is required.
IT1-03
355
Unit of Measurement Code
Required
Identifier (ID)

Code identifying the basic unit of measurement.

  • If IT110 is present, then IT111 is required.
PC
Piece
IT1-04
212
Unit Price
Required
Decimal number (R)
Min 1Max 14

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

  • If IT112 is present, then IT113 is required.
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.
  • If IT116 is present, then IT117 is required.
PO
Purchase Order Number
IT1-07
234
Product/Service ID
Required
String (AN)

Identifying number for a product or service.

  • If IT118 is present, then IT119 is required.
TELE
Telemarketing
IT1-08
235
Product/Service ID Qualifier
Required
Identifier (ID)

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

  • If IT120 is present, then IT121 is required.
VN
Vendor's (Seller's) Item Number
IT1-09
234
Product/Service ID
Required
String (AN)
Min 1Max 30

Identifying number for a product or service.

  • If IT122 is present, then IT123 is required.
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).

  • If IT124 is present, then IT125 is required.
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. No dashes (“-“) allowed.

IT1 Loop end
Detail end

Summary

TDS
010
Summary > TDS

Total Monetary Value Summary

RequiredMax use 1

To specify the total invoice discounts and amounts

Usage notes

Specifies invoice amounts and discount amount.

Example
TDS-01
361
Total Invoice Amount
Required
Numeric (N2)
Min 1Max 10

Amount of invoice (including charges, less allowances) before terms discount (if discount is applicable).

TDS-04
362
Terms Discount Amount
Required
Numeric (N2)
Min 1Max 10

Total amount of terms discount.

TXI
020
Summary > TXI

Tax Information

OptionalMax use 10

To specify tax information.

Usage notes

Specifies which type of tax and the tax dollar amount.

Example
TXI-01
963
Tax Type Code
Required
Identifier (ID)

Code specifying the type of tax.

  • Either TXI02 or TXI03 is required
CP
County/Parish Sales Tax
CS
City Sales Tax
CT
County Tax
FT
Federal Excise Tax
LS
State and Local Sales Tax
LT
Local Tax (All applicable sales taxes by taxing authority below the state level).
MT
Metropolitan Transit Tax
ST
State Sales Tax
VA
Value Added Tax
ZZ
Mutually Defined
TXI-02
782
Monetary Amount
Required
Decimal number (R)
Min 1Max 15

Monetary amount.

  • TXI02 is the monetary amount of the tax.
  • If either TXI04 or TXI05 is present, then the other is required.
ITA Loop
OptionalMax >1
Usage notes

Specifies charge indicator, charge method.

ITA
040
Summary > 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.
C
Charge
ITA-03
560
Special Services Code
Required
Identifier (ID)

Code identifying the special service.

240
Brokerage Charges
315
Duty Charges
FC
Freight Charges
IN
Insurance Charges
PC
Packaging Charges
S0022
Sleeving
ZZ
Mutually Defined
ITA-04
331
Allowance or Charge Method of Handling Code
Required
Identifier (ID)

Code indicating method of handling for an allowance or charge.

06
Charge to be Paid by Customer
ITA-07
360
Allowance or Charge Total Amount
Required
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
CTT
070
Summary > CTT

Transaction Totals

RequiredMax use 1

To transmit a hash total for a specific element in the transaction set

  • Number of line items (CTT01) is the accumulation of the number of IT1 segments. If used, hash total (CTT02) is the sum of the value of quantities invoiced (IT102) for each IT1 segment.
Usage notes

Used to transmit a total for a specific element in the transaction.

Example
CTT-01
354
Number of Line Items
Required
Numeric (N0)
Min 1Max 6

Total number of line items in the transaction set.

  • If CTT03 is present, then CTT04 is required.
SE
080
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 6

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

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.