Buying Operations Software in Tunisia: A Straight Guide
One question separates vendors here faster than any feature list: compute 1,000 dinars plus FODEC plus VAT and show me the split. We publish what ours does, which is wrong, which is the only reason the question is fair to ask.
Buying operations software in Tunisia is unusually easy to get wrong, and not for the reasons a shortlist normally trips over. The interface language question is real and everybody raises it. The clearance question is real and most vendors will answer it. The one that gets missed is arithmetic: a Tunisian transaction carries up to five levies and no two of them share a base or a moment, and almost every system on your list holds tax as one rate applied to one net amount.
This guide is written to be used against us as much as against anyone else. Where our own answer is the wrong one, it is stated with the figure.
The five levies, and why the count matters
| Levy | A percentage of what | Decided when |
|---|---|---|
| FODEC, 1% | The net amount. Applies to a listed scope, at the production and import stages | At invoicing |
| VAT, 19% standard | The net amount plus the FODEC, where FODEC applies | At invoicing |
| Stamp duty | Nothing. A fixed sum per document, stepped by value for large retail | At invoicing |
| TCL, 0.2% local / 0.1% export | The period's turnover, with a minimum from floor area | At the return |
| Withholding, 1.5% ceiling — reduced to 1% or 0.5% by the payer's corporate tax bracket | A payment over TND 1,000 including VAT, assessed per payment rather than per invoice | At settlement |
Exactly one of those five is "a rate applied to the line at the moment the invoice is raised", which is the only shape a general finance system is built for. It is FODEC — the one nobody outside Tunisia has heard of.
Five levies, five bases, three moments. A system with one tax field is not slightly wrong here. It is wrong four times, in four different ways.
The ninety-second test
Ask any vendor to enter a thousand dinars with FODEC at 1% and VAT at 19%, and to show you the two tax amounts separately.
The two possible answers
There is no third answer. Either the system computes the levies in sequence against their own bases, or it adds the percentages. No amount of configuration moves a system from the second answer to the first, because the base reference it would need was never stored.
Our answer is 200.000, and there is a test in the repository that says so
AWRA OpsHub resolves the tax on a document by taking every tax type you have enabled and adding their default rates into one blended figure. Two taxes at 19 and 1 return 20, labelled with both codes joined together and no split between them. That reaches invoices, quotations, point of sale, the vendor portal and the API from twenty-one places in the code. We measured it rather than assumed it, and we pinned the behaviour with a test so that fixing it has to be a deliberate act. Two consequences: the total is short by 19% of the FODEC on every affected line, and because the figure is blended there is no VAT amount to put on a return. Both are reasons we are not the system that should be issuing your invoices in Tunisia.
The reason to publish that is not modesty. It is that the test is only a fair thing to recommend if we have taken it ourselves in public, and a vendor who has never been asked will usually answer confidently and wrongly.
The three purchases, and which order to make them in
What gets discussed as one system is three separate purchases here. Getting the order right saves more money than negotiating any of them.
Buy first, and buy locally
Clearance and statutory filing
El Fatoora, run by Tunisie TradeNet, clears invoices in TEIF XML with a signature and a QR code before they are valid — already mandatory for business-to-government within the Large Enterprises Directorate and for medicine and fuel sales between professionals, and extended to service providers from 1 January 2026 by Article 53 of the 2026 Finance Law. TEJ takes withholding declarations in XML from every company from the same date. Two obligations, two formats, both compulsory, both with penalties. This is the purchase with a deadline attached and it belongs with a local provider or your fiduciaire.
Buy second, and buy locally
Payroll and social contributions
Income tax bands, CNSS, TFP and FOPROLOS, filed in the layout the administration expects. A local payroll provider will be cheaper and correct, and the maintenance is the product rather than the software.
Buy third, if at all
Operations — cost, stock, procurement, evidence
What a thing actually cost once every charge arrived, where stock is, who approved what, and whether the document that evidences it can be found from the transaction. This is the one with no deadline, which is exactly why it is usually bought first and regretted.
A vendor claiming all three in one subscription in this market should be asked which of their customers has cleared an invoice through El Fatoora using their software, and to give you the name.
Questions worth asking, and what the answers mean
Ten minutes that will save you a quarter
Compute 1,000 with FODEC at 1% and VAT at 19%. Show me both tax amounts.
What you will hear
Usually a total of 200, and often no split at all.
How to read it
If the total is 200 the system adds rates. That is not a defect you can configure away, and it means the system cannot produce a compliant total or a splittable return where FODEC applies. Our answer is 200 and we have published it.
Are you connected to El Fatoora, and are you accredited?
What you will hear
A distinction between "we can export a file" and "we clear invoices".
How to read it
Producing TEIF XML, signing it, carrying the QR code and clearing before issue are four things. Ask which of the four they do, and ask for a customer name.
Do you produce TEJ output for withholding declarations?
What you will hear
Frequently confusion between TEJ and El Fatoora.
How to read it
They are two obligations, two platforms and two formats. A vendor who conflates them has not worked here, whatever else they can do.
Is a payment a record, or a status on an invoice?
What you will hear
A one-word answer, and it is usually "a status".
How to read it
The withholding threshold is measured on the payment, not the invoice, so a system where payment is only a status cannot evaluate it. Three invoices below the threshold settled in one transfer are above it.
Where does a fixed duty on a purchase document end up?
What you will hear
A charge line, or a miscellaneous expense.
How to read it
It is unrecoverable, so it belongs in the cost of what you bought. If it lands in an expense pool, your unit cost is understated by a knowable amount and nobody can attribute any entry in that pool to a purchase.
What are amounts stored to, and does the dinar have three decimals?
What you will hear
Rarely an answer without checking.
How to read it
Many systems store money to two decimal places, ours included. A millime cannot be held. Immaterial to a margin, not immaterial when a bank line carrying three decimals has to match a stored amount rounded to two.
French, Arabic, or right-to-left layout?
What you will hear
Sometimes a roadmap.
How to read it
Ask to see it, in a document your customer would receive. Right-to-left is a build rather than a translation, and a roadmap is not a capability. We have none of the three and say so on the first screen.
Who supports us, from where, in which language, and what happens when the implementer leaves?
What you will hear
A time zone, and a pause on the second half.
How to read it
The second half is the question that actually separates vendors, here and everywhere. Ask it of us as bluntly as you ask anyone.
What is genuinely easier here than the shortlist suggests
Two things, and it is worth saying them because a guide made only of warnings is not a guide.
The export-facing half of this economy is well served by ordinary operations discipline. A manufacturer selling into Europe under a suspension regime has a landed-cost problem, a traceability problem and a document-retention problem, and none of those are Tunisia-specific. The tax complexity above sits on the domestic side of the ledger; a wholly exporting operation buying VAT-free under authorisation is dealing with a document rather than an arithmetic.
And the time zone is a non-issue. Tunisia is two hours behind Nairobi, so almost the whole working day overlaps. That is a fact about geography rather than a substitute for a local partner, and it should not be presented as one.
What to insist on in writing
- The arithmetic answer, in writing: what does the system return for 1,000 with FODEC at 1% and VAT at 19%, and are the two amounts stored separately?
- Whether the vendor clears to El Fatoora or exports a file, with a customer name against the claim.
- Whether TEJ output exists, named as a separate thing from clearance.
- Whether payment is a record with the invoices it clears, in the demonstration rather than in a brochure.
- What money amounts are stored to, in decimal places, and what happens at bank reconciliation if the dinar has three.
- Which interface languages exist today, shown in a document a customer would receive.
- What happens when the person who implemented your system leaves — the answer, not the reassurance.
None of the Tunisian pipelines are built today — and all of them are buildable
"Not built in" describes what ships in the standard product, not the limit of what AWRA OpsHub can do in Tunisia. Kenya's eTIMS integration exists because Kenyan clients needed it and commissioned it; it did not appear by itself. The same door is open here. The honest ordering matters though, and it is different from every other market in this series: the arithmetic comes before the pipeline. A cleared invoice carrying a total that is short by 19% of the FODEC is worse than no clearance at all, so a compounding tax base would be the first thing built and El Fatoora the second. If either is what stands between you and a decision, tell us and we will scope it as a build — written spec, timeline and price — before you commit to anything.
A compounding tax base
A base that can contain another levy, computed in sequence rather than by adding rates, with each amount stored separately so a return can be split. First, because everything else depends on the total being right.
El Fatoora clearance
TEIF XML through Tunisie TradeNet, signed, QR-coded and cleared before issue — built against the published specification rather than against a description of it.
TEJ declaration output
Withholding declarations and certificates in the XML the platform accepts, generated from the payment records rather than re-keyed from them.
A French or Arabic interface
Interface text and document templates in French, or in Arabic with genuine right-to-left layout — a build rather than a translation, and quoted as one.
A Tunisian payroll engine
Income tax bands, CNSS, TFP and FOPROLOS on live employee records. Worth saying that we would still recommend a local provider for this one first.
The verdict
Buy the clearance and the payroll locally, on the deadlines that come with them, and buy them first. Then decide whether you have an operations problem worth solving separately — cost that is true once every charge arrived, evidence retrievable from the transaction, approvals that refuse rather than warn. Test every vendor with the thousand-dinar question before anything else on your list, because it takes ninety seconds and it cannot be answered with a roadmap. Ours returns 200 where Tunisia charges 201.900. We would rather you knew that from us than found it in month four.
Ask us the thousand-dinar question
We have published the answer, the direction of the error and the number of places in the code it reaches. Bring one supplier invoice and we will tell you honestly which half of your problem we are for.
Talk to us about Tunisia