E‑invoicing for the system you already run.

On Odoo, install our module. On anything else, we build, test and maintain the connection between your system and your Accredited Service Provider (ASP), or your developers connect to our API. Your team keeps invoicing where it does today. Every invoice is checked against PINT AE before it leaves and tracked until your ASP has reported it to the Federal Tax Authority (FTA).

The connection is one part of the work. See our services →

Systems we connect

The ERP, accounting, CRM, commerce, hospitality, property, legal and industry systems we connect to UAE e‑invoicing. On Odoo you install our module; for everything else we build, test and maintain the connection, mapped to your data, on its own or as part of a project. Yours isn't here? If it has an API or can export invoices, tell us and we'll scope the connection, or your developers can connect to our API directly.

ERP

Accounting

CRM and commerce

Hospitality, property, legal and industry

Customer procurement portals

When your buyers ask you to invoice through SAP Ariba or Coupa. Your ASP still carries the UAE e‑invoice.

ERP

SAP

We connect your SAP system to the ASP you appoint. Invoices and credit memos are taken once they post (in S/4HANA when the billing document is released to accounting, in Business One when the A/R invoice or credit memo is added), either directly or from SAP Document and Reporting Compliance where you run it. Each one is checked against PINT AE and sent to your ASP in the format it takes. The route is set up for your release and setup. Customers, tax codes and units are mapped once and reused for every document. Where your setup allows, the status is written back to SAP.

Talk to us about SAP
SAP
S/4HANA and Business One

The route depends on your release and setup: OData APIs, IDocs or DRC output on S/4HANA, the Service Layer on Business One

  1. 1Posted to accounting
    Billing document or A/R invoice picked up
  2. 2Mapped and checked
    Against PINT AE, before sending
  3. 3Sent to your ASP
    Tracked to the buyer and the FTA
  4. 4Status back to SAP
    Where your setup allows
Oracle
Fusion Cloud ERP, NetSuite and E‑Business Suite

The route depends on your Oracle product and version

  1. 1Completed in receivables
    In the cloud or on-premises
  2. 2Mapped and checked
    Against PINT AE, before sending
  3. 3Sent to your ASP
    Tracked to the buyer and the FTA
  4. 4Status back in Oracle
    Where your setup allows
ERP and hospitality

Oracle

We build and configure the connection to the receivables flow you already run, in Fusion Cloud ERP, NetSuite or E‑Business Suite, in the cloud or on-premises. Invoices and credit memos are checked against PINT AE before they go to your ASP, and where your setup allows, the status is written back to the transaction in Oracle. For hotels on OPERA, and for custom APEX applications, we work out the route with your team.

Talk to us about Oracle
CRM

HubSpot

When you finalise an invoice in HubSpot, we pick it up and check it before anything is sent. The customer's TRN, email and address are read from HubSpot properties. The e‑invoice status is written back to the invoice in HubSpot.

Talk to us about HubSpot
HubSpot
Your HubSpot invoices

Connects through the HubSpot API, with access you approve

  1. 1Invoice finalised
    Picked up from HubSpot invoices
  2. 2Customer TRN
    Read from HubSpot properties and checked
  3. 3Sent to your ASP
    Tracked to the buyer and the FTA
  4. 4Status on the invoice
    Written back as an invoice property
Xero
Your Xero organisation

Connects through the Xero API. You authorise access from your Xero account and can disconnect it there at any time.

  1. 1Invoice approved
    Sales invoices and credit notes
  2. 2Mapped and checked
    Contacts and tax rates, mapped once
  3. 3Sent to your ASP
    Tracked to the buyer and the FTA
  4. 4Status back in Xero
    Against the invoice
Accounting

Xero

Approved sales invoices and credit notes are picked up from your Xero organisation, checked against PINT AE and sent to your ASP in the format it takes. Contacts and tax rates are mapped once. You keep approving invoices in Xero as you do now.

Talk to us about Xero
Your own system

Direct integration (API)

For custom, legacy or in-house systems, your developers or your software vendor connect to our API. Every invoice gets the same PINT AE checks and the same tracking as any other system, and your ASP still carries it to the buyer and reports it to the FTA.

  • Send invoices as JSON in our common invoice schema, as PINT AE (UBL) XML, or as CSV with a mapping profile
  • Read each invoice's status and its full event history
  • List exceptions and resolve them
  • Receive signed (HMAC) webhooks when a status changes
  • Build against the OpenAPI specification and JSON schema, in a sandbox with a test key
  • We review your test results with you before go‑live

Rather not build it yourselves? We build, test and maintain the connection for you as an integration only.

APISandbox example
Send an invoice, follow its status

1 · Your system sends the invoice

POST /v1/documents
Authorization: Bearer your_test_key
Content-Type: application/json

{
  "source_pk": "INV-0042",
  "invoice": { … common invoice schema … }
}
202 Accepted
{ "document_id": "…", "validation": "passed" }

2 · Its event history

GET /v1/documents/{id}/events

  1. 1Checked against PINT AE
  2. 2Submitted to your ASP
  3. 3Accepted by your ASP
  4. 4Delivered to the buyer
  5. 5Reported to the FTA by your ASP
  6. ↗Webhook to your endpoint at each change
    document.status_changed, signed in the X-IB-Signature header

Illustration with example data. The full fields are in the OpenAPI specification.

The same checks and tracking, whichever system sends.

Checked against PINT AE
Missing TRNs, addresses and VAT categories caught before sending and explained in plain words: on the invoice where your system allows it, otherwise in the exception list and monthly report.

Every status, tracked
Sent to your ASP, delivered to the buyer, reported to the FTA. Written back to the invoice in your system wherever your system allows it.

One ASP per company
Each legal entity sends through the ASP it appointed, as UAE rules require.

Corrections by credit note
Never a silent edit. Every request and response is kept against the document for your auditors.

Beyond the connection

The connection is one part of the work.

Before the first live invoice, your customer data has to be clean, your VAT treatment signed off by your tax adviser, an ASP appointed and onboarded for each legal entity, and your team trained. If you already have your ASP and your plan, we can do the integration only. Or we do all of it as an implementation project, and can run it for you after go‑live as managed e‑invoicing.

Each way of working is quoted after a short scoping call.

See our services →

Readiness, ASP choice and onboarding, data clean‑upProject
Connection to your ASP, checks and testingIntegration
Receiving supplier e‑invoices through your ASPProject
Training, go‑live and early-life supportProject
Managed e‑invoicing after go‑liveOngoing

Tell us what you invoice from.

Send us your system and version, the legal entities that will send, and your ASP if you've appointed one. After a short scoping call, you receive a written readiness plan: how we'd connect it, what we need from you, a timeline and a quote. Building it yourselves? Tell us, and we'll scope direct integration (API) with you.

Request a scoping call