EDI 810 Invoice: Complete Guide

The EDI 810 is the X12 transaction set for electronic invoices. Vendors send it to buyers to request payment for goods or services delivered, almost always referencing the original 850 Purchase Order via BIG04. It is the billing-side counterpart to the 850 and the document that closes the order-to-cash loop in EDI.

This guide walks through the structure of an 810, shows three real examples (Walmart, Amazon Vendor Central, and a generic invoice) with our interactive renderer, and covers the partner-specific gotchas that trigger chargebacks and payment delays.

What is an EDI 810?

An EDI 810 Invoice is a structured electronic billing document defined by the ASC X12 standards body for vendor-to-buyer payment requests. It carries the same data as a paper invoice (line items, totals, terms, remittance) but in a fixed, machine-readable format that buyer ERPs can three-way match against the original 850 PO and the 856 ASN without human re-keying.

A typical 810 contains:

• Invoice number and date
• Reference to the original purchase order
• Line item details (quantity shipped, unit price)
• Subtotals, taxes, and shipping charges
• Payment terms and due date
• Remittance information

For trading partner specifics, vendors typically work from authoritative public docs:

• The X12.org Implementation Guidelines define the base 810 structure used by all retailers
• GS1 US governs the GTIN/UPC identifiers carried in IT108-IT109 and the SCAC carrier codes referenced in invoice and ASN segments
• Most retailers publish their own EDI implementation guides (Walmart Retail Link, Amazon Vendor Central, Target Partners Online), which extend the base spec with required references and qualifiers

Interactive Example: Walmart 810 Invoice

Walmart 810s reference the original PO number in BIG04 and require a SCAC code, BOL number, and department reference. Use the Plain English tab below for a human-readable translation, the Split View to see raw and parsed side-by-side, or click any segment to break it down element-by-element.

Interactive Example: Amazon Vendor Central 810

Amazon Vendor Central invoices use ASINs in the line items, must arrive before goods reach the FC, and apply Amazon-specific allowances via SAC*A segments.

Interactive Example: Generic 810 Invoice

A standard 810 with payment terms (1% 15, Net 30), freight (CAD), tax (TXI), and handling charges (SAC):

Key Segments Explained

BIG - Beginning Segment for Invoice

The BIG segment contains invoice header information:

• BIG01: Invoice date (CCYYMMDD format)
• BIG02: Invoice number
• BIG04: Purchase order number (reference to original 850)

ITD - Terms of Sale/Deferred Terms of Sale

Payment terms are critical for cash flow management:

ITD*01*3*1*20231221*15**30

• ITD01: Terms type code (01 = Basic)
• ITD02: Terms basis date code (3 = Invoice date)
• ITD03: Terms discount percent (1 = 1%)
• ITD04: Terms discount due date
• ITD05: Terms discount days due (15 days for discount)
• ITD07: Terms net days (30 days net)

Translation: "1% discount if paid within 15 days, net 30 days"

IT1 - Baseline Item Data (Invoice)

Each IT1 segment represents one invoiced line item:

• IT101: Line item number
• IT102: Quantity invoiced
• IT103: Unit of measure
• IT104: Unit price
• IT106-IT107: Part number identifier
• IT108-IT109: UPC identifier

TDS - Total Monetary Value Summary

Summary segments show the financial breakdown:

TDS*309900          // Subtotal: $3,099.00
CAD*C*FREIGHT***150000  // Freight charge: $1,500.00
TXI*TX*250*5        // Sales tax: $250.00
SAC*C*D500*******125000 // Handling charge: $1,250.00
TDS*323150          // Total amount due: $3,231.50

Invoice Calculation Breakdown

Line Items

Line 1: 100 × $15.99 = $1,599.00
Line 2:  50 × $29.99 = $1,499.50
                       ─────────
Subtotal:              $3,098.50

Additional Charges

Freight:               $1,500.00
Handling:              $1,250.00
Sales Tax (5%):        $  250.00
                       ─────────
Total Amount Due:      $3,231.50

Payment Terms

Invoice Date:    11/21/2023
Discount Terms:  1% if paid by 12/06/2023
Net Terms:       Pay by 12/21/2023

Common Use Cases

1. Standard Invoice After Shipment

The most common flow:

1. Receive 850 Purchase Order
2. Ship goods and send 856 ASN
3. Send 810 Invoice (usually within 24-48 hours of shipment)
4. Receive payment within net terms

2. Consolidated Invoice

Some trading partners prefer consolidated invoices:

• Multiple shipments on one invoice
• Weekly or monthly billing cycles
• Includes all deliveries for a period

3. Credit/Debit Adjustments

Use 810 for adjustments:

• Price corrections
• Quantity discrepancies
• Damaged goods credits
• Promotional allowances

Use special codes in BIG segment:

• BIG03: Credit/Debit flag (C = Credit, D = Debit)

Matching 810 to 850 Purchase Order

Critical Matching Fields

When the buyer receives your 810, their system will match it to the original 850:

Important: If quantity or price differs from the 850:

• Document the reason (partial shipment, price change)
• May trigger a dispute resolution process
• Could delay payment

Payment Terms Code Quick Reference

Common ITD codes you'll encounter:

Tax and Charges

TXI - Tax Information

TXI*TX*250*5***STATE SALES TAX

• TXI01: Tax type (TX = Sales Tax)
• TXI02: Tax amount in cents ($250.00)
• TXI03: Tax percent (5%)
• TXI06: Description

SAC - Service, Promotion, Allowance, or Charge

SAC*C*D500*******125000

• SAC01: Allowance or charge indicator (C = Charge, A = Allowance)
• SAC02: Service/charge code (D500 = Handling)
• SAC09: Amount in cents ($1,250.00)

