Oman's e-invoicing mandate is coming. Your invoices are already compliant.
Validate, seal, report and archive Fawtara invoices without replacing your ERP.
Every invoice. Validated, reported, archived.
One live lifecycle shared by the portal, API and SDK.
If you're VAT-registered in Oman, one of these dates is yours.
One engine. Every size of business.
SMEs & growing businesses
A guided “make me compliant” workflow in the browser. Ready in days, not months.
Enterprise finance teams
ERP connectors, bulk ops, dashboards and per-invoice audit dossiers. Wave one lands here first.
Government & large groups
Isolated infrastructure and audit-first visibility, built to pass a security review.
Compliant. Secure. Fast.
Validate every invoice before it moves.
Local rule checks, versioned profiles and a per-invoice evidence dossier — defensible years later.
- RulesPINT-OM · Schematron · monetary
- FormatXML · PDF-A3
- ProfileVersioned per country
- DossierDefault on every invoice
Protect every customer's data, provably.
Tenant isolation, mTLS exchange, MFA + RBAC and encrypted archive. Architecture, not a promise.
- KeysSigning-ready · enabled if mandated
- TenancyRow-level isolation
- NetworkmTLS provider exchange
- AccessMFA + RBAC · audit log
Never block the user. The network catches up.
Validate and seal in milliseconds; report, exchange and archive run behind a queue. Scale is a queue concern, not a UX one.
- SyncValidate + seal · ~ms
- AsyncReport · exchange · archive
- RetriesIdempotent by design
- ScaleWorkers, not users, queued
Your system stays the source of truth. The engine takes it the rest of the way.
Capture
Screens, ERP, SDK or API.
Validate
Field errors before network calls.
Seal
Final XML bound to its rule version.
Report & send
OTA and buyer delivery run async.
Archive
Artifacts become one audit dossier.
Built to clear invoices at national scale.
Four interfaces, one backend contract.
Web app
Guided issuing and tracking.
Download · Archive
Enterprise portal
Bulk actions, disputes and dossiers.
Dossier · Reports
Operator console
The screen that runs the service.
Tenants · Compliance · Billing
API & webhooks
Open API, events and connectors.
Sandbox · Events
Six ways to plug Finarc into the way you already work.
Embedded SDK
Issue, receive and status inside your own portal.
REST API
Issue, validate, fetch status and pull dossiers.
Webhooks
Subscribe to invoice, OTA and exchange events.
ERP connectors
Declarative mapping packs, starting with SAP.
File batch
CSV or UBL/XML batches with per-row results.
Sandbox & CLI
Synthetic OTA plus local PINT-OM validation.
# Issue a tax invoice — synchronous validate + seal curl https://api.finarc.io/v1/invoices \ -H "Authorization: Bearer $FINARC_TOKEN" \ -H "X-Idempotency-Key: ord-7421" \ -H "Content-Type: application/json" \ -d '{ "profile": "OM-PINT-1.0", "document_type": "TaxInvoice", "seller": { "vat": "OM1100012345", "name": "Finarc Demo SAOG" }, "buyer": { "vat": "OM1100098765", "name": "Sohar Logistics" }, "lines": [{ "description": "Telematics monthly", "qty": 12, "unit_price": "45.50", "hsn": "998313", "vat_rate": 5 }] }' # → 201 · invoice sealed in 142 ms · INV-007423 · queued for OTA reporting
# Pull lifecycle status & receipts curl https://api.finarc.io/v1/invoices/INV-007423/status \ -H "Authorization: Bearer $FINARC_TOKEN" { "id": "INV-007423", "state": "reported", "profile_version": "OM-PINT-1.0", "sealed_at": "2026-05-28T11:42:18Z", "ota": { "reported_at": "2026-05-28T11:42:19Z", "receipt_id": "OTA-2026-05-9F71A", "ack": "accepted" }, "exchange": { "delivered_at": "2026-05-28T11:42:21Z", "counterparty": "OM1100098765" }, "dossier_url": "https://archive.finarc.io/d/INV-007423" }
# Inbound webhook · HMAC-SHA256 signed POST https://your-app.example/finarc/webhook X-Finarc-Signature: t=1717010522,v1=8c3a…f08e X-Finarc-Event: invoice.sealed { "event": "invoice.sealed", "id": "evt_01J9P3R2…", "created": 1717010522, "data": { "invoice_id": "INV-007423", "profile": "OM-PINT-1.0", "amount_total": "18440.00", "currency": "OMR", "buyer_vat": "OM1100098765" } } # Retries: 0s · 30s · 5m · 30m · 2h · 12h (DLQ after)
Everything your team needs to evaluate the engine.
A local-first engine — not a foreign black box with an Oman adapter.
Oman rules are first-class profile packs, not late localisation.
- Late Oman localisation
- Opaque signing and archive flows
- SME screens that expose the plumbing
- Compliance added after the fact
- PINT-OM built in from day one
- Connect your ERP, don't migrate it
- Errors in English or Arabic before send
- One ten-year dossier per invoice
Live before your wave — in three steps, not a migration.
Assess & connect
Map sources and open a sandbox tenant.
Prove it in the sandbox
Run real data against Oman's rules.
Seal, report, archive
Switch to production with alerts on.
Fawtara, in plain language.
01What is Fawtara, and who has to comply?
02When does the mandate actually start?
03Do I have to replace my ERP or accounting system?
04How does an invoice actually get cleared?
05What happens if an invoice is rejected?
06Is my data secure, and where is it stored?
07How long does it take to go live?
Book a working session with the Finarc Labs team.
Ninety minutes with finance, IT and compliance. Engine, rollout, decision package.