The same problem at every size
Every dealership that carries floorplan financing faces the same underlying question: does the lender's dealer statement actually match what's on the lot. A single-rooftop used-car dealer asks it about forty units. A regional group asks it about several hundred, across multiple lenders and locations. The question doesn't change; the effort to answer it correctly does.
What follows are specific scenarios independent dealerships run into around floorplan reconciliation, and how the matching handles each — not as abstract capability claims, but as the actual situations that come up.
Why a single lot and a dealer group need different things
A single rooftop with one floorplan lender can often get by with a manual VIN check once a month, tedious but survivable. Add a second rooftop, a second lender, or simply enough volume that a monthly check misses things for weeks at a time, and the manual approach stops being survivable — not because the underlying task changed, but because it no longer fits in the time anyone has for it.
What tends to happen in practice is that a dealership grows past manual reconciliation gradually, without a single obvious moment where it stopped working. A monthly check that used to take an hour starts taking half a day. A discrepancy that used to be obvious at a glance gets buried in a longer list. By the time a genuine problem surfaces, it's often been sitting unnoticed for a cycle or two — not because anyone got careless, but because the manual process quietly stopped scaling with the business well before anyone flagged it as broken.
Scenario: preparing for a scheduled audit
In practice: a floorplan lender gives five business days' notice of an upcoming audit. The dealer statement and a fresh lot inventory export are uploaded the same afternoon; every VIN is matched within minutes, with two flagged for a same-day sale still processing and one for a unit transferred to a sister rooftop the week before. Both are resolved with documentation before the auditor arrives.
Scenario: a second floorplan line opens up
In practice: a dealership adds a second floorplan lender to increase available credit during a high-inventory season. The new lender's statement format differs from the first, but it's read and matched the same way, with both lines rolled into one consolidated view so a unit's financing source stays clear without manually cross-referencing two separate systems.
Scenario: acquiring a second rooftop
In practice: an independent dealer group acquires a second location with its own existing floorplan relationship and no prior reconciliation history. The new rooftop's statement and inventory are read from the very first upload — there's nothing to set up first, since the matching relies on the documents themselves rather than an established baseline.
Scenario: a suspected sold-out-of-trust unit
In practice: a routine weekly reconciliation flags a VIN on the statement with no matching lot record and no obvious explanation. Checking the DMS shows a sale three weeks earlier with no payoff on file — a genuine finding, caught internally, disclosed to the lender proactively with the sale date and a payoff plan already in hand, rather than discovered by the lender first.
Scenario: month-end true cost reporting
In practice: a controller closing out the month needs true per-unit cost, including floorplan carrying cost, for every vehicle sold that month. Acquisition invoices, reconditioning invoices, and the dealer statement's interest lines are matched per VIN, producing a cost figure that's traceable back to source documents instead of an estimate built the night before the report is due.
Scenario: a controller inheriting the floorplan relationship
In practice: a new controller takes over floorplan oversight from a predecessor who managed it entirely by memory and a personal spreadsheet. The first month is spent simply establishing a reliable, matched baseline — every VIN on every current statement confirmed against the lot — so going forward starts from a known-clean state instead of an inherited unknown.
Scenario: a credit line renewal review
In practice: a floorplan lender schedules an annual review ahead of renewing a dealership's credit line, asking for the last four quarters of audit results and a summary of any findings. Because reconciliation has been running weekly rather than only around scheduled audits, the controller pulls a clean four-quarter history in under an hour, with every prior finding already documented and closed — turning what could have been a week of digging through old records into a same-day response.
Scenario: seasonal inventory swings
In practice: a dealership doubles its floorplan draw heading into a seasonal high-demand period, adding dozens of units in a few weeks. The volume increase means more VINs to match each cycle, but the reconciliation itself doesn't change in kind — the same weekly process simply processes a larger statement and a larger inventory export, catching the same kinds of discrepancies at a larger scale without needing extra staff time to keep pace.
Scenario: switching floorplan lenders
In practice: a dealership decides to switch primary floorplan lenders for better terms, requiring every currently financed unit to be paid off on the old line and re-floored on the new one over a transition month. Both lenders' statements are read and matched the same way during the overlap period, so a unit mid-transfer between the two doesn't get mistaken for a duplicate or a missing VIN — it's simply tracked as present on both statements briefly, exactly as expected during a real transition.
Scenario: preparing for a lot sale or valuation
In practice: an owner considering selling a rooftop needs a clean, verifiable snapshot of exactly what's financed, what's owned free and clear, and what the true carrying cost of current inventory looks like, for a buyer's due diligence review. Because the reconciliation has been running as a routine rather than assembled once for the occasion, that snapshot already exists — turning what could be weeks of due-diligence document gathering into a package that's largely ready to hand over.
Scenario: standardizing reporting after a merger
In practice: two independent dealer groups merge, each having tracked floorplan reconciliation a different way — one on a well-maintained spreadsheet, the other largely informally through a trusted office manager's memory. Bringing both onto the same matching process, applied identically to every rooftop regardless of which group it came from, gives the combined finance team its first genuinely comparable view across the merged company, rather than two incompatible legacy habits running in parallel indefinitely.
Scenario: disputing a curtailment fee
In practice: a lender charges a curtailment fee on a unit the dealership believes was paid down on time. Because the statement history and the corresponding payment confirmations are already matched and dated per unit, resolving the dispute is a matter of pulling the specific record and comparing dates — rather than reconstructing, after the fact, what happened weeks earlier from memory or scattered email confirmations.
Scenario: a new GM inheriting an unfamiliar lot
In practice: a general manager takes over a rooftop mid-year, inheriting whatever floorplan reconciliation habits the previous GM had in place — in this case, an informal spot-check done occasionally rather than any documented routine. Running the first full reconciliation establishes a clean, verified baseline within the first week, giving the new GM a concrete answer to exactly where the lot stands rather than inheriting an open question along with everything else that comes with a leadership transition.
When it's several rooftops, not one
For a dealer group running several rooftops, each with its own inventory and sometimes its own floorplan line, the pattern above repeats at every location — but the value compounds. A discrepancy caught at one rooftop doesn't require redoing the whole process elsewhere; each location's statement and inventory are matched independently and rolled up into one group-level view, so a controller overseeing the whole group sees both the consolidated picture and the store-by-store detail behind it.
The practical benefit compounds fastest for a group that's grown through acquisition, where each rooftop may have arrived with its own inherited habits, spreadsheets, and floorplan lenders. Running every location through the same matching process, regardless of what it inherited, is often the first time a group-level controller sees a genuinely consistent, comparable view of floorplan exposure across the whole company rather than a patchwork of different local practices.
What it costs not to reconcile
It's worth being concrete about what's actually at stake when floorplan reconciliation is skipped or done only sporadically. The direct cost of a missed curtailment payment is a fee — usually modest on its own. The cost of a genuine sold-out-of-trust finding, discovered by the lender rather than self-reported, is a different order of magnitude: a demand for immediate payoff, a reduced credit line, or in a serious or repeated case, the loss of the floorplan relationship entirely.
There's also a quieter cost that rarely gets attributed correctly: a controller's time spent reconstructing what happened after the fact, once a discrepancy has already been flagged by someone else. That reconstruction — tracking down a sale record, confirming a payoff date, explaining a transfer — takes far longer after the fact than the same check would have taken as a routine, proactive step days or weeks earlier.
There's a relationship cost too, harder to put a number on but real over time. A lender who has seen a dealership handle several audits cleanly and proactively extends a different level of trust than one who has had to chase down explanations more than once — a difference that can matter at renewal time even when every individual finding along the way was eventually resolved.
Why this approach fits how dealerships actually work
Most finance software built for dealerships assumes a big DMS integration project, a lengthy implementation, and a commitment to restructure how records are kept. Floorplan reconciliation doesn't need any of that — the dealer statement and the lot inventory already exist as documents every dealership already produces. Reading and matching those documents directly, without requiring a system migration first, is what makes this fit into an existing routine rather than replacing it.
That matters especially for independent, owner-operated dealerships that don't have a dedicated IT function to manage a bigger integration project. The barrier to starting is uploading a statement and an inventory export — not a procurement process, not a multi-week onboarding, not a change to how the DMS itself is used day to day.
It also means the tool adapts to however a dealership already organizes its own records rather than forcing a particular structure onto it. A rooftop that exports inventory as a spreadsheet works the same as one pulling directly from a DMS report — the input format doesn't dictate how the dealership has to operate day to day.
Common hesitations, addressed
“We already have a DMS — isn't this redundant?”A DMS tracks lot inventory well but generally isn't built to read and match an external lender's statement against it automatically. This fills that specific gap rather than duplicating what the DMS already does.
“Our volume is too small to justify this.”The value doesn't scale only with volume — a forty-unit lot still needs every VIN confirmed before an audit, and a missed sold-out-of-trust unit is just as serious a finding at forty units as at four hundred. Smaller lots simply spend less time on each reconciliation cycle, not less benefit per unit checked.
“We don't have time to adopt a new tool.”There's no implementation period that has to happen first — the first use is uploading a statement and an inventory export and seeing the result immediately, which is a smaller time investment than most dealerships expect going in.
“Our office manager already handles this fine.”That's often true right up until volume grows, a second lender gets added, or that specific person is out sick during audit week. The question worth asking isn't whether the current process works today — it's whether it still works the same way six months from now, and whether the knowledge behind it is written down anywhere else.
“What if the tool misreads a VIN?”This is exactly why VINs are held to a stricter standard than other fields — every one is checksum-validated, and anything that fails is flagged for a manual look rather than silently accepted. A misread VIN doesn't slip through unnoticed; it gets surfaced specifically because it needs a second look.
“What happens to our data once we upload it?”Uploaded documents are encrypted in transit, processed, and deleted shortly afterward — nothing uploaded is retained indefinitely or used to train models. For a dealership handling financing data across multiple lenders, that's a reasonable thing to ask about upfront, and worth confirming rather than assuming.
Who this is for
Independent used-car dealers
A single lot managing its own floorplan line without a dedicated finance team.
Multi-rooftop dealer groups
Consolidated visibility across locations and lenders without losing per-store detail.
Controllers and office managers
A reliable process for audit prep and month-end cost reporting alike.
Newly acquired rooftops
A clean starting point without needing prior reconciliation history.
Dealer group owners
A consolidated, comparable view of floorplan exposure across every rooftop they own.
Auditors and third-party inspectors
A pre-matched VIN list and documentation package that shortens the physical visit.
What all of these roles share is the same underlying need — a reliable answer to whether financed inventory matches what the lender believes is financed, without having to reconstruct that answer from scratch each time someone asks. Whether the person asking is a controller closing the month, an owner reviewing group-wide exposure, or an auditor standing on the lot, the same matched data serves the question. Nobody has to maintain a separate version of the truth for their particular role — the underlying reconciliation is the same regardless of who's asking or why.
Getting started
There's no setup step that has to happen before the first reconciliation runs. Upload a current dealer statement and a lot inventory export and see the matching directly — the same starting point whether it's a single lot's first audit or a dealer group bringing on a newly acquired rooftop.
From there, most dealerships settle into running the reconciliation weekly, ahead of any scheduled audit, so the answer to “does the statement match the lot” is always current rather than reconstructed under time pressure.
For a multi-rooftop group evaluating this for the first time, a common approach is to start with a single location — usually the one with the largest inventory or the most recent audit history — run it for a full statement cycle, and confirm the process fits before rolling it out across the rest of the group. Because each rooftop is matched independently regardless of how many others are already using it, there's no coordination overhead to expanding from one location to the whole group once the first one is running smoothly.
Most dealerships that go through this process describe the first reconciliation as the moment floorplan exposure stopped being an abstract concern and became something concrete they could point to — a specific list of matched units, a specific handful flagged, rather than a general sense that things were probably fine.