The short answer
If you run a VAT-liable service business in Tunisia (law firm, accounting practice, medical office, architecture or engineering studio, consulting, IT services, hotel, restaurant, agency), electronic invoicing through the El Fatoora platform (Tunisie TradeNet) has been legally mandatory since January 1, 2026, under Article 53 of the 2026 Finance Law. Roughly 380,000 businesses, about 85% of Tunisia’s service economy, are affected (TTN El Fatoora).
The mandate arrived in two stages, which is worth knowing because it explains why some of your suppliers were already sending compliant invoices before you were required to:
| Date | Who it covered |
|---|---|
| 1 July 2025 | Large companies |
| 1 January 2026 | Generalisation to all VAT-liable service providers |
On enforcement, the honest position: the fines written into the 2026 Finance Law are real and are stated below, but as of September 2026 they have not yet started being applied. Tunisian practitioners expect enforcement during 2026 or early 2027, and no official date has been confirmed. Treat that as time to get compliant, not as a reason to wait: the obligation is already in force, and the slowest step is a physical token with a lead time.
What the law actually requires
A compliant invoice is not a PDF sent by email. It must be:
- Generated in TEIF format: the Tunisian Electronic Invoice Format, an XML structure based on the international UBL 2.1 standard with local specifics defined by the INNORPI TTN 2026 norm: mandatory fields, a unique invoice identifier, and a QR code.
- Digitally signed with a qualified electronic certificate issued by ANCE (TunTrust), delivered as a USB cryptographic token, roughly 350 TND excluding tax, valid two years. The signature format is XAdES-B, not a generic PDF signature, which is the detail most software gets wrong (TTN El Fatoora).
- Submitted to El Fatoora (Tunisie TradeNet’s platform), which validates and registers the invoice before it has legal value.
The two ways to comply
1. Manual portal entry. You can type invoices directly into the El Fatoora web portal. Workable if you issue a handful of invoices a month; painful and error-prone beyond that.
2. Software integration. Your invoicing software generates the TEIF XML, signs it, and submits it to TTN automatically. You keep your normal workflow and the compliance happens underneath. This is the only realistic path for businesses invoicing weekly or daily, and for accountants managing many clients.
What to do this month if you’re not compliant yet
- Get your ANCE/TunTrust certificate: the lead time on the physical token is the slowest step, so start it first.
- Open your El Fatoora account with Tunisie TradeNet.
- Decide portal vs. software based on your invoice volume, and if your current invoicing tool can’t produce TEIF, that’s the gap to close now, not after a tax control.
What it costs to get it wrong
The 2026 Finance Law attaches real numbers to non-compliance, and they are worth knowing before deciding the portal is “probably fine”:
- Issuing a paper invoice where a compliant electronic one was required: 100 to 500 TND per document, capped at 50,000 TND per year.
- Issuing a non-compliant electronic invoice (wrong format, missing signature, rejected by the platform): 250 to 10,000 TND, doubled on repeat offence.
The per-document structure is what catches people out. A business issuing forty invoices a month on paper is not risking one fine, it is risking forty, and it reaches the annual cap faster than it expects.
The archiving obligation nobody budgets for
Compliance does not end when the invoice is accepted. Invoices and the evidence of their transmission must be archived for ten years.
That is a longer retention window than most small businesses have ever had to plan for, and it has two practical consequences. The signed XML is the legal artefact, not the PDF you send the client, so archiving the PDF alone does not satisfy the obligation. And ten years is long enough that “it is in the software” is only an answer if you are confident the software, and the company behind it, will still be there.
If you take one thing from this section: ask your invoicing provider, in writing, how you get your signed TEIF files out if you stop being their customer.
What is actually inside a TEIF invoice
Useful to know, because it explains why a PDF cannot be retrofitted:
- Structured header data: issuer and recipient tax identifiers, invoice number, dates, currency
- Line items as machine-readable fields rather than text in a table
- Tax breakdown per rate, which the platform validates arithmetically
- A unique invoice identifier and a QR code
- The electronic signature block, bound to the content
The platform checks these before the invoice has any legal standing. An invoice that fails validation has not been issued, even though you sent it.
The honest caveat
If you issue two or three invoices a month, the portal is fine and you don’t need to buy anything beyond the certificate. The businesses at real risk are the ones invoicing at volume on tools that were never built for Tunisian compliance. Foreign SaaS products won’t add TEIF support for a market this size.
Common questions
Does this apply to B2C invoices, or only B2B? The obligation follows VAT liability, not the type of customer. If you are VAT-liable and the transaction requires an invoice, it requires a compliant one.
I already use accounting software. Am I covered? Only if it produces TEIF XML, signs it with your ANCE certificate and submits it to TTN. Producing a nice-looking PDF is not the same thing. Ask your vendor for the TEIF output specifically, not for “e-invoicing support”.
What if my software is foreign? International invoicing products are unlikely to add TEIF for a market this size. If your tool is foreign and you invoice at volume, integration or replacement is the realistic path, and it is better decided now than during a tax control.
Can my accountant do it for me? They can file on your behalf, but the certificate is issued to your business and the legal obligation stays with you. Accounting practices managing many clients generally need integration rather than portal entry, simply because of volume.
How long does the certificate take? The ANCE/TunTrust token is a physical device, and that lead time is usually the slowest part of the whole process. Start it before anything else.
What happens if an invoice is rejected? It has not legally been issued. Correct and resubmit. This is the failure mode that quietly accumulates penalties, because the invoice looks sent from your side.
Where we fit
Axynoxia builds software for exactly this kind of problem, where a regulatory requirement meets a daily operational workflow, and we are building El Fatoora/TEIF compliance into our own invoicing platform, ProInvoice.
If you already run an ERP or invoicing system you like, the usual answer is not to replace it. It is to connect it: generate the TEIF XML, sign it, submit it, and leave the workflow your team already knows exactly as it is.
If you want to know whether the portal is enough for your volume or whether you need real integration, book a 15-minute call. We will tell you honestly, including when the answer is that you do not need us.
If you need integration, we start with a fixed-price compliance audit: 1,200 TND excl. VAT, delivered in 5 working days and credited against the integration if you go ahead within 30 days. See what the audit covers.