Compliance isn’t a feature. It’s the default.
Every document is tested against the tax rules before a dirham moves. Every journal carries its evidence. Every period lock is final. This page is the plain-language map of how Orbit keeps your books defensible — in the UAE and in Saudi Arabia.
Before input VAT is claimed, each invoice is tested against the FTA's tax-invoice criteria — TRN present, rates, arithmetic, rounding. An invoice that fails is held with the reason stated, not silently claimed.
UAE Corporate Tax (9%) accrues monthly instead of surfacing as a year-end surprise — and VAT and CT are reconciled against each other, so the two returns never tell different stories.
For Saudi entities, the 15% VAT rules apply and ZATCA e-invoice clearance status is tracked invoice by invoice — the claim is only as good as the cleared document behind it.
Orbit reads and validates structured invoices today, ahead of the UAE e-invoicing mandate — the switch is a date on a calendar, not a migration.
When you close a period it locks, and agents cannot cross the lock. Nothing is ever deleted — voids are mirrored reversals, so the trail stays whole.
Every action, human or agent, is logged with its source evidence and the agent's commentary. When the auditor or the FTA asks, you hand over the packaged trail — not a shoebox.
Agents propose, deterministic engines post, humans approve. Anything above your journal-value threshold, any low-confidence coding, any duplicate suspicion — waits in the decision queue for a person.
Your books live in an isolated tenant with row-level security. Ledger credentials are stored server-side, encrypted, and never reach a browser. Sign-in supports mandatory two-factor authentication, and your ledger connection can be revoked at any time — from Orbit or from the ledger's side.