Receipt scanning for households: how it actually works

If you live with other people, you already know the shape of this problem. Someone does the weekly shop. They get home with twelve bags and a 90cm-long receipt. They pay on their card. Then nothing happens for three days, because nobody wants to be the person who sits down at the kitchen table and types out forty line items into a shared spreadsheet.

So the receipt sits on the bench. It curls. Someone moves it. Then it's gone. The household has spent $187 on groceries and the only person who knows that is the person who paid.

The receipt scanner in Flatmate Flow exists to delete that whole sequence. You take one photo. The app does the rest.

What it actually does#

You open the app, tap the camera, point it at the receipt, and that's the entire interaction. About three seconds later you have:

• An itemised list of everything on the receipt, with quantities and prices
• Any item that was already on your household shopping list ticked off
• The total added to the current month's household budget under "Groceries"
• A line in your spend history showing who paid and what was bought

Nothing to confirm. Nothing to categorise. No "tap to add to budget" prompt. If the photo's good enough to read, the scanner just does it.

That's the bit other household apps don't do. Most of them stop at "scan and store the image." Useful for tax, useless for the way roommates actually think about shared money.

The flow, step by step#

Here's what happens between the shutter click and the budget update.

1. The photo. It goes through a tiny image-prep step in the app first: auto-rotate, light de-skew if you held the camera at an angle, contrast boost on the faded thermal-paper receipts that supermarkets seem determined to keep printing. You don't see any of this. It takes about 200ms.

2. The extraction. The processed image is sent to Anthropic's Claude with a prompt that knows what a supermarket receipt looks like. Claude returns a structured list: vendor, date, every line with quantity, item name, price, plus the total and any discounts or loyalty deductions. We use Claude specifically because messy real-world receipts (smudged ink, two items on one line, item codes mixed with names, multi-buy promos) trip up traditional OCR. A language model that's read a few million receipts handles the edge cases the way a human would.

3. The list match. The extracted items get compared against your current household shopping list. Anything that matches gets ticked off (so the other flatmates can see the bread arrived). Anything new just appears in the spend list. Matching is fuzzy, so "Coles full cream milk 2L" on the receipt matches "milk" on the list.

4. The budget update. The total drops into the current month's "Groceries" category in your household budget. Your share is calculated based on whatever split rules you've already set up: equal, by income, custom. The other flatmates see a notification: Sam added a $187 grocery shop. Your share: $46.75.

5. The audit trail. The original photo is kept (you can tap any spend line to see the actual receipt), so when somebody asks "what did we spend on groceries this month?" there's a real answer, not a vibe.

The whole thing, from camera to budget-updated, is one continuous action. You don't have to be a "person who's good at finances" to use it. You have to be a person who can take a photo.

What it handles#

The boring answer: most receipts from most supermarkets.

The more useful answer:

• Long receipts. The 90cm Coles or Tesco specials with 50 line items, multi-buy bundles, and the "you saved $14.30" footer. Handled.
• Faded thermal paper. The ones that look like they've already started disappearing. The contrast boost in step 1 was built for these.
• Folded or wrinkled receipts. Fine, as long as the text isn't obscured by the fold.
• Receipts in different currencies. Works on AUD, USD, GBP, EUR, NZD out of the box. Currency is detected from the receipt, not your phone settings, so a receipt from a holiday gets logged in the local currency and converted in the budget view.
• Café and restaurant receipts. They work, though "items" are less meaningful (two flat whites and a banana bread). The total still posts to your budget.
• Handwritten receipts from a corner shop. Honestly hit-and-miss. If the handwriting is clear, you'll get a total and a few items. If it's a scrawl, the scanner will return the total and one line that says "items unclear" so you can tap in what you actually bought.

What it doesn't do (yet)#

We're being upfront about the gaps because this is the bit nobody else writes about.

• It doesn't read price tags off products in a shop. It only reads printed receipts.
• It doesn't know about brand loyalty. If you bought a $9 specialty olive oil, it goes into "Groceries" with everything else. We don't auto-categorise by item type beyond the receipt's vendor.
• It doesn't split a receipt between two budgets. If half your shop was a flatmate's birthday cake and you want to bill it to them personally rather than the household, you do that split manually after the scan. (It's two taps. We just don't guess.)
• It doesn't handle multi-page receipts as one scan. If your receipt is two physical pieces of paper, that's two scans.

These are all on the roadmap. The first two are landing in the next month. The split-on-scan one is a UX problem we're still designing around, because the wrong default would create more friction than it solves.

Why we built this first#

When we mapped out what makes shared-household money actually painful, the same answer kept coming up: it's not the splitting. It's the capturing. The split logic is simple maths. The reason households drift into "we'll sort it out later" purgatory is that someone has to physically log what was spent, and nobody does, and the longer you wait the less anyone can remember what the $112 charge at IGA was even for.

Take the capture step from "five minutes of typing" to "one photo," and the whole pattern changes. Households actually log their spend in real time. The budget is alive instead of a museum piece. Disputes about who owes what stop happening, because there's a photo of every shop and a list of every item and nobody can credibly argue.

That's why the scanner was the first thing we built after the core split engine. Everything else (chore rosters, polls, the notice board) sits on top of households that have a real grip on their money. The scanner is what gives them that grip.

Try it#

You don't need a flatmate to try the scanner. If you live with anyone (partner, family, kids who eat half the fridge), the same logic applies. It's free. Sign up and snap a receipt within five minutes.

Sign up free →

You'll see what we mean.