Approve payment plan overrides
Review requests to deviate a specific booking from the standard payment plan — extend due dates, waive late fees, or restructure instalments.
You need the Admin role (or higher) to complete the steps on this page.
A payment plan override is a per-booking variation from the standard plan — for example, pushing one instalment out by 30 days, waiving a late fee, or restructuring the remaining tail. Sales raises the request; an approver with booking.approve signs off.
Overrides are reversible — rejecting an override snaps the schedule back to the original plan. Approvals are not — once applied, further changes need a fresh override.
Open the queue
Step 1: Open Approvals → Payment plan overrides
The queue shows every pending override with the booking, the requested change and the submitter.
payment-plan-overrides-01.png
Review the diff
Step 1: Click an override
The preview shows the current schedule side-by-side with the requested schedule. Changes are highlighted — pushed dates in amber, waived rows in rose.
Step 2: Read the justification
The submitter must have filled a justification. If the justification is thin or missing context, use Reject with a note asking for more detail.
Approve or reject
Step 1: Click Approve
The new schedule replaces the current one on the booking. The customer's dunning schedule is recomputed.
Step 2: Click Reject
The override is closed. The current schedule is unchanged. The submitter sees the reason.
Approved overrides change the booking's receivable aging immediately. If a 30-day push covers the current month-end, the "Overdue >30 days" bucket in the aging report will drop. Communicate accepted overrides to Finance.
What's next
- Payment plans — set up the standard plans.
- Payments received — record collections against the new schedule.