Customer work, connected.

Help & supportMyAccount
Fleet and vehicle compliance

Track hire-and-reward cover expiry

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Maintain the monitored hire-and-reward cover date and act before it expires.

Audience: Courier operations staffPermission: Courier: Manage complianceModule v2.0.0
Jump to steps
Where to goAdmin Area → Courier & Logistics → Vehicles → Open vehicle → Compliance

What this guide helps you do

Maintain the monitored hire-and-reward cover date and act before it expires. 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 the vehicle.
  2. Enter or verify the hire-and-reward cover expiry date.
  3. Save the vehicle.
  4. Check Compliance alerts and renew the evidence before expiry.

Fields and options

hire_reward_expirySaved date used by vehicle compliance monitoring and automation.

Rules and limits

  • When the monitored hire-and-reward cover date is in the past, automation can mark the vehicle expired and unavailable.
  • A future date alone does not prove the evidence is valid; retain and verify the source document through the organisation’s process.

Check 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.

Search the platform, integrations and practical Help Centre guides.

Press Esc to close.Browse every page