Supply Chain & InventoryFree referencePDF, Excel, Word export

Invoice Document Type Codes: UNTDID 1001, X12 and EDIFACT Reference

Document AI that extracts invoices has to decide whether a page is an invoice, a credit note or a proforma, because each one posts differently. This table lists the standard type codes and the matching EDI messages in one place.

Download:
StandardCodeNameTypical use in AP and purchasing
UNTDID 1001
380
Commercial invoice
Standard supplier invoice; the default type in e-invoicing formats
UNTDID 1001
381
Credit note
Reduces the amount owed, for returns or price corrections
UNTDID 1001
383
Debit note
Increases the amount owed after an original invoice
UNTDID 1001
384
Corrected invoice
Replaces an earlier invoice with corrected data
UNTDID 1001
386
Prepayment invoice
Invoice for an advance payment before delivery
UNTDID 1001
389
Self-billed invoice
Invoice raised by the buyer on behalf of the supplier
UNTDID 1001
325
Proforma invoice
Preliminary invoice for customs or prepayment, not a payment demand
UNTDID 1001
326
Partial invoice
Invoice for part of the goods or services
UNTDID 1001
393
Factored invoice
Invoice assigned to a factoring company that must be paid to the factor
UNTDID 1001
751
Invoice information for accounting purposes
Information copy, not a payment request
ASC X12
810
Invoice
Electronic supplier invoice in North American EDI
ASC X12
812
Credit/Debit Adjustment
Adjusts a prior invoice amount
ASC X12
820
Payment Order/Remittance Advice
Payment and remittance detail from buyer to supplier
ASC X12
824
Application Advice
Reports acceptance or rejection of a business document at application level
ASC X12
850
Purchase Order
Order from buyer; first leg of three way match
ASC X12
855
Purchase Order Acknowledgment
Supplier confirms or changes the order
ASC X12
856
Ship Notice/Manifest
Advance ship notice (ASN) sent by the supplier
ASC X12
860
Purchase Order Change Request - Buyer Initiated
Buyer changes an open order
ASC X12
861
Receiving Advice/Acceptance Certificate
Buyer confirms receipt; supports evaluated receipt settlement
ASC X12
865
Purchase Order Change Acknowledgment/Request - Seller Initiated
Seller proposes or confirms order changes
ASC X12
997
Functional Acknowledgment
Confirms an EDI interchange was received and syntactically accepted
UN/EDIFACT
INVOIC
Invoice message
EDIFACT equivalent of X12 810, includes credit notes by type code
UN/EDIFACT
ORDERS
Purchase order message
EDIFACT equivalent of X12 850
UN/EDIFACT
ORDRSP
Purchase order response message
EDIFACT equivalent of X12 855
UN/EDIFACT
DESADV
Despatch advice message
EDIFACT equivalent of X12 856 ship notice
UN/EDIFACT
RECADV
Receiving advice message
EDIFACT equivalent of X12 861
UN/EDIFACT
REMADV
Remittance advice message
EDIFACT equivalent of X12 820 remittance detail

Code lists are maintained by UN/CEFACT, ASC X12 and trading partner agreements. Partners may restrict the subset they accept, so check the implementation guide your partner or e-invoicing network publishes.

Need invoice types routed correctly in your ERP?

Optional: an expert can map your document types to posting logic.

Optional. The tool and every export work without this. No spam.

How to use this table

Search for the code that appears in a customer or supplier file, or the document name you want to classify. Use the UNTDID 1001 rows to map your OCR classification labels to standard codes, so that scanned PDFs and e-invoices end up with the same type values in your ERP. Use the X12 and EDIFACT rows to see which message belongs to which step of the order to cash or procure to pay flow.

Why the type code matters for posting

A credit note must reverse the original posting, a prepayment invoice usually creates a down payment rather than a payable for goods, and a proforma should not be paid at all. If your classifier treats every document as a standard invoice, a credit note may be posted as a new payable. Add the type to your extraction output and route anything other than a standard invoice through its own approval path.

  • 380: normal payable posting
  • 381: reverse or offset the original invoice
  • 384: replace the earlier invoice, avoid double posting
  • 386: down payment handling
  • 325: do not post, hold for the final invoice

Mapping to the three way match

In a typical flow the purchase order (850 or ORDERS), the ship notice (856 or DESADV), the receiving advice (861 or RECADV) and the invoice (810 or INVOIC) are compared. Keeping the codes together helps when you design the document links that a matching rule needs to look up in your ERP.

Common mistakes

Do not assume a document with the word Credit anywhere on it is a credit note, since terms and conditions often contain the word. Another error is treating a corrected invoice as a new one, which causes duplicate payments. Always carry the reference to the original invoice number for types 381 and 384.

Frequently Asked Questions

What does invoice type code 380 mean?

Code 380 in UNTDID 1001 is a commercial invoice, the ordinary request for payment for goods or services. It is the default in many e-invoicing formats, including Peppol BIS Billing, where 381 is used for credit notes.

What is the difference between 381 and 383?

381 is a credit note, which reduces the amount the buyer owes. 383 is a debit note, which increases it, for example when a supplier adds charges after the original invoice was issued.

Is X12 810 the same as EDIFACT INVOIC?

They serve the same purpose, an electronic invoice, but belong to different standards with different segment structures. 810 is used mostly in North America, INVOIC in Europe and by many global trading partners.

Should proforma invoices be posted in AP?

Normally not. A proforma invoice (325) is a preliminary document, often used for customs or prepayment. Hold it for approval and post only the final tax invoice unless your prepayment process says otherwise.

If you want document classification and posting rules built around your ERP, Netray can design them to run privately on your own systems.