Skip to content

Fleets, carriers, and last-mile operators.

Fuel, maintenance, and freight revenue — closed on time.

Fuel moves weekly, maintenance is unpredictable, and driver pay hides inside generic categories — so the ledger runs a step behind a fleet that never stops.

Inbox · needs you
02:14

Transactions to review

CATEGORIZED · AWAITING A SECOND LOOK

9

Bill from Uni-Select

INVOICE READ · FIELDS EXTRACTED

95%

Journal batch · accruals

PREPARED FOR JULY

Approve

Unmatched deposit

NO SOURCE DOCUMENT

Review
1,811 auto-posted9 routed for review
Bell Canada
Entity B
AccountTelecom96%
Tax codeStandard rate
Matched onRecurring vendor
SourceStatement line
Code Bell to Utilities from now on

The problem

Broad categories that erase the vehicle and the lane

Fuel cards, maintenance shops, owner-operator settlements, and freight billing all generate their own transaction streams, on their own schedules, usually coded into broad categories (“fuel,” “maintenance,” “driver pay”) that don’t tie back to a specific route, vehicle, or load. That makes per-route or per-vehicle profitability close to impossible to see without a manual analysis nobody has time to run monthly — so decisions about which lanes or vehicles are actually worth running get made on instinct.

What cruisr does

Coded at the level the decision needs

Fuel, maintenance, and driver pay coded continuously

Reconciled as they arrive, not batched into broad categories at month-end. Proof: the same nightly reconciliation behind the 1,811-of-1,820 stat used sitewide.

Freight revenue reconciled against what settles

So recognized revenue and cash collected don’t quietly drift apart the way they can with factored or delayed freight payments.

The close finishes by business day 3

On a calendar you can plan around — not whenever the fuel-card statement and the settlement report both happen to be ready.

One queue for exceptions

A maintenance charge that doesn’t match a vehicle, a settlement discrepancy, a fuel-card anomaly — routed to a human, not buried in a general ledger nobody reviews line by line. Proof: the same 9-of-1,820 human-reviewed queue used sitewide.

Every vehicle or route in one group view

Vehicles, routes and lanes are tracked as their own dimension — the same entity, department and project tagging behind every other cut of the books — so a lane’s costs roll up without a manual analysis nobody has time to run.

Every entry carries its evidence

The fuel-card line, the maintenance invoice, the settlement statement — each attached to the entry it produced, with the reason it was coded that way. A disputed settlement is answered from the books, not from memory.

See the real state of your books — free, in 48 hours.

No obligation · No migration · Nothing installed

Why not just track this in a spreadsheet?

Coding fuel, maintenance, and settlements into broad categories is fast, but it erases exactly the detail — which vehicle, which route, which load — that would tell you whether a lane is actually worth running. cruisr codes and reconciles at that level of detail continuously, so the answer is sitting in the books already, not buried in a spreadsheet nobody has time to build.

Today · every entity
02:14

Hydro-Québec

PREAUTH DEBIT · recurring vendor match

98%

Bell Canada

PREAUTH DEBIT · recurring vendor match

96%

Uni-Select

INVOICE · line-item pattern

95%

Unmatched deposit

NO SOURCE DOCUMENT

Review
1,811 auto-posted9 routed for review

FAQ

Transportation questions

Three about running a fleet, and the one every operator asks before handing over a bank feed.

By whichever of the two you tag. Fuel, maintenance and driver pay are coded to the dimension you actually run the business on — vehicle, route, or both — using the same tagging behind every other view of the books. There is no telematics feed underneath it: it’s the ledger, cut the way you need it, which is why the tagging has to match how you dispatch.

Not directly, today. cruisr works from what those systems already post into QuickBooks or Xero — fuel-card charges, maintenance invoices, settlements, freight billing — and codes and reconciles them nightly. A direct connection isn’t live; tell us which systems you run on the diagnostic call.

Both, and differently, because they are different: settlements to owner-operators are payables against the loads that earned them, company drivers are payroll. Each is coded to the vehicle or route it belongs to, and both land in the same close on the same calendar.

Access is read-only and permissioned; every entry carries a confidence score and visible reasoning, with anything below threshold routed to a human before it posts.

See which lanes are actually worth running.

Free, on your own QuickBooks or Xero, delivered in a 30-minute readout.

No obligation · No migration · Nothing installed · No credit card required