How to Split Group Travel Expenses: Unequal Shares, Refunds and Net Settlement

A shared travel ledger is not the trip total divided blindly by the number of travellers. A room may be split by bed use, only two people may join a dinner, and A may front a shuttle that only C uses. This guide uses one invented CNY example to keep “who paid” separate from “who should bear the cost,” then turns received refunds into checkable net balances.

If the trip has not begun and you need to decide whether it is affordable, start with the budget-travel guide. To test whether a remote room will add local transport costs, use the hotel-location tutorial. This page is for reconciling expenses that have happened. It is not a price guide, currency converter or decision about anyone's legal liability.

1. Agree the shares before paying

Write down the rules for this trip and for the relevant purchases. No one needs another traveller's bank details to do this.

• Choose the participants for every line. A person who did not eat the meal, take the ride or use the room does not automatically share it merely because they are in the trip group.
• The payer is not necessarily the person assigned the cost. Put the person whose cash or account paid in the payer column. Record each person’s agreed cost share in the shares columns. The same person can appear in both places.
• Unequal splits are valid when the group agrees. Use exact amounts, percentages or units, but each line's shares must add up to that line's amount. If percentage rounding leaves one or two cents, agree who takes the remainder instead of hiding it at settlement.
• Set boundaries for partial participation. For someone joining late or leaving early, identify the first and last room night, shared vehicle or group purchase they join. “Two days on the trip” is too vague to determine every line.
• Remove personal shopping. Souvenirs, personal medicine and individual upgrades stay outside shared costs unless other people expressly agree to share them. If one traveller fronts the purchase, assign the share only to its actual user.

Agree a rule for allocating leftover fen

First establish the actual payment, currency, participants, non-negative integer share weights and the order for breaking ties. The following is one editorial method for recording CNY in whole fen, with 100 fen to one yuan. The participants in this particular expense must agree to it; it is not an official standard, a default rule of fairness or a finding of legal liability. If exact amounts have already been agreed, check their sum instead of forcing them into a ratio. Do not copy this precision into other currencies, currency conversion or payment rules.

Handle each expense separately in whole fen rather than combining different expenses into one trip total. Let the amount be T fen and the total share weight be W:

1. For each person, calculate T × their weight ÷ W. Keep the integer part as the base share, without rounding to nearest. Also keep the exact remainder T × their weight − base share × W. W is the same for everyone in that row, so compare these integer remainders directly rather than rounding displayed percentages first.
2. Find the unassigned amount: T − the sum of the base shares. Allocate one extra fen per person in descending remainder order, stopping when it is exhausted. Break equal remainders using the order agreed in advance, not by assigning the difference to the payer on the spot. Non-participants are outside this allocation order.
3. Check that the final shares are whole fen and total exactly T before displaying yuan. Keep the original weights, base shares, remainders and recipients of extra fen. If W is zero or the payment or participants need checking, stop; rounding cannot supply missing facts.

This invented exercise is separate from the CNY 1,530 ledger below. A actually fronts one CNY 100.01 shared expense. A, B and C agree weights of 2:2:1, with ties resolved in A, B, C order. T is 10001 fen and W is 5.

The bases total 10000 fen, leaving one fen. A and B have equal remainders, so the agreed tie order gives it to A: 4001 + 4000 + 2000 = 10001 fen. Independently rounding the yuan amounts to 40.00, 40.00 and 20.00 would total only CNY 100.00, losing one fen. Values such as 4000.4 are intermediate calculations, not a request to pay a fraction of a fen. Initial balances for this exercise are A +60.00, B −40.00 and C −20.00. They reach zero only after B actually pays A CNY 40.00, C pays A CNY 20.00 and A confirms both receipts. The remainder was already allocated within the expense; do not add a second “rounding expense” at settlement.

Allocate a small refund without replacing previous settlements

