A wedding planner should connect the booking retainer and every later invoice to one scope version, couple record and event date. The payment schedule should follow real planning commitments, while the final operational ledger shows what was invoiced, confirmed, changed and still due.
This workflow is for independent planners billing a multi-month service. Its original asset is a six-state wedding billing ledger that separates planner fees, client-approved extras and vendor money instead of treating every incoming payment as one balance.
Separate Three Money Lanes
Keep the planner's professional fee, reimbursable expenses and money owed directly to venues or suppliers in separate lanes. If you collect or pass through vendor funds, document who contracts with the vendor, who owns the funds and how refunds are handled; local accounting, tax and client-money rules can apply.
| Lane | Example | Billing control |
|---|---|---|
| Planner fee | Full-service planning package | Retainer plus agreed milestones |
| Approved extra | Added design or coordination hours | Written change approval before invoice |
| Vendor cost | Venue, florist or rentals | Separate responsible party and evidence |
This is an operational model, not legal, tax or accounting advice.
Tie Milestones to Commitments
Avoid copying a universal percentage schedule. A useful plan might invoice at contract signing, after a defined vendor-booking phase and before final coordination begins. For a €6,000 planning fee, an illustrative 30/40/30 schedule would be €1,800, €2,400 and €1,800. Those figures are an example, not an industry standard.
For every stage, name the due date, amount, work activated, cancellation treatment and prerequisite approval. The event date alone is not enough: the planner may commit substantial work months before the wedding.
Use a Six-State Wedding Billing Ledger
Track each amount as scheduled, invoiced, payment pending, confirmed, credited/refunded or overdue/escalated. Record invoice ID, scope version, payer, couple, event, due date, currency, provider transaction, confirmed amount and remaining planner-fee balance.
Never mark a milestone paid from an email, screenshot or browser return page. Confirm it in the connected payment provider and match the transaction to the invoice. Preserve later credits and changes as new events instead of rewriting the earlier invoice history.
Freeze Scope Before Each Invoice
At booking, define package, meeting allowance, vendor categories, event coverage, travel, exclusions and cancellation terms. Before a later milestone, issue a short scope checkpoint: original work, approved changes, completed stage and next stage.
If guest count, venue count, event days or design responsibilities expand, approve the impact before invoicing. Do not bury a client-approved extra in the final balance where neither side can reconstruct it.
Rehearse Reminders and Exceptions
Test the sequence for a paid retainer, pending bank payment, failed card, duplicate payment, date move, planner cancellation, reduced scope and approved extra. Reminder copy should identify the invoice and due date without exposing private event details in a subject line.
A signed contract and a payment each solve different proof jobs. Keep the agreed scope and change approvals beside the ledger; do not imply that checkout alone creates complete wedding-planning terms.
Build the Workflow in PayRequest
Use PayRequest invoicing for the planner fee and connect each invoice to the customer and event record. Where the same defined service renews automatically, billing automation may fit; a wedding milestone schedule normally remains project-specific.
Start with one client record and one verified retainer invoice. Add later milestones only after the scope, date and money lane are unambiguous, then measure confirmed payments and overdue resolution rather than sent-email counts.