CII-FIX-TOTALS:CII invoice totals recalculation
Fix: Recalculate entire header monetary summation cascade.
The invoice header totals must be internally consistent: LineTotalAmount must equal the sum of line totals, TaxBasisTotalAmount must equal LineTotalAmount + charges - allowances, GrandTotalAmount must equal TaxBasisTotalAmount + TaxTotalAmount, and DuePayableAmount must equal GrandTotalAmount - prepaid amounts. This recalculates the entire cascade and requires your confirmation because it modifies financial values.
Engine Classification
Requires user confirmation before application
What is CII-FIX-TOTALS?
CII-FIX-TOTALS is a fatal validation rule defined in the cii-d16b specification. It validates the ram:SpecifiedTradeSettlementHeaderMonetarySummation element in the UBL invoice XML.
When this rule fires, the invoice is rejected by Peppol access points and never reaches the buyer.
Target path: ram:SpecifiedTradeSettlementHeaderMonetarySummation
Why This Error Matters
CII-FIX-TOTALS is a hard failure — the invoice must be corrected and re-sent before it can reach the recipient.
Inconsistent invoice totals are the most common reason for automatic rejection. Payment systems compare line totals against header totals and reject mismatches.
Validator Behavior
- ·Causes invoice rejection
- ·Fails CII schema validation
- ·Error returned: CII-FIX-TOTALS
- ·Specification: cii-d16b
How to Fix It
Identify the calculation mismatch
Check ram:SpecifiedTradeSettlementHeaderMonetarySummation at ram:SpecifiedTradeSettlementHeaderMonetarySummation. The value does not match the expected sum or formula result.
Recalculate the value
Recalculate entire header monetary summation cascade.
Re-validate your invoice
Upload the corrected invoice to confirm CII-FIX-TOTALS is resolved. Calculation errors can cascade — check related totals too.
XML Example
Generic example based on the rule's target XPath. Your actual XML structure may differ.
<!-- Triggers validation error --> <ram:SpecifiedTradeSettlementHeaderMonetarySummation></ram:SpecifiedTradeSettlementHeaderMonetarySummation>
<!-- Corrected --> <ram:SpecifiedTradeSettlementHeaderMonetarySummation>VALID_VALUE</ram:SpecifiedTradeSettlementHeaderMonetarySummation>
Technical Reference
ram:SpecifiedTradeSettlementHeaderMonetarySummationCommon Causes
- ·Line amounts changed without updating totals
- ·Allowances/charges added without recalculating
- ·Rounding drift across multiple lines
- ·Partial invoice updates
Seeing this in production? The API handles CII-FIX-TOTALS automatically. See the fix response →
Commonly Seen In
Frequently Asked Questions
The invoice header totals must be internally consistent: LineTotalAmount must equal the sum of line totals, TaxBasisTotalAmount must equal LineTotalAmount + charges - allowances, GrandTotalAmount must equal TaxBasisTotalAmount + TaxTotalAmount, and DuePayableAmount must equal GrandTotalAmount - prepaid amounts. This recalculates the entire cascade and requires your confirmation because it modifies financial values.
Recalculate entire header monetary summation cascade. You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.
Yes, CII-FIX-TOTALS is a critical error that will cause invoice rejection. It must be fixed before submission.
Many instances of CII-FIX-TOTALS can be automatically corrected using Invoice Navigator's compliance engine. The fix is applied in your pipeline with full audit evidence.
CII-FIX-TOTALS is commonly seen in exports from ZUGFeRD generators, Factur-X converters, All invoicing software. These packages sometimes generate invoices that need adjustment.
Related Content
Last updated: 14 April 2026
Validate your invoice
Drop your XML here to check for CII-FIX-TOTALS
Fix CII-FIX-TOTALS with one click
Upload your invoice and we'll suggest a fix for your review before applying it.