A Google Sheets tracker can hold a bachelor party's shared costs, receipts, and reimbursements in one place. Use one row for every purchase, store the amount before splitting it, and settle only after the group checks the log.
Keep it boring. That is a strength here.
Build the tracker around one expense ledger
Turns out, the cleanest setup separates expenses from repayments. The expense ledger records what the group bought and who advanced the money; a separate payments tab records money sent later.
One row, one story.
| Column | What to enter |
|---|---|
| Date | The purchase date |
| Description | A clear label such as group dinner, rental deposit, or activity tickets |
| Category | Travel, lodging, food, drinks, activity, or another agreed category |
| Amount | The full amount being shared, entered as a number and formatted as currency |
| Paid by | The person who paid the merchant |
| Split method | Equal, Weighted, or Reimbursement |
| Receipt link | A Google Drive link to the receipt or confirmation |
| Notes | Context such as personal items removed, a deposit, or a cancellation |
| Member columns | One column per person, using weights such as 1, 0, or 0.5 |
The Amount field is the source of truth. Enter the shared charge once, then let the participant weights determine each person's share.
Member cells are weights, not payments. Use 1 for a full weight, 0 for no share, and a value such as 0.5 for a half weight. If everyone has a weight of 1, the formula creates an equal split.
Do not mix those meanings. Paid by tells you who advanced the money. The member columns tell you who is responsible for the cost.
A reimbursement row needs a little care. If Mike pays for the groom's ticket, enter Mike under Paid by, give the groom a weight of 1, and give everyone else 0. The groom owes the amount, while Mike is due the reimbursement. If Mike is also sharing the cost, give him the weight you agreed on.
Create the tabs and input rules
Start with four tabs named Expenses, Shares, Balances, and Payments. Keeping the tabs separate makes it harder to overwrite a formula while someone is adding a receipt.
- Build the
Expensestab with the columns above. Put the participant names inI1:M1, or continue farther right if the group is larger. - Format the
Amountcolumn as currency, but enter numeric values rather than text that includes a dollar sign. - Add dropdowns to
Paid byandSplit method. Use the participant names for the first dropdown andEqual,Weighted, andReimbursementfor the second. - Create a Drive folder for receipts. Google Drive help covers folder organization and sharing basics.
- Add two test expenses before the trip. Try one equal split and one reimbursement-only row, then check the results.
A useful file name might be Bachelor Party Shared Costs. Put the trip dates in the notes or file name only if they help the group recognize the correct version.
Add formulas for shares and balances
The Shares tab calculates each person's portion of every expense. Copy the participant names from Expenses!I1:M1 into Shares!I1:M1.
In Shares!I2, enter:
=IFERROR(Expenses!$D2*Expenses!I2/SUM(Expenses!$I2:$M2),0)
Copy that formula across the participant columns and down through the rows you expect to use. The reference to Expenses!I2 should move across as you copy, while the denominator should continue to cover every participant column.
The formula works like this:
- Equal weights divide the amount equally.
- A zero weight gives that person a zero share.
- A half weight gives that person half the weight of someone marked
1. - A row with one weight of
1assigns the full amount to that person.
If you add participants after column M, extend the denominator in every formula. Otherwise, the new person's weight won't be included.
Set up the Balances tab horizontally. Put the member names in I1:M1 and these labels in column H:
| Row | Label | Formula in column I |
|---|---|---|
| 2 | Paid | =SUMIF(Expenses!$E$2:$E$200,I$1,Expenses!$D$2:$D$200) |
| 3 | Owed | =SUM(Shares!I$2:I$200) |
| 4 | Expense balance | =I2-I3 |
| 5 | Sent | =SUMIF(Payments!$B$2:$B$200,I$1,Payments!$D$2:$D$200) |
| 6 | Received | =SUMIF(Payments!$C$2:$C$200,I$1,Payments!$D$2:$D$200) |
| 7 | Final balance | =I4+I5-I6 |
| 8 | Status | =IF(ROUND(I7,2)=0,"Settled",IF(I7>0,"Should receive","Should pay")) |
Copy each formula across the participant columns. A positive final balance means the person should receive money. A negative balance means the person still owes money.
The Payments tab needs six columns: Date, From, To, Amount, Method or note, and Confirmation link. Add a payment only after money has actually been sent. If Alex sends $50 to Jordan, put Alex in From, Jordan in To, and 50 in Amount.
Payments are not expenses. Do not add a second negative expense to show that someone paid Jordan back.
Add a simple allocation check somewhere visible:
=SUM(Expenses!$D$2:$D$200)-SUM(Shares!$I$2:$M$200)
A result of 0 means the expense amounts and calculated shares match. A nonzero result usually points to a row without participants, a missing participant column in the formula, or an amount entered as text.
For a category total, list a category in A2 on a summary area and use:
=SUMIF(Expenses!$C$2:$C$200,A2,Expenses!$D$2:$D$200)
Use a filter view on the Expenses tab to review large charges, missing receipt links, or every expense paid by one person.
Keep receipts connected to the money record
Create one receipt folder before purchases start. Name files consistently, such as dinner receipt or rental deposit confirmation, then paste each file link into the matching expense row.
Receipts settle arguments faster.
If a receipt includes personal items, record only the amount the group agreed to share and explain the adjustment in Notes. Keep the full receipt link so people can see how the amount was determined.
A flight confirmation, lodging invoice, activity ticket, or bar receipt can all work as supporting records. The sheet does not need a scan for every small purchase, but missing documentation should be visible rather than silently ignored.
Share the sheet without handing away the formulas
Give edit access to the people who will enter expenses. Everyone else can use viewer access if they only need to inspect the record. An "anyone with the link can edit" setting is convenient, but it also makes accidental changes easier.
Protect the calculation areas after testing them.
- Keep
Expensesinputs separate fromSharesandBalancesformulas. - Protect formula ranges so an editor cannot replace them with typed values.
- Use dropdowns for names and split methods, but do not treat dropdowns as security.
- Leave a notes column for disputed charges or agreed exceptions.
- Make a copy of the finished ledger before the group settles.
Use a restricted Drive folder when the receipts contain more detail than the group needs to share broadly. The sheet can remain collaborative without making every receipt publicly editable.
Review the ledger before anyone settles up
Set a review point after the last shared purchase. Ask the group to check the following:
| Check | What a clean result looks like |
|---|---|
| Expense rows | Each row has a payer, amount, description, and split rule |
| Participant weights | Every shared expense has at least one positive weight |
| Receipt records | Each meaningful charge has a working link or a note explaining the gap |
| Allocation check | The check formula returns zero |
| Balance totals | Positive and negative final balances offset each other, apart from rounding |
| Payments | Only completed transfers appear on the Payments tab |
Thing is, a spreadsheet shows the agreed accounting. It does not decide whether an expense was fair. If the group disagrees about the groom's share, a room assignment, or a personal upgrade, record the decision in Notes before changing numbers.
When a spreadsheet is enough
A sheet is a good fit when the event is a one-time trip, the split rules are clear, and one or two people can maintain the log. It also works well when the group wants a record but will use a separate payment service to settle balances.
| Need | Spreadsheet fit | Consider another tool when |
|---|---|---|
| Shared expense record | Strong fit for a small, agreed list of purchases | Many people need to enter items constantly |
| Uneven rules | Flexible with weights and notes | You need detailed item assignment without manual setup |
| Receipts | Easy to connect with Drive links | You want a tool to process receipts automatically |
| Payment requests | Requires a separate payment step | The group expects built-in requests or reminders |
| Final records | Easy to copy or export | Everyone needs a different live view or automated report |
Tracking, requesting, paying, and recordkeeping are separate jobs. To be honest, choose a spreadsheet when the record is the main need, and check any other tool's actual features before relying on it for payments or exports.
Questions about bachelor party expense tracking
How should the groom's smaller share work?
Agree on the rule before buying anything. A groom weight of 0.5 gives the groom half the weight of a person marked 1; a weight of 0 excludes the groom from that row. This creates a proportional split, not necessarily an exact dollar amount.
For a fixed dollar arrangement, use direct share columns instead. Make sure each row's participant shares add up to the amount being split.
Should the person who paid always be included?
No. Include the payer only if that person is responsible for part of the expense. Someone can advance the entire cost for another person and still have a zero participant weight.
What belongs in a reimbursement row?
Use it for a cost one person covered on behalf of another, such as a ticket, deposit, or personal add-on. Put the person who owes the cost in the participant columns, then record the later transfer on Payments.
What should happen if a receipt is missing?
Leave the receipt cell blank only temporarily and explain the gap in Notes. Ask the payer for a confirmation, photo, or digital copy before final settlement.
Before the first shared purchase, add the member names, test one equal split and one reimbursement row, then share the file with the people responsible for updating it.