CargoWise · UAE e-invoicing

CargoWise invoices, compliant with UAE e-invoicing.

CargoWise raises the invoice. Alya Books maps it to PINT AE, checks every rule, submits it through Taxilla and writes the FTA acknowledgement back to the job. Pick a connection below and watch an invoice travel.

Play the simulation Request a demo

Push, API, file or inbound
Every PINT AE rule checked
Taxilla, accredited ASP
Audit-firm mapping sign-off

Tax invoice · 380

INV-2027-00012

Reported to FTA

Buyer

Al Noor Trading LLC

TRN 100 2345 6789 0003

Issue date

12 Jan 2027

Emirate of supply: Dubai

Item	Qty	VAT	Net
Consulting, January	10 h	5 %	5,000.00
Export of goods	1	0 % Z	2,400.00

Subtotal7,400.00

VAT250.00

Total AED7,650.00

PINT AE validPeppol deliveredPay link sent

Stage 0

Nothing is connected until the readiness assessment is signed.

A freight forwarding and logistics business issues more invoice variants than it lists at kick-off. Before the integration, the audit firm classifies what you really issue, maps every combination to the UAE transaction types and signs the VAT position. The simulation below shows what happens after that gate.

0.1
Invoice population analysis
A sample of posted AR and AP invoices classified by document type, customer type, currency, charge code and VAT treatment: what you really issue.
0.2
Transaction type matrix
Every combination mapped to the UAE transaction types and VAT categories, with the rule that decides each. This matrix drives the integration mapping.
0.3
Master data risk review
Customer TRNs validated, Peppol IDs looked up, foreign buyers flagged, tax group members identified, missing fields listed with owners.
0.4
VAT position review
Place of supply for transport, disbursements versus reimbursements, agent versus principal billing, free zone treatment, historical exposure. A signed position paper.
0.5
Readiness report
Gaps, risks, remediation, the connection route we recommend and the go-live date you can meet.

Gate: a signed readiness report with the transaction type matrix. The integration mapping is built from it and reviewed by the same advisers.

Simulation

Four ways to connect CargoWise. Watch one invoice travel.

Pick a route, press play, and follow the invoice from posting to the FTA acknowledgement. Then break the invoice and see the rejection finance would get, from the same validator that runs in Alya Books.

Automatic push

For forwarders who post hundreds of invoices a day and want nothing re-keyed. CargoWise's integration layer (eAdaptor) delivers the posted AR invoice as XML to a Alya Books endpoint; the result is written back to the job.

CargoWise
Alya Books
Taxilla (ASP)
Buyer's ASP
FTA

Draft
Validated
Submitted
Delivered
Reported
Accepted

8 steps

1
AR invoice posted in CargoWiseDraft
2
Received by Alya BooksDraft
3
Mapped to PINT AEDraft
4
Validated against every UAE ruleValidated
5
Submitted to Taxilla (corner 2)Submitted
6
Delivered to the buyer's ASP (corner 3)Delivered
7
Tax data reported to the FTA (corner 5)Reported
8
Status and documents written backAccepted

Break the invoice

Mistakes an ERP mapping really makes. The check runs in your browser with the validator Alya Books uses.

Valid as posted

Every PINT AE rule passed, so the invoice goes to Taxilla. Pick a break above to see a rejection.

Outbound message from CargoWise (UniversalTransaction, abridged)

<UniversalTransaction>
    <TransactionInfo>
      <TransactionType>INV</TransactionType>
      <Number>INV-2027-00412</Number>
      <TransactionDate>2027-01-12</TransactionDate>
      <Branch><Code>DXB</Code></Branch>
      <JobNumber>S00123456</JobNumber>
      <HouseBill>DXBSHA2701234</HouseBill>
      <Currency><Code>AED</Code></Currency>
    </TransactionInfo>
    <Organization>
      <Code>DESROSE</Code>
      <FullName>Desert Rose Trading LLC</FullName>
      <RegistrationNumber Type="TRN">100765432100003</RegistrationNumber>
    </Organization>
    <PostingJournalCollection>
      <PostingJournal><ChargeCode>FRT</ChargeCode><Description>Ocean freight DXB to SHA</Description><Amount>12000.00</Amount><VATCode>Z</VATCode></PostingJournal>
      <PostingJournal><ChargeCode>THC</ChargeCode><Description>Terminal handling, Jebel Ali</Description><Amount>1800.00</Amount><VATCode>S</VATCode></PostingJournal>
      <PostingJournal><ChargeCode>DUTY</ChargeCode><Description>Customs duty paid on your behalf</Description><Amount>3250.00</Amount><VATCode>O</VATCode></PostingJournal>
    </PostingJournalCollection>
  </UniversalTransaction>

On the CargoWise side

