How do I fix CII-FIX-TOTALS?

Recalculate entire header monetary summation cascade. You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.

Is CII-FIX-TOTALS a critical error?

Yes, CII-FIX-TOTALS is a critical error that will cause invoice rejection. It must be fixed before submission.

Can CII-FIX-TOTALS be automatically fixed?

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.

Which accounting software causes CII-FIX-TOTALS?

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.

errorcii-d16b

`CII-FIX-TOTALS`:CII invoice totals recalculation

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.

Severity

Fatal

Rule set

cii-d16b

Country

All EU

Fix type

CONFIRM

Confidence

80%

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 non-compliant and will be rejected by Peppol access points and national validation services. The sending system receives a rejection response and the invoice does not reach the buyer.

Target path: ram:SpecifiedTradeSettlementHeaderMonetarySummation

Get API Access

Why This Error Matters

CII-FIX-TOTALS is a hard failure. Invoices that trigger this rule are rejected at the access point and never reach the recipient. In Peppol networks, this means your sending system receives an MLR (Message Level Response) with a rejection status. The invoice must be corrected and re-sent, adding delay to your payment cycle.

Validator Behavior

·Causes invoice rejection
·Fails CII schema validation
·Error returned: CII-FIX-TOTALS
·Specification: cii-d16b

XML Example

Generic example based on the rule's target XPath. Your actual XML structure may differ.

Before

<!-- Triggers validation error -->
<ram:SpecifiedTradeSettlementHeaderMonetarySummation></ram:SpecifiedTradeSettlementHeaderMonetarySummation>

After

<!-- Corrected -->
<ram:SpecifiedTradeSettlementHeaderMonetarySummation>VALID_VALUE</ram:SpecifiedTradeSettlementHeaderMonetarySummation>

Technical Reference

XPathram:SpecifiedTradeSettlementHeaderMonetarySummation

Speccii-d16b

Operationrecalculate

StrategyCascading recalculation: LineTotalAmount → TaxBasisTotalAmount → BasisAmount sync → TaxTotalAmount → GrandTotalAmount → DuePayableAmount

Common 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

ZUGFeRD generatorsFactur-X convertersAll invoicing software

Last updated: 18 February 2026

Share this guide:

Handle CII-FIX-TOTALS Automatically in Your Pipeline

The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.

Get API Access View API Documentation

CII-FIX-TOTALS:CII invoice totals recalculation