Tax Star E-Invoice documentation
Tax Star files your invoices on the UAE Peppol network in the PINT-AE format the FTA requires. There are two ways onto the platform and this site documents both: connect the accounting system you already run and we read the invoices out of it, or call the OAuth API from your own software. The tax rules are identical either way — only the delivery differs.
No code
Connect your accounting system
QuickBooks, Xero, Zoho Books, Odoo, Wafeq or Naqood. You keep invoicing the way you already do; the platform reads each invoice out of your system, converts it to PINT-AE and files it. The work is data entry inside your own ERP — mostly on customer records, once each.
Start with the applicationFor developers
Build with the OAuth API
Register an application, exchange client credentials for an access token, and push invoices straight from your own software over HTTPS. REST and JSON throughout, with a Try-It console on every endpoint.
Start with the APIWhich side are you on?
Pick the row that describes you. Nothing stops you using both — a company onboarded in the application can be connected to an OAuth app and invoiced through the API.
| If this is you | Read |
|---|---|
| You already invoice from an accounting system we connect to | Application |
| You invoice from your own software, or from a product you sell | OAuth API |
| You want invoices filed without writing any code | Application |
| You need webhooks, bulk sending or programmatic validation | OAuth API |
What both routes share
The integration differs; the compliance does not.
The UAE Peppol network
However an invoice reaches us, it is dispatched through the UAE national Peppol framework to the buyer's access point. Delivery and status come back the same way on both tracks.
One set of PINT-AE rules
The same validation decides whether an invoice can be filed — a unique number, a tax category on every line, a currency, and a buyer that can be addressed. An ERP invoice and an API invoice fail for identical reasons.
One company, one TRN
The entity you onboard — its TRN, trade licence, address and emirate — is the seller on every invoice. An entity registered in the application can be connected to an OAuth app, so both tracks can run side by side.
What happens to an invoice
It arrives — read out of your accounting system, or posted to the API. It is validated against the PINT-AE rules. It is converted to the UAE XML format. It is delivered to the buyer's access point on the Peppol network, and the outcome is reported back: in the dashboard for the application, over webhooks and the invoice endpoints for the API.