Skip to content

Stacksync × Supabase Miami: AI-Native OperationsOct 13Reserve your spot

X12 transaction code

EDI 810 Invoice (X12 810)

EDI 810 is the electronic invoice, the X12 Invoice transaction set, used when a bill is ready for the buyer to process. 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.

Standard
X12
Code
810
Partner references
360
Book an EDI demo ← All trading partners

At a glance

EDI 810 at a glance

What the 810 carries, who sends it to whom, when it goes out, and the segments trading partners list for it.

X12 810 Invoice summary
Document X12 810 Invoice
Business record Accounts-receivable or accounts-payable invoice
Who sends it to whom 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 is sent An order ships or a service is completed against a purchase order and the seller's ERP generates the invoice, usually at shipment confirmation.
Match on Invoice number, purchase order and invoice line
Partner references 360 trading partners in this directory
Related documents X12 850 Purchase Order, X12 856 Ship Notice/Manifest, X12 820 Payment Order/Remittance Advice

Key segments in an EDI 810

The business segments that appear in at least half of the 472 partner document references listed below, most common first. The table leaves out envelope segments (ISA, GS, ST, SE, GE, IEA). Your partner guide sets which segments and elements your account must send.

Segment Name Purpose Partner references
BIG Beginning Segment for Invoice To indicate the beginning of an invoice transaction set and transmit identifying numbers and dates. 472 of 472
IT1 Baseline Item Data (Invoice) To specify the basic and most frequently used line item data for the invoice and related transactions. 472 of 472
TDS Total Monetary Value Summary To specify the total invoice discounts and amounts. 472 of 472
SAC Service, Promotion, Allowance, or Charge Information To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge. 456 of 472
CTT Transaction Totals To transmit a hash total for a specific element in the transaction set. 448 of 472
N1 Party Identification To identify a party by type of organization, name, and code. 434 of 472
ITD Terms of Sale/Deferred Terms of Sale To specify terms of sale. 419 of 472
REF Reference Information To specify identifying information. 414 of 472
PID Product/Item Description To describe a product or process in coded or free-form format. 399 of 472
N4 Geographic Location To specify the geographic place of the named party. 374 of 472

Stacksync connects EDI documents such as the X12 810 to your ERP, CRM and databases with two-way sync. Read the EDI overview, check pricing and security, or book a demo to walk through your partner guide.

Implementation guide

X12 810 mapping and validation

X12 810 Invoice is used when a bill is ready for the buyer to process. Preserve invoice number, purchase order and invoice line so the accounts-receivable or accounts-payable invoice in your business system stays connected to the original document.

Use the version and implementation guide agreed with your trading partner to confirm required fields and responses.

Map records and test the business result
Document or decisionRecord and matching IDsWhat to test
Match the business record accounts-receivable or accounts-payable invoice

invoice number, purchase order and invoice line
  • Define which combination of invoice number, purchase order and invoice line identifies one business record, its lines and any later revision.
Update the receiving system Processing the accounts-receivable or accounts-payable invoice

ID assigned by the receiving system and processing result
  • Reconcile line amounts, allowances, charges and tax to the invoice total.
  • Submit the same invoice twice and verify that it cannot create a second payable.
Check the processing result Processing status for the accounts-receivable or accounts-payable invoice

Original document reference and matching response
  • Reconcile the accounts-receivable or accounts-payable invoice with the source after a timeout before sending it again. A lost response can occur after the destination has already processed the document.

How the related documents differ

Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately.

Implementation steps

  1. Choose the starting event and owner

    Decide which application acts when a bill is ready for the buyer to process. Name the operational owner of the accounts-receivable or accounts-payable invoice and the team that resolves rejected or ambiguous messages.

  2. Keep record IDs connected

    Map invoice number, purchase order and invoice line. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and partner guide. Preserve the source reference alongside any new destination identifier.

  3. Test failures before launch

    Run the failure cases in the mapping table against realistic accounts-receivable or accounts-payable invoice data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.

  4. Track every document to completion

    Record transport delivery and document validation separately from successful accounts-receivable or accounts-payable invoice processing. Give unresolved errors an owner and check the receiving system before approving retries.

Go-live checklist

  • An approved 810 sample and the agreed version and partner guide are available.
  • The mapping tests pass with realistic accounts-receivable or accounts-payable invoice data.
  • Each submitted document can be traced through delivery, validation and processing in the receiving system.
  • Your team knows how to investigate and recover a rejected or timed-out accounts-receivable or accounts-payable invoice without processing it twice.

Document structure

X12 810 Invoice at the element level

The X12 810 reference contains 46 segment entries and 209 data elements; 60 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.

Segments
46
Data elements
209
Mandatory elements
60
Segments with elements marked mandatory in this reference
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

Find your trading partner for X12 810

360 partners, 473 channels. Choose a channel to inspect its listed document reference and implementation context.

Catalog breakdown

Where X12 810 Invoice appears in this catalog

The largest groups of classified 810 catalog entries are in retail, grocery & food and apparel & footwear.

By industry

  • retail 85 channels
  • grocery & food 80 channels
  • apparel & footwear 62 channels
  • building & hardware 61 channels
  • furniture & home 41 channels
  • healthcare & pharma 34 channels

By network

  • SPS Commerce 91 channels
  • Epicor Eclipse 44 channels
  • TrueCommerce 25 channels
  • Rithum 20 channels
  • Logicbroker 9 channels
  • iTradeNetwork 8 channels
Partner entries with the most listed channels

FAQ

EDI 810 questions

What is an EDI 810?

EDI 810 is the electronic invoice, the X12 Invoice transaction set. Trading partners use it when a bill is ready for the buyer to process. It carries the data for the accounts-receivable or accounts-payable invoice, and your system matches it on invoice number, purchase order and invoice line.

Who sends an EDI 810 and who receives it?

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. Your trading partner agreement confirms the direction and version for your account.

When is an EDI 810 sent?

An order ships or a service is completed against a purchase order and the seller's ERP generates the invoice, usually at shipment confirmation. Your partner guide sets any deadline or schedule for the document.

What are the key segments in an EDI 810?

Across 472 partner document references listed here, the business segments that appear most often include BIG (Beginning Segment for Invoice), IT1 (Baseline Item Data (Invoice)), TDS (Total Monetary Value Summary), SAC (Service, Promotion, Allowance, or Charge Information), CTT (Transaction Totals), N1 (Party Identification). Each partner guide sets which segments and elements your account must send.

What is the difference between EDI 810 and EDI 850?

The 850 is the order and the 810 is the bill for it. The 810 quotes the 850's purchase order number, and the buyer matches the invoice's prices and quantities to the order before paying.

What is the difference between EDI 810 and EDI 856?

The 856 tells the buyer what shipped, and the 810 bills for it. Many buyers match the 810 against both the 850 and the 856 before they pay.

What should I map for X12 810?

Start with invoice number, purchase order and invoice line and the target accounts-receivable or accounts-payable invoice. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats.

How should I test 810 error handling?

Reconcile line amounts, allowances, charges and tax to the invoice total. Submit the same invoice twice and verify that it cannot create a second payable. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.

Connect EDI to your business systems

See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.

Book an EDI demo Explore the EDI platform