CAD - Carrier Detail

CAD*C*FREIGHT***150000

• Freight charges
• Amount in cents ($1,500.00)

Implementation Best Practices

1. Timely Invoice Submission

Trading partner requirements vary:

• Walmart: Within 24 hours of shipment
• Target: Within 48 hours of delivery
• Amazon: Before goods arrive at FC

Late invoices can result in:

• Payment delays
• Chargebacks
• Compliance violations

2. Accurate Reference Numbers

Always include:

• ✅ Original PO number (BIG04)
• ✅ ASN/BOL number (REF*BM segment)
• ✅ Delivery ticket number (REF*DT)
• ✅ Department number if required (REF*DP)

3. Price and Quantity Validation

Before sending 810:

• ✅ Verify prices match 850 or approved changes
• ✅ Confirm quantities shipped match invoice
• ✅ Check for promotional pricing agreements
• ✅ Validate tax calculations

4. Currency and Amounts

Critical: All monetary amounts in EDI are in cents (no decimal point):

❌ TDS*3099.00  // WRONG - Don't include decimal
✅ TDS*309900   // CORRECT - Amount in cents

Common Errors to Avoid

1. Missing Purchase Order Reference

❌ BIG*20231121*INV-001234  // Missing PO reference
✅ BIG*20231121*INV-001234**PO-987654  // Correct

2. Incorrect Amount Format

❌ TDS*3,099.00  // Commas and decimals not allowed
✅ TDS*309900    // Cents only, no punctuation

3. Missing Tax Information

❌ No TXI segment when tax charged
✅ TXI*TX*250*5***STATE SALES TAX

4. Invalid Terms Format

❌ ITD*Net 30 Days  // Text not allowed
✅ ITD*01*3*0****30  // Proper code structure

Testing Your 810 Implementation

Use our EDI Inspector to:

• Validate mathematical accuracy
• Check reference number formats
• Verify segment structure
• Test matching logic against 850

Integration with Other Transaction Sets

The Complete Order-to-Cash Flow

1. 850 Purchase Order     → Buyer sends order
2. 855 PO Acknowledgment  → You confirm order
3. 856 ASN               → You notify shipment
4. 810 Invoice (YOU)     → You request payment
5. 820 Payment Remittance → Buyer sends payment details

How the 810 Relates to Other EDI Documents

The 810 sits near the end of the order cycle, between the shipment and the payment. This table shows how it connects to the order, the ship notice, and the remittance.

The 810 should bill for what the 856 reported as shipped, and the buyer responds with an 820 carrying the remittance once the invoice clears their three-way match.

Related Transaction Sets

• 850 Purchase Order - Original order reference
• 856 Ship Notice - Shipment notification
• 997 Functional Acknowledgment - Receipt confirmation
• 820 Payment Order/Remittance - Payment notification

Compliance Tips

Walmart Specific

• Must include SCAC code for carrier
• Require BOL number reference
• Strict 24-hour submission window

Target Specific

• Include original ship-to location code
• Department number mandatory
• Store number in reference segments

Amazon Vendor Central

• ASIN must match exactly
• Invoice must arrive before goods
• Routing number validation

Frequently Asked Questions

What is the difference between an EDI 810 and a 210?

The 810 is the standard X12 invoice for retail and distribution trading partners. The 210 is the freight-specific version used by carriers (LTL, parcel, ocean) to bill shippers for transportation services. They share concepts but use different segments — for example, the 210 uses B3 instead of BIG, and it ties to bill of lading numbers rather than purchase orders.

Does the 810 invoice have to match the 850 exactly?

No, but mismatches need to be explainable. Most buyer ERPs run a three-way match between the 850 (what was ordered), the 856 ASN (what was shipped), and the 810 (what is being billed). Quantity differences are normally fine when there was a partial shipment. Price differences usually require a documented reason (an approved price change, a promotional allowance), or the invoice will be flagged for dispute and held from payment.

How fast does an 810 need to be sent after shipment?

It depends on the trading partner. Walmart requires the invoice within 24 hours of shipment, Target within 48 hours of delivery, and Amazon Vendor Central typically requires it before the goods arrive at the FC. Late invoices are a common cause of chargebacks and aging-driven payment delays.

What format are amounts in on an EDI 810?

All monetary amounts in EDI are expressed as integers with implied decimal places — usually cents with no decimal point. So TDS*309900 represents $3,099.00, not $309,900.00. Decimal points and thousands separators in amount fields are non-compliant and most translators will reject them.

Do all 810s carry tax information?

No. If the buyer is tax-exempt (typical for big-box retailers like Walmart that handle tax themselves at point-of-sale), the TXI segment is omitted or set to zero with an exemption note. If you charge tax incorrectly, the buyer's AP system will flag the invoice and short-pay or reject it. Always confirm a partner's tax handling in their EDI implementation guide.

What is the difference between EDI 810 and 820?

The 810 is the invoice and the 820 is the payment. The supplier sends the 810 to request payment for a shipment. The buyer sends the 820 Payment Order/Remittance Advice back to report that payment is being made and which invoices it covers. In short, the 810 asks for money and the 820 explains the money being sent. The 820 often accompanies an ACH or wire transfer and lets the supplier's accounts receivable team apply the cash to the right invoices automatically.

What is the difference between EDI 810 and 850?

The 850 is the purchase order the buyer sends to place an order; the 810 is the invoice the supplier sends to get paid for it. The 850 comes first and defines what was ordered and the expected price. The 810 comes after shipment, references the 850's PO number in BIG04, and bills for what was actually shipped. The 850 starts the order-to-cash cycle and the 810 closes it.

Need Help?

Try our free EDI inspector to validate your 810 invoices or contact our team for implementation support and compliance verification.