Two lists, one lot
Ask a dealer principal why their floorplan lender's statement doesn't match their lot inventory, and the honest answer is that the two documents were never built to line up automatically. The dealer statement lists every unit the lender has financed, by VIN, with a payoff amount and a curtailment schedule. The lot inventory — pulled from the DMS, or a walked count — shows what's physically there today.
A unit that sold last week should be off both lists, its loan paid off the same day. A unit still aging on the lot should be on both. The gap between the two — a unit on the statement but not on the lot, a unit on the lot with no matching financed record — is exactly what a floor plan audit exists to find, and exactly what most dealerships only check once a quarter, right before the auditor arrives.
None of this means anything is wrong by default. It means the two lists answer different questions, and confirming they agree means reading both deliberately instead of assuming one already reflects the other.
Why this isn't a simple lookup
A dealer statement and a lot inventory are produced by two different systems on two different schedules, using two different formats for the same underlying fact: which vehicles the dealership actually owns free and clear versus owes money against. The lender's statement is a PDF or a portal export; the lot inventory is whatever the DMS produces, or a spreadsheet from a physical walk.
Multiply that by every curtailment cycle, or by several rooftops each running their own floorplan line, and the VIN-by-VIN comparison that took twenty minutes on a small lot becomes a recurring task nobody has time to protect every cycle — right up until an audit finding makes it everyone's problem at once.
What a floor plan audit actually checks
A floor plan audit — sometimes called a floorplan inspection — is the lender's periodic verification that every unit it has financed is still in trust: physically on the lot, still owned by the dealership, with the loan against it still outstanding. An auditor, either from the lender or a third-party firm, walks the lot and checks VINs against the dealer statement.
The single finding every audit is built to catch is a unit sold out of trust — sold to a customer without the floorplan loan being paid off, so the lender still carries it as financed inventory that no longer exists on the lot. A pattern of units sold out of trust is treated seriously, and can lead to a reduced credit line, a demand for immediate payoff, or worse.
What a dealer statement actually is
A dealer statement is the summary a floorplan lender produces on a regular cycle, listing every unit currently financed by VIN, along with the amount owed on it, the date it was floored, and its curtailment schedule. The statement total is what the lender believes is financed — it's not a confirmation that every one of those units is still physically present.
The gap between the statement and the actual lot is where timing lag, unreported sales and genuine sold-out-of-trust situations all live, and only reading both sides together separates the three.
The curtailment schedule, unit by unit
Most floorplan lines require curtailment payments as a unit ages — a partial principal paydown at 30, 60 or 90 days on the lot, scaling up the longer a unit sits unsold. Each unit's curtailment schedule is read directly from the statement and tracked individually, since missing a curtailment date carries its own fee separate from any audit finding.
| Aging bucket | What typically happens |
|---|---|
| 0–30 days on the lot | Standard financed status, no curtailment yet due |
| 31–60 days | First curtailment payment typically due |
| 61–90 days | Second curtailment, increased audit attention |
| 90+ days | Highest scrutiny, some lenders require full payoff or removal |
None of these thresholds are universal — every lender sets its own curtailment terms — but the underlying pattern is the same: a unit's scrutiny rises with its age on the lot, which is exactly why tracking the schedule per unit matters more than watching a single portfolio-level aging number.
Why the lot and the statement rarely match on the same day
A dealer statement is dated to the lender's own cycle, not the moment a sale happens. A unit sold yesterday might still appear as financed on a statement generated last week, and a payoff submitted today can take a day or two to reflect on the lender's side.
Matching by date alone, without allowing for this lag, produces false alarms — a unit that sold three days ago and still shows financed on the statement isn't sold out of trust, it's the normal processing window for that lender's payoff cycle.
What gets read
From a dealer statement: VIN, financed amount, floor date, curtailment schedule, and any fees applied. From a lot inventory export: VIN, days on lot, stock number, and sale status where the DMS tracks it.
A field that can't be read with confidence — a VIN that fails a checksum, a truncated stock number — is flagged rather than filled in with a best guess, so a review focuses on the handful of fields that genuinely need a second look.
How it works
Upload the dealer statement and lot inventory
From any floorplan lender and any DMS export, for the period you're reconciling.
Each document is read
VINs, financed amounts, curtailment dates and inventory status extracted from both sides.
Units matched by VIN
Exact VIN matching, with a checksum check on every read.
Gaps flagged, not guessed
A financed unit with no matching lot record, or vice versa, is marked for review.
Exported
Excel, CSV or JSON, with every matched unit traceable to its source document.
An audit, prepared for
A used-car lot carrying 68 financed units gets notice of a floor plan audit in five business days. The dealer statement lists 68 VINs; the current lot inventory export lists 65.
| Result | Count |
|---|---|
| Matched, in trust, no action needed | 62 |
| Matched, curtailment due within 5 days | 3 |
| On the statement, not on the lot — flagged | 2 |
| Sold, payoff already submitted, still processing | 1 |
Of the two genuinely flagged VINs, one turns out to be a unit transferred to a sister rooftop the day before, not yet reflected on either inventory list — resolved with a phone call. The other is a unit that sold four days earlier with the payoff submitted but not yet processed by the lender — also resolved, with the submission date as evidence, before the auditor ever walks the lot.
When more than one floorplan line is in use
A dealer group that has grown through acquisition, or a single rooftop that splits inventory across more than one lender for capacity reasons, ends up with two or more dealer statements to reconcile against the same lot.
Each statement is read for its own format and matched independently, then rolled into one consolidated view — a VIN never gets double-counted across lenders, and a unit's financing source stays traceable even when the lot itself doesn't distinguish between them.
Handling a discrepancy with method
A VIN on the statement with no matching lot record, or a lot record with no matching financed VIN, gets flagged rather than assumed to be an eventual match. The first step is confirming whether the unit actually sold and whether a payoff was submitted — a submitted payoff still processing is a timing gap, not a violation.
The second step is checking for an inter-rooftop transfer, where a unit moved to a different location in the same dealer group — a common pattern that looks like a missing unit until the receiving rooftop's inventory is checked.
Manual vs. automatic
| Manual | Automatic |
|---|---|
| VINs eyeballed line by line between two documents | Every VIN matched exactly with a checksum check |
| A sold-out-of-trust pattern discovered at the audit | An unmatched VIN flagged before the auditor arrives |
| Curtailment dates tracked on a whiteboard or not at all | Every unit's curtailment schedule tracked automatically |
| Redone from scratch for a second floorplan lender | Same method applies regardless of lender |
From one rooftop to a multi-store group
A single lot with fifty units is a manageable manual check, if tedious. A dealer group with several rooftops, each carrying a hundred or more units across multiple lenders, turns the same check into a job someone has to be assigned to full-time if it's done by hand.
Reading and matching each rooftop's statement and inventory the same way regardless of volume keeps the effort per unit flat as the group grows — what changes is only how many VINs need a human look, which a well-tuned matching process keeps small.
Who uses this
Dealer principals and controllers
One matched view of every financed unit against the lot, without a manual VIN check each cycle.
Office managers preparing for an audit
A verified record of what's financed and what's on the lot, ready before the auditor calls.
Multi-rooftop dealer groups
The same matching method applied across every location and every floorplan lender in the group.
CFOs monitoring floorplan exposure
A consolidated view of curtailment risk and aging inventory across the whole group.
Edge cases worth knowing
A unit sold at wholesale to another dealer, rather than retail to a customer, still requires the floorplan payoff — a wholesale sale that skips the payoff step produces the same unmatched pattern as a retail sale sold out of trust, and is worth checking for specifically since the two can be confused internally.
A demo or loaner unit, kept off the active sales lot but still financed, is easy to overlook during a lot walk since it isn't parked with the rest of inventory — matched the same way as any other unit as long as it appears on whatever inventory export is used.
A unit that fails a VIN checksum on the statement itself, rather than on the inventory side, points to a data entry error at the lender — worth flagging back to the lender rather than assuming your own records are wrong.
Why a flagged unit beats a guessed one
A dashboard that shows only matched totals, without the reasoning behind each match, is easy to trust until an auditor asks why a specific VIN was considered accounted for. Reconstructing that reasoning later means going back to both source documents and starting over.
Keeping the match basis attached to every VIN — statement date, inventory date, confidence level — turns that reconstruction from a scramble during the audit into a detail already sitting in the data, ready the moment the auditor asks.
Bringing a new rooftop or lender online
A newly acquired rooftop, or a dealership adding a second floorplan line, starts with no prior reconciliation history — nothing to compare a first cycle against. That first statement and inventory export still get read and matched the same way as any other, since the matching relies on the documents themselves rather than a rooftop's history.
What's worth watching closely in those first few cycles is whether the new lender's statement format holds any surprises — a curtailment schedule structured differently from the rest of the group, a VIN format quirk — the kind of detail that only becomes visible once real statements start flowing through.
None of that requires a separate setup step before the first reconciliation can run — the new rooftop's documents are read the same way from the very first upload.
What this doesn't do
Doesn't replace a physical lot walk
It narrows down which VINs need eyes on them — the physical confirmation an audit requires stays with a person on the lot.
Doesn't calculate curtailment amounts
It reads the schedule the lender's statement reports; it doesn't recompute what a curtailment payment should be.
Doesn't submit payoffs or communicate with lenders
It surfaces what needs attention. Submitting a payoff or contacting a lender stays your step.
Doesn't replace an audit
It builds the traceable record an auditor needs faster — the audit itself stays with the lender or its auditor.
What it does fits in one sentence: turn a dealer statement and a lot inventory into matched, traceable rows, so the question “is every financed unit still in trust” has an answer before the auditor has to find out the hard way.
Security and privacy
Uploads are encrypted with TLS from end to end.
Processing runs on infrastructure with SOC 2-aligned controls.
Original documents are deleted shortly after processing.
Nothing you upload is ever used to train AI models.
For dealer groups handling financing data across multiple lenders and rooftops, that matters — details are on the security page.