Fuel integration

EFS + Yolda

Fuel source setup and report review; API readiness depends on the exact provider contract.

Reviewed purchases retain their source identity, amounts and driver or vehicle mapping.

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.

EFS and Fleet One cards, read from EFS's web service. Feeds Fuel & Tolls and IFTA.

Yolda reads your EFS and Fleet One card purchases every 4 hours, starting at your company's midnight.

  1. Ask EFS for a web service login
  2. Open EFS in Yolda
  3. Enter the login EFS sent
  4. Check that it works

Read the full EFS setup guide, with every screen and setting.

How do I connect EFS to Yolda?

1. Ask EFS for a web service login. 2. Open EFS in Yolda. 3. Enter the login EFS sent. 4. Check that it works. The full guide, with each screen and setting, is at https://yolda.ai/integrations/guides/fuel-efs.

Does Yolda work with EFS?

Yolda has a provider interface for EFS. 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 EFS 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.

Run EFS and a TMS that actually reads it.

Start Free Trial