The Chishtian Logistic case study
From assigned Mile to approved trip cost: one driver-to-finance trail.
How TCL Mile Expenses gives a driver one active-trip view for route events, petty cash and road expenses while Odoo keeps assignment, review and fleet costing under office control.
Road expenses need a trip reference, amount, location and supporting receipt so the office can review them promptly.
For The Chishtian Logistic (TCL), the useful unit of work is the Mile: the operating trip record that already knows the vehicle, pickup point, drop-off point and bilty date. A driver expense makes sense only when it remains attached to that trip.
The driver sees assigned work, records journey events and submits road expenses. Assignment, policy, approval and transfer to fleet costing remain in Odoo.
01 / ERP-owned assignment
The app starts with the Mile assigned to that mobile user.
The app uses the vehicle and trip references held in Odoo. Odoo returns only active Miles explicitly assigned to the signed-in mobile profile. The app shows the Mile reference, vehicle, pickup, drop-off and bilty date from that record.
Expenses are restricted to active Miles assigned to the driver. Changes made by operations in Odoo update the work available in the app.
02 / Journey evidence
Four actions record the main stages of each trip.
The trip control follows the driver’s working sequence: Start Mile, Destination Reached, Start Return Ride and End Trip. Each action captures the device location, time and accuracy against the assigned Mile. Odoo retains the trip status and the related location events instead of leaving the journey as an informal update.
When route tracking is enabled, the app can also send periodic location records at a configured thirty-minute interval. Start, destination, return and end remain identifiable business events; periodic points add continuity between them. The office can review the latest location and travelled-distance context from the Mile rather than treating the phone as an unconnected tracker.
03 / Expense at source
The claim carries its trip, category, location and evidence with it.
Add Expense opens against the assigned Mile. The driver selects an Odoo-managed expense head, enters the reported amount and a short remark, and captures or chooses a receipt image when the category requires one. The same submission records the current GPS location and device time.
That detail matters because “fuel”, “toll” or “repair” is not enough for review on its own. The useful record answers which Mile, which vehicle, where, when, how much and what evidence. The driver’s recent expense list then shows the reference, Mile, reported amount, approved amount and current status.
Context
The assigned Mile supplies the vehicle, route and operating reference.
MILE + VEHICLEClaim
The driver selects the controlled expense head and reports the amount.
HEAD + AMOUNTEvidence
GPS, device time, remarks and the required receipt stay with the claim.
PLACE + PROOF04 / Spend visibility
The app shows vehicle petty cash from Odoo.
The home screen presents vehicle petty cash as three practical numbers: advance released, amount used and balance remaining. These are not a second wallet maintained inside the app. They are calculated from the vehicle-linked payment and reconciliation position in Odoo.
Released
The outbound vehicle advance that has actually been paid.
Used
The portion consumed through reconciled vehicle expense.
Remaining
The unreconciled balance still available for the vehicle.
The driver gets a simple operational answer without seeing journals, payable lines or reconciliation screens. Finance retains those controls in the ERP where they belong.
05 / Road-ready continuity
Expenses and location records can be queued offline.
The app stores its working data locally and keeps unsent expense or location requests in a device queue. It clearly shows whether the phone is online, how many items are pending and provides a manual Sync action. Connectivity returning triggers the same queue automatically.
Each offline expense carries a unique device reference. If a retry reaches Odoo twice, that reference allows the API to recognise the earlier submission instead of creating a duplicate claim. The cached Mile, expense heads and recent history keep the driver’s interface useful while the road connection is unreliable.
06 / Odoo approval
Reported amount and approved amount remain separate.
A submitted claim enters Odoo for review. The reviewer can inspect the Mile, vehicle, driver, expense head, receipt and mapped location before deciding the accepted amount.
An approved amount must be positive and cannot exceed the reported amount. A rejection requires a review note. Those rules keep the adjustment visible: the original driver claim remains intact while the financial decision is recorded alongside it.
07 / Fleet-finance handover
The accepted road cost finishes inside the vehicle’s expense statement.
Once the Mile is completed, an approved mobile expense can be transferred to its fleet expense statement. Odoo carries the Mile, vehicle, trip date, pickup and drop-off context into that statement and adds the accepted amount under the configured expense head.
The transfer is controlled: a mobile expense cannot be moved twice, and it cannot be inserted into an already posted statement. Related operational references remain available for vehicle costing, trip profitability and the later accounting process.
Drivers, operations and finance use the same Mile and expense references from capture through approval and fleet-cost transfer.
08 / Product boundary
Driver actions and office controls.
TCL Mile Expenses keeps the mobile vocabulary close to the job: assigned trip, route, trip stage, petty cash, expense and Sync. It supports English and Urdu without exposing server configuration, journals or approval screens to the driver.
Odoo manages user assignment, trip-state rules, duplicate protection, expense categories, evidence review and fleet-cost transfer. Drivers use the app to record the trip events and expenses needed by those workflows.