VDA 4938: The Self-Billing Invoice (INVOIC) Explained
With most VDA messages the supplier sends the data. VDA 4938 is the odd one out: the OEM builds the invoice and sends it to you. If you supply a German car maker and your mailbox suddenly contains INVOIC files instead of payment advice notes, this guideline is the reason.
What self-billing changes for you
VDA 4938 is the German automotive application guideline for the EDIFACT INVOIC message, and it is built for self-billing. Under a self-billing agreement, the customer calculates what it owes you from its own goods-receipt data and agreed prices, creates the invoice on its own system, and transmits it as VDA 4938. Your job shifts from issuing invoices to checking them. Fast.
The billing document is legally still your invoice, created by the buyer on your behalf. That is why the message carries both parties: NAD+BY for the buyer and NAD+SE for the seller, with the amounts agreed in your price and conditions agreement as the only source of truth both sides can reconcile against.
Historically this replaced VDA 4906, the older German invoice format. Most OEMs that self-bill finished the move years ago; if your customer is part of that world, VDA 4906 knowledge is only useful for reading legacy archives. Our history of the VDA 49xx family covers how self-billing ended up inside the same EDIFACT generation as 4984 and 4987.
How a VDA 4938 invoice is born
- You deliver goods and send the VDA 4987 DESADV as usual. Nothing changes on that side.
- The OEM's system posts the goods receipt, matches it against your despatch advice and against the open order or JIT call-off.
- At the billing run, the OEM's system prices the received quantity with your contract prices, applies tax logic, and builds one INVOIC per billing arrangement.
- The file reaches you as VDA 4938, typically over the same OFTP2 channel you use for everything else.
- You compare the invoice against your own delivery data, confirm it through the agreed process (or raise a dispute within the agreed window), and post it as a receivable. Payment follows the OEM's terms.
The whole model only works if the quantity and price data on both sides match closely. Self-billing does not remove reconciliation; it moves it in front of the invoice instead of behind it.
What is inside the message
A VDA 4938 file is an EDIFACT interchange, so it opens and closes like any other: UNB, UNH, UNT, UNZ. The interesting part is the INVOIC body. A simplified skeleton looks like this:
UNH+4938001+INVOIC:D:96A:UN'
BGM+380+493811234567'
DTM+137:20261116:102'
NAD+BY+CUSTOMERGLN::9'
NAD+SE+SUPPLIERID::9'
LIN+1++12345678:IN'
QTY+47:100:PCE'
MOA+79:1985.00'
TAX+7+VAT+++:::19+S'
MOA+125:1985.00'
MOA+124:377.15'
UNT+12+4938001'
Reading it line by line:
BGM+380: document name code 380 means commercial invoice. Credit notes in self-billing corrections typically arrive as code 381. The BGM reference is the invoice number the OEM assigned; quote it in every dispute.DTM+137: the invoice issue date, format 102 (CCYYMMDD).LINwithIN: the buyer's item number identifies your part. Check that it maps to your material master the way the OEM's guidelines say it should.MOA+79: the line item amount.MOA+125is the taxable basis andMOA+124the tax amount. The arithmetic across lines, tax and total must close: the invoice total (MOA+9) equals the sum of the lines plus tax. Our validator flags sums that do not add up, because in self-billing that almost always means a price condition was missed on one side.TAX+7+VAT: the tax line, here with a 19% rate in the duty/tax/fee rate field.
Exact segment usage is narrowed down by the VDA 4938 guideline and then again by each OEM's own implementation rules, so always work from the current guideline your customer issued.
The checks suppliers actually run
When a 4938 lands in your system, four checks catch most of the pain:
- Quantity vs. your DESADV. Pull the delivery note referenced in the invoice and compare per line. Partial deliveries and consolidated invoices are where mismatches hide.
- Price vs. your agreement. Self-billing quietly assumes both sides priced with the same conditions. A forgotten surcharge change shows up as an invoice you would never have issued yourself.
- The sum game. Line amounts, taxable basis, tax, total. If the file's own numbers do not add up, nothing downstream will save it.
- References. Order number, delivery note and invoice number should all be present and traceable. Vague references make disputes slow, and the dispute window is short.
The same envelope rules as everywhere apply: UNT segment count must match the real segment count, UNZ must match UNB's control reference. A file cut short in transfer fails here before any content check runs. See envelope errors that break the whole file if you want the full list.
Where it goes wrong in practice
Three failure patterns come up more than everything else. First, a goods receipt posted against the wrong delivery turns into an invoice for goods you shipped twice or not at all, and the fix belongs in the receipt, not the invoice. Second, price condition changes that were agreed by email and never entered into both systems produce systematic differences on a whole part family. Third, credit notes: a rejected or corrected delivery comes back as a 381 credit note, and teams that only watch for 380 invoices sit on them until month-end reconciliation explodes.
Pre-flight check
If your ERP hands you a 4938 to post, paste it into a checker before you confirm anything. The VDA 4984 validator side of this site is built for the DELFOR side of the same relationship, and the envelope logic that wraps a 4938 is identical to what the tools check on every file: segment counts, date formats, references, separator hygiene. Test files contain real part numbers and prices, so run them locally rather than uploading them anywhere.
Related reading: what the VDA 4987 DESADV contains, the VDA message family at a glance, and how VDA profiles map onto EDIFACT.