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

X12 810 Drop Ship 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
  • None included
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/macys/drop-ship-invoice/01HBXV0A265PCB31SK43DDS5RZ
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 1
Optional
N1 Loop
N1 Loop Rest All
ITD
1300
Terms of Sale/Deferred Terms of Sale
Max use 1
Required
DTM
1400
Date/Time Reference
Max use 1
Optional
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 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
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 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
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

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

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

08
UCC EDI Communications ID (Comm ID)
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
I65
Repetition Separator
Required
String (AN)
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
Identifier (ID)

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
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 indicating sender's request for an interchange acknowledgment

0
No Acknowledgment Requested
1
Interchange Acknowledgment Requested
ISA-15
I14
Usage Indicator
Required
Identifier (ID)
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
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)
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 where CC represents the first two digits of the calendar year

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

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

Heading

ST
0100
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) 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
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
0200
Heading > BIG

Beginning Segment for Invoice

RequiredMax use 1

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

Example
Required
Date (DT)
CCYYMMDD format

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

  • BIG01 is the invoice issue date.
Usage notes

CCYYMMDD; date invoice was generated (Invoice date cannot be
later than transmission date).

BIG-02
76
Invoice Number
Required
String (AN)
Min 1Max 22

Identifying number assigned by issuer

Usage notes

Identifying # from issuer. Each invoice number must be unique. MACY’S system will only process numeric characters. Ten of the most significant numeric characters will be processed.

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

Identifying number for Purchase Order assigned by the orderer/purchaser

Usage notes

Identifying # from Purchaser. Valid Macy’s Purchase Order number. Must be numeric only.

REF
0500
Heading > REF

Reference Identification

OptionalMax use 1

To specify identifying information

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

Code qualifying the Reference Identification

Usage notes

DP- Department Number

DP
Department Number
REF-02
127
Reference Identification
Required
String (AN)
Min 1Max 50

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

Usage notes

4-digit numeric Department Number (leading zero plus 3 digit dept number)

N1 Loop
OptionalMax 1
Variants (all may be used)
N1 Loop Rest All
N1
0700
Heading > N1 Loop > N1

Name

RequiredMax use 1

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

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
Required
String (AN)
Min 1Max 60

Free-form name

N4
1000
Heading > N1 Loop > N4

Geographic Location

OptionalMax use 1

To specify the geographic place of the named party

Example
N4-01
19
City Name
Optional
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
Optional
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
Optional
Identifier (ID)
Min 3Max 15

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

N1 Loop end
N1 Loop Rest All
RequiredMax 3
Variants (all may be used)
N1 Loop
N1
0700
Heading > N1 Loop Rest All > N1

Name

RequiredMax use 1

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

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

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

BY
Buying Party (Purchaser)
RI
Remit To
ST
Ship To
N1-03
66
Identification Code Qualifier
Required
Identifier (ID)

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

1
D-U-N-S Number, Dun & Bradstreet
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.
0149
Macy’s VDF location
0158
Bloomingdale’s VDF location
DS
N1 Loop Rest All end
ITD
1300
Heading > ITD

Terms of Sale/Deferred Terms of Sale

RequiredMax use >1

To specify terms of sale

Example
ITD-01
336
Terms Type Code
Optional
Identifier (ID)

Code identifying type of payment terms

  • If the code in ITD01 is "04", then ITD07 or ITD09 is required and either ITD10 or ITD11 is required; if the code in ITD01 is "05", then ITD06 or ITD07 is required.
01
Basic

(uses invoice date as due date unless the ITD01 = 2)

02
End of Month (EOM)
05
Discount Not Applicable

uses invoice
date as due date unless the ITD02 = 2

08
Basic Discount Offered

uses invoice date as due date unless the ITD02 = 2

12
10 Days After End of Month (10 EOM)
ITD-02
333
Terms Basis Date Code
Optional
Identifier (ID)

Code identifying the beginning of the terms period

Usage notes

1 – Ship Date
2 – Delivery Date or Receipt Date
3 – Invoice Date
15 – ROG (Receipt of Goods)

1
Ship Date
2
Delivery Date
3
Invoice Date
15
Receipt of Goods
ITD-03
338
Terms Discount Percent
Optional
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

Usage notes

Terms Discount percentage available to buyer. Expressed as %—Decimal point only used when needed (8.00 would be sent as 8 and 8.50 would be sent as 8.5).

ITD-05
351
Terms Discount Days Due
Optional
Numeric (N0)
Min 1Max 3

Number of days in the terms discount period by which payment is due if terms discount is earned

Usage notes

Number of days in the Terms Discount period

ITD-07
386
Terms Net Days
Optional
Numeric (N0)
Min 1Max 3

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

Usage notes

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

DTM
1400
Heading > DTM

Date/Time Reference

OptionalMax use 1

To specify pertinent dates and times

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 where CC represents the first two digits of the calendar year

Usage notes

Date Shipped

Heading end

Detail

IT1 Loop
RequiredMax 200000
Usage notes

MACY’S only receives transmissions at the UPC level.

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

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
If either Product/Service ID Qualifier (IT1-06) or Product/Service ID (IT1-07) is present, then the other is required
IT1-02
358
Quantity Invoiced
Optional
Decimal number (R)
Min 1Max 10

Number of units invoiced (supplier units)

Usage notes

Number of Units Invoiced

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

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

Usage notes

