To start and identify an interchange of zero or more functional groups and interchange-related control segments
DSW Inc. X12 810 Invoice
X12 810 (Invoice) is the EDI transaction exchanged between DSW Inc. (DSW Dropship (via DSCO (dba Rithum))) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 22
- Loops
- 6
- X12 810
- All partners ↗
Transaction context
Where 810 Invoice fits on DSW Dropship (via DSCO (dba Rithum))
On DSW Dropship (via DSCO (dba Rithum)), the X12 810 Invoice follows the 850 Purchase Order and 856 Ship Notice Manifest in the Order-to-cash cycle.
- DSW Inc. channels
- 1 of 2
- Trading partners
- 360
- Channels
- 473
1 of DSW Inc.'s 2 channels carries 810
partners across the Stacksync network trade 810
channels network-wide carry 810
Most common alongside 810
On Rithum, 810 runs on 20 channels.
The X12 810 is the electronic invoice a supplier issues against a purchase order. It carries the invoice number and date (BIG), the PO reference, line items with quantity, unit price, and unit of measure (IT1), allowances and charges (SAC), and the total amount due (TDS). Buyers require it so accounts payable can match invoices against purchase order and receipt data automatically, and a clean 810 is a precondition for on-time payment. The supplier or seller sends the 810 to the buyer (retailer, distributor, or manufacturer) after shipping the order, closing the loop opened by the EDI 850 purchase order.
When it fires: An order ships or a service is completed against a purchase order and the seller's ERP generates the invoice, usually at shipment confirmation.
Common 810 rejection causes
- PO number mismatch: if BIG04 does not echo the buyer's 850 exactly, the invoice lands in a rejection queue and payment stalls.
- TDS totals computed anywhere other than from the line data, or with rounding that differs from the buyer's standard, cause the AP system to hold or short-pay the invoice.
- Stale party or location code tables in the N1 loop produce invalid ship-to deductions and misapplied cash receipts.
- Invoiced quantities that conflict with the EDI 856 ASN, or unapproved SAC allowance and charge codes, drive short-pays and repeat deduction research.
Specification summary
X12 810 Invoice at the element level
The X12 810 specification defines 46 segments carrying 209 data elements, 60 of which are mandatory.
- Segments
- 46
- Data elements
- 209
- Mandatory elements
- 60
| Segment | Elements | Mandatory |
|---|---|---|
| BIG | 7 | 2 |
| NTE | 2 | 1 |
| CUR | 4 | 2 |
| REF | 3 | 1 |
| N1 | 4 | 1 |
| N2 | 2 | 1 |
| N3 | 2 | 1 |
| PER | 8 | 1 |
| DTM | 4 | 1 |
| N9 | 3 | 1 |
| MSG | 2 | 1 |
Key identifiers in 810
- Date
- Invoice Number
- Description
- Entity Identifier Code
- Currency Code
- Reference Identification Qualifier
- Name
- Address Information
Full segment guideline — 22 segments 6 loops · X12 810 Invoice
To indicate the beginning of a functional group and to provide control information
To indicate the start of a transaction set and to assign a control number
To indicate the beginning of an invoice transaction set and transmit identifying numbers and dates
To specify the currency (dollars, pounds, francs, etc.) used in a transaction
To specify identifying information
N1 Loop Repeat: 200
To identify a party by type of organization, name, and code
To specify additional names
To specify the location of the named party
To specify the geographic place of the named party
To specify terms of sale
To specify pertinent dates and times
To describe a product or process in coded or free-form format
IT1 Loop Repeat: 200,000
To specify the basic and most frequently used line item data for the invoice and related transactions
PID Loop Repeat: 1,000
To specify the total invoice discounts and amounts
To indicate the total monetary amount
SAC Loop
To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge
ISS Loop
To specify summary details of total items shipped in terms of quantity, weight, and volume
To transmit a hash total for a specific element in the transaction set
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
To identify a person or office to whom administrative communications should be directed
SLN Loop Repeat: 1,000
To specify product subline detail item data
Trading partners
4+ trading partners.
And every channel covered.
We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.
No trading partner matches your search.
Browse the full directory
DSW Inc. DSW Dropship (via DSCO (dba Rithum)) EDI 810 FAQ
Common questions about 810 Invoice on the DSW Dropship (via DSCO (dba Rithum)) channel.
What is X12 810 Invoice?
X12 810 (Invoice) is the EDI transaction set used to exchange invoice data. DSW Inc.'s DSW Dropship (via DSCO (dba Rithum)) channel requires it from trading partners.
Does DSW Inc. DSW Dropship (via DSCO (dba Rithum)) require 810 for trading partners?
Yes, DSW Inc. (DSW Dropship (via DSCO (dba Rithum))) supports X12 810 Invoice. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate DSW Inc. 810 with Stacksync?
Most companies go live with DSW Inc. 810 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which documents accompany 810 on DSW Dropship (via DSCO (dba Rithum))?
On DSW Dropship (via DSCO (dba Rithum)), X12 810 is typically exchanged alongside 850 Purchase Order, 856 Ship Notice Manifest, 846 Inventory Inquiry Advice. Stacksync maps each document into the same ERP or WMS workflow, so the full cycle stays in sync end to end.
Ready to automate your DSW Inc. EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
