A system that holds back every invoice Fawtara would reject. Set up before 1 April 2027.
We compare your current invoices with the Fawtara requirements, clean your buyer and product data, and connect Submit-Ready to the systems that issue your invoices. After go-live it checks every invoice before your accredited provider sends it, and tracks rejections. Your finance team approves each correction.
- Your systems
- Submit-Ready
- Your provider
- Tax Authority
Held: buyer VAT number missing
Illustrative screen, fictional data.
From 1 April 2027 (supplies above OMR 5 million) and 1 October 2027 (everyone else), every invoice goes through an accredited provider to the Tax Authority. Invoices missing required fields are rejected, and data spread across several systems is usually the slow part.
- Invoices issued from three systems and several branches.
- Customer records with no VAT number.
- A provider chosen, but nobody owning the project.
How it works, start to finish
Hover or tap a step to see an example.
- 1
Invoices from your systems
Your teamInvoices come from your billing, ERP and POS systems, often more than one.
ExampleSAP for B2B invoices · POS in six branches for B2C · an Excel sheet for credit notes - 2
Data cleaned
Submit-ReadyAt setup we clean buyer, product and tax-code data so every required field can be filled.
Example1,240 buyers checked: 214 missing a VAT number, 37 duplicates merged - 3
Checked against Fawtara
Submit-ReadyThe system checks every invoice against the Fawtara required fields and holds back what would be rejected.
ExampleINV-2026-0412 held back: buyer VAT number missing on a B2B invoice - 4
Your provider sends
OutsideYour accredited provider sends the invoices to the Tax Authority.
ExampleClean invoices go to your accredited provider in the format it expects. - 5
Accepted, or followed up
Submit-ReadyAfter go-live the system tracks rejected invoices; your finance team approves each correction.
ExampleThis week: 2 rejections, each with its reason and a fix for your finance team to approve.
What Fawtara would reject today
What the system takes off your desk
- Gap report on your real invoices
- Clean-up of buyer, product and tax-code data
- Mapping of each system and branch that issues invoices
- Testing with your accredited provider
- Follow-up on rejected invoices after go-live, approved by your finance team
What stays with you
- Your accredited provider sends the invoices
- Your finance team signs off each step
Fawtara: two mandatory dates, set by the size of the business.
Tax Authority Decision 189/2026 (Official Gazette 1660, 9 Aug 2026). The timeline for your company is fixed in writing after discovery; it depends mostly on how clean your data is and how many systems issue invoices.
163 days to 1 April 2027
How to start
Free gap note
What changes for you on your date, and what to fix first, within 2 working days. Based on your public information, plus up to 20 masked sample invoices if you choose to share them.
FreePaid discovery
We review your invoices, systems and master data. Deducted if you continue.
From OMR 750Readiness project
Data clean-up, connecting your systems, and testing with your provider.
Setup feeSystem + support
After go-live the system checks every invoice and tracks rejections; we keep it up to date. Your finance team approves each correction.
Monthly
Questions
Are you an accredited e-invoicing provider?
No. Invoices go through an accredited provider. We prepare your data and systems and follow up on rejections.
We are below OMR 5m. Is this for us?
Your date is 1 October 2027. The same free gap note works for you; ask for one.
Does it work with SAP, Oracle, Odoo or Tally?
We start from standard exports, such as SAP billing documents or POS end-of-day files. We work alongside your ERP partner and accredited provider and don't change your system configuration.
Ask for a gap note for your company.
One page: what changes on your date, and what to fix first.