Dealership Floorplan Reconciliation: VIN-Level Guide

Dealership floorplan reconciliation is the VIN-level process of matching each financed vehicle on the lender statement to inventory records, sold-unit payoff activity, curtailments, floor-check results, and the related floorplan payable balance. The goal is to clear liability when a unit is sold, catch sold-not-paid and paid-not-cleared exceptions early, and resolve aged balances before month-end or lender audits. Teams usually struggle because lender lines, DMS status, and payoff support arrive on different timelines and in different formats.

A dealer floorplan reconciliation cannot stop at the account summary. A floorplan payable balance can look reasonable in the general ledger while one VIN has been sold for days, another has payoff evidence but still appears open, and a third sits in inventory status with an unresolved floor-check issue. A broad liability roll-forward still matters, but controllers need a unit-by-unit view because the real risk sits in the exceptions tied to specific vehicles, not just in the ending balance.

The Record Match Every Unit Has to Pass

A reliable dealership floorplan reconciliation starts with one unit, not one balance. For each vehicle on the lender statement, you need to trace the same VIN and stock number through the lender floorplan statement line, the dealership management system inventory record, the trust receipt or lender unit record, the curtailment schedule, any payoff support, and the related floorplan schedule or general-ledger tie-out. If one of those records cannot be connected to the same unit, the item is not fully reconciled no matter how clean the summary looks.

In practice, your dealership floorplan statement reconciliation should confirm that the core fields either match exactly or have a documented explanation for the difference. That means checking:

• VIN
• Stock number
• financed amount or current principal balance
• unit status in the dealership management system
• curtailment due date and curtailment amount
• sold or unsold status
• posted payoff status and payoff date
• the amount carried on the internal floorplan schedule or GL

For example, imagine a unit that appears on the April 30 lender statement with a $41,800 open balance. The DMS shows the same VIN and stock number sold on April 29, the trust receipt matches the lender unit record, the curtailment schedule shows the next due date in May, and the payoff confirmation is dated April 30. That tells you the unit is identified and supported, but it still needs timing review before you treat it as an aged exception.

The point is not just to prove that total floorplan payable roughly equals total financed inventory. It is to prove that each unit on the liability side has a valid record trail. A VIN that appears on the lender statement but not on your inventory record, a sold unit still showing as open on the trust receipt, or a payoff that cleared operationally but not in accounting are all signs that the reconciliation is incomplete.

That same unit-level logic has to include floorplan curtailment schedule reconciliation. Controllers often treat curtailments as a separate cleanup task, but they belong inside the main match because they affect whether a unit's balance, aging, and expected payoff activity make sense. If the curtailment schedule shows a payment due this month and your internal record does not, or if a curtailment posted internally but is missing from the lender record, you already have an exception worth chasing before month-end.

If this sounds familiar, it is the same control mindset behind dealership invoice workflows that already depend on RO, PO, and VIN matching. The difference is that here you are matching lender statements and financed inventory rather than repair invoices. The discipline is the same: follow the unit across every source document until the VIN, stock number, status, and dollars tell one consistent story. Controllers often build a working VIN-level sheet first because lender statements, curtailment schedules, and payoff support rarely arrive in one format.

When a Sold Unit Should Clear the Floorplan Payable

In dealership floorplan payable reconciliation, a sold vehicle should move from financed inventory to a cleared lender balance only after the full post-sale chain is complete. In controller terms, that sequence is straightforward: the unit is sold, the deal or funding status is updated, the payoff is initiated, the lender receives and posts the payment, and the VIN either disappears from the next floorplan statement or shows as paid off. If any one of those steps is incomplete, the vehicle may be off the lot while the floorplan payable is still legitimately open.

You cannot treat every sold unit on the statement as a failure. Sometimes the issue is just timing. A normal contracts in transit delay usually means the deal is done operationally, but funding, cash movement, or lender posting has not fully landed by the statement cutoff. A real exception looks different: the unit shows sold in the DMS, but no payoff was sent; payoff was sent, but cash was misapplied; payment cleared the bank, but the lender has not applied it to the correct VIN; or the lender statement date captured the balance before the posting cycle finished. The key question in sold unit payoff timing dealership work is not "Was it sold?" but "Which step in the settlement chain is still open?"

