Free tier

← All guides · EN 16931 & validation

Invoice type codes 380, 381, 384 and 389: what each one means

By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026

Convert an invoice free

Put this guide into practice now: convert one invoice free — validated UBL 2.1 XML plus a Factur-X PDF, with the acceptance checker for your client’s country. See pricing for bulk conversion, country rule packs and monitored clients.

Short answer

The type code on an e-invoice (BT-3) must be one of four values in this product's validator: 380 commercial invoice, 381 credit note, 384 corrected invoice, 389 self-billed invoice — anything else fails BR-03. The code decides how the receiving system books the document, so a credit note sent as 380 is not a typo but a financial error in the client's ledger.

What is the invoice type code?

The invoice type code (BT-3) classifies the document. The validation rule implemented here, BR-03, states: 'Invoice type code must be 380/381/384/389 (BT-3).' — 380 commercial invoice, 381 credit note, 384 corrected invoice, 389 self-billed invoice. It is set in §1 of the converter form alongside the invoice number, issue date and currency.

380: the commercial invoice

380 is the default and the document this whole site is mostly about: a seller's demand for payment for goods or services supplied. It is the code your ordinary billing carries, the code the demonstration invoice uses, and the code receiving systems book as a payable. If you are issuing a normal invoice, 380 is correct and unremarkable — which is exactly why the errors happen elsewhere: templates default to 380, and every other document kind must actively escape the default.

Treat 380 as a claim with a specific shape: this document originates a debt. Everything about its validation — lines, totals, tax breakdown — exists to make that claim precise and checkable. When a document's substance is not an originating claim, another code owns it.

381: the credit note

381 reverses value: refunds, price reductions after the fact, returned goods, cancelled services. The credit note is a full document with its own number and date, positive lines and computed totals, whose type code instructs the receiving system to apply its payable amount as a credit against the seller's account. The pairing with the original invoice lives in your records and correspondence; the direction of the money lives in the code.

The failure mode to avoid is the copied template: duplicate last month's invoice, change the figures, forget the code — and your EUR 960.00 credit becomes a second EUR 960.00 charge in the client's system. Checklists beat memory here: type code is a §1 field, reviewed before submission like the invoice number itself.

384: the corrected invoice

384 replaces a document that was wrong as a document: a misspelled party, a wrong identifier, a defective data point — where the commercial deal stands but its record must be reissued correctly. The corrected invoice supersedes the original as the operative record, which is a different legal gesture from crediting: nothing is refunded; the paperwork is repaired.

Jurisdictions and accountants differ on when correction replaces versus when credit-and-reissue is required, and that choice is theirs, not the converter's. What the model guarantees is that 384 exists as a distinct signal, so the receiving system can treat the document as a replacement rather than a new debt or a credit. Sending a 'corrected' invoice coded 380 creates a duplicate debt; coded 384, it creates a repaired record.

389: the self-billed invoice

389 covers self-billing: arrangements where the buyer creates the invoice in the seller's name — common in industries with many small suppliers and one dominant buyer who measures the supply (quantities delivered, work logged) and issues the document from its own records. The document still names the seller as seller; the code discloses who actually issued it, which matters for both parties' VAT and audit positions.

Self-billing exists only by prior arrangement — a buyer cannot unilaterally start issuing your invoices. If you receive or produce 389 documents, the arrangement, the numbering series and the acceptance procedure should be written down between the parties. Within the converter, a 389 document validates like any other: the code is allowed, and the data rules are unchanged.

Choosing the code: a substance test

Ask what the document does. It originates a payment claim for a supply: 380. It gives value back against an earlier invoice: 381. It repairs an earlier document's data while the deal stands: 384. It is issued by the buyer under a self-billing arrangement: 389. If two answers feel plausible — the deal changed and the document was wrong — the sequence is usually credit the wrong document (381) and issue the right one (380), but that is an accounting judgement to confirm, not a formatting preference.

The validator's role is narrower and vital: it refuses everything outside the four codes (BR-03), so a code like 'INV' or 'CN' typed from habit fails loudly at your desk. Within the four, the choice is yours — which is why this guide exists: the machine enforces the list, you enforce the meaning.

Type code check before you convert: 5 steps

  1. Name the document's job in one sentence: claim, credit, correction or self-billed.
  2. Match it to the code: 380, 381, 384 or 389 — and set it deliberately in §1, never by template default.
  3. For 381, confirm the credit note has its own number and mirrors the original lines' VAT treatment.
  4. For 384, confirm with your accountant that correction (not credit-and-reissue) is the right instrument.
  5. For 389, confirm a written self-billing arrangement exists before the document is issued.

Worked example: the EUR 960 mistake that BR-03 cannot catch

A firm cancels a training day billed at EUR 800.00 plus 20% VAT and prepares the credit: one line, EUR 800.00, category S at 20%, computed tax EUR 160.00, payable EUR 960.00. The data is perfect — and the preparer, duplicating the original invoice in the form, leaves the type code at 380. Validation passes, because 380 is a legal code; the document is internally flawless and commercially backwards.

The client's system books a second EUR 960.00 payable. The error surfaces at payment, as a dispute, with both sides staring at a valid invoice that should have been a credit note. BR-03 guarantees the code is one of four; only the preparer's one-sentence test — 'this document gives value back' — guarantees it is the right one. Code 381, and the same flawless data nets to zero as intended.

Frequently asked questions

What type code is a normal invoice?

380 — commercial invoice. It is the converter's default and the code for an ordinary demand for payment.

Can I use a code outside 380/381/384/389?

No — BR-03 rejects any other value. Free-text codes from the PDF era ('INV', 'CN') are exactly what the rule exists to stop.

Who chooses between 381 and 384?

The substance does: value given back is a credit note (381); a defective document repaired is a correction (384). Where both seem to apply, your accountant's call governs.

Does the type code change how totals are computed?

No — totals are computed from lines identically for all four codes. The code changes how the receiving system applies the document: as a debt, a credit, a replacement or a self-billed record.

What is a self-billed invoice (389)?

An invoice the buyer issues in the seller's name under a prior self-billing arrangement — used where the buyer measures the supply. The code discloses the issuer; the data rules are unchanged.

Keep going

Run the free tool this guide is about: convert an invoice · acceptance checker · pricing · about EInvoice Translator · all guides

Related guides

← Back