GRA E-VAT
How to test a POS before GRA E-VAT go-live
A practical acceptance-test plan for a Ghana POS and E-VAT integration project.
Reviewed by the EazSell editorial team · Updated 21 September 2026
Direct answer
Test one complete working day, not one receipt. Include tax classes, discounts, returns, rejected invoices, device changes, a broken connection and daily reconciliation. Record the fiscal response for every case.
Reference: GRA: E-VAT
Use real shop scenarios
Choose products that cover the tax treatments your business actually sells. Include a price override if staff can make one, a split payment if the POS supports it and a return against an earlier sale. A clean single-item cash sale misses most operational errors.
Check the evidence
For each test, keep the POS transaction reference, fiscal document reference, response status and printed or electronic receipt. The cashier should know whether to retry, correct the data or ask a supervisor. An unexplained error code is not a usable workflow.
Get sign-off before launch
The merchant, local implementer and tax adviser should agree which cases passed. If a case cannot be completed under the approved route, write down the interim process rather than hiding it in training notes.
What to check before you decide
- Test all applicable tax classes.
- Test errors, corrections and refunds.
- Sign off receipt evidence and daily totals.
Questions people ask
Is a successful API call enough?
No. It does not prove the cashier saw the correct status or the receipt and reports reconciled.
Sources and verification
Check current GRA instructions and your own taxpayer position before treating this guide as an implementation decision.
Keep reading
Want to test this against your own shop?
Tell us about your checkout, devices and current invoicing process. We can show the relevant POS workflow and identify what still needs local verification.
Request a demo