Balkamp
/
Invoice
  • Specification
  • EDI Inspector
Stedi maintains this guide based on public documentation from Balkamp. Contact Balkamp for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Balkamp logo

X12 810 Invoice

X12 Release 4010

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.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI sample
  • Sample 1
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/balkamp/invoice/01HW5SF2WRB71ZJ13M8Q01STK4
Powered by
Build EDI implementation guides at stedi.com
Overview
ISA
-
Interchange Control Header
Max use 1
Required
GS
-
Functional Group Header
Max use 1
Required
heading
ST
010
Transaction Set Header
Max use 1
Required
BIG
020
Beginning Segment for Invoice
Max use 1
Required
REF
050
Reference Identification
Max use 12
Required
N1 Loop Bill-to-Party
ITD
130
Terms of Sale/Deferred Terms of Sale
Max use 1
Required
DTM
140
Date/Time Reference
Max use 10
Required
summary
TDS
010
Total Monetary Value Summary
Max use 1
Required
SAC Loop
CTT
070
Transaction Totals
Max use 1
Required
SE
080
Transaction Set Trailer
Max use 1
Required
GE
-
Functional Group Trailer
Max use 1
Required
IEA
-
Interchange Control Trailer
Max use 1
Required
ISA

Interchange Control Header

RequiredMax use 1

To start and identify an interchange of zero or more functional groups and interchange-related control segments

Example
ISA-01
I01
Authorization Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Authorization Information

00
No Authorization Information Present (No Meaningful Information in I02)
ISA-02
I02
Authorization Information
Required
String (AN)
Min 10Max 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)

ISA-03
I03
Security Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Security Information

00
No Security Information Present (No Meaningful Information in I04)
ISA-04
I04
Security Information
Required
String (AN)
Min 10Max 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)

ISA-05
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-06
I06
Interchange Sender ID
Required
String (AN)
Min 15Max 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

ISA-07
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-08
I07
Interchange Receiver ID
Required
String (AN)
Min 15Max 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

ISA-09
I08
Interchange Date
Required
Date (DT)
YYMMDD format

Date of the interchange

ISA-10
I09
Interchange Time
Required
Time (TM)
HHMM format

Time of the interchange

ISA-11
I10
Interchange Control Standards Identifier
Required
Identifier (ID)

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
ISA-12
I11
Interchange Control Version Number
Required
Identifier (ID)

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
ISA-13
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

ISA-14
I13
Acknowledgment Requested
Required
Identifier (ID)
Min 1Max 1

Code sent by the sender to request an interchange acknowledgment (TA1)

0
No Acknowledgment Requested
1
Interchange Acknowledgment Requested
ISA-15
I14
Usage Indicator
Required
Identifier (ID)
Min 1Max 1

Code to indicate whether data enclosed by this interchange envelope is test, production or information

I
Information
P
Production Data
T
Test Data
ISA-16
I15
Component Element Separator
Required
String (AN)
Min 1Max 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

>
Component Element Separator

Functional Group Header

RequiredMax use 1

To indicate the beginning of a functional group and to provide control information

Example
GS-01
479
Functional Identifier Code
Required
Identifier (ID)

Code identifying a group of application related transaction sets

IN
Invoice Information (810,819)
GS-02
142
Application Sender's Code
Required
String (AN)
Min 2Max 15

Code identifying party sending transmission; codes agreed to by trading partners

GS-03
124
Application Receiver's Code
Required
String (AN)
Min 2Max 15

Code identifying party receiving transmission. Codes agreed to by trading partners

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

Required
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

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)

GS-06
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

GS-07
455
Responsible Agency Code
Required
Identifier (ID)
Min 1Max 2

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
GS-08
480
Version / Release / Industry Identifier Code
Required
String (AN)

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

ST
010
Heading > ST

Transaction Set Header

RequiredMax use 1

To indicate the start of a transaction set and to assign a control number

