QuickTill guide · 9 min read
Understand the operational work around POS fiscalisation.
Fiscalisation is more than printing a receipt. The business must configure accurate taxpayer, device, buyer, item and tax information, manage fiscal days and preserve responses when a submission is interrupted. Exact obligations should always be confirmed with ZIMRA and the business’s authorised fiscal provider.
Information that must be prepared
A reliable workflow starts with correct business and item data. Missing tax identifiers or inconsistent tax configuration should be found before the transaction reaches submission.
- Business taxpayer and receipt details
- Fiscal device and branch configuration
- Buyer identity where required
- Item tax codes, percentages and totals
Keep the fiscal day visible
Staff should be able to see whether the fiscal day is open, inspect counters and close the day through a controlled process. Managers need clear diagnostics rather than raw server pages.
- Open-day and close-day actions
- Status and counter visibility
- Receipt verification details
- User-friendly error and response history
Recover safely after interruptions
A network failure must not silently discard work or encourage duplicate submissions. Pending transactions need stable identifiers, retry rules and an audit trail.
- Visible pending queue
- Idempotent retry behaviour
- Original request and response history
- Reconciliation before the next close
Confirm fiscal, tax, hardware and connectivity requirements against the exact business and deployment. This guide is operational information, not tax or legal advice.