Carrier. Invoice. EDI 210 Format X12 Version Inbound. Revised: August 25, 2011 Version:
|
|
|
- Julianna Welch
- 10 years ago
- Views:
Transcription
1 Carrier Invoice EDI 210 Format X12 Version Inbound Revised: August 25, 2011 Version: Please see last page of document for updates included in this version
2 EXECUTIVE SUMMARY The Invoice is used to electronically communicate shipment cost information to the Shipper. The Invoice includes information about the load such as reference numbers, actual pickup and delivery times, locations, line-haul rate and charge, accessorial rates and charges, etc. Freight Invoice EDI documents in Sterling TMS use the ANSI X (Motor Carrier Load Freight Details and Invoice) specification version This specification is included as well as examples of its use. Three types of inbound Freight Invoice messages are supported by Sterling TMS: 1. Original First invoice for a particular shipment. 2. Adjustment An invoice that contains only new charges, not included on the original invoice. 3. Rebilling A complete replacement invoice for a particular shipment. Sterling TMS will send 997 Functional Acknowledgments for this EDI transaction upon request. Sterling TMS sends both positive and negative acknowledgements. If a 210 transaction does not adhere to this spec, it will be rejected and the reason for the rejection will be included in the 997. Special Characters Delimiters Sterling TMS uses the asterisk (*) for the element separator, the tilde (~) for the segment terminator, and the vertical bar ( ) for the sub-element separator. Please do not use any other delimiters. Handling of Other Special Characters Sterling TMS will change the following characters to spaces: \ Sterling TMS will change the pound sign (#) to be NO. Sterling TMS will change the percent symbol (%) to be C/O which stands for care of if the percent symbol is the first character in an element. Other uses of the percent symbol will be changed to PCT. 1
3 EDI FORMAT 210 Motor Carrier Freight Details and Invoice Introduction: Functional Group ID=IM This Draft Standard for Trial Use 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 or as details pertaining to motor freight shipment(s) charges. Heading: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments M 0010 ISA Interchange Control Header M 1 M 0020 GS Functional Group Header M 1 M 0100 ST Transaction Set Header M 1 M 0200 B3 Beginning Segment for Carrier's Invoice M 1 R 0400 C3 Currency O ITD Terms of Sale/Deferred Terms of Sale O N9 Reference Identification O R3 Route Information - Motor O K1 Remarks O 10 LOOP ID M 1100 N1 Name O N3 Address Information O N4 Geographic Location O 1 Detail: LOOP ID N7 Equipment Details O 1 Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments LOOP ID S5 Stop-off Details O 1 n N9 Reference Identification O G62 Date/Time O 10 LOOP ID N1 Name O N3 Address Information O N4 Geographic Location O N9 Reference Identification O 5 LOOP ID M 1200 LX Assigned Number O N9 Reference Identification O L5 Description, Marks and Numbers O L0 Line Item - Quantity and Weight O 10 R 1800 L1 Rate and Charges O 10 Summary: 2
4 Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments M 0200 SE Transaction Set Trailer M 1 M 0210 GE Functional Group Trailer M 1 M 0220 IEA Interchange Control Trailer M 1 Transaction Set Notes 1. Loops 0300, 0305, 0310 and 0320 shall only be used to identify locations and associated data for loading and unloading of freight. 3
5 Segment: ISA Interchange Control Header Position: 0010 Loop: Level: Heading Usage: Mandatory Max Use: 1 Purpose: Syntax Notes: Semantic Notes: Comments: To start and identify an interchange of zero or more functional groups and interchange-related control segments M ISA01 I01 Authorization Information Qualifier M ID 2/2 Code to identify the type of information in the Authorization Information 00 No Authorization Information Present (No Meaningful Information in I02) M ISA02 I02 Authorization Information M AN 10/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) M ISA03 I03 Security Information Qualifier M ID 2/2 Code to identify the type of information in the Security Information 00 No Security Information Present (No Meaningful Information in I04) M ISA04 I04 Security Information M AN 10/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) M ISA05 I05 Interchange ID Qualifier M ID 2/2 Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified 02 SCAC (Standard Carrier Alpha Code) M ISA06 I06 Interchange Sender ID M AN 15/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 Carrier s Legal SCAC. M ISA07 I05 Interchange ID Qualifier M ID 2/2 Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified. ZZ for test (Sandbox) 01 for Production Mutually Defined Duns (Dun & Bradstreet) Number 4
6 M ISA08 I07 Interchange Receiver ID M AN 15/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 NISTEVO or NVTxxxxxxxxx for Test (Sandbox) or NVOxxxxxxxxx for production Note: use NVTxxxxxxxxx or NVOxxxxxxxxx to create unique Trading Partner relationships per Shipper (our TMS Customer) where xxxxxxxxx is usually the Shipper s DUNS Number. M ISA09 I08 Interchange Date M DT 6/6 Date of the interchange M ISA10 I09 Interchange Time M TM 4/4 Time of the interchange M ISA11 I65 Repetition Separator M AN 1/1 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 The repetition separator is "^" M ISA12 I11 Interchange Control Version Number M ID 5/5 This version number covers the interchange control segments Standard Issued as ANSI X M ISA13 I12 Interchange Control Number M N0 9/9 A control number assigned by the interchange sender M ISA14 I13 Acknowledgment Requested M ID 1/1 Code sent by the sender to request an interchange acknowledgment (TA1) 0 No Acknowledgment Requested M ISA15 I14 Usage Indicator M ID 1/1 Code to indicate whether data enclosed by this interchange envelope is test, production or information P Production Data T Test Data M ISA16 I15 Component Element Separator M AN 1/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 " " is the sub-element separator. 5
7 Segment: GS Functional Group Header Position: 0020 Loop: Level: Heading Usage: Mandatory Max Use: 1 Purpose: To indicate the beginning of a functional group and to provide control information Syntax Notes: Semantic Notes: 1 GS04 is the group date. 2 GS05 is the group time. 3 The data interchange control number GS06 in this header must be identical to the same data element in the associated functional group trailer, GE02. 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. M GS Functional Identifier Code M ID 2/2 IM Motor Carrier Freight Details and Invoice (210) M GS Application Sender's Code M AN 2/15 Code identifying party sending transmission; codes agreed to by trading partners Carrier s Legal SCAC code. M GS Application Receiver s Code M AN 2/15 Code identifying party receiving transmission; codes agreed to by trading partners NISTEVO or NVTxxxxxxxxx for Test (Sandbox) or NVOxxxxxxxxx for production M GS Date M DT 8/8 Date expressed as CCYYMMDD M GS Time M TM 4/8 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) M GS06 28 Group Control Number M N0 1/9 Assigned number originated and maintained by the sender M GS Responsible Agency Code M ID 1/2 X Accredited Standards Committee X12 M GS Version / Release / Industry Identifier Code M AN 1/ Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October
8 Segment: ST Transaction Set Header Position: 0100 Loop: Level: Heading Usage: Mandatory Max Use: 1 Purpose: To indicate the start of a transaction set and to assign a control number Syntax Notes: Semantic Notes: 1 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). 1 The implementation convention reference (ST03) is used by the translation routines of the interchange partners to select the appropriate implementation convention to match the transaction set definition. Comments: M ST Transaction Set Identifier Code M ID 3/3 Code uniquely identifying a Transaction Set 210 Motor Carrier Freight Details and Invoice M ST Transaction Set Control Number M AN 4/9 Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set. THIS NUMBER SHOULD BE UNIQUE! We recommend following the UCS guidelines by concatenating a 5-digit GS control number with a 4-digit incremental counter. For example, if your GS control number is and this is the third occurrence of the ST loop in this document, the value in ST02 would be ST Implementation Convention Reference O AN 1/35 Reference assigned to identify Implementation Convention 7
9 Segment: B3 Beginning Segment for Carrier s Invoice Position: 0200 Loop: Level: Heading Usage: Mandatory Max Use: 1 Purpose: To transmit basic data relating to the carrier s invoice Syntax Notes: 1 If either B309 or B310 is present, then the other is required. Semantic Notes: 1 B306 is the billing date. 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. 1 If B314 is used, B304 will indicate the party or parties responsible for payment of the transportation terms identified in B314. Comments: M B Invoice Number M AN 1/22 Identifying number assigned by issuer M B Shipment Identification Number O AN 1/30 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) Must match the SID in the Sterling TMS system to be processed. M B Shipment Method of Payment M ID 2/2 Code identifying payment terms for transportation charges CC Collect CF Collect, Freight Credited Back to Customer PC Prepaid but Charged to Customer PP Prepaid (by Seller) TP Third Party Pay M B Date M DT 8/8 Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year Current Invoice Date M B Net Amount Due M N2 1/12 Total charges to be paid by the receiver of this transaction set expressed in the standard monetary denomination for the currency specified B Correction Indicator O ID 2/2 Code used to indicate that the transaction set contains information which corrects previous information AD RB Adjustment of Previous Freight Bill Charges This should be sent after the first invoice if there are new accessorial charges or changes to previous charges. Rebilling (Ignore Previous Bill) Rebillings are treated as replacements and should contain all freight invoice detail information. M B Standard Carrier Alpha Code M ID 2/4 Standard Carrier Alpha Code Carrier SCAC or Carrier Fleet SCAC 8
10 B Date O DT 8/8 Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year Original Invoice Date 9
11 Segment: C3 Currency Position: 0400 Loop: Level: Heading Usage: Optional (Recommended for Sterling TMS) Max Use: 1 Purpose: To specify the currency being used in the transaction set Syntax Notes: Semantic Notes: 1 C301 is the billing currency. 2 C303 is the payment currency. 3 C304 is the rated currency. Comments: 1 Currency is implied by the code for the country in whose currency the monetary amounts are specified. Notes: This segment is recommended for Sterling TMS and should be sent when possible. Note that if this segment is not supplied then the applicable Contract currency will be assumed. M C Currency Code M ID 3/3 Code (Standard ISO) for country in whose currency the charges are specified Any valid code may be placed in this element. CAD Canadian Dollars USD United States Dollars MXN Mexican Pesos EUR Euro Dollars 10
12 Segment: ITD Terms of Sale/Deferred Terms of Sale Position: 0500 Loop: Level: Heading Usage: Optional Max Use: 1 Purpose: To specify terms of sale Syntax Notes: 1 If ITD03 is present, then at least one of ITD04 ITD05 or ITD13 is required. 2 If ITD08 is present, then at least one of ITD04 ITD05 or ITD13 is required. 3 If ITD09 is present, then at least one of ITD10 or ITD11 is required. Semantic Notes: 1 ITD15 is the percentage applied to a base amount used to determine a late payment charge. Comments: 1 If the code in ITD01 is "04", then ITD07 or ITD09 is required and either ITD10 or ITD11 is required; if the code in ITD01 is "05", then ITD06 or ITD07 is required. Notes: In general this segment is for backwards compatibility. ITD Terms Type Code O ID 2/2 Code identifying type of payment terms Refer to Data Element Dictionary for acceptable code values. ITD Terms Basis Date Code O ID 1/2 Code identifying the beginning of the terms period Refer to Data Element Dictionary for acceptable code values. ITD Terms Discount Percent O R 1/6 Terms discount percentage, expressed as a percent, available to the purchaser if an invoice is paid on or before the Terms Discount Due Date ITD Terms Discount Days Due X N0 1/3 Number of days in the terms discount period by which payment is due if terms discount is earned ITD Terms Net Days O N0 1/3 Number of days until total invoice amount is due (discount not applicable) 11
13 Segment: N9 Reference Identification Position: 0600 Loop: Level: Heading Usage: Optional Max Use: 300 Purpose: To transmit identifying information as specified by the Reference Identification Qualifier Syntax Notes: 1 At least one of N902 or N903 is required. 2 If N906 is present, then N905 is required. 3 If either C04003 or C04004 is present, then the other is required. 4 If either C04005 or C04006 is present, then the other is required. Semantic Notes: 1 N906 reflects the time zone which the time reflects. 2 N907 contains data relating to the value cited in N902. Comments: M N Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification Refer to Data Element Dictionary for acceptable code values. See Appendix 1 for list of supported reference qualifiers. N Reference Identification X AN 1/50 Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier N Free-form Description X AN 1/45 Free-form descriptive text 12
14 Segment: R3 Route Information - Motor Position: 0800 Loop: Level: Heading Usage: Optional Max Use: 12 Purpose: To specify carrier and routing sequences and details Syntax Notes: 1 If R311 is present, then R310 is required. 2 If R312 is present, then R311 is required. Semantic Notes: 1 R303 is the station or city name at which carriers interchange shipments 2 R307 is the carrier's billing date. 3 R308 is the amount due the carrier. Comments: Notes: In general this segment is for backwards compatibility. M R Standard Carrier Alpha Code M ID 2/4 Standard Carrier Alpha Code M R Routing Sequence Code M ID 1/2 Code describing the relationship of a carrier to a specific shipment movement Refer to Data Element Dictionary for acceptable code values. R Transportation Method/Type Code O ID 1/2 Code specifying the method or type of transportation for the shipment A Air H Customer Pickup LT Less Than Trailer Load (LTL) M Motor (Common Carrier) O Containerized Ocean R Rail U Private Parcel Service X Intermodal (Piggyback) ZZ Mutually defined 13
15 Segment: K1 Remarks Position: 1000 Loop: Level: Heading Usage: Optional Max Use: 10 Purpose: To transmit information in a free-form format for comment or special instruction Syntax Notes: Semantic Notes: Comments: M K Free-Form Message M AN 1/30 Free-form information K Free-Form Message O AN 1/30 Free-form information 14
16 Segment: N1 Name Position: 1100 Loop: 0100 Optional Level: Heading Usage: Optional (Mandatory for Sterling TMS) Max Use: 1 Purpose: To identify a party by type of organization, name, and code Syntax Notes: 1 At least one of N102 or N103 is required. 2 If either N103 or N104 is present, then the other is required. Semantic Notes: Comments: 1 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. 2 N105 and N106 further define the type of entity in N101. Notes: The N1 SH segment is used to identify the Sterling TMS s Subscriber Organization Id. Sterling TMS often refers to its subscriber as the Shipper or the Shipment Owner. M N Entity Identifier Code M ID 2/3 Code identifying an organizational entity, a physical location, property or an individual BT Bill-to-Party Optional N1 Segment Usage Used to indicate the Bill-to-Party Name, Bill-to-Party Organization Id, and Bill-to-Party Address Information.. PE PF N104 contains the DUNS Number of the Party that should be Billed for this Freight Invoice. Note that the N104 will also be used as the Shipment Owner Organization if it is not supplied in the N1 SH or PR segments. Payee Optional N1 Segment Usage N104 contains the SCAC or DUNS Number of the Party that should be paid for this Freight Invoice. Party to Receive Freight Bill Optional, maybe used instead of the Bill-to-Party to indicate the Bill-to-Party Name, Bill-to-Party Organization Id, and Bill-to-Party Address Information. Note that the N104 will also be used as the Shipment Owner Organization if it is not supplied in the N1 SH or PR segments. 15
17 PR SH Payer Optional N1 Segment Usage N104 contains the DUNS Number of the Party that should be Paying for this Freight Invoice. Note that the N104 will also be used as the Shipment Owner Organization if it is not supplied in the N1 SH segment. Shipper Mandatory N1 Segment Usage N104 contains the DUNS Number of the Shipper. If the Shipper is Multi-Org Shipper then this is their Child-Org DUNS Number. Note that it is mandatory to provide the Shipment Owner Organization Id. This is the Shipment Owner Organization. N Name X AN 1/60 Free-form name N Identification Code Qualifier X ID 1/2 Code designating the system/method of code structure used for Identification Code (67) 1 D-U-N-S Number, Dun & Bradstreet 2 Standard Carrier Alpha Code (SCAC) N Identification Code X AN 2/80 Code identifying a party or other code Note that Sterling TMS expects this element to be sent when possible. 16
18 Segment: N3 Address Information Position: 1300 Loop: 0100 Optional Level: Heading Usage: Optional Max Use: 2 Purpose: To specify the location of the named party Syntax Notes: Semantic Notes: Comments: Notes: Use the N3 to identify Bill-to-party Address. M N Address Information M AN 1/55 Address information N Address Information O AN 1/55 Address information 17
19 Segment: N4 Geographic Location Position: 1400 Loop: 0100 Optional Level: Heading Usage: Optional Max Use: 1 Purpose: To specify the geographic place of the named party Syntax Notes: 1 Only one of N402 or N407 may be present. 2 If N406 is present, then N405 is required. 3 If N407 is present, then N404 is required. Semantic Notes: Comments: 1 A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location. 2 N402 is required only if city name (N401) is in the U.S. or Canada. Notes: Use the N4 to identify Bill-to-party City, State, and Postal Code. N City Name O AN 2/30 Free-form text for city name N State or Province Code X ID 2/2 Code (Standard State/Province) as defined by appropriate government agency N Postal Code O ID 3/15 Code defining international postal zone code excluding punctuation and blanks (zip code for United States) N Country Code X ID 2/3 Code identifying the country 18
20 Segment: N7 Equipment Details Position: 1600 Loop: 0200 Optional Level: Heading Usage: Optional Max Use: 1 Purpose: To identify the equipment Syntax Notes: 1 If either N703 or N704 is present, then the other is required. 2 If either N705 or N716 is present, then the other is required. 3 If either N708 or N709 is present, then the other is required. Semantic Notes: 1 N712 is the owner of the equipment. 2 N723 is the operator or carrier of the rights of the equipment. Comments: 1 N701 is mandatory for rail transactions. 2 N720 and N721 are expressed in inches. Notes: In general this segment is for backwards compatibility. N Equipment Initial O AN 1/4 Prefix or alphabetic part of an equipment unit's identifying number M N Equipment Number M AN 1/10 Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred) N Equipment Description Code O ID 2/2 Code identifying type of equipment used for shipment Refer to Data Element Dictionary for acceptable code values. N Equipment Length O N0 4/5 Length (in feet and inches) of equipment ordered or used to transport shipment (The format is FFFII where FFF is feet and II is inches; the range for II is 00 through 11) N Equipment Type O ID 4/4 Code identifying equipment type 19
21 Segment: S5 Stop-off Details Position: 0100 Loop: 0300 Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To specify stop-off detail reference numbers and stop reason Syntax Notes: 1 If either S503 or S504 is present, then the other is required. 2 If either S505 or S506 is present, then the other is required. 3 If either S507 or S508 is present, then the other is required. Semantic Notes: 1 S509 is the stop reason description. Comments: Notes: In general this segment is for backwards compatibility only. M S Stop Sequence Number M N0 1/3 Identifying number for the specific stop and the sequence in which the stop is to be performed M S Stop Reason Code M ID 2/2 Code specifying the reason for the stop Refer to Data Element Dictionary for acceptable code values. 20
22 Segment: N9 Reference Identification Position: 0200 Loop: 0300 Optional Level: Detail Usage: Optional Max Use: 10 Purpose: To transmit identifying information as specified by the Reference Identification Qualifier Syntax Notes: 1 At least one of N902 or N903 is required. 2 If N906 is present, then N905 is required. 3 If either C04003 or C04004 is present, then the other is required. 4 If either C04005 or C04006 is present, then the other is required. Semantic Notes: 1 N906 reflects the time zone which the time reflects. 2 N907 contains data relating to the value cited in N902. Comments: Notes: In general this segment is for backwards compatibility only. M N Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification Refer to Data Element Dictionary for acceptable code values. N Reference Identification X AN 1/30 Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier N Free-form Description X AN 1/45 Free-form descriptive text 21
23 Segment: G62 Date/Time Position: 0300 Loop: 0300 Optional Level: Detail Usage: Optional Max Use: 10 Purpose: To specify pertinent dates and times Syntax Notes: 1 At least one of G6201 or G6203 is required. 2 If either G6201 or G6202 is present, then the other is required. 3 If either G6203 or G6204 is present, then the other is required. Semantic Notes: Comments: Notes: In general this segment is for backwards compatibility only. G Date Qualifier X ID 2/2 Code specifying type of date Refer to Data Element Dictionary for acceptable code values. G Date X DT 8/8 Date expressed as CCYYMMDD G Time Qualifier X ID 1/2 Code specifying the reported time Refer to Data Element Dictionary for acceptable code values. G Time X TM 4/8 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) G Time Code O ID 2/2 Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that follow Refer to Data Element Dictionary for acceptable code values. 22
24 Segment: N1 Name Position: 0500 Loop: 0310 Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To identify a party by type of organization, name, and code Syntax Notes: 1 At least one of N102 or N103 is required. 2 If either N103 or N104 is present, then the other is required. Semantic Notes: Comments: 1 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. 2 N105 and N106 further define the type of entity in N101. Notes: In general this segment is for backwards compatibility only. M N Entity Identifier Code M ID 2/3 Code identifying an organizational entity, a physical location, property or an individual Refer to Data Element Dictionary for acceptable code values. SF Ship From ST Ship To N Name X AN 1/60 Free-form name N Identification Code Qualifier X ID 1/2 Code designating the system/method of code structure used for Identification Code (67) Refer to Data Element Dictionary for acceptable code values. N Identification Code X AN 2/80 Code identifying a party or other code ID number of the pickup (if N101 = "SF") or delivery (if N101 = "ST") location. 23
25 Segment: Segment: N3 Address Information Position: 0700 Loop: 0310 Optional Level: Detail Usage: Optional Max Use: 2 Purpose: To specify the location of the named party Syntax Notes: Semantic Notes: Comments: Notes: In general this segment is for backwards compatibility only. M N Address Information M AN 1/55 Address information N Address Information O AN 1/55 Address information 24
26 Segment: N4 Geographic Location Position: 0800 Loop: 0310 Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To specify the geographic place of the named party Syntax Notes: 1 Only one of N402 or N407 may be present. 2 If N406 is present, then N405 is required. 3 If N407 is present, then N404 is required. Semantic Notes: Comments: 1 A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location. 2 N402 is required only if city name (N401) is in the U.S. or Canada. Notes: In general this segment is for backwards compatibility only. N City Name O AN 2/30 Free-form text for city name N State or Province Code X ID 2/2 Code (Standard State/Province) as defined by appropriate government agency N Postal Code O ID 3/15 Code defining international postal zone code excluding punctuation and blanks (zip code for United States) N Country Code X ID 2/3 Code identifying the country 25
27 Segment: N9 Reference Identification Position: 0900 Loop: 0310 Optional Level: Detail Usage: Optional Max Use: 5 Purpose: To transmit identifying information as specified by the Reference Identification Qualifier Syntax Notes: 1 At least one of N902 or N903 is required. 2 If N906 is present, then N905 is required. 3 If either C04003 or C04004 is present, then the other is required. 4 If either C04005 or C04006 is present, then the other is required. Semantic Notes: 1 N906 reflects the time zone which the time reflects. 2 N907 contains data relating to the value cited in N902. Comments: Notes: In general this segment is for backwards compatibility only. M N Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification Refer to Data Element Dictionary for acceptable code values. N Reference Identification X AN 1/30 Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier N Free-form Description X AN 1/45 Free-form descriptive text 26
28 Segment: LX Assigned Number Position: 1200 Loop: 0400 Optional Level: Detail Usage: Optional (Mandatory for Sterling TMS) Max Use: 1 Purpose: To reference a line number in a transaction set Syntax Notes: Semantic Notes: Comments: M LX Assigned Number M N0 1/6 Number assigned for differentiation within a transaction set 27
29 Segment: N9 Reference Identification Position: 1300 Loop: 0400 Optional Level: Detail Usage: Optional Max Use: 5 Purpose: To transmit identifying information as specified by the Reference Identification Qualifier Syntax Notes: 1 At least one of N902 or N903 is required. 2 If N906 is present, then N905 is required. 3 If either C04003 or C04004 is present, then the other is required. 4 If either C04005 or C04006 is present, then the other is required. Semantic Notes: 1 N906 reflects the time zone which the time reflects. 2 N907 contains data relating to the value cited in N902. Comments: Notes: This segment is used to indicate the Location of the Freight Cost Detail M N Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification See Appendix 1 for a list of valid reference qualifiers. LU Location Number Used to indicate the Location of the Freight Cost Detail N Reference Identification X AN 1/50 Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier N Free-form Description X AN 1/45 Free-form descriptive text 28
30 Segment: L5 Description, Marks and Numbers Position: 1400 Loop: 0400 Optional Level: Detail Usage: Optional Max Use: 30 Purpose: To specify the line item in terms of description, quantity, packaging, and marks and numbers Syntax Notes: 1 If either L503 or L504 is present, then the other is required. 2 If L507 is present, then L506 is required. 3 If either L508 or L509 is present, then the other is required. Semantic Notes: Comments: 1 L502 may be used to send quantity information as part of the product description. Notes: In general this segment is for backwards compatibility. L Lading Line Item Number O N0 1/3 Sequential line number for a lading item L Lading Description O AN 1/50 Description of an item as required for rating and billing purposes L Commodity Code X AN 1/30 Code describing a commodity or group of commodities L Commodity Code Qualifier X ID 1/1 Code identifying the commodity coding system used for Commodity Code Refer to Data Element Dictionary for acceptable code values. L Commodity Code Qualifier X ID 1/1 Code identifying the commodity coding system used for Commodity Code Refer to Data Element Dictionary for acceptable code values. L Commodity Code X AN 1/30 Code describing a commodity or group of commodities 29
31 Segment: L0 Line Item - Quantity and Weight Position: 1700 Loop: 0400 Optional Level: Detail Usage: Optional Max Use: 10 Purpose: To specify quantity, weight, volume, and type of service for a line item including applicable "quantity/rate-as" data Syntax Notes: 1 If either L002 or L003 is present, then the other is required. 2 If either L004 or L005 is present, then the other is required. 3 If either L006 or L007 is present, then the other is required. 4 If either L008 or L009 is present, then the other is required. 5 If L011 is present, then L004 is required. 6 If either L013 or L015 is present, then the other is required. Semantic Notes: 1 L008 is the number of handling units of the line item tendered to the carrier. 2 L013 can only be used if the code in L009 is PLT, SKD, or SLP. 3 L015 designates whether the carrier will be required to verify the number of units contained on a pallet, slip sheet or skid. Code "Y" indicates that the carrier will be required to verify. Code "N" indicates that the carrier will not be required to verify. Comments: 1 L013 is used to convey the total number of boxes, cartons, or pieces contained on a pallet, skid, or slip sheet for the line item. Notes: In general this segment is for backwards compatibility. L Lading Line Item Number O N0 1/3 Sequential line number for a lading item L Billed/Rated-as Quantity X R 1/11 Basis for rating (miles, value, volume, etc.); Note: Weight may be defined by either data element 220 or 81 L Billed/Rated-as Qualifier X ID 2/2 Code identifying the type of quantity or value on which the rate or item pricing is based Refer to Data Element Dictionary for acceptable code values. 30
32 Segment: L1 Rate and Charges Position: 1800 Loop: 0400 Level: Detail Usage: Optional (Recommended for Sterling TMS) Max Use: 10 Purpose: To specify rate and charges detail relative to a line item including freight charges, advances, special charges, and entitlements Syntax Notes: 1 If either L102 or L103 is present, then the other is required. 2 At least one of L104 L105 or L106 is required. 3 If either L114 or L115 is present, then the other is required. 4 If either L117 or L118 is present, then the other is required. Semantic Notes: 1 L119 is the percent used to determine the charge in L L120, if used, indicates the currency for all monetary amounts in this L1 segment. 3 L121 is the origin rated as charge amount. Comments: Notes: This segment is used to indicate the Invoice Line Detail Rated Quantity, Charge Rate, and Charge Amount. Its usage is preferred and recommended over the L0 segment. L Lading Line Item Number O N0 1/3 Sequential line number for a lading item L Freight Rate X R 1/9 Rate that applies to the specific commodity Invoice Line Detail Charge Rate L Rate/Value Qualifier X ID 2/2 Code qualifying how to extend charges or interpret value See your Shipper s List of accepted and valid codes. AG Percentage AV Ad Valorum (Per Cent of Value) [Percentage] BR Per Barrel CM Per Cubic Meter CW Per Hundred Weight Describes a transportation rate that applies to every one hundred pounds of total weight of an individual shipment FR Flat Rate FT Per Foot KG Per Kilograms KP Per Kilometer LB Per Pound MM Per Metric Ton (Tonne) MU Multiplier PD Per Day PF Per Cubic Foot PG Per Gallon PM Per Mile PP Per Piece PR Per Hour SP Per Stop WK Per Week Invoice Line Detail Charge Rate UM 31
33 L Charge X N2 1/12 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 Invoice Line Detail Charge Amount L Special Charge or Allowance Code O ID 3/3 Code identifying type of special charge or allowance Used to indicate whether the Invoice Line Detail refers to an additional Special Charge or Allowance (the L108 is supplied) or to the Standard Line Haul Charge (when the L108 is not present). Always supply the L108 element to indicate a Special Charge or Allowance accessorial. See your Shipper s List of accepted and valid codes. Also see Appendix 2 for list of supported code values. L Special Charge Description O AN 2/25 Identification of special charge; this data element is used whenever an applicable code cannot be found in data element 150 Invoice Line Detail Charge Description L Billed/Rated-as Quantity X R 1/11 Basis for rating (miles, value, volume, etc.); Note: Weight may be defined by either data element 220 or 81 Invoice Line Detail Rated Quantity L Billed/Rated-as Qualifier X ID 2/2 Code identifying the type of quantity or value on which the rate or item pricing is based See your Shipper s List of accepted and valid codes. BA Barrels Identifies a billable unit expressed as a type of container CF Cubic Foot DK Kilometers DM Miles EA Each FR Flat Rate FT Foot GL Gallon KG Kilogram LB Pound LC 100 Pounds MV Monetary Value NP Piece NU Unit A specific measurement in rating shipments SP Stops Identifies a billable unit expressed as stops that are authorized as part of a shipment of goods TD Days TH TN Hours Tons Identifies a billable unit expressed as short tons (2000 pounds) Invoice Line Detail Rated Quantity UM 32
34 L Currency Code O ID 3/3 Code (Standard ISO) for country in whose currency the charges are specified Use only if the currency for this specific charge is different than specified in the C3 segment at the heading level of the transaction. Note that any valid code may be placed in this element. CAD Canadian Dollars USD United States Dollars MXN Mexican Pesos EUR Euro Dollars 33
35 Segment: SE Transaction Set Trailer Position: 0200 Loop: Level: Summary Usage: Mandatory Max Use: 1 Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments) Syntax Notes: Semantic Notes: Comments: 1 SE is the last segment of each transaction set. M SE01 96 Number of Included Segments M N0 1/10 Total number of segments included in a transaction set including ST and SE segments M SE Transaction Set Control Number M AN 4/9 Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set 34
36 Segment: GE Functional Group Trailer Position: 0210 Loop: Level: Summary Usage: Mandatory Max Use: 1 Purpose: To indicate the end of a functional group and to provide control information Syntax Notes: Semantic Notes: 1 The data interchange control number GE02 in this trailer must be identical to the same data element in the associated functional group header, 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. M GE01 97 Number of Transaction Sets Included M N0 1/6 Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element M GE02 28 Group Control Number M N0 1/9 Assigned number originated and maintained by the sender 35
37 Segment: IEA Interchange Control Trailer Position: 0220 Loop: Level: Summary Usage: Mandatory Max Use: 1 Purpose: Syntax Notes: Semantic Notes: Comments: To define the end of an interchange of zero or more functional groups and interchange-related control segments M IEA01 I16 Number of Included Functional Groups M N0 1/5 A count of the number of functional groups included in an interchange M IEA02 I12 Interchange Control Number M N0 9/9 A control number assigned by the interchange sender 36
38 APPENDIX 1 Reference Number Qualifiers This section lists all the valid reference number qualifiers allowed by Sterling TMS. SI Shippers Identifying Number for Shipment (SID) 12 Billing Account 1P Accessorial Status Code 2I Tracking Number 4M Special Move Reference Number 6A Consignee Reference Number AO Appointment Number BL Government Bill of Lading Number BM Bill of Lading Number BN Booking Number CB Combined Shipment CG Consignee's Order Number CK Check Number CMN Continuous Move Id CN Carrier's Reference Number (PRO/Invoice) CO Customer Order Number CR Customer Reference Number CT Contract Number DJ Delivery Ticket Number DK Dock Number DO Delivery Order Number DP Department Number EV Receiving Number F8 Original Reference Number FR Freight Bill Number GD Return Goods Bill of Lading Number GZ General Ledger Account HO Shipper's Hazardous Number IA Internal Vendor Number IF Issue Number IK Invoice Number IL Internal Order Number IN Consignee's Invoice Number IT Internal Customer Number K0 Approval Code KK Delivery Reference KL Contract Reference LO Load number LT Lot Number LU Location Number MA Ship Notice/Manifest Number MB Master Bill of Lading MH Manufacturing Order Number MI Mill Order Number MR Merchandise Type OQ Order Number P8 Pickup Reference Number 37
39 PO PU PV RE RF RN RP S8 S9 SCA SN SO ST TB TK VN WY XE ZH ZZ Purchase Order Number Previous Bill of Lading Number Receiving Number Release Number Export Reference Number Run Number Repetitive Pattern Code Seal Off Number Seal On Number Standard Carrier Alpha Code (SCAC) Seal Number Shipper's Sales Order Number [Shipper's Order (Invoice Number)] Store Number Trucker's Bill of Lading Tank Number Vendor Order Number Waybill Number Transportation Priority Number Carrier Assigned Reference Number Mutually Defined 38
40 APPENDIX 2 Special Charge or Allowance Code values This section lists all the valid Special Charge or Allowance code values allowed by Sterling TMS. 020 Address Correction 045 Advance Fee 105 Acknowledgment of Delivery Fee (AOD) 140 Call Tag 160 Canadian Reconsignment Fee 240 Customs Broker Fee 250 Customs Invoice - Additional Page 275 Discount - Incentive 280 Discount - Multiple Shipment 295 Discount - Special 300 Distribution Fee 400 Freight 405 Fuel Surcharge 445 Insurance Fee 455 Insurance Premium 485 Messenger Service 520 Oversized Premium 665 Saturday Delivery 675 Security Signature Service 705 Stamp Fee 735 Tracing Inbound Via Other Carriers ADH Advance Charges Handling AFB Additional Copies of Freight Bill AIR Air Freight APT Appointment (Notification) ARB Arbitrary (In Addition to Through Rates and Charges) BEY Beyond Freight Charges BLC Bill of Lading Charge BLK Blocking and Bracing Charge BND Bond Charges BOB Bobtail Charges BUA Bunker Adjustment CHE Chassis Equipment Lease Charge CLN Cleaning Charge CNS Consolidation COD COD Amount COF Ocean Freight COL Fee for Collecting COD Charge COM Combination CON Congestion Surcharge COU Consignee Unload CRS Courier Services CSE Customs Entry CSF Customs Formalities CTG Cartage Charge CTX Customs Exams (Intensive, Tailgate) CUF Currency Adjustment Factor CUS Customs Charge DCT City Delivery 39
41 DEL DEM DEP DER DES DET DIS DIV DLH DMC DOC DRC DSC DSF DST DTD DTF DTL DTU DTV ECR EIC ELS ERS EVC EXC EXM EXP EXW FAH FUE FWA GST HAN HAZ HHB HOL HOS HOX IDL IFC IHT IIA INC INS IPU LAB LAY LDG LEC LFT LMC LNT LOA LOC LSC Delivery Charge Demurrage Detention of Power Units Derrick Charge Demurrage - Special Detention of Trailers Distribution Service Diversion and Reconsignment Drayage/Line Haul Deadhead Mileage Charge Documentation Charge Drayage Discount Detention - Special Type Flat Car Container Destuffing Destination Duty Destination Inland Freight Detention Loading Detention Unloading Detention (Vehicle) Escort/Courier Service Charge Export/Import Charge Extra Lights Empty Return Excessive Value Charge Exclusive Use Charge Excess Mileage Charge Expedited Service Charge Excess Weight Freight Surcharge Fuel Charge Forwarding Agent Commission Goods and Services Tax Charge Handling Charges on Distribution Freight Forwarded Beyond Hazardous Cargo Charge Handling Sunday or Holiday Pick-up or Delivery Hose Charge Hose Charge Special Inside Delivery Inbound Freight Charges Interstate/Highway Toll Invoice Adjustment Insurance Surcharge Insurance Inside Pick-up Extra Labor (Helper Service) Layover Charges Loading Less than Container Lift Gate (Truck) or Forklift Service at Pick-up/Delivery Labor, Modify Labor, No Trouble Found Loading (Labor Charges) Local Delivery/Drayage Labor Service 40
42 MEN MET MFC MIN MNC MPC MRK MSC MSG NFY OVR PBE PEC PER PIR PLT PMU PMX POD POS PRS PSC PSH PUC PUD PUK PWH RCC RCL REE REP RES RFD SAT SCL SCU SDC SDL SEG SER SGL SHL SOC SPC SPT SPU SRG SSC SSF SST SSX STP STR SUF SUR SWC Escort Service with Overnight Subsistence Escort Service (Telephone) Manifest Charge Minimum Guarantee Notify Consignee Miscellaneous Parts Charge Marking or Tagging Charge Other Accessorial Service Charge Miscellaneous Charge Carrier Notification Charge Over Dimension Permits Bonds Escort Attendant Pallet Exchange Charge Permit Charge Pier Pick-up and/or Delivery Pallets/Skids/Platforms Normal Pump Charge Special Pump Charge Proof of Delivery Positioning at Origin Stuffing Charge Protective Service - Cold Protective Service - Heat Pick-up Charge Pick-up and Delivery Pack and Unpack Pier Charges - Wharfage Reconsignment Charge Redelivery Regulatory Fee Residential Pick-up Residential Delivery Refund Saturday Pick-up or Delivery Charge Scale Charge Scale Charge Unloading Special Detention Charge Split Delivery Segregating (Sorting) Service Charge Single Pick-up Shipper Load Stop-off Charge Special Permits Spotting of Trailer Split Pick-up Storage Stripping, Sorting, and Consolidation Single Shipment Fee Sales Tax (State and Local) Sales and Use Tax Stopping in Transit Storage in Transit Sufferance Warehouse Charge (Export or Import) Surcharge Switching Charge 41
43 TAA TAX TDT TER TRA TRC TRF UND UNL URC USW VOR WFG WFH WHC WRC WRE WTG WTV ZZZ Telephone Charge Tax Charge Truck Detention Terminal Charge Travel Charge Trailer Rental Charge Transfer Charge Unloading Unloading (Labor Charges) Unloading/Reloading Charge Unabsorbed Switching Vehicle Ordered but Not Used Wharfage Wharfage & Handling Warehouse Charge Load Weighing Charge Empty Weighing Charge Waiting Time Weight Verification Charge Mutually Defined 42
44 This page is intentionally left blank. 43
45 EDI SAMPLE USAGE Example 1 Description This example is for a shipment that has two charges o o Line-haul is $300 for 200 miles at $1.50 per mile. Detention charge of $100 for 2 hours at $50.00 per hour. EDI Transaction ISA*00* *00* *02*SCAC *ZZ*NISTEVO *030818*2300*^*00402* *0*P* ~ GS*IM*SCAC*NISTEVO* *2300*00001*X*004020~ ST*210* ~ B3**CARRIER-INVOICE-01*SID*PP** *40000****SCAC~ C3*USD~ N9*CN*CARRIER-PRO-NUM~ N1*SH*SHIPPER*1*DUNS~ N1*BT*SENDBILLHERE*1*DUNS~ N3*123 FIRST AVENUE~ N4*MPLS*MN*55402*USA~ LX*1~ L1**1.5*PM*30000********LINE HAUL CHARGE*****200*DM~ LX*2~ L1**50*PR*10000****DET****DETENTION CHARGE*****2*TH~ SE*13* ~ GE*1*00001~ IEA*1* ~ 44
46 Example 2 Description This invoice is a second invoice for the same shipment used in Example 1. In this case, there has been a new accessorial charge added to the shipment. o Unloading charge of $70 for 2 hours at $35.00 per hour. EDI Transaction ISA*00* *00* *02*SCAC *ZZ*NISTEVO *030818*2300*^*00402* *0*P* ~ GS*IM*SCAC*NISTEVO* *2300*00002*X*004020~ ST*210* ~ B3**CARRIER-INVOICE-02*SID*PP** *40000*AD***SCAC~ C3*USD~ N9*CN*CARRIER-PRO-NUM~ N1*SH*SHIPPER*1*DUNS~ N1*BT*SENDBILLHERE*1*DUNS~ N3*123 FIRST AVENUE~ N4*MPLS*MN*55402*USA~ LX*1~ L1**35*PR*7000****UNL****UNLOADING CHARGE*****2*TH~ SE*11* ~ GE*1*00002~ IEA*1* ~ 45
47 Example 3 Description This invoice is a third invoice for the same shipment used in Example 1and 2. In this case the line-haul charge has been re-rated at a new rate. o o o Line-haul was $300 for 200 miles at $1.50 per mile. Line-haul is now $350 for 200 miles at $1.75 per mile. Difference is $50 for 200 miles at $0.25 per mile. EDI Transaction ISA*00* *00* *02*SCAC *ZZ*NISTEVO *030818*2300*^*00402* *0*P* ~ GS*IM*SCAC*NISTEVO* *2300*00003*X*004020~ ST*210* ~ B3**CARRIER-INVOICE-02*SID*PP** *40000*AD***SCAC~ C3*USD~ N9*CN*CARRIER-PRO-NUM~ N1*SH*SHIPPER*1*DUNS~ N1*BT*SENDBILLHERE*1*DUNS~ N3*123 FIRST AVENUE~ N4*MPLS*MN*55402*USA~ LX*1~ L1**0.25*PM*5000******** LINE HAUL CHARGE *****200*DM~ SE*11* ~ GE*1*00003~ IEA*1* ~ 46
48 Document Change Log /08/2003 New Document /10/2003 Removed ID code lists for L1 segment direct carrier to get this from the shipper. Corrected a number of incorrect codes and comments /31/2005 Added Appendix 2 Special Charge or Allowance Code values /03/2005 Added list of Sterling TMS supported L103 and L118 values /15/2005 Added new B308 Correction Indicator value Rebilling (RB) /10/2006 Added new Location Number Reference LU, etc /31/2006 Added new Special Charge or Allowance Code values /27/2007 Added ISA08/GS03 options /25/2007 Added new Special Charge or Allowance Code values /30/2007 Rebranded references from Nistevo to Sterling TMS where appropriate /05/2007 Update Currency Codes and added some undocumented segments /03/2008 Added additional usage information to the header level N1 segment /08/2008 Added additional usage information for the L1 segment, etc /02/2008 Allow N1 PR, or the PF or BT segments to provide the Sterling TMS Subscriber Id /27/2009 Added new Special Charge or Allowance Code values /20/2009 Remove usage of the ST03 element /15/2010 Further clarified the usage of the C3 segment /04/2011 Updated the C3 segment usage to indicated that USD is no longer assumed /29/2011 Rebranding with Sterling/IBM logo /25/2011 Rebranding with IBM logo.. 47
EDI 210 Invoice. Motor Freight 210 Invoice with Stop Offs. Version: 1.0 ANSI X.12-4010 Draft
EDI 210 Invoice Motor Freight 210 Invoice with Stop Offs Version: 1.0 ANSI X.12-4010 Draft Motor Freight Invoice 210 EDI Transaction. ANSI X.12 Standards Version 4010 1 Table of Contents 210 Motor Carrier
214 Transportation Carrier Shipment Status Message
214 Transportation Carrier Shipment Status Message Introduction: Functional Group ID=QM This Draft Standard for Tria l Use contains the format and establishes the data contents of the Transportation Carrier
EDI GUIDELINES. Motor Carrier Load Tender 204 VERSION 004010
EDI GUIDELINES otor Carrier Load Tender 204 VERSION 004010 ASC X12 Version 4010 1 April 5, 2007 204 otor Carrier Load Tender Functional Group ID=S Introduction: This Draft Standard for Trial Use contains
810 Invoice ANSI ASC X12 Version 4010
810 Invoice ANSI ASC X12 Version 4010 ERICO International 31700 Solon Rd. Solon, OH 44139 7/15/2009 Purchase Order Acknowledgment Invoice-810-855 ii 7/15/2009 Purchase Order Acknowledgment Invoice-810-855
ANSI X12 version 4010 856 Advance Ship Notice
ANSI X12 version 4010 856 Advance Ship Notice VERSION: 1.0 FINAL Author: Superior Essex Publication Date: 05/01/07 Trading Partner: All 856 All Partners 4010 Outbound.rtf 1 856 Ship Notice/Manifest Functional
810 Invoice Revised 01/26/15
Functional Group ID=IN Introduction: This Standard contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the context of an Electronic Data Interchange
ANSI X12 version 4010 820 Remittance Advice
ANSI X12 version 4010 820 Remittance Advice VERSION: 1.0 FINAL Author: Superior Essex Publication Date: 08/18/00 Trading Partner: All Notes: Remittance Advice 820's are transmitted with payment to the
ANSI ASC X.12 Standard Version 4010 Transaction Set 214 Transportation Carrier Shipment Status Message
ANSI ASC X.12 Standard Version 4010 Transaction Set 214 Transportation Carrier Shipment Status Message Revised 01/04/11 214 Transportation Carrier Shipment Status Message Functional Group=QM This Draft
ANSI X12 version 4010 864 Text Message
ANSI X12 version 4010 864 Text Message VERSION: 1.0 FINAL Author: Superior Essex Publication Date: 08/22/00 Trading Partner: All Partners 864 All Partners 4010 Inbound.rtf 1 Superior Essex 864 Text Message
2.8 861 Receiving Advice/Acceptance Certificate - SERVICE PARTS ONLY
2.8 861 Receiving Advice/Acceptance Certificate - SERVICE PARTS ONLY INFORMATION TMM REQUIRES FROM TRADING PARTNER SCOPE THIS INFORMATION INCLUDES START-UP INFORMATION SPECIFIC TO TRADING PARTNER. APPROACH
EDI 214 ANSI X12 Version 4010 Transportation Carrier Shipment Status Message
EDI 214 ANSI X12 Version 4010 Transportation Carrier Shipment Status Message 214 Transportation Carrier Shipment Status Message Functional Group=QM This Draft Standard for Trial Use contains the format
214 Transportation Carrier Shipment Status Message - LTL
214 Transportation Carrier Shipment Status Message - LTL Lowe's 214 - LTL Shipment Status Message Version: 4010 Author: Lowe's Companies, Inc Modified: 2/27/2013 Notes: This 214 Implementation Guide should
850 Purchase Order. X12/V4030/850: 850 Purchase Order. Version: 1.0 Draft
850 Purchase Order X12/V4030/850: 850 Purchase Order Version: 1.0 Draft Author: Supplier Automation Trading Partner: Ross Stores, Inc. Notes: This is the standard guide prepared by JPMC/Xign for Merchandise
Customer EDI Guidelines United States 810 Invoice
Customer EDI Guidelines United States 810 Invoice Author: CSC Consulting EMD 810_USA.doc 1 For internal only 810 Invoice Functional Group=IN This Draft Standard for Trial Use contains the format and establishes
810 Invoice. Version: 2.3 Final. X12/V4010/810 : 810 Invoice. Advance Auto Parts. Publication: 3/17/2014 Trading Partner: Notes:
810 Invoice X12/V4010/810 : 810 Invoice Version: 2.3 Final Author: Advance Auto Parts Company: Advance Auto Parts Publication: 3/17/2014 Trading Partner: Notes: Table of Contents 810 Invoice... 1 ISA
ADOBE ANSI X12 810 4010. Version: 1.0
ADOBE ANSI X12 810 4010 Version: 1.0 Author: Adobe Systems Modified: 06/15/2009 810 Invoice Functional Group=IN This Draft Standard for Trial Use contains the format and establishes the data contents of
3/31/08 ALTRA INDUSTRIAL MOTION Invoice - 810. Inbound 810 X12 4010. Page 1 Created by Ralph Lenoir
Inbound 810 X12 4010 Page 1 DOCUMENT OVERVIEW This document contains the requirements for the standard EDI 810 document in ANSI version 4010 as d by ALTRA INDUSTRIAL MOTION. It describes the layout, syntax,
824 Application Advice
824 Application Advice X12/V4040/824: 824 Application Advice Version: 2.1 Final Author: Insight Direct USA, Inc. Modified: 10/12/2006 824 Application Advice Functional Group=AG This Draft Standard for
810 Invoice ANSI X.12 Version 5010
810 Invoice SI X.12 Version 5010 *** HEADE AEA *** SEG SEGMENT EQ MAX LOOP NAME DES USE EPEAT ISA Interchange Control Header M 1 GS Functional Group Header M 1 ST Transaction Set Header M 1 BIG Beginning
EDI IMPLEMENTATION GUIDE. 856 ANSI X12 V4010 Ship Notice/Manifest Regular (Non Steel)
EDI IMPLEMENTATION GUIDE 856 ANSI X12 V4010 Ship Notice/Manifest Regular (Non Steel) Revision Date: November 7, 2013 Regular (Non Steel) Rev 6 X12 004010 pg. 1 856 Ship Notice/Manifest Introduction: Functional
EDI GUIDELINES INVOICE 810 VERSION 4010
EDI GUIDELINES INVOICE 810 VERSION 4010 Rev. 7/23/2013 GLOSSARY OF TERS Seg. Use: Reference : Number: : Consists of a segment identifier, one or more data element each preceded by an element separator,
ANSI X12 version 4010 830 Planning Schedule with Release Capability
ANSI X12 version 4010 830 Planning Schedule with Release Capability VERSION: 1.0 FINAL Author: Superior Essex Publication Date: 04/07/00 Trading Partner: All 830 All Partners 4010 Inbound.rtf 1 830 Planning
Invoice. Transaction Set (810) (Outbound from TI)
Invoice Transaction Set (810) (Outbound from TI) ANSI X12 Version Format: 3020 Date: October 1996 Copyright 1996 Texas Instruments Inc. All Rights Reserved The information and/or drawings set forth in
CSX EDI 824 Application Advice Version: 005030
CSX EDI 824 Application Advice Version: 005030 Questions about the CSX EDI 284 Implementation Guide should be directed to: 877-SHIPCSX option 2, prompt 2 Monday Friday: 7:00 AM 6:00 PM Publication: September
Portland General Electric Implementation Standard
Portland General Electric Implementation Standard for Electronic Data Interchange TRANSACTION SET 810 Ver/Rel 004010 Invoice Inbound from Vendor 8104010I 1 August 18, 2004 810 Invoice Functional Group
Note: The following information is required on all Merchandise Invoices:
810 NORDSTROM CANADA Invoice Functional Group=IN Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the
CAVALIER / GEORBON TRANSPORTATION SERVICES INC. STANDARD RULES & ACCESSORIAL CHARGES TARIFF CAV. CAVALIER / GEORBON TRANSPORTATION SERVICES INC.
CAVALIER / GEORBON TRANSPORTATION SERVICES INC. STANDARD RULES AND ACCESSORIAL CHARGES TARIFF NAMING STANDARD RULES AND ACCESSORIAL CHARGES APPLICABLE FOR THE TRANSPORTATION OF GENERAL COMMODITIES BETWEEN
856 Advance Ship Notice Supplier Implementation Guide November 2015
856 Advance Ship Notice Supplier Implementation Guide November 2015 856 Ship Notice/Manifest INTRODUCTION This implementation guideline for the 856 Ship Notice/Manifest electronic data interchange (EDI)
VERSION: ANSI X-12 004010
855 Purchase Order Acknowledgment VERSION: ANSI X-12 004010 Author: Family Dollar Stores FDS 855 layout ( VMI Order s) 1 For internal only 855 Purchase Order Acknowledgment Functional Group=PR This Draft
CVS/Caremark. Implementation Guide. 810 RX DC Invoice. Version X12-4010
CVS/Caremark Implementation Guide 810 RX DC Invoice Version X12-4010 810 Mapping Specifications v4010 i Table of Contents 810 Invoice... 1 ST Transaction Set Header... 2 BIG Beginning Segment for Invoice...
Electronic Data Interchange
Electronic Data Interchange Transaction Set: 856 Supplier Advance Ship Notice ANSI X12 Version 4010 This specification covers the requirements for Grainger and our Business Units. Grainger Industrial Supply
BIG LOTS STORES INC. IMPLEMENTATION SPECIFICATIONS ASC X12 INVOICE TRANSACTION SET 810 VERSION 5010
BIG LOTS STORES INC. IMPLEMENTATION SPECIFICATIONS ASC X12 INVOICE TRANSACTION SET 810 VERSION 5010 Last revised 3/2/2015 9:47:55 AM - 1 - Summary of Changes 2012 Changes Return merchandise must be on
IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS APPLICATION ADVICE (824) TRANSACTION SET
IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS APPLICATION ADVICE (824) TRANSACTION SET FCA US INFORMATION & COMMUNICATION TECHNOLOGY MANAGEMENT ANSI ASC X12 VERSION/RELEASE 002040CHRY FCA
BORGWARNER IMPLEMENTATION GUIDELINE FOR V4010 830 PLANNING SCHEDULE
BORGWARNER IMPLEMENTATION GUIDELINE FOR V4010 830 PLANNING SCHEDULE 1 Implementation Guideline 830 3-Jun-15 830 BorgWarner Material Release v004010 Functional Group ID=PS Introduction: This Standard contains
ANSI ASC X12 SHIPMENT STATUS (214) VERSION 004010
ANSI ASC X12 SHIPMENT STATUS (214) VERSION 004010 YRC Freight Inc. 10990 Roe Avenue Overland Park, KS 66211 www.yrcfreight.com Last Reviewed 11/22/13 Dear YRC Freight Customer: Thank you for your interest
ANSI X12 4010 867 - Product Transfer and Resale Report
ANSI X12 4010 867 - Product Transfer and Resale Report Version: R8674010v1 Draft Modified: 10/27/2004 Notes: 10/26/2004 - In an effort to validate that 100% of a partners reporting locations have been
DoD Transportation Electronic Data Interchange (EDI) Convention
Department of Defense DoD Transportation Electronic Data Interchange (EDI) Convention ASC X12 Transaction Set 824 Application Advice Invoice Acknowledgment (004010) INITIAL DRAFT August 2003 20030829 TTC
856 Advanced Shipping Notices (ASN)
NEXTEER Supplier Information Packet 856 Advanced Shipping Notices (ASN) Revised March, 2010 s GENERAL INFORMATION This packet is to provide information to Nexteer and SteeeringMex Direct Suppliers who
Implementation Guidelines: ANSI X12 Transaction Set 850 Purchase Order (Suppliers) DOCUMENT NUMBER: ICS 004010 850 S Supplier
Implementation Guidelines: ANSI X12 Transaction Set 850 (Suppliers) DOCUMENT NUMBER: ICS 004010 850 S Supplier ESSAR Steel Algoma Inc. Information Systems and Business Process Improvement Author: Greg
Toyota Boshoku America EDI Implementation Manual Version 1 for: TBA o TBIN o TBMS o TBCA - Woodstock o TBCA - Elmira
Toyota Boshoku America EDI Implementation Manual Version 1 for: TBA o TBIN o TBMS o TBCA - Woodstock o TBCA - Elmira Forward The widespread implementation of EDI (Electronic Data Interchange) throughout
999 Implementation Acknowledgment. Version: 1.0 Draft
999 Implementation Acknowledgment Version: 1.0 Draft Company: Network Health Publication: 9/11/2012 Table of Contents 999 Implementation Acknowledgment... 1 ISA Interchange Control Header... 2 GS Functional
Pos. Seg. Req. Loop No. ID Name Des. Max.Use Repeat LOOP ID IT1 200000 0100 IT1 Baseline Item Data M 1 0600 PID Product / Item Description M 1 1000
810 Invoice Introduction: Functional Group ID=IN This Standard contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the context of an Electronic Data
ASN. HDMA Electronic Data Interchange (EDI) Guidelines for the 856 Advance Ship Notice to Support Implementation of DSCSA
ASN HDMA Electronic Data Interchange (EDI) Guidelines for the Advance Ship Notice to Support Implementation of DSCSA HDMA Electronic Data Interchange (EDI) Guidelines for the Advance Ship Notice to Support
322 TERMINAL OPERATIONS AND INTERMODAL RAMP ACTIVITY
ELECTRONIC DATA INTERCHANGE (EDI) 322 TERMINAL OPERATIONS AND INTERMODAL RAMP ACTIVITY USING ASC X12 TRANSACTION SET 322 VERSION 004010 07/01/04 2 Table of Contents Introduction... 3 Sample 322... 4 The
856 Ship Notice/Manifest - R US CANADA
856 Ship Notice/Manifest - R US CANADA Introduction: Functional Group ID=SH This Implementation Guide contains the format and establishes the data contents of the Ship Notice/Manifest Transaction Set (856)
Electronic Data Interchange
Electronic Data Interchange Transaction Set: 850 Supplier Purchase Order ANSI X12 Version 4010 This specification covers the requirements for Grainger and our Business Units. Grainger Industrial Supply
EDI GUIDELINES PURCHASE ORDER 850 VERSION 4010
EDI GUIDELINES PURCHASE RDER 850 VERSIN 4010 Rev. 7/23/2013 GLSSARY F TERS BLACKHAWK NETWRK s 850 GUIDELINES Seg. Use: Reference : Number: : Consists of a segment identifier, one or more data element each
Implementation Guidelines: ANSI X12 Transaction Set 824 Application Advice DOCUMENT NUMBER: ICS 004010 824 S
Implementation Guidelines: ANSI X12 Transaction Set 824 DOCUMENT NUMBER: ICS 004010 824 S ESSAR Steel Algoma Inc. Information Systems and Business Process Improvement Author: Greg Masters Effective Date:
Eaton Corporation Electronic Data Interchange (EDI) Standards Application Advice (824) Version 4010
Eaton Corporation Electronic Data Interchange (EDI) Standards Application Advice (824) Version 4010 Revision date: 12/15/2003 Author: Kathy Grubar Copyright 2003 Eaton Corporation. All rights reserved.
84 LUMBER ELECTRONIC DATA INTERCHANGE VENDOR IMPLEMENTATION PROGRAM INFORMATION PACKAGE 810 INVOICES VERSION 4010. August 21, 2007
84 LUMBER ELECTRONIC DATA INTERCHANGE VENDOR IMPLEMENTATION PROGRAM INFORMATION PACKAGE 810 INVOICES VERSION 4010 August 21, 2007 1 of 16 84 LUMBER EDI PROFILE 1. 84 LUMBER PERSONNEL Linda Smitley, EDI
VOLVO Dealer Programs 810 Invoice EDI Guideline
VOLVO 1. 810 INVOICE General This document describes Volvo's application of the ANSI X12 transaction set. The specification offers a detailed description of those data elements which will be used. The
Dart Container Corporation. EDI 810 Outbound Invoice Version 4010
Dart Container Corporation EDI 810 Outbound Invoice Version 4010 HEADER SECTION ST - Transaction Set Header 01 Transaction Set Identifier N0 1/10 810 02 Transaction Set Control Number AN 4/9 Unique Sequence
ACE HARDWARE 810 INVOICE (FOR CREDIT MEMO ONLY) ANSI X12 4010 PLEASE DO NOT TRANSMIT WAREHOUSE OR REBATE CREDIT MEMOS.
ACE HARDWARE 810 INVOICE (FOR CREDIT MEMO ONLY) ANSI X12 4010 *NOTES: PLEASE DO NOT TRANSMIT WAREHOUSE OR REBATE CREDIT MEMOS. EXISTING DOCUMENT - SEE HIGHLIGHTED FIELDS FOR NEW ADDITIONS PLEASE REVIEW
997 MUST be sent to Safeway to confirm receipt of 824 transmission. This is unrelated to EDI syntax errors as reported on 997.
This document defines Safeway Inc. s guidelines of EDI Transaction Set 824, Application Advice, VICS Version 004010. It does not vary from the X12/UCS/VICS standards. Only segments and elements that are
944 Warehouse Stock Transfer Receipt Advice. X12/V4030/944: 944 Warehouse Stock Transfer Receipt Advice
944 Warehouse Stock Transfer Receipt Advice X12/V4030/944: 944 Warehouse Stock Transfer Receipt Advice Author: Tim Wright Company: Created: 09/04/2012 Current: 09/04/2012 Table of Contents 944 Warehouse
Produce Traceability Initiative Why and How to Use EDI 856 Advance Ship Notice/Manifest Transaction Set (ASN)
Produce Traceability Initiative Why and How to Use EDI 856 Advance Ship Notice/Manifest Transaction Set (ASN) About this Guidance Document (Revision 1.0) Guidelines are generally accepted, informally standardized
860 Purchase Order Change Request Buyer Initiated
860 Purchase Order Change Request Buyer Initiated Set Number - 860 Set Name Purchase Order Change Request Buyer Initiated Functional Group - PC This Draft Standard for Trail Use contains the format and
945 Warehouse Shipping Advice
945 Warehouse Shipping Advice Functional Group ID=SW Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Warehouse Shipping Advice Transaction Set
Now, suppliers can also select EDI as a method for receiving Change and Cancel Orders.
850 Purchase Order Functional Group ID=PO Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Transaction Set (850) for use within
Implementation Guidelines For ANSI X12 Interchange Control Structures Inbound & outbound. (v2002)
Implementation Guidelines For ANSI X12 Interchange Control Structures Inbound & outbound (v2002) ICS Interchange Control Structures Functional Group ID= Introduction: The purpose of this standard is to
KANSAS CITY SOUTHERN EDI On-Boarding Guide
KANSAS CITY SOUTHERN EDI On-Boarding Guide EDI Standards and Requirements v1.0 2015 by Kansas City Southern 1 Table of Contents 1.0 INTRODUCTION... 3 1.1 INTRODUCTION... 3 1.2 PURPOSE OF THE DOCUMENT...
Transaction Set 824 - Application Advice
TS 824 for TS 264 in X12 Version 003040 IMPLEMENTATION GUIDE Transaction Set 824 - Application Advice Transaction set (TS) 824 can be used to provide the ability to report the results of an application
CSXT EDI 404 Rail Carrier Shipment Information (Bill of Lading) v005010
CSXT EDI 404 Rail Carrier Shipment Information (Bill of Lading) v005010 Questions about the CSXT EDI 404 Implementation Guide should be directed to: 877-SHIPCSX option 2, prompt 1 Monday Friday: 7:00 AM
810 Invoice. Introduction: Heading: Functional Group ID=IN
810 Invoice Functional Group ID=IN Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the context
Bill of Lading Number REF02 127 Reference Identification M AN 1/30 MustUse
Updated 05/08/06 810 Invoice Version 005010 X12 Functional Group=IN BIG Beginning Segment for Invoice Pos: 020 Max: 1 Heading - Mandatory Loop: N/A Elements: 4 BIG01 373 Date Description: Invoice Date
RULES TARIFF 100 EFFECTIVE DATE:
RULES TARIFF 100 EFFECTIVE DATE: August 1, 2014 ISSUED BY: Quik X Transportation Inc. 6767 Davand Drive Mississauga, ON L5T 2T2 INDEX OF RULES RULE ITEM - A - Advancing of Charges... 100 After Hours Delivery
Electronic Data Interchange- Inbound Payments EDI 820/EFT Specifications for Duke Energy
Electronic Data Interchange- Inbound Payments EDI 820/EFT Specifications for Duke Energy To: Electronic Data Interchange (EDI) Partners: The following pages contain layout specifications for EDI/EFT transmissions
VDP Program Vendor Guidelines
AutoZone Merchandising Systems Vendor Reference VDP Program Vendor Guidelines (EDI X12 version 004010) Revised by Dept. 8309 EDI group February 2007 Portions of this document contain hyperlinks that are
LOOP ID - N9 1000 295 N9 Reference Identification O 1 300 MSG Message Text O 1000
850 Purchase Order Functional Group ID=PO Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Transaction Set (850) for use within
The information in this document will be common for all X12N implementation guides.
ASC X12N Implementation Guide Common Content The information in this document will be common for all X12N implementation guides. Underlined information will be replaced with publisher-inserted implementation
Electronic Document Interchange Standards Version 5050
Yazaki North America, Inc. Electronic Document Interchange Standards Version 5050 Dear Supplier. Enclosed you will find current versions of our EDI Document Guidelines for our Suppliers that are shipping
ANSI X12 ASN 856 Version 002040
ADVANCE SHIP NOTICE MESSAGE ANSI X12 ASN 856 Version 002040 V01 23/08/12 Page 1/36 Property of VALEO Duplication Prohibited Table of Contents 1 THE ADVANCE SHIP NOTICE MESSAGE...4 1.1 Introduction...4
GENERAL TARIFF 2016 EFFECTIVE: JANUARY 1 ST, 2016 REVISION: 1.6
GENERAL TARIFF 2016 N.B.: The English version of this document is the official version. In case of any inconsistency between the English and French version of same, the English version shall prevail. Oceanex
Implementation Guideline
Pennsylvania New Jersey Delaware Maryland Implementation Guideline For Electronic Data Interchange TRANSACTION SET 814 Advance Notice of Intent to Drop Request and Response Ver/Rel 004010 814 Advance Notice
Electronic Data Interchange (EDI) Standards 810 Invoice Version 4010
Electronic Data Interchange (EDI) Standards 810 Invoice Version 4010 Approved: 07/26/2010 Authors: Dave Danko HCR ManorCare is a leading provider of short and long term medical and rehabilitation care.
Staples Supplier Electronic Data Interchange Implementation Guide
Staples Supplier Electronic Data Interchange Implementation Guide June 2010 ANSI 4010 Revision 002.13 Staples Supplier EDI Implementation Guide Table of Contents GETTING STARTED WITH STAPLES...3 VAN (Value
SIDNEY TRANSPORTATION SERVICES, LLC. 777 West Russell Road P. O. Box 946 Sidney, Ohio 45365 (937) 498-2323 STS 102 STANDARD RULES AND REGULATIONS FOR
SIDNEY TRANSPORTATION SERVICES, LLC. 777 West Russell Road P. O. Box 946 Sidney, Ohio 45365 (937) 498-2323 STS 102 STANDARD RULES AND REGULATIONS FOR TRANSPORTATION SERVICES Revised January 1, 2011 APPLICATION:
Excel Invoice Format. SupplierWebsite - Excel Invoice Upload. Data Element Definition UCLA Supplier website (Rev. July 9, 2013)
Excel Invoice Format Excel Column Name Cell Format Notes Campus* Supplier Number* Invoice Number* Order Number* Invoice Date* Total Invoice Amount* Total Sales Tax Amount* Discount Amount Discount Percent
HIPAA EDI Companion Guide for 835 Electronic Remittance Advice
HIPAA EDI Companion Guide for 835 Electronic Remittance Advice ASC X12 Standards for Electronic Data Interchange Technical Report Type 3 (TR3) Version 005010X221A1 Companion Guide Version: 2.0 Disclosure
810 - Invoice. Set Number - 810 Set Name - Invoice Functional Group - IN
810 - Invoice Set Number - 810 Set Name - Invoice Functional Group - IN This standard contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the context
Ultramar Ltd IMPLEMENTATION GUIDE
IMPLEMENTATION GUIDE for electronic data interchange November 2002 TABLE OF CONTENTS INTRODUCTION... 1 KEY CONTACTS... 1 EDI STANDARDS... 1 DOCUMENT PROCESSING FREQUENCY... 1 RESPONSIBILITY FOR COMMUNICATION
FedEx Ship Manager. FedEx Transborder Distribution FedEx International DirectDistribution Surface Solutions. User Guide
FedEx Ship Manager TM FedEx Transborder Distribution FedEx International DirectDistribution Surface Solutions User Guide Table of Contents FedEx Transborder Distribution FedEx International DirectDistribution
CVS/Caremark. Implementation Guide. 852 Product Activity Data Warehouse Movement. Version X12-4010
CVS/Caremark Implementation Guide 852 Product Activity Data Warehouse Movement Version X12-4010 852 Mapping Specifications v4010 i Table of Contents 852 Product Activity Data... 1 ST Transaction Set Header...
The EDI 810 specification is separated into logically distinct groups, which are composed of particular segment types.
EDI 810 File Format Direct Commerce (DCI) supports the EDI 810 format for uploaded invoice transactions. This document describes our implementation of the EDI 810 format for invoicing Carolinas Healthcare
RANDOM HOUSE. EDI Implementation Guide. 8 10 Invoice X12 Version 4010
RANDOM HOUSE EDI Implementation Guide 8 10 Invoice X12 Version 4010 Effective: 9-2-2006 Notes: The Random House EDI Implementation Guide for the 810 transaction documents only the segments and elements
DRS Defect Report Inbound 322. DRS Defect Report from Trading partner to Chassis.Com IB 322 Implementation Guide Prepared by Advent Inc for OCEMA
DRS Defect Report Inbound 322 DRS Defect Report from Trading partner to Chassis.Com IB 322 Implementation Guide Prepared by Advent Inc for OCEMA TABLE OF CONTENTS Revision History...3 DRS Defect Report
Transportation Requirements
Transportation Requirements DEFINITIONS Small Package: Less than 151 pounds per single package or less than 251 pounds per single shipment, up to 11 packages, and complies with carrier s requirements.
NEXCOM EDI 753 / 754 Supplier Shipping Instructions
NEXCOM EDI 753 / 754 Supplier Shipping Instructions Effective July 01, 2015 I. INTRODUCTION The Navy Exchange Service Command (NEXCOM) requires our suppliers to obtain routing for all purchase orders regardless
6.0 Transportation Routing Requirements
6.0 Transportation Routing Requirements 6.1 General Routing Requirements Overview: The Company s Transportation department ( Transportation ) will route all shipments when the Company is the responsible
WEST BEND TRANSIT AND SERVICE CO.
WEST BEND TRANSIT AND SERVICE CO. MEMORANDUM TARIFF WEBE 2 NAMING EXCEPTIONS TO S OF NATIONAL MOTOR FREIGHT CLASSIFICATION APPLICATION ON WISCONSIN, ILLINOIS, AND MINNESOTA TRAFFIC ONLY IN CONNECTION WITH
Mode of Shipment Carrier Payee/Terms Threshold Rules
VENDOR ROUTING GUIDE 2013 Mode of Shipment Carrier Payee/Terms Threshold Rules *PARCEL Inbound to Medline ***PARCEL Inbound to Medline Less Than Truckload Inbound to Medline PARCEL Direct to Customer Less
Streamline Accessorial Charges
Streamline Accessorial Charges Chargeable Item Charge Dray Related Accessorials Driver Assist (Load/Unload) $125 per hour Driver Count 1 (pallet) $75 Driver count 2 (pieces) $80 per hour Driver Clean (Sweep)
State of Tennessee Department of Revenue
State of Tennessee Department of Revenue PET 350 - Distributor Monthly Fuel Tax Return PET 368 - Blenders Return PET 372 - Petroleum Products Terminal Return PET 373 - Petroleum Products Transporter Return
997 Functional Acknowledgment
997 Functional Acknowledgment Version: 1.0 Draft Author: Margie Stewart Publication: 06/10/2013 Notes: Table of Contents 997 Functional Acknowledgment.......................................................................................
867 Product Transfer and Resale Report Ver/Rel 003060. Electronic Data I nterchange. Utility Industry Group Implementation Guideline.
Utility Industry Group Implementation Guideline for Electronic Data I nterchange TRANSACTION SET 867 Product Transfer and Resale Report Ver/Rel 003060 Acid Rain Allowance Transfer Reporting to the U.S.
TEXAS DEPARTMENT OF TRANSPORTATION GENERAL SERVICES DIVISION INTERSTATE TRANSPORTATION OF GOODS (FREIGHT) SERVICES PUBLICATION
TEXAS DEPARTMENT OF TRANSPORTATION GENERAL SERVICES DIVISION SPECIFICATION NO. TxDOT 9628622 INTERSTATE TRANSPORTATION OF GOODS (FREIGHT) SERVICES PUBLICATION This specification is a product of the Texas
820 ANSI X12 Version 003030
820 ANSI X12 Version 003030 Remittance Advice (Credit Card) FUNCTIONAL GROUP = RA This document is used by Medtronic to forward Credit Card payment information captured by the MAPP-PC system to the Automated
Orchard Supplier Operation Guidelines Domestic Shipping & Transportation Requirements
Orchard Supplier Operation Guidelines Domestic Shipping & Transportation Requirements Overview Routing Options Collect Routing Process The shipping and transportation routing instructions and requirements
Canada Customs emanifest Program Q & A
Canada Customs emanifest Program Q & A What is emanifest? emanifest is a Canada Border Services Agency (CBSA) initiative to ensure Canada Border processes are secure and compatible with North American
ShipRite On Demand Inland Motor Freight Management 24 / 7
Inland Motor Freight Management 24 / 7 S t r e a m l i n e s Y o u r : Quoting Ordering Scheduling Tracking Auditing Payment Table Of Contents Page Introduction 3 General Instructions 4 Log on to CTS Website
