Extract data from debit notes
When a supplier undercharges on the original invoice, the correction travels as a debit note. It is a fresh billing document that adds to what the buyer already owes: a fuel surcharge that was omitted, a unit price that was set too low, a freight cost that landed after the invoice went out. Under the UNTDID 1001 code list the document type is 383, which tells an accounts payable system to increase the payable against the referenced invoice rather than open a new order. Reconciling a debit note depends on the link back to the original. It quotes the preceding invoice number and that invoice's date, states the reason for the debit in plain text, and prices each additional charge as its own line net of VAT. The buyer's ledger has to attach the extra amount to the right invoice and the right cost centre, so the buyer reference and the purchase order reference matter as much as the money. Payment terms and a due date set when the added amount falls due. Talonic pulls the debit note into a structured record keyed to the invoice it adjusts. A note dated 2026-06-04 from Ostsee Logistik GmbH to Bavaria Kitchenware GmbH, raised against invoice INV-2026-08842 of 2026-05-20 for a fuel surcharge and a unit-price correction, returns the preceding invoice reference, two charge lines, a 19% VAT breakdown of 136.80 EUR, and an amount due of 856.80 EUR payable by 2026-07-04 that a payables clerk posts against the original booking.
What gets extracted from debit notes
How extraction works for debit notes
Debit notes are produced by billing and ERP systems and forwarded as PDFs or print-rendered exports, and the reason for the charge is often buried in free text. Talonic reads the document against the EN 16931 field model and captures the invoice type code, the preceding invoice number and its reference date, and the debit reason as discrete fields, so the note is matched to its parent invoice automatically. Each added charge is held as a line with its net amount, VAT category, and rate, and the VAT breakdown is reconciled to the stated tax amount and to the amount due. Where a note carries several corrections, every line keeps its own purchase order line reference. Field-level confidence and a pixel-region pointer conform to DIN SPEC 91491, and the canonical field bindings come from the same Field Registry that maps a standard invoice, so a reviewer verifies a surcharge against the source before it posts.
Sample extraction
A debit note correcting an earlier invoice
{
"document_number": "DN-2026-0552",
"document_date": "2026-06-04",
"invoice_type_code": "383",
"preceding_invoice_number": "INV-2026-08842",
"reference_invoice_date": "2026-05-20",
"debit_reason": "Omitted fuel surcharge and unit price correction on the original invoice",
"supplier": {
"name": "Ostsee Logistik GmbH",
"tax_id": "DE246801357",
"city": "Rostock",
"country_code": "DE"
},
"buyer": {
"name": "Bavaria Kitchenware GmbH",
"tax_id": "DE135792468",
"city": "Nuremberg",
"country_code": "DE"
},
"currency": "EUR",
"purchase_order_reference": "PO-BK-2026-1180",
"line_items": [
{
"line_id": "1",
"item_name": "Fuel surcharge, May delivery",
"quantity": 1,
"quantity_unit_code": "C62",
"line_net_amount": 420,
"item_vat_category_code": "S",
"item_vat_rate": 19
},
{
"line_id": "2",
"item_name": "Unit price correction, 200 units at 1.50",
"quantity": 200,
"quantity_unit_code": "C62",
"item_net_price": 1.5,
"line_net_amount": 300,
"item_vat_category_code": "S",
"item_vat_rate": 19
}
],
"subtotal": 720,
"total_amount_without_vat": 720,
"vat_breakdown": [
{
"vat_category_code": "S",
"vat_category_taxable_amount": 720,
"vat_category_rate": 19,
"vat_category_tax_amount": 136.8
}
],
"tax_amount": 136.8,
"total_amount": 856.8,
"amount_due": 856.8,
"due_date": "2026-07-04"
}Frequently asked
Does it link the debit note to the original invoice?
Yes. The preceding invoice number and its reference date are captured as discrete fields, so an accounts payable system attaches the added amount to the invoice it adjusts rather than treating it as a new order.
What does the document type code 383 signify?
In the UNTDID 1001 code list, 383 identifies a debit note, which raises the buyer payable. The code is read from the source so a ledger can route the document correctly rather than infer intent from the layout.
How is the added charge priced?
Each correction is held as its own line net of VAT with a category and rate, and the VAT breakdown is reconciled to the tax amount and the amount due, so a note covering both a surcharge and a price fix keeps the two lines separate.
Which references support ledger matching?
The buyer reference, the purchase order reference, and the buyer accounting reference (cost centre) are captured, so the extra amount posts to the right invoice and the right general-ledger account.
Ready to extract from your own debit notes?
Author note
Reviewed by Talonic engineering · last reviewed 2026-07-06