Start with a transaction that needs explaining. Reconcile the receipt, statement, vehicle assignment and journey timeline before assigning a cause. A good investigation leaves a reviewer able to reproduce the finding from the original records.
Build the evidence trail for each flagged transaction
Record the card transaction ID, merchant, amount, litres, product and original timestamp. Attach the receipt or identify it by a document reference. Look up the card-to-vehicle assignment valid at that time, then check the dispatch sheet and the tracking event for the matching vehicle. Keep the timezone and coverage dates visible.
Use a separate field for each source. When a tracker entry is missing, record the gap and check the trip sheet or other available records. When a receipt is illegible, keep its image and request a better copy. Treat the field as missing until the evidence arrives.
What each flag should prompt you to check
- Two similar charges. Compare authorisation IDs, merchant references, posting dates and any reversal. A duplicate export row and two separate settled charges produce different outcomes.
- Card used away from the expected route. Confirm the card assignment and check for a documented vehicle swap, detour or approved refuelling stop. Review the coverage of the tracker export.
- Unexpected product or volume. Read the receipt line items and confirm the recorded fuel product, asset, and capacity relevant to the transaction. Identify authorised refuelling of other equipment separately.
- Sudden increase in consumption. Rebuild the full-to-full interval and check whether terrain, payload, idling, a missing receipt or a suspect odometer changed the comparison.
Worked example with two R1,296 entries
Monday's review flags two charges of R1,296 for the same card at the same merchant, 11 minutes apart. Both list 54 L. The first record is a charge with authorisation reference A175. The second record has reference A176. The receipt file contains only A175. The next statement line contains a R1,296 credit referencing A176.
Link the charge and credit in the working file. The two debits and the credit net to R1,296. The fleet administrator asks the merchant for the missing document and notes that one charge remains in the ledger after the reversal. If the credit had referenced a different transaction, the second charge would stay open with its own owner and due date.
Give the reviewer one neutral question
Write a question that names the record and evidence required. For example, “Please match card authorisation A176 to its original charge, receipt or credit confirmation for the Tuesday close.” That provides a workable action and a closure test. Avoid attaching driver names to broad dashboards when vehicle or transaction identifiers are enough to route the check.
Use three stages in the register. Flagged means the rule detected a pattern. Explained means supporting records account for it, such as a confirmed reversal. Escalated means a material discrepancy persists after review and goes through your organisation's authorised process. Record who verified the evidence and when.
Reduce the next month's investigation load
Reconfirm the card-to-vehicle mapping after a replacement or vehicle move. Keep the original statement export and the receipt reference in the same close folder. Review a short list of open exceptions every week and track their age. Repeated missing receipts usually call for a source or handover fix, with a designated owner and a date to verify the improvement.
Use the Basic Fuel Record workbook to capture the inputs and the odometer discrepancy guide when distance looks unreliable. The sample report shows how to present the evidence and next question in one register.