Continue this separate exercise after both settlement payments have arrived. A then actually receives a CNY 0.03 refund for the original expense. For this example, all three agreed in advance that a non-targeted refund would use the same 2:2:1 weights and remainder method. Receipt by A does not give A the entire benefit, and the example does not prescribe how every real refund belongs. Verify refunds for an individual's item or disputed amounts or ownership separately under section 5 rather than applying this allocation automatically.

Three fen at 2:2:1 gives 1.2, 1.2 and 0.6 fen. The base whole amounts are 1, 1 and 0; the integer remainders are 1, 1 and 3, leaving one fen. C now has the largest remainder and receives the extra fen. Each person's refund benefit is therefore one fen, totaling three. Do not round each share and then distribute another three fen. Keep the original CNY 100.01 expense and both settlement payments; add one “CNY 0.03 refund received” row linked to the original expense.

Because A received the refund, the complete formula in section 4, including prior settlements, now gives A −0.02, B +0.01 and C +0.01, summing to zero. B and C do not pay their original CNY 40.00 and CNY 20.00 again. If A actually returns CNY 0.01 to each and both confirm receipt, the balances reach zero again. Final costs are A 40.00, B 39.99 and C 19.99, totaling CNY 99.98 = 100.01 − 0.03. Neither the refund nor a settlement payment is entered again as new spending.

This does not establish that any payment channel can process CNY 0.01. If the channel cannot complete that payment, retain the actual balance and the handling both people agree to. They may combine it with a later shared item already agreed to; do not erase it unilaterally, invent spending to reach a payment amount, or mark a failed transfer as received. Number separate refund receipts and check their cumulative allocations, original ownership and actual money received. Pause the row if anything is inconsistent.

Keep a redacted check card in the private offline travel kit: expense ID___ | paid amount, currency and whole fen___ | participants and weights___ | tie order___ | base amounts/remainders___ | extra-fen recipients___ | share total___ | prior settlement references___ | refund recipient and amount___ | agreed refund ownership and each benefit___ | new balances including prior settlements___ | actual receipt confirmations___. Separately test the payer's available cash with the payment-by-payment budget check. These methods and invented calculations were added on 4 October 2026 UTC; the original official-source access dates are unchanged. They help travellers reproduce an agreed small-expense ledger and recommend no app, payment channel or financial product.

2. Give every expense six fields

On narrow screens, scroll the table sideways to read all columns.

The US Consumer Financial Protection Bureau's educational spending tracker recommends retaining receipts, or writing down an expense when there is no receipt, before adding totals. It also warns against putting names, account numbers or similar sensitive information into such worksheets. This guide borrows only the method of recording actual spending before totaling it; the US material is not presented as Chinese law.

A duplicate ledger entry is not the same as two real charges

Assign a unique row ID to each actual payment before combining screenshots from the group. Two companions uploading evidence of the same person's single transaction does not create two expenses. Conversely, if two accounts were actually charged, do not discard one merely because amounts, dates or order details look alike. Screenshot counts are not payment counts, and matching amounts do not prove a duplicate charge.

This invented exercise is separate from the CNY 1,530 ledger below. A, B and C share one CNY 360 dinner equally, at CNY 120 each. A actually pays CNY 360. Both A and B send the ledger keeper the same redacted evidence of A's payment; B is only the uploader.

Shared spending remains CNY 360, not CNY 720. Only after B and C each actually pay A CNY 120 and A confirms receipt do these balances reach zero. This exercise has no deposit, refund or previous settlement; do not add its results to the larger ledger below.

If you instead verify an actual CNY 360 charge in each of A's and B's accounts, retain both cash movements and check whether they relate to the same dinner, different orders or other purchases. Suppose all three agree that there was only one shared dinner, A's payment is confirmed as paying for that CNY 360 dinner, and the merchant has not yet clarified B's second charge. Record the confirmed CNY 360 as a shared expense. Keep B's separate CNY 360 as an open item: “charged; corresponding purchase unconfirmed.” B's cash has genuinely decreased. The amount has not been refunded and must not disappear, but it is temporarily excluded from shared costs and settlement balances. Do not automatically assign it to A or split it among all three.