An outbound message trigger on AR invoice posting
A Alya Books endpoint URL and API key in the message configuration
Nothing else: mapping lives in Alya Books, signed by the audit firm

In Alya Books

CargoWise stays the system of record. Alya Books keeps the evidence.

Status and documents are written back to the job. The invoice itself, its timeline, the acknowledgements, the reports and the VAT return figures live in Alya Books, with roles for finance, approvers and the audit firm.

The invoice, with its timeline

Every CargoWise invoice opens in Alya Books with the PINT AE view, the PDF, the XML, and a timeline of Submitted, Delivered and Reported with each acknowledgement file.

Rejections, explained

A rejected invoice names the rule, the field and the fix in English and Arabic. Finance corrects it in the editor or in CargoWise and resubmits; the number is never consumed twice.

Reports and the VAT return

Sales by VAT category, by emirate and by customer; the VAT 201 figures; a reconciliation of what the FTA has acknowledged against what CargoWise posted.

Audit trail for the firm

Every change, approval and submission is logged with the user and the time. The audit firm's monthly reconciliation reads from here.

INV-2027-00412 · timeline

Accepted

12 Jan 09:14Received from CargoWise · job S00123456
12 Jan 09:14Validated · 302 rules, 0 errors
12 Jan 09:15Submitted to TaxillaINV-2027-00412.xml
12 Jan 09:15Delivered · buyer's ASP acknowledgedMLS
12 Jan 09:16Reported · FTA acknowledged the tax dataTDD-MLS
12 Jan 09:16Written back to CargoWise · Accepted

Sales by VAT category · January 2027

VAT 201 box 1 to 3

Category	Net AED	VAT AED
Standard rated (5%)	412,900.00	20,645.00
Zero rated · international transport	1,284,300.00	0.00
Out of scope · disbursements	386,120.00	–
Exports of services	96,400.00	0.00

Reconciled: 1,318 invoices acknowledged by the FTA, 1,318 posted in CargoWise, 0 exceptions.

Why the assessment

Freight forwarding and logistics invoicing is the most varied invoicing the mandate covers.

Documents you issue

Commercial invoice (380) per shipment, per job or as a monthly summary
Credit note (381), often against several invoices
Self-billed invoice and credit note (389, 261) with overseas agents
Debit notes for charges added after delivery
Intercompany recharges between branches and group entities

Transaction types on those documents

Standard rated: local handling, storage, documentation
Zero rated: international transport and related services
Out of scope: customs duty and other disbursements paid as agent
Exports of services to foreign customers without a TRN
Reverse charge on services bought from abroad
Free zone and designated zone supplies
Disclosed agent billing on behalf of a principal
Continuous supply and summary invoicing for account customers

One CargoWise invoice can carry four of these at once. The mapping is a tax decision first and a technical task second, which is why the audit firm owns it.

The framework

Where each party sits in the UAE five-corner model.

Your ERP and Alya Books are corner 1. Taxilla is corner 2 and, for invoices you receive, corner 3. The Federal Tax Authority receives the tax data from both sides.

CORNER 1

You, the seller

Create the invoice in Alya Books

CORNER 2

Your ASP

Taxilla, connected by Alya Books

CORNER 4

Buyer's ASP

Any accredited provider

CORNER 5

Your buyer

Receives the e-invoice

Tax data reported by corner 2

Tax data reported by corner 4

CORNER 3

Federal Tax Authority

Central data platform receives both reports

Questions

What clients ask first.

Bring your CargoWise invoices to the FTA with an audit firm behind the mapping.

Start with the readiness assessment. The integration follows the signed matrix.

Request a demo See the API

A demo organisation seeded with your invoice types is part of the first call.

CargoWise invoices, compliant with UAE e-invoicing.

Nothing is connected until the readiness assessment is signed.

Invoice population analysis

Transaction type matrix

Master data risk review

VAT position review

Readiness report

Four ways to connect CargoWise. Watch one invoice travel.

Automatic push

Break the invoice

On the CargoWise side

CargoWise stays the system of record. Alya Books keeps the evidence.

The invoice, with its timeline

Rejections, explained

Reports and the VAT return

Audit trail for the firm

Freight forwarding and logistics invoicing is the most varied invoicing the mandate covers.

Documents you issue

Transaction types on those documents

Where each party sits in the UAE five-corner model.

What clients ask first.

Does CargoWise produce PINT AE itself?

Do we need a WiseTech partner or developer?

Where does the audit firm come in?

What happens to a rejected invoice?

Who is the accredited service provider?

Why not connect CargoWise straight to an accredited service provider?

Will the PDF look like our CargoWise invoice?

Can we see invoices and reports in Alya Books, or only in CargoWise?

Bring your CargoWise invoices to the FTA with an audit firm behind the mapping.