Terms Discount percentage available to buyer. Expressed as %—Decimal point only used when needed (8.00 would be sent as 8 and 8.50 would be sent as 8.5).

EA
Each
IT1-04
212
Unit Price
Optional
Decimal number (R)
Min 1Max 15

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

Usage notes

Price per Unit, the price is sent with the decimal point only when needed
($15.95 would be sent as 15.95 and $29.00 would be sent as 29).

IT1-06
235
Product/Service ID Qualifier
Optional
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.
Usage notes

UP – UPC number
EN – European Article Number
UK – GTIN

EN
European Article Number

EAN Number (13 Digits)

UK
GTIN

GTIN Number (14 Digits)

UP
UPC number

UPC Number (12 Digits)

IT1-07
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

UPC Number (12 Digits)
EAN Number (13 Digits)
GTIN Number (14 Digits)

PID Loop
OptionalMax 1000
PID
0600
Detail > IT1 Loop > PID Loop > PID

Product/Item Description

RequiredMax use 1

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

Example
PID-01
349
Item Description Type
Required
Identifier (ID)

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

F – Free-form

F
Free-form
PID-05
352
Description
Optional
String (AN)
Min 1Max 80

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

Usage notes

Vendor Style Number/Description

PID Loop end
IT1 Loop end
Detail end

Summary

TDS
0100
Summary > TDS

Total Monetary Value Summary

RequiredMax use 1

To specify the total invoice discounts and amounts

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

Total amount of invoice (including charges, less allowances) before terms
discount (if discount is applicable), (no decimal necessary, two decimal places are implied; for example, $8.00 will be sent as 800).

TDS-02
610
Amount
Optional
Numeric (N2)
Min 1Max 15

Monetary amount

  • TDS02 indicates the amount upon which the terms discount amount is calculated.
  • TDS02 is required if the dollar value subject to discount is not equal to the dollar value of TDS01.
Usage notes

The amount upon which the terms discount amount is calculated (no
decimal necessary, two decimal places are implied).

CAD
0300
Summary > CAD

Carrier Detail

RequiredMax use 1

To specify transportation details for the transaction

Usage notes

2 to 4 Digit Carrier Code (SCAC Code) (See External Code Source 17 in Section III for reference document)

Example
At least one of Standard Carrier Alpha Code (CAD-04) or Routing (CAD-05) is required
If Reference Identification Qualifier (CAD-07) is present, then Reference Identification (CAD-08) is required
CAD-04
140
Standard Carrier Alpha Code
Optional
Identifier (ID)
Min 2Max 4

Standard Carrier Alpha Code

CAD-05
387
Routing
Optional
String (AN)
Min 1Max 35

Free-form description of the routing or requested routing for shipment, or the originating carrier's identity

Usage notes

Carrier Description

CAD-07
128
Reference Identification Qualifier
Optional
Identifier (ID)

Code qualifying the Reference Identification

Usage notes

BM – Bill of Lading or tracking number

BM
Bill of Lading Number
CAD-08
127
Reference Identification
Optional
String (AN)
Min 1Max 50

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

Usage notes

Bill of Lading Number or tracking number from lead carton per location (Small package carriers, i.e. UPS or RPS)

SAC Loop
OptionalMax >1
SAC
0400
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

Example
At least one of Service, Promotion, Allowance, or Charge Code (SAC-02) or Agency Qualifier Code (SAC-03) is required
If either Agency Qualifier Code (SAC-03) or Agency Service, Promotion, Allowance, or Charge Code (SAC-04) is present, then the other is required
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.
C
Charge
SAC-02
1300
Service, Promotion, Allowance, or Charge Code
Optional
Identifier (ID)

Code identifying the service, promotion, allowance, or charge

C040
Delivery
D500
Handling
ZZZZ
Mutually Defined
SAC-03
559
Agency Qualifier Code
Optional
Identifier (ID)

Code identifying the agency assigning the code values

Usage notes

VI – Voluntary Inter-Industry Commerce Standard (VICS) EDI

VI
Voluntary Inter-Industry Commerce Standard (VICS) EDI
SAC-04
1301
Agency Service, Promotion, Allowance, or Charge Code
Optional
String (AN)

Agency maintained code identifying the service, promotion, allowance, or charge

  • SAC04 may be used to uniquely identify the service, promotion, allowance, or charge. In addition, it may be used in conjunction with SAC03 to further define SAC02.
Usage notes

GW – Gift Wrap

GW
SAC-05
610
Amount
Optional
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

This data element has an implied decimal point with 2 digits to the right of the decimal point; for example, $29.00 will be sent as 2900.

SAC-12
331
Allowance or Charge Method of Handling Code
Optional
Identifier (ID)

Code indicating method of handling for an allowance or charge

Usage notes

02 – Off Invoice (Allowances)

02
Off Invoice
SAC-15
352
Description
Optional
String (AN)
Min 1Max 80

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

Usage notes

Free-Form

SAC Loop end
ISS Loop
RequiredMax >1
ISS
0600
Summary > ISS Loop > ISS

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
ISS-01
382
Number of Units Shipped
Optional
Decimal number (R)
Min 1Max 10

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

Usage notes

Total Quantity Cartons Shipped.

ISS-02
355
Unit or Basis for Measurement Code
Optional
Identifier (ID)

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

Usage notes

CT – Carton

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

Total number of line items in the transaction set

Usage notes

Total Number of Line Items in Transaction Set.

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

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.