Shared expense splitter

Start with the purchases, not the whole bank balance

A statement mixes groceries with wages, personal spending and payments to other accounts. None of those rows belongs in a shared bill just because it appears in the file. Load a CSV, confirm its columns and signs, then select the purchases you agreed to share. Give each one a payer; the account holder isn't always the person who covered it.

In the fictional example, Alex pays 90.00 for groceries and Sam pays 30.00 for utilities. Equal halves give each person a 60.00 share of the 120.00 total. Alex has paid 30.00 more than their share, so Sam pays Alex 30.00. The result shows the purchases and shares as well as the final suggestion, so you can check the explanation together.

You can use equal shares, weights such as 60 and 40, or exact amounts for each purchase. A zero weight leaves someone out. Exact amounts must add up to the full purchase; a blank isn't treated as zero.

Someone gets the extra cent, and you can see who

Splitting 10.00 three ways can't produce three identical cent amounts. With Alex, Sam and Jo in that displayed order, equal shares are 3.34, 3.33 and 3.33. Move Sam ahead of Alex and Sam gets the extra cent instead. The total is still 10.00.

The same rule handles weights: calculate each exact proportion, round down to the currency unit, then give the leftover units to the largest fractional remainders. Participant order breaks ties. This happens separately for each purchase, so the first person may get several extra cents across several tied purchases. It's a visible allocation rule, not a claim about what's fair.

A refund and a repayment do different jobs

A refund reduces a purchase cost. Select who received the money and enter the exact amount returned to each participant, adding up to the refund total. That avoids quietly applying today's split to an older purchase that used a different agreement. If you can't establish those shares, leave the refund out and resolve it together.

An existing settlement is money one participant has already sent another. It changes what's left to settle but doesn't create another shared expense. Choose its sender and recipient explicitly, and include only one side if both people's bank records show the transfer. A payment to a credit-card provider usually stays excluded because the purchases are already on the card rows.

Arithmetic you can review, not a decision for your household

For each participant, the tool subtracts their allocated share from what they paid, then adjusts for settlements already sent or received. Positive means they receive money; negative means they pay. The suggested list repeatedly matches the largest debtor to the largest creditor, breaking ties in participant order. It doesn't promise the globally smallest number of transfers.

This is not a fairness judgment or a payment service. No money moves, and unequal incomes don't establish the right split. Nor does a bank CSV prove who paid cash, whether a purchase is genuine, or whether the group has supplied every expense. Check the imported rows and the split separately: readable data doesn't mean everyone has agreed to share it.

The output is not tax, legal, lending or accounting advice. It makes no fraud or document-authenticity judgment and doesn't guarantee another app will accept the CSV.

Keep currencies separate and check the signs

The tool accepts one UTF-8 CSV of up to 5 MB and 10,000 data rows, with 2 to 20 participants. Use a combined CSV for multiple payers, then set the payer per row. Account aliases and currency codes can come from columns or from the file settings. Accounts stay separate unless you explicitly combine them for this shared-expense group. Different currencies never net against each other, and there is no exchange-rate conversion.

Choose 0, 2 or 3 decimal places to match your currencies. Every currency in the file must use that precision. Amounts with excess precision are rejected, not rounded on import. The chosen date column can mean posted date or transaction date; ambiguous formats need your choice, and the displayed range covers selected rows rather than proving a complete statement period.

Invalid rows, repeated headers and subtotal-like records block calculation, even if you would have excluded them. The issue list points back to original source lines. Make corrections in a working copy and keep the original. Changing source settings resets row decisions and separates accounts again. Changing participant order recalculates tied shares visibly.

If a card purchase points the wrong way, read the card-sign explanation before flipping it. The debit/credit converter can help with separate columns. For overlapping exports, use the duplicate finder before counting the same purchase twice.

Share the settlement, not your entire statement

Your file and the values you enter are processed in this browser tab. They are not uploaded or sent to analytics. We do not save them between visits. Downloads you choose to save remain on your device.

The review CSV contains all source rows, including excluded purchases and original cells, so don't forward it without reviewing what it reveals. The minimal settlement note contains only account aliases, currencies and suggested payments. Copying it is an explicit click to your device clipboard, not a hosted result link. Your device may have its own clipboard history or syncing settings.

Clear removes the active input and choices. Back navigation can restore uncleared input, so leaving the page is not a clearing action. Clearing the tool doesn't delete downloads or erase your clipboard. Exported files are new copies, and spreadsheet formula protection may prefix text with an apostrophe; parsed negative amounts remain numeric.

Only have PDF statements?

Already have a bank CSV? This tool is free. Only have PDF statements? First check your bank's native export or any included extraction option. AnyStatement can convert PDFs into reviewable transaction data. Check those rows before deciding which purchases to split.