Wedding vendor deposits are rarely one standard percentage. The amount depends on the vendor, the contract, the date and the market. What matters operationally is knowing what you have committed, what remains due and when each balance becomes payable.
If you are trying to plan cash flow before booking vendors, the ranges below are useful starting points. They are not fixed rules: your signed contract is the source of truth for every real payment.
Typical wedding deposit amounts by vendor
Recent wedding-planning guides commonly place many booking deposits somewhere around 20% to 50% of the contract value, but the ranges overlap and individual contracts vary considerably. Some caterers and other suppliers use a flat booking amount instead of a percentage.
| Vendor | Typical booking range | What to check |
|---|---|---|
| Venue | About 20–50% | Whether later instalments are required before the final balance. |
| Caterer | About 20–40%, or sometimes a flat deposit | When the final guest count locks the balance. |
| Photographer / videographer | About 25–50% | Whether the booking payment is described as a non-refundable retainer. |
| DJ / band | About 20–50% | Final-payment date and any overtime terms. |
| Florist / decor | About 20–50% | When quantities and design choices become final. |
| Wedding planner | Often around 25–50% | Whether the remaining fee is split into instalments. |
| Cake | Often around 25–50% | Final headcount, delivery and setup charges. |
| Hair / makeup | Varies | Whether trials and wedding-day services are billed separately. |
| Transport | Often around 20–50% | Minimum hours, final balance and overtime. |
Published 2026 guides show why a single “normal deposit” number is misleading. Some put venue deposits around 25–50%, while Spain-focused guidance often shows roughly 20–30% for venues and similar starting ranges for several other suppliers. The useful conclusion is not that one percentage is correct; it is that you need a payment schedule built from your actual contracts.
Wedding vendor deposit schedule example
Imagine a wedding with five major vendors already booked. A useful payment view does not just show the total budget. It shows what has already left your account and what will leave it next.
Example payment schedule
- Venue
- €8,000 total · €2,000 paid · €6,000 remaining · final balance due 30 days before.
- Catering
- €7,500 estimate · €1,500 paid · final amount depends on confirmed guest count.
- Photography
- €2,400 total · €720 retainer paid · €1,680 due two weeks before.
- Florist
- €1,800 total · €540 paid · €1,260 due after final design approval.
- DJ
- €1,200 total · €300 paid · €900 due before the wedding.
The numbers above are hypothetical. The useful part is the structure: total cost, amount already paid, remaining balance, next due date and any condition that can change the final amount.
What to track for every wedding vendor
1. Contract total
Record the agreed total or the latest estimate. If the final amount depends on guest count, hours or quantities, make that visible instead of pretending the number is fixed.
2. Deposit or retainer paid
Store the amount and the date it was paid. Do not rely on the bank transaction as your only record.
3. Remaining balance
The amount still committed matters more than the amount already spent when you are planning the next few months of wedding cash flow.
4. Next payment due date
This is the field that turns a vendor list into a useful operating system. A balance without a date is easy to forget.
5. Payment status
Keep the states simple: not paid, deposit paid, part paid and paid in full are usually enough.
6. Contract and payment terms
Keep the contract attached or linked to the vendor record and note anything operationally important, such as refund terms, postponement rules or a guest-count deadline.
How to track wedding vendor deposits in Notion
You do not need a separate page for every payment. A Vendors database can hold the supplier, contract value and payment status, while a related Payments database handles individual due dates when a vendor has several instalments.
| Property | Purpose |
|---|---|
| Vendor | Name of the supplier. |
| Category | Venue, catering, photography, flowers, music and so on. |
| Contract total | Total agreed or current estimated cost. |
| Paid | Amount already paid. |
| Balance | Amount still outstanding. |
| Next due | Next payment deadline. |
| Status | Not paid, deposit paid, part paid or paid. |
| Contract | File or link to the signed agreement. |
If one vendor has several instalments, create each payment as its own record and relate it back to the vendor. Then a view filtered to unpaid payments and sorted by due date becomes your payment calendar.
That separation also prevents a common mistake: mixing the vendor relationship with the individual transactions. The vendor is one thing; each payment deadline is another.
Common wedding payment tracking mistakes
Tracking only the total wedding budget
A €25,000 wedding does not mean €25,000 is due at once. Cash-flow pressure comes from when deposits and balances fall, so dates matter as much as totals.
Assuming every vendor uses the same deposit percentage
Published ranges are useful for rough planning, but they are not contract terms. Record the actual figure as soon as you receive the proposal.
Forgetting the final guest-count dependency
Catering and some venue costs may change when the final headcount is confirmed. Keep the deadline and the variable amount visible together.
Leaving payment dates inside PDFs and emails
The contract should remain the source of truth, but the due date should also appear in the system you actually review. Otherwise the information is technically recorded and operationally invisible.
Sources and notes
The ranges above are planning references rather than official standards. They were cross-checked against current 2026 wedding-payment guides from InviteCount, Organiser Son Mariage and Mi Web de Boda. Your signed vendor contract always takes priority over a general range.