How to choose invoicing software for a Tunisian PME

Choosing invoicing software for a Tunisian PME is not the same as picking the app with the prettiest PDF template. Your shortlist must survive TTN El Fatoora clearance, VAT lines your accountant accepts, TEJ-related payment tracking, and day-to-day use by non-finance staff.

We see three failure modes: buying a global SaaS that ignores Tunisian clearance, staying on Excel because migration feels risky, or adopting a local tool that cannot export what your expert-comptable needs. This checklist helps you evaluate options before you migrate customer data and train the team.

Start with your compliance profile

Before comparing features, write down facts your accountant already knows: VAT registration, TTN enrollment status, monthly invoice volume, percentage of B2B vs B2C, and whether you pay external consultants subject to withholding. Software fit follows compliance reality—not the other way around.

• Are you in scope for mandatory El Fatoora e-invoicing in 2026?
• Do you need TEJ-oriented exports for fees paid to third parties?
• Does your accountant require specific export formats (CSV, structured PDF annexes)?
• Will multiple users issue invoices (sales, ops, field team)?

Non-negotiable technical requirements

1. TTN / TEIF readiness or a documented roadmap with dates (not marketing slides)
2. Correct Tunisian VAT treatment on lines (rates, exemptions you actually use)
3. Unique invoice numbering and audit trail—no silent edits after issuance
4. Role-based access: who can draft, approve, and submit clearance
5. Export path for accountant: trial balance hooks, payment lists, TEJ-relevant fields
6. Backup and data portability if you switch vendors later

Ask vendors for a live demo using your invoice types—not a generic sample. A consulting SARL with retainer invoices behaves differently from a retail PME with daily cash sales.

Usability questions your team will ask

Compliance features nobody uses still fail audits because staff revert to WhatsApp PDFs. Evaluate French/Arabic UI clarity, mobile access for field staff, duplicate customer detection, and how fast a new hire can issue a correct invoice with supervision.

Pilot with one real client and one real supplier cycle before cutover. Parallel-run old and new process for at least one declaration period. If the pilot needs more than two weeks of consultant customization, factor that cost into TCO.

Compare total cost, not subscription alone

• Digital certificate fees (TUNTRUST or accredited provider)
• Accountant time to fix exports during year one
• Training and change management for sales/ops
• Integration with bank feeds or existing ERP, if any
• Penalty risk from delayed TTN enrollment—not theoretical for 2026 scope expansions

Red flags in vendor answers

• We support Tunisia in the roadmap with no production TTN customers
• Just email PDFs—TTN is optional
• One global tax engine covers all Maghreb countries
• No answer on who holds liability when clearance fails
• Cannot show audit log of invoice changes

Where Hesabi fits

Hesabi targets Tunisian PME operational finance: invoicing, accountant collaboration, and compliance-oriented exports rather than multinational ERP complexity. We are explicit about Tunisia-only coverage so you do not assume cross-border fiscal support we do not provide.

Pair software selection with our TTN El Fatoora guide and TEJ reporting overview, then review the shortlist with your expert-comptable before purchase.

Evaluation scorecard (copy to spreadsheet)

• TTN production readiness (weight 25%)
• Accountant export quality (25%)
• Daily user usability (20%)
• TCO including certificates and training (15%)
• Vendor support responsiveness in Tunisia time zone (15%)

Score each vendor 1–5 with finance, one sales user, and your accountant in the same room. Disagreement on usability scores usually predicts adoption failure—resolve before signing.

Reference calls matter: ask vendors for two Tunisian customers in a similar sector and invoice volume. Generic testimonials without clearance experience are worthless.

Contract review: confirm data export on exit, SLA for clearance-related incidents, and whether pricing changes when TTN transaction volume tiers increase.

Seasonal businesses should test peak-month volume in the pilot: clearance queues and support response times matter when you 10x invoice count in December or before school-year starts.

After go-live, schedule a 30-day and 90-day review with your accountant: clearance success rate, export exceptions, and user tickets. Software choice is not finished at signature—it is proven in the first declaration cycle.

Keep a living requirements doc: every time clearance fails or exports break, add a line so the next vendor review starts from evidence—not memory, slides, or promises.

Document the decision in writing: chosen vendor, go-live date, accountant sign-off, and rollback plan if clearance failure rate exceeds an agreed threshold in the first 90 days.