UAE e-invoicing readiness: check your Tally masters and invoices, with an AI agent

Short answer: To get ready for UAE e-invoicing, make the company name, TRN and address match the VAT certificate, give every UAE business customer a 15-digit TRN and an emirate, map every unit to a UN/ECE code, give every discount a reason and code exports as zero-rated. Then fix or resend anything pending. An AI agent can check the masters and invoices and list what would be rejected; your Tally partner and your ASP make the changes.

Under UAE e-invoicing, an invoice with a bad TRN or an unmapped unit is rejected before it reaches the buyer. Most of the fixes are in the masters, not the invoices.

Here is the readiness checklist from a recent TallyPrime webinar, then an agent checking a Dubai distributor's masters and October invoices, and the two follow-ups it needed.

The tutorial this is based on

How to Prepare for UAE e-Invoicing with TallyPrime? by #VIDYA TV, published 26 July 2026 (in English). A TallyPrime partner webinar: the timeline, the flow through the service providers, then Tally's exception reports. We took the readiness checklist from it and checked the dates and rules against the Ministry of Finance decisions and the PINT AE validation rules.

How do you get Tally ready for UAE e-invoicing?

  1. Confirm your phase. Revenue of AED 50m or more: appoint an accredited service provider (ASP) by 30 October 2026 and go live on 1 January 2027. Under AED 50m: ASP by 31 March 2027, live 1 July 2027. Check the Ministry of Finance for the current dates.
  2. Company master: the name, TRN and address exactly as on the VAT certificate. The seller name on every e-invoice comes from here.
  3. Customer master: every UAE business customer needs a 15-digit TRN (starting 1, ending 03), an address line, a city and an emirate. Export customers have no UAE TRN.
  4. Stock items: map every unit to a UN/ECE Rec 20 code, for example kg to KGM, litre to LTR, piece to H87 or C62. Ask your ASP which piece code it expects.
  5. Ledgers: code exports as zero-rated, with the country the goods go to.
  6. Invoices: give every discount a reason or reason code, never type over the computed VAT, and never edit an invoice after its e-invoice is generated. Issue a credit note and a new invoice instead.
  7. Run Tally's exception reports and send anything pending. Once live, invoices go to your ASP within 14 days (Ministerial Decision No. 243 of 2025; check for later changes).

Where it usually goes wrong

How an AI agent does it from Slack

We gave the agent four files for a made-up Dubai food distributor, Zafran Pearl General Trading: the company profile, customer master and stock items from Tally, and October's 72 invoices with their status in the ASP test run. Every company, name, tax number and amount in these files is made up. The agent works in Slack, where it shows up as Mnemio AI, because Accountant AI is built on Mnemio AI.

The message in SlackThese are Zafran Pearl General Trading's Tally masters and the October 2026 invoices from our ASP test run. Check them for UAE e-invoicing and tell me what would be rejected. Don't send or change anything.
Slack request to check Tally masters and October invoices for UAE e-invoicing, with four Excel files
The request with the four files: the Tally masters and October's invoices from the ASP test run.

What the agent did

  1. Checked the company master, the customer master, the stock items and all 72 October invoices, and saved its findings as a workbook.
  2. Found the company name that doesn't match the VAT certificate, two customers with 14-digit TRNs, one with no TRN, one with no emirate, and 11 stock items whose units have no code.
  3. Listed the 18 invoices that would be rejected, including VAT keyed AED 137.40 short and a 2% discount with no reason, and flagged an invoice edited after its e-invoice was generated.
  4. Got several things wrong in its first reply: its totals didn't tie to the invoice file, it suggested 15-digit TRNs it had made up, it labelled some rules with IDs from another rule set, it called the Muscat export fine, it missed a TRN that differs from the master, and it gave an invented reason for three invoices pending since 1 October.
  5. Asked five questions, it found the Muscat invoice coded standard-rated with AED 5,120 of VAT, found the swapped TRN digits on ZP-OCT26-4159, said TRNs must come from the customer's VAT certificate, put the three old invoices well past the 14-day window and placed the company in the first phase, live 1 January 2027.
  6. Asked to re-add its totals, it gave the right figures: 18 invoices, AED 1,516,036.80, and 21 pending in all.
The agent's finding that 11 stock items use the units kgs, Ltr and pcs with no code, mapped to KGM, LTR and H87, affecting 9 invoices
Units with no code: 11 items, 9 invoices. Confirm H87 or C62 with your ASP.

What it found

What the agent found, after two follow-ups
What the agent foundInvoicesWhere it's fixed
Company name differs from the VAT certificateAllCompany master
Customer TRN with 14 digits (2 customers)7Customer master
Customer with no TRN1Customer master
Customer with no emirate2Customer master
Units with no code (11 items)9Stock items
VAT keyed AED 137.40 short1Invoice
Discount with no reason1Invoice
Would be rejected (AED 1,516,036.80)18
Export to Oman coded standard-rated (VAT AED 5,120)1Accepted in the test run
TRN differs from the master1Accepted in the test run
Edited after the e-invoice was generated1Credit note and new invoice
Pending since 1-2 October3Send now
The agent's answer to a follow-up: invoice ZP-OCT26-4203 to a hotel in Muscat is coded standard-rated with AED 5,120 of VAT, unlike the export to Bahrain
Asked about the Muscat invoice, it found it coded standard-rated, unlike the Bahrain export. The export rule is Article 30 of the VAT Executive Regulation, not of the VAT Law.
The agent's finding that the TRN on invoice ZP-OCT26-4159 differs from the customer master by two swapped digits
The TRN on one invoice has two digits swapped. The test run accepted it.
The agent's corrected totals: 18 invoices that would be rejected, AED 1,516,036.80, three pending since early October, and 51 accepted in the test run
After a second follow-up, the totals tie to the invoice file. "Clean" here means not edited: two of the 50 still need a credit note.

What you still check

Questions accountants ask

When does UAE e-invoicing start?

For businesses with revenue of AED 50m or more, on 1 January 2027, with an ASP appointed by 30 October 2026. Businesses under AED 50m follow on 1 July 2027, with an ASP by 31 March 2027. Check the Ministry of Finance for the current dates.

Can I edit an e-invoice after it is issued?

No. Issue an electronic credit note and a new invoice. The agent flagged one invoice edited in Tally after its e-invoice was generated.

Does the agent send e-invoices?

No. It checks the masters and invoices and lists the fixes. Your Tally partner makes the changes and your ASP sends the invoices. It asks before it changes or sends anything.

Hand this job to an agent

Bring one of your own files to a 30-minute call and watch an agent do it.

Book a 30-min demo