Spreadsheets are where many Tunisian PMEs start—and where growing teams get stuck. One Excel workbook for invoices, another for stock, a Google Sheet the sales manager edits on mobile: it works until TTN El Fatoora applies to your activity and your expert-comptable asks who changed a line last March. The risks are version chaos, a TTN gap your sheet cannot close, and an audit trail that does not survive review.
This guide explains why spreadsheet accounting breaks down as headcount and invoice volume rise, and how to migrate without losing historical data. Operational guidance only—confirm obligations with your accountant or DGI advisor.
Why version chaos is the first failure mode
Spreadsheets have no single source of truth once more than one person edits them. Typical patterns: Compta_v2_FINAL.xlsx on the finance PC, Compta_v2_FINAL_ahmed.xlsx in email, and a Drive copy someone rolled back without telling anyone. Invoice numbers diverge. VAT totals no longer match declarations. Bank reconciliation becomes detective work.
- Email attachments create parallel universes—each reply is a fork
- Manual invoice numbering breaks when two people issue on the same day
- Copy-paste from WhatsApp PDFs introduces typos in client tax IDs
- Month-end close requires merging tabs nobody documented
Version chaos is a tooling limit, not just discipline. Excel and Sheets were built for analysis, not concurrent operational accounting with enforced sequencing. A five-person SARL with warehouse and field sales usually crosses that line faster than founders expect.
The TTN gap: spreadsheets cannot clear El Fatoora
Tunisian e-invoicing through TTN El Fatoora requires TEIF XML, a qualified digital signature, and clearance before many invoices count as legally issued. Spreadsheets produce numbers and maybe a PDF—they do not produce signed TEIF, submit to TTN, or store the official reference and QR code B2B clients expect.
Teams bridge the gap by retyping rows into TTN's web portal or maintaining fragile export scripts. Retyping invites transcription errors. Scripts break when TTN schema or certificate renewal changes. Neither path shows which rows are draft, submitted, cleared, or rejected.
Our TTN El Fatoora guide for Tunisian SMEs walks through enrollment and clearance. For spreadsheet users: compliance is structured data and signing—not a column beside Total TTC.
- Inventory what you issue
List invoice types and volumes; separate internal trackers from legally issued documents.
- Map columns to TEIF fields
Customer tax ID and VAT codes must match master data—not free text in column D.
- Pilot integrated software one cycle
Parallel-run old sheet and new system for one billing month before cutover.
- Archive sheets read-only
Keep historical workbooks as evidence, not live ledgers.
Audit trail gaps that fail reviews
Auditors ask: who created this invoice, who modified the amount, when was it sent, and what was declared? Spreadsheets offer weak answers. Excel cell history is limited and often disabled. Sheets revision history does not tie changes to approval steps or declaration batches. Deleting a row can erase the story.
TEJ reporting and VAT declarations need traceability from transaction to filed totals. Pivoting tabs for TEJ exports compounds errors silently. Integrated systems log user actions, invoice states, and export snapshots—the audit trail growing PMEs need before a formal audit.
- No immutable record of invoice state (draft → cleared → paid)
- Formulas overwritten with pasted values—logic lost
- Shared Windows logins—actions attributed to nobody
- Credit notes handled by editing rows instead of linked reversals
If you report TEJ withholdings, see our guide on TEJ reporting obligations in Tunisia—spreadsheet pivots often mismatch operational invoices and declared withholdings.

When spreadsheets are still reasonable
Sheets remain fine for cash-flow models and scenario planning. A solo founder with few monthly invoices and an accountant who owns TTN entry may stay on sheets longer—if one owner controls numbering. The inflection point is multiple editors, TTN scope covering your activity, or clients rejecting uncertified PDFs.
Choosing software without repeating spreadsheet mistakes
Pick software with Tunisian fiscal fit—not generic international SaaS. Use our checklist on choosing invoicing software for a Tunisian PME: verify TTN integration, certificate handling, role separation, and accountant access. Clean master data before import—deduplicate clients, normalize tax IDs, document opening balances.
How Hesabi addresses these risks
Hesabi on hesabi.tn targets Tunisian SME finance: local VAT logic, TEJ-oriented reporting, audit trails, and TTN-era workflows—not a spreadsheet with a login screen. Tunisia-only today by design.
Evaluate a move off Excel with a structured pilot: one product line, one month, accountant in the loop. Measure time to month close, TTN rejection rate, and hours retyping between systems.
Can I keep Excel for reporting after moving invoicing to software?
Yes—export cleared data monthly for analysis. The operational ledger should live in one system; sheets become read-only views, not competing masters.
We use TTN's web portal manually—is that enough?
Low volume may work short term, but portal entry from sheets reintroduces transcription risk as volume grows. Integrated software reduces double entry.
How long does migration from spreadsheets take?
Master data cleanup often takes longer than setup. Plan two to six weeks: clean clients and products, run one parallel billing cycle, then cutover with accountant sign-off.
What if staff resist leaving Excel?
Train on one workflow first—invoice from draft to clearance. Show how version conflicts disappear with a shared customer record.
Is Hesabi available outside Tunisia?
No. Hesabi is built for Tunisian fiscal rules only.



