Your files in the morning, your rents out that evening.
We take your fleet over ourselves, Excel files included. You send everything as it is, every row is reviewed together on screen, and billing picks up the same evening. No IT project, nothing to install, no freeze on your operation.
One day, not one quarter.
How a 1,500-vehicle switch actually runs. The times are indicative; the order is not.
You drop your files
Excel, CSV, the raw export from your current tool. No format imposed, no column to rename, no template to fill.
youThe mapping is proposed to you
Your headers are matched against our schema, each with a confidence level. A wrongly guessed column is fixed in one click, and the whole batch recomputes without a new upload.
BacklaneThe verification screen
Row by row: what will be created, what already exists, what is rejected and exactly why. We read it with you. A value is fixed on screen, not in the file.
togetherThe fleet is written
1,500 vehicles in one pass: plates, states, mileage, lessor financing and upstream cost. Lessors missing from your directory are created along the way.
BacklaneDrivers, contracts, financing
Every contract finds its driver and its vehicle on its own. The rent cycle, weekly or monthly, is the one you actually run: we convert nothing.
BacklaneOpening invoices
With their original number, their balance and their lines. Aging and collections restart on your real history, not from zero: an invoice 32 days late arrives 32 days late.
BacklaneDocuments in bulk
One ZIP of scans. Each file joins its vehicle through the plate read in its filename; whatever stays ambiguous is opened and classified by type, never guessed.
BacklaneBilling picks up
The fleet is live, contracts are in place, debits are scheduled. Your old tool stays readable for as long as you need it: nothing is deleted there.
youEvery entity keeps what makes it recognisable.
The middle column is the natural key: what a row is recognised by. It is what makes a re-import correct rather than duplicate.
What makes the switch reversible.
The batch waits behind a verification screen. It can wait a week. Until you approve, your data is untouched, and a pending batch is deleted without a trace.
A row is recognised by its natural key, not by its position in the file. Fix your Excel and send it again: existing rows are updated. A vehicle created by hand yesterday is recognised by its plate, not duplicated.
Every committed batch can be rolled back as long as no active contract depends on it. Two deliberate exceptions: opening invoices, which touch accounting, and archived documents, which fall under retention. Those get corrected, not erased.
A rejected row tells you why.
The fleet goes in before contracts, financing and documents: a contract whose vehicle does not exist yet is rejected with the exact reason, "import the fleet first", not with an error code. Once the fleet is in, one button re-reads the batch against the current data without resending anything, and rejections turn into valid rows. It is the opposite of the batch that fails at 3% and has to be rerun whole.
Is my historical data carried over?
Yes: opening invoices import with their original numbers and balances, so aging and collections restart with the real history. Documents (registrations, insurance) upload in bulk.
What if I want to leave?
Your data stays yours: everything exports. An import can also be undone: any committed batch can be rolled back as long as no active contract depends on it.
How long does it take?
A typical day for a fleet of a few hundred vehicles: the import itself takes minutes, the joint review takes hours.
Our files are messy: duplicates, empty columns, badly typed plates. Is that a blocker?
No, that is the normal case. Duplicates on the natural key are flagged before writing, empty columns are ignored, and a malformed plate becomes a readable rejection you fix on screen. No file needs cleaning before you send it to us.
Who does the work: you or us?
We do. You provide the files and read the verification screen with us, because you are the only ones who know whether an odd row is a mistake or a real exception. The rest is on our side.
What if we only switch part of the fleet first?
That is common, and it works: an import covers the rows you send. We regularly see one branch or one vehicle category go first and the rest follow two weeks later. The second batch does not duplicate the first.
No commitment. Nothing changes with your current tools or insurer.