- The dates in law: businesses with annual revenue below AED 50 million appoint an Accredited Service Provider by 31 March 2027 and issue through the system from 1 July 2027 — that is the wave most Tally estates sit in, and it is 135 and 227 days away. Government entities appoint by the same date and go live 1 October 2027. The Phase 1 deadline — 30 October 2026, for revenue of AED 50 million or more — has already passed; that cohort goes live 1 January 2027, 46 days from today.
- Unlike the Oracle, NetSuite and Microsoft estates we have covered, a Tally shop has a vendor entity to appoint: Tally Software Solutions FZCO is on the Ministry's register, which stood at 88 accredited providers on 16 November 2026. Tally's guidance names TallyPrime 7.1 as the release that carries UAE e-invoicing onboarding — which makes the version question, not the vendor question, the first thing to check.
- The rules moved in October. Ministerial Decision No. 197 of 2026, announced 19 October and effective from 1 October, set the transmission window at 14 business days, removed the requirement to store e-invoicing data inside the UAE, repealed the two-day system-failure notification, and excluded intra-Tax-Group transactions for 24 months from 1 January 2027.
- The sequence has six stages — scope, data audit, architecture decision, ASP appointment, UAT, cutover — and on a Tally estate the critical path runs through party ledgers and company-to-TRN mapping, not through the connector. Accreditation answers the transmission question; it does not clean a decade of free-text addresses.
Every Tally UAE e-invoicing conversation we have had this autumn opens with the same sentence: "our vendor is accredited, so we are covered." Half of that sentence is true, and it is the half without a deadline attached to your name. Tally Software Solutions FZCO does sit on the Ministry of Finance's accredited register — we checked on 16 November 2026, and the register stood at 88 providers, with the page itself showing an update on 12 November. What the register entry does not do is appoint the provider for you, upgrade the estate to the release that carries the feature, map your companies to their Tax Registration Numbers, or fix the party ledgers your invoices will be validated against, field by field, from go-live. Those four jobs are the programme. The accreditation just means one procurement question has an easy answer.
What the calendar says, precisely
The facts, verified against the Ministry of Finance's publications on the day this was written. The mandate is Ministerial Decisions 243 and 244 of 2025, with Phase 1's appointment date moved to 30 October 2026 by Ministerial Resolution No. 66 of 2026. That date has passed: businesses at or above AED 50 million in revenue should already have appointed, go live on 1 January 2027, and — if the appointment slipped — are accruing exposure under Cabinet Decision No. 106 of 2025 at AED 5,000 for each month or part of a month; the recovery sequence is its own note. For everyone else, the dates ahead: appointment by 31 March 2027 and go-live on 1 July 2027 for businesses below the threshold, with government entities appointing by 31 March 2027 and going live on 1 October 2027. The scope is B2B and B2G under the five-corner Peppol-based model — invoice data leaves your system in PINT AE format through your ASP, and the FTA receives its tax data in the fifth corner. The full legal picture stays current on the UAE compliance page.
Then there is what changed four weeks ago, because several summaries in circulation now describe rules that no longer exist. Ministerial Decision No. 197 of 2026, announced by the Ministry on 19 October 2026 and effective from 1 October, amends Decision 243 in four places that matter to an implementation plan. The transmission window is 14 business days from the business transaction date — with VAT-registered issuers still bound by the VAT law's own timeline. The requirement to store e-invoicing data within the UAE is removed; records must still be retained for the Tax Procedures Law period and produced to the FTA on request. The obligation to notify the FTA of a system failure within two business days is repealed outright. And transactions between members of the same VAT Tax Group are treated as excluded transactions for 24 months from 1 January 2027 — a temporary relief for intra-group invoicing, not for sales to anyone outside the group. None of this moves the deadlines above. All of it changes the diligence questions you put to a provider, which we come to below.
Where Tally actually is
Tally's position is the one Zoho reached before it and the one SAP reached in September: the vendor's own UAE entity is on the register, so the single-vendor chain from billing screen to Peppol network is actually on offer — the chain that NetSuite and Dynamics estates spent the autumn discovering they could not buy. Tally's published guidance describes the mechanics: the appointment runs from inside the product — a sign-in from TallyPrime, a hand-off to EmaraTax, selection of Tally Software Solutions FZCO on the ASP screen against the right legal name and TRN, and a Peppol participant identifier issued on confirmation. The same guidance is specific about the prerequisite, and it is the sentence to read twice: this lives in TallyPrime 7.1. Tally describes the release as generating PINT AE documents natively and exchanging them through the five-corner model.
Read that against your estate before treating it as done. Tally installations age in place — companies running Tally ERP 9 or an earlier TallyPrime release are common, often on a machine in the accounts office that nobody has touched beyond licence renewals — and for them the mandate arrives with an upgrade project attached, including whatever customisations (TDL extensions, custom invoice formats, third-party add-ons) were built against the old release. Vendor product claims are also exactly that: Tally's statements about coverage are Tally's, they move between releases, and the release notes for your licence — not a marketing page — are where to confirm what your version transmits, for which document types. What is structural rather than documentary: the accredited entity exists, and the appointment is still an act you perform, per legal entity, through EmaraTax.
What accreditation settles — and what it does not
It settles the transmission route, and for a single-company Tally estate it removes the shortlisting exercise entirely if you want it to. It does not remove the selection questions — it changes who you address them to. The five lock-in questions still deserve written answers even when the answer-giver is your software vendor: which legal entity's invoices flow through which registration, what the exit terms return to you if you leave the product, what the connector consumes and when. One of those questions changed shape in October: before Decision 197, "where is my invoice data stored?" had a legally required answer — inside the State. That requirement is gone, which means storage location is now a commercial preference you negotiate rather than a compliance box the provider ticks. Ask it anyway, and get the answer in writing; data custody did not stop mattering because the geography clause fell away. And a group running Tally in two entities alongside SAP in a third may still rationally appoint one third-party ASP across all of them rather than one route per system — the register at 88 providers gives you that option, and the scorecard is built for exactly that comparison.
The six-stage sequence
1. Scope: which companies, which phase, which billing edges. The unit of obligation is the legal entity, tested against the AED 50 million threshold — not your Tally installation. Tally estates blur this more than most, because "company" in Tally is a data file, and a decade of year-end splits, test companies and branch books can leave a dozen of them for three legal entities. Map each real entity to its TRN, its phase and the Tally company that actually issues its invoices — then map what does not go through Tally at all: the point-of-sale tills, the rental or job-card system, the Excel-and-letterhead habit for one-off charges. Every issuing route needs a plan, because the mandate attaches to the invoice, not to the software it happens to come from.
2. Audit the data before touching the architecture. The Ministry's field list defines 51 mandatory fields on an electronic Tax Invoice, 13 of them on the invoice line, validated field by field — and the e-invoicing participant identifier is not your 15-digit TRN, a distinction that generates rework when discovered late. In Tally terms this is an audit of your party ledgers and masters: customer names that match their trade-licence registrations character for character, structured address fields where years of free-text "mailing details" have accumulated, TRNs present and valid on every B2B party, item and tax ledgers that resolve to the right VAT treatment per line. This work is measurable today, with no appointment made and no upgrade installed, and it transfers whichever route you pick. Run the 25-point checklist and the TRN validation sequence first; rejections are a master-data story far more often than a connector story.
3. Make the architecture decision deliberately. For most single-entity Tally shops the default is now obvious: upgrade to the supported release and use the vendor-native route — the mapping from Tally's own data structures to PINT AE is the vendor's problem, which is the strongest argument for the chain. The deliberate part is testing the default against your actual landscape: multi-entity groups standardising on one third-party ASP, edge billers that will never run through Tally, and any constraint that surfaces in the upgrade assessment itself. Whichever way you go, ask the sizing question in writing: what exactly does the route consume from my books — which vouchers, which masters, which trigger — and what happens to documents that fail validation? The answer tells you how much of stage two is load-bearing.
4. Appoint the ASP — formally, per entity, by 31 March. The appointment is an act, not a side effect of owning the software: the EmaraTax selection, per in-scope legal entity, against the correct legal name and TRN, with the contract and exit terms read. The in-product flow makes this mercifully short on a Tally estate — which is precisely why it should come after stages one and two, not instead of them. If your revenue is at or above AED 50 million, this stage is already overdue, and the sequencing advice changes: appoint immediately, then run the stages in parallel against the 46 days that remain to 1 January.
5. UAT with production-shaped data, including the ugly documents. Clean invoices pass first time almost everywhere. Failures concentrate in credit notes referencing their originals, foreign-currency invoices with their AED amounts, advance receipts, and the voucher types a branch still uses that head office forgot about. Test the 14-business-day transmission window — as amended by Decision 197 — against your real month-end, and if you came to the UAE from a Saudi implementation, unlearn it: UAE invoices carry no QR ceremony and there is no clearance step; the exchange model is different, as the ZATCA cohort keeps rediscovering.
6. Cut over, then run it as an operation. Go entity by entity where structure allows. Staff the run state: a named owner for rejections who fixes root causes in the masters, not in the error queue; a change-window habit for every TallyPrime release and TDL add-on update, with a regression pass over the e-invoicing flow; and a quarterly re-check of the register and the rules — this year has already shown both move without ceremony.
The register finally has a Tally entity on it. What it does not have is your party ledgers, your TRN mapping, or your upgrade — accredited is not implemented.
Where Tally projects slip
Three patterns repeat. First, reading the vendor's accreditation as the company's compliance: the obligation in Ministerial Decision 244 is an appointment plus a working system by a date, per legal entity — a register entry with the vendor's name on it satisfies neither until you act on it. Second, discovering the upgrade late: the estates that struggle are not the ones on current releases; they are the ones where the upgrade from ERP 9-era installations surfaces custom invoice formats and add-ons mid-programme, each needing rework against a release nobody budgeted for. Put the version audit in week one. Third, treating party masters as cosmetic: Tally will let a ledger invoice for years with a name in the address field and an address in the name field — the validation layer will not, and from 1 July 2027 that is not a formatting quibble, it is a rejected document with its own penalty rows under Decision 106.
How long does this take?
For the SME wave the arithmetic is kind, today: 135 days to the appointment, 227 to go-live, which is enough to run the six stages in order — the luxury Phase 1 did not get. The honest caveat is that the first two stages are the slow ones, they are entirely yours, and they get no faster for starting in February. Scoping the entities and auditing the data they would transmit are the first stages of the readiness assessment — that conversation is free, with a senior practitioner. The remediation itself is the data practice's core work; the connector, upgrade and landscape questions sit with the ERP integration practice; and the compliance framing is set out plainly on the e-invoicing practice page.
Dates, thresholds and the provider count were verified on 16 November 2026 against the Ministry of Finance's publications — Ministerial Decisions 243 and 244 of 2025, Ministerial Resolution No. 66 of 2026, Ministerial Decision No. 197 of 2026 (announced 19 October 2026, effective 1 October 2026), and Cabinet Decision No. 106 of 2025. Our summary of Decision 197 is abridged; the official text governs. The provider count comes from the Ministry's accredited-provider register, checked 16 November 2026 (88 accredited; the page showed a last update of 12 November 2026), where Tally Software Solutions FZCO appears. Statements about TallyPrime 7.1, the in-product appointment flow and PINT AE generation follow Tally Solutions' published UAE guidance as of the same date and should be read against the release documentation for your own licence. All of these are revised without ceremony — check the primary documents before relying on any date here.