Splitting a group bill by line items

Six people, one bill, four people had pasta and water, two had steak and a bottle of wine. The waiter asks "one bill or separate?". Someone says "let's just split it" because it's late and nobody wants to do mental math at the table. The pasta-and-water four quietly subsidise the steak-and-wine two. Over the year this happens enough times that some friendships get a little frostier than they need to be.

The fix isn't "split it per item at the table" — that's slow and awkward. The fix is to capture the receipt and do the per-item split in five minutes after the fact, then bill people via Venmo / Revolut / PayPal / however your group settles. This guide is the practical workflow.

Why equal-split is unfair more often than people admit

The fairness of equal-split depends on how similarly everyone ordered. At a casual lunch where everyone gets a sandwich and a coffee, equal-split is roughly fair and the overhead saved is worth it. At a wine dinner with mixed appetites, equal-split is a 20–40% transfer from the moderate orderers to the heavy orderers.

The rule of thumb we'd offer: if the highest individual order is more than 1.5× the lowest, per-item splitting is materially fairer and worth doing. Below that, equal-split is fine. The 1.5× threshold is roughly "one person ordered an entrée + dessert, another ordered just an entrée" — a difference small enough that nobody really minds, but past which the maths matters.

The five-step workflow

Here's how to do it without becoming the friend who insists on calculating the bill:

• 1. Photograph the receipt at the table. Just snap it; don't process it then. Five seconds. The receipt is now in your photo roll.
• 2. Settle the table normally. Pay with one card, equal-split for now if you want, get out of the restaurant. Don't do maths in front of the wait staff.
• 3. After dinner, run the photo through Receipt Ripper. Each line item gets a quantity and a price extracted. Edit any field that came through wrong; check the total matches what you paid.
• 4. Assign items to people. Open the parsed receipt in a spreadsheet (CSV or XLSX export), add a column "Who", fill in each person's name against their items. Use a comma-separated list for shared items.
• 5. Sum per person, including their share of shared items and a proportional cut of tax + tip. Send the amounts in a group chat. Done.

Handling the three awkward cases

Shared items (the bottle of wine)

A bottle of wine that two people split equally costs each of them half. A starter that three people picked at equally costs each of them a third. In your spreadsheet, just list the names with commas (Alice, Bob) and divide that line's cost evenly across the listed people. If consumption wasn't equal (Alice had three glasses, Bob had one) and you want to be precise, split by an explicit ratio — but for friendly meals, equal-share of shared items is the convention that keeps the peace.

Tax and tip

Add each person's share of tax and tip proportionally to what they ordered. If Alice's items total 25% of the subtotal, she pays 25% of the tax and 25% of the tip. This is the convention restaurants use when they actually print itemised bills per diner, and it's the right answer most people intuit anyway. The "exclude tax from exports" toggle in Receipt Ripper isn't what you want here — keep tax in for splitting purposes.

Items the receipt got wrong

OCR sometimes joins two line items into one or misreads a price. Always glance at the parsed result against your memory of the meal: did you actually order something called "OYSTERSAUC E"? Probably a fused line. The review table is editable; fix it in place. The validator catches major arithmetic mismatches; minor ones are easier to verify by eye against the receipt photo.

When to skip the line-item split entirely

Some situations don't need this level of precision:

• Everyone ordered roughly the same thing. Equal-split is fine.
• The total per person is small enough that fairness doesn't matter. A €40 dinner where the variance is €5 either way — just split it.
• One person is paying the whole thing for a clear reason (birthday, work meal, the host treating). Then no split at all.
• The group always rotates who pays. If five friends meet every week and each person hosts a round, the long-run average works out; nobody needs to itemise.

Per-item splitting is for the case where the variance is meaningful and the group sees each other often enough that the fairness matters. For one-off groups, equal-split is the lower-friction default.

A worked example

Six people, total bill €240 (subtotal €200, tax €25, tip €15). Per-item breakdown after parsing the receipt:

• Alice: Caesar salad €15, water €2.50 → subtotal €17.50 (8.75% of subtotal)
• Bob: Burger €18, beer €6.50 → subtotal €24.50 (12.25%)
• Carla: Pasta €16, water €2.50 → subtotal €18.50 (9.25%)
• Dan: Steak €38, wine €30 (shared with Eve) → subtotal €53 (26.5%)
• Eve: Steak €38, wine €30 (shared with Dan) → subtotal €53 (26.5%)
• Frank: Pasta €16, beer €6.50 → subtotal €22.50 (11.25%)
• (Shared wine €30 split between Dan and Eve = €15 each.)

Equal-split would have charged everyone €40. The per-item method charges roughly: Alice €21, Bob €29.40, Carla €22.20, Dan €63.60, Eve €63.60, Frank €27. Total checks out at €240. Dan and Eve pay more, the other four pay less, everyone's share matches what they actually consumed. Nobody got the rough end.

The tooling

You don't need a dedicated bill-splitting app for this. Receipt Ripper extracts the line items; a spreadsheet (Excel, Numbers, Google Sheets) does the per-person sums with a SUMIF formula. The whole post-dinner process is five minutes of work for a six-person meal.

For groups that do this regularly (housemates, regular dinner clubs), keep a running tally — assigning each meal's shares to the same set of named people, settling weekly or monthly via one transfer per person rather than per meal. The arithmetic is trivial; the social benefit of "we don't do this at the table" is the actual win.

For more on getting the line items extracted cleanly in the first place, see how to photograph a receipt so OCR actually reads it.