Submit to Taxilla and FTA reporting

Alya Books reports e-invoices to the FTA through Taxilla, an accredited service provider (ASP). Submission sends the PINT AE XML to Taxilla, which validates it, delivers it to the buyer's access point and forwards the tax data to the FTA.

1. Check the mode under Settings → E-invoicing: Test (simulated), Taxilla UAT or Taxilla Live. The banner above the editor shows the active mode.
2. Open a Validated invoice and click Submit to Taxilla. From Invoices you can also use the row menu or select several invoices and click Batch Submit. Alya Books checks the invoice once more before sending; if it no longer passes validation it returns to Draft and the message names what to correct.
3. Follow the E-invoicing Submissions card. While a submission is in flight the page checks the status every few seconds; click Refresh status to check now. You do not need to keep the page open: Alya Books also checks in the background (every 5 minutes at first, then less often) and notifies you when the invoice is reported or rejected. If there is still no final answer after 7 days, automatic checks stop and you get a notification.
4. When the last step is green, the invoice status is Reported and the bell shows "reported to the FTA".

Taxilla's files

Open the invoice and scroll below the invoice page to the E-invoicing Submissions card. Each attempt has its own entry, newest first, and download buttons appear as Taxilla returns each file:

Each file is fetched once from Taxilla's document flow and kept. Submissions made before October 2026 may also show Taxilla PDF (earlier format) and JSON report (earlier format), which Taxilla's earlier interface produced.

• An export to a buyer that is not on the Peppol network has no Buyer MLS: Taxilla sends only the tax data to the FTA, and the invoice is Reported once the FTA MLS arrives.

• Every version is kept. If Taxilla sends a changed file later, the button downloads the newest one and the older ones are listed under Earlier versions with their date and time.

• Nothing can be changed or deleted. These files, and the XML Alya Books sent, are kept as a legal record. For the same reason an invoice sent in UAT or Live mode cannot be deleted, even after a rejection.

• Earlier attempts keep their own files, so after a rejection and a new submission you can still download what was sent and returned the first time.

Rejections

Any step can fail. The card shows which stage rejected the document and the message, for example a buyer TRN error at Taxilla or an MLS RE response from the buyer or FTA. The invoice becomes Rejected and editable: fix it, click Validate & save, then submit again. A new attempt is listed above the old one.

If the card says "Could not reach Taxilla", nothing was sent. Check the connection in Settings → E-invoicing and submit again.

Good to know:

• Submission is refused while an approval is pending or declined, and for archived invoices.
• Each submission consumes credits (Settings → Subscription).
• The organization needs a real TRN and Peppol ID (0235:<TIN>, the TIN being the first 10 digits of the TRN), and the buyer contact needs a Peppol ID, for UAT and Live.
• Owners, admins and accountants can submit; only owners and admins can change the connection and credentials.
• Test-mode submissions are marked TEST and can be reset.

Related:

• Invoice statuses explained
• Test documents and the simulated ASP
• Understand validation errors