Skip to content
X12 EDI

Wiz X12 810 Invoice

Plan X12 810 Invoice for Wiz / Out Me. Connect document identifiers to your business records, test exception handling and track each exchange to completion.

Segments
Not listed
Loops
Not listed
X12 810
Partner references ↗

Implementation guide

Wiz / Out Me: 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.

This document is listed for Wiz / Out Me. Confirm the version, required fields and responses that apply to your account.

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.

Segment and field details are not available for this document here. Request the current partner guide and a sample document to complete the field mapping.

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

Transaction context

Where 810 Invoice fits on Out Me

Wiz channels
1 of 2

1 of Wiz's 2 channels list 810

Trading partners
360

partner references list 810

Channels
473

channel entries list 810

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

Wiz / Out Me EDI 810 questions

Common questions about 810 Invoice on the Out Me channel.

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.

Is 810 required for Wiz / Out Me?

810 is listed for Wiz / Out Me. Confirm the required version and direction for your business unit and account with the partner.

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?

Keep 810 business processing separate from transport receipt and technical validation. Agree which preceding record, response or reconciliation completes the accounts-receivable or accounts-payable invoice workflow; confirm any required companion messages with your partner.

Connect Wiz 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.