Symptoms

What this usually looks like

BR-CO-10 errorTotals mismatchValidation rule is too technical
Likely cause

What is usually actually broken

One of the base amounts, tax amounts, or final totals no longer lines up after edits, discounts, or charges.

Next steps

Do these before you resend

  1. Review tax-exclusive, tax amount, and tax-inclusive totals together.
  2. Recompute the invoice in the ERP rather than editing XML by hand.
  3. 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.

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

What does BR-CO-10 usually mean in practice?

It usually means the total amounts no longer reconcile after an edit, charge, discount, or tax change.

Should I patch the XML directly?

No. Recompute the invoice in the source ERP and export a clean file.

Operator guides

Go one level deeper before you resend

BR-CO-10 and cash-rounding errors without the validator fog

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

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.

Open issue page
Payable amount is higher than the tax-inclusive total

This 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