On this page
What changed, in support termsQuestions users will askTriage checklist for a reported mismatchWhat to collect when escalatingKey facts to keep straightFor Support
What changed, in support terms
The amount Dentolize reports to ZATCA is now computed the same way as the invoice total shown in the app. This closes a bug where, on multi‑line invoices, the reported total could be a cent higher or lower than the invoice total (e.g. a 2999.99 invoice reported as 3000.00).
Nothing in the UI moved. There is no new setting.
Questions users will ask
"Why was my ZATCA total a cent off from my invoice?" Because the e‑invoice used to round VAT per line and then add up the rounded pieces, while the invoice rounds VAT once on the whole taxable base. On multi‑line invoices those two can differ by a cent. The fix makes the e‑invoice use the same single‑rounding method, so they match.
"Do I need to do anything?" No. It applies automatically to e‑invoices built after the update. No setting, no re‑onboarding.
"Are my old/already‑reported invoices wrong now?" The change affects how future e‑invoices are built. It does not rewrite or re‑report past submissions. If a customer has a specific historical mismatch, escalate — don't attempt a bulk re‑report.
"My invoices say 'E‑Invoice Not Reported' — is that this bug?" No. "Not Reported" means the ZATCA connection isn't set up (or the invoice hasn't been submitted yet), not a rounding problem. Check Settings → Zatca Integration — if it says "ZATCA integration not configured," onboarding (OTP + counter) is incomplete.
Triage checklist for a reported mismatch
- Confirm it's a rounding mismatch, not an onboarding/connection issue.
- Settings → Zatca Integration configured? Business Registration (CRN, VAT number, address) complete?
- Is the invoice multi‑line? Single‑line invoices were never affected by this bug.
- Compare the numbers: invoice Total (the app figure) vs the reported ZATCA amount. Note the exact values and whether the difference is exactly one cent.
- Check timing: was the e‑invoice built before the fix shipped? Pre‑fix submissions won't retro‑correct.
- If the gap is more than a cent, or isn't on a multi‑line invoice, it's likely a different issue — capture details and escalate. Candidates the team has flagged: per‑unit discount rounding on lines whose discount doesn't divide evenly by quantity (see The Cent Problem & the Fix, follow‑ups).
What to collect when escalating
- Company / branch and invoice ID (e.g.
#26). - The invoice Subtotal, Discount, Tax, Total.
- The number of line items and their prices/quantities/discounts.
- The amount ZATCA received (from the e‑invoice document), and whether the invoice was reported before or after the fix.
- Whether ZATCA integration is configured for that company.
Key facts to keep straight
- The fix touches document‑level totals only. Per‑line tax amounts on the e‑invoice are intentionally unchanged.
- It affects both simplified (patient/B2C) and standard (insurance/B2B) e‑invoices.
- It's unreleased — verify a given customer's environment actually has it before promising the behaviour.