Fiscal POS guide
Fiscal POS Software: What Merchants and Partners Should Verify
A plain-language guide to fiscal POS workflows, official requirements, integration and deployment evidence.
The short answer
Fiscal POS software helps a merchant prepare required invoice data, communicate through the approved local route and retain the resulting status or receipt evidence. Product capability alone does not prove tax-authority approval: verify the applicable rules, integration and authorization for each market.
Separate product capability from approval
A POS may support invoice fields, QR data, signing or API communication, while local rules still require approved equipment, a certified integrator or a taxpayer onboarding process. Ask for official evidence that matches the exact country and deployment.
- Identify the tax authority and current rule.
- Confirm the merchant category and invoice type.
- Verify the integration or device approval path.
Make status understandable
Cashiers, managers and support teams need different levels of detail, but all should know whether an invoice is ready, queued, submitted, accepted or needs attention. A printed receipt should not be presented as accepted when confirmation is still pending.
- Show validation before submission.
- Retain authority references and responses.
- Control refunds, credit notes and voids.
Use official sources
Requirements change. Start with the relevant authority, then confirm implementation details with a qualified local adviser or approved integration partner. EazSell country pages link to sources such as KRA in Kenya, ZIMRA in Zimbabwe and MRA in Malawi.
- Record the source and review date.
- Retest when rules or interfaces change.
- Avoid making certification claims based only on a demo.