Extract the issuer, buyer, the original invoice referenced, debit reason, line items, VAT, and amount due from a debit note PDF. EN 16931 field model.
The full guide: Debit note: preceding invoice, reason, and added charges
Need to scale? Create an API key, then run this from your own code or an agent.
Create an API keyFree account required
Upload a file or pick a sample, and see the fields come back.
No signup · nothing stored
The document number and date, the invoice type code (UNTDID 1001, typically 383 for a debit note), the preceding invoice number and reference date of the original invoice, and the debit reason, such as a price correction or a quality adjustment.
Yes. The preceding invoice number and its reference date tie the debit note to the invoice it adjusts, and the purchase order reference and buyer reference support matching it in your ledger.
The line items table returns each line with its item name and description, quantity and unit code, net and gross price, line net amount, and VAT category code and rate, and the VAT breakdown table returns the taxable amount, tax amount, category code, rate, and any exemption reason.
The subtotal, total without VAT, tax amount, total amount, and amount due, plus payment terms, due date, the payment means code, the IBAN and BIC, and the remittance information for settling the debit.
The field set follows the EN 16931 semantic data model shared across the e-invoicing family. PDF only, up to 10MB and 100 pages, and the document is not retained after extraction.
The tool reads a single document. The platform reads the whole estate once and keeps it queryable — the same engine, with a memory.
See invoice data extraction if you run this for finance and AP teams, or the extraction API if you are building it in.