Bed Bath & Beyond
/
Invoice
  • Specification
  • EDI Inspector
Import
Stedi maintains this guide based on public documentation from Bed Bath & Beyond. Contact Bed Bath & Beyond for official EDI specifications. To report any errors in this guide, please contact us.
Go to EDI Guide Catalog
Bed Bath & Beyond 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.

---
  1. The invoice number may contain a maximum of 12 characters.
  2. The invoice number must not repeat within a 36-month period.
  3. The invoice must include a literal description of each item being invoiced (materials, supplies, parts, equipment, labor – installation, fabrication or services). Technical descriptions and/or model or part numbers are not sufficient descriptions.
  4. All costs including baseline items should not exceed 2 decimal places.
  5. Any discounts/allowances/charges may be sent in a SAC segment in the summary section of the invoice. Only once SAC segment per SAC code is allowed.
  6. Not all purchase orders will be sent EDI. Only those orders sent EDI should be invoiced through EDI. If you have any questions concerning this, you should contact our Expense Department at 908-688-4223.
  7. Rollout orders are defined as orders placed under one purchase order for multiple “Ship To” locations. Invoicing for rollout orders must be in the form of a consolidated invoice.
  8. Invoices for orders not sent EDI should be mailed according to the Vendor Invoicing Guide for Non-Merchandise Vendors.
  9. Invoices should not be sent for zero cost POs.
Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI sample
    View the latest version of this implementation guide as an interactive webpage
    Powered by
    Build free 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
    Buying Party (Purchaser)
    DTM
    140
    Date/Time Reference
    Max use 10
    Optional
    FOB
    150
    F.O.B. Related Instructions
    Max use 1
    Optional
    detail
    IT1 Loop
    IT1
    010
    Baseline Item Data (Invoice)
    Max use 1
    Required
    PID Loop
    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 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
    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 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
    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

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

    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
    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
    I10
    Interchange Control Standards Identifier
    Required

    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

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

    A control number assigned by the interchange sender

    ISA-14
    I13
    Acknowledgment Requested
    Required
    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
    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
    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,819)
    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

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

    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

    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) 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
    020

    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

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

    Identifying number assigned by issuer

    Usage notes

    The invoice number may contain a maximum of 12 characters.

    The invoice number must not repeat within a 36-month period.

    BIG-03
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD

    • BIG03 is the date assigned by the purchaser to purchase order.
    Usage notes

    Original PO Date

    BIG-04
    324
    Purchase Order Number
    Required
    Min 1Max 22

    Identifying number for Purchase Order assigned by the orderer/purchaser

    Usage notes

    Original PO Number

    REF
    050

    Reference Identification

    RequiredMax use 12

    To specify identifying information

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    Usage notes

    Assigned by BBB.

    IA
    Internal Vendor Number
    REF-02
    127
    Reference Identification
    Required
    Min 1Max 30

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

    Usage notes

    Vendor Number

    N1 Buying Party (Purchaser)
    RequiredMax >1
    Variants (all may be used)
    N1Ship To
    N1
    070

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

    Usage notes

    Bed Bath & Beyond (BBB)
    Christmas Tree Shops (CTS)
    Harmon Stores
    buybuy BABY
    BBB Canada

    N1-03
    66
    Identification Code Qualifier
    Required

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

    Usage notes

    Assigned by BBB.

    92
    Assigned by Buyer or Buyer's Agent
    N1-04
    67
    Identification Code
    Required

    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.
    0010
    Bed Bath & Beyond (BBB)
    0020
    Christmas Tree Shops (CTS)
    0030
    Harmon Stores
    0040
    buybuy BABY
    0060
    Cost Plus
    5050
    BBB Canada
    N1 Ship To
    RequiredMax >1
    Variants (all may be used)
    N1Buying Party (Purchaser)
    N1
    070

    Name

    RequiredMax use 1

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

    Usage notes

    Rollout orders are defined as orders placed under one purchase order for multiple “Ship To” locations. Invoicing for rollout orders must be in the form of a consolidated invoice.

    Example
    N1-01
    98
    Entity Identifier Code
    Required

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

    ST
    Ship To
    N1-02
    93
    Name
    Optional
    Min 1Max 60

    Free-form name

    Usage notes

    Store Name

    N1-03
    66
    Identification Code Qualifier
    Required

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

    Usage notes

    Assigned by BBB.

    92
    Assigned by Buyer or Buyer's Agent
    N1-04
    67
    Identification Code
    Required
    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

    Store Number

    DTM
    140

    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
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    FOB
    150

    F.O.B. Related Instructions

    OptionalMax use 1

    To specify transportation instructions relating to shipment

    Example
    FOB-01
    146
    Shipment Method of Payment
    Required

    Code identifying payment terms for transportation charges

    • FOB01 indicates which party will pay the carrier.
    CC
    Collect
    PP
    Prepaid (by Seller)

    Detail

    IT1 Loop
    RequiredMax >1
    IT1
    010

    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
    IT1-02
    358
    Quantity Invoiced
    Required
    Min 1Max 10

    Number of units invoiced (supplier units)

    IT1-03
    355
    Unit or Basis for Measurement Code
    Required
    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

    Same as UOM Ordered.

    IT1-04
    212
    Unit Price
    Required
    Min 1Max 15

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

    Usage notes

    All costs including baseline items should not exceed 2 decimal places.

    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.
    VN
    Vendor's (Seller's) Item Number
    IT1-07
    234
    Product/Service ID
    Required
    Min 1Max 48

    Identifying number for a product or service

    Usage notes

    Vendor's Item Number

    PID Loop
    OptionalMax >1
    PID
    060

    Product/Item Description

    RequiredMax use 1

    To describe a product or process in coded or free-form format

    Usage notes

    The invoice must include a literal description of each item being invoiced (materials, supplies, parts, equipment, labor – installation, fabrication or services). Technical descriptions and/or model or part numbers are not sufficient descriptions.

    Example
    PID-01
    349
    Item Description Type
    Required

    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
    PID-05
    352
    Description
    Optional
    Min 1Max 80

    A free-form description to clarify the related data elements and their content

    Summary

    TDS
    010

    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).
    SAC Loop
    OptionalMax >1
    SAC
    040

    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

    Any discounts/allowances/charges may be sent in a SAC segment in the summary section of the invoice. Only once SAC segment per SAC code is allowed.

    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
    Required

    Code identifying the service, promotion, allowance, or charge

    H850
    Tax
    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.
    SAC-15
    352
    Description
    Optional
    Min 1Max 80

    A free-form description to clarify the related data elements and their content

    CTT
    070

    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.
    Example
    CTT-01
    354
    Number of Line Items
    Required
    Min 1Max 6

    Total number of line items in the transaction set

    Usage notes

    Number of IT1 Segments present.

    SE
    080

    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

    Sample

    ST*810*000000001
    BIG*20070616*0361045*20070605*5790313-07
    REF*IA*000201937
    N1*BY*Bed Bath & Beyond*92*0010
    N1*ST*EDGEWATER*92*115
    DTM*011*20070616
    FOB*PP
    IT1**24*EA*10.85**VN*001-5376
    PID*F****S-10 SHELF
    IT1**12*EA*49.67**VN*001-5052
    PID*F****SWDV-IWE S/W SIDE SILVER METAL WHITE EDGE BAND
    IT1**6*EA*33.11**VN*001-5425
    PID*F****MC-SWEC-15IP SIDE FOR ENDCAP METAL INSTER 15” SILVER EDGE
    TDS*111840
    SAC*C*H850***6330**********TAX
    CTT*3
    SE*18*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.