Understand BP transaction mapping
Map external transaction fields into fuel expense/reconciliation records. 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.
Where to goAdmin Area → Courier & Logistics → Settings → BP Fuel → Mapping
What you’ll accomplish
Map external transaction fields into fuel expense/reconciliation records. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.
Follow these steps
- Enter valid JSON mapping.
- Include transaction_id and transaction_at.
- Map card, amount, VAT, litres, station, currency and vehicle/driver identifiers where supplied.
- Save and test.
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
- Invalid JSON or missing required mapping keys is rejected.
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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.