Preflight validation only - not an accredited provider

E-invoicing in the UAE breaks at the file,
not at the filing.

A wrong TRN, a 0.01 rounding gap, a VAT category that does not match its rate - and your accredited provider bounces the invoice back days later. einvoicecheck.ae validates the PINT AE / UBL file before it leaves your system, in one API call.

Get an API key at launch Read the API docs

What this is not

einvoicecheck.ae is a preflight validator. It is not FTA-accredited, it does not transmit legal e-invoices, it does not replace an accredited service provider, and it does not provide statutory archival.

One POST. Every error, with the fix.

Send a canonical JSON invoice, an envelope, or raw UBL 2.1 / PINT AE XML. Get back a deterministic list of failures - each with a path, a rule id, a severity, and a suggested fix your developer can act on without reading a 200-page guideline.

curl -X POST https://api.einvoicecheck.ae/v1/validate \
  -H "x-api-key: $EINVOICECHECK_KEY" \
  -H "content-type: application/json" \
  --data-binary @invoice.json

{
  "valid": false,
  "invoiceType": "380",
  "schemaVersion": "PINT-AE-1.0",
  "errors": [
    {
      "path": "/AccountingSupplierParty/PartyTaxScheme/CompanyID",
      "rule": "AE-TRN-FORMAT",
      "severity": "error",
      "message": "Supplier TRN must be 15 digits.",
      "fix": "Remove spaces and check the TRN length: 1000xxxxxxxxxxx"
    }
  ]
}

How it works

Three steps, no onboarding project. You keep your accredited service provider; this sits in front of it.

POST the invoice

Send one document to /v1/validate with your API key - canonical JSON, an envelope, or raw UBL 2.1 / PINT AE XML straight out of your ERP export. No file upload portal, no SFTP, no mapping project.

Get normalized, field-level errors

Back comes a deterministic list: JSON path, rule id, severity, a human message, and a concrete fix. TRN format, required tax fields, VAT category vs rate, line and document total arithmetic, currency and code lists, invoice type.

Fix it before your ASP rejects it

Correct the file in your own pipeline, then hand the clean invoice to your accredited provider for transmission. The rejection never happens, so nobody has to reconcile it three days later.

Who it is for

UAE ERP integrators

You are wiring several clients' ERPs into accredited providers before the mandate date. You need to know which exports are broken now, per client, without buying a seat on every vendor's platform.

Finance & accounting software vendors

Your product has to emit PINT AE-conformant invoices for every customer. You need a validation dependency you can gate a release on - not a support ticket after a customer's invoice bounces.

In-house finance engineering teams

You own the invoice pipeline at a UAE business. You want a failing test in CI, not a rejection notice landing in the finance team's inbox with a deadline attached.

Built for the pipeline, not the procurement cycle

Deterministic, not advisory

Same invoice in, same error list out. No model calls, no "confidence" - so you can gate a CI build on it.

Self-serve, priced in public

$29 or $99 a month, on the pricing page. No discovery call, no onboarding fee, no four-month implementation.

Honest about its scope

It lints the file. Your accredited provider sends it. We say so on every page because the mistake is expensive.

How teams use it

In CI: fail the build when an ERP export produces an invoice that would be rejected downstream.
At the boundary: validate before handing the document to your accredited service provider, so rejections never reach your finance team.
During migration: run a batch of historical invoices through /v1/validate to size the mapping work before the mandate date.
In support: paste a failing invoice into the free browser validator and get the same error list without writing code.

Frequently asked questions about UAE e-invoicing

What is e-invoicing in the UAE?

UAE e-invoicing requires businesses to issue structured electronic invoices in the PINT AE format and exchange them through an accredited service provider rather than sending PDFs. The structured file has to be arithmetically and semantically correct before it is accepted.

Is einvoicecheck.ae an accredited service provider?

No. einvoicecheck.ae is a preflight validator. It is not FTA-accredited, it does not transmit legal e-invoices, it does not replace an accredited service provider, and it does not provide statutory archival. You still need an accredited provider to send the invoice.

Why do I need preflight validation if my provider already validates?

Because your provider validates at submission time, when a rejection is already an incident. Preflight validation runs in your own pipeline, before the file leaves your system, so a bad TRN or a rounding mismatch is a failing test instead of a rejected invoice.

What does the validator actually check?

TRN format, required tax fields, line-item and document total arithmetic, VAT category and rate consistency, currency and code-list membership, and invoice type detection against PINT AE / UBL 2.1.

Can I use it before the API is generally available?

Billing is not live yet. Join the waitlist and you will get an API key for the free trial as soon as keys are issued.

Join the waitlist See pricing