Innovation Analytics · Insights
Meet the date without replacing your systems
Connect your invoice data to the chosen Fawtara provider with a written mapping, exception-handling design and reconciliation plan.
Taxpayer-side implementation. Innovation Analytics is not an Oman Tax Authority accredited service provider.
General information, not legal advice.
Sources, review dates & scope
Oman Tax Authority Decision 189/2026, Article 3 — Official Gazette 1660, 9 August 2026
This is general information about published Omani law. It is not legal advice. Innovation Analytics is not a law office or legal-consultancy office registered under Royal Decree 41/2024.
Accurate as at 7 September 2026, sourced from Oman Tax Authority Decision 189/2026, Official Gazette issue 1660, 9 August 2026.
Innovation Analytics is not an Oman Tax Authority accredited service provider. We provide taxpayer-side implementation — ERP, accounting and point-of-sale integration to an accredited provider of the client's choosing. The Tax Authority publishes the list of accredited providers at fawtara.taxoman.gov.om.
Fawtara integration
A buildable plan for your invoice flow
We review the export or API available from your accounting system, map the invoice fields and specify how failures reach the right person. The fixed-price specification covers one ledger, one entity and one VATIN.
PINT-OM Mapping Specification
One ledger, one entity, one VATIN. Specification only — build, parallel running, cutover and training are quoted separately.
Inclusive of VAT. Valid to 31 March 2027.
Published prices are an invitation to treat, not an offer capable of acceptance. Work is governed by a signed engagement letter.
Innovation Analytics is not an Oman Tax Authority accredited service provider.
Build and cutover are quoted separately
The implementation quotation follows the specification and requires test access to your chosen accredited provider. You contract with the provider directly.
One worked PINT-OM field mapping
Illustrative example using synthetic data. These 12 rows show how source fields can map to PINT-OM business terms. They are a subset, not a complete invoice, a validated XML document or certification.
| Source field | Example value | PINT-OM term | Mapping decision |
|---|---|---|---|
invoice_no | DEMO-2026-0042 | IBT-001Invoice identifier | Preserve the source identifier. |
issued_on | 2026-09-07 | IBT-002Issue date | Export a calendar date in ISO format. |
document_kind | Commercial invoice → 380 | IBT-003Document type | Translate the source type using the applicable code list. |
currency | OMR | IBT-005Invoice currency | Export the currency code, not its display symbol. |
due_on | 2026-10-07 | IBT-009Due date | Carry the agreed payment date where applicable. |
customer_reference | DEMO-OPS-07 | IBT-010Buyer routing reference | Use the reference supplied by the buyer. |
purchase_order | DEMO-PO-0019 | IBT-013Purchase order | Keep the buyer's order reference separate from the invoice number. |
supplier_name | Example Supplier (synthetic) | IBT-027Seller name | Read from the supplier master record. |
supplier_city | Muscat | IBT-037Seller city | Use a structured city field. |
supplier_country | OM | IBT-040Seller country | Translate the country label to its country code. |
customer_name | Example Buyer (synthetic) | IBT-044Buyer name | Read from the customer master record. |
customer_country | OM | IBT-055Buyer country | Translate the country label to its country code. |
Production mapping also covers Oman-specific identifiers, tax data, line items, totals, addressing and business rules. Validation against the applicable schema and rules, plus testing with the chosen provider, is a separate implementation step.
Term references checked on 7 September 2026 against the OpenPeppol PINT-OM invoice semantic model.
Download mapping example · PNG, 1600 × 900
Connector or API
The answer depends on your ledger's export surface, not on our preference. A ledger with a scheduled, complete, machine-readable export is a different job from one whose only outlet is a report screen. The Determination establishes which of the two you have before anyone quotes a build.
Exceptions and retry
A rejected invoice is not a technical curiosity — it is an invoice that has not legally been issued. The specification covers the queue, the retry policy, who sees a failure, and what a rejection costs you in working days.
Reconciliation scope
Ledger to provider acknowledgements only. The Tax Authority leg is named as a provider dependency, not offered: it presupposes provider-side and Authority-side data access that only an accredited provider holds.
What accreditation covers, and what it does not
Accreditation covers the provider's platform and its transmission to the Authority. It does not cover your implementation, your field mapping, your master data or your exception handling. Those stay yours, and they are what this specification addresses.
The five-step delivery model
- 1Determination
- 2Mapping specification
- 3Build
- 4Parallel run
- 5Cutover, with two weeks of hypercare
Provider subscriptions
Your accredited provider subscription is purchased directly from that provider and is separate from our implementation scope.
The operations retainer
After cutover, an operating support scope can be agreed for your systems and provider account. Responsibilities, business hours and escalation arrangements are defined in the engagement.
Tax treatment is not our call
Whether a given transaction is standard-rated, exempt or zero-rated is a question for your tax adviser. We map what your ledger says; we do not determine it.
Start a conversation
Discuss a project
Share your billing system and chosen provider. If the date and data gaps are still unclear, the Fawtara Determination is the starting point — OMR 750.000, fixed.
- +968 7643 6295English
- +968 9964 1047العربية