After a customer pays a deposit, staff need the agreed total, the amount received and the date the balance is due. If the group size changes, the updated amount must remain connected to the original booking.
Build that record before opening sales for a retreat, private event or training program.
Make outstanding payments visible
Keeping future payments only in notes on an order makes missed balances and refunds harder to explain. Distinct states show whether terms are still proposed, a deposit has been received or a balance is overdue. The following states illustrate one possible workflow; when a place becomes confirmed depends on the agreed booking terms.
| State | Meaning | Typical next action |
|---|---|---|
| Draft | Terms not accepted | Review total and schedule |
| Deposit due | Initial payment outstanding; reservation follows the agreed terms | 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 |
| Canceled/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 installment terms behind a generic checkout label.
Check the payment workflow in Gomry
Gomry's standard approval flow preauthorizes the ticket payment at the request and captures it on approval; rejecting the request releases the hold. That is a full ticket-price approval, not a deposit agreement. Buy-now-pay-later is also available in payment settings, but it is a provider payment option rather than an in-person POS installment arrangement.
A deposit arrangement needs one record of the agreed total, payments received, due dates and balance. If the business uses a separate invoicing system, keep its booking reference with the Event and participant records so staff can reconcile the agreement and any refunds.
For corporate purchase orders or invoices with payment terms, retain the accounting workflow that produces the invoice. The private-booking guide covers the handoff from quote to confirmed event; the retreat guide adds room allocation and participant details.
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.
Use one upcoming booking to test the agreed total, deposit, changed headcount and final balance. Confirm how each step will be recorded before sending the customer a payment schedule.