BackboneAtlasSource to Pay
Book a demo
UAE e-invoicing

E-invoices from your ASP, checked before you pay.

Atlas takes in your suppliers' UAE e-invoices from your ASP. It reads each one, checks it and keeps it exactly as it arrived. Atlas connects to your ASP. It is not one, and it never reports to the FTA.

Where Atlas sits

Your ASP receives it. Atlas takes it from there.

The UAE model has five corners. Your supplier's ASP sends to your ASP, and both report to the FTA. Atlas is your system at corner four.

  • PulledAtlas collects from your connected ASP every five minutes.
  • PushedOr your ASP or ERP sends each file to the Atlas API. It uses a key you issue.
  • UploadedOr someone uploads the file. All three are read the same way.
  • Credit notesE-credit notes arrive as credit notes. A person approves or rejects them.
.../api/v1/einvoices
CORNER 1 Supplier issues the e-invoice CORNER 2 Their ASP sends it on Peppol CORNER 3 Your ASP receives it for you CORNER 4 · YOU Atlas your buying system CORNER 5 The FTA gets reports from both ASPs THREE WAYS IN Pulled every 5 minutes Pushed to the API Uploaded by hand Atlas reads PINT AE, and Peppol BIS, UBL and Factur-X. Atlas is not an ASP. It never reports to the FTA.
The five cornersWhere Atlas sits, and who reports to the FTA.
Before anything is lodged

Every e-invoice is checked. A failure is refused, with the reason.

Atlas reads PINT AE, the UAE format. It knows the six FTA document types and the transaction flags.

  • SellerThe supplier's TRN is there, in the right format, on a tax invoice.
  • BuyerOne addressed to another company's TRN is refused.
  • VAT in AEDA tax invoice in another currency states its VAT in AED too.
  • CurrencyIt is in the same currency as the purchase order.
.../invoices?view=incoming
FROM YOUR ASP E-invoice or e-credit note CHECKED ON ARRIVAL One of the six FTA types 380 · 381 · 480 · 81 · 389 · 261 The seller's TRN on a tax invoice: present, right format The buyer's TRN if it names one, it must be yours VAT stated in AED when it is in another currency The order's currency PASSES Lodged against its purchase order FAILS Refused the reason shows on the incoming queue
The checksWhat is checked, and what happens when a check fails.
The mandate, at payment

No e-invoice, no approval for payment.

Switch the mandate on for your organization, from a date. A UAE supplier's invoice typed into the portal is then advance notice only.

  • HeldIt cannot be approved for payment until the e-invoice arrives from the ASP.
  • AttachedThe e-invoice attaches itself to that record. If the figures differ, it is held as a mismatch.
  • Per supplierGive a supplier its own start date. Or record it as outside the mandate, with a reason.
  • Off by defaultNothing changes until you switch it on.
.../settings
IN THE PORTAL Typed invoice from a UAE supplier: advance notice only THE GATE Held cannot be approved for payment yet RELEASED Approvable for payment, once the e-invoice is attached FROM YOUR ASP The e-invoice same invoice number, arriving later ATTACHES ITSELF IF THE FIGURES DIFFER Mismatch held for a person to resolve Off until you switch it on, from a date. Per supplier: its own date, or outside the mandate with a reason.
The payment gateWhy a typed invoice waits for its e-invoice.
When you raise the invoice

Under a self-billing agreement, you issue the tax invoice.

Record the agreement on the supplier. Atlas then issues the PINT AE self-billed tax invoice for what you received.

  • MarkedEach one says “Tax Invoice raised by buyer”.
  • CorrectionsA mistake is corrected with a self-billed tax credit note.
  • No double billingThe supplier's own invoice for those supplies is refused.
  • Sent firstUnder the mandate, it must go through your ASP first. Only then can it be approved for payment.
.../pos
RECORDED Agreement on the supplier, with its dates ATLAS ISSUES Self-billed tax invoice · 389 tax credit note · 261 CORNER 3 Your ASP sends it on CORNER 1 Supplier receives it Marked: “Tax Invoice raised by buyer” REFUSED The supplier's own invoice for the same supplies, so nothing is billed twice UNDER THE MANDATE Sent before payment not approved for payment until it has gone through your ASP
Self-billingIssued by you, sent through your ASP.
Telling the supplier

Suppliers hear what happened to their invoice.

An optional setting, for invoices that arrived as e-invoices. Atlas writes a Peppol Invoice Response at each step. Your ASP carries it to the supplier.

  • ReceivedWhen the e-invoice is lodged.
  • QueriedWhen it does not match, or is disputed.
  • RejectedWhen it cannot be lodged, with the reason.
  • Approved, paidWhen it is approved for payment, and when it is marked paid.
.../integrations
AB Received when it is lodged UQ Queried a mismatch, or a dispute RE Rejected cannot be lodged, with the reason AP Approved for payment PD Paid marked paid EACH STEP SENDS ONE RESPONSE ATLAS Writes it a Peppol Invoice Response CORNER 3 Your ASP carries it CORNER 1 Supplier sees what happened Optional. Only for invoices that arrived as e-invoices. If your ASP cannot carry them, they wait for you to send.
Invoice responsesOne answer at each step, through your ASP.
Kept as it arrived

Every e-invoice kept exactly as it arrived.

UAE guidelines allow storage outside the UAE on three conditions: integrity, retrievability and reproducibility. Atlas is hosted in Toronto, Canada.

  • IntegrityA SHA-256 fingerprint is taken the moment a file arrives.
  • CheckedIt is checked each time the file is opened. A changed file is not handed out, and the screen says why.
  • RetrievableThe latest files are listed on the incoming queue, each with its fingerprint.
  • ReproducibleDownload gives you the original file, exactly as it came.
.../invoices?view=incoming
UAE CONDITION Integrity UAE CONDITION Retrievability UAE CONDITION Reproducibility ON ARRIVAL Original file kept exactly as it was sent ALSO ON ARRIVAL SHA-256 fingerprint recorded EACH TIME IT IS OPENED Checked again Match: the original is served Changed: refused, and says why Hosted in Toronto, Canada. UAE guidelines allow storage outside the UAE on these three conditions. Documents you issue are kept the same way. The latest are listed on the incoming queue, with fingerprints.
The archiveThe three conditions, and what Atlas does for each.
Said plainly

What Atlas is not.

Atlas is your buying system, at corner four. Some jobs belong to your ASP, and stay there.

  • Not an ASPAtlas is not an Accredited Service Provider. You still need one.
  • No FTA reportingAtlas never reports to the FTA. Your ASP does that.
  • No sales invoicesAtlas does not issue your sales invoices. It issues only self-billed ones, under an agreement.
  • Not yet proven liveAdapters for accredited providers are built from their published APIs. None has run on a live account yet. Any ASP or ERP can deliver through the API today.
.../integrations
ATLAS · CORNER 4 Does Receives from your ASP Checks each document Holds approval for the e-invoice Issues self-billed invoices Answers suppliers Keeps the archive NOT ATLAS Does not Act as an ASP Report to the FTA Issue your sales invoices Those jobs belong to your ASP, and to your own sales system. Adapters for accredited providers are built from their published APIs. None has run on a live account yet. Any ASP or ERP can deliver through the API today.
What Atlas does, and does notAtlas works at corner four. The rest is your ASP's job.