b2KIT

Payment Splitter

Split expenses among multiple people with equal or custom shares, track who owes whom, and settle debts with minimum transactions.

Tested tool guide Tested browser tools Checked August 16, 2026

What Payment Splitter does, with a checked example

This tool converts a list of shared expenses into two deliverables: each person's share of the total, and a settlement plan that clears every debt with the fewest possible transfers. You enter each expense, who paid it, and who shares it, under an equal split or with custom weights. The tool nets what everyone paid against what everyone owes and pairs creditors with debtors. The surprise is that it does not repay expenses one by one: a $60 dinner paid by Anna can end with Ben paying her $5, because his shares of other expenses already covered most of his debt.

Worked example

A concrete input and expected output from the current implementation.

Input

Dinner: $60, paid by Anna, split equally among Anna, Ben, Clara
Taxi: $30, paid by Ben, split equally between Ben and Clara

Expected output

Shares: Anna $20, Ben $35, Clara $35 (total $70)
Balances: Anna +$40, Ben -$5, Clara -$35
Settlement (2 transfers): Clara pays Anna $35; Ben pays Anna $5

The dinner costs $20 per person and the taxi $15 for each of Ben and Clara, so shares total $70. Netting payments against shares leaves Anna owed $40, Ben owing $5, and Clara owing $35, which balances to zero; with two debtors, two transfers is the minimum.

How the result is produced

1

Net balances per person

Every expense records a payer and a participant list. An equal split divides the cost by the number of participants; a custom split applies the weights or amounts you assign. The tool sums, per person, everything paid and everything owed across all expenses. The difference is that person's balance: positive means they are owed money, negative means they owe.

2

Minimal settlement plan

Instead of reimbursing each payer separately, the tool matches total creditors against total debtors and arranges transfers so each person settles with a single payment where possible. The plan is built from net balances only, which is why the person who paid the restaurant bill may appear only as a recipient, or even as a payer. The result is a small number of transfers, not one per expense.

Good uses

  • Group trip: after a weekend of one person paying for fuel, another for groceries, and another for the rental, enter all receipts once and settle in a handful of transfers instead of chasing each bill separately.
  • Shared housing: monthly rent, utilities, and groceries where roommates use things unevenly, entered with custom shares so the unequal usage is reflected in each person's balance.
  • One person covers a whole table's check: enter the bill once with that person as payer and everyone else as participants, then reimburse from the computed shares instead of doing mental math on the menu.

Limits and checks

  • The tool divides exactly as you enter: an expense listed with the wrong participants, or custom shares that do not sum to the bill total, silently shifts money between people. Verify each participant list against the actual receipt before settling.
  • Equal splits rarely land on whole cents with three or more people (a $100 bill split three ways is $33.33 each with a penny unassigned). Custom weights can leave the same residual, so balances may show a one-cent imbalance that is a rounding artifact, not an entry error.
  • The plan settles what was entered, not reality: cash already handed over, tips added later, or a coupon discount are invisible unless entered. And the minimum-transfer plan is not the only fair one, so if you prefer paying the original payer directly, treat each expense as its own group.

Common questions

Two people at our table had much more expensive dishes than the rest. Can I split the bill unevenly?

Yes. Pick a custom split and give each person their own share or percentage instead of dividing equally. On an itemized restaurant bill, an alternative is entering each dish as its own expense with only the people who ordered it; both methods give the same balances as long as the shares add up to the total.

Why does the plan tell me to pay someone I never shared a purchase with?

Because the settlement is built from each person's net balance across all expenses, not from individual bills. If one friend covered the dinners and another the transport, the minimal set of transfers can route money in a different order, so the pairing never mirrors the receipts. The amounts are correct; only the pairing differs.

References and verification

The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.

Related Tools