You have two ways to meet the El Fatoora rules: buy invoicing software that already speaks the platform, or connect the system you use today. The right choice depends on one question: can your current system give you clean invoice data? This article lists what TTN publishes for integrators and what to ask before you decide.
What TTN gives integrators
TTN publishes a specification archive with the TEIF guide and XSD files, a web service specification and an SFTP specification, plus a document on signatures. The two exchange channels work like this:
- Web service. The specification lists operations to deposit a signed TEIF invoice (saveEfact), to search invoices by number, TTN reference, date or amount (consultEfact), and to check a QR code. Calls carry a login, a password and the taxpayer identifier. The version in the archive is dated 2016, so ask TTN for the current one.
- SFTP. Each taxpayer has a directory named after the tax identifier, with an “in” folder to drop invoices and an “out” folder to read answers. Only XML files are accepted, named after the invoice number. A valid invoice returns number.xml and an invalid one returns number.error.
Both channels expect the same thing: a TEIF file with one valid signature.
Option 1: new invoicing software
This makes sense when your current tool cannot export structured invoice data, or when nobody maintains it. Ask the vendor:
- Does it produce TEIF that validates against the current XSD?
- Does it sign with a certificate that ANCE accepts, and is its signing solution approved by ANCE, as TTN requires?
- Does it read TTN’s answers and show accepted and rejected invoices?
- Does a retry ever create a duplicate document?
- Does it store the reference TTN assigns, and can it print the paper copy?
- Can you export all your data if you leave?
Ask for a demonstration of a real submission, not a screenshot of a dashboard.
Option 2: connect the ERP you already have
This makes sense when your ERP or accounting software already holds good invoice data and exposes an API or a structured export. The connection has four jobs:
- Map your invoice data to TEIF, including credit notes, several VAT rates and foreign currencies if you use them.
- Sign the file once, in its final form, with your certificate.
- Send it through the web service or SFTP and read the answer.
- Keep the signed file, TTN’s reference and any rejection, and let a person fix a rejected invoice.
The data stays in your ERP. You change one step in how an invoice leaves it.
Steps before going live
The Ministry of Finance note of January 2026 and decree no. 2016-1066 set the administrative steps (note commune 02/2026, Arabic). The issuer must:
- join the TTN network;
- file a declaration with the competent tax office, using a form prepared by the administration and attaching the certificate TTN issues to prove membership;
- sign each invoice with an electronic signature and carry the unique reference TTN assigns.
Add to these a signing certificate from a provider ANCE recognises. TunTrust describes a company seal that lists electronic invoices among its uses.
How to decide
Count the invoices you issue, the systems that issue them and who maintains them. If one system issues all your invoices and it exposes data, a connection is usually a smaller change than a migration. If invoices come from a spreadsheet, or the system is end of life, new software is the cleaner start. Get written quotes for both and compare the yearly cost, not only the first invoice.
Axynoxia builds these connections. See our El Fatoora integration service. We also built Axynoxia Invoice, an invoicing platform prepared for Tunisian electronic invoicing, as a demo you can open. We do not present it as a certified solution.
Questions
Do I need to replace my ERP to issue El Fatoora invoices?
Not necessarily. If your system holds clean invoice data and has an API or a structured export, a connection can produce, sign and send the TEIF file. If it cannot, new software is the better start.
How do I send invoices to El Fatoora from my own system?
TTN publishes two channels: a web service to deposit signed TEIF invoices, and an SFTP exchange with an in folder and an out folder per taxpayer. Ask TTN for the current versions of both specifications.
What should I ask an invoicing software vendor?
Whether it produces valid TEIF, signs with an ANCE-accepted certificate through an ANCE-approved solution, reads TTN answers, avoids duplicates on retry, stores TTN references and exports your data.
What are the administrative steps before the first invoice?
Join the TTN network, file a declaration with the tax office with the membership certificate from TTN, and obtain a signing certificate that ANCE recognises.
Sources
- TTN, El Fatoora specification archive (TEIF guide, XSD, web service and SFTP specifications)
- TTN, Technical specifications of the electronic signature, version 3.0 of 29 May 2026
- Ministry of Finance, note commune no. 2/2026, recalling decree no. 2016-1066 (Arabic only, Jibaya)
- TunTrust, Enterprise-ID electronic seal
Related reading: who must issue electronic invoices, TEIF and the electronic signature and penalties and common mistakes.
This article is general information based on the texts cited. It is not legal or tax advice. Confirm your situation with your accountant.
Axynoxia connects existing invoicing software to El Fatoora and reviews setups before go-live. See the integration service or book a discovery call. You can also open Axynoxia Invoice, our invoicing platform prepared for Tunisian electronic invoicing, at invoice.products.axynoxia.com.