Published: September 14, 2026.
Fuel card exports, receipts, odometer entries, and trip records often reach the office through different systems. A source register shows what was received and what still needs review before a qualified carrier or tax professional makes filing decisions.
Inventory sources before matching
List each approved system, report name, covered period, extraction time, file link, and responsible owner. Preserve raw exports. Record filters and timezone settings used during extraction so another authorized person can reproduce the file.
Keep reported values distinct
Store transaction amount, quantity, unit, jurisdiction, vehicle, driver, merchant, and odometer as supplied. Normalize a copy for matching while retaining the original field and rule. A corrected receipt or reassigned vehicle becomes a dated event rather than an overwrite.
Route exceptions by type
Useful administrative labels include missing receipt, unreadable receipt, unmatched transaction, unit conflict, jurisdiction conflict, duplicate candidate, and owner review required. A label should describe the record problem, not a tax conclusion.
Administrative staff may request missing evidence and assemble an exception packet. They should not determine taxability, allocate mileage, select a jurisdiction, amend a return, or approve a filing unless separately authorized and qualified.
Reconcile completeness
At period close, compare expected source files with received files. Count records that match, remain open, were excluded under a documented rule, or changed after review. Keep late arrivals tied to the period and log the owner response.
Test the register
Select transactions with clean matches, missing sources, duplicates, and unit conflicts. A second reviewer should reproduce the status from the stored evidence and identify which decisions remain with the carrier or adviser.
Working standard
The register provides a traceable input inventory and a visible exception population. It does not calculate or certify tax liability.