These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Fuel Management System
- Features
- Purchase analysis
Purchase analysis
Compare purchase activity by vehicle, card reference and site while keeping units and review outcomes visible.
OverviewMy load follow-up×
Fuel Management System · Purchase analysis
New
My load follow-up
Loads
| Record number | Subject | Organization | Lane | Planned departure | Promised delivery at | |
|---|---|---|---|---|---|---|
| LDS-92515 | Draft lds-501 | ORG-2123 | LNE-881 | 11 Oct | 17 Oct | |
| LDS-20681 | Planned lds-299 | ORG-3212 | LNE-584 | 13 Oct | 16 Oct | |
| LDS-53530 | Dispatched lds-594 | ORG-6322 | LNE-586 | 12 Oct | 19 Oct | |
| LDS-75004 | In transit lds-183 | ORG-8470 | LNE-282 | 15 Oct | 19 Oct | |
| LDS-40210 | Delivered lds-391 | ORG-9307 | LNE-636 | 04 Oct | 08 Oct |
6 of 6 records
Draft lds-501Loads · LDS-92515
DraftOrganizationORG-2123
LaneLNE-881
Planned departure11 Oct
Promised delivery at17 Oct
Revision820
What you can do
Read purchase patterns with their operating context
The Transport Supervisor and Auditor review purchases across an agreed period to identify entries that need explanation. Vehicle, card reference, site and fuel type provide useful groupings. Keep the review state visible so Draft or Rejected entries are distinguishable from purchases the team has approved.
A useful comparison starts with consistent dates and quantity conventions. Review gallons separately from other recorded volume conventions and compare unit costs within the same fuel type, quantity unit and confirmed receipt currency. Inspect odometer readings in date order for the same vehicle when a purchase sequence looks unusual.
How the work is organized
- Period selection. Agree the purchase date used for the review and include the intended states. The supervisor should be able to explain why an entry appears in the reviewed set and whether it still needs a decision.
- Comparable records. Group purchases by vehicle, card reference or site with fuel type and units visible. Open the individual entries before combining quantities that came from different capture conventions.
- Exception investigation. Use an unexpected quantity, repeated card reference or odometer sequence as a starting point for examining receipts and operating work. Record the follow-up decision with its source reference and rationale.
What to agree during setup
Agree the review period and whether the team uses Approved purchases, Completed purchases or another clearly defined set. Reconcile imported entries to the same date and quantity rules before comparing them with new purchases. Check how the displayed purchase amount is calculated against the source quantities and unit cost during the pilot. Confirm the currency from the receipt and agree its treatment with accounting before combining monetary amounts.
Define which discrepancies need a supervisor’s decision and who gathers the supporting evidence. The Dispatcher can correct a purchase under the agreed procedure, while the App Administrator maintains fleet identity and state. Keep the Auditor’s role focused on reading the evidence and reporting a concern to the responsible person.
Check the handoff on an actual case
The supervisor reviews a week’s diesel purchases for a truck and finds two entries using the same card reference at different sites. The reviewer opens the records, checks the dates and odometer readings, then follows the receipts and related loads. The evidence may explain separate legitimate purchases or identify a record that needs correction.
Now include a receipt priced in another currency and review its cost separately until accounting confirms a common monetary basis. Also include an entry imported with a different volume convention. Keep it distinguishable until the quantity basis is reconciled, and explain its treatment in the period review. Ask the Auditor to follow a returned decision back to the purchase and identify the person responsible for the next action. The review should produce an explainable follow-up, with the supporting record available to the next shift.
What your team sees
- Approved fuel purchases — Approved and Completed purchases with quantity, displayed amount and odometer information for the period review.
- Fuel decision history — The recorded outcomes that explain how purchases reached their reviewed state.
- Operations Overview — A ranked exception queue across dispatch, fleet upkeep and evidence, with linked-record detail.
Follow the work through
Run period review and follow-up, then use receipt correction for entries that need a fresh decision.
What it keeps track of
Data model- Fuel transactions
- Fuel and energy purchases recorded per asset
- Vehicles
- Powered units and trailing equipment in the fleet
- Loads
- Planned and executed transport loads
- Review decisions
- Approval, rejection and escalation decisions on records
- Record attachments
- Documents, photos and signature evidence attached to records
- Operation receipts
- Recorded operational outcomes awaiting verification
Who uses it
Permissions- Transport Supervisor
- , Auditor, Dispatcher.
- The supervisor leads the review, the Auditor examines the record trail, and the Dispatcher resolves purchase questions under the agreed procedure.
Set up Fuel Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.