UBL · Rechnungsimport · Help

UBL import: an allowance or charge is missing from totals

Reconcile line totals, document allowances, charges and the payable amount separately when import reports an arithmetic difference.

Source date: 5 November 2026Editorial team: KAN KAI WORKSEditorially updated:

Quick answer

An arithmetic warning during UBL import does not automatically prove that the source invoice is wrong. Compare XML values with the imported model first: line totals, document allowances and document charges belong at their respective levels. Discounts already included in line amounts must not be deducted again. Distinguish the net total from the payable amount, including prepayments and rounding, before changing source data or mappings.

Source basis: Q1 · Q2 · Q3

Applies to
Covers the archived Mustang UBL import case and Peppol rules for net totals and payable amounts. Assessment depends on document structure, profile and actual importer version.
How to verify the result
Control files without adjustments, with an allowance, with a charge and with both produce the expected stored totals, without double counting line and document adjustments.
Your first check

Does the import model account for the same document allowance as the XML?

Compare LineExtensionAmount, AllowanceTotalAmount, ChargeTotalAmount and TaxExclusiveAmount first. The amount due belongs to a separate later calculation.

A UBL invoice import produces Arithmetical issue, although another validator accepts the document. The target amount may differ by a discount or charge. An original Mustang report describes this situation involving document-level allowances and charges. Q1 The warning alone establishes neither an incorrect source invoice nor a particular importer defect.

Separate calculation stages

The pre-tax document total reconciles line net amounts, document allowances and document charges. Peppol rule BR-CO-13 describes that relationship. Q2 Amount due instead starts with the tax-inclusive total and accounts for paid amounts and any stated rounding. Q3 These two stages must not be mixed together.

Trace one amount from source to destination

  1. Preserve the same document version. Keep the XML, import warning and target values linked by a hash or unambiguous reference. Check whether a preview displays a different export from the bytes actually imported.
  2. Record the pre-tax stage. Read LineExtensionAmount, AllowanceTotalAmount, ChargeTotalAmount and TaxExclusiveAmount within LegalMonetaryTotal. Mark absent optional fields explicitly instead of substituting an old displayed value.
  3. Identify the allowance level. Distinguish line-level adjustments from document-level adjustments. A discount already included in a line net amount must not be deducted again as a document allowance. In a simple control example, line net 100 minus document allowance 10 plus document charge 5 gives a pre-tax total of 95.
  4. Reconcile amount due separately. Compare TaxInclusiveAmount, PrepaidAmount, PayableRoundingAmount and PayableAmount under the intended rule profile. Check currency and signs. A rounding adjustment must not conceal failure to import an entire allowance.
  5. Compare XML with the import model. If the source values reconcile, establish whether the importer actually transfers document adjustments into its objects. If they exist there but the result is wrong, inspect the target calculation. If the source XML already omits them, correct the exporter instead.

Verify with meaningful examples

Test an invoice without document adjustments, one with an allowance, one with a charge and one containing both. Do not check only whether the warning disappears: compare all imported totals with the respective source. Record both validator and importer versions so that later changes remain interpretable.

For handoff, provide sanitised total fields, the relevant allowance/charge location and the target amount. The underlying commercial agreement remains authoritative for the intended prices. This guide investigates the technical representation and does not approve tax treatment or the invoice's legal status.

Frequently asked questions

Can I ignore the warning if the XML is valid?

A valid source does not automatically prove correct transfer into the target system. Compare the values actually stored there.

Is every discount a document allowance?

No. Its level and any effect already included in other amounts must be established from the specific invoice.

Describe your case

Support with this issue

We can reconcile UBL locations, imported totals and the target system’s calculation.

Describe your case →Related service: Data & improvements

Sources