UAE e-invoicing, validated before it reaches your ASP.

Kodowo sits between your ERP or accounting system and your accredited Access Service Provider: normalizing, validating, and mapping every invoice to the required PINT-AE structure before it’s ever transmitted.

Check your readiness Need hands-on implementation? →

ERP-agnostic ingestion
Works with any accredited ASP
Full audit trail

app.kodowo.com/dashboard

Kodowo dashboard overview showing invoiced-this-period, rejection rate, and penalty exposure stat cards

Works with the ERP and accounting systems you already run

The kind of businesses Kodowo is built for

Al Rashid Trading Co.Zenith Freight GroupMarina Retail HoldingsFalcon & Co. DistributionCrescent Manufacturing

What actually happens to every invoice you send.

Kodowo is not a single-ERP plugin and not an Access Service Provider. It is the layer that makes sure what reaches your ASP is already correct.

ERP-agnostic ingestion

Accepts invoice data via API, CSV, XLSX, or JSON, regardless of which ERP or accounting system it came from.

One canonical schema

Every source format normalizes into a single internal schema before validation, not a single-ERP plugin bolted onto one system.

PINT-AE validation and mapping

Invoice data is validated and mapped into the exact structure your accredited ASP requires, before it ever leaves Kodowo.

End-to-end status tracking

Every invoice moves through a real lifecycle, received through cleared, and you can see exactly where it stands at any point.

Failures you can act on

Rejected or failed submissions surface the actual reason, not a generic failure state you have to go dig for.

Full audit trail

Every status change and account action is recorded in an append-only trail, ready for internal review or an FTA audit.

Credit notes

A complete lifecycle from draft through submission and acceptance, cancellable before it goes out, alongside your invoices.

Multi-tenant isolation

Row-level tenant isolation is enforced at the database layer, so your data never mixes with another organization's.

Why a middleware layer at all?

Built for how your finance stack actually works

Most businesses run more than one system, and none of them were built for PINT-AE. Kodowo ingests from whatever you already have.

One schema, not a single-ERP plugin

The normalization layer is ERP-agnostic by design, so switching or adding a system later doesn't mean rebuilding your compliance path.

Never a black hole

Every invoice has a visible status and a full audit trail, so a failure is something you can see and fix, not something you find out about later.

The architecture, stated plainly

ERP / Accounting System

Kodowo

Accredited ASP

FTA

Kodowo does not connect directly to the FTA and is not itself an accredited ASP. It hands off validated, correctly-structured invoices to whichever accredited ASP your business already uses.

From your ERP to a cleared invoice.

Four steps, in this order, every time.

Connect

Send invoice data from your ERP or accounting system via API, or import CSV, XLSX, or JSON directly. No rebuild required.

Validate

Kodowo normalizes the payload into one canonical schema, then validates and maps it to the required PINT-AE structure.

Transmit

A passing invoice is submitted through your accredited ASP. A failing one is held with a precise, actionable reason.

Track

Follow status end to end, from received through cleared by the FTA, with a full audit trail behind every change.

The dashboard your finance team actually uses.

Every screen below is the real, shipped Kodowo dashboard, not a design mockup.

app.kodowo.com/dashboard

Kodowo dashboard status breakdown chart showing invoices across pending transmission, transmitted, cleared by FTA, rejected, failed, and needs review states

A real lifecycle, not a black box

RECEIVED, VALIDATED, PENDING TRANSMISSION, TRANSMITTED, CLEARED BY FTA, plus REJECTED, FAILED, and NEEDS REVIEW as real states you can act on.

Credit notes, live

Draft, submit, and track credit notes alongside your invoices, cancellable before submission.

Status, broken down by state

See exactly how many invoices sit in each stage of the pipeline at a glance, not buried in a spreadsheet export.

Built to be integrated, not fought.

One validate endpoint to dry-run any payload against the full PINT-AE sandbox before you commit to anything, and one submit endpoint that does the real thing. Same request shape, every time.

Dry-run validation writes nothing to your ledger.
Submission is validate, persist, and enqueue, in one call.
Every source_reference is idempotent by default.

Read the full API docs →

cURL

curl -X POST "$KODOWO_API_BASE/api/v1/compliance/validate" \
  -H "X-API-Key: $KODOWO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "source_reference": "INV-2026-0001",
    "payload": {
      "invoiceNumber": "INV-2026-0001",
      "issue_date": "2026-07-10",
      "currency": "AED",
      "seller_name": "Acme Trading LLC",
      "seller_trn": "100000000000003",
      "buyer_name": "Beta Retail FZE",
      "buyer_trn": "100000000100102"
    }
  }'

Python

import requests
response = requests.post(
    f"{KODOWO_API_BASE}/api/v1/compliance/validate",
    headers={"X-API-Key": KODOWO_API_KEY},
    json={
        "source_reference": "INV-2026-0001",
        "payload": {
            "invoiceNumber": "INV-2026-0001",
            "issue_date": "2026-07-10",
            "currency": "AED",
            "seller_name": "Acme Trading LLC",
            "seller_trn": "100000000000003",
            "buyer_name": "Beta Retail FZE",
            "buyer_trn": "100000000100102",
        },
    },
)
result = response.json()
print(result["is_valid"], result["issues"])

JavaScript

const response = await fetch(
  `${KODOWO_API_BASE}/api/v1/compliance/validate`,
  {
    method: "POST",
    headers: {
      "X-API-Key": process.env.KODOWO_API_KEY,
      "Content-Type": "application/json",
    },
    body: JSON.stringify({
      source_reference: "INV-2026-0001",
      payload: {
        invoiceNumber: "INV-2026-0001",
        issue_date: "2026-07-10",
        currency: "AED",
        seller_name: "Acme Trading LLC",
        seller_trn: "100000000000003",
        buyer_name: "Beta Retail FZE",
        buyer_trn: "100000000100102",
      },
    }),
  },
);
const result = await response.json();

Not locked to one Access Service Provider.

Kodowo is not an accredited ASP, and it is not built around a single one. It hands off validated invoices to whichever accredited ASP your business appoints, and keeps working if that choice changes.

Your ASP relationship and appointment stay entirely yours.
Kodowo never talks to the FTA directly, and never claims to.
Switching ASPs later doesn’t mean rebuilding your integration.

Your ERP or accounting system

Kodowo

Any accredited ASP

FTA

Row-level tenant isolation

Append-only audit trail

PINT-AE / UBL structured validation

Works with your accredited ASP

Idempotent submission by design

Get ahead of the Wave 1 deadline.

Due Oct 30, 2026

Check your readiness Talk to enterprise