Jobs, stops, dispatch and status control

Understand job payment statuses

Track invoice/payment progress separately from delivery status. 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.

Audience: Courier operations staffPermission: Courier: ViewModule v2.0.0
Jump to steps
Where to goAdmin Area → Courier & Logistics → Jobs → Open job → Finance

What you’ll accomplish

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.

Follow these steps

  1. Go to Admin Area → Courier & Logistics → Jobs → Open job → Finance.
  2. Check the source record and choose the supported action.
  3. Save or submit once, then reopen the record and verify the result.

Fields and options to review

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.

Rules the system enforces

  • Invoice status hooks and payment hooks reconcile the job payment state.
  • Do not change delivery status merely to change payment status.

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.