Symptoms
What this usually looks like
Cash rounding enabledTotals mismatch after roundingValidator complains about payable amount or BR-CO-10
Cash rounding is breaking Peppol totals
Rounding logic that looks harmless in the ERP can still produce totals that fail e-invoice validation. This page isolates the most common pattern.
Likely cause
What is usually actually broken
A rounding or settlement line was applied after the main invoice totals were computed, so the exported amounts no longer reconcile cleanly.
Next steps
Do these before you resend
- Check the payable amount against the tax-inclusive total.
- Inspect rounding, prepayments, and manual charges in the ERP.
- Regenerate the invoice after correcting the source logic.
The fastest path from this page is a prefilled diagnosis. It opens the analyzer with this exact issue pattern already loaded and immediately prepares the EUR 9 fix-pack preview when the route looks blocked or risky.
Direct help
Buy the rescue kit for this exact issue
If this page matches the exact blocker, you can unlock the issue-specific rescue kit directly without running the analyzer first.
FAQ
What people ask right before they get blocked
No. The problem is usually how the rounding is exported into the final totals, not the business choice to round.
Start with settlement lines, prepayments, and any late adjustments that can push the payable amount above the tax-inclusive total.
Operator guides
Go one level deeper before you resend
A field-by-field guide for totals mismatches, payable amount drift, and rounding side effects in e-invoice exports.
Read the guide Related issues
Similar failure patterns worth checking
If you hit BR-CO-10, the invoice totals do not reconcile. This page translates the rule into practical bookkeeping and ERP checks.
Open issue pageThis is a precise invoice arithmetic failure, not vague validator fog. The page shows what causes it and which ERP fields to inspect first.
Open issue page