ERP Integration · Oman

Tally on Fawtara.

TallyPrime handles Oman VAT well and is deeply embedded across Omani business. It does not document Fawtara e-invoicing. This page is for the organisations that have to decide whether Tally carries them through the mandate — written around what Tally itself publishes about its limits, which is more than most vendors admit.

No Fawtara Tally documents no Oman e-invoicing; its MENA e-invoicing material covers UAE and KSA only
1 cert One e-invoice certificate per VAT registration — it cannot be reused across companies
No edits Vouchers with generated e-invoices cannot be deleted, modified or cancelled
No REST Integration is TDL, XML or JSON over HTTP, ODBC and DLLs — no documented REST API
The honest answer

Oman VAT, yes. Oman e-invoicing, no.

TallyPrime has a real Oman VAT capability — VAT return reporting, party VATIN handling, intra-GCC supply treatment, and bilingual Arabic and English invoice printing. What it does not have, anywhere in its published material, is Fawtara.

We checked Tally's Oman product page, its MENA hub and its Oman VAT help documentation for Fawtara, the Oman Tax Authority e-invoicing programme, PINT OM and Peppol. None appear. Oman is not mentioned at all in Tally's e-invoicing material, which covers the UAE and Saudi Arabia only. Tally does not describe Oman e-invoicing as available, in beta, or planned.

What Tally has built for Saudi Arabia shows the shape it would take, and it is a capable implementation: a KSA e-invoicing plug-in, certificate signing request onboarding against the tax portal, real-time submission for B2B against a 24-hour window for B2C, distinct clearance and reporting statuses in an overview report, and an archives report with a configurable retention path. Tally asserts ZATCA accreditation for this — that is Tally's claim rather than something we have verified against the authority's own register.

For the UAE, be careful what you read. Tally's own pages now assert Ministry of Finance listing as an Accredited Service Provider and native PINT AE generation — while simultaneously describing the solution as available "after the launch". Those pages also appear to have been updated recently from a weaker claim. If UAE matters to your group, verify against the Ministry's register rather than the vendor's page.

Where Oman actually stands
  • Phase 1 — August 2026, 100 large VAT-registered companies selected by the Tax Authority
  • Phase 2 — February 2027, all large VAT-registered companies
  • Phase 3 — August 2027, all remaining VAT taxpayers including SMEs
  • B2C is in scope from the start, on a 24-hour window
  • QR codes are required on B2C — the UAE requires none, so a UAE design will not port
  • Notice — the Tax Authority states it contacts participants at least six months ahead

Full Fawtara timeline and obligations →

What Tally publishes about its own limits

Four constraints that decide the answer at scale.

01 · Identity

One certificate, one registration

Credit where it is due — Tally states this plainly, and it is the constraint that shapes every multi-entity design. A certificate is bound to a VAT registration and to the software instance that generated it.

  • The same e-invoice certificate cannot be used for another company with a different VAT registration
  • Credentials generated in one software instance cannot be used in another — you must revoke first, both in the software and at the portal
  • After credentials are generated, VAT registration fields are locked and cannot be edited
  • Renaming a company breaks access to previously generated e-invoice archives
02 · Immutability

No edits after generation

Correct behaviour for a compliance system, and a genuine operational shock to teams used to adjusting vouchers freely. Plan your controls upstream, because downstream there is no undo.

  • Vouchers with generated e-invoices cannot be deleted, modified or cancelled — corrections go through a credit or debit note
  • A transaction cannot be deleted after saving; cancel or alter must happen before submission
  • Revoking the certificate does not unwind what was already uploaded
  • Rejections are the exception — those can be corrected and re-uploaded, but only with the Edit Log enabled
03 · Scale

The numbers Tally publishes

These are the ones to hold against your actual operation. They are not disqualifying on their own — but they decide the architecture, and they are easier to plan for than to discover.

  • Tally server supports roughly 100–150 connected users, with performance degrading as you add more
  • A maximum of 40 IPs can be configured on a single computer to access company data
  • Remote sessions are licence-bound — ten on Gold, one on Silver — and a user can be in only one remote company at a time
  • Data import is not permitted through a remote login, which constrains any multi-branch submission design
04 · Integration

No REST API

The practical constraint for connecting Tally to an access point. Integration is possible and widely done — but through Tally's own mechanisms, and with an explicit boundary on what they may do.

  • Documented methods are TDL, XML over HTTP, JSON over HTTP, ODBC and DLLs
  • No official REST API is documented
  • Tally states external integrations are limited to data exchange and cannot alter its interface or reports
  • Phase 1 and Phase 2 plug-ins cannot coexist against a single Tally serial number — relevant to any staged migration
The real decision

Running it, or outgrowing it.

