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

X12 810 Invoice

X12 Release 4030

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
  • ^ Repetition
EDI samples
    View the latest version of this implementation guide as an interactive webpage
    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
    0100
    Transaction Set Header
    Max use 1
    Required
    BIG
    0200
    Beginning Segment for Invoice
    Max use 1
    Required
    REF
    0500
    Reference Identification
    Max use 12
    Optional
    Buying Party (Purchaser)
    ITD
    1300
    Terms of Sale/Deferred Terms of Sale
    Max use 1
    Required
    DTM
    1400
    Date/Time Reference
    Max use 10
    Optional
    summary
    TDS
    0100
    Total Monetary Value Summary
    Max use 1
    Required
    CAD
    0300
    Carrier Detail
    Max use 1
    Optional
    SAC Loop
    CTT
    0700
    Transaction Totals
    Max use 1
    Required
    SE
    0800
    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

    Code identifying the type of information in the Authorization Information

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

    Code identifying the type of information in the Security Information

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

    Code indicating 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
    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
    Min 2Max 2

    Code indicating 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
    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
    YYMMDD format

    Date of the interchange

    ISA-10
    I09
    Interchange Time
    Required
    HHMM format

    Time of the interchange

    ISA-11
    I65
    Repetition Separator
    Required
    Min 1Max 1

    Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator

    ^
    Repetition Separator
    ISA-12
    I11
    Interchange Control Version Number
    Required

    Code specifying the version number of the interchange control segments

    00403
    Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1999
    ISA-13
    I12
    Interchange Control Number
    Required
    Min 9Max 9

    A control number assigned by the interchange sender

    ISA-14
    I13
    Acknowledgment Requested
    Required
    Min 1Max 1

    Code indicating sender's request for an interchange acknowledgment

    0
    No Acknowledgment Requested
    1
    Interchange Acknowledgment Requested
    ISA-15
    I14
    Usage Indicator
    Required
    Min 1Max 1

    Code indicating 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
    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

    Code identifying a group of application related transaction sets

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

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

    GS-03
    124
    Application Receiver's Code
    Required
    Min 2Max 15

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

    GS-04
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

    GS-05
    337
    Time
    Required
    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
    Min 1Max 9

    Assigned number originated and maintained by the sender

    GS-07
    455
    Responsible Agency Code
    Required
    Min 1Max 2

    Code identifying the issuer of the standard; this code is used in conjunction with Data Element 480

    T
    Transportation Data Coordinating Committee (TDCC)
    X
    Accredited Standards Committee X12
    GS-08
    480
    Version / Release / Industry Identifier Code
    Required

    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

    004030
    Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1999

    Heading

    ST
    0100

    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

    Code uniquely identifying a Transaction Set

    • 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).
    810
    Invoice
    ST-02
    329
    Transaction Set Control Number
    Required
    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
    0200

    Beginning Segment for Invoice

    RequiredMax use 1

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

    Example
    BIG-01
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

    • BIG01 is the invoice issue date.
    BIG-02
    76
    Invoice Number
    Required
    Min 1Max 30

    Identifying number assigned by issuer

    BIG-03
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

    • BIG03 is the date assigned by the purchaser to purchase order.
    BIG-04
    324
    Purchase Order Number
    Required
    Min 1Max 22

    Identifying number for Purchase Order assigned by the orderer/purchaser

    REF
    0500

    Reference Identification

    OptionalMax use 12

    To specify identifying information

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    DP
    Department Number
    REF-02
    127
    Reference Identification
    Optional
    Min 4Max 4

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

    Usage notes

    Will contain the four digit department number

    N1 Buying Party (Purchaser)
    RequiredMax >1
    Variants (all may be used)
    N1Remit To
    N1
    0700

    Name

    RequiredMax use 1

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

    Example
    At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
    If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
    N1-01
    98
    Entity Identifier Code
    Required

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

    BY
    Buying Party (Purchaser)
    N1-02
    93
    Name
    Optional
    Min 1Max 60

    Free-form name

    N1-03
    66
    Identification Code Qualifier
    Optional

    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
    Optional
    Min 4Max 4

    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

    This is the location code as defined by N103.

    The identification code (N104) is the four digit Belk Distribution Center location number. There are three DC location numbers - 0737, 0744, 0745

    N1 Remit To
    RequiredMax >1
    Variants (all may be used)
    N1Buying Party (Purchaser)
    N1
    0700

    Name

    RequiredMax use 1

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

    Example
    If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
    N1-01
    98
    Entity Identifier Code
    Required

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

    RI
    Remit To
    N1-02
    93
    Name
    Required
    Min 1Max 60

    Free-form name

    N1-03
    66
    Identification Code Qualifier
    Optional

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

    1
    D-U-N-S Number, Dun & Bradstreet

    See External Code Source A16 in Section III for reference document

    N1-04
    67
    Identification Code
    Optional
    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

    This is the location code as defined by N103.

    The identification code (N104) is the vendor's nine or thirteen digit Dun and Bradstreet number.

    ITD
    1300

    Terms of Sale/Deferred Terms of Sale

    RequiredMax use >1

    To specify terms of sale

    Example
    ITD-01
    336
    Terms Type Code
    Required

    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.
    02
    End of Month (EOM)
    05
    Discount Not Applicable
    08
    Basic Discount Offered
    09
    Proximo
    12
    10 Days After End of Month (10 EOM)
    ITD-02
    333
    Terms Basis Date Code
    Required

    Code identifying the beginning of the terms period

    3
    Invoice Date
    ITD-07
    386
    Terms Net Days
    Required
    Min 1Max 3

    Number of days until total invoice amount is due (discount not applicable)

    Usage notes

    The end of the term period is derived by adding this value to the beginning of the term period, as qualified by ITD02.

    DTM
    1400

    Date/Time Reference

    OptionalMax use 10

    To specify pertinent dates and times

    Example
    DTM-01
    374
    Date/Time Qualifier
    Required

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

    011
    Shipped
    DTM-02
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

    Detail

    IT1 Loop
    RequiredMax >1
    IT1
    0100

    Baseline Item Data (Invoice)

    RequiredMax use 1

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

    Example
    If either Product/Service ID Qualifier (IT1-08) or Product/Service ID (IT1-09) is present, then the other is required
    IT1-01
    350
    Assigned Identification
    Required
    Min 1Max 11

    Alphanumeric characters assigned for differentiation within a transaction set

    • IT101 is the line item identification.
    IT1-02
    358
    Quantity Invoiced
    Required
    Min 1Max 10

    Number of units invoiced (supplier units)

    Usage notes

    Number of Units must be a whole number and contain no decimals

    IT1-03
    355
    Unit or Basis for Measurement Code
    Required

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

    Usage notes

    See Section III for code list.

    AS
    Assortment
    EA
    Each
    IT1-04
    212
    Unit Price
    Required
    Min 1Max 15

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

    Usage notes

    The price is sent with a decimal point only when needed, e.g., $15.95 would be sent as "15.95", and $29.00 would be sent as "29".

    To indicate a no charge item or free goods, IT104 will contain a single zero (0) and IT105 will contain code NC.

    IT1-05
    639
    Basis of Unit Price Code
    Optional

    Code identifying the type of unit price for an item

    Usage notes

    This data element is used to clarify or alter the basis of unit price. The unit price expressed in IT104 is always in the same terms as the unit of measure in IT103, unless otherwise specified in IT105.

    NC
    No Charge
    WE
    Wholesale Price per Each
    IT1-06
    235
    Product/Service ID Qualifier
    Required

    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.
    EN
    EAN/UCC - 13
    UP
    UCC - 12

    The product/service ID qualifier (IT106) of "UP" is preferred.

    IT1-07
    234
    Product/Service ID
    Required
    Min 1Max 48

    Identifying number for a product or service

    IT1-08
    235
    Product/Service ID Qualifier
    Optional

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

    VA
    Vendor's Style Number
    IT1-09
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    Summary

    TDS
    0100

    Total Monetary Value Summary

    RequiredMax use 1

    To specify the total invoice discounts and amounts

    Example
    TDS-01
    610
    Amount
    Required
    Min 1Max 15

    Monetary amount

    • TDS01 is the total amount of invoice (including charges, less allowances) before terms discount (if discount is applicable).
    CAD
    0300

    Carrier Detail

    OptionalMax use 1

    To specify transportation details for the transaction

    Example
    If Reference Identification Qualifier (CAD-07) is present, then Reference Identification (CAD-08) is required
    CAD-04
    140
    Standard Carrier Alpha Code
    Required
    Min 2Max 4

    Standard Carrier Alpha Code

    Usage notes

    See External Code Source A17 in Section III for reference document

    CAD-07
    128
    Reference Identification Qualifier
    Optional

    Code qualifying the Reference Identification

    BM
    Bill of Lading Number

    The reference identification qualifier (CAD07) of "BM" is preferred.

    CAD-08
    127
    Reference Identification
    Optional
    Min 1Max 50

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

    Usage notes

    The reference identification (CAD08) will contain the Transplace ME#

    SAC Loop
    OptionalMax >1
    SAC
    0400

    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

    Example
    SAC-01
    248
    Allowance or Charge Indicator
    Required

    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
    Optional

    Code identifying the service, promotion, allowance, or charge

    Usage notes

    See Section III for code list.

    B950
    Damaged Merchandise
    C310
    Discount
    D240
    Freight
    D920
    Insurance Fee
    D980
    Insurance
    E750
    New Store Discount
    G970
    Small Order Charge
    H630
    Tax - City Sales Tax (Only)
    H660
    Tax - Federal Excise Tax, FET
    H700
    Tax - Local Tax
    H770
    Tax - State Tax
    H850
    Tax
    ZZZZ
    Mutually Defined
    SAC-05
    610
    Amount
    Required
    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

    When SAC01 contains code A or code C, then this data element is required.

    This will resolve any differences between the sender's and receiver's system calculations of amounts, i.e., rounding errors when allowances or charges are expressed in percentages or rates.

    ISS Loop
    OptionalMax >1
    ISS
    0600

    Invoice Shipment Summary

    RequiredMax use 1

    To specify summary details of total items shipped in terms of quantity, weight, and volume

    Example
    If either Number of Units Shipped (ISS-01) or Unit or Basis for Measurement Code (ISS-02) is present, then the other is required
    If either Weight (ISS-03) or Unit or Basis for Measurement Code (ISS-04) is present, then the other is required
    ISS-01
    382
    Number of Units Shipped
    Optional
    Min 1Max 10

    Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set

    ISS-02
    355
    Unit or Basis for Measurement Code
    Optional

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

    Usage notes

    See Section III for code list.

    CT
    Carton
    ISS-03
    81
    Weight
    Optional
    Min 1Max 10

    Numeric value of weight

    ISS-04
    355
    Unit or Basis for Measurement Code
    Optional

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

    Usage notes

    See Section III for code list.

    LB
    Pound
    CTT
    0700

    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 CTT02 is the hash total of the quantities invoiced (IT102) for each IT1 segment.
    Example
    CTT-01
    354
    Number of Line Items
    Required
    Min 1Max 6

    Total number of line items in the transaction set

    Usage notes

    The number of IT1 segments present in the transaction set

    SE
    0800

    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
    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
    Min 4Max 9

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

    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
    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
    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
    Min 1Max 5

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

    IEA-02
    I12
    Interchange Control Number
    Required
    Min 9Max 9

    A control number assigned by the interchange sender

    EDI Samples

    Eaches/SKU

    ST*810*0001~
    BIG*20131030*12345678900*20131030*5051234~
    REF*DP*0421~
    N1*BY**92*0737~
    N1*RI*ABC CO.*1*003456789~
    ITD*05*3*****30~
    DTM*011*20130630~
    IT1*1*55*EA*10*WE*UP*400663067199*VA*40C4210131~
    IT1*2*55*EA*12.5*WE*UP*400663067200*VA*40C4210131~
    IT1*3*55*EA*8*WE*UP*400663067201*VA*40C4210131~
    TDS*168002~
    CAD****UQEP***BM*F12345~
    SAC*C*D240***252~
    ISS*7*CT*3.5*LB~
    CTT*3~
    SE*16*0001~

    Pack

    ST*810*0001~
    BIG*20131030*12345678901*20131030*5053401~
    REF*DP*0421~
    N1*BY**92*0744~
    N1*RI*ABC CO.*1*003456789~
    ITD*05*3*****30~
    DTM*011*20130630~
    IT1*1*60*AS*30*WE*UP*400663067208*VA*40C4210131~
    IT1*2*60*AS*45*WE*UP*400663067209*VA*40C4210131~
    IT1*3*60*AS*30*WE*UP*400663067211*VA*A105BB~
    TDS*630252~
    CAD****UQEP***BM*F12345~
    SAC*C*D240***252~
    ISS*7*CT*3.5*LB~
    CTT*3~
    SE*16*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.