← All guides · EN 16931 & validation
Allowances, charges and prepaid amounts on an e-invoice, explained
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
Three adjustments shape an e-invoice's totals beyond its lines: allowances (document-level discounts) reduce the tax-exclusive amount, charges (delivery, handling) increase it, and prepaid amounts (deposits, part-payments) reduce the final payable amount after tax. Each has its own field in the converter — because a discount hidden in a typed total is the classic cause of BR-CO totals failures.
What are allowances, charges and prepaid amounts?
In the engine's compute_totals, the document allowance and charge are explicit inputs: 'allowance = q2(D(inv.allowance_total)); charge = q2(D(inv.charge_total)); tax_exclusive = line_total − allowance + charge', and the payable amount is 'tax_exclusive + tax_total − prepaid'. They are first-class fields of the invoice data — entered in the converter, carried in the UBL output, and reconciled by the BR-CO rules like every other figure.
Allowances: discounts with an address
An allowance is a reduction of the amount otherwise payable — a volume discount, a prompt-payment concession agreed upfront, a goodwill reduction. Its defining virtue in the structured model is visibility: the allowance sits in its own field, the client sees the full price and the reduction as separate facts, and the totals arithmetic subtracts it in the open. Compare the PDF-era alternatives — a quietly lowered unit price, a footnote, a total that simply differs from the lines — each of which destroys information the client's booking and your audit both need.
Choose the right level. A discount on one item belongs with that line's pricing story; a discount on the whole engagement belongs in the document allowance. Either way it is a field, not a fudge: if a figure in the invoice cannot be traced to lines, allowances, charges, tax or prepaid, it does not belong in the invoice — that traceability is the entire BR-CO philosophy in one sentence.
Charges: surcharges in the open
Charges are the mirror: amounts added beyond the lines — delivery, travel, materials handling, a rush fee. In their own field, they raise the tax-exclusive amount transparently: the client sees what the work cost and what its logistics cost, itemised by the structure itself. Buried inside unit prices, the same amounts distort the price record of the work itself and confuse every future comparison ('why did the day rate change?' — it didn't; travel moved inside it).
Tax treatment of charges follows the invoice's logic — they enter the tax-exclusive base before tax is settled — which is another reason to keep them distinct: a charge's VAT story must be computable, and it can only be computed if the charge exists as a figure in the model rather than as an unexplained swelling of a total. When in doubt about a charge's treatment, the question is for your accountant; the field for its amount is already waiting.
Prepaid: the deposit becomes data
Prepaid is the amount already paid against this invoice — a deposit, a milestone payment, a retainer drawn down. The computation subtracts it last: payable equals tax-exclusive plus tax minus prepaid. The client is asked only for the residue, and the residue is provable: anyone can recompute it from the document's own fields, without hunting the covering email that mentioned the deposit three months ago.
This field retires one of the oldest invoicing disputes — 'we already paid part of this' — by moving the fact into the invoice itself. The client's payables system books the payable amount as the amount due; if the deposit lived only in your correspondence, their system would demand the full figure and the argument would start. State the prepaid amount, and the invoice agrees with both parties' memories because it contains them.
How the three interact in the computation
Order matters, and the engine's order is: lines sum to the line total; allowances subtract and charges add to form the tax-exclusive amount; the tax breakdown computes tax per category and rate; the tax total joins the tax-exclusive amount; prepaid subtracts to give the payable amount. Each adjustment applies at its own stage, on the record, and the BR-CO rules compare the outcome against any supplied totals — so an adjustment entered at the wrong stage (a discount netted against the payable, bypassing the tax-exclusive stage) announces itself as a totals mismatch.
That staging is also why partial payments and discounts must never be merged into one fiddled figure. A EUR 200 discount and a EUR 200 deposit are different facts with different tax consequences and different audit meanings, even when their net effect on the payable amount coincides. The model gives each its own field precisely so coincidence cannot erase the distinction.
Habits that keep adjustments clean
Name the reason in your own records for every allowance: future you, reading a discounted invoice in two years, should not have to reconstruct the negotiation. Agree charges before they appear — a surcharge first met on the invoice is a dispute with a head start. Record prepaid amounts against the specific invoice they reduce at the moment the payment lands, not at billing time from memory.
And validate: a conversion run recomputes the whole chain and stamps the result. If a client's system queries an adjusted invoice, your answer is the document itself — lines, allowance, charge, tax, prepaid, payable, each traceable. Adjustments handled this way stop being the soft underbelly of your billing and become what they should be: ordinary, provable arithmetic.
Handling adjustments in 5 steps
- Put every discount in an allowance field — document-level for whole-invoice reductions, priced visibly for single items.
- Put delivery, travel and fees in the charge field; never swell unit prices to hide them.
- Record deposits and part-payments in the prepaid field at the moment they land, against the specific invoice.
- Check the staged computation after conversion: line total → tax-exclusive → plus tax → minus prepaid → payable.
- If BR-CO fires on an adjusted invoice, look for an adjustment applied at the wrong stage before questioning the arithmetic.
Worked example: discount, delivery and a deposit on one invoice
A supplier invoices EUR 5,000.00 of equipment configuration — lines at category S, 20%. A EUR 250.00 loyalty allowance applies to the whole job; delivery adds a EUR 60.00 charge; the client prepaid a EUR 1,000.00 deposit. The computation: line total EUR 5,000.00; tax-exclusive EUR 5,000.00 − 250.00 + 60.00 = EUR 4,810.00; tax at 20% computed by the engine on the breakdown; payable = tax-exclusive + tax − EUR 1,000.00.
Every party can re-derive the payable from the document: the client sees the discount they negotiated, the delivery they agreed, and the deposit they paid, each in its field. Remove any one fact to a side channel — the discount into a phone call, the deposit into an email — and the same invoice becomes an argument. The fields exist so the argument never starts.
Frequently asked questions
Where does a discount go on an e-invoice?
In the allowance fields — document allowance for a whole-invoice reduction. Not netted silently into the payable total, where the BR-CO comparison will flag the mismatch.
Are charges taxed?
Charges enter the tax-exclusive amount before the tax computation in the engine's model. Their precise treatment for your supply is your accountant's call; the structural point is that they are a visible field, not hidden in prices.
How do deposits appear?
In the prepaid field, subtracted after tax: payable = tax-exclusive + tax total − prepaid. The client is billed only the residue, provably.
Can an allowance exceed the line total?
The arithmetic would drive the tax-exclusive amount negative — a sign the 'discount' is really a credit note situation. Credits belong in a type-381 document, not in an allowance swallowing an invoice.
Why not just lower the unit price instead of an allowance?
Sometimes that is right — for an item-specific price agreement. But a whole-engagement discount recorded as lowered prices falsifies the price record of the work. The allowance keeps both truths: the price, and the reduction.
Keep going
Run the free tool this guide is about: convert an invoice · acceptance checker · pricing · about EInvoice Translator · all guides
Related guides
- Invoice totals and the BR-CO rules: how e-invoice arithmetic must reconcile
- How to issue a credit note as an e-invoice (type code 381)
- How to validate an e-invoice before you send it (and read the errors)
- Convert your first invoice free: a walkthrough of the one-invoice job
- EN 16931 business rules explained: what BR codes mean when validation fails