At month-end, that cutoff problem gets sharper. A vehicle can be delivered on the last day of the month, funded shortly after, and still remain on the lender statement if the payoff posts after the lender's reporting date. That does not automatically make it an aged recon issue. What matters is whether you can support the open item with evidence: deal status, funding documentation, payoff confirmation, bank or cash application support, and the lender statement date. Without that support, the balance is no longer a timing item. It is an exception.

A practical controller framework is to age sold units by status first, days second:

• Sold, not yet funded: Usually a contracts-in-transit item. Watch closely, but do not treat it like a lender error.
• Funded, payoff not initiated: Internal process break. The unit is sold, but the payoff step has not started.
• Payoff initiated, not yet posted by lender: Often a temporary open item if timing aligns with statement and bank posting cycles.
• Payment posted by bank, still open on lender statement: Likely cash application, reference, or VIN-match issue that needs follow-up.
• No clear support in any system: Highest-risk exception. Assume nothing until you find documentary proof.

That status-based view helps you separate normal settlement lag from true sold-not-paid or paid-not-cleared problems, so your team investigates the right VINs before balances age under lender scrutiny.

The Exception Patterns That Keep Balances Aged

Most aged floorplan reconciling items are not random. They fall into a short list of repeat offenders, and each one needs a different investigation path at the VIN level.

Sold-not-paid is usually the highest-risk bucket. The vehicle shows as sold in the DMS or deal jacket, but the lender still carries it on the floorplan statement because payoff has not been initiated, funded, or confirmed. That is where you need payoff support, funding timing, and proof that the unit is in process of payment. If not, the risk moves beyond routine reconciliation. As the Office of the Comptroller of the Currency explains in the OCC's floor plan lending handbook, floor plan checks should be completed at least quarterly, and inventory sold but not in process of payment represents a breach of trust that leaves part of the lender's credit unsecured. In practice, that is the clearest signal that an aged balance cannot sit in a month-end exception queue waiting for cleanup later.

Paid-not-cleared is different. Here, the dealership has payoff evidence, ACH support, or a cash application trail, but the unit still appears on the lender schedule. That usually points to posting lag, reference mismatch, unapplied funds, or an unreleased title packet rather than an unpaid exposure. You still escalate it, but the ask is operational: confirm when the lender will clear the VIN and remove the payable.

Missing curtailments tend to surface when the curtailment schedule does not match what accounting accrued or paid. The controller needs to test whether the curtailment was due, paid to the wrong unit, short-paid, or omitted from the lender record entirely. This is where schedule version control matters. A team that is reconciling from an outdated statement can spend hours chasing a variance that was already superseded.

Duplicate or stale units usually come from inventory timing, unit transfers, unwound deals, or old records that never dropped off the schedule. If the same VIN appears twice, or a closed unit still sits on a floorplan aging report months later, do not treat it as a generic balance mismatch. Tie the exception back to the current inventory status, sale status, and lender open-unit listing. A stale unit can distort both payable exposure and floor check preparation.

Units on the wrong rooftop or the wrong schedule are common in dealer groups. A vehicle may have been transferred operationally, but the lender statement, store mapping, or internal reconciliation file still reflects the prior rooftop. That creates false aged items at one store and hidden exposure at another. The fix is not just a journal entry. You need to confirm which legal entity, curb location, and lender line should carry the VIN.

Floor-check discrepancies involving missing inventory demand a separate path from routine statement cleanup. This is the heart of floor check exception handling. If a unit cannot be physically verified, if a sold unit has no payoff trail, or if the lender still shows exposure with no clean supporting story, the issue moves from reconciliation noise to lender control risk. Missing inventory, unresolved sold out of trust situations, and unexplained lender exposure should be escalated faster than a normal paid-not-cleared item because the downstream scrutiny is different.

For every aged exception, your documentation should be standardized. At minimum, log:

• Unit identifier: VIN, stock number, lender reference
• Current status: in inventory, sold, transferred, paid, missing, under floor check review
• Missing support: payoff proof, wire confirmation, curtailment notice, transfer support, floor-check response
• Next action: obtain payoff, confirm lender release, research duplicate listing, validate rooftop assignment, escalate to GM or treasury
• Owner: the person responsible for clearing the item
• Escalation date: the date the issue must move beyond normal follow-up if unresolved

That structure does two things. It shortens review time for controllers managing dozens of units, and it separates ordinary posting lag from exceptions that could expose the store or group to lender scrutiny.

---

How Structured Statement Data Speeds VIN-Level Investigation

