AS24 transactions, attached to the order that burned them.
The AS24 portal will tell you what the fleet spent. It cannot tell you what a load cost, because it has never heard of your loads. That last step, matching a transaction to the job that caused it, is the one that turns a fuel bill into a margin.
A direct partner API connection, not a monthly CSV.
VIGILFleet talks to the AS24 partner API with your own key, on a schedule staggered per company so a large fleet's sync does not queue behind someone else's. Keys are encrypted at rest, and a carrier with one contract and a fuel card reseller with several are both handled: each contract has its own key, environment and sync schedule.
- Hourly sync per contract, plus a nightly reconciliation pass
- Production and integration environments, so card operations can be tested safely
- Multiple AS24 contracts under one company, each synced separately
- Backfill on connection, so the history arrives with the integration
Diesel, AdBlue and tolls are counted separately.
This sounds like a detail and is not. AdBlue at around half a euro a litre averaged into diesel at around one and a half quietly drags the fleet's price per litre down, and every cost per kilometre calculated from it is then wrong in the same direction for months. VIGILFleet classifies each product on the transaction and keeps them apart.
- Diesel priced and averaged on its own, per truck
- AdBlue tracked as its own cost line
- Télépéage and toll products routed to toll cost rather than fuel
- Transactions matched to the truck by normalised plate, and to the order by time
What it becomes once it is matched.
A transaction attached to an order is no longer an expense line, it is part of a margin. By the time accounting opens the invoice, the fuel and the tolls for that job are already on it.
- Fuel and toll cost per order, ready before the invoice is raised
- Revenue, fuel, tolls, driver cost and margin per truck
- Euro per kilometre by truck and by month
- Fuel card management, including blocking and unblocking a card
One thing worth knowing before you connect: an AS24 card number is not unique on its own. It is reused across card types, so the identity has to be the contract, the card and the type together. We match on all three, which matters the day you are billing a subcontractor.
Questions people actually ask.
- What do you need to connect AS24?
- Your AS24 partner API key. It is stored encrypted, and if you run several AS24 contracts each one is connected separately with its own schedule.
- How far back does the history go?
- A backfill runs when the integration is connected, so you do not start with an empty fuel history.
- Are tolls included, or only fuel?
- Both. Toll and Télépéage products are classified as toll cost and kept apart from diesel and AdBlue.
- We are a fuel card reseller, not just a carrier. Does that work?
- Yes. Several AS24 contracts can sit under one account, each with its own key and sync, which is what a reseller billing subcontractors needs.
- Do you support other fuel cards?
- AS24 is the direct API integration today. Other providers are loaded from their statement files. Ask on the call and we will tell you plainly which of the two your card would be.
Read next
See your own fuel data on your own orders.
Bring an AS24 key to a 30 minute call and we will backfill it live and show you the margin on a load you already ran.