Skip to content

X12 transaction code

X12 810 Invoice

X12 810 Invoice: explore its business purpose, mapping identifiers, validation tests and 360 partner references across 473 listed channels.

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

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

X12 810 questions

What is X12 810 Invoice used for?

810 is used when a bill is ready for the buyer to process. It carries information for the accounts-receivable or accounts-payable invoice. Match it to your business system using invoice number, purchase order and invoice line.

Which partners list X12 810?

The directory on this page links 360 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires.

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.

How does 810 relate to other EDI messages?

X12 850 Purchase Order; X12 856 Ship Notice Manifest; X12 820 Payment Order Remittance Advice are related documents linked from this page. Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete.

What is the difference between 810 and 850?

810 is used when a bill is ready for the buyer to process. 850 is used when a buyer places an order. Each message represents a different business step. Keep their record references connected and track the processing result for each message.

What is the difference between 810 and 856?

810 is used when a bill is ready for the buyer to process. 856 is used when shipment contents are known before the agreed notification deadline. Each message represents a different business step. Keep their record references connected and track the processing result for each message.

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