VIN-level floorplan reconciliation slows down when the evidence for one unit lives across a lender statement PDF, a curtailment schedule export, a payoff email attachment, a screenshot from the DMS, and a floor-check report in yet another format. Before your team can investigate the exception, someone has to rekey or copy those details into a common worksheet. That is where the work piles up, especially in multi-rooftop accounting environments where each lender and store may send different layouts on different timelines.

A usable reconciliation dataset should standardize the fields you actually review at unit level, not just dump document text into a spreadsheet. In practice, that means capturing VIN, stock number, financed amount, curtailment timing, unit status, lender reference, rooftop or store, and payoff-related status indicators so the same columns exist regardless of source format. Once those fields are aligned, you can sort sold units that still appear open, filter balances by rooftop, isolate missing payoff support, and group aged items by lender or exception type.

This is where upstream document structuring helps. Teams can convert floorplan statements into structured spreadsheets before review, then apply the same approach to schedules and supporting documents so each source lands in a comparable format. If you already use a process like extracting statement lines into Excel before reconciliation review, the benefit here is the same: the extraction step prepares the data so controllers can investigate faster, but it does not make the reconciliation decision for them.

For dealership teams handling mixed inputs, Invoice Data Extraction can pull VIN, stock number, financed amount, curtailment timing, rooftop, and payoff-related fields from PDF, JPG, or PNG statements and schedules into Excel, CSV, or JSON so controllers start with one review-ready sheet instead of a stack of attachments.

The time savings show up in the investigation sequence. Instead of opening each attachment one by one, your team can filter the structured file for units with a sold status and no payoff indicator, balances with a curtailment due date already passed, or VINs appearing under the wrong rooftop. In a high-volume store group, that makes it easier to triage aged exceptions first, assign follow-up by lender or location, and spend controller time on root cause analysis rather than document cleanup.

---

A Controller Month-End Floorplan Reconciliation Checklist

A workable floorplan reconciliation checklist should let you close the month at VIN level, explain every open balance, and carry unresolved items forward with a clear owner and next action. For most stores, that means running the same controller month-end floorplan review each period instead of rebuilding the process when lender pressure rises.

1. Lock the reconciliation date and statement cutoff. Use the lender statement date, your DMS inventory snapshot date, and the GL close date on the same workpaper header so the whole team is matching to one point in time.
2. Pull the current VIN-level inventory population. Export all units still showing as floorplanned or recently sold, including stock number, VIN, lender, advance amount, payoff status, sale date, and current inventory status.
3. Match every open statement unit to an internal unit record. For each VIN on the floorplan statement, confirm the unit exists in inventory, is tied to the correct lender, and carries the expected principal balance after any curtailment activity.
4. Flag sold units that should have cleared. Build a separate exception tab for vehicles marked sold or delivered internally but still outstanding on the lender statement. Add sale date, funding date, payoff initiation date, payoff amount, and whether payoff evidence is on file.
5. Review curtailments due, paid, and still accruing. Identify units approaching the next curtailment tier, units with curtailments paid but not reflected correctly on the statement, and units where the aged balance is driven by missed or partial curtailment activity.
6. Reconcile floor-check findings to the statement and inventory records. Any unit noted in a floor check as missing, transferred, demoed, or otherwise out of status should be traced back to the current statement and your internal records immediately.
7. Tie the unresolved VIN exceptions to the GL. Your open floorplan payable, accrued interest, and any related clearing accounts should reconcile back to the unit-level exception list, not just to a high-level lender total.
8. Document the root cause and save the support with it. Use short categories such as payoff in transit, funding delay, title issue, unit transfer mismatch, curtailment timing, lender posting delay, or inventory status error, then keep the supporting statement pages, payoff confirmations, wire support, floor-check notes, and lender correspondence in the same exception file.
9. Assign an owner and deadline to every open exception. Treasury, accounting, title, F&I, or store ops should each know exactly which VINs they own before the close package is finalized.

For dealer groups, this kind of dealer floorplan reconciliation works best when each rooftop uses the same exception categories and aging logic. That makes it easier to compare lenders, spot recurring breakdowns, and fit floorplan review into broader dealership AP workflows across stores and statement-heavy month-end work without losing focus on financed inventory.

Keep the final workpaper simple: one tab for matched units, one for sold units awaiting clearance, one for curtailment review, and one for unresolved exceptions with owner, status, and required follow-up. If you can open that file next month and know exactly why each VIN is still open, your month-end process is doing its job.