Floorplan reconciliation is a VIN-level match of the lender’s floored-unit list against your DMS and general ledger, and the goal is to clear every exception before month-end closes. Guidance from the FDIC frames this as a core lending control, not busywork. Controllers should prioritize sold-but-not-paid units, confirm bank payoffs, and document every exception for auditors and lenders alike.
TL;DR:
- The reconciliation process requires structured lender statements, VIN normalization, and documentation for each exception to prevent errors and delays.
- Most discrepancies stem from sold-but-not-paid units, paid-but-not-cleared cases, and formatting issues with VINs, requiring targeted investigation and documentation.
- Weekly reconciliation tasks include matching payoffs and verifying inventory, while month-end involves completing full VIN tie-outs, aging analysis, and obtaining management sign-off.
- Fixing mismatches involves journal entries that clear accounts such as floorplan payable and inventory, backed by supporting documents and dual approval when necessary.
- Automation tools that handle structured imports, VIN normalization, and audit logs significantly reduce reconciliation time and improve accuracy during month-end closing.
Table of Contents
- VIN-level matching: the records and checks that prove your position
- Common mismatches and how to investigate them
- Your month-end floorplan reconciliation checklist and timeline
- Fixing mismatches: workflow and journal entry patterns
- Tools and automation that speed VIN-level reconciliation
- What controllers get wrong about the reconciliation timeline
- How Loturn helps close floorplan reconciliation faster
- Sources
- FAQ
VIN-level matching: the records and checks that prove your position
A reconciliation is only as strong as its inputs. Before you can tie anything out, you need the lender statement (VIN, loan number, principal, interest accrued, and payoff date), your DMS record for each VIN and its sale status, retail contract or payoff evidence for anything marked sold, title or MSO location, and the GL postings for unit cost and floorplan liability.
The matching process itself runs VIN by VIN. Pull the lender’s floored list, sort your DMS inventory the same way, and flag any unit that appears on one side but not the other. Date mismatches of a few business days are normal, since payoffs post on the lender’s schedule, not yours, but anything older than a billing cycle needs an explanation.
New and used inventory behave differently here; used units often carry equity positions that shift as units age, so reviewing real sold prices can help assess ageing risk accurately. New units typically move on a straight loan-to-cost basis, while used units often carry equity positions that shift as units age, so your tolerance for variance should be wider on used stock but the investigation should start sooner.
- Insist on structured statement formats (CSV or EDI) rather than PDFs; manual re-keying is where most VIN errors originate.
- Confirm the lender’s file includes loan number, VIN, principal, and payoff date as separate fields, not bundled into a single description column.
- Flag any VIN with a formatting inconsistency (leading zeros, dashes, mixed case) before it causes a false exception.
Common mismatches and how to investigate them
Most aged floorplan discrepancies fall into a handful of repeatable patterns. Knowing which one you’re looking at determines how fast you can close it.
- Sold but not paid: check whether the retail contract is still in transit, confirm the buyer’s financing funded, and trace the bank payoff receipt against your operating account. If the payoff hasn’t hit the lender, the delay is usually on the funding source, not your books.
- Paid but not cleared: request remittance evidence from the bank, then compare posting dates and loan numbers between your GL and the lender statement. When no proof of payment turns up within a few business days, escalate to the lender directly.
- Duplicate or mismatched VINs: normalize VIN formatting across both files, review your DMS import mapping for truncation errors, and scan for transposed characters, which are the most common cause of a VIN that looks unmatched but isn’t.
- Missing units on the lender’s list: coordinate a physical inspection, verify where the title or MSO actually sits, and document the escalation in writing in case it becomes an audit question.
Pro Tip: Triage every open exception by age, dollar exposure, and whether the VIN could be pledged to more than one creditor. That third factor is the one examiners care about most.
The FDIC’s examination guidance treats aging analysis and multiple-pledge risk as standard procedures for detecting default exposure, which is a useful reminder that your internal reconciliation and the lender’s exam are checking for the same thing.
Your month-end floorplan reconciliation checklist and timeline
Reconciliation works best as a weekly habit that builds toward a clean month-end close, not a scramble on the last day of the month.
Weekly tasks:
- Clear recent payoffs against the lender statement as they post.
- Run a VIN feed check between the DMS and the lender’s floored list.
- Verify floor checks against physical inventory and reconcile any discrepancy immediately.
Month-end tasks:
- Complete a full VIN tie-out between the lender statement, DMS, and GL.
- Roll forward the floorplan liability account and confirm the ending balance matches the lender’s statement.
- Run an aging analysis on every open exception and calculate expected curtailments.
- Obtain sign-off from the controller once exceptions are documented and closed or escalated.
Assign VIN ownership so one person tracks each unit from floor to payoff, and attach supporting documentation (bank remittance, retail contract, payoff confirmation) to every entry, retained for at least the length of your lender’s audit cycle. A practical calendar runs from day minus 15, when weekly checks tighten, through day plus 3, when the controller signs off on the closed reconciliation. The OCC’s Comptroller’s Handbook recommends inspection frequency proportional to risk, which is a useful anchor for how often to tighten this cadence during high-volume months.
Fixing mismatches: workflow and journal entry patterns
Once you’ve identified an exception, the fix usually touches the same handful of accounts: floorplan payable, inventory, we-owe or trade payables, interest expense, and the operating account that funded the payoff.
- A payoff that’s posted at the bank but not yet reflected in your books gets a debit to floorplan payable and a credit to cash, backed by the remittance confirmation.
- A unit that’s sold but still shows an open floorplan balance needs the inventory relieved and the floorplan payable cleared in the same entry, cross-referenced to the retail contract.
- A curtailment payment gets booked as a reduction to floorplan payable with the corresponding cash outflow, tied to the lender’s curtailment schedule rather than an estimate.
Every correcting entry should carry its supporting documents: the bank remittance, the retail contract, or the loan payoff confirmation. Dual authorization on entries above a set dollar threshold keeps one person from clearing an exception without a second set of eyes, which matters when an examiner or auditor asks to see the trail. The OCC’s guidance on inventory financing points to written verification and physical testing as the baseline for defensible collateral reporting, and your journal entries should be able to stand up to that same standard.
Tools and automation that speed VIN-level reconciliation
Manual reconciliation eats hours because most of the work is formatting, not analysis. The highest-value automations handle structured lender imports, normalize VIN formatting automatically, match payoffs without manual lookup, and log every action for audit purposes.
- Structured statement imports remove the re-keying step that causes most VIN mismatches.
- Automatic payoff matching flags exceptions the same day a statement lands, instead of at month-end.
- Per-VIN cost and profit tracking keeps the floorplan balance tied to the same record you use for margin reporting.
- Audit logs capture who cleared an exception and when, which is the documentation lenders and examiners ask for first.
Loturn is built around this per-VIN approach: native dealer accounting, secure statement imports, and onboarding support that gets historical data loaded rather than re-entered by hand. Whatever tool you choose, demand exportable reconciliation reports, attachment storage for supporting documents, multi-user approval steps, and clear data provenance on every imported record.
Pro Tip: Pilot any new reconciliation tool with a single lender first. Document your exception rules on that one relationship before rolling it out across your full floorplan.
What controllers get wrong about the reconciliation timeline
Most reconciliation problems trace back to staffing, not accounting knowledge. Assign one owner per VIN from floor to payoff, and cross-train that person on both the DMS and the lender statement so the same set of eyes sees the whole trail. Title control and sales desk documentation requirements prevent more exceptions than any reconciliation process ever will, and a clear escalation trigger, a fixed number of days past due before you call the lender, keeps small delays from becoming aged deficits.
— Eric Dosset
How Loturn helps close floorplan reconciliation faster
Independent dealers often lose the most time on the same VIN mismatches this article walks through, and Loturn was built to close that gap without adding another spreadsheet to the month-end routine. The platform supports per-VIN reconciliation, structured statement imports, GL tie-outs, and audit logs that hold up when a lender asks for documentation.
- Import lender statements and see the VIN-level exceptions surface automatically.
- Pilot the process with a single lender or lot before rolling it across your full floorplan.
- Compare pricing across the Flipper, Dealer, and Multi-Lot plans to find the fit for your dealership’s volume.
For background on how curtailment math and floorplan interest actually work, the floor plan financing guide and floorplan interest accounting pages walk through the mechanics in more depth.
Sources
Keep these on hand for lender inspections, audits, and internal control documentation.
- FDIC: Floor Plan Lending (Risk Management Manual of Examination Policies)
- OCC: Floor Plan Lending, Comptroller’s Handbook
FAQ
What is a 3 point reconciliation?
A three-point reconciliation typically compares the lender’s floored-unit statement, the dealer’s DMS inventory record, and the general ledger floorplan liability for each VIN. The goal is confirming all three sources agree on which units are financed and at what balance.
How do you perform a general ledger reconciliation?
A general ledger reconciliation compares the GL account balance, in this case floorplan payable, against an independent source, such as the lender’s statement, then investigates and clears any difference. For floorplan accounts, that independent source should be checked at the VIN level, not just as a summary total, since summary totals can mask individual unit exceptions.
Does floorplan inventory need to be reconciled every month?
Most lenders expect a full reconciliation at month-end, with lighter checks run weekly to catch payoffs and sales as they happen. The FDIC’s examination guidance treats regular, documented floor checks as a standard part of sound lending controls.
Can you give an example of floor plan financing?
Floor plan financing is a line of credit a lender extends to a dealer to purchase inventory, with each vehicle serving as collateral until it’s sold and the loan is paid off. The OCC’s Comptroller’s Handbook describes this as typically structured as a three-party arrangement between the dealer, the lender, and sometimes the manufacturer, with curtailment schedules requiring partial paydown as units age.