BP fuel connection, fuel cards and reconciliation

Create a fuel card

Add a masked card alias and allocate it to a driver/vehicle.

Audience: Courier operations staffPermission: Courier: Manage integrationsModule v2.0.0
Exact navigationAdmin Area → Courier & Logistics → Settings → BP Fuel → Fuel Cards → Add

What this guide covers

Add a masked card alias and allocate it to a driver/vehicle. 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

  1. Enter a clear card alias.
  2. Enter the card number through the protected field.
  3. Select driver and/or vehicle allocation.
  4. Save.
  5. Verify only the masked last four digits are displayed.

Fields, choices and supported possibilities

AliasRequired.
Stored display**** plus the final four digits.
AllocationDriver and/or vehicle references.
ActiveControls matching/use in sync.

Code-backed validations and workflow rules

  • The full card number is not retained as a visible value.

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.