X12 810 Drop Ship 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
- None included
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
Beginning Segment for Invoice
To indicate the beginning of an invoice transaction set and transmit identifying numbers and dates
Starting in Dec 2017, Target will start phasing in a new PO format. The new format removes the 4 digit department number prefix and the purchase order number will be moving from 7 digits to 11 digits. No changes are being made to the location number. During this transition, your company needs to be able to receive both PO formats, as both may be received during transition. The same PO format received from Target will need to be returned on all EDI related documents for that PO to ensure no business interruption.
New PO Format:
12345678909-1234
Sample BIG Segment:
BIG200103061234567**0123-1234567-1234
NOTE: DSD vendors should add leading zeroes to the PO number to make it 7 digits.
New Purchase Order Number Format:
BIG200103061234567**12345678909-1234
Date expressed as CCYYMMDD
- BIG01 is the invoice issue date.
Identifying number assigned by issuer
Invoice numbers must not be more than 19 characters long. Invoice numbers may contain alphas but no special characters. Alpha characters must be in upper case.
Identifying number for Purchase Order assigned by the orderer/purchaser
This field is required.
Send the same number here that was received on the 850 PO in element BEG03. The purchase order number will be formatted either as SSSS-PPPPPPP-LLLL (17 characters) or SSSS-PPPPPPP (12 characters).
SSSS = Source code, PPPPPPP = PO number, LLLL = Location ID Code
New Purchase Order Number Format:
12345678901-1234
Code specifying the type of transaction
- BIG07 is used only to further define the type of invoice when needed.
The "DO" code is required for Drop Ship to Guest Home. N1, N3 and N4 are also required for this situation.
**All other invoices (credit, display, samples, freight only, pallets, etc.) must be on paper and mailed to the appropriate area.
- DO
- Drop Shipment Invoice
Note/Special Instruction
To transmit information in a free-form format, if necessary, for comment or special instruction
Example: NTECERFree Form Text
Code identifying the functional area or purpose for which the note applies
- CER
- Certification Narrative
Any notes associated with the certification involved.
Reference Identification Department Number
To specify identifying information
Two occurrences must be sent, where REF01 = IA & DP.
Example: REFDP023
Code qualifying the Reference Identification
- DP
- Department Number
Reference Identification Internal Vendor Number
To specify identifying information
Two occurrences must be sent, where REF01 = IA & DP.
Example: REFIA1234567
Code qualifying the Reference Identification
- IA
- Internal Vendor Number
Reference Identification Promotion/Deal Number
To specify identifying information
Send only if received on the PO.
Example: REFPD9876543210
Code qualifying the Reference Identification
- PD
- Promotion/Deal Number
Name
To identify a party by type of organization, name, and code
One occurrence of the N1 must be sent, where N101 = BY or BS (Common Predistro).
Examples:
N1BY**920551
N1BY**921001
N1BS**923902 (Predistro - packed and marked for store, but shipped to DC)
Code identifying an organizational entity, a physical location, property or an individual
- BS
- Bill and Ship To
- BY
- Buying Party (Purchaser)
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
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.
A list of Target location codes may be found on the Partners Online website.
Address Information
To specify the location of the named party
Send this segment when the invoice is for a Drop Ship to the Guest's home.
Example: N3*Main St.
Geographic Location
To specify the geographic place of the named party
Send this segment when the invoice is for a Drop Ship to the Guest's home.
Send only if sending the N3.
Example: N4HometownMN*55402
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.
Name
To identify a party by type of organization, name, and code
ST used for Drop Ship to Guest Home or when CAD01 = C.
Example: N1ST**929998 (Direct Ship to Guest)
Code identifying an organizational entity, a physical location, property or an individual
- SF
- Ship From
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67)
- 91
- Assigned by Seller or Seller's Agent
Used when N101 = SF.
- 92
- Assigned by Buyer or Buyer's Agent
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.
A list of Target location codes may be found on the Partners Online website.
Address Information
To specify the location of the named party
Send this segment when the invoice is for a Drop Ship to the Guest's home.
Example: N3*Main St.
Geographic Location
To specify the geographic place of the named party
Send this segment when the invoice is for a Drop Ship to the Guest's home.
Send only if sending the N3.
Example: N4HometownMN*55402
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.
Terms of Sale/Deferred Terms of Sale
To specify terms of sale
For Target Store only:
ITD012***30 (with no discount, use elements 01, 02 and 07)
ITD02*28**34 (with discount, use elements 01, 02, 03 and 05)
Code identifying type of payment terms
- 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.
- 01
- Basic
- 02
- End of Month (EOM)
When this code is used, ITD07 should NOT be sent.
- 14
- Previously agreed upon
Not used by Target at this time.
Code identifying the beginning of the terms period
- 2
- Delivery Date
- 3
- Invoice Date
Terms discount percentage, expressed as a percent, available to the purchaser if an invoice is paid on or before the Terms Discount Due Date
Number of days in the terms discount period by which payment is due if terms discount is earned
Number of days until total invoice amount is due (discount not applicable)
Date/Time Reference
To specify pertinent dates and times
Example: DTM01120020205
Reference Identification
To transmit identifying information as specified by the Reference Identification Qualifier
This segment used only when the MSG segment is present.
Example: N9ZZPACA
Code qualifying the Reference Identification
- ZZ
- Mutually Defined
Message Text
To provide a free-form format that allows the transmission of text information
This segment is NOT required by Target. If the N9 loop is included, then this segment must be sent.
The MSG segment is used to send the Perishable Agricultural Commodities Act (PACA) "trust statement". One MSG segment will be sent for each line of text as follows:
MSGThe perishable agricultural commodities listed on this
MSGinvoice are sold subject to the statutory trust authorized
MSGby Section 5(c) of the Perishable Agricultural Commodities
MSGAct, 1930 (7 U.S.C. 4993(c)). The seller of these
MSGcommodities retains a trust claim over these commodities,
MSGall inventories of food or other products derived from
MGSthese commodities, and any receivables or proceeds from
MSGthe sale of these commodities until full payment is
MSG*received.
Free-form message text
MSGThe perishable agricultural commodities listed on this
MSGinvoice are sold subject to the statutory trust authorized
MSGby Section 5(c) of the Perishable Agricultural Commodities
MSGAct, 1930 (7 U.S.C. 4993(c)). The seller of these
MSGcommodities retains a trust claim over these commodities,
MSGall inventories of food or other products derived from
MGSthese commodities, and any receivables or proceeds from
MSGthe sale of these commodities until full payment is
MSG*received.
Detail
Baseline Item Data (Invoice)
To specify the basic and most frequently used line item data for the invoice and related transactions
Note: IN will be used as an item identifier for Target in the future. When this item identifier is sent by Target, your system must be capable of sending it back on inbound EDI documents.
When sending a substitution (must be pre-approved by the Buyer) please follow these instructions: Send the substitute item info in the IT1 segment. The original item should not be included in the 810.
Example: IT150EA1.49CB058020714UP*123456789012
Alphanumeric characters assigned for differentiation within a transaction set
- IT101 is the purchase order line item identification.
Number of units invoiced (supplier units)
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
The UOM should match the UOM received on the PO. The value in the ISS02 must be the same as this value.
- CA
- Case
- EA
- Each
- LB
- Pound
Price per unit of product, service, commodity, etc.
Target only reads out five places after the decimal point, sending more than 5 places can result in a fatal error.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IT106 through IT125 provide for ten different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
Either a CB or UP or UI or EN must be sent.
- CB
- Buyer's Catalog Number
- EN
- European Article Number (EAN) (2-5-5-1)
- EO
- EAN/UCC - 8
- IN
- Buyer's Item Number
Target Corporation Item Number (TCIN)
- UI
- U.P.C. Consumer Package Code (1-5-5)
To be used by direct to store delivery beverage vendors only.
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- CB
- Buyer's Catalog Number
- EN
- European Article Number (EAN) (2-5-5-1)
- EO
- EAN/UCC - 8
- IN
- Buyer's Item Number
Target Corporation Item Number (TCIN)
- UI
- U.P.C. Consumer Package Code (1-5-5)
To be used by direct to store delivery beverage vendors only.
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- CB
- Buyer's Catalog Number
- EN
- European Article Number (EAN) (2-5-5-1)
- EO
- EAN/UCC - 8
- IN
- Buyer's Item Number
Target Corporation Item Number (TCIN)
- UI
- U.P.C. Consumer Package Code (1-5-5)
To be used by direct to store delivery beverage vendors only.
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Product/Item Description
To describe a product or process in coded or free-form format
Description of Item. This helps better define your product. Please send this segment if DPCI/TCIN doesn't fully describe your product.
Example: PIDF08***BLUE XL
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.
- F
- Free-form
Code identifying the general class of a product or process characteristic
- 08
- Product
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
Examples:
PO412 (no inner packs)
PO46*******************4 (inner packs)
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
Example: SACAC310***1542
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.
- A
- Allowance
- C
- Charge
Code identifying the service, promotion, allowance, or charge
Most common codes:
B950 Damaged Merchandise
C310 Discount
D170 Free Goods
D270 Fuel Surcharge
F800 Promotional Allowance
H000 Special Allowance
H090 Special Handling
H700 Tax - Local Tax (CRV - Container Redemption (bottle deposit))
H750 State and Local Tax
Code identifying the agency assigning the code values
- VI
- Voluntary Inter-Industry Commerce Standard (VICS) EDI
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.
- HA
- Hanger Service
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.
Monetary amount must be 10 cents or greater. Anything less than 10 cents will be rejected and will not feed into Target's application system. Two decimal places are implied, do not send a decimal point.
Code indicating on what basis allowance or charge percent is calculated
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- Each
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.
When SAC02 = D170, this data element is required and should contain the quantity of free goods. SAC09 should contain the unit of measure of the free goods.
Code indicating method of handling for an allowance or charge
- 02
- Off Invoice
- 06
- Charge to be Paid by Customer
Summary
Total Monetary Value Summary
To specify the total invoice discounts and amounts
2 Decimal places implied - do NOT send a decimal point in the TDS01 or 02
Example: TDS*53000
Monetary amount
- TDS01 is the total amount of invoice (including charges, less allowances) before terms discount (if discount is applicable).
Total amount of invoice (including charges, less allowances) before terms discount.
Monetary amount
- TDS02 indicates the amount upon which the terms discount amount is calculated.
- TDS02 is required if the dollar value subject to discount is not equal to the dollar value of TDS01.
Total amount of merchandise. If you offer a discount on gross amount before allowances, this field is required. Otherwise it is not needed.
Carrier Detail
To specify transportation details for the transaction
Transportation Method Type // CAD01 // CAD07
Consolidation // C // BM Bill of Lading #
TL or LTL // M // BM Bill of Lading #
Private Parcel // U // CN Carrier Ref.#
Direct Store Delivery // P // CN Carrier Ref.#
Examples:
CADMRDWYBM12345678901234567
CADUUPSN*UPSCN123456
CADPSELFCN*123456 (Direct Store Delivery vendors may use "SELF" in the CAD04, if the vendor does not have a SCAC code assigned by the National Freight Traffic Association (NFTA))
Code specifying the method or type of transportation for the shipment
- C
- Consolidation
Used for domestic consolidation.
- M
- Motor (Common Carrier)
Used for larger quantity shipments.
- P
- Private Carrier
Used for Direct Store Delivery (DSD).
- U
- Private Parcel Service
Used for small package or small quantities. ONLY UPSN or FDEG may use this.
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
Code qualifying the Reference Identification
A value is not required in the CAD07 for DSD vendors.
- BM
- Bill of Lading Number
Required when shipping via motor carrier or consolidation.
- CN
- Carrier's Reference Number (PRO/Invoice)
Required when shipping parcel package shipments.
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
Example: SACCD2401500*02Freight 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.
- A
- Allowance
- C
- Charge
Code identifying the service, promotion, allowance, or charge
Most common codes:
B950 Damaged Merchandise
C310 Discount
D170 Free Goods
D270 Fuel Surcharge
F800 Promotional Allowance
H000 Special Allowance
H090 Special Handling
H700 Tax - Local Tax (CRV - Container Redemption (bottle deposit))
H750 State and Local Tax
Code identifying the agency assigning the code values
- VI
- Voluntary Inter-Industry Commerce Standard (VICS) EDI
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.
- HA
- Hanger Service
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.
Monetary amount must be 10 cents or greater. Anything less than 10 cents will be rejected and will not feed into Target's application system. Two decimal places are implied, do not send a decimal point.
Code indicating on what basis allowance or charge percent is calculated
- 3
- Discount/Gross
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.
Code indicating method of handling for an allowance or charge
- 02
- Off Invoice
- 06
- Charge to be Paid by Customer
Invoice Shipment Summary
To specify summary details of total items shipped in terms of quantity, weight, and volume
Target requires at least one occurrence of the ISS with the total number of eaches, pounds or cases (same UOM as found on the PO). If there are multiple units of measure in the invoice, an ISS should be sent with the total number of each unit of measure.
Only ISS01 & ISS02 are mandatory. ISS03 & ISS04 may be sent.
Examples:
ISS45EA
ISS60EA3LB
When multiple units of measure occur in the invoice, send multiple ISS segments as in the following example:
ISS40EA
ISS10CA
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- CA
- Case
- CT
- Carton
- EA
- Each
- LB
- Pound
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.
Example: CTT*25
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
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
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
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.