The challenge
French weekly-driver rental operators do not usually fail for lack of an invoice template. They fail when departure, return, SAV, and cleaning live in chat or a yard whiteboard while the weekly rent run lives in a spreadsheet — and return inspections never close beside the same contract that owns the week. Ops generate unpaid balances against a story they cannot open in one place. Charges and recalculations arrive after the fact. Monday morning is reconstruction. The industry gap is simple: a booking calendar with an export is not a weekly billing workbench. Week navigation, unpaid rent and charges, payments, balances, guided Movement transitions, and a return-inspection queue have to share one rental identity — or staff rebuild status from chat before they can trust the invoice week.
Architecture
In FleetFlow, a French rental operations Admin built end to end by TechMania, weekly billing is not a side spreadsheet. The invoices surface is organized by billing week and sits next to Movement and Inspections so close depends on recorded vehicle state and return control — not on reconstructing handoffs from messages. This case study isolates that weekly billing + movement + inspections loop. It is not the full FleetFlow product story already covered on the TechMania site, and it is not the ANTAI fines workbench depth covered separately.
Solution
The surfaces that make up that loop: - Invoices — weekly rental billing with unpaid-rent / fines / driver-debt cues, week navigation, Excel import, payments, charges, weekly generation, rent recalculation, driver balances, unpaid invoices, and invoice-line views - Movement — guided vehicle state transitions for departure, return, SAV/garage, cleaning, loaned/ready, and waiting so yard status is an Admin action before the week closes - Inspections — return-control queue highlighting rentals awaiting a return inspection and completed departure/return reviews beside the same contracts - Rentals — contracts with driver/plate context, weekly price, and active/completed status so the billing week has a clear rental identity - Also in the same Admin: reimbursements approval filters, drivers, notifications, staff roles, and settings for weekly invoicing automation — so back-office close is not a second product from yard work Fines and OCR designation sit beside this loop in the product; they are out of scope for this write-up. SaaS subscription plan tiers on the product billing screen are likewise out of scope — this case is weekly rental invoices for drivers and contracts.
Results
What this changes for operators: - Weekly invoices generate and navigate by billing week inside the same Admin as contracts — not only in a separate finance tool - Unpaid rent, charges, payments, and balances are openable next to the rental identity that owns the week - Movement transitions (departure, return, SAV, cleaning, ready) are recorded before close, so availability and billing share one status model - Return-pending inspections surface beside active rentals instead of after the invoice week has already run - Ops can move from Movement → rental → inspection → weekly invoice without rebuilding the handoff story from chat - Staff roles keep yard work and back-office billing with the right tier instead of one oversized Admin login for everyone Next step Need weekly rental billing with week navigation, unpaid balances, and invoice generation inside the same French Admin as guided Movement states and a return-inspection queue? https://techmania.solutions
Related project
FleetFlow — rental fleet operations Admin
Rental fleet Admin we built end to end: vehicles, drivers, rental contracts, inspections, weekly invoicing and the ANTAI/FPS fines workflow in one workspace.
View project in portfolio