Skip to content

EDIFACT transaction code

EDIFACT INVOIC Invoice

EDIFACT INVOIC Invoice: explore its business purpose, mapping identifiers, validation tests and 5 partner references across 5 listed channels.

Standard
EDIFACT
Code
INVOIC
Partner references
5

Implementation guide

EDIFACT INVOIC mapping and validation

EDIFACT INVOIC Invoice is used when billing or an agreed adjustment is ready. Preserve invoice, document function and order references so the invoice or qualified credit/debit note 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 invoice or qualified credit/debit note

invoice, document function and order references

  • Define which combination of invoice, document function and order references identifies one business record, its lines and any later revision.
Update the receiving system Processing the invoice or qualified credit/debit note

ID assigned by the receiving system and processing result

  • Interpret credit and debit document functions before posting amounts.
  • Reconcile monetary totals and avoid duplicate liabilities on retransmission.
Check the processing result Processing status for the invoice or qualified credit/debit note

Original document reference and matching response

  • Reconcile the invoice or qualified credit/debit note 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 billing or an agreed adjustment is ready. Name the operational owner of the invoice or qualified credit/debit note and the team that resolves rejected or ambiguous messages.

  2. Keep record IDs connected

    Map invoice, document function and order references. Confirm qualifiers, code lists, units and date/time meaning against the agreed EDIFACT 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 invoice or qualified credit/debit note 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 invoice or qualified credit/debit note processing. Give unresolved errors an owner and check the receiving system before approving retries.

Go-live checklist

  • An approved INVOIC sample and the agreed version and partner guide are available.
  • The mapping tests pass with realistic invoice or qualified credit/debit note 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 invoice or qualified credit/debit note without processing it twice.

Find your trading partner for EDIFACT INVOIC

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

FAQ

EDIFACT INVOIC questions

What is EDIFACT INVOIC Invoice used for?

INVOIC is used when billing or an agreed adjustment is ready. It carries information for the invoice or qualified credit/debit note. Match it to your business system using invoice, document function and order references.

Which partners list EDIFACT INVOIC?

The directory on this page links 5 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 EDIFACT INVOIC?

Start with invoice, document function and order references and the target invoice or qualified credit/debit note. 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 INVOIC error handling?

Interpret credit and debit document functions before posting amounts. Reconcile monetary totals and avoid duplicate liabilities on retransmission. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.

How does INVOIC relate to other EDI messages?

EDIFACT ORDERS Purchase Order; EDIFACT DESADV Despatch 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 INVOIC and ORDERS?

INVOIC is used when billing or an agreed adjustment is ready. ORDERS 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.

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.