Vendor installments and payment history

Open a wedding’s Budget → Vendor installments & payment history. Choose a booked vendor, confirm the currency and agreed total, and split it into dated installments. Installments must add up to the exact agreed total. Review the plan against the amount on the linked vendor booking before confirming it.

This is a private operational ledger for the wedding’s owning business. It does not move money, send reminders, charge a card, create a business expense, change an invoice or silently overwrite another budget worksheet. Other businesses invited to the same wedding do not inherit access.

Record the actual payment

For example, a florist’s $1,000 agreement has a $300 deposit and a $700 balance. Record a $200 check against the deposit. The deposit shows $100 remaining; the vendor’s total shows $800 remaining. Recording that check twice by retrying the same interrupted request creates one entry.

Choose the paid installment, actual amount, date and method. Include an explanatory note and optional reference, then confirm that you checked the record against the real payment. Do not save bank login details or sensitive account credentials in these notes.

If a payment exceeds an installment, the schedule shows an unapplied credit warning. The vendor’s overall balance reflects net recorded payments, while installment due dates remain separately visible. Review the allocation before paying another installment; no automatic transfer between installments is inferred.

Due dates and categories

Filter by category, paid installments, overdue installments or installments due in the next 30 days. The as-of date defaults to the business timezone. Currency totals are kept separate. The top-level totals describe all saved vendor schedules; the installment list follows the selected filters.

A changed vendor cost or booking status adds a review warning. Saving a new reviewed schedule retains its earlier history. Installments with payment history cannot be removed, and a schedule with payments cannot change currency. Their due dates and agreed amounts can be explicitly reviewed and adjusted.

Refunds, corrections and recovery

Open the original payment in retained history. Choose Refund received from vendor for money actually returned, or Correct an erroneous payment record when the original recording was wrong. Enter the amount and reason. A linked adjustment cannot exceed the original payment’s unadjusted amount or precede its date.

Original entries remain immutable; refunds and corrections add linked records. Refunds reduce net paid amounts, so confirm any corresponding contract reduction separately. These records do not initiate a refund or imply that a provider has processed one.

If confirmation is interrupted, retry the unchanged request. Changed schedule revisions require a fresh review. History is paginated in groups of 50; the planner and API retain prior entries. Up to 200 vendor schedules per wedding and 50 installments per schedule are supported.

Keep a vendor booking with retained payment history instead of deleting it. Update its status and review its remaining obligation. Vendor schedules and payment entries are preserved by database restrictions even when an old deletion shortcut is used.