Create a driver settlement
Aggregate completed-job driver pay for a date range. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goAdmin Area → Courier & Logistics → Finance → Settlements → Create
What you’ll accomplish
Aggregate completed-job driver pay for a date range. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.
Follow these steps
- Select the driver.
- Enter From and To dates.
- Create the settlement.
- Go to the settlement and compare included completed jobs and amounts.
- Keep it draft until reviewed.
Fields and options to review
Date rangeUsed to select completed jobs for the driver.
Initial statusdraft.
Lifecycledraft, approved, paid or cancelled.
Rules the system enforces
- Use valid dates and the intended inclusive operational period.
- Do not include non-completed work by manual manipulation.
How to confirm it worked
- The source record, status/history and any downstream notification, provider, POD or finance record should agree after the action.
Security, audit and operational checks
- Use the exact record and least-privilege role before changing any state.
- Verify the saved record after every action; a browser message alone is not evidence that every downstream step completed.
- Use protected document and image routes rather than exposing server filesystem paths.
- Keep customer, driver, provider, financial and credential data within the authorised workflow.
- For provider, finance, employment, transport and compliance decisions, follow the organisation’s authorised professional process.
Do not bypass the code flowDo not force database values, invent a status, mark a job completed without signed POD evidence, or expose encrypted credentials to make a screen appear successful.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.