Skip to content

X12 transaction code

X12 880 Grocery Products Invoice

X12 880 Grocery Products Invoice: explore its business purpose, mapping identifiers, validation tests and 33 partner references across 36 listed channels.

Standard
X12
Code
880
Partner references
33

Implementation guide

X12 880 mapping and validation

X12 880 Grocery Products Invoice is used when grocery goods are ready for detail billing. Preserve invoice, grocery order and item so the grocery 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 grocery invoice

invoice, grocery order and item

  • Define which combination of invoice, grocery order and item identifies one business record, its lines and any later revision.
Update the receiving system Processing the grocery invoice

ID assigned by the receiving system and processing result

  • Reconcile quantity units and allowances before posting the invoice.
  • Test a duplicate invoice while keeping an authorized correction traceable.
Check the processing result Processing status for the grocery invoice

Original document reference and matching response

  • Reconcile the grocery 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 grocery goods are ready for detail billing. Name the operational owner of the grocery invoice and the team that resolves rejected or ambiguous messages.

  2. Keep record IDs connected

    Map invoice, grocery order and item. 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 grocery 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 grocery invoice processing. Give unresolved errors an owner and check the receiving system before approving retries.

Go-live checklist

  • An approved 880 sample and the agreed version and partner guide are available.
  • The mapping tests pass with realistic grocery 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 grocery invoice without processing it twice.

Document structure

X12 880 Grocery Products Invoice at the element level

The X12 880 reference contains 33 segment entries and 180 data elements; 58 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.

Segments
33
Data elements
180
Mandatory elements
58
Segments with elements marked mandatory in this reference
Segment Elements Mandatory
G01 6 2
N9 5 1
G61 5 2
NTE 2 1
G27 6 1
G23 16 2
G25 3 2
N1 4 1
N2 2 1
N3 2 1
G72 11 2
G73 1 1
Key identifiers in 880
  • Date
  • Invoice Number
  • Reference Identification Qualifier
  • Contact Function Code
  • Name
  • Description
  • Transportation Method/Type Code
  • Terms Type Code

Find your trading partner for X12 880

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

Catalog breakdown

Where X12 880 Grocery Products Invoice appears in this catalog

The largest groups of classified 880 catalog entries are in grocery & food.

By industry

  • grocery & food 36 channels

By network

  • Edict Systems 5 channels
  • SPS Commerce 3 channels

FAQ

X12 880 questions

What is X12 880 Grocery Products Invoice used for?

880 is used when grocery goods are ready for detail billing. It carries information for the grocery invoice. Match it to your business system using invoice, grocery order and item.

Which partners list X12 880?

The directory on this page links 33 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 880?

Start with invoice, grocery order and item and the target grocery 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 880 error handling?

Reconcile quantity units and allowances before posting the invoice. Test a duplicate invoice while keeping an authorized correction traceable. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.

How does 880 relate to other EDI messages?

X12 875 Grocery Products Purchase Order; X12 879 Price Information; 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 880 and 875?

880 is used when grocery goods are ready for detail billing. 875 is used when a grocery buyer places an order. 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.