Outgoing invoices

The right format. Submitted with proof.

PINT AE for the UAE buyer, PDF and XML by email for the buyer abroad. Alya Books produces the right document for each recipient, validated against the FTA's business terms, and reports it through Taxilla. You focus on your business.

Start for free Request a demo

PINT AE
Taxilla ASP
FTA reporting
Delivery log

Status quo

The invoice goes out. And comes back.

Wrong field, invoice rejected

A missing buyer TRN, a VAT category without an exemption reason or totals that do not tie: the ASP or the FTA rejects the document, it has to be reissued and payment is delayed.

Which route for which buyer?

Peppol for UAE businesses with a provider, email for everyone else, and self-billing for agency models. Without a system, the choice is made by hand every time.

Sent, but no proof

Was it delivered? Was it reported? Without a log, queries from buyers and auditors pile up.

Your workflow

Four steps. Format checked. Proof included.

One continuous process instead of format questions, portal logins and manual checking.

01
Create
Enter in the editor, start from a quote, a recurring template or a copy, import lines from Excel, or hand over via API. Guided entry for every mandatory field.
- Editor
- Templates
- API
- Excel
02
Check
Alya Books validates business terms, VAT logic and totals against PINT AE before submission. Optionally a structured approval before dispatch.
- PINT AE
- Approvals
03
Submit
One click hands the document to Taxilla, which transmits it over Peppol and reports the tax data to the FTA. Status comes back as submitted, delivered, accepted or rejected.
- ASP
- Peppol
- FTA
04
Deliver
The buyer receives PDF and XML by email (and by Peppol where registered), with a pay-by-link button if you use a gateway. Every delivery is logged.
- Email
- Pay link
- Delivery log

Result: Reported and delivered, proof included. Format checked before submission, so rejections become rare.

How companies use Alya Books

Invoice delivery straight from their own system.

Invoice data arrives via the REST API from the existing ERP: Alya Books converts it into PINT AE, checks it, submits and delivers it. The status comes back via webhooks, and the archive fills itself.

For your setup

Three typical situations. Three ways to bring Alya Books in.

Suppliers to government and large buyers

Mandatory fields and structure checked automatically
Direct delivery via Peppol, proof included
No portal logins, no manual reformatting

Companies with many business customers

Every buyer gets the right route: Peppol or email
Bulk issuing via the REST API and recurring invoices
Pay-by-link and reminders to get paid sooner

Companies with an existing ERP

The API or a connector hands invoice data to Alya Books
Alya Books converts, validates, submits
The status goes back into the ERP automatically

Compliance and security

Compliance that takes care of itself.

FTA reporting

Every issued document is reported through an FTA-accredited service provider; the ASP and FTA timeline is kept on the invoice.

Records

XML, PDF, the service provider's responses, delivery log and audit trail are kept together. Once an invoice is sent they cannot be changed or deleted, and you can export them at any time.

Access control

Roles and granular permissions decide who may create, approve, submit or delete; every action is logged with user and time.

The right format. For every buyer.

Send your next invoice in PINT AE, with proof.