Finance, settlements, expenses and accounting

Post a job accounting journal

Follow this guide to create the module journal for completed job revenue/cost effects. 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: Manage financeModule v2.0.0
Jump to steps
Where to goAdmin Area → Courier & Logistics → Jobs → Open completed job

What you’ll accomplish

Create the module journal for completed job revenue/cost effects. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.

Follow these steps

  1. Check the job is completed and commercial values are correct.
  2. Allow the completion/accounting workflow to post the journal.
  3. Go to Finance → Journals/Ledger.
  4. Check source type, source ID, job ID, memo, currency, debit and credit lines.

Fields and options to review

This action uses the values already stored on the selected source record. Review that record before continuing.

Rules the system enforces

  • Journal posting is performed by the accounting service.
  • Duplicate/source protection should be respected; do not add balancing entries manually without reconciliation.

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.