Home / How it works
The process
What happens to an invoice after your ERP has written it
The short version: Cinnyx picks it up, turns it into PINT AE, checks it, prints the Arabic and English tax invoice and gets it ready for your ASP. Here is the longer version, and what your team actually sees.
Your ERP bills as usual
Nothing changes in how your team raises invoices. Someone in IT sets up an export once: a CSV or JSON file, a UBL file (Peppol BIS 3 is fine too) or a call to the Cinnyx API.
If your system has no export at all, invoices can be uploaded in the browser or typed into a form. That is meant for small volumes.
Cinnyx picks the file up
The service checks the inbox folder at a fixed interval, every minute for example, and handles each file on its own. If a network drive drops out for a moment, the files simply wait for the next run. Nothing is lost and nothing is sent twice.
Your fields become PINT AE
Which column of your export goes into which field of the e-invoice is set up once, together with us. Your fixed details, such as your TRN, legal name, address and the default tax category, live in the settings.
The UAE adds things a European invoice does not have: the transaction type flags, the emirate of supply, an AED tax total when you invoice in another currency. Cinnyx fills what it can from your settings and asks for the rest.
Amounts are copied, not recalculated. If you want Cinnyx to fill missing line amounts or the AED totals from the exchange rate on the invoice, you can turn that on. Every value it fills is then listed in the report.
The check
Every invoice runs through the official OpenPeppol PINT AE schematron, version 1.0.4, inside Cinnyx. Typical findings: a TRN with the wrong length, a missing emirate, a VAT amount that does not match 5 % of the line, a credit note without the invoice it corrects.
An invoice that fails goes to the error folder, with the rule and a plain-language explanation. It is not sent. Once it is fixed in the ERP, you send it again with one click.
All or nothing
If you produce the PINT AE file and a PDF, and one of them cannot be written, neither is. Half an invoice never reaches your ASP or your customer.
The bilingual tax invoice
Next to the XML, Cinnyx prints a PDF tax invoice in Arabic and English, with your logo. Arabic is shaped and set right to left the way a reader expects, not as disconnected letters.
Handover to your ASP
The checked PINT AE file lands in the outbox, ready for your Accredited Service Provider. A direct connection to your ASP's REST API or SFTP server, with a delivery queue and automatic retries, is in final testing and will be released once it has passed against a live ASP.
Received invoices
The other direction works too
Your suppliers will send you PINT AE through their ASP. Somebody has to get those into your ERP.
Arrive
Your ASP drops received invoices into a folder or sends them to the Cinnyx inbound API.
Check
Each one is checked against the same PINT AE rules, so you know if a supplier sent something broken.
Approve
Optionally, someone matches it against the purchase order and approves it before it goes further.
Import
Cinnyx writes CSV, JSON or UBL in the layout your ERP expects. No retyping.
Getting started
How we get you to your first live invoice
Not a big project. Most of the time goes into your special cases, not into the software.
Call and samples
You show us what your invoices look like today, including the awkward ones: credit notes, foreign currency, free-zone customers, government buyers.
Trial run
We convert your samples and show you the result with the full rule report. Whatever is missing, you see in black and white.
Install
Cinnyx goes onto your server, as a Windows service or in Docker. Your IT team usually needs about half a day.
Go live
The first real invoices go out. For the first weeks we watch the error list with you. After that, only when you need us.
See it with your own invoices
On the demo call we take one export from your ERP and run it all the way through.