ERP · Decision guide
Custom ERP vs Odoo: how an SME should choose
Custom ERP or Odoo? An honest decision grid for SMEs: process fit, recurring costs, Tunisian tax rules, code ownership, and when Odoo is the better choice.
Invoicing · Tunisia
Since 1 January 2026, mandatory e-invoicing in Tunisia extends to the provision of services, on top of large companies’ sales to the State and trade in medicines and fuels between professionals. Invoices go through Tunisie TradeNet (TTN). For your software, the real work is the data model: mandatory details, tax ids, statuses and archiving.
We build ERP and invoicing software for Tunisian companies. This guide keeps two things apart: what the official texts say, quoted from the Ministry of Finance's common note n° 02/2026, and what we draw from them when we design software. It is written for product teams, ERP vendors and finance leads who deal with Tunisian invoices. It is not tax advice. Reference date: 19 October 2026.
Three kinds of transactions, under Article 18 of the Tunisian VAT Code as explained by common note n° 02/2026: sales to the State, local authorities and public bodies by companies under the Large Enterprises Directorate; sales of medicines and fuels between professionals, retailers excepted; and, since 2026, the provision of services.
The scope of electronic invoicing was extended by Article 53 of Law n° 17 of 2025, dated 12 December 2025, on the Finance Law for 2026, to include service provision operations.
The note narrows the scope in practice: the obligation targets providers who declared a service activity in their declaration of existence, whether as their main or a secondary activity. It explicitly includes non-commercial professions that issue fee notes (notes d’honoraires), for all the services they provide, and recalls that these professionals must register for VAT.
The extension to services applies from 1 January 2026, first to providers already connected to the e-invoicing network who meet Article 18 of the VAT Code and Decree n° 2016-1066. Providers whose registration with TTN is still being processed may keep issuing paper invoices. Those who have not applied must file their request.
Government Decree n° 2016-1066 of 15 August 2016 sets the conditions for issuing and storing electronic invoices and entrusts the system to Tunisie TradeNet (TTN), the authorised body. TTN records and stores e-invoices, gives a copy to the issuer or the recipient on request, and automatically sends a copy to the Ministry of Finance.
Three steps belong to the company, not to its software: registering with TTN; filing a declaration with its tax office, on the administration’s form, together with TTN’s certificate of registration; and obtaining the means of electronic signature. The software then has to produce each invoice with the right details, get it signed, transmit it and keep the reference it receives.
The note excludes other documents that stand in for invoices: contracts, debit notes and account statements accepted as such by the customs of certain sectors. It also excludes services attached to the main activity, such as transport or installation at the time of a sale, unless they are declared as a secondary activity.
For software, the consequence is concrete: the document type must be an explicit field, not a numbering habit. A sales invoice that carries an installation line and an installation invoice issued under a declared secondary activity follow different paths. If your tool cannot tell them apart, it cannot decide which ones to transmit either.
Article 71 of the 2025 Finance Law sets a fine of 100 to 500 dinars per invoice issued on paper for a transaction that must be invoiced electronically, capped at 50,000 dinars for all the invoices found. Penalties for missing mandatory details now also apply to electronic invoices.
Buyers are protected on one point: according to the same note, an issuer’s failure to follow the electronic regime does not remove the buyer’s right to deduct VAT, as long as the buyer holds a paper invoice that complies with Article 18 of the VAT Code. The risk sits with the party that invoices.
The same mandatory details as a paper invoice: date of the transaction, the customer's identity and address with its tax identification number where it is registered, the supplier's tax number, description and price excluding VAT, VAT rates and amounts, and any suspended tax. An e-invoice adds the issuer's signature and TTN's unique reference.
| Mandatory detail | Field in the software | Control to build in |
|---|---|---|
| Date of the transaction | Transaction date, separate from the entry date | Frozen at validation |
| Customer's identity and address | Structured customer record | Copied onto the invoice when it is validated |
| Customer's tax number (matricule fiscal) | Dedicated field with a format check | Required for registered businesses; individuals accepted without one |
| Supplier's tax number | Company settings | Printed on every document |
| Description and price excluding VAT | Lines: item, quantity, unit price, discount | Exact amounts with three decimals (millimes) |
| VAT rates and amounts | Rate per line and a summary per rate | Totals recomputed on the server |
| Suspended VAT | Reason and certificate reference | Invoice blocked without a valid certificate |
| Electronic signature (e-invoice) | Issuer's certificate | Applied at the right step of the flow |
| TTN unique reference (e-invoice) | Identifier and status returned by TTN | Stored and printed on paper copies |
Printing matters in two situations. A paper copy of an e-invoice, handed to a customer who asks for it or carried with goods subject to roadside checks, must state that it is a copy of an electronic invoice registered with the authorised body under a unique identifier, with stamp and signature, which a visible electronic seal may replace. And a delivery note stands in for an invoice during transport if it shows at least its date, the names and addresses of sender and recipient, and the nature and quantity of the goods.
Six things we learned building ERPs for Tunisian companies: exact amounts in millimes, a structured tax identity, totals computed on the server, exemptions that block, a traceable chain of documents, and statuses that separate internal validation from acceptance by TTN. Everything else follows from those choices.
The Tunisian dinar has three decimals. We store amounts as numeric(14,3) in PostgreSQL, never as floating point, and display them the Tunisian way: 1 571,800 DT. On an invoicing application we deployed, the default decimal type rounded to two decimals, so 14.875 became 14.88, and 52 columns had to be migrated. Such gaps never show on screen; they show the day a statement, a VAT return and a bank transfer stop agreeing.
The customer’s tax number is a field, not a line of the address, and so is the customer type. In the ERP of Mohamed Damak et Cie, customers are segmented into companies, resellers, partners and investors. Structured identity lets you check the mandatory detail, filter statements and, later, fill an e-invoice without retyping.
The VAT rate sits on each line and the summary is computed per rate. Stamp duty and withholding tax are computed automatically too, as they are in the ERP of TSS Company. We run these calculations on the server from the lines received, never in the browser. Rates are settings, not constants in the code, because a finance law can change them.
A sale with suspended or exempted VAT must rest on a valid certificate. In the TSS Company ERP, an exempt invoice is blocked until a certificate valid at that date is on file for the customer. The same ERP tracks withholding-tax certificates (retenue à la source) and flags the missing ones, so nobody chases them at year end.
Quote, delivery note, invoice, then credit note or payment: each document is created from the previous one, which pre-fills the next. On the purchasing side, purchase order, receipt, supplier invoice. Two rules we recommend: the final number is assigned at validation, never to a draft, so the series stays continuous; and a validated invoice is never edited, it is corrected with a credit note.
With e-invoicing, “validated” is no longer enough. A robust model has at least: draft, validated and numbered, transmitted, accepted with its unique reference, or rejected with a reason. A rejection must lead to a clear action, a correction or a credit note, and the accepted reference must appear on every paper copy.
Adapt it if its data model already holds the mandatory details, a structured tax identity and clean statuses: signing, transmission and storage are what remains. Replace it if amounts are rounded, validated invoices can still be edited or customers are free text. E-invoicing would only expose those flaws, one rejected invoice at a time.
Questions to ask your vendor or development partner before deciding:
Connecting to TTN is a project of its own, scoped together with the company’s registration and signature certificate; the data model above is its prerequisite. It is the model behind our custom invoicing software, built into a custom ERP or connected to existing tools through API integration. If you are weighing a packaged ERP against custom development, read custom ERP vs Odoo. Terms such as withholding tax, stamp duty and TTN are defined in our glossary.
Where this applies
FAQ
Not for every transaction. It is mandatory for sales to the State and public bodies by companies under the Large Enterprises Directorate, for sales of medicines and fuels between professionals other than retailers and, since 1 January 2026, for the provision of services, applied progressively as providers complete their registration with TTN.
El Fatoora is the e-invoicing service of Tunisie TradeNet (TTN), the body designated by Decree n° 2016-1066 to run the system. TTN records and stores electronic invoices, gives each one a unique reference, provides copies on request and automatically sends a copy to the Ministry of Finance.
Yes, as a copy. When the customer asks for it, or when goods subject to roadside checks are transported, the issuer provides a paper copy stating that the invoice is registered electronically with the authorised body under its unique identifier, with stamp and signature, or a visible electronic seal instead.
Yes, if your product issues invoices for Tunisian businesses. The obligation falls on the Tunisian issuer, but your software must carry the mandatory details, three-decimal amounts, tax numbers, signature and the TTN reference. Building those into the data model early costs far less than retrofitting them after the first rejections.
Sources
External facts in this guide come from these documents. Examples from our projects are first-hand.
Keep reading
ERP · Decision guide
Custom ERP or Odoo? An honest decision grid for SMEs: process fit, recurring costs, Tunisian tax rules, code ownership, and when Odoo is the better choice.
Agencies · Delivery models
White-label development for agencies: what the agreement covers, who owns code and accounts, how a studio stays invisible, a sample week and a handover list.
Engineering · DevOps
How we run Next.js 16 and Strapi 5 on our own server: PostgreSQL, pm2, nginx, Cloudflare, six Strapi traps, and the cache header that kept old pages live.
Send us your current documents: we will tell you what your data model is missing.