Integration guide
Tally Prime keeps running your books after the UAE mandate — nothing forces you off it. What changes is downstream: every invoice must become PINT-AE XML with roughly 51 mandatory fields, pass validation, and travel through an Accredited Service Provider. Invaq adds that layer: export a CSV from Tally Prime, and it maps, validates, and routes.
TallyPrime is dominant among UAE trading businesses, so the mandate lands on a very large installed base at once. The UAE model is the Peppol 5-corner / DCTCE architecture: your invoice goes from you to your Accredited Service Provider, on to your buyer’s provider and the buyer, with tax data reported to the authority in parallel. A pilot opened on 1 July 2026. Under Ministerial Decision No. 56 of 2026, businesses with revenue of AED 50 million or more must appoint an ASP by 30 October 2026 and comply from 1 January 2027; everyone else must appoint by 31 March 2027 and comply from 1 July 2027. Penalties can reach AED 5,000 per non-compliant invoice.
The invoice format is PINT AE — the UAE Peppol invoice profile, built on UBL 2.1 XML with roughly 51 mandatory fields. None of that lives inside your Tally ledgers today: the mandate is about what happens to invoice data after your books are posted. Tally publishes its own UAE e-invoicing readiness guidance (as of July 2026), and the Ministry of Finance pre-approved list stands at 42 providers as of 17 July 2026, with none fully accredited yet. The practical takeaway: keep entering vouchers in Tally Prime exactly as you do, and put a compliance layer between Tally and the ASP network before your deadline.
The zero-engineering route is CSV: export invoices from Tally Prime, import the file into Invaq, and the AI column mapper proposes how your Tally column names map to the canonical invoice fields — it works with exports from any accounting system, and you confirm the mapping before anything imports. Invaq then validates every invoice with a deterministic 0-100 score, surfaces failures as exceptions with the exact rule and field that failed, and — once fixed and finalized — generates the PINT-AE-aligned XML and submits it through your chosen Accredited Service Provider.
Two honest caveats. First, validation currently runs against a draft ruleset (uae-pint-ae-draft-1), pending the final regulator specification — the engine is versioned so your historical results remain traceable when the official spec lands. Second, Invaq is not itself an ASP: it prepares, validates, and routes invoices to ASPs through a provider-agnostic adapter, so you can pick or switch providers as accreditation finalises without redoing your integration.
When you outgrow file exports, API keys let your middleware push invoices in directly, and HMAC-signed webhooks notify your systems of validation, submission, and delivery events. Every action along the way is recorded in the Trust Ledger, a SHA-256 hash-chained audit trail, and the FTA audit pack export bundles XML, validation evidence, and the integrity report for any date range. The Growth plan is AED 369 per month; you can also sanity-check a single invoice for free with the PINT-AE validator or explore the ICV calculator.
This is a division of labour, not a criticism: Tally Prime is a ledger, and the mandate adds a transmission layer no ledger provides by itself. As of July 2026, based on Tally’s public product documentation, the standard UAE edition covers bookkeeping and VAT records but not the downstream PINT-AE pipeline:
| Requirement | Tally Prime (standard UAE edition) | Invaq layer |
|---|---|---|
| Compliant PINT AE XML | Keeps books and prints VAT invoices; does not emit PINT-AE UBL 2.1 XML | Generates PINT-AE-aligned UBL 2.1 XML per invoice |
| Validating the ~51 mandatory fields | Voucher-level checks only; no PINT-AE field validation | Deterministic 0-100 score against the PINT-AE draft ruleset |
| Routing via an Accredited Service Provider | No built-in connection to the UAE 5-corner network | Provider-agnostic ASP adapter — pick or switch providers |
| Tamper-evident audit trail | Edit logs exist, but not a cryptographic integrity chain | SHA-256 hash-chained Trust Ledger plus FTA audit pack export |
Use Tally Prime’s standard export (sales register or day book) to produce a CSV or Excel file of the invoices you want to process. No plugin, no TDL customisation, no change to how your team enters vouchers.
Drop the file into the import screen. Invaq reads the raw rows exactly as Tally exported them — you do not need to rename headers or reshape the file first.
The AI column mapper inspects your Tally column names and proposes a mapping to the canonical invoice fields — party TRN, line amounts, VAT category, currency, and the rest. You review and confirm the mapping before a single row is imported; it is saved for next time.
Each imported invoice is checked against the PINT-AE draft ruleset and given a deterministic 0-100 score with a PASS, FAIL, or WARNING result per rule — the same input always produces the same score, so results are reproducible for auditors.
Failed invoices land in an exceptions queue with the exact rule that failed and the field that caused it — typically a missing or malformed TRN, an absent VAT category, or a rounding mismatch in tax totals. Correct the data and re-validate.
Passing invoices are rendered as PINT-AE-aligned UBL XML and handed to your chosen Accredited Service Provider through Invaq’s provider-agnostic adapter. Every step is written to the SHA-256 hash-chained Trust Ledger.
No. The mandate governs how invoice data is structured, validated, and transmitted — not which ledger you keep your books in. Tally Prime remains your system of record; the PINT-AE layer, validation, and ASP routing happen downstream. Tally also publishes its own UAE e-invoicing readiness guidance (as of July 2026), so watch both your software vendor and your compliance layer.
Yes. The AI column mapper is built for arbitrary column names from any accounting system’s export, including Tally Prime’s. It proposes a mapping from your headers to the canonical invoice fields, and you confirm it before anything imports — so a mislabelled column never silently becomes wrong data.
Yes. Invaq exposes API keys for pushing invoices in directly and HMAC-signed webhooks for reacting to validation, submission, and delivery events — so an integration script or middleware can move data from Tally Prime without anyone touching a file. CSV import remains the zero-engineering path.
The sandbox opens a full Invaq workspace instantly — import a real CSV from Tally Prime, watch the AI mapper propose the columns, and see the validation scores and Trust Ledger for yourself.
Related reading: the UAE e-invoicing guide, the free PINT-AE validator, the ICV calculator, or pricing.
Last updated: 18 July 2026