Run your company on one audited operating system.

Every invoice is first normalized into a single canonical structure, then rendered as UBL 2.1 XML aligned to the PINT-AE profile — the format the UAE mandate is built around. The XML is generated deterministically and stored on the invoice record, so what you submitted is always exactly what you can re-inspect later.

• Correct UBL document types per UNCL1001: commercial invoice (380), credit note (381), debit note (383) — each with the right root element and references back to the original invoice.
• Full party detail on both sides: legal names, addresses, and 15-digit TRNs rendered into AccountingSupplierParty / AccountingCustomerParty.
• Tax totals and legal monetary totals (TaxTotal, LegalMonetaryTotal) computed from the same canonical amounts the validation engine checks — the XML can never disagree with what was validated.
• Foreign-currency invoices carry TaxCurrencyCode and TaxExchangeRate blocks with the locked AED conversion.
• Every interpolated value is XML-escaped — invoice content can never break or inject into the document structure.

Under the UAE model, invoices reach the tax authority through Accredited Service Providers. Invaq treats the ASP as a pluggable adapter behind one interface — your invoices, workflows, and audit history never depend on any single provider.

• Submissions run asynchronously through Google Cloud Tasks with automatic retries — a provider outage delays delivery, it never loses an invoice.
• Failed submissions land in the Exceptions center with the real error, where they can be retried individually or bulk-fixed.
• Provider acknowledgements and delivery-status callbacks arrive over HMAC-signed webhooks and are written back onto the invoice record.
• Every attempt, success, and failure is recorded in the audit trail with the provider message ID.
• Outbound webhooks let your own systems react the moment an invoice is submitted or delivered.

Live ASP connections switch on as the FTA finalizes the accreditation spec — the routing, retry, and audit machinery around them is already running in production.

A pure, deterministic rule engine checks every invoice against the PINT-AE draft ruleset before it can move forward — same input, same verdict, every time. Nothing reaches an ASP unvalidated.

• Identity checks: 15-digit TRN format on both parties, ISO country codes, required fields per document type.
• Line-level math: quantity × unit price reconciliation, VAT-per-line, and category rate enforcement (Standard 5%, Zero-rated, Exempt, Out of scope).
• Totals reconciliation including per-category VAT breakdown computed on the aggregated base (BR-CO-17), with rounding tolerances that match the standard.
• Duplicate invoice-number detection per legal entity, and mandatory original-invoice references on credit/debit notes.
• Your own workspace policies (PO required, value limits, custom required fields) are layered on top — they can only make validation stricter, never looser.
• Every run produces a 0–100 score and a persisted evidence record, kept separately from the invoice so re-validation never overwrites history.

UAE rules require foreign-currency invoices to state their AED equivalent at the rate published for the invoice date. Invaq resolves that rate exactly once — at finalization, when the invoice legally comes into existence — and locks it.

• Rate lookup keyed to the invoice issue date (including past dates), from a daily-published source covering AED against all major currencies.
• The locked conversion is stored on the invoice — re-opening it later can never silently change the legal AED amounts.
• Rendered into the XML as TaxCurrencyCode and TaxExchangeRate, with a second AED TaxTotal, per PINT-AE convention.
• Invoice in USD, EUR, GBP, SAR and more; receivables, aging, and executive reporting all normalize to AED using each invoice’s own locked rate.

Roles in Invaq are enforced by the API on every request — not hidden buttons in the interface. A submitter physically cannot finalize an invoice; an auditor physically cannot change one.

• Four staff roles: Admin (workspace control), Approver (finalize & submit), Submitter (create & import drafts), Auditor (read-only audit access).
• A fifth, deliberately restricted Vendor role gives external suppliers a portal scoped to exactly one supplier record — and nothing else.
• Invite teammates by email with a pre-assigned role; they land in your workspace on first sign-in.
• Role changes and removals revoke existing sessions immediately — a demoted account can’t keep acting on a stale token.
• Server-to-server API keys carry the same role scoping, and can never be created with admin rights.

Most audit logs ask you to trust that nobody edited them. Invaq’s can prove it: each event stores a SHA-256 hash of its own canonical content combined with the hash of the event before it, forming an unbroken chain from the very first record.

• Editing, deleting, or reordering any past event breaks every hash after it — tampering is mathematically evident, not just policy-forbidden.
• One-click verification re-computes the entire chain and reports exactly where (if anywhere) it breaks.
• Everything is chained: invoice lifecycle events, validation runs, payments, role changes, policy edits, document activity.
• The FTA audit pack export includes the chain-integrity report alongside the XML documents and validation evidence — a self-proving compliance bundle for any date range.