What should a wedding vendor payment checklist include?
Track the reusable vendor record, wedding engagement, contract currency, total fee, deposit schedule, approved scope changes, final balance, approval owner, payout status, payment reference, and final event cost. The goal is to close the wedding with every vendor payment explainable without searching email or bank transactions.
- Use one reusable payee record across weddings
- Track deposits and final balances as separate payment stages
- Keep contract currency visible for destination weddings
- Record approved changes separately from the base agreement
- Reconcile completed vendor cost back to the wedding
Wedding vendor payments become difficult when the planner has to remember what happened instead of reading it from the payment record. A clean process should survive team handoffs, destination currencies, deposits, last-minute scope changes, and the final rush before the event.
Before the vendor is booked
Create or reuse the vendor record and confirm the commercial basics:
- legal/business payee name,
- primary contact,
- wedding or client,
- service category,
- contract currency,
- total contracted fee,
- deposit amount and due date,
- final balance timing,
- expense or change-order rules,
- internal payment owner.
If the vendor has worked another wedding, reuse the payee record but create a new wedding-level engagement.
After the contract is signed
Enter each payment stage separately. Do not use one generic “amount due” field for the whole relationship.
For example:
- booking deposit,
- second milestone,
- final pre-event balance,
- approved post-event adjustment.
The free wedding vendor payment schedule is built around this model.
During planning
Keep approved scope changes visible. If floral scope increases by $1,200, do not silently overwrite the original contract amount without an audit note.
Record:
- original contract,
- approved change,
- date approved,
- approving person,
- revised payment obligation.
This is especially important for destination weddings where FX changes can otherwise be confused with scope changes.
Before each payment
A payment should be ready only when the team can answer four questions:
Who are we paying?
Confirm the payee record and payment destination.
Why are we paying now?
Identify the deposit, milestone, final balance, or approved adjustment.
How much is approved?
Use the contract currency and approved amount, not a number copied from an email thread.
Who approved it?
Keep the approval owner and date on the payment record.
After payment is sent
Record the payment status and reference immediately.
Useful statuses include:
- approved,
- processing,
- paid,
- failed,
- returned,
- cancelled.
A failed payment is not reconciled simply because a bank transfer was attempted.
After the wedding
Close every vendor engagement by reconciling:
- approved amount,
- amount actually paid,
- payment reference,
- outstanding exceptions,
- final wedding vendor cost.
That actual cost should feed the post-event profitability review.
Kelvaro's wedding vendor payment software turns these spreadsheet fields into a reusable operating workflow.
FAQ
Should wedding planners track vendor deposits separately from final balances?
Yes. Separate payment stages make due dates, approvals, outstanding obligations, and reconciliation much easier to understand.
How should destination wedding vendors be tracked?
Keep the contract currency, payment stage, approved amount, payout reference, and wedding context together. Cross-border tax and legal treatment should be reviewed separately based on the actual payee and engagement.
Can the same vendor record be reused across weddings?
Yes. Reuse the core payee record while keeping each wedding's scope, contract, payment schedule, approvals, and cost separate.