A deposit is not just an amount due today. It is the start of an obligation: total price, future instalments, deadlines, payment state, changes, refunds, and customer notices. Retreats, private events, training cohorts, trips, and other high-value experiences need that record when full payment at checkout creates unnecessary friction or cash-flow risk.
A payment plan is a state machine
Treating future payments as notes on an order leads to missed balances and confusing refunds. A robust plan moves through explicit states.
| State | Meaning | Typical next action |
|---|---|---|
| Draft | Terms not accepted | Review total and schedule |
| Deposit due | Place not secured yet | Pay before deadline |
| Active | Deposit paid, future amount due | Monitor scheduled payments |
| Past due | Expected payment failed or is late | Retry, contact, or apply policy |
| Paid | Full agreed amount collected | Deliver experience |
| Changed | Scope or dates altered | Recalculate with audit trail |
| Cancelled/refunded | Obligation ended | Reconcile retained and returned amounts |
Two sample schedules
For a $1,500 booking, a 25% deposit is $375 and leaves $1,125. That balance could be due once or split into three payments of $375.
For a $4,800 private event, a fixed $1,000 deposit leaves $3,800. If the final balance changes with headcount, the quote should state the calculation and the date when the count becomes binding.
These figures illustrate arithmetic only. Deposit size, cancellation terms, taxes, credit rules, and payment authorization require policies appropriate to the business and jurisdiction.
What the software must do
Preserve the agreed terms
Store the original total, schedule, policy version, and acceptance. Changes should create a visible adjustment rather than overwrite history.
Make failures actionable
A failed charge should have a reason category, next retry, customer notice, and human owner when automation cannot resolve it.
Reconcile money precisely
Finance should trace each payment, refund, fee, dispute, and net payout back to the booking and plan.
Protect customer trust
Before payment, show amount and timing. After payment, send a clear receipt and remaining balance. Do not hide material instalment terms behind a generic checkout label.
Where Gomry fits
Gomry is relevant when scheduled payments belong to a wider experience record with bookings, tickets, memberships, customer data, and mobile operations. Confirm the exact deposit and instalment configuration available for your account before publishing a customer promise.
A standalone invoicing system may be enough for a small number of bespoke corporate events, especially when purchase orders and accounts-receivable approval dominate the workflow.
Frequently asked questions
Is a deposit refundable?
That depends on the agreed policy and applicable law. The software should represent the rule accurately, not decide it.
Should cards be charged automatically?
Only with valid authorization, clear notice, appropriate payment setup, and a compliant process for the relevant market.
What happens when the total changes?
Issue an adjustment that shows the new total, payments already made, amount remaining, and reason. Preserve the prior agreement.
How should overdue balances be handled?
Define retry timing, communication, grace period, escalation, and the effect on the reservation before launching the plan.