Under those assumptions, settle only the CNY 360 expense everyone has agreed to, not the entire ledger. If both charges later prove to be for two dinners that were used and agreed as shared costs, create separate expense rows and confirm each set of shares. If B's open charge never entered shared costs and CNY 360 is later actually returned to B, record the receipt and close B's open item; do not also distribute that same refund to all three as a shared-expense refund. If the merchant establishes another cost to be borne, agree its allocation from the new evidence. A suspected extra charge does not determine liability or guarantee a refund.

Work through these checks:

1. Each payer checks the transaction status in their own account, matching the order, merchant, amount, date and redacted transaction reference. Do not ask for passwords, full card numbers, one-time codes or payment QR codes.
2. Number expense rows separately from evidence, for example expense D01 with references R01/R02. Only after confirming that an extra ledger row records the same actual payment should you mark that row “duplicate entry; D01 retained.” Keep the editor, date and reason, rather than silently deleting history.
3. Distinguish an unconfirmed expense, an actual charge and a refund not yet received. A successful refund request is not cash returned. Use the budget-travel payment timeline to check whether the open charge affects that payer's money for the journey home and emergencies.
4. Calculate balances after agreeing the shared cost, payer and shares. Settle only the undisputed portion and identify every remaining open row. Save redacted row IDs, current status and the next check date in the offline travel kit; each person retains their own original account evidence.

These deduplication steps and examples are an editorial addition dated 4 October 2026, not a determination of merchant or bank refund deadlines or legal liability. They do not depend on an app's automatic duplicate detection. Keep insufficiently evidenced items open instead of guessing payers or shares to make the balances zero.

Keep a separate ledger for each currency

If a shared travel ledger contains more than one currency, treat the amount and currency as an inseparable pair. This section is only for expenses that the participants have agreed to record in their respective currencies and whose actual amounts can be checked. It provides no currency-exchange, rate, fee, tax or cross-border payment advice. Copy the section 7 template for each currency. Expenses, assigned shares, received refunds and previous settlements all need the same currency label within that ledger, and each ledger uses the section 4 formula independently. CNY 100 and USD 15 do not make a total of “115”. Similar-looking currency symbols do not establish that two amounts are in the same currency.

1. Give each expense a unique ID and confirm its actual amount, currency, payer, participants and shares. If the order and payment evidence show different currencies, have the participants agree which actual amount is the basis for sharing that expense. Until then, keep it pending. Do not enter two currency representations of the same purchase as two shared expenses.
2. Within each currency, check the share total, refund ownership and completed settlements. Include that currency's previous payments and receipts; do not move a payment in another currency into the ledger to fill a gap. Check uncertain precision or payment conditions rather than automatically applying the earlier CNY fen method to every currency.
3. Keep a list of balances by currency. Repaying in a different currency is a separate arrangement requiring agreement and verification of actual payments and receipts; it is outside this worked example. Do not fill unresolved conversion terms, fee ownership or receipt status with an online quote, estimate or unilateral offset. You can establish the undisputed balances in each currency while leaving a proposed repayment in another currency pending.

Keep redacted expense IDs, currency labels and the evidence for actual amounts in the private offline travel kit, without full card numbers, account details or transaction codes. Check available cash separately with the payment-by-payment budget check. An amount owed to you in the ledger is not money you have already received and can use.

Check that each currency balances independently

This invented two-person exercise is separate from the CNY 1,530 example below and the CNY 100.01 exercise above. It contains no conversion or fees and represents no real price, service or payment-channel capability. A actually fronts CNY 200 for shared accommodation, with A and B agreeing to CNY 100 each. B actually fronts USD 30 for shared tickets, with USD 15 assigned to each. B later actually receives a USD 6 ticket refund, and both agree that USD 3 of the refund belongs to each person. There is no accommodation refund or previous settlement payment.

