One folder, one log. That's the whole system. Every cost the group might split goes into a single shared place, and each file proves one purchase while a short log records who fronted the money and how the charge divides. Dinners, rentals, activities, deposits, group gifts: it all fits.
The folder won't settle balances by itself. That's fine. What it does is give everyone something concrete to review before anyone sends an IOU or asks to be paid back.
Decide what the folder needs to show
Every entry has to answer four questions: what was bought, when, how much, and who paid. Group expenses add a fifth. Who belongs in the split.
| Detail | What to record | Example |
|---|---|---|
| Purchase | Date, vendor, and total | May 16, venue dinner, $45.75 |
| Payer | Person and payment method | Jane, cash |
| Split | Participants and agreed rule | Bride plus four friends; split six ways |
| Proof | Legible photo, scan, or PDF | Full receipt with total visible |
One record per transaction. If a receipt carries a deposit, tip, tax, or a later refund, add a note right there. Memory is a bad place to store money details.
Group gifts deserve one extra step. Write down whether the purchase was optional and who actually agreed to contribute, because not every attendee owes every charge.
Choose a physical, digital, or hybrid folder
Paper still has a place. Unreliable service, limited phone access, or lots of cash purchases all argue for a small accordion folder with sections like Pre-Trip Deposits, Meals and Drinks, Activities and Entertainment, Travel and Gas, and Miscellaneous.
Digital storage fits remote attendees, plus organizers who want to review receipts from different locations. Put the folder in a service the group already understands, then keep a simple log beside the receipt files.
Turns out, a hybrid setup is often the easiest for travel. Photograph the important paper receipts as soon as you can, and hold the originals until the final balance is accepted.
Build the digital folder before anyone pays
Build it before the first group charge. Four small decisions head off most end-of-trip confusion.
- Create a folder named
Bachelorette ReceiptsorBachelorette Party - Receipts. Add category folders only if they'll make searching easier. - Pick one or two trusted organizers as editors. Everyone else gets viewing access unless they have a specific upload task.
- Add a receipt log as a simple spreadsheet or a printable cover sheet. The log points to the proof, it doesn't replace it.
- Send the naming rule and the split rule to the group chat before the weekend starts.
Permissions are worth a minute of your time. On Google Drive, people with edit access may edit, delete, or move files in a shared folder, while viewers can open the files without changing them. Check Google's folder-sharing guidance before you share anything.
A short group message does the job:
Please upload each shared receipt within 24 hours. Use the agreed file name, add who paid and who participated, and flag any unclear split before requesting reimbursement.
Use a filename that carries the basics
A consistent filename lets people search without opening every single file. Use:
YYYY-MM-DD_Vendor_Category_Amount_PaymentMethod.pdf
For example:
2026-05-16_Venue_Dinner_45.75_Cash.pdf
2026-05-16_CoffeeHouse_12.50_Card.pdf
Use underscores instead of spaces when you need a separator. If a scanning tool saves a JPG rather than a PDF, keep the same naming pattern and change only the extension.
The filename identifies the purchase. People and exceptions belong in the log or an accompanying note (especially when only some attendees joined an activity), not in the file name itself.
Keep a short log beside the files
The log is the index.
Use a paper cover sheet for a physical folder or a basic spreadsheet for a digital one. These columns are enough for most small parties:
| Date | Vendor | Amount | Paid by | Method | Split note | Status |
|---|---|---|---|---|---|---|
| May 16 | Venue | $45.75 | Jane | Cash | Six people | Needs review |
| May 16 | Spa | $240.00 | Alexis | Card | Four participants | Confirmed |
Stick with simple status labels such as Needs review, Confirmed, Reimbursed, or Disputed. The status tells the organizer what still needs attention at a glance. And an index isn't proof, so keep the original receipt file even after someone records the amount.
Agree on the split before settling up
Thing is, an equal split is convenient but not always fair. Write the rule down before the organizer totals anything.
| Split method | Works well for | Check before reimbursement |
|---|---|---|
| Equal per-person | Shared dinners or common rental costs | Include only people covered by the agreement |
| Usage-based | Optional spa services or activities | Record the participants on that receipt |
| Contributor-only | A group gift or special add-on | List who opted in |
| Reimbursement after proof | Unclear or disputed charges | Hold that line until the group reviews it |
The bride's share should follow the group's agreement. Some groups include her in shared costs, others choose to cover selected items for her. Put that decision in writing instead of treating it as automatic.
A workable example: "Shared dinners are split among attendees. Optional activities are split only among participants. Deposits are reimbursed after the final charge or refund is known."
Review receipts during the trip
Upload receipts within 24 hours while the details are still fresh. A quick nightly check covers a weekend trip. Longer trips can run weekly reviews instead.
Each review confirms the same five things: vendor, total, payer, participants, and payment method. Anything unclear gets marked for review rather than guessed at.
For the final tally, total by category first, then apply the split rule, and only then start on adjustments, because if dinners came to $300 for eight people, that's $37.50 each as a starting share before you account for anyone who didn't attend, any agreed exclusion, or any usage-based charge.
Then record the amount owed, the person receiving it, and the date it gets paid. Someone waiting on proof can sit marked as an IOU pending review, but an IOU should never quietly turn into a confirmed group expense.
Handle cash, deposits, refunds, and missing receipts
This is where most disputes start, because the paper trail is usually incomplete.
| Situation | What to save or write down |
|---|---|
| Cash purchase | Photograph the receipt and write Cash plus the payer's name |
| Deposit | Keep the original charge and note what it covers |
| Refund or cancellation | Save the refund proof and record it as a separate line |
| Missing receipt | Note the date, vendor, amount, purpose, payer, and participants; let the group decide whether it is enough |
| Duplicate upload | Mark one file as a duplicate rather than counting it twice |
Don't overwrite the original charge when a refund arrives. The group needs to see both sides of the transaction and the net amount left over.
A missing receipt doesn't automatically invalidate a charge, but it removes useful proof. If the group can't agree on the details, pause that line until it's sorted.
Know when a folder needs a spreadsheet or app
A folder plus log is usually enough for a small trip with fewer than about 20 receipts and one person coordinating the review. That's a practical starting point, not a universal cutoff.
Past about 50 receipts, or with many partial shares and repeated deposits and refunds, add a spreadsheet for the formulas and filters. Equal shares are simple math: if the amount sits in cell C2 and the share count in F2, the starting formula is =C2/F2.
To be honest, an app may make payment requests easier, but it doesn't automatically replace source receipts or the group's split agreement. Separate tools for separate jobs. The folder preserves proof, the spreadsheet calculates totals, and a payment tool can help request money if the group prefers one.
Keep access limited
A receipt can expose more than a price. It may show a name, an address, a reservation detail, or financial information.
So share the folder directly with attendees instead of using a public link. Keep one or two editors, give everyone else view access, and remove former collaborators after the balance settles. The FTC's Protecting Personal Information guide, although written for businesses, recommends taking stock of where sensitive information is kept and how it moves.
Crop or redact anything the group doesn't need, but leave the date, vendor, and total visible. Full card numbers, bank login details, and unrelated personal documents never go in.
Fix the mistakes that create reimbursement disputes
Most reimbursement fights trace back to a handful of avoidable slips.
| Common mistake | Better practice |
|---|---|
Files named receipt.jpg |
Use the date, vendor, category, amount, and payment method |
| All uploads wait until departure | Upload within 24 hours |
| The payer is not recorded | Add the payer to the log and filename note |
| Everyone can edit or delete files | Limit editing to one or two organizers |
| A refund replaces the original receipt | Keep the original and add the refund separately |
| Optional activities are split with everything else | Record participants and use a usage-based split |
A rotating uploader helps when one organizer gets busy. One person checks Friday's receipts, another takes Saturday's, and the final reviewer still confirms the total.
Questions people ask
Is a physical backup necessary? Not always. It earns its keep on cash-heavy trips and in places with poor service. Scan key receipts when possible, then keep the paper copies until the group accepts the final balance.
What if someone disputes one expense? Pause reimbursement for that line and share the original receipt, the payer note, and the split decision. Undisputed expenses can settle separately if the group agrees.
Who should review the folder? One or two trusted organizers check uploads during the trip and complete the final tally. Everyone else still gets to view the proof and question a charge.
Before the first group purchase, run a mock entry. Upload one sample receipt, open it as a viewer would, check the filename, and confirm the split rule in chat. That five-minute test catches access and naming problems while the weekend is still calm.