Understand job payment statuses
Track invoice/payment progress separately from delivery status.
Exact navigationAdmin Area → Courier & Logistics → Jobs → Open job → Finance
What this guide covers
Track invoice/payment progress separately from delivery status. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.
Exact step-by-step process
- Open Admin Area → Courier & Logistics → Jobs → Open job → Finance.
- Review the source record and choose the supported action.
- Save or submit once, then reopen the record and verify the result.
Fields, choices and supported possibilities
not_invoicedNo linked invoice has been created.
draftLinked invoice is draft.
sentInvoice sent/open for payment.
part_paidSome payment recorded.
paidFully reconciled as paid.
overdueInvoice overdue.
disputedOperationally disputed.
Code-backed validations and workflow rules
- Invoice status hooks and payment hooks reconcile the job payment state.
- Do not change delivery status merely to change payment status.
Expected result and verification
- 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.