For CNY, A has 200 − 100 = +100 and B has 0 − 100 = −100. For USD, A has 0 − 15 − 0 + 3 = −12, while B has 30 − 15 − 6 + 3 = +12. The balances sum to zero separately in each currency. Net shared costs are CNY 200 and USD 24; each person's costs are CNY 100 and USD 12. There is no single “230 total spending” or “224 net cost”. Nor can USD 12 be subtracted from CNY 100 to produce “only 88 to pay”.

If both people separately confirm that the agreed payments in each currency can actually be completed, B pays A CNY 100 and A confirms receipt. Only the CNY ledger then reaches zero: USD still shows A −12 and B +12. The USD ledger reaches zero only after A actually pays B USD 12 and B confirms receipt. Record each repayment with its currency, payer, recipient, amount, status and redacted reference, not as another expense. This order merely demonstrates the ledger; it recommends no payment channel. If a payment cannot be completed as agreed, its currency changes or an unagreed fee appears, pause reconciliation and verify the arrangement rather than treating one settled ledger as proof that everything is settled.

Private check card: expense ID___ | actual amount and currency___ | agreed basis for that amount___ | each person's share in this currency___ | received refund and ownership in this currency___ | previous settlements in this currency___ | balance sum for this currency___ | unresolved currency/amount/repayment arrangement___ | payment and receipt separately confirmed___. This section is an editorial method for checking units, with invented calculations. It does not change the original official-source access dates.

3. Worked example: different users, one ledger that still balances

Every number below is an invented, single-currency CNY exercise, not a quote for any city. A, B and C agree that the accommodation uses two, two and one shares; only A and B attend the dinner and accept exact shares of CNY 120 and CNY 240; the tickets are equal; and A fronts a shuttle used only by C.

On narrow screens, scroll the table sideways to read all columns.

A also buys CNY 80 of personal goods, which are excluded. A pays a CNY 300 refundable accommodation deposit that has not been returned. Record it as “deposit held,” not as part of the CNY 1,530 expense total. This preserves the distinction between cash temporarily unavailable and a confirmed final cost.

C later receives a CNY 90 partial refund for the tickets. Because the original ticket cost belonged equally to all three, reverse CNY 30 for each original participant; do not give the whole benefit to C merely because C received the money. Keep the original CNY 450 line and add a separate “CNY 90 refund received” line. That audit trail is clearer than silently changing the original expense to CNY 360.

A separate CNY 60 dinner refund has been requested but has not reached B's account. It remains in the pending-refund list and changes nobody's balance. In this example, the travellers agreed that if it arrives, it will reverse the original dinner shares: CNY 20 for A and CNY 40 for B. Recalculate while retaining every prior settlement payment. This is the agreement for this example; a refund expressly belonging to one person's item must not automatically be spread across the whole group.

4. Net-balance formula and one settlement payment

Use a positive number for “this person should receive” and a negative number for “this person should pay.” Include only completed expenses and refunds actually received:

Net balance = shared expenses paid - assigned expense shares - shared refunds received + assigned refund benefit + prior settlement payments made to travellers - prior settlement payments received from travellers

• A: 720 - 510 - 0 + 30 = CNY +240.
• B: 360 - 630 - 0 + 30 = CNY -240.
• C: 450 - 390 - 90 + 30 = CNY 0.

The balances add to zero, so the internal ledger conserves the full amount. Check it from the cost side as well: CNY 1,530 gross spending minus the CNY 90 received refund is CNY 1,440 net group cost. The final costs are A 480, B 600 and C 360, also totaling CNY 1,440.

There are no earlier settlements in this example, so the formula's final two terms are zero in the first calculation. Only one payment is needed for the currently confirmed entries: B actually pays A CNY 240. Once receipt is confirmed, that payment changes A's balance by -240 and B's by +240, leaving A, B and C at zero for those entries. Within this travel-sharing ledger, repayment closes a balance; it is not recorded again as new income for A or another travel expense for B. Doing so would double count it. This is not a tax or general accounting classification.

