An electronic receipt is not a smaller invoice
Most writing about tax compliance is about e-invoicing and treats the receipt as a footnote. But selling to a consumer falls under a different system, with its own deadlines, requirements and operational behaviour — and the difference shows up at the till, during the busiest minutes of your day. This page explains what differs. The integration itself is still in development at Hesbba.
The difference that actually matters
An invoice and a receipt differ in who is on the other side of the transaction, and everything else follows from that.
Who is on the other side
An invoice is issued to a registered business with a tax number that gets validated. A receipt is issued to a consumer who has none, so validation shifts from the customer's details to the seller's and the item's.
The moment
An invoice is reviewed before it goes out. A receipt prints while the customer is standing in front of you — there is no later review and no quiet correction.
The volume
A business issuing dozens of invoices a month may issue thousands of receipts. What is tolerable manually for the first is impossible for the second.
Going offline
A till does not stop when the internet does. The receipt has to print and the sale has to complete, then be filed afterwards — that is an operational requirement, not a technical one.
What we are building for point of sale
Everything below is in development and has not shipped. It is written in the future tense because that is its actual status.
Filing never blocks the sale
The receipt will print and the sale will complete immediately, with filing happening in the background. A network drop delays the submission; it does not stop the till.
A queue you can see
Whatever has not been filed yet will show as an explicit list with a count and a reason, not a silent counter your accountant discovers at month end.
Returns handled as receipts
Returns are a daily event in retail. Each will create its own document, get filed, and post a reversing entry — not edit the original receipt.
Per branch, separately
Each branch has its own devices and sequence, and filing status will be visible per branch rather than as one aggregate number that tells you nothing about where the problem is.
What you can prepare today
These are steps on your own data and hardware, not on software, and they help whichever system you end up using.
Code your items
A receipt carries the item code just as an invoice does. In retail the catalogue is far larger, so this is by far the longest step — start with the best sellers.
Check your till hardware
Confirm every device prints legibly, reads barcodes and works offline. A till that struggles today will struggle more with an extra filing step.
Settle your document numbering
Every branch and device needs a sequence that cannot collide. Duplicate numbering across two branches is a small annoyance today and a recurring rejection later.
Train whoever works the till
The person who sees a rejection first is the cashier, not the accountant. They need to know what to do — and to know the sale does not stop.
Common questions
Do I need electronic receipts if I already issue invoices?
If you sell to consumers, yes — they are two separate systems and one does not substitute for the other. Businesses selling to both companies and individuals need both tracks, which is more common than it sounds: any retail shop occasionally invoices a company.
What happens if the internet drops at peak hour?
The sale has to continue. The receipt prints and goes to the customer, and it sits in a filing queue until the network returns. Any system that makes the sale itself depend on a live connection to a third party is unfit for retail, however precise its compliance.
When will this be available in Hesbba?
We are not announcing a date, for the same reason given on the e-invoicing page: it depends on a third party and on administrative approvals, and a date we announce and then miss is worse than none. The point of sale itself works today, including offline.
Does the electronic receipt differ between countries?
Yes — in format, in deadlines, and in whether it is even a separate system. But the operational shape is the same everywhere: fast sales, high volume, unreliable networks, and a document that must arrive. The groundwork is built around that shared shape.
Related
- E-invoicingHesbba is building e-invoicing into the ledger rather than on top of it: one document posts and files in the same action. The feature is in development — here is what we are building and what it requires.
- Inventory & purchasingWarehouse software for multiple locations, receipt, issue and transfer notes, barcode stock counts, and inventory cost posted to the ledger on every movement.
- Point of salePOS software that completes and prints sales while the internet is down, then syncs automatically — barcode, thermal printer and cash drawer, connected to inventory and accounting.
The till works today, offline included
Hesbba's point of sale completes and prints the sale without a connection, then syncs, with stock and the ledger moving with it. Get your branches ready now so that filing, when it arrives, is a settings step.