What actually happens when you WhatsApp a receipt

Step one: you send a photo

It starts the way most WhatsApp messages do. You photograph a till slip, or you forward an invoice that landed in your inbox, and you send it — to a WhatsApp number, or by email, whichever suits the document in front of you. That's the entire action required of you at this stage. There's no form to fill in first and nothing to set up before you can send the first one. (If you want tips on getting a clean photo, that's a separate topic — this one picks up from the moment you hit send.)

Both routes lead to the same place. A photo sent on WhatsApp and an invoice forwarded by email are treated as two doors into the same process — the reading, the check, the filing and the dashboard that follow are identical either way. Which one you use on a given day just comes down to where the document already lives: a paper slip in your hand becomes a photo, a PDF invoice in your inbox gets forwarded as-is.

Step two: the details are read

Once it arrives, the document is read automatically. That means pulling out the specific fields that matter for your books: the vendor's name, the date, the total, the VAT amount, the line items where they're present, the receipt or invoice number, and the payment method. This happens in the background, and it happens quickly — usually within seconds of the message arriving. But speed isn't really the point of this step. Accuracy is, and that's exactly why the next step exists.

Step three: you check it, before anything is committed

This is the part worth slowing down for, because it's the part that makes the rest of this trustworthy. Before anything is filed, added to a dashboard, or posted anywhere, you're shown what was read off your receipt — the vendor, the date, the amount, the VAT — and asked to confirm it's correct.

If it's right, you approve it and the process continues. If something's off — a total misread, a vendor name that's not quite right — you can correct it before it goes any further. Nothing downstream happens on the strength of a guess. Your confirmation is the gate, and it stays that way for every receipt, every time, not just the first few while the system is "learning."

Step four: the original is filed — into your own Drive

Once you've confirmed the details, the original file itself — the photo or the forwarded invoice — is filed into your own Google Drive. It goes into a folder called SlipStack Receipts, organised into subfolders by year and then by month, so a receipt from March sits inside a "March" folder inside a "2026" folder, and so on.

The word "your" is doing real work in that sentence. It's your Drive, under your Google account, not a vault someone else controls. The files are yours to open, move, download or delete as you see fit — this step simply saves you the ten minutes a week you'd otherwise spend renaming photos and dragging them into folders yourself.

Step five: a running cost dashboard updates

At the same time, a cost dashboard updates — a Google Sheet, with one sheet per year and a tab for each month. The confirmed vendor, date, amount and VAT land in a row on the relevant tab, so instead of a phone full of photos you slowly lose track of, you have a running, searchable record of what's been spent, when, and with whom. It's a spreadsheet you can open, scroll, sort and filter like any other — nothing hidden behind an app you'd need to learn.

Step six: if you use Xero or Sage, it posts there too

If your business already runs on Xero or Sage, the confirmed transaction can post through to your accounting system as well, with the receipt image attached so it's sitting right there when you or your bookkeeper come to reconcile it. This is entirely optional and depends on your setup being connected — it doesn't happen automatically the moment you sign up for anything.

And if you don't use either of those — plenty of small businesses don't — that's fine too. Steps four and five, the filing and the dashboard, work perfectly well on their own. You don't need accounting software in the background for any of this to be useful; it simply does more if you have one connected.

What happens when the VAT looks uncertain

Not every receipt is a clean read. A faded thermal slip, a torn corner over the VAT line, a supplier whose VAT number doesn't quite parse — these things happen, and it matters what happens next. Rather than posting a guessed figure and hoping it's close enough, anything where the VAT looks uncertain is held back for a human to look at and approve, instead of being assumed. The same caution that governs the confirmation step in general applies with extra weight here, because getting VAT wrong is the kind of small error that's genuinely tedious to unpick later.

Why the order of these steps matters

Laid out end to end, the sequence is: send, read, check, file, update, and — where relevant — post. It's worth noticing that "check" sits before "file" and "post", not after. A lot of automation tools default to the opposite order — act first, and let you undo or correct afterwards. Here, the correction happens before anything is written anywhere, which means there's never a mistaken entry sitting in your Drive or your accounting system that you then have to notice and unpick. The record you end up with is the one you already approved.

What this doesn't involve

It's worth being just as clear about what doesn't happen. Extraction from the photo takes seconds — but that's not a promise about how quickly anything lands in Xero or Sage, and there's no fixed turnaround time attached to that step; some paths, like a batch of forwarded emails, are deliberately processed together rather than instantly. There's no obligation created by sending a receipt through, no trial clock silently starting, and no commitment implied anywhere in this description. It's simply the mechanism, laid out plainly, so you can weigh it up for yourself.

This is a description of how the process works, not tax or accounting advice. Your own VAT and record-keeping obligations still rest with you — confirm anything uncertain with SARS or a registered tax practitioner.