The CNY 300 deposit and CNY 60 pending refund are still open, so “zero now” does not mean the trip can never change. Suppose B has paid the CNY 240 and the CNY 60 dinner refund later reaches B. Expenses and refunds alone would then show A +260 and B -260. Put the prior B-to-A settlement payment back into the full formula: B has already paid 240 and A has already received 240, leaving A +20 and B -20. B pays A only another CNY 20, not CNY 260.

Splitwise's official explanation of debt simplification likewise says that changing payment paths does not change anyone's total balance. The table, formula and example here are original HeTuZhi editorial material and can be reproduced on paper or in a plain spreadsheet. No particular app or payment channel is required.

5. Keep separate states for refunds, deposits and corrections

1. Refund requested: Record the expected amount, original line, request date and current status, but do not alter the net balances. “Initiated” on a merchant screen is not proof that the receiving account has the money.
2. Refund received: Add a reversing line against the original expense. Allocate it to the original participants and shares or another ownership rule the travellers confirm; do not spread a refund for one person's item across the whole group automatically. The expense tool's official refund help also treats a refunded shared expense as money to distribute back to the relevant members; it does not resolve any real-world dispute for them. Keep earlier settlement payments in every recalculation.
3. Refundable deposit: Track paid, partly returned, fully returned or confirmed deduction. While held, it is tied-up cash rather than confirmed spending. If a deduction is later confirmed, create an expense only for that amount and let the group agree who bears it.
4. Withdrawal or correction: Do not erase history silently. Mark the old row “voided—replaced by [new row],” with the editor, time and reason. Recalculate the balances, then determine whether an earlier settlement needs a top-up or a return payment.

6. Reconcile the ledger with money actually received

When the sheet says “B pays A CNY 240,” do not mark the trip settled immediately. Check payer, recipient, amount, date and status first. Add the repayment only after the recipient confirms receipt, then bring both balances to zero.

For cash, both people can confirm “paid” and “received” in the same group message. For an electronic transfer, keep only a redacted reference. A shared ledger does not need a full account name, card number or payment QR code. This guide recommends no financial product, expense app or particular payment rail.

Never send an identity number, full bank-card number or SMS one-time code merely to “check the trip expenses.” Before sharing a booking or receipt, mask names, document numbers, contact details, room numbers, barcodes, QR codes and unrelated orders.

7. Copyable blank travel-expense ledger

Trip:
Ledger currency (no automatic conversion):
Participants:
Settlement date:

Agreement
- Equal split by default? If not, what rule applies?
- How will unequal shares be confirmed?
- Item boundaries for anyone joining or leaving partway:
- Who takes a rounding remainder?

Completed expenses
ID | Date | Item | Amount | Payer | Each person's share | Status | Redacted evidence reference

Pending items (excluded from net balances)
ID | Type (deposit / refund not received / needs checking) | Original expense ID | Amount | Current holder | Status | Next check date

Received refunds
ID | Receipt date | Original expense ID | Amount | Recipient | Each person's refund benefit | Redacted evidence reference

Net balances (positive = receive; negative = pay)
Person | Shared expenses paid | Assigned expense shares | Refunds received | Assigned refund benefit | Prior settlement payments made | Prior settlement payments received | Net balance
Balance sum (must be zero):

Settlement record
Date | Payer | Recipient | Amount | Cash/transfer | Receipt confirmed | Redacted reference

Withdrawal/correction
Old row ID | Status | Reason | Replacement row ID | Editor and time | Balances recalculated

The travellers themselves must agree on shares. If an amount, participation boundary or deduction is disputed, freeze that row and preserve each person's account instead of assigning the disputed amount unilaterally. Where necessary, verify with the booking provider or a qualified professional. This tutorial does not allocate legal responsibility. The official public materials linked above were accessed on 25 September 2026; the worked arithmetic, formula and template are original editorial material from HeTuZhi.