What each system is missing for PINT AE, and which part of it is the vendor's problem rather than yours.
Every one of these systems will need an accredited service provider, and none of the providers will fix your data. The difference between systems is not whether you have work to do — you do — but how much of it is configuration and how much is collecting information from other people, which is the part measured in weeks.
Zoho Books
Small and mid-size businesses · desk review of published material
Where it stands. Building PINT AE support; an accredited provider is still required
The route out. Native export plus an accredited service provider
No service accounting code field. In the UAE edition there is no field for a service accounting code at all — the SAC field exists in the India edition and does not appear here. For any item typed as a service, or as both goods and services, the value has to be carried in a custom field and mapped on the way out.
Item type is not a native concept. Nothing in the standard item record says whether a line is goods, services or both. That matters more than it looks: the classification rules fire on the item type, so a catalogue with no type populated passes validation today and fails the day the type starts being sent.
Counterparty side is strong. Tax treatment with six values, the tax number visible on the contact record, and emirate selected from a list rather than typed. Less to fix here than in most systems we looked at.
Ours to fix. Field mapping including the custom fields the format needs, item type and classification across the catalogue, transaction type flags configured from decisions you or your adviser have confirmed.
The vendor’s, not yours. The connector itself, and anything inside Zoho's own roadmap.
First Bit (1C platform)
Russian-speaking businesses and mid-market in the UAE · we have worked in it directly
Where it stands. Not in the pre-approved provider list; export exists, roadmap unpublished
The route out. Likely a vendor connector eventually; a provider portal in the meantime
Classification codes are not part of the standard item card. The catalogue carries names, units and prices. HS and service accounting codes have to be added as attributes and then mapped, which is a configuration job before it is a data job.
Counterparty tax numbers are stored inconsistently. The field exists, but in practice the number arrives with spaces, hyphens or a trailing note, and sometimes in a comment field instead. The format rejects all of those.
Export is available and workable. The system exports enough to work from, which is more than several competitors in the same segment manage. The work is in the mapping, not in getting data out.
Ours to fix. Everything upstream: catalogue attributes, counterparty records, transaction type flags, and a dry run against the published schematrons.
The vendor’s, not yours. Writing a connector to the platform, and speaking for the vendor's plans.
QuickBooks
Small businesses · desk review of published material
Where it stands. No published UAE path; mandatory fields absent from the standard setup
The route out. Middleware or a provider portal, plus an accredited provider
Mandatory UAE fields are not in the standard configuration. The invoice model was not built for this mandate, and several fields the format requires have nowhere obvious to live. Working around that is a configuration and mapping exercise rather than a setting to switch on.
No classification codes on the item record. Same problem as elsewhere, with the same consequence: today's clean test run proves nothing about the day item type starts being populated.
Ours to fix. The mapping layer and all the data work behind it.
The vendor’s, not yours. Any statement about what Intuit will release for the UAE. We have not seen one and we are not going to invent one.
Tally Prime
Small and mid-size businesses, very widely used · desk review of published material
Where it stands. Pre-approved by the Ministry of Finance, Full Member of OpenPeppol and a certified Peppol Service Provider; PINT AE conversion is announced as part of capabilities still being rolled out
The route out. The vendor's own offering once it ships, or a third-party provider today
The vendor's position moved, and the version you run may not have. Tally states it is pre-approved by the Ministry of Finance, holds Full Member status with OpenPeppol and is a certified Peppol Service Provider. Its own page describes PINT AE conversion in the future tense — “once these capabilities are rolled out” — and describes ASP accreditation as an ongoing journey. So the direction is settled and the date is not. The question for you is narrower than the vendor's roadmap: which release are you on, and does it carry the fields.
Being on the provider list is not the same as your data being ready. The vendor appearing in the pre-approved list says the transmission side is being handled. It says nothing about whether your catalogue carries classification codes or your counterparty records carry tax numbers — those are your data, and no provider fixes them.
One number on the vendor's own page does not match the tax law. That page states a five-year retention requirement. Article 56 of the Corporate Tax Law says seven years from the end of the tax period. Five is the VAT-era figure. Worth knowing before anyone configures archiving to the shorter one.
Ours to fix. The data: catalogue, counterparties, transaction types.
The vendor’s, not yours. The connector, the vendor's release schedule, and the date its ASP accreditation completes.
Excel, Word or no system at all
Micro and small businesses — a very large group in the UAE · we have worked in it directly
Where it stands. No invoicing process to connect; the process itself changes
The route out. A provider portal, plus a change in how invoices get made
There is no system to integrate, and that is the easy part. Connecting nothing to a provider portal is straightforward. What is not straightforward is that invoice numbering, approval and storage all move, and the people who currently type invoices in Word have to do something else.
The catalogue exists only in the invoices themselves. Building an item master is the first job, not a later one — there is nothing to classify until the list of things you sell exists somewhere other than in past documents.
Ours to fix. Building the catalogue from your own documents, classifying it, collecting counterparty tax numbers, and setting up a process that survives the person who currently does it going on holiday.
The vendor’s, not yours. Choosing your provider, and running your finance function.
Your system is not on the list
Then it is probably in the group where this is easiest to underestimate: in-house systems, older 1C installations, industry-specific billing. No vendor is going to build a connector for those, which means a portal or a bridge, and it means the data work happens either way. The three steps at the bottom of any page here apply unchanged.
Where this comes from
Our own review of vendor and provider material, read in 2026-07-30. Two of these systems we have worked in directly and the pages say so; for the rest this is a desk review, and those pages say that instead. It is an observation, not a regulatory fact, and vendor positions move month to month. The regulatory side — deadlines, penalties, the rules themselves — is sourced separately on the pages that state it.