Reviewed purchases retain their source identity, amounts and driver or vehicle mapping.
Fuel integration
BVD + Yolda
Fuel source setup and report review; API readiness depends on the exact provider contract.
What it feeds
Eligible propulsion fuel evidence supports IFTA review; missing units or receipts remain exceptions.
Who carries the cost comes from the pay agreement in force when the purchase happened — never a per-row checkbox.
How the data arrives
Reads BVD Petroleum card purchases by token or portal login.
How to connect it
Start a Yolda workspace, open Integrations, and pick BVD. You authorize the connection with your own BVD credentials — Yolda never stores them in a client-visible record. From there the data flows into dispatch, accounting, and IFTA on its own. See every connection on the integrations page.
Questions
Does Yolda work with BVD?
Yolda has a provider interface for BVD. Fuel source setup and report review; API readiness depends on the exact provider contract. Availability requires the correct provider product, authorized account access and source-data verification. A report import does not establish a working API connection.
What needs review before using BVD data?
Verify the source account and supported delivery method, then resolve driver and vehicle identities, ownership, units and financial differences. Unmatched or changed records require review before downstream use. Finalized statements retain their frozen records.