Example
ST-01
143
Transaction Set Identifier Code
Required
Identifier (ID)

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
ST-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

BIG
020
Heading > BIG

Beginning Segment for Invoice

RequiredMax use 1

To indicate the beginning of an invoice transaction set and transmit identifying numbers and dates

Usage notes

Example: BIG2010080108765432**E0231231~

Example
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • BIG01 is the invoice issue date.
BIG-02
76
Invoice Number
Required
String (AN)
Min 1Max 22

Identifying number assigned by issuer

BIG-04
324
Purchase Order Number
Required
String (AN)
Min 1Max 22

Identifying number for Purchase Order assigned by the orderer/purchaser

REF
050
Heading > REF

Reference Identification

RequiredMax use 12

To specify identifying information

Usage notes

Example: REFFR1234567890

Example
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

FR
Freight Bill Number
REF-02
127
Reference Identification
Required
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Usage notes

Must match REF01-‘CN’ from 856 ASN.

N1 Loop Bill-to-Party
RequiredMax 1
Variants (all may be used)
N1 Loop Ship FromN1 Loop Ship To
N1
070
Heading > N1 Loop Bill-to-Party > N1

Name

RequiredMax use 1

To identify a party by type of organization, name, and code

Usage notes

Examples:
N1BY**92BALKCENT**
N1BY**92ARC**
N1BY**92TWA**

Example
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

BT
Bill-to-Party
N1-03
66
Identification Code Qualifier
Required
Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

92
Assigned by Buyer or Buyer's Agent
N1-04
67
Identification Code
Required
String (AN)

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.
Usage notes

Identifier for the Balkamp Distribution Center.

ARC
Indianapolis, IN West Jordan, UT ARC Nashville, TN
BALKCENT
Plainfield, IN West Jordan, UT Nashville, TN
DIRECT
Direct

If BEG02 = ‘DS’.

TWA
Lithia Springs, GA
TWP
Payson, UT
N1 Loop Bill-to-Party end
N1 Loop Ship From
RequiredMax >1
Variants (all may be used)
N1 Loop Bill-to-PartyN1 Loop Ship To
N1
070
Heading > N1 Loop Ship From > N1

Name

RequiredMax use 1

To identify a party by type of organization, name, and code

Usage notes

Example: N1SF**92123456789

Example
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

SF
Ship From
Optional
String (AN)
Min 1Max 60

Free-form name

N1-03
66
Identification Code Qualifier
Required
Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

92
Assigned by Buyer or Buyer's Agent
N1-04
67
Identification Code
Required
String (AN)
Min 2Max 80

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.
Usage notes

Identifier of Shipping Location

Must be the same as PO N104.

N1 Loop Ship From end
N1 Loop Ship To
RequiredMax 1
Variants (all may be used)
N1 Loop Bill-to-PartyN1 Loop Ship From
N1
070
Heading > N1 Loop Ship To > N1

Name

RequiredMax use 1

To identify a party by type of organization, name, and code

Usage notes

Examples:
When 850 BEG02 PO type = 'SA'.
N1STBALKAMP PLAINFIELD92BALKCENT**
When 850 BEG02 PO type = 'DS'.
N1STBRUNNER AUTO SUPPLY 565920000158197

Example
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

ST
Ship To
Required
String (AN)
Min 1Max 60

Free-form name

N1-03
66
Identification Code Qualifier
Required
Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

92
Assigned by Buyer or Buyer's Agent
N1-04
67
Identification Code
Required
String (AN)
Min 2Max 80

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.
Usage notes

Identifier for Distribution Center

“BALKCENT” Plainfield, IN
“BALKWEST” West Jordan, UT
“NSH” Nashville, TN
“VISIONSLC“ Packager – Salt Lake City
“ARC” Indianapolis, IN
“ARW” West Jordan, UT
“ARN” ARC Nashville, TN

If BEG02 = ‘DS’ then N104 will contain the drop ship customer’s identifier.

