BR-CO-10 explained without validator jargon
If you hit BR-CO-10, the invoice totals do not reconcile. This page translates the rule into practical bookkeeping and ERP checks.
What is usually actually broken
One of the base amounts, tax amounts, or final totals no longer lines up after edits, discounts, or charges.
Do these before you resend
- Review tax-exclusive, tax amount, and tax-inclusive totals together.
- Recompute the invoice in the ERP rather than editing XML by hand.
- Use a fresh export for the resend.
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.
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.
What people ask right before they get blocked
It usually means the total amounts no longer reconcile after an edit, charge, discount, or tax change.
No. Recompute the invoice in the source ERP and export a clean file.
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 guideSimilar failure patterns worth checking
Rounding logic that looks harmless in the ERP can still produce totals that fail e-invoice validation. This page isolates the most common pattern.
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