X12 810 Freight Activity Invoice
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 of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary and established business and industry practice relative to the billing for goods and services provided.
- ~ Segment
- * Element
- > Component
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code to identify the type of information in the Authorization Information
- 00
- No Authorization Information Present (No Meaningful Information in I02)
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)
Code to identify the type of information in the Security Information
- 00
- No Security Information Present (No Meaningful Information in I04)
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)
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
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
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
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
Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer
- U
- U.S. EDI Community of ASC X12, TDCC, and UCS
This version number covers the interchange control segments
- 00401
- Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
A control number assigned by the interchange sender
Code sent by the sender to request an interchange acknowledgment (TA1)
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code to indicate whether data enclosed by this interchange envelope is test, production or information
- I
- Information
- P
- Production Data
- T
- Test Data
Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator
- >
- Component Element Separator
Functional Group Header
To indicate the beginning of a functional group and to provide control information
Code identifying a group of application related transaction sets
- IN
- Invoice Information (810,819)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission. Codes agreed to by trading partners
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)
Assigned number originated and maintained by the sender
Code used in conjunction with Data Element 480 to identify the issuer of the standard
- T
- Transportation Data Coordinating Committee (TDCC)
- X
- Accredited Standards Committee X12
Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed
- 004010
- Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997
Heading
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
Code uniquely identifying a Transaction Set
- The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
- 810
- Invoice
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning Segment for Invoice
To indicate the beginning of an invoice transaction set and transmit identifying numbers and dates
Date expressed as CCYYMMDD
- BIG01 is the invoice issue date.
File creation date for this file.
Identifying number assigned by issuer
The unique Reference Number within Syncada associated with the related document, generally the Buyer's document (order or eBill) when the extract type is paid, accrual, or cycled. This identifier may be used as a cross reference to be reconciled with the document information provided on the Syncada Invoice Summary or Detail file.
Identifying number for Purchase Order assigned by the orderer/purchaser
Syncada-created identifier that may be used to link all documents in this file together, since each document is presented within its own ST/SE loop.
Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction
This data element is used to present the 'processing group type.' It is used to differentiate the method by which documents are extracted and the file is organized. It is used in conjunction with the BIG08 as is defined by the requestor of the file. It is only presented when the BIG08 is not equal to 'SU' (indicating the exchange purpose = 'Advice').
Limited to:
BILL-TO ACCOUNT NUMBER
ORGANIZATION
Code identifying purpose of transaction set
This data element is used to present the 'exchange purpose.' It is used to differentiate the method by which documents are extracted as defined by the receiver of the file. As explained in the Syncada Notes section, all outbound buyers' files will be sent as originals.
- 9
- Not capable of taking action
- 22
- Information Copy
Syncada exchange purpose = 'Accrual'.
- 53
- Completion
Syncada exchange purpose = 'Cycled'.
- 54
- Approval
Syncada exchange purpose = 'Paid'.
- SU
- Status Update
Syncada exchange purpose = 'Advice'.
Identifying number assigned by issuer
- BIG10 indicates the consolidated invoice number. When BIG07 contains code CI, BIG10 is not used.
Syncada's account number for the party responsible for payment of the Summary Invoice presented on the Syncada website. It is only presented when BIG08 = '53', or when BIG05 = 'BILL-TO ACCOUNT NUMBER.
Note/Special Instruction
To transmit information in a free-form format, if necessary, for comment or special instruction
Code identifying the functional area or purpose for which the note applies
- ADD
- Additional Information
- APN
- Application Notes
- CAR
- Other Related Information
- DOI
- Outcome Description
- GEN
- Entire Transaction Set
- GPI
- General Product or Process Information
- INV
- Invoice Instruction
- LIN
- Line Item
- ORI
- Order Instructions
- OTH
- Other Instructions
- PCS
- Process Specification
- PDS
- Product Specification
- PMT
- Payment
A free-form description to clarify the related data elements and their content
EBILL Used when the method of sourcing the eBill line items is the service charge details on the eBill line items; occurs only when NTE01 = "ADD".
GL CODE Used when the method of sourcing the eBill line items is the G/L Accounting details associated with the eBill line items; occurs only when NTE01 = "CAR".
INVOICE Used when the document sourcing the service charge line items is an invoice; occurs only when NTE01 = "INV".
ORDER Used for paid, accrual, cycled or advice feeds when NTE01 = "LIN".
MERGED Used for paid, accrual, cycled, or advice feeds when NTE01 = "PCS".
DOCUMENT DETAIL Used when NTE01 = "PDS"
Burlington Stores Inc (Weekly Detail NS Cycled PPO) Used to help differentiate multiple feeds of otherwise identical construction when NTE01 = "OTH".
Currency
To specify the currency (dollars, pounds, francs, etc.) used in a transaction
Code identifying an organizational entity, a physical location, property or an individual
- ZZ
- Mutually Defined
Code (Standard ISO) for country in whose currency the charges are specified
Includes, but not restricted to:
USD - U.S. Dollar
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
- 1Z
- Financial Detail Code
- 4C
- Shipment Destination Code
- 06
- System Number
- 8X
- Transaction Category or Type
- ACC
- Status
- BM
- Bill of Lading Number
- CO
- Customer Order Number
- IV
- Seller's Invoice Number
- PO
- Purchase Order Number
- RE
- Release Number
- TN
- Transaction Reference Number
- ZZ
- Mutually Defined
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Syncada Document Type where REF01 = "8X".
Limited to:
ORDER
BOL
EBILL
INVOICE
PRO
FEE
SUPPLEMENTAL INVOICE
Limited to for REF01 = "06":
06 System Number
Syncada designated status for this document within the payment approval process where REF01 = "IZ":
Limited to:
PS Payment Settled
PI Payment Initiated
AE Audit Exception
AF Approval Final
CA Cancelled
DN Denied
HD Held
ON Unmatched Buyer
OP Approval Required
MA Matched Buyer
Identifier of the mode of Transportation (Transportation) where REF01 = "ZZ".
Included, but not limited to:
LT Less than truckload
M Motor freight
A Air freight
O Ocean
R Rail
HHG Household goods
A free-form description to clarify the related data elements and their content
Syncada Invoice Processing Model (Describes how orders and invoices interface with each other, or not and the party responsible for submitting the document when the order is not matched with the invoice) and REF01 = 8X. If REF02 = 'FEE' this value represents the fee description.
Limited to (for non-fee transactions):
MATCHING
BUYER SELF INVOICING
SELLER INVOICING
For REF01 = "06":
This is the System ID used at the Customer's site for the source system used to send the document to Syncada. Documents entered through the Syncada User Interface will inherit the System ID associated with the organization owning payment responsibilities for this document.
For REF01 = "IZ":
Financial Status Description as described in the REF02 immediately above.
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- BY
- Buying Party (Purchaser)
- PE
- Payee
- PR
- Payer
- RC
- Receiving Location
- SE
- Selling Party
- SF
- Ship From
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67)
- 1
- D-U-N-S Number, Dun & Bradstreet
- PI
- Payor Identification
- ZZ
- Mutually Defined
Code identifying a party or other code
- This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Code qualifying the Reference Identification
- 1J
- Facility ID Number
- 4M
- Special Move Reference Number
- BE
- Business Activity
- I5
- Invoice Identification
- LU
- Location Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Code identifying the major duty or responsibility of the person or group named
- CC
- Computer Systems Contact
- CN
- General Contact
- DC
- Delivery Contact
- OC
- Order Contact
- RE
- Receiving Contact
- SH
- Shipper Contact
- SU
- Supplier Contact
Code identifying the type of communication number
- TE
- Telephone
Complete communications number including country or area code when applicable
Code identifying the beginning of the terms period
- 3
- Invoice Date
- 4
- Specified Date
- 7
- Effective Date
- 11
- Completion And Acceptance Date
- 16
- Quarter Start Date
- ZZ
- Mutually Defined
Date when total invoice amount becomes due expressed in format CCYYMMDD
Limited to ITD02 = "11":
Date on which Syncada recognized the completion of the service as defined by the business rules associated with this document.
Limited to ITD02 = "16":
Start of period within which documents are selected for this output file.
Limited to ITD02 = "ZZ":
End of period within which documents are selected for this output file.
Code specifying type of date or time, or both date and time
- 002
- Delivery Requested
- 003
- Invoice
- 004
- Purchase Order
- 007
- Effective
- 011
- Shipped
- 013
- Terms Net Due
- 035
- Delivered
- 095
- Bill of Lading
- 097
- Transaction Creation
- 118
- Requested Pick-up
- COM
- Compliance
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)
Reference Identification
To transmit identifying information as specified by the Reference Identification Qualifier
Detail
Baseline Item Data (Invoice)
To specify the basic and most frequently used line item data for the invoice and related transactions
Alphanumeric characters assigned for differentiation within a transaction set
- IT101 is the purchase order line item identification.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
The actual 'unit of basis for measurement code' for a line item is written to the CTP05. A value of 'EA' is always written to this data element (IT103) to conform with the syntax requirements for the IT1 segment.
- EA
- Each
Price per unit of product, service, commodity, etc.
Total price for this line item (order/invoice line item or service charge line item). The sum of all the IT104 dollars for this document will equal the amount in the TDS01 for this document.
Goods and Services: if line item taxes apply to the product line, the amount of the product and the amount of the line item tax will be added together and presented in the IT104.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
If the value in the IT113 = 'Freight' this data element will be set to '400'.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- KF
- Item Type Number
Identifying number for a product or service
- EBILL
- EBill
Transportation only.
- FEE
- Fee
- FREIGHT
- Freight
Transportation documents only.
- PRODUCT
- Product
Goods and Services documents only.
- SERVICE CHARGE
- Service Charge
Applies to all documents because the Accessorial View of this product offering for Transportation documents supports this line type.
- TAX
- Tax
Goods and Services documents only.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- OT
- Internal Number
- ZZ
- Mutually Defined
Identifying number for a product or service
When IT114 = 'OT,' this date element presents the stopoff number presented in the associated N106 where that segment's N101 = 'RC.'
When IT114 = 'ZZ,' this date element presents the industry tied to this document (e.g. Household Goods).
Quantity
To specify quantity information
- The QTY segment is used to specify a quantity of units which are expected as payments, e.g., trade-ins or returns.
Code specifying the type of quantity
- 12
- Ship Notice Quantity
- 38
- Original Quantity
- 39
- Shipped Quantity
- 63
- On Order Quantity
- OC
- Order Count
- T5
- Total Number of Units
- TO
- Total
Free-form information
- QTY04 is used when the quantity is non-numeric.
Tax Information
To specify tax information
Percentage expressed as a decimal
- TXI03 is the tax percent expressed as a decimal.
Code identifying the source of the data used in tax jurisdiction code
Code indicating the relationship between entities
- TXI07 is a code indicating the relationship of the price or amount to the associated segment.
- A
- Add
Dollar basis to be used in the percent calculation of the allowance, charge or tax
Number assigned to a purchaser (buyer, orderer) by a taxing jurisdiction (state, county, etc.); often called a tax exemption number or certificate number
Alphanumeric characters assigned for differentiation within a transaction set
Pricing Information
To specify pricing information
Data element 355, as used twice in this segment, refers to Goods and Services documents only. The unit of measure information for Transportation documents is presented in the REF 'Rated Unit of Measure' segment. See that segment for details.
This represents data from the Invoice - Goods and Services
Example (single quantity, no discount): CTPINV10.005EA50.00
Example (single quantity with discount): CTPINV10.005EADIS0.945.00
Example (multiple quantity): CTPINV1.005PD|||DA||1050.00
Example (multiple quantity with discount): CTPINV1.005PD|||DA||10DIS0.950.00
Code identifying pricing specification
- ALT
- Alternate Price
- INV
- Invoice Billing Price
- OPP
- Original Purchase Order Price
Price per unit of product, service, commodity, etc.
- See Figures Appendix for an example detailing the use of CTP03 and CTP04.
- See Figures Appendix for an example detailing the use of CTP03, CTP04 and CTP07.
Numeric value of quantity
If two quantities are used to calculate the price, this represents the first of the two quantities. If only one quantity is used, it is found here.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- ZZ
- Mutually Defined
Code indicating the type of price multiplier
- DIS
- Discount Multiplier
Value to be used as a multiplier to obtain a new value
- CTP07 is a multiplier factor to arrive at a final discounted price. A multiplier of .90 would be the factor if a 10% discount is given.
Product/Item Description
To describe a product or process in coded or free-form format
Code indicating the format of a description
- If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
A free-form description to clarify the related data elements and their content
Code qualifying the Reference Identification
- 6R
- Provider Control Number
- 9F
- Referral Number
- 19
- Division Identifier
- CT
- Contract Number
- DO
- Delivery Order Number
- FJ
- Line Item Control Number
- L1
- Letters or Notes
- PG
- Product Group
- PO
- Purchase Order Number
- ZZ
- Mutually Defined
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Limited to when REF01 = "ZZ":
INF Informational item
LOT Lot based item
MRC Monthly-recurring charge
NRC Non-recurring charge
OTC One-time charge
USG Usage based line item
Service, Promotion, Allowance, or Charge Information
To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge
Code which indicates an allowance or charge for the service specified
- If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.
- S
- Service
Code identifying the service, promotion, allowance, or charge
Code identifying the agency assigning the code values
- ZZ
- Mutually Defined
Agency maintained code identifying the service, promotion, allowance, or charge
- SAC04 may be used to uniquely identify the service, promotion, allowance, or charge. In addition, it may be used in conjunction to further the code in SAC02.
This element represents the service charge code stored in Syncada for the line item referenced in the IT101.
This element is used for Transportation line items only.
Monetary amount
- SAC05 is the total amount for the service, promotion, allowance, or charge.
- If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence.
Code indicating on what basis allowance or charge percent is calculated
Rate expressed in the standard monetary denomination for the currency specified
- SAC08 is the allowance or charge rate per unit.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- DO
- Dollars, U.S.
Numeric value of quantity
- SAC10 and SAC11 is the quantity basis when the allowance or charge quantity is different from the purchase order or invoice quantity.
- SAC10 and SAC11 used together indicate a quantity range, which could be a dollar amount, that is applicable to service, promotion, allowance, or charge.
- In some business applications, it is necessary to advise the trading partner of the actual dollar amount that a particular allowance, charge, or promotion was based on to reduce ambiguity. This amount is commonly referred to as "Dollar Basis Amount". It is represented in the SAC segment in SAC10 using the qualifier "DO" - Dollars in SAC09.
A free-form description to clarify the related data elements and their content
This represents the description of a service charge.
This element is used for Transportation line items only.
Tax Information
To specify tax information
Percentage expressed as a decimal
- TXI03 is the tax percent expressed as a decimal.
Code identifying the source of the data used in tax jurisdiction code
Code indicating the relationship between entities
- TXI07 is a code indicating the relationship of the price or amount to the associated segment.
- A
- Add
Number assigned to a purchaser (buyer, orderer) by a taxing jurisdiction (state, county, etc.); often called a tax exemption number or certificate number
Type of Financial Accounting Data
To specify the organization controlling the content of the accounting citation, and the purpose associated with the accounting citation
1 FA101 Identifies the organization controlling the assignment of financial accounting information.
2 FA102 Identifies the purpose of the accounting allowance or charge information.
Comments: This segment is not used for a service charge line item for a Transportation document (i.e. IT113 = 'Service Charge Line Item') because Syncada does not associate general ledger account numbers with service charges.
Code identifying the agency assigning the code values
- FA101 Identifies the organization controlling the assignment of financial accounting information.
1 FA101 Identifies the organization controlling the assignment of financial accounting information.
2 FA102 Identifies the purpose of the accounting allowance or charge information.
Comments: This segment is not used for a service charge line item for a Transportation document (i.e. IT113 = 'Service Charge Line Item') because Syncada does not associate general ledger account numbers with service charges.
- ZZ
- Mutually Defined
Codes identifying details relating to a reporting breakdown structure tree
This element is taken from the segment qualifier for the g/l account number assigned to this line item. See the FA202 description for the use of an '84' in this data element.
- 84
- Total Direct Costs
- ZZ
- Mutually Defined
Code representing financial accounting information
This element represents the g/l account number related to the segment qualifier in the FA201. When '84' is used in the FA201, the FA202 represents the total dollars to be charged to the g/l account number in the previous FA2 segment (see example below). For Transportation documents, this total amount represents the sum of this g/l account
number's line haul charges plus this g/l account number's pro-rata allocation of the sum of all the service charge dollars for this document. For both Goods and Services and Transportation documents, the sum of all the FA202 dollars (where FA201 = '84') for this document will equal the amount in the TDS01 for this document. See comments section above noting that this segment is not used for service charge line items on Transportation documents.
Summary
Total Monetary Value Summary
To specify the total invoice discounts and amounts
Monetary amount
- TDS01 is the total amount of invoice (including charges, less allowances) before terms discount (if discount is applicable).
Sum of all line items/service charges for this document (i.e. all information between the ST and SE loops.
Tax Information
To specify tax information
Percentage expressed as a decimal
- TXI03 is the tax percent expressed as a decimal.
Code identifying the source of the data used in tax jurisdiction code
Code indicating the relationship between entities
- TXI07 is a code indicating the relationship of the price or amount to the associated segment.
Dollar basis to be used in the percent calculation of the allowance, charge or tax
Number assigned to a purchaser (buyer, orderer) by a taxing jurisdiction (state, county, etc.); often called a tax exemption number or certificate number
Alphanumeric characters assigned for differentiation within a transaction set
Monetary Amount
To indicate the total monetary amount
This amount represents the total of all 810 invoices created for this file creation request.
Monetary amount
Sum of all line items/service charges across all documents in this file. In other words, the sum of all TDS01s. This segment is used for balancing purposes when all the documents in the file are tied back against a pre-determined total.
Code indicating whether amount is a credit or debit
- C
- Credit
- D
- Debit
Transaction Totals
To transmit a hash total for a specific element in the transaction set
- Number of line items (CTT01) is the accumulation of the number of IT1 segments.
If used, hash total (CTT02) is the sum of the value of quantities invoiced (IT102) for each IT1 segment.
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Total number of segments included in a transaction set including ST and SE segments
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Functional Group Trailer
To indicate the end of a functional group and to provide control information
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element
Assigned number originated and maintained by the sender
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
EDI 810 US Bank Freight Invoice Sample File
BIG*20220913*1711798286**201675031*BILL-TO-ACCOUNT NUMBER***53**248872
NTE*PCS*MERGED
NTE*LIN*ORDER
NTE*INV*INVOICE
NTE*CAR*GL CODE
NTE*PDS*Document Detail Accessorial View
NTE*OTH*Burlington Stores Inc (Weekly Detail NS Cycled PPO) Out-Of-Network
CUR*ZZ*USD
REF*BM*CS0000404831
REF*IV*BL356591001*1711793641
REF*8X*PRO*MATCHING
REF*06*42870
REF*4C*INBOUND
REF*1Z*PI*Payment Initiated
REF*ACC*DV
REF*ZZ*TL
N1*PR*Burlington Stores Inc L0*PI*NOT PROVIDED
N3*4287 ROUTE 130 SOUTH
N4*EDGEWATER PARK*NJ*08010-301
PER*CN*Brad Helgesen*TE*1-609-3877800
N1*PE*PowerTrack*1*071791990
N3*200 So 6th Street
N4*Minneapolis*MN*55402*USA
REF*I5*24887203271
PER*CN*PowerTrack Help Desk*TE*(800)-417-1844
N1*BY*Burlington Stores USA*PI*BRLNGTNUSA
N3*4287 Route 130 South
N4*Edgewater Park*NJ*08010*USA
PER*CN*Brad Helgesen*TE*1-609-3877800
N1*SE*OON Jay-Dee Fast Delivery*ZZ*JDFD
N3*480 Duncan Ave
N4*Jersey City*NJ*07306*USA
PER*CN*Bibi Dalana*TE*1-201-4346338
N1*SF*ISAAC MORRIS
N3*1000 Riverside Dr
N4*Keasbey*NJ*08832-1218*USA
N1*ST*BURLINGTON COAT DC#9
N3*4287 Route 130
N4*Edgewater Park*NJ*08010-3015*USA
ITD**ZZ****20221121
ITD**4****20221122
ITD**11****20220908
ITD**3****20221122
ITD**7****20221128
DTM*011*20220908
DTM*035*20220908*00010000
DTM*003*20220906
DTM*095*20220913
DTM*097*20220913
N9*ZZ*System Generated
MSG*ET:RV45;MT:;BU:;SB:NO;SI:;
IT1*1*1*EA*27.79******VN*400*KF*FREIGHT*OT*1
QTY*T5**ZZ>>687.12*LB
QTY*39**ZZ>>20.68*CTN
QTY*12**ZZ>>108.53*MP
QTY*TO**ZZ>>10926.98*LB
CTP**INV*.0404*687.1228*ZZ***27.79
REF*6R*439811401
REF*9F*439811405
REF*DO*_40397839
REF*ZZ*6
FA1*ZZ
FA2*84*36.41
FA2*ZZ*99999999
IT1*2*1*EA*91.78******VN*400*KF*FREIGHT*OT*1
QTY*T5**ZZ>>2269.05*LB
QTY*39**ZZ>>68.31*CTN
QTY*12**ZZ>>358.41*MP
QTY*TO**ZZ>>10926.98*LB
CTP**INV*.0404*2269.0582*ZZ***91.78
REF*6R*439811402
REF*9F*439811405
REF*DO*_40397839
REF*ZZ*6
FA1*ZZ
FA2*84*120.28
FA2*ZZ*99999999
IT1*3*1*EA*45.22******VN*400*KF*FREIGHT*OT*1
QTY*T5**ZZ>>1118.03*LB
QTY*39**ZZ>>33.66*CTN
QTY*12**ZZ>>176.6*MP
QTY*TO**ZZ>>10926.98*LB
CTP**INV*.0404*1118.0304*ZZ***45.22
REF*6R*439811403
REF*9F*439811405
REF*DO*_40397839
REF*ZZ*6
FA1*ZZ
FA2*84*59.26
FA2*ZZ*99999999
IT1*4*1*EA*159.7******VN*400*KF*FREIGHT*OT*1
QTY*T5**ZZ>>3948.04*LB
QTY*39**ZZ>>118.87*CTN
QTY*12**ZZ>>623.62*MP
QTY*TO**ZZ>>10926.98*LB
CTP**INV*.0404*3948.0448*ZZ***159.7
REF*6R*439811404
REF*9F*439811405
REF*DO*_40397839
REF*ZZ*6
FA1*ZZ
FA2*84*209.28
FA2*ZZ*99999999
IT1*5*1*EA*117.51******VN*400*KF*FREIGHT*OT*1
QTY*T5**ZZ>>2904.74*LB
QTY*39**ZZ>>87.45*CTN
QTY*12**ZZ>>458.82*MP
QTY*TO**ZZ>>10926.98*LB
CTP**INV*.0405*2904.7438*ZZ***117.51
REF*6R*439811405
REF*9F*439811405
REF*DO*_40397839
REF*ZZ*6
FA1*ZZ
FA2*84*154.01
FA2*ZZ*99999999
IT1*1*1*EA*40********KF*SERVICE CHARGE
QTY*39**ZZ>>1*EA
CTP**INV*40*1*ZZ***40
SAC*S**ZZ*DEP*****DO*40*****Detention with Power Unit
IT1*2*1*EA*97.24********KF*SERVICE CHARGE
QTY*39**ZZ>>22*OR
CTP**INV*97.24*22*ZZ***97.24
SAC*S**ZZ*405*****DO*97.24*****Fuel Surcharge
TDS*57924
AMT*2*1052085.94*D
CTT*7
SE*129*0001
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.