N3
090
Heading > N1 Loop Ship To > N3

Address Information

OptionalMax use 2

To specify the location of the named party

Usage notes

Example: N3*1601 WHITAKER ROAD

Example
N3-01
166
Address Information
Required
String (AN)
Min 1Max 55

Address information

N3-02
166
Address Information
Optional
String (AN)
Min 1Max 55

Address information

N4
100
Heading > N1 Loop Ship To > N4

Geographic Location

OptionalMax use 1

To specify the geographic place of the named party

Usage notes

Example: N4PLAINFIELDIN*46168

Example
N4-01
19
City Name
Required
String (AN)
Min 2Max 30

Free-form text for city name

  • A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
N4-02
156
State or Province Code
Required
Identifier (ID)
Min 2Max 2

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.
N4-03
116
Postal Code
Required
Identifier (ID)
Min 3Max 15

Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

N1 Loop Ship To end
ITD
130
Heading > ITD

Terms of Sale/Deferred Terms of Sale

RequiredMax use >1

To specify terms of sale

Usage notes

Example: ITD22010083120100915

Example
ITD-03
338
Terms Discount Percent
Required
Decimal number (R)
Min 1Max 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-04
370
Terms Discount Due Date
Required
Date (DT)
CCYYMMDD format

Date payment is due if discount is to be earned expressed in format CCYYMMDD

ITD-06
446
Terms Net Due Date
Required
Date (DT)
CCYYMMDD format

Date when total invoice amount becomes due expressed in format CCYYMMDD

DTM
140
Heading > DTM

Date/Time Reference

RequiredMax use 10

To specify pertinent dates and times

Usage notes

Example: DTM01120100731

Example
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

Code specifying type of date or time, or both date and time

011
Shipped
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

Heading end

Detail

IT1 Loop
RequiredMax >1
IT1
010
Detail > IT1 Loop > IT1

Baseline Item Data (Invoice)

RequiredMax use 1

To specify the basic and most frequently used line item data for the invoice and related transactions

Usage notes

Example: IT10112EA123.45*BP123-4567VC9999999

Example
If either Quantity Invoiced (IT1-02), Unit or Basis for Measurement Code (IT1-03) or Unit Price (IT1-04) are present, then the others are required
IT1-01
350
Assigned Identification
Required
String (AN)
Min 1Max 20

Alphanumeric characters assigned for differentiation within a transaction set

  • IT101 is the purchase order line item identification.
IT1-02
358
Quantity Invoiced
Required
Decimal number (R)
Min 1Max 10

Number of units invoiced (supplier units)

IT1-03
355
Unit or Basis for Measurement Code
Optional
Identifier (ID)
Min 2Max 2

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

Usage notes

Unit of measure listed should be the same unit of measure listed in the purchase order.

IT1-04
212
Unit Price
Required
Decimal number (R)
Min 1Max 15

Price per unit of product, service, commodity, etc.

Usage notes

Rate charged per unit of measure less discount, but not to include order level discounts or allowances.

IT1-06
235
Product/Service ID Qualifier
Required
Identifier (ID)

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.
BP
Buyer's Part Number
IT1-07
234
Product/Service ID
Required
String (AN)
Min 1Max 48

Identifying number for a product or service

IT1-08
235
Product/Service ID Qualifier
Required
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

VC
Vendor's (Seller's) Catalog Number
IT1-09
234
Product/Service ID
Required
String (AN)
Min 1Max 48

Identifying number for a product or service

IT1 Loop end
Detail end

Summary

TDS
010
Summary > TDS

Total Monetary Value Summary

RequiredMax use 1

To specify the total invoice discounts and amounts

Usage notes

Example: TDS*13098

Example
TDS-01
610
Amount
Required
Numeric (N2)
Min 1Max 15

Monetary amount

  • TDS01 is the total amount of invoice (including charges, less allowances) before terms discount (if discount is applicable).
