Field teams in Tunisia—installers, technicians, sales reps visiting clients—often create invoices at the job site. If those invoices live as photos in WhatsApp or offline PDFs, finance retypes everything at month end. That delay breaks VAT accuracy, slows TTN clearance, and frustrates customers waiting for official documents.
Mobile invoicing done well means capture at the point of service, approval rules that match your org, and automatic handoff to the back-office system that handles TTN El Fatoora clearance. This guide describes a practical workflow for Tunisian PMEs without pretending phones replace accountant oversight.
What field teams actually need on mobile
- Customer lookup or quick create with tax ID validation where possible
- Product/service catalog with correct VAT rates preconfigured
- Draft invoice while offline, sync when connectivity returns
- Photo attachments for delivery proof or meter readings
- Clear status: draft vs submitted for finance approval vs cleared
Sales reps should not have permission to finalize legally issued e-invoices unless your process explicitly allows it and TTN credentials are controlled. Most PMEs use mobile for draft + site data; finance or a supervisor submits clearance.
Why WhatsApp PDFs fail at scale
Informal PDFs skip numbering discipline, mix corrected and uncorrected versions, and leave no audit trail. When DGI or a corporate client asks for the cleared e-invoice reference, finance searches chat history. Under TTN rules, the cleared document is the issued one—not an uncertified attachment.
Recommended workflow
- Site capture
Technician completes job checklist, selects services, adds photos, saves draft synced to central system.
- Finance review
Back office validates VAT lines, customer master data, and credit limits before clearance submission.
- TTN clearance
Authorized user submits TEIF to TTN; system stores reference and QR metadata.
- Customer delivery
Email or print copy of cleared invoice; field app shows status so reps do not resend drafts.
- Cash collection linkage
Mark paid on site or via bank import; reduces orphan invoices at month close.
Connectivity and device policy
Rural gouvernorats and industrial zones still have dead zones. Offline-first capture with queued sync beats forcing real-time clearance on a phone. Company-owned devices with screen lock and remote wipe beat personal phones storing client tax IDs.
Keep the mobile UI minimal: five taps to a draft invoice beats a desktop form shrunk to unusable size. Complex credit notes and cancellations stay on finance desktops.
Metrics to track after rollout
- Hours from job complete to cleared invoice
- Percentage of field drafts returned for master data fixes
- Duplicate customer records created on mobile
- Invoices still retyped manually in finance after go-live
If retyping persists after 60 days, the problem is usually permissions or catalog setup—not user training alone.
Hesabi and mobile-first PMEs
Hesabi focuses on Tunisian SME finance workflows including invoicing built for local VAT and TTN-oriented clearance. Mobile experience evolves with product releases—verify current mobile capabilities on hesabi.tn before planning a field rollout.
Security review: field apps should not cache TTN signing credentials on shared tablets. Use role separation so technicians see customers and job lines only—not company-wide financial reports.
Onboarding checklist for new reps: practice customer search, create one draft invoice, attach a photo, and hand off to finance in a test environment before first client visit.
Sector-specific notes
Maintenance and installation companies often invoice on site with variable parts lists—mobile catalog must support ad hoc lines with supervisor approval. Wholesale reps need price list tiers and credit limits enforced before draft submission.
B2B clients increasingly ask for cleared e-invoice references in their own AP systems. Field drafts that never reach clearance become collection delays when the buyer's finance team rejects uncertified documents.
Arabic and French labels on line items reduce disputes with end customers; align wording with what TTN clearance stores as the legal description.
Run a monthly retrospective with field and finance: count drafts rejected, top rejection reasons, and one process tweak per month. Compounding small fixes beats annual ERP replacement.
When mobile rollout succeeds, finance stops being the bottleneck for every site invoice—and TTN clearance happens while the job is still fresh in the customer's mind.
Plan training refreshers after summer hiring peaks and before busy service seasons when temporary staff join field crews without knowing your invoice approval rules.
Escalation path: if a rep cannot sync after 24 hours offline, they call finance with draft ID—not a screenshot—to avoid duplicate submissions and numbering conflicts.
Treat mobile invoicing as a handoff between field operations and compliance—not a shortcut around TTN rules your accountant remains accountable for under Tunisian law.
Battery and data plan policy: reps on day-long routes should know whether mobile uploads wait for Wi-Fi at the depot or use cellular data budgets you approve.
Can reps issue final TTN invoices on phone?
Technically possible with proper certificates and roles; many PMEs restrict clearance to finance for control.
Offline mode required?
Strongly recommended for field teams outside always-on connectivity.
What about cash payments on site?
Record payment method at capture; reconcile with caisse or bank deposit rules your accountant defines.
Integrate with route planning apps?
Usually via customer ID in both systems—deep integration is custom project scope.
Hesabi outside Tunisia?
No. Tunisia-only today.
