ZIMRA fiscalisation lives or dies on fiscal day discipline. Virtual Fiscal Devices (VFDs) still need a clean open, a healthy queue, and a deliberate close — even when there is no plastic box on the counter. Teams that scramble at 08:00 usually skipped the same three checks the night before: certificate freshness, device status, and pending receipts. Mutero surfaces those signals in one place so operators can open the day with confidence.
The morning preflight
Before you open a fiscal day, confirm the device can reach FDMS, the signing certificate is not near expiry, and yesterday’s close completed without orphaned receipts. If any of those fail, fix them before the first invoice — not after a customer is waiting. When FDMS is slow, keep issuing through the offline queue. Fiscal receipt numbers and QR codes write back when connectivity returns. Closing early just to “reset” often creates more reconciliation work than waiting for the queue to drain.
Closing without drama
Close only when the queue is empty (or every remaining item is intentionally held). Export or note any exceptions, then close the day so ZIMRA sees a coherent period. Consultants managing multiple TINs should close per business — never mix fiscal days across clients.
Key takeaways
Run the same five preflight checks before every open-day. Never close a fiscal day with a stuck queue — clear retries first. Treat FDMS slowness as a queue problem, not a reason to skip fiscalisation.
