To issue UAE e-invoices, your ERP or accounting system must produce structured invoice data in the PINT AE format or connect to an Accredited Service Provider that does so. It must hold correct customer and product master data, handle credit notes and special tax cases and keep an audit trail. Ask your software vendor for its e-invoicing roadmap in writing.
What the system has to do
Under the UAE model, invoices are exchanged through an Accredited Service Provider. Your system does not need to speak the network protocol itself, but it must hand the provider complete, accurate invoice data, receive status messages back and store the result. In practice, that means five capabilities: create structured data, connect to an ASP, handle each invoice scenario you use, track statuses and keep records.
Checklist by area
| Area | Check |
|---|---|
| Data | Customer legal names, tax numbers, addresses, country codes in one master record |
| Products | Description, unit of measure mapped to standard codes, tax category per item |
| Tax | Codes for standard, zero-rated, exempt, out of scope and reverse charge |
| Numbering | Unique invoice number series, no duplicates across systems or branches |
| Scenarios | Credit notes, debit notes, advance payments, discounts, multi-currency |
| Connection | API or connector to the chosen ASP, tested in a sandbox |
| Status | Sent, accepted, rejected and error statuses visible to users |
| Storage | Structured file and any PDF copy stored with the transaction |
Questions for your software vendor
- Does the product support PINT AE, directly or through a connector?
- Which Accredited Service Providers does it integrate with today?
- When will the integration be available, in which version, and at what cost?
- Who tests the integration and who fixes errors?
- How are credit notes, advance payments and reverse charge handled?
- Can the system store the acknowledgement and status for each invoice?
- What happens to invoices raised while the service is down?
Ask for written answers with dates. A vague statement that the product will be compliant is not a plan. The FTA's approved accounting software list is a separate matter; see FTA-approved accounting software.
Invoices from several systems
Many businesses issue invoices from more than one place: an ERP for large customers, a point-of-sale in shops, a billing tool for subscriptions, spreadsheets for odd cases. List every source. Each must either connect to an ASP or be replaced before your go-live date. Spreadsheets and word-processor invoices are the highest risk, because they cannot produce structured data.
Finance and IT tasks
- Finance: clean master data, define tax codes, document scenarios, train billing staff, set the status review routine.
- IT: network access, security review of the connection, user rights, test environments, backups.
- Both: sign off test results, agree the cut-over date, write the failure procedure.
Testing before go-live
Run a set of sample invoices through the test environment for each scenario. Include edge cases such as rounding, long descriptions, a customer without a tax number and a credit note to an old invoice. Record the results and the fixes. See mandatory fields and e-invoicing penalties.
Related reading
Dates are in the ASP deadline guide, and the choice of provider is in how to choose an ASP.
Integration patterns
There are usually three ways to connect an invoicing system to a provider. A direct connector is built by the software vendor or the provider and is the simplest where one exists. An API integration is built by your IT team or an integrator to send data to the provider's interface. A file-based exchange sends batches of invoice data to the provider, which is common for older systems, though it makes status tracking harder. Ask which pattern each of your systems will use and who owns it.
Data quality as a project
Treat master data clean-up as a separate work stream with an owner and a deadline. List how many customers have no tax number on file, how many products have no unit of measure and how many use a tax code that does not map to a category. These numbers give a fair measure of readiness. Many finance teams find that the oldest customer records are the weakest.
Controls after go-live
- A daily report of rejected and pending invoices.
- A weekly reconciliation of invoices issued, invoices accepted and the sales ledger.
- A monthly check that the VAT return agrees with accepted invoices.
- A log of outages and the date each was reported.
Training your team
Billing staff need to know that an invoice is not complete until it is accepted, and what to do if it is rejected. Sales staff need to know that customer details must be right before an order is invoiced. Management needs to understand the status reports. A one-hour session and a one-page guide are enough for most teams if the process is simple.
Frequently asked questions
Your system must provide complete data to an Accredited Service Provider and connect to it. The ASP is the accredited party. Ask your vendor for its roadmap.
Only if they can feed a provider with structured data. Manual word-processor or spreadsheet invoices are a high risk.
Normal sales, discounts, credit notes, advance payments, zero-rated sales, reverse charge and rejected invoice handling.
You are, with support from your vendor and ASP. Agree the process beforehand.
Check the Ministerial Decision for what must be retained. Keep structured files as well as any readable copies.
No. We help with accounting data, tax codes and process readiness, and your software vendor and ASP handle the technical build.