Month end stops being archaeology
The alternative is four spreadsheets and three drivers' memories, assembled on a Sunday, believed because nobody has the energy to check it.
How the figures get there
Recorded as you operate, not reconstructed after.
Four steps, none of which is a data-entry job.
01
Recorded
The number is written while the job runs
Nothing here is a separate data-entry step. The quote, the legs, the awards and the invoice each leave the figure behind them.
- Margin computed from the legs and the awards, never from a booking total
- Committed partner cost sits on the leg beside the client price
- Driver settlements built from the jobs actually driven
02
Grouped
By client, by class, by period
The breakdowns that change a decision: which accounts carry the month, which vehicle class earns, which work is quietly unprofitable.
- Revenue and job counts per client
- Vehicle class and fleet utilisation
- Period comparisons rather than a single running total
03
Chased
What is owed, and how late it is
The invoice ledger carries its own aging, so cash position is a screen rather than a spreadsheet built on a Sunday.
- Aging buckets and days sales outstanding, computed
- Statement import matches payments; the exceptions are the short list
- A sent invoice cannot have its figures edited, so the history stays true
04
Exported
Out to CSV and PDF, whenever you want it
For the accountant, for a board pack, or for whatever you already run alongside.
- Report generators across revenue, jobs, fleet and people
- CSV for working with, PDF for sending
- A REST API with webhooks for the systems you keep
No card · Cancel in one click · Export anytime