VAT across three GCC companies, with no silent filing gaps
One tax classifier replaced scattered detection logic, and every filing period is checked against the last.
The problem a client brought us
“We operate as three separate companies across three GCC jurisdictions, and our VAT filing has to reflect that correctly — with no room for a filing gap nobody notices.”
Before and after
Tax treatment inferred in several places
- Invoice totals
- Batch selection
- Report rows
One field on each tax
One VAT category
What we found and built
A VAT engine built for GCC multi-company reporting from the ground up: a single canonical tax classifier replaced scattered, ad hoc detection logic, and the system checks each new filing period against the last one — raising an explicit warning if there's an unexplained gap, rather than silently carrying forward a credit that shouldn't be there.
Result
Filing gaps get caught before they become a compliance problem, not after.
The pattern behind it
When the data is ambiguous, refuse to guess
Carry forward automatically when the facts are clean; stop and make a person decide when they aren't. An unnoticed gap silently misstates a filed return — a warning makes someone look.
How we think about problemsRecognise any of this?
Most of our work starts with a message that sounds a lot like this one did.