TL;DR:
- Planners who get paid on time collect guest travel money through a booking page they control — deposit at booking, instalments auto-charged, every balance visible — not through the couple's Venmo or a personal account.
- The planner's fee is a separate matter: a flat fee to the couple, a per-guest amount in the package, resort commission, or a mix. Keep it separate from the pass-through travel money.
- The two things that generate the most support work — pausing a guest's plan and expired cards — should be dashboard edits, not rebuilt bookings.
- SquadTrip is free for planners; guests pay one 6% processing fee and the planner or couple receives the full package price.
Destination wedding planners who get paid on time collect guest travel money through a booking page they control: each guest chooses a room package, pays a deposit, and is charged the instalments automatically, while the planner sees every balance and exports the rooming list. The planner's own fee is handled separately — invoiced to the couple, built into the package, or earned as resort commission — so the travel money stays a clean pass-through and the fee stays clean income. SquadTrip is built for exactly this and is free for the planner; guests pay a single 6% processing fee at checkout.
This guide covers the four ways planners collect today and what each costs you, where the fee goes, the set-up for a client wedding, the pause-and-restructure problem, and how to hand the couple the numbers.
Four Ways Planners Collect Today
1. The couple collects, the planner tracks
Guests pay the couple on Venmo or by transfer; the planner keeps the spreadsheet. The planner has all of the responsibility for the headcount and none of the control over the money.
2. The planner's own account
Guests pay the planner, who pays the resort. Fast to set up, and the worst place to be when a guest disputes a charge, a card fails, or year-end reconciliation arrives with sixty guests' deposits mixed into the planner's income.
3. Resort direct, planner reconciles
Guests book the group rate with the hotel; the planner chases the rooming list. Works for courtesy blocks; fails for villas and resorts that want one payer.
4. A booking page
Guests pay for their own room and add-ons through a page the planner controls; payments settle to a Stripe account set up for the wedding; the planner's dashboard is the source of truth. The rest of this guide is about doing this well.
| Method | Control | Chasing | Liability sits with | Fee handling |
|---|---|---|---|---|
| Couple collects, planner tracks | Low | High | Couple | Separate invoice |
| Planner's own account | High | High | Planner, personally | Mixed with travel money |
| Resort direct | Low | Medium | Resort | Commission or invoice |
| Booking page | High | Automated | Wedding's own Stripe account | Separate, or built into package |
Choose a booking page for any contracted block, villa, or resort that wants one payer. Choose resort direct only for a courtesy block where every guest can book the group rate themselves.
Where the Planner's Fee Goes
1. Flat fee to the couple
Invoiced separately, usually in stages. Cleanest for accounting: the fee is income, the travel money is pass-through.
2. Per-guest amount in the package
A $1,800 room becomes $1,900, with $100 per guest as the coordination fee. Simple for guests; make sure the couple knows and the ledger records it, so the margin is explainable at year end.
3. Resort commission
Many resorts pay a commission on the room block to the planner or agent who booked it. It is earned on the block regardless of how guests pay, so it combines with either of the above. Do not rely on it to cover a shortfall from attrition.
Whichever you use, keep the fee and the guests' travel money on separate lines. The taxes on money collected from wedding guests guide explains why the pass-through needs its own ledger.
Setting Up the Page for a Client Wedding
- Packages mirror the room block. One package per room type, priced per guest or per room, with the group rate and what it includes.
- Deposit and instalments tied to the block's dates. Deposit at booking sized to cover the block deposit; the last instalment 2–3 weeks before the hotel's cut-off. See room block vs booking page for the timeline.
- Add-ons at checkout. Welcome dinner, catamaran, spa, extra nights — optional, priced separately, each with its own headcount.
- Registration fields. Names for the rooming list, sharing preferences, arrival and departure, dietary needs, plus-ones.
- BNPL on. Guests who cannot pay the deposit today book today through Klarna, Affirm or Afterpay; the wedding is paid in full at booking.
- One link. "Book your travel" on the couple's wedding website, in the invitation, in the group chat.
The Pause-and-Restructure Problem
This is where planners spend their support hours, and it is worth choosing a platform around.
1. A guest asks to pause
A job loss, a change of plans, a guest who will pay the balance in cash to the couple. The planner needs to pause that guest's remaining instalments — not cancel the booking, not refund — in one edit the guest can see.
2. A card expires mid-plan
Four instalments over six months and one card lapses. The platform should retry, notify the guest, and let them update the card themselves without the planner in the loop.
3. Older guests and online checkout
Some guests will not complete a checkout on their own. The planner needs to be able to take the booking on the guest's behalf, or send a direct payment link, without breaking the ledger.
4. A change after the cut-off
A guest switches rooms or adds a night. The booking is edited, the balance updates, and the rooming list export reflects it — no parallel spreadsheet.
On SquadTrip each of these is a dashboard action: pause or edit a guest's schedule, resend a card request, book on a guest's behalf, edit a booking. The couple's travel money stays on one ledger through all of it.
Pause, edit, re-request — without rebuilding the booking
Guests book and pay on schedule; you adjust any plan from the dashboard. Every balance and the rooming list are one export away.
Set up a wedding booking pageHanding the Couple the Numbers
- Balances: who has paid what, who is behind — the weekly "who has paid?" email becomes a shared view.
- Rooming list: exported at the cut-off in the format the hotel wants.
- Add-on headcounts: per event, to the caterer and the excursion operator.
- Year-end export: every payment, refund and guest, so the couple's 1099-K question is a one-page reconciliation.
Managing a wedding room block? SquadTrip takes it off the spreadsheet — guests book and pay themselves, and you see every balance. Free for planners.
Common Mistakes
- Letting travel money run through the planner's personal or general account
- Folding the fee into the package without recording it
- Setting the payment schedule to the wedding date rather than the block's cut-off
- Choosing a platform where a paused plan means a cancelled booking
- Chasing sixty guests by hand for a second instalment
A Client Wedding, Start to Finish
Sixty guests, a resort block in Mexico, a couple who want to be told the number rather than manage it.
1. Month 10: the block and the page
The block is signed at 80% attrition with a cut-off 45 days out. The page goes live the same week: three room packages mirroring the block, a welcome dinner and a catamaran as add-ons, a 25% deposit sized to cover the block deposit, and three instalments finishing three weeks before the cut-off. The planner's fee is invoiced to the couple separately, in three stages.
2. Months 9 to 5: the money arrives
Deposits come in as the invitations land; the planner watches fill rate against the 48-room attrition line. Two guests use Klarna for the deposit. One guest asks to pause after a job change - the planner pauses the plan from the dashboard, no cancellation, and picks it up two months later.
3. Month 4: the card problem
Three cards fail on the second instalment. The platform retries and emails the guests; two update their card themselves, the third calls the planner, who resends the card request. No rebuilt bookings.
4. The cut-off
Fifty-two rooms filled; the attrition clause never applies. The rooming list is exported to the resort. The couple gets the balances view: two guests still owe a final instalment, both flagged.
5. After the wedding
The booking export, the resort invoice and the vendor invoices go in one folder. The couple's 1099-K question is a one-page reconciliation; the planner's fee income is on its own ledger. The next wedding is this one, duplicated.
Final Thoughts
Planners get paid on time when the guests' money and the planner's fee are two different things, each with its own ledger, and when the guest side runs on a booking page rather than a spreadsheet. Set the packages to the block, the schedule to the cut-off, and the fee to a separate line — then the next wedding is a template, not a rebuild. For the operational side of a large block, see managing a 100-guest wedding block; for the website side, the best destination wedding websites.
Run every client wedding on one page. Start free on SquadTrip — deposits, instalments, BNPL, rooming list export, and a planner dashboard.








