What GRA E-VAT actually requires at the counter

Ghana's move to electronic VAT invoicing changes what a receipt is. It stops being a slip of paper confirming a sale and becomes a record the tax system expects to see. That sounds like an accounting problem. It is really a point of sale problem, because the information has to be right at the moment of the sale or it is not right at all.

What the receipt has to carry

A compliant receipt itemises the tax lines rather than folding them into one total. On our own product's documentation, current as of July 2026, those lines are VAT at 15 percent, NHIL at 2.5 percent and GETFund at 2.5 percent, each applied to the subtotal of the sale.

Beyond the tax lines the receipt carries a clearance reference and the business's VAT or TIN number, so an individual sale can be traced back to the electronic VAT system. That traceability is the point of the whole exercise. A receipt that shows the right total but cannot be tied back to a specific business and a specific transaction does not do the job.

Who this applies to

VAT-registered businesses are the ones affected. The rollout has been staged, and requirements can differ by business type and size, which means the honest answer to "does this apply to me yet" is that you should confirm your own position directly with the Ghana Revenue Authority rather than take a vendor's word for it, ours included.

Be wary of anyone who tells you their software makes you compliant. Software can produce a receipt in the required shape and can talk to the system that issues clearance references. Compliance is a status your business holds with the GRA, and no supplier can grant it to you. Our own point of sale product is built for these requirements and is not certified or endorsed by the GRA, and we say so on the product page.

Why the counter is the right place

The tempting shortcut is to keep selling the way you always have and reconstruct compliant records later from a spreadsheet. It rarely survives contact with a busy shop. Reconstruction means somebody remembers which sale was which, at the end of a long day, from a stack of handwritten slips.

Doing it at the counter inverts that. The tax lines are calculated on the sale that is actually happening, against the actual line items, and the receipt prints with the reference already on it. The paperwork becomes a by-product of selling rather than a separate job with its own deadline and its own opportunities to get it wrong.

What usually goes wrong

Three failures come up more than the rest.

Prices that already include tax, recorded as if they do not. If your shelf price is what the customer pays, your system needs to work backwards from that figure to a subtotal and the tax lines. Getting the direction wrong changes every number on the receipt.

Mixed baskets. Not everything a shop sells carries the same treatment. A basket combining items with different treatments has to be split correctly, and a system that applies one rate to the whole sale will be wrong on most transactions.

The connection dropping mid-sale. If issuing a receipt requires a live call to a remote service, then every outage becomes a decision between not selling and selling without a compliant receipt. Neither is acceptable, which is why this problem belongs with the offline design of the till rather than with the tax rules. We wrote about that separately in designing software for networks that drop.

What to do this week

Confirm your obligations with the GRA directly, in writing if you can. Check whether your current till can itemise the three tax lines and carry a clearance reference, and ask your supplier plainly rather than assuming. Then look at what happens to your receipts when the internet goes down for an hour, because that is the case that decides whether a system works in a Ghanaian shop or only in a demonstration.