Core-Mark 810 Invoice v5010
Core-Mark 810 Invoice v5010
810 Invoice
Functional Group= IN
Purpose: This X12 Transaction Set 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.
General Usage:
Invoice (810)– Core-Mark is requiring suppliers to provide electronic Invoices for all orders
shipped. This information will be used to automate the receipt of invoices, use the three way
matching functionality against the Inventory receipt and Purchase order and apply the invoice
into their accounts payable system for timely payments to the suppliers. The suppliers are to
create an invoice per single PO.
Heading:
Pos Id Segment Name Req Max Use Repeat Notes Usage
0100 ST Transaction Set Header M 1 Must use
0200 BIG Beginning Segment for M 1 Must use
Invoice
0500 REF Reference Information M 4 Must use
0600 PER Administrative O 1 Used
Communications Contact
LOOP ID - N1 3
0700 N1 Party Identification M 1 Must use
0800 N2 Additional Name O 1 Used
Information
0900 N3 Party Location M 2 Must use
1000 N4 Geographic Location M 1 Must use
1300 ITD Terms of Sale/Deferred O 1 Used
Terms of Sale
1400 DTM Date/Time Reference M 2 Must use
1500 FOB F.O.B. Related Instructions M 1 Must use
LOOP ID - N9 1
2400 N9 Extended Reference C 1 Used
Information
2500 MSG Message Text C 1 Used
Detail:
Pos Id Segment Name Req Max Use Repeat Notes Usage
LOOP ID - IT1 200000
0100 IT1 Baseline Item Data M 1 Must use
(Invoice)
0300 IT3 Additional Item Data C 1 Used
0500 CTP Pricing Information M 1 Must use
LOOP ID - PID 2
0600 PID Product/Item Description M 1 Must use
1000 PO4 Item Physical Details O 1 Used
Coremark_810_Invoice_v5010.ecs 1 X12V5010
4/30/2024 Invoice - 810
Summary:
Pos Id Segment Name Req Max Use Repeat Notes Usage
0100 TDS Total Monetary Value M 1 Must use
Summary
0200 TXI Tax Information O 10 Used
LOOP ID - SAC 25
0400 SAC Service, Promotion, M 1 Must use
Allowance, or Charge
Information
LOOP ID - ISS 1
0600 ISS Invoice Shipment Summary M 1 Must use
0700 CTT Transaction Totals O 1 N3/0700 Used
0800 SE Transaction Set Trailer M 1 Must use
Notes:
3/0700 Number of line items (CTT01) is the accumulation of the number of IT1 segments. If used CTT02 is the
hash total of the quantities invoiced (IT102) for each IT1 segment.
Coremark_810_Invoice_v5010.ecs 2 X12V5010
4/30/2024 Invoice - 810
Element Summary:
Ref Id Element Name Req Type Min/Max Usage
ST01 143 Transaction Set Identifier Code M ID 3/3 Must use
Description: Identifying control number that must be unique within the transaction set
functional group assigned by the originator for a transaction set
Semantics:
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).
2. 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. When
used, this implementation convention reference takes precedence over the implementation reference
specified in the GS08.
Coremark_810_Invoice_v5010.ecs 3 X12V5010
4/30/2024 Invoice - 810
Element Summary:
Ref Id Element Name Req Type Min/Max Usage
BIG01 373 Date M DT 8/8 Must use
Description: Date expressed as CCYYMMDD where CC represents the first two digits of
the calendar year
User Note 1: Invoice Date
Description: Date expressed as CCYYMMDD where CC represents the first two digits of
the calendar year
User Note 1: Purchase Order Date
Semantics:
1. BIG01 is the invoice issue date.
2. BIG03 is the date assigned by the purchaser to purchase order.
3. BIG10 is the consolidated invoice number associated with the invoice identified in BIG02. When BIG07
contains code CI (Consolidated Invoice), BIG02 will contain the consolidated invoice number and BIG10 is not
used.
Comments:
1. BIG07 is used only to further define the type of invoice when needed.
Coremark_810_Invoice_v5010.ecs 4 X12V5010
4/30/2024 Invoice - 810
User Note 1:
One of Bill of Lading Number (REF01 = BM), CarrierProNumber (REF01 = CN) or Tracking Number (2I) is
recommended. (Both a carrier pro number and tracking number should not be sent).
Element Summary:
Ref Id Element Name Req Type Min/Max Usage
REF01 128 Reference Identification Qualifier M ID 2/3 Must use
Syntax Rules:
1. R0203 - At least one of REF02 or REF03 is required.
Semantics:
1. REF04 contains data relating to the value cited in REF02.
Coremark_810_Invoice_v5010.ecs 5 X12V5010
4/30/2024 Invoice - 810
Element Summary:
Ref Id Element Name Req Type Min/Max Usage
PER01 366 Contact Function Code M ID 2/2 Must use
Description: Code identifying the major duty or responsibility of the person or group
named
Syntax Rules:
1. P0304 - If either PER03 or PER04 is present, then the other is required.
2. P0506 - If either PER05 or PER06 is present, then the other is required.
3. P0708 - If either PER07 or PER08 is present, then the other is required.
Coremark_810_Invoice_v5010.ecs 6 X12V5010
4/30/2024 Invoice - 810
Loop Summary:
Pos Id Segment Name Req Max Use Repeat Usage
0700 N1 Party Identification M 1 Must use
0800 N2 Additional Name Information O 1 Used
0900 N3 Party Location M 2 Must use
1000 N4 Geographic Location M 1 Must use
Coremark_810_Invoice_v5010.ecs 7 X12V5010
4/30/2024 Invoice - 810
User Note 1:
Only one repetition of each N101 qualifier is allowed.
Element Summary:
Ref Id Element Name Req Type Min/Max Usage
N101 98 Entity Identifier Code M ID 2/3 Must use
Description: Code designating the system/method of code structure used for Identification
Code (67)
User Note 1: Return if provided on the Purchase Order
Coremark_810_Invoice_v5010.ecs 8 X12V5010
4/30/2024 Invoice - 810
Syntax Rules:
1. R0203 - At least one of N102 or N103 is required.
2. P0304 - If either N103 or N104 is present, then the other is required.
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.
Coremark_810_Invoice_v5010.ecs 9 X12V5010
4/30/2024 Invoice - 810
Element Summary:
Ref Id Element Name Req Type Min/Max Usage
N201 93 Name M AN 1/60 Must use
Coremark_810_Invoice_v5010.ecs 10 X12V5010
4/30/2024 Invoice - 810
Element Summary:
Ref Id Element Name Req Type Min/Max Usage
N301 166 Address Information M AN 1/55 Must use
Coremark_810_Invoice_v5010.ecs 11 X12V5010
4/30/2024 Invoice - 810
Element Summary:
Ref Id Element Name Req Type Min/Max Usage
N401 19 City Name M AN 2/30 Must use
Description: Code defining international postal zone code excluding punctuation and
blanks (zip code for United States)
N404 26 Country Code O ID 2/3 Used
Syntax Rules:
1. E0207 - Only one of N402 or N407 may be present.
2. C0605 - If N406 is present, then N405 is required.
3. C0704 - If N407 is present, then N404 is required.
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.
Coremark_810_Invoice_v5010.ecs 12 X12V5010
4/30/2024 Invoice - 810
Element Summary:
Ref Id Element Name Req Type Min/Max Usage
ITD01 336 Terms Type Code O ID 2/2 Used
Description: Number of days in the terms discount period by which payment is due if
terms discount is earned
User Note 1: If either ITD03 or ITD08 is present, ITD05 is required
Description: Date when total invoice amount becomes due expressed in format
CCYYMMDD where CC represents the first two digits of the calendar year
ITD07 386 Terms Net Days O N0 1/3 Used
Description: Number of days until total invoice amount is due (discount not applicable)
Description: A free-form description to clarify the related data elements and their content
Coremark_810_Invoice_v5010.ecs 13 X12V5010
4/30/2024 Invoice - 810
Syntax Rules:
1. L03040513 - If ITD03 is present, then at least one of ITD04, ITD05 or ITD13 is required.
2. L08040513 - If ITD08 is present, then at least one of ITD04, ITD05 or ITD13 is required.
3. L091011 - If ITD09 is present, then at least one of ITD10 or ITD11 is required.
Semantics:
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.
Coremark_810_Invoice_v5010.ecs 14 X12V5010
4/30/2024 Invoice - 810
Element Summary:
Ref Id Element Name Req Type Min/Max Usage
DTM01 374 Date/Time Qualifier M ID 3/3 Must use
Description: Code specifying type of date or time, or both date and time
Description: Date expressed as CCYYMMDD where CC represents the first two digits of
the calendar year
Syntax Rules:
1. R020305 - At least one of DTM02, DTM03 or DTM05 is required.
2. C0403 - If DTM04 is present, then DTM03 is required.
3. P0506 - If either DTM05 or DTM06 is present, then the other is required.
Coremark_810_Invoice_v5010.ecs 15 X12V5010
4/30/2024 Invoice - 810
Element Summary:
Ref Id Element Name Req Type Min/Max Usage
FOB01 146 Shipment Method of Payment M ID 2/2 Must use
Description: A free-form description to clarify the related data elements and their content
Syntax Rules:
1. C0302 - If FOB03 is present, then FOB02 is required.
2. C0405 - If FOB04 is present, then FOB05 is required.
3. C0706 - If FOB07 is present, then FOB06 is required.
4. C0809 - If FOB08 is present, then FOB09 is required.
Semantics:
1. FOB01 indicates which party will pay the carrier.
2. FOB02 is the code specifying transportation responsibility location.
3. FOB06 is the code specifying the title passage location.
4. FOB08 is the code specifying the point at which the risk of loss transfers. This may be different than the
location specified in FOB02/FOB03 and FOB06/FOB07.
Coremark_810_Invoice_v5010.ecs 16 X12V5010
4/30/2024 Invoice - 810
N9*L1*GEN
MSG*Note Here
Loop Summary:
Pos Id Segment Name Req Max Use Repeat Usage
2400 N9 Extended Reference Information C 1 Used
2500 MSG Message Text C 1 Used
Coremark_810_Invoice_v5010.ecs 17 X12V5010
4/30/2024 Invoice - 810
Element Summary:
Ref Id Element Name Req Type Min/Max Usage
N901 128 Reference Identification Qualifier M ID 2/3 Must use
Syntax Rules:
1. R0203 - At least one of N902 or N903 is required.
2. C0605 - If N906 is present, then N905 is required.
Semantics:
1. N906 reflects the time zone which the time reflects.
2. N907 contains data relating to the value cited in N902.
Coremark_810_Invoice_v5010.ecs 18 X12V5010
4/30/2024 Invoice - 810
Element Summary:
Ref Id Element Name Req Type Min/Max Usage
MSG01 933 Free-form Message Text M AN 1/264 Must use
Syntax Rules:
1. C0302 - If MSG03 is present, then MSG02 is required.
Semantics:
1. MSG03 is the number of lines to advance before printing.
Comments:
1. MSG02 is not related to the specific characteristics of a printer, but identifies top of page, advance a line, etc.
2. If MSG02 is "AA - Advance the specified number of lines before print" then MSG03 is required.
Coremark_810_Invoice_v5010.ecs 19 X12V5010
4/30/2024 Invoice - 810
Loop Summary:
Pos Id Segment Name Req Max Use Repeat Usage
0100 IT1 Baseline Item Data (Invoice) M 1 Must use
0300 IT3 Additional Item Data C 1 Used
0500 CTP Pricing Information M 1 Must use
0600 Loop PID M 2 Must use
1000 PO4 Item Physical Details O 1 Used
1800 Loop SAC O 25 Used
Coremark_810_Invoice_v5010.ecs 20 X12V5010
4/30/2024 Invoice - 810
User Note 1:
One of Core-Mark SKU (SK), Vendor Part Number (VN), UPC (UA) or GTIN (UK) must be returned as sent on the
Purchase Order
If the order was sent with Core-Mark Segment 'Core-Mark ' then the Core-Mark SKU (SK) must be returned
850: REF02 (REF01 = 06)
875: N902 (N901 = 06)
Element Summary:
Ref Id Element Name Req Type Min/Max Usage
IT101 350 Assigned Identification M AN 1/20 Must use
IT103 355 Unit or Basis for Measurement Code M ID 2/2 Must use
Description: Code specifying the units in which a value is being expressed, or manner in
which a measurement has been taken
Coremark_810_Invoice_v5010.ecs 21 X12V5010
4/30/2024 Invoice - 810
Coremark_810_Invoice_v5010.ecs 22 X12V5010
4/30/2024 Invoice - 810
Syntax Rules:
1. P020304 - If either IT102, IT103 or IT104 are present, then the others are required.
2. P0607 - If either IT106 or IT107 is present, then the other is required.
3. P0809 - If either IT108 or IT109 is present, then the other is required.
4. P1011 - If either IT110 or IT111 is present, then the other is required.
5. P1213 - If either IT112 or IT113 is present, then the other is required.
6. P1415 - If either IT114 or IT115 is present, then the other is required.
7. P1617 - If either IT116 or IT117 is present, then the other is required.
8. P1819 - If either IT118 or IT119 is present, then the other is required.
9. P2021 - If either IT120 or IT121 is present, then the other is required.
10. P2223 - If either IT122 or IT123 is present, then the other is required.
11. P2425 - If either IT124 or IT125 is present, then the other is required.
Semantics:
1. IT101 is the line item identification.
Comments:
1. Element 235/234 combinations should be interpreted to include products and/or services. See the Data
Dictionary for a complete list of IDs.
2. 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.
Coremark_810_Invoice_v5010.ecs 23 X12V5010
4/30/2024 Invoice - 810
User Note 1:
If IT103 = LB or KG, then the IT3 segment is required.
Element Summary:
Ref Id Element Name Req Type Min/Max Usage
IT301 382 Number of Units Shipped M R 1/10 Must use
Description: Numeric value of units shipped in manufacturer's shipping units for a line
item or transaction set
IT302 355 Unit or Basis for Measurement Code M ID 2/2 Must use
Description: Code specifying the units in which a value is being expressed, or manner in
which a measurement has been taken
Coremark_810_Invoice_v5010.ecs 24 X12V5010
4/30/2024 Invoice - 810
Element Summary:
Ref Id Element Name Req Type Min/Max Usage
CTP08 782 Monetary Amount M R 1/18 Must use
Syntax Rules:
1. P0405 - If either CTP04 or CTP05 is present, then the other is required.
2. C0607 - If CTP06 is present, then CTP07 is required.
3. C0902 - If CTP09 is present, then CTP02 is required.
4. C1002 - If CTP10 is present, then CTP02 is required.
5. C1103 - If CTP11 is present, then CTP03 is required.
Semantics:
1. 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.
2. CTP08 is the rebate amount.
Comments:
1. See Figures Appendix for an example detailing the use of CTP03 and CTP04.
2. See Figures Appendix for an example detailing the use of CTP03, CTP04 and CTP07.
Coremark_810_Invoice_v5010.ecs 25 X12V5010
4/30/2024 Invoice - 810
Loop Summary:
Pos Id Segment Name Req Max Use Repeat Usage
0600 PID Product/Item Description M 1 Must use
Coremark_810_Invoice_v5010.ecs 26 X12V5010
4/30/2024 Invoice - 810
Element Summary:
Ref Id Element Name Req Type Min/Max Usage
PID01 349 Item Description Type M ID 1/1 Must use
Description: A free-form description to clarify the related data elements and their content
Syntax Rules:
1. C0403 - If PID04 is present, then PID03 is required.
2. R0405 - At least one of PID04 or PID05 is required.
3. C0703 - If PID07 is present, then PID03 is required.
4. C0804 - If PID08 is present, then PID04 is required.
5. C0905 - If PID09 is present, then PID05 is required.
Semantics:
1. Use PID03 to indicate the organization that publishes the code list being referred to.
2. PID04 should be used for industry-specific product description codes.
3. PID08 describes the physical characteristics of the product identified in PID04. A "Y" indicates that the
specified attribute applies to this item; an "N" indicates it does not apply. Any other value is indeterminate.
4. PID09 is used to identify the language being used in PID05.
Comments:
1. 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.
2. Use PID06 when necessary to refer to the product surface or layer being described in the segment.
3. PID07 specifies the individual code list of the agency specified in PID03.
Coremark_810_Invoice_v5010.ecs 27 X12V5010
4/30/2024 Invoice - 810
Element Summary:
Ref Id Element Name Req Type Min/Max Usage
PO401 356 Pack O N0 1/6 Used
Description: The number of inner containers, or number of eaches if there are no inner
containers, per outer container
PO402 357 Size X R 1/8 Used
Description: Code specifying the units in which a value is being expressed, or manner in
which a measurement has been taken
Semantics:
1. PO415 is used to indicate the relative layer of this package or range of packages within the layers of
packaging. Relative Position 1 (value R1) is the innermost package.
2. PO416 is the package identifier or the beginning package identifier in a range of identifiers.
3. PO417 is the ending package identifier in a range of identifiers.
4. PO418 is the number of packages in this layer.
Comments:
1. PO403 - The "Unit or Basis for Measure Code" in this segment position is for purposes of defining the unit of
measure of the "Size" identified in the PO402. For example: If the carton contains 24 12-Ounce packages, it
would be described as follows: Data element 356 = "24"; Data element 357 = "12"; Data element 355 = "OZ".
2. PO413 defines the unit of measure for PO410, PO411, and PO412.
Coremark_810_Invoice_v5010.ecs 28 X12V5010
4/30/2024 Invoice - 810
Loop Summary:
Pos Id Segment Name Req Max Use Repeat Usage
1800 SAC Service, Promotion, Allowance, or Charge O 1 Used
Information
Coremark_810_Invoice_v5010.ecs 29 X12V5010
4/30/2024 Invoice - 810
Information
User Option (Usage): Used
Purpose: To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for
the service, promotion, allowance, or charge
User Note 1:
If allowance and charges are included on the PO, Core-mark expects those to be included in the invoice.
Element Summary:
Ref Id Element Name Req Type Min/Max Usage
SAC01 248 Allowance or Charge Indicator M ID 1/1 Must use
Description: Code which indicates an allowance or charge for the service specified
Coremark_810_Invoice_v5010.ecs 30 X12V5010
4/30/2024 Invoice - 810
Code Name
H000 Special Allowance
H970 Terms Allowance
I250 Transportation Charge (Minimum Rate)
I500 Vendor Freight
Description: Rate expressed in the standard monetary denomination for the currency
specified
SAC12 331 Allowance or Charge Method of O ID 2/2 Used
Handling Code
Description: A free-form description to clarify the related data elements and their content
User Note 1: Required when SAC02 = F050
Syntax Rules:
1. R0203 - At least one of SAC02 or SAC03 is required.
2. P0304 - If either SAC03 or SAC04 is present, then the other is required.
3. P0607 - If either SAC06 or SAC07 is present, then the other is required.
4. P0910 - If either SAC09 or SAC10 is present, then the other is required.
5. C1110 - If SAC11 is present, then SAC10 is required.
6. C1413 - If SAC14 is present, then SAC13 is required.
7. C1615 - If SAC16 is present, then SAC15 is required.
8. R0507 - At least one of SAC05 or SAC07 is required.
Semantics:
1. If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.
2. SAC05 is the total amount for the service, promotion, allowance, or charge.
3. If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence.
4. SAC08 is the allowance or charge rate per unit.
5. SAC10 and SAC11 is the quantity basis when the allowance or charge quantity is different from the purchase
order or invoice quantity.
6. SAC10 and SAC11 used together indicate a quantity range, which could be a dollar amount, that is applicable
to service, promotion, allowance, or charge.
7. SAC13 is used in conjunction with SAC02 or SAC04 to provide a specific reference number as identified by
the code used.
8. SAC14 is used in conjunction with SAC13 to identify an option when there is more than one option of the
promotion.
9. SAC16 is used to identify the language being used in SAC15.
Coremark_810_Invoice_v5010.ecs 31 X12V5010
4/30/2024 Invoice - 810
Comments:
1. SAC04 may be used to uniquely identify the service, promotion, allowance, or charge. In addition, it may be
used in conjunction with SAC03 to further define SAC02.
2. 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.
Coremark_810_Invoice_v5010.ecs 32 X12V5010
4/30/2024 Invoice - 810
Element Summary:
Ref Id Element Name Req Type Min/Max Usage
TDS01 610 Amount M N2 1/15 Must use
Semantics:
1. TDS01 is the total amount of invoice (including charges, less allowances) before terms discount (if discount is
applicable).
2. TDS02 indicates the amount upon which the terms discount amount is calculated.
3. TDS03 is the amount of invoice due if paid by terms discount due date (total invoice or installment amount
less cash discount).
4. TDS04 indicates the total amount of terms discount.
Comments:
1. TDS02 is required if the dollar value subject to discount is not equal to the dollar value of TDS01.
Coremark_810_Invoice_v5010.ecs 33 X12V5010
4/30/2024 Invoice - 810
Element Summary:
Ref Id Element Name Req Type Min/Max Usage
TXI01 963 Tax Type Code M ID 2/2 Must use
Syntax Rules:
1. R020306 - At least one of TXI02, TXI03 or TXI06 is required.
2. P0405 - If either TXI04 or TXI05 is present, then the other is required.
3. C0803 - If TXI08 is present, then TXI03 is required.
Semantics:
1. TXI02 is the monetary amount of the tax.
2. TXI03 is the tax percent expressed as a decimal.
3. TXI07 is a code indicating the relationship of the price or amount to the associated segment.
Coremark_810_Invoice_v5010.ecs 34 X12V5010
4/30/2024 Invoice - 810
Loop Summary:
Pos Id Segment Name Req Max Use Repeat Usage
0400 SAC Service, Promotion, Allowance, or Charge M 1 Must use
Information
Coremark_810_Invoice_v5010.ecs 35 X12V5010
4/30/2024 Invoice - 810
Information
User Option (Usage): Must use
Purpose: To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for
the service, promotion, allowance, or charge
Element Summary:
Ref Id Element Name Req Type Min/Max Usage
SAC01 248 Allowance or Charge Indicator M ID 1/1 Must use
Description: Code which indicates an allowance or charge for the service specified
Coremark_810_Invoice_v5010.ecs 36 X12V5010
4/30/2024 Invoice - 810
Code Name
I500 Vendor Freight
Description: Rate expressed in the standard monetary denomination for the currency
specified
SAC12 331 Allowance or Charge Method of O ID 2/2 Used
Handling Code
Description: A free-form description to clarify the related data elements and their content
User Note 1: Required when SAC02 = F050
Syntax Rules:
1. R0203 - At least one of SAC02 or SAC03 is required.
2. P0304 - If either SAC03 or SAC04 is present, then the other is required.
3. P0607 - If either SAC06 or SAC07 is present, then the other is required.
4. P0910 - If either SAC09 or SAC10 is present, then the other is required.
5. C1110 - If SAC11 is present, then SAC10 is required.
6. C1413 - If SAC14 is present, then SAC13 is required.
7. C1615 - If SAC16 is present, then SAC15 is required.
8. R0507 - At least one of SAC05 or SAC07 is required.
Semantics:
1. If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.
2. SAC05 is the total amount for the service, promotion, allowance, or charge.
3. If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence.
4. SAC08 is the allowance or charge rate per unit.
5. SAC10 and SAC11 is the quantity basis when the allowance or charge quantity is different from the purchase
order or invoice quantity.
6. SAC10 and SAC11 used together indicate a quantity range, which could be a dollar amount, that is applicable
to service, promotion, allowance, or charge.
7. SAC13 is used in conjunction with SAC02 or SAC04 to provide a specific reference number as identified by
the code used.
8. SAC14 is used in conjunction with SAC13 to identify an option when there is more than one option of the
promotion.
9. SAC16 is used to identify the language being used in SAC15.
Comments:
1. SAC04 may be used to uniquely identify the service, promotion, allowance, or charge. In addition, it may be
used in conjunction with SAC03 to further define SAC02.
2. In some business applications, it is necessary to advise the trading partner of the actual dollar amount that a
Coremark_810_Invoice_v5010.ecs 37 X12V5010
4/30/2024 Invoice - 810
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.
Coremark_810_Invoice_v5010.ecs 38 X12V5010
4/30/2024 Invoice - 810
Loop Summary:
Pos Id Segment Name Req Max Use Repeat Usage
0600 ISS Invoice Shipment Summary M 1 Must use
Coremark_810_Invoice_v5010.ecs 39 X12V5010
4/30/2024 Invoice - 810
Element Summary:
Ref Id Element Name Req Type Min/Max Usage
ISS01 382 Number of Units Shipped X R 1/10 Used
Description: Numeric value of units shipped in manufacturer's shipping units for a line
item or transaction set
ISS02 355 Unit or Basis for Measurement Code X ID 2/2 Used
Description: Code specifying the units in which a value is being expressed, or manner in
which a measurement has been taken
Description: Code specifying the units in which a value is being expressed, or manner in
which a measurement has been taken
Semantics:
1. ISS07 is the quantity of third party pallets.
2. ISS08 is the gross weight of third party pallets in pounds.
Coremark_810_Invoice_v5010.ecs 40 X12V5010
4/30/2024 Invoice - 810
Element Summary:
Ref Id Element Name Req Type Min/Max Usage
CTT01 354 Number of Line Items M N0 1/6 Must use
Syntax Rules:
1. P0304 - If either CTT03 or CTT04 is present, then the other is required.
2. P0506 - If either CTT05 or CTT06 is present, then the other is required.
Comments:
1. This segment is intended to provide hash totals to validate transaction completeness and correctness.
Coremark_810_Invoice_v5010.ecs 41 X12V5010
4/30/2024 Invoice - 810
Element Summary:
Ref Id Element Name Req Type Min/Max Usage
SE01 96 Number of Included Segments M N0 1/10 Must use
Description: Identifying control number that must be unique within the transaction set
functional group assigned by the originator for a transaction set
Comments:
1. SE is the last segment of each transaction set.
Coremark_810_Invoice_v5010.ecs 42 X12V5010