For a single Omani company with modest volume, Tally plus an access point connection is a perfectly sound answer, and we would say so. The question gets harder in a specific and recognisable shape.

Multiple entities, one finance team. Because certificates bind to VAT registrations and to software instances, a group with several registered entities runs several credential sets, several company files, and — because import is not permitted through a remote login — a submission design that has to work locally to each data set. That is operable. It is also the point where the administrative overhead starts to exceed what a licence upgrade elsewhere would cost.

You are in Phase 1 or 2. Oman's early phases target large taxpayers. Organisations of that size running Tally as the system of record are usually already feeling the ceiling for other reasons, and a mandate is an expensive moment to discover it. If you have been contacted by the Tax Authority, the honest first question is whether Tally is still the right system of record — not how to bolt e-invoicing onto it.

Cross-border groups. Oman, Saudi and the UAE are three different formats with three different models. Tally supports GCC VAT across the region, but per country at company level — and it publishes nothing about running two mandate regimes concurrently. Given that Phase 1 and Phase 2 plug-ins cannot coexist on one serial number, we would treat multi-regime behaviour as an open question to test, not an assumption to build on.

Where we land, honestly: if you are staying on Tally, the work is the access point connection and the master data. If you are outgrowing it, do that migration deliberately rather than under mandate pressure — the worst version of this is discovering the ceiling six weeks before a phase date.

Questions that decide it
  • How many VAT-registered entities do you invoice from?
  • Is Tally your system of record, or a bookkeeping layer beside something else?
  • How many concurrent users, and across how many locations?
  • Do branches submit locally, or does everything route through head office?
  • Which Fawtara phase are you in — and have you been contacted?
  • Who would correct a rejected invoice, and is the Edit Log enabled?

Product statements verified against Tally's own product and help documentation on 28 July 2026. Tally's ZATCA accreditation and UAE Ministry of Finance listing are Tally's own claims; the respective authorities' registers are the authority for them. Vendor documentation changes — re-check before committing a plan.

Questions we actually get

Asked on most Tally discovery calls.

Does TallyPrime support Oman Fawtara?

Not as far as Tally documents. Oman VAT is well supported — VAT returns, party VATIN handling, bilingual invoices — but there is no reference to Fawtara, the Oman Tax Authority e-invoicing programme, PINT OM or Peppol anywhere in Tally's Oman material, and Oman is absent from its e-invoicing pages entirely. If a reseller tells you otherwise, ask which Tally documentation page says so.

We have five registered entities. Can they share one certificate?

No. Tally documents that the same e-invoice certificate cannot be used for another company with a different VAT registration, and that credentials are bound to the software instance that generated them — moving requires revoking first, in both the software and the portal. Five registrations means five credential sets to obtain, renew and revoke. That is the administrative reality people underestimate.

Someone made a mistake on a submitted invoice. Can we just fix it?

Not in place. Tally documents that vouchers with generated e-invoices cannot be deleted, modified or cancelled — the correction route is a credit or debit note. This is correct compliance behaviour and it catches teams out constantly, because it removes a habit. The exception is a rejected invoice: those can be corrected and re-uploaded, provided the Edit Log is enabled.

How do we get invoices from Tally to an access point?

Through Tally's documented mechanisms — TDL, XML or JSON over HTTP, ODBC, or a DLL. There is no official REST API, and Tally is explicit that external integrations are limited to data exchange. This is a solved problem and we build it regularly; the thing to plan for is that data import is not permitted through a remote login, which shapes how a multi-branch operation submits.

Should we migrate off Tally before the mandate?

Only if you were going to anyway. A mandate is a bad reason to change system of record and a good reason to notice that you should have. If Tally is comfortably within its documented limits for your operation, connect it and move on. If you are already straining against user counts, entity sprawl or remote-access constraints, then plan the migration on its own timeline — and bridge the phase date with the lightest compliant option rather than doing both at once.

Other ERPs

We integrate on your ERP — we don't replace it.

Each mandate lands differently on each platform. These are the ones we implement most often in the GCC.

SAP Oracle Dynamics 365 Zoho Odoo

Mandate Monitor

Deadlines move. We will tell you when.

Short, source-checked notes when a GCC mandate actually changes — a wave announced, a specification revised, a date moved. Written by the people doing the implementations. No sequence, and you can leave in one click.

We use it to send mandate updates and nothing else. See our privacy policy.

Start with thirty minutes.

Tell us how many entities you invoice from, how many users and locations you run, and which Fawtara phase you are in. We will tell you whether Tally carries you through it, what the connection would look like, and what it would cost — with a written fixed-fee quote within 24 hours.

Book a consultation → Read the Oman Fawtara briefing Free · Senior practitioner · Quote in 24 hours