EDI Specifications 210 Motor Invoice Based on ANSI X.12...
Transcript of EDI Specifications 210 Motor Invoice Based on ANSI X.12...
EDI Specifications 210 – Motor Invoice
Based on ANSI X.12 Standards Version 4010
EDI Implementation Guide – 210 Specs
2
Table of Contents (Control + Click to Navigate)
1. Introduction 3
1.1 Status 3
1.2 Introduction 3
1.3 Customization 3
2. Transaction Set Structure Chart 3
3. Motor Invoice Transaction Set Details 4
3.1 Motor Segment Details 4
3.2 Motor Invoice Header Section 6 3.2.1 ISA Interchange Control Header 6
3.2.2 GS Functional Group Header 8
3.2.3 ST Transaction Set Header 9
3.2.4 B3 Beginning Segment for Carrier Invoice 10
3.2.5 C3 Currency 12
3.2.6 N9 Reference Identification 13
3.2.7 G62 Date/Time 14
3.2.8 R3 Route Information – Motor 15 3.3 Motor Invoice Loop 0100 16
3.3.1 N1 Name 17
3.3.2 N3 Address Information 18
3.3.3 N4 Geographic Location 19
3.4 Motor Invoice Loop 0400 20 3.4.1 LX Assigned Number 21
3.4.2 L5 Description, Marks, and Numbers 22
3.4.3 L0 Line Item – Quantity and Weight 23
3.4.4 L1 Rates and Charges 25
3.4.5 L7 Tariff Reference 26
3.4.6 K1 Remarks 27
3.5 Motor Invoice Summary Section 28 3.5.1 L3 Total Weight and Charges 28
3.5.2 SE Transaction Set Trailer 29
3.5.3 GE Functional Group Trailer 30
3.5.4 IEA Interchange Control Trailer 31
4. Raw Data Example 32
EDI Implementation Guide – 210 Specs
3
1. Introduction
1.1 Status Transaction set 210
Version 4010
1.2 Introduction
This Draft Standard modified by enVista contains the format and establishes the data contents of the Motor Carrier Freight Details and Invoice Transaction Set (210) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide detail information for charges for services rendered by a motor carrier. It is used both as a motor carrier invoice to request payment and as details pertaining to motor freight shipment(s) charges. This draft includes specifications and notes pertaining to enVista specific EDI
transmission setups. Any questions about these specs or enVista and the services they provide can be directed to
1.3 Customization –
enVista is capable of a wide range of customizations based off of these specs, your system, and different set-up requirements. At the beginning of the new setup enVista will provide a Trading Partner Profile, listing credentials, contact information, and specific requirements for your client. enVista also engages in a test-file process, ensuring that the sending and receiving systems align correctly.
2. 210 Transaction Set Organization Chart
EDI Implementation Guide – 210 Specs
4
3. Motor Invoice Transaction Set Details
3.1 Motor Segment Details
This section describes each segment used in the enVista version of the 4010- 210 – Motor Invoice Transaction set.
Only those elements or codes used by enVista are used in this document. This document should be used in
conjunction with published 4010 standards. This will ensure the correct use for all data elements and segments.
Ref. Destination: The destination field (segment) for the element.
ID: The identification number of the element.
Element Name: Name of the element, can be used in conjunction with the reference destination in
communication.
Req:
M Mandatory The data element must be used if the segment is used.
O Optional The data element may be used if the segment is used.
X Conditional The data element may be used only if other elements are used within
the segment.
The particular condition/relation will be stated in the Data Element
Summary for the segment when used.
Element Type:
ID Identifier Values for the identifier-type data elements are taken from a pre-defined
list in the ASC X12 Data Element Dictionary.
AN String Values for the string-type data elements are a sequence of any
printable characters.
DT Date Values for a date-type data element are in the format YYYYMMDD.
TM Time Values for a time-type data element are in the format HHMM,
expressed in 24 hour clock.
Nx Numeric Values for a numeric-type data element are in an implied decimal
format, where „„X‟‟ indicates the number of places to the right of
the decimal point.
e.g.
N0 is a whole number (999)
N2 is 999.99 shown as 99999
R Decimal This is a numeric field in character format, with a decimal point
included. It is treated as alpha/numeric. The decimal point is not
sent for whole numbers.
to send the number 0128.734 the field would contain „„128.734‟‟.
to send the number 0789.00 the field would contain „„789‟‟.
EDI Implementation Guide – 210 Specs
5
Minimum/Maximum: This is the minimum and maximum length the field can be.
e.g.
02/02 - fixed length of 2 characters.
04/09 - minimum length of 4 characters and maximum length of 9
characters.
Usage: Note: This differs from the “Req” Attribute as Usage is set by enVista for
information needed. This will vary based on the specific setup. Please consult the
Trading Partner Profile provided at the beginning of the on-boarding process for
additional requirements.
MU Must Use This element must be included if the segment is present.
U Used This element may be included within the segment.
U/MU Conditional This element must be used if another element is used within the segment. This
will be listed within the description of the element.
Segment Specific Attributes:
User Option (Usage): Whether enVista requires you must use this segment, or if it can be used.
Elements: The number of elements that can be included within the segment.
Loop: The applicable loop that this segment resides in.
Max: The maximum number of times the segment can be repeated within the file (for
the ISA, GS, GE, IEA) , within each transaction set (ST, B3, C3, N9, G62, R3,
Loop 0100, Loop 0400, L3, SE), or within each loop (N1,N3, N4, LX, L5, L0,
L1, L7, K1).
EDI Implementation Guide – 210 Specs
6
3.2 Motor Invoice Header Section
3.2.1 ISA Interchange Control Header
User Option (Usage): Must use Elements: 16 Loop: N/A Max: 1 To start and identify an interchange of zero or more functional groups and interchange-related control segments
Ref Id Element Name Req Type Min/Max Usage
ISA01 I01 Authorization Information Qualifier M ID 2/2 MU
Description: Code to identify the type of information in the Authorization Information
ISA02 I02 Authorization Information M AN 10/10 MU
Description: 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)
ISA03 I03 Security Information Qualifier M ID 2/2 MU
Description: Code to identify the type of information in the Security Information
ISA04 I04 Security Information M AN 10/10 MU
Description: 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)
ISA05 I05 Interchange ID Qualifier M ID 2/2 MU
Description: Qualifier to designate the system/method of code structure used to designate
the sender or receiver ID element being qualified
ISA06 I06 Interchange Sender ID M AN 15/15 MU
Description: 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
ISA07 I05 Interchange ID Qualifier M ID 2/2 MU
Description: Qualifier to designate the system/method of code structure used to designate
the sender or receiver ID element being qualified
ISA08 I07 Interchange Receiver ID M AN 15/15 MU
Description: 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.
Note: This code is provided by enVista in the Trading Partner Profile
ISA09 I08 Interchange Date M DT 6/6 MU
Description: Date of the interchange
ISA10 I09 Interchange Time M TM 4/4 MU
Description: Time of the interchange
EDI Implementation Guide – 210 Specs
7
Ref Id Element Name Req Type Min/Max Usage
ISA11 I10 Interchange Control Standards Identifier M ID 1/1 MU
Description: Code to identify the agency responsible for the control standard used by the
message that is enclosed by the interchange header and trailer
ISA12 I11 Interchange Control Version Number M ID 5/5 MU
Description: Code specifying the version number of the interchange control segments
ISA13 I12 Interchange Control Number M N0 9/9 MU
Description: A control number assigned by the interchange sender
ISA14 I13 Acknowledgment Requested M ID 1/1 MU
Description: Code sent by the sender to request an interchange acknowledgment (TA10)
ISA15 I14 Usage Indicator M ID 1/1 MU
Description: Code to indicate whether data enclosed by this interchange envelope is test,
production or information.
Note: For enVista, use “T” for test files and “P” for production files.
ISA16 I15 Component Element Separator M 1/1 MU
Description: 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
Example:
ISA*00* *00* *02*SENDER ID *ZZ*RECEIVER ID
*140730*0950*U*00401*000000017*0*P*>
EDI Implementation Guide – 210 Specs
8
3.2.2 GS Functional Group Header
User Option (Usage): Must use Elements: 8 Loop: N/A Max: 1
To indicate the beginning of a functional group and to provide control information
Ref Id Element Name Req Type Min/Max Usage
GS01 479 Functional Identifier Code M ID 2/2 MU
Description: Code identifying a group of application related transaction sets
GS02 142 Application Sender's Code M AN 2/15 MU
Description: Code identifying party sending transmission; codes agreed to by trading partners
GS03 124 Application Receiver's Code M AN 2/15 MU
Description: Code identifying party receiving transmission; codes agreed to by trading partners
Note: Code is provided by enVista
GS04 373 Date - Group Date M DT 8/8 MU
Description: Date expressed as CCYYMMDD
GS05 337 Time - Group Time M TM 4/8 MU
Description: 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 (00-99)
GS06 28 Group Control Number M N0 1/9 MU
Description: Assigned number originated and maintained by the sender. This must be identical to
the same data element in the associated functional group trailer, GE02
GS07 455 Responsible Agency Code M ID 1/2 MU
Description: Code identifying the issuer of the standard; this code is used in conjunction with
Data Element 480
GS08 480 Version / Release / Industry Identifier Code M AN 1/12 MU
Description: Code indicating the version, release, sub release, and industry identifier of the EDI
standard being used, including the GS and GE segments.
Note: enVista requires the use of version 4010 or 4030
Comments: 1. A functional group of related transaction sets, within the scope of X12 standards, consists of a collection of similar transaction sets enclosed by a functional group header and a functional group trailer.
Example:
GS*IM*SCAC*Receiver ID*20140530*0950*13*X*004010
EDI Implementation Guide – 210 Specs
9
3.2.3 ST Transaction Set Header
User Option (Usage): Must use Elements: 2 Loop: N/A Max: 1
To indicate the start of a transaction set and to assign a control number
Ref Id Element Name Req Type Min/Max Usage
ST01 143 Transaction Set Identifier Code - 210 M ID 3/3 MU
Description: Code uniquely identifying a Transaction Set
Note: For Motor Invoices this code will be “210”
ST02 329 Transaction Set Control Number M AN 4/9 MU
Description: Identifying control number that must be unique within the transaction
set functional group assigned by the originator for a transaction set, this code must match with SE*02
Example:
ST*210*000000135
EDI Implementation Guide – 210 Specs
10
3.2.4 B3 Beginning Segment for Carrier Invoice
User Option (Usage): Must use Elements: 13 Loop: N/A Max: 1
To transmit basic data relating to the carrier's invoice
Ref Id Element Name Req Type Min/Max Usage
B302 76 Invoice Number M AN 1/22 MU
Description: Identifying number assigned by issuer
B303 145 Shipment Identification Number O AN 1/30 U/MU
Description: Identification number assigned to the shipment by the shipper that uniquely
identifies the shipment from origin to ultimate destination and is not subject to modification; (Does not contain blanks or special characters)
Note: Please refer to Trading Partner Profile to determine if this element must be used and what reference
category to use ie. BOL #
B304 146 Shipment Method of Payment M ID 2/2 MU
Description: Code identifying payment terms for transportation charges
B305 188 Weight Unit Code O ID 1/1 U
Description: Code specifying the weight unit.
B306 373 Date – Ship Date M DT 8/8 MU
Description: Date expressed as CCYYMMDD
B307 193 Net Amount Due M N2 1/12 MU
Description: Total charges to be paid by the receiver of this transaction set expressed in the standard
monetary denomination for the currency specified
Note: Needs to match with L3*05 and sum of the L104’s
B308 202 Correction Indicator O ID 2/2 U
Description: Code used to indicate that the transaction set contains information which
corrects previous information.
Note: Only original invoices should be sent to enVista. All Balance Due invoices should be sent as
paper to [email protected] or the physical address noted in the Trading Partner Profile.
B309 32 Delivery Date X DT 8/8 U/MU
Description: Date for delivery of cargo to final consignee or to next mode expressed in format CCYYMMDD.
If B310 is present then B309 must be used as well
B310 374 Date/Time Qualifier X ID 3/3 U
Description: Code specifying type of date or time, or both date and time. If B309 is present, B310must be
used as well
Note: For enVista use code 035 - Delivered
Code Name Code Name Code Name
CC Collect PP Prepaid (By Seller) TP Third Party Pay
Code Name Code Name
L Pounds K Kilograms
EDI Implementation Guide – 210 Specs
11
Ref Id Element Name Req Type Min/Max Usage
B311 140 Standard Carrier Alpha Code M ID 2/4 MU
Description: Standard Carrier Alpha Code (SCAC)
B312 373 Date O DT 8/8 U
Description: Date expressed as CCYYMMDD
B313 375 Tariff Service Code O ID 2/2 U
Description: Code specifying the types of services for rating purposes
B314 335 Transportation Terms Code O ID 3/3 U
Description: Code identifying the trade terms which apply to the shipment transportation responsibility
Semantics: 1. On collect freight bills the data in B309 will be the actual delivery date. For the shipments invoiced prior to delivery, the B309 will be the estimated date of delivery. 2. If B314 is used, B304 will indicate the party or parties responsible for payment of the transportation terms identified in B314.
Example:
B3**0576289*057628913*CC*L*20140730*41564**20140328*035*SCAC
EDI Implementation Guide – 210 Specs
12
3.2.5 C3 Currency
User Option (Usage): Used (Must Use if not USD) Elements: 4 Loop: N/A Max: 1
To specify the currency being used in the transaction set
Ref Id Element Name Req Type Min/Max Usage
C301 100 Currency Code – Billing Currency M ID 3/3 MU
Description: Code (Standard ISO) for country in whose currency the charges are specified
C302 280 Exchange Rate O R 4/10 U
Description: Value to be used as a multiplier conversion factor to convert monetary value
from one currency to another
C303 100 Currency Code – Payment Currency O ID 3/3 U
Description: Code (Standard ISO) for country in whose currency the charges are specified
C304 100 Currency Code – Rated Currency O ID 3/3 U
Description: Code (Standard ISO) for country in whose currency the charges are specified
Comments: 1. Currency is implied by the code for the country in whose currency the monetary amounts are specified.
Example:
C3*USD
Code Name Code Name
CAD Canadian Dollars EUR Euro
GBP British Pound USD US Dollars
EDI Implementation Guide – 210 Specs
13
3.2.6 N9 Reference Identification
User Option (Usage): Used/Must Use Elements: 2 Loop: N/A Max: 300
To transmit identifying information as specified by the Reference Identification Qualifier
Note: Depending on the setup this segment may be required. Please refer to the Trading Partner Profile.
Ref Id Element Name Req Type Min/Max Usage
N901 128 Reference Identification Qualifier M ID 2/3 MU
Description: Code qualifying the Reference Identification
N902 127 Reference Identification X AN 1/30 MU
Description: Reference information as defined for a particular Transaction Set or as
specified by the Reference Identification Qualifier
Example:
N9*PO*700428
Code Name Code Name
BM Bill of Lading Number LO Load Planning Number
CR Customer Reference Number PG Product Group
CT Contract Number PO Purchase Order Number
DP Department Number TH Transportation Account Code
GE Geographic Number More See TPP for additional codes if required
EDI Implementation Guide – 210 Specs
14
3.2.7 G62 Date/Time
User Option (Usage): Used/Must Use Elements: 4 Loop: N/A Max: 62
To specify pertinent dates and times
Note: Depending on the setup this segment may be required. Please refer to the Trading Partner Profile.
Ref Id Element Name Req Type Min/Max Usage
G6201 432 Date Qualifier X ID 2/2 MU
Description: Code specifying type of date. If G6202 is present, then the G6201 is required.
G6202 373 Date X DT 8/8 MU
Description: Date expressed as CCYYMMDD. If G6201 is present, then the G6202 is required.
G6203 176 Time Qualifier X ID 1/2 U/MU
Description: Code specifying type of time. If G6204 is present, then the G6203 is required.
G6204 337 Time X TM 4/8 U/MU
Description: 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 (00-99). If G6203 is present, then the G6204 is required.
Example:
G62*86*20140911*8*0930
Code Name Code Name
35 Delivery Date 86 Actual Pickup Date
11 Shipped on Date
Code Name Code Name
8 Actual Delivery Time
EDI Implementation Guide – 210 Specs
15
3.2.8 R3 Route Information - Motor
User Option (Usage): Used Elements: 5 Loop: N/A Max: 12
To specify carrier and routing sequences and details
Ref Id Element Name Req Type Min/Max Usage
R301 140 Standard Carrier Alpha Code M ID 2/4 MU
Description: Standard Carrier Alpha Code (SCAC)
R302 133 Routing Sequence Code M ID 1/2 MU
Description: Code describing the relationship of a carrier to a specific shipment movement
Code Name Code Name
B Origin/Delivery Carrier 1 1st Carrier after Origin Carrier
2 2nd Carrier after Origin C, etc.. O Origin Carrier (Air, Motor, or Ocean)
R304 91 Transportation Method/Type Code O ID 1/2 U
Description: Code specifying the method or type of transportation for the shipment
R306 76 Invoice Number O AN 1/22 U
Description: Identifying number assigned by issuer
R310 284 Service Level Code X ID 2/2 U
Description: Code indicating the level of transportation service or the billing service offered
by the transportation carrier
Example:
R3*SCAC*B
Code Name Code Name
A Air FL Motor (Flatbed)
J Motor/Truck Load LT Less than Trailer load (LTL)
S Ocean ZZ Mutually Defined
EDI Implementation Guide – 210 Specs
16
3.3 Motor Invoice Loop 0100
User Option (Usage): Must Use Elements: N/A Loop: 0100 Max: 10
To identify a party by type of organization, name, and code
Note: enVista requires this is used for the Shipper, Consignee, and Bill-To.
Ref Id Element Name Req Type Min/Max Usage
110 N1 Name O 1 MU
130 N3 Address Information O 2 MU
140 N4 Geographic Location O 1 MU
EDI Implementation Guide – 210 Specs
17
3.3.1 N1 Name
User Option (Usage): Must Use Elements: 4 Loop: 0100 Max: 1
To identify a party by type of organization, name, and code
Ref Id Element Name Req Type Min/Max Usage
N101 98 Entity Identifier Code M ID 2/3 MU
Description: Code identifying an organizational entity, a physical location, property or an individual
Code Name Code Name
BT Bill-To (Required) CN Consignee (Required)
SH Shipper (Required)
N102 93 Name X AN 1/60 MU
Description: Free-form name
Note: For enVista the Bill-To must be listed as “(Customer) c/o enVista”
N103 66 Identification Code Qualifier X ID 1/2 U/MU
Description: Code designating the system/method of code structure used for Identification Code. If N104 is
present then N103 is required.
N104 67 Identification Code X AN 2/80 U/MU
Description: Code identifying a party or other code. If N103 is present then N104 is required.
Syntax Rules: 1. R0203 - At least one of N102 or N103 is required. Example:
N1*BT*BILL-TO NAME % ENVISTA
EDI Implementation Guide – 210 Specs
18
3.3.2 N3 Address Information
User Option (Usage): Must Use Elements: 1 Loop: 0100 Max: 2
To specify the location of the named party
Ref Id Element Name Req Type Min/Max Usage
N301 166 Address Information M AN 1/55 MU
Description: Address number and street name
Note: For enVista the Bill-To must be listed as “11711 N MERIDIAN ST - STE 415”
Example:
N3*11711 N MERIDIAN ST STE 415
EDI Implementation Guide – 210 Specs
19
3.3.3 N4 Geographic Location
User Option (Usage): Must use Elements: 4 Loop: 0100 Max: 1
To specify the geographic place of the named party
Note: For enVista the Bill-To must be listed as “Carmel*IN*46032”
Ref Id Element Name Req Type Min/Max Usage
N401 19 City Name O AN 2/30 MU
Description: Free-form text for city name
N402 156 State or Province Code O ID 2/2 U/MU
Description: Code (Standard State/Province) as defined by appropriate government agency
Note: N402 is required only if city name (N401) is in the U.S. or Canada.
N403 116 Postal Code O ID 3/15 MU
Description: Code defining international postal zone code excluding punctuation and blanks Note: For N403 if within the United States must use the zip code
N404 26 Country Code O ID 2/3 U/MU
Description: Code identifying the country
Note: Required if city name (N401) is not in the U.S.
Example:
N4*CARMEL*IN*46032*US
EDI Implementation Guide – 210 Specs
20
3.4 Motor Invoice Loop 0400
User Option (Usage): Must use Elements: N/A Loop: 0400 Max: 9999
To reference a line number in a transaction set
Ref Id Element Name Req Type Min/Max Usage
120 LX Assigned Number O 1 MU
140 L5 Description, Marks and Numbers O 30 U
170 L0 Line Item - Quantity and Weight O 10 MU
180 L1 Rate and Charges O 10 MU
200 L7 Tariff Reference O 10 U
210 K1 Remarks O 10 U
EDI Implementation Guide – 210 Specs
21
3.4.1 LX Assigned Number
User Option (Usage): Must Use Elements: 1 Loop: 0400 Max: 1
To reference a line number in a transaction set
Ref Id Element Name Req Type Min/Max Usage
LX01 554 Assigned Number M N0 1/6 MU
Description: Number assigned for differentiation within a transaction set
Example:
LX*1
EDI Implementation Guide – 210 Specs
22
3.4.2 L5 Description, Marks and Numbers
User Option (Usage): Must Use Elements: 2 Loop: 0400 Max: 30
To specify the line item in terms of description, quantity, packaging, and marks and numbers
Ref Id Element Name Req Type Min/Max Usage
L501 213 Lading Line Item Number O N0 1/3 MU
Description: Sequential line number for a lading item
L502 79 Lading Description O AN 1/50 U
Description: Description of an item as required for rating and billing purposes. This may also be used to send
quantity information as part of the product description.
Note: Must use L1*12 for lading description
Example:
L5*1*POSTER MATERIAL
EDI Implementation Guide – 210 Specs
23
3.4.3 L0 Line Item – Quantity and Weight
User Option (Usage): Used/Must Use Elements: 5 Loop: 0400 Max: 10
To specify quantity, weight, volume, and type of service for a line item including applicable "quantity/rate-as" data
Note: This section is Must Use if applicable
Ref Id Element Name Req Type Min/Max Usage
L001 213 Lading Line Item Number O N0 1/3 MU
Description: Sequential line number for a lading item
L002 220 Billed/Rated-as Quantity X R 1/11 U/MU
Description: Amount of what is being billed. If L003 is present then L002 must be used
L003 221 Billed/Rated-as Qualifier X ID 2/2 U/MU
Description: Code defining type of billed/rated quantity. If L002 is present then L003 must be used
Code Name Code Name
FR Flat Rate LB Pound
MR Mileage NP Piece
L004 81 Weight X R 1/10 U/MU
Description: Numeric value of weight. If L005 is present then L004 must be used
L005 187 Weight Qualifier X ID 1/2 U/MU
Description: Code defining the type of weight. If L004 is present then L005 must be used as well
L008 80 Lading Quantity X N0 1/7 U/MU
Description: Number of units (pieces) of the lading commodity. If L009 is present then L008 must be used
L009 211 Packaging Form Code X ID 3/3 U/MU
Description: Code for packaging form of the lading quantity. If L008 is included then L009 must be used
Code Name Code Name
CTN Carton PCS Pieces
PLT Pallets UNT Unit
Code Name Code Name
B Billed Weight G Gross Weight
N Actual Net Weight
EDI Implementation Guide – 210 Specs
24
Ref Id Element Name Req Type Min/Max Usage
L011 188 Weight Unit Code X ID 1/1 U/MU
Description: Code for the carrier quantity unit of measurement in relation to L008 and L009
Code Name Code Name
G Grams K Kilograms
L Pounds
Syntax Rules: 1. C1104 - If L011 is present, then L004 is required.
Example: L0*1*1146*FR*2029*G***32*PCS
EDI Implementation Guide – 210 Specs
25
3.4.4 L1 Rate and Charges
User Option (Usage): Must Use Elements: 5 Loop: 0400 Max: 10
To specify rate and charges detail relative to a line item including freight charges, advances, special charges, and entitlements
Ref Id Element Name Req Type Min/Max Usage
L101 213 Lading Line Item Number O N0 1/3 MU
Description: Sequential line number for a lading item
L102 60 Freight Rate X R 1/9 U/MU
Description: Rate that applies to the specific commodity. If L103 is present then L102 must be used
L103 122 Rate/Value Qualifier X ID 2/2 U/MU
Description: Code qualifying how to extend charges or interpret value. If L102 is present then L103 must be
used
L104 58 Charge X N2 1/12 MU
Description: For a line item: freight or special charge; for the total invoice: the total charges --
expressed in the standard monetary denomination for the currency specified
L108 150 Special Charge or Allowance Code O ID 3/3 MU
Description: Code identifying type of special charge or allowance
L112 276 Special Charge Description O AN 2/25 MU
Description: Description of an item as required for rating and billing purposes.
Note: Use the L1*12 for Item description instead of L5*02
Example: L1*1*295.1*FR*29510****400****Freight of All Kinds
Code Name Code Name
FR Flat Rate PM Per Mile
PH Per Hundred Percent Percent
Code Name Code Name
400 Freight FUE Fuel Charge
EDI Implementation Guide – 210 Specs
26
3.4.5 L7 Tariff Reference
User Option (Usage): Used Elements: 2 Loop: 0400 Max: 10
To reference details of the tariff used to arrive at applicable rates or charge
Ref Id Element Name Req Type Min/Max Usage
L701 213 Lading Line Item Number O N0 1/3 MU
Description: Sequential line number for a lading item
L707 59 Freight Class Code O AN 2/5 MU
Description: Code indicating generalized classification that applies to one or more items
in the shipment, i.e., class 70, 77.5, etc.
Example:
L7*1******77.5
EDI Implementation Guide – 210 Specs
27
3.4.6 K1 Remarks
User Option (Usage): Used Elements: 2 Loop: 0400 Max: 10
To transmit information in a free-form format for comment or special instruction
Ref Id Element Name Req Type Min/Max Usage
K101 61 Free-Form Message M AN 1/30 MU
K102 61 Free-Form Message O AN 1/30 U
EDI Implementation Guide – 210 Specs
28
3.5 Motor Invoice Summary Section
3.5.1 L3 Total Weight and Charges
User Option (Usage): Must use Elements: 7 Loop: N/A Max: 1
To specify the total shipment in terms of weight, volume, rates, charges, advances, and prepaid amounts applicable to one or more line items
Ref Id Element Name Req Type Min/Max Usage
L301 81 Weight X R 1/10 MU
Description: Numeric value of weight.
L302 187 Weight Qualifier X ID 1/2 MU
Description: Code defining the type of weight.
Code Name Code Name
B Billed Weight G Gross Weight
N Actual Net Weight
L303 60 Freight Rate X R 1/9 U
Description: Rate that applies to the specific commodity. If L304 is present then L303 must be used
L304 122 Rate/Value Qualifier X ID 2/2 U
Description: Code qualifying how to extend charges or interpret value. If L303 is present then L304 must be
used
Code Name Code Name
FR Flat Rate LB Pound
MR Mileage NP Piece
L305 58 Charge – Total Charge O N2 1/12 MU
Description: For a line item: freight or special charge; for the total invoice: the total charges --
expressed in the standard monetary denomination for the currency specified
L311 80 Lading Quantity O N0 1/7 U
Description: Number of units (pieces) of the lading commodity
L312 188 Weight Unit Code O ID 1/1 U
Description: Code specifying the weight unit
Code Name Code Name
G Grams K Kilograms
L Pounds
Example: L3*800*G***27926******2
EDI Implementation Guide – 210 Specs
29
3.5.2 SE Transaction Set Trailer
User Option (Usage): Must Use Elements: 2 Loop: N/A Max: 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)
Ref Id Element Name Req Type Min/Max Usage
SE01 96 Number of Included Segments M N0 1/10 MU
Description: Total number of segments included in a transaction set including ST and SE segments
SE02 329 Transaction Set Control Number M AN 4/9 MU
Description: Identifying control number that must be unique within the transaction
set functional group assigned by the originator for a transaction set. Matches with ST*02
Comments: 1. SE is the last segment of each transaction set.
Example:
SE*25*000000138
EDI Implementation Guide – 210 Specs
30
3.5.3 GE Functional Group Trailer
User Option (Usage): Must Use Elements: 2 Loop: N/A Max: 1
To indicate the end of a functional group and to provide control information
Ref Id Element Name Req Type Min/Max Usage
GE01 97 Number of Transaction Sets Included M N0 1/6 MU
Description: Total number of transaction sets included in the functional group or interchange
(transmission) group terminated by the trailer containing this data element
GE02 28 Group Control Number M N0 1/9 MU
Description: Assigned number originated and maintained by the sender. Must be identical to GS06
Comments: 1. The use of identical data interchange control numbers in the associated functional group header and trailer is designed to maximize functional group integrity. The control number is the same as that used in the corresponding header.
Example:
GE*4*17
EDI Implementation Guide – 210 Specs
31
3.5.4 IEA Interchange Control Trailer
User Option (Usage): Must Use Elements: 2 Loop: N/A Max: 1
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Ref Id Element Name Req Type Min/Max Usage
IEA01 I16 Number of Included Functional Groups M N0 1/5 MU
Description: A count of the number of functional groups included in an interchange
IEA02 I12 Interchange Control Number M N0 9/9 MU
Description: A control number assigned by the interchange sender
Example:
IEA*1*000000017
EDI Implementation Guide – 210 Specs
32
4. Raw Data Example
The following is a generic 210, 4 invoice EDI file. This raw data example is also included in the
onboarding packet as an .EDI file, which can be viewed in a data viewer/editor such as Liason’s EDI
Notepad or Helios Software Solution’s TextPad. The first invoices in this file matches with the examples
located in each segment.
ISA*00* *00* *02*SENDER ID *ZZ*RECEIVER ID
*140730*0950*U*00401*000000017*0*P*>
GS*IM*SCAC*Receiver ID*20140530*0950*13*X*004010
ST*210*000000135
B3**0576289*057628913*CC*L*20140730*41564**20140328*035*SCAC
C3*USD
N9*PO*700428
R3*SCAC*B
G62*86*20140911*8*0930
N1*SH*SHIPPERS NAME
N3*SHIPPERS STREET ADDRESS
N4*CITY*ST*POSTAL CODE*COUNTRY
N1*CN*CONSIGNEE NAME
N3*CONSIGNEE STREET ADDRESS
N4*CITY*STATE*POSTAL CODE*COUNTRY
N1*BT*BILL-TO NAME % ENVISTA
N3*11711 N MERIDIAN ST STE 415
N4*CARMEL*IN*46032*US
LX*1
L5*1*POSTER MATERIAL
L0*1*1146*FR*2029*G***32*PCS
L1*1*295.1*FR*29510****400****POSTER MATERIAL
L7*1******77.5
LX*2
L5*2*FUEL SURCHARGE(29.%)
L1*2***12054****FUE
L3*2029*G***41564******2
SE*25*000000135
ST*210*000000136
B3**0576290*B05762901*TP*L*20140730*16478**20140215*035*SCAC
C3*USD
N9*PO*700438
R3*SCAC*B
N1*SH*SHIPPERS NAME
N3*SHIPPERS STREET ADDRESS
N4*CITY*STATE*POSTAL CODE*COUNTRY
N1*CN*CONSIGNEE NAME
N3*CONSIGNEE STREET ADDRESS
N4*CITY*STATE*POSTAL CODE*COUNTRY
N1*BT*BILL-TO NAME % ENVISTA
N3*11711 N MERIDIAN ST STE 415
N4*CARMEL*IN*46032*US
LX*1
L5*1*BANNERS AND FLAGS
L0*1*1062*FR*450*G
L1*1*115.51*FR*11551****400****BANNERS AND FLAGS
L7*1******77.5
EDI Implementation Guide – 210 Specs
33
LX*2
L5*2*FUEL SURCHARGE(29%)
L1*2***4927****FUE
L3*450*G***16478******1
SE*24*000000136
ST*210*000000137
B3**0576291*B0576525911*CC*L*20140730*16918**20140221*035*SCAC
C3*USD
N9*PO*27524837
R3*SCAC*B
N1*SH*SHIPPERS NAME
N3*SHIPPERS STREET ADDRESS
N4*CITY*STATE*POSTAL CODE*COUNTRY
N1*CN*CONSIGNEE NAME
N3*CONSIGNEE STREET ADDRESS
N4*CITY*STATE*POSTAL CODE*COUNTRY
N1*BT*BILL-TO NAME % ENVISTA
N3*11711 N MERIDIAN ST STE 415
N4*CARMEL*IN*46032*US
LX*1
L5*1*PLASTIC DISPLAYS
L0*1*293*FR*125*G
L1*1*118.43*FR*11843****400****PLASTIC DISPLAYS
L7*1******77.5
LX*2
L5*2*FUEL SURCHARGE(30%)
L1*2***5075****FUE****FUEL SURCHARGE
L3*125*G***16918******28
SE*24*000000137
ST*210*000000138
B3**0576292*B05763229259*PP*L*20140730*27926**20140423*035*SCAC
C3*USD
N9*PO*701595828
R3*SCAC*B
N1*SH*SHIPPERS NAME
N3*SHIPPERS STREET ADDRESS
N4*CITY*STATE*POSTAL CODE*COUNTRY
N1*CN*CONSIGNEE NAME
N3*CONSIGNEE STREET ADDRESS
N4*CITY*STATE*POSTAL CODE*COUNTRY
N1*BT*BILL-TO NAME % ENVISTA
N3*11711 N MERIDIAN ST STE 415
N4*CARMEL*IN*46032*US
LX*1
L5*1*MIXED MERCHANDICE
L0*1*1029*FR*800*G
L1*1*195.48*FR*19548****400****MIXED MERCHANDICE
L7*1******77.5
LX*2
L5*2*FUEL SURCHARGE(30%)
L1*2***8378****FUE****FUEL SURCHARGE
L3*800*G***27926******2
SE*24*000000138
GE*4*13
IEA*1*000000017