Tally to FTA: Connecting Tally ERP to UAE E-Invoicing

Why Tally Matters in the UAE

Tally is the dominant accounting system across UAE SMEs and a substantial chunk of mid-market traders, distributors, and contractors. When the FTA e-invoicing mandate hits Phase 2 on 1 July 2027, the largest single cohort of newly-compliant businesses will be Tally users. The good news: Tally is well-suited to UAE e-invoicing because it already understands UAE VAT, multi-currency, and structured invoice records. The integration is straightforward if you do it right.

What Version of Tally You Need

The minimum viable version is TallyPrime 4.0. Older Tally.ERP 9 versions can technically be bridged with middleware, but you will spend more on the workaround than on a TallyPrime upgrade. TallyPrime 5.0 and later have built-in connected services that simplify ASP integration further. If your business is on Tally.ERP 9 and still planning to be on it past mid-2026, schedule the upgrade now.

The Integration Architecture

There are three viable patterns to move invoice data from Tally to an Accredited Service Provider:

1. TDL (Tally Definition Language) Extension

The cleanest path. A TDL extension installed in your Tally company file pushes invoices to the ASP via HTTPS as soon as you save the voucher. Pros: real-time, native to Tally, no extra software. Cons: requires a Tally TDL developer for initial setup, must be updated when PINT AE specifications change.

2. Connected Services / API (TallyPrime 5.0+)

Newer TallyPrime versions expose voucher data via Tally's connected services framework. The ASP polls or subscribes to new vouchers and lifts them out. Pros: no TDL development, cloud-friendly. Cons: requires TallyPrime 5.0 or later and the connected services subscription.

3. XML Export + ASP Watcher

The fallback. Tally exports voucher data as XML (built-in feature). The ASP either watches a folder or accepts file uploads. Pros: works on any Tally version. Cons: not real-time, requires file-handling middleware, manual exception handling.

For most UAE SMEs, the TDL extension is the right starting point. It is reliable, supported by every UAE-based ASP, and does not depend on the latest TallyPrime release.

What Configuration Tally Needs

1. Statutory Configuration

Confirm UAE GCC VAT is enabled and the correct VAT rates (5 percent standard, zero-rated, exempt, out-of-scope) are mapped to the correct ledger groups and stock item tax classifications. Most UAE Tally setups have this in place but check before integration - mis-mapped tax codes will fail PINT AE validation.

2. Party Master Cleanup

Every B2B customer ledger needs:

• TRN populated in the Party Tax Details (do not store it in a description field)
• Address with emirate, area, building, P.O. Box - structured, not free-text
• Country set to United Arab Emirates for UAE customers
• Registration type - Regular, Unregistered, Composition, Consumer - set correctly

3. Stock Item Tax Classifications

Each stock item should have a clear tax classification. Free-zone goods and services need different treatments. Use Tally's GST classification framework (re-purposed for UAE GCC VAT) to set this consistently rather than overriding tax on every voucher.

4. Voucher Type Setup

Sales, sales return (credit note), debit note, advance receipt, and bill of supply are all distinct PINT AE document types. Make sure your Tally voucher types are not overloaded - one voucher type per document type, with consistent numbering.

5. Multi-Company Considerations

Many UAE SMEs run multiple Tally companies for mainland + free zone entities. Each company is a separate PINT AE issuer with its own TRN. The integration must connect each company separately, not aggregate them.

The Outbound Flow End-to-End

1. User creates a sales voucher in TallyPrime as usual.
2. TDL extension fires on save, sending voucher XML to the ASP.
3. ASP maps Tally voucher fields to PINT AE elements (Party → Supplier/Customer Party, Inventory → InvoiceLine, etc.).
4. ASP validates against PINT AE cardinality and FTA business rules.
5. ASP applies XAdES digital signature and routes through Peppol to the customer's ASP.
6. ASP reports invoice metadata to the FTA.
7. Status (FTA reference, Peppol acknowledgement, any errors) writes back to the Tally voucher as a UDF (user-defined field) so finance can see compliance status in Tally.

The Inbound Flow for Tally

Inbound is where many Tally integrations fall short. Supplier invoices arriving via Peppol need to land somewhere your AP team can process them. Two options:

• Purchase voucher auto-creation - the ASP creates a Tally purchase voucher draft via TDL or import, with supplier ledger pre-matched by TRN and line items mapped to existing stock items where possible.
• Inbox + manual posting - ASP provides a web inbox; AP team reviews each invoice and triggers Tally voucher creation. Slower but simpler.

For SMEs processing fewer than 100 supplier invoices a month, the inbox approach is usually fine. For higher volumes, auto-creation pays back quickly.

Tally-Specific Gotchas

• Voucher number conflicts. If two users in Tally enter the same voucher number (common in multi-user Tally with offline copies), PINT AE will reject the duplicate at the FTA. Switch to auto-numbering with prefix per user.
• Free-text party names. Many UAE Tally setups have customers entered with slight variations ("Acme LLC" vs "ACME LLC" vs "Acme L.L.C."). Each is a different ledger to Tally but the same TRN. Consolidate before integration.
• Stock units of measure. PINT AE expects standard unit codes. "Pcs", "Piece", "EA" must all map to a single code (typically EA for each).
• Currency handling. Foreign-currency vouchers in Tally need an AED exchange rate at the document level. PINT AE reports AED-equivalent totals to the FTA.
• Voided vouchers. Cancelling a voucher in Tally is destructive; PINT AE requires credit-note-plus-reissue. Train users to use credit notes, not voucher cancellation.

A Realistic Timeline for Tally

For a single-company TallyPrime setup, expect 4-6 weeks from kick-off to go-live:

1. Week 1 - Discovery: Tally version, party master audit, voucher types, multi-company status.
2. Week 2 - TDL installation, ASP credentials, sandbox connection.
3. Weeks 3-4 - Master data cleanup (TRNs, addresses, stock classifications).
4. Week 5 - Sandbox pilot with real vouchers, including credit notes and multi-currency.
5. Week 6 - Go live and hypercare.

Multi-company Tally setups add 1-2 weeks per additional company.

How InvoiceNet Connects to Tally

InvoiceNet ships a maintained TDL extension for TallyPrime 4.0 and 5.0, supports the connected services framework on TallyPrime 5.0+, and provides XML watchers as a fallback for legacy Tally.ERP 9 estates. Status write-back to Tally vouchers is included. Talk to us for a Tally-specific readiness assessment.