SAC Loop
OptionalMax >1
SAC
040
Summary > SAC Loop > SAC

Service, Promotion, Allowance, or Charge Information

RequiredMax use 1

To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge

Usage notes

Example: SACCD240***7.53

Example
SAC-01
248
Allowance or Charge Indicator
Required
Identifier (ID)

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
SAC-02
1300
Service, Promotion, Allowance, or Charge Code
Required
Identifier (ID)

Code identifying the service, promotion, allowance, or charge

Usage notes

We will work with you to identify the correct code.

A260
Advertising Allowance (2630)
A990
Cataloging Services (2505)
B310
Commission Amount (2234-BK) (3534-ARC)
B320
Competitive Allowance (3508)
B660
Contract Allowance (3534)
B750
Core (1674)-Charge
C000
Defective Allowance (3560)
C240
Freight (3700-SA)/(6403-DS)
C260
Discount-Incentive (8000)
C310
Freight In (3700-SA) (6403-DS) Charge
D240
Freight In (3700-SA)/(6403-DS) Charge
D500
Handling Fee (6404) Charge
E065
Invoice Adjustment (2218)
E550
Marketing Development Funds (2216)
F340
Pick/Up (3706)
F670
Price and Marketing Allowance (1684)
F800
Promotional Allowance (3505)
I590
Warranty (3560)
SAC-05
610
Amount
Required
Numeric (N2)
Min 1Max 15

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.
Usage notes

Must be greater than 0.

SAC Loop end
CTT
070
Summary > CTT

Transaction Totals

RequiredMax use 1

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.
Usage notes

Example: CTT12

Example
CTT-01
354
Number of Line Items
Required
Numeric (N0)
Min 1Max 6

Total number of line items in the transaction set

CTT-02
347
Hash Total
Required
Decimal number (R)
Min 1Max 10

Sum of values of the specified data element. All values in the data element will be summed without regard to decimal points (explicit or implicit) or signs. Truncation will occur on the left most digits if the sum is greater than the maximum size of the hash total of the data element.

## Example:
-.0018 First occurrence of value being hashed.
.18 Second occurrence of value being hashed.
1.8 Third occurrence of value being hashed.
18.01 Fourth occurrence of value being hashed.

1855 Hash total prior to truncation.
855 Hash total after truncation to three-digit field.

SE
080
Summary > SE

Transaction Set Trailer

RequiredMax use 1

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Example
SE-01
96
Number of Included Segments
Required
Numeric (N0)
Min 1Max 10

Total number of segments included in a transaction set including ST and SE segments

SE-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

Summary end

Functional Group Trailer

RequiredMax use 1

To indicate the end of a functional group and to provide control information

Example
GE-01
97
Number of Transaction Sets Included
Required
Numeric (N0)
Min 1Max 6

Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

GE-02
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

Interchange Control Trailer

RequiredMax use 1

To define the end of an interchange of zero or more functional groups and interchange-related control segments

Example
IEA-01
I16
Number of Included Functional Groups
Required
Numeric (N0)
Min 1Max 5

A count of the number of functional groups included in an interchange

IEA-02
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

EDI Samples

Sample 1

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *240509*1529*U*00401*000000001*0*T*>~
GS*IN*SENDERGS*RECEIVERGS*20240509*152942*000000001*X*004010~
ST*810*0001~
BIG*20100801*08765432**E0231231~
REF*FR*1234567890~
N1*SF*123456789*92*12~
N1*ST*BALKAMP PLAINFIELD*92*BALKCENT~
N3*1601 WHITAKER ROAD~
N4*PLAINFIELD*IN*46168~
N1*BT**92*BALKCENT~
ITD***2*20100831**20100915~
DTM*011*20100731~
IT1*1*2*EA*123.45**BP*123-4567*VC*9999999~
TDS*13098~
SAC*C*D240***753~
CTT*1*2~
SE*15*0001~
GE*1*000000001~
IEA*1*000000001~

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.