Troubleshoot BP fuel sync

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

Check connection activation, dates, mapping and card allocation.

What this guide helps you do

Check connection activation, dates, mapping and card allocation. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.

Follow these steps

1. Run Test.
2. Check connection active and interval.
3. Check transaction_id and transaction_at mappings.
4. Check lookback dates.
5. Check fuel-card aliases/allocations.
6. Run Sync Now and inspect result.

Fields and options

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

Rules and limits

• Use the supported screen and permission; do not bypass validation or edit database records directly.

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.

Related guides