Floor Plan Financing Software Problems: The 6 That Cost Real Money, and How to Avoid Them

Why does the design treat the credit line as the loan?

Because that is how the exposure is reported and how the credit committee talks about it. A dealer has a line, the line has a limit, and utilisation is the number on the page. So the data model gets built around the dealer and the line, with units hanging off it as inventory.

Floor plan does not work that way. It is a few hundred loans standing in a trench coat. Every vehicle, boat, coach, tractor or skid steer on the lot is a separate advance with its own invoice amount, advance date, accrual, curtailment schedule, title location and payoff. The line is an aggregate for reporting and nothing more. Model it as the primary object and every question that matters becomes a reconciliation exercise: which units are unpaid, which are unaudited, which have a title you no longer hold.

Make the unit the object and give it its own clock. Advance, accrual, curtailment schedule version, audit events, exceptions, cures, payoff allocation and title custody all attach to the unit, and the dealer line is derived from the units rather than the other way round. This is not a preference. It is the difference between a system that can answer a question in seconds and one that hands you three numbers from three places and lets you sort it out in Excel, which is exactly the Tuesday morning that started the project.

What goes wrong when you migrate live units, accruals and audit history?

Everything in this portfolio is mid stream, which makes migration unusually unforgiving.

The first failure is loading a current curtailment position rather than the schedule that produced it. Without the schedule version and its effective date, the system cannot state what a unit owed on a past date, and the first dealer dispute after go live exposes it.

The second is loading accrued interest as a balance rather than as the accrual basis. Rates change, subsidy periods end, and a balance carries none of that, so the next recalculation quietly disagrees with the statement you already sent.

The third is dropping audit history entirely because it lives in PDFs. That history is the raw material for everything useful you will do later, including ranking dealers by exception risk, and once you launch without it you are two years from having it again.

Migrate the rule and the transaction, never the answer. Every unit carries its program, its schedule version and its advance and payment transactions. Then run in parallel: load the live portfolio into the new ledger, run both systems for two full curtailment cycles, and reconcile daily until the differences are explainable rather than surprising. That parallel period is where the undocumented exceptions surface, and it is real cost rather than overhead.

Why do dealer system, title and payment integrations break after launch?

Three integrations, three separate competencies, and they are routinely priced as one.

Dealer management system feeds from CDK, Reynolds and Reynolds or Dealertrack are individually negotiated and individually slow, and they break commercially more often than technically: a dealer withdraws consent, or a group changes provider, and the detection improvement you built your risk model around disappears for that dealer. They also cannot be trusted as a control, because a dealer hiding a sale will not expose it in a feed you can see.

Electronic lien and title is state by state, each provider has its own certification, and your reality will be mixed: some jurisdictions fully electronic, others still moving paper you hold in a vault with a filing cabinet as the source of truth.

Payments break on allocation. A single wire or automated clearing house payment covers nine units, sometimes with a remittance advice and sometimes with a subject line that says payoff. Allocate to the wrong units and the curtailment clocks on the remaining ones are now wrong too, which is a silent error that compounds.

Build one title custody record per unit carrying the state, the mechanism, the current holder and the release conditions, then add provider integrations in order of portfolio concentration and budget each as its own certification effort. Apply cash by rule with a review queue for anything ambiguous, and release titles on cleared funds rather than received funds.

What happens when audit exceptions and title custody are not covered?

These are the two omissions that let a loss stay hidden.

The audit is your only real control, because everything else in wholesale finance is derived. It is the one moment somebody physically confirms the collateral exists. In most shops that moment ends as a scanned spreadsheet from one of several audit firms, each with its own column layout, emailed to a shared inbox. Handled that way, the exception taxonomy that carries all the risk collapses into a single line item. Unit not found, unit sold with payoff pending, unit at a satellite location, unit out on demonstration, unit at a body shop, unit wholesaled to another dealer and duplicate identification number from a re-flooring each have a different cure clock and a different escalation. In email, cures get missed and a sold out of trust unit hides behind an unresolved not found for six weeks.

Title custody is the other. If nobody can say where a title is, you cannot tell whether an unpaid unit is a timing issue or a loss.

Make the exception a case with an owner and a cure deadline, produced by an audit event rather than by an email. Give auditors mobile capture with barcode and identification number scanning that works offline, because back lots have no signal. Then the exception queue, not the audit report, becomes the thing your risk committee reads, and an ageing not found stops being invisible.

Should you build custom or configure what you already own?

If you fund a few hundred units on one manufacturer program with a standard curtailment ladder, your audits already arrive as structured output, and your title work is entirely electronic, configure rather than build. Solifi and NETSOL Ascent are credible asset finance platforms with solid contract accounting, and Sopra Banking Software Cassiopae occupies similar ground. Configuration will take a quarter, and a custom build would be an expensive way to arrive at the same ledger.

Keep configuring even at larger sizes for the parts these platforms genuinely do well. Contract accounting, interest calculation and general ledger posting are solved problems and rebuilding them adds risk without adding control.

Where they thin out is the floorplan module, which encodes a generic curtailment ladder and a generic audit cycle and expects your programs to bend into it. Build when two or more are true: you run three or more programs with variations negotiated at dealer level, your exceptions live in a spreadsheet one person maintains, you have taken a sold out of trust loss in the last two years where the post mortem said the data existed but nobody joined it, you fund collateral classes with no reliable sales feed, or you securitise and assemble investor reporting by hand each month.

How do hidden costs get into the quote?

• Programs counted as configuration. Each manufacturer or captive program is a rule set plus its own reporting, and the third one is not cheaper than the first.
• Title integrations priced as a feature. Each state provider is a separate integration with its own certification timeline, and none of them move at your pace.
• Dealer system feeds assumed available. These are commercial negotiations before they are technical work, and the calendar belongs to somebody else.
• Non automotive collateral treated as a variation. Marine, recreational vehicle, powersports and agricultural units have inconsistent serial number conventions and no clean sales feed, which changes both matching and detection strategy.
• Parallel running left out. Two full curtailment cycles of daily reconciliation is where undocumented exceptions surface. Budget it as project cost, because it is.
• Securitisation reporting discovered late. Investor level reporting on a wholesale facility is a project in its own right rather than a report on top of the ledger.

The honest bands from Digital Heroes delivery experience: $90,000 to $200,000 over 14 to 20 weeks for a first release covering the unit level ledger, an effective dated curtailment engine, mobile audit capture and exception workflow, and $250,000 to $700,000 over 9 to 18 months for a full platform adding dealer portal, title integrations, dealer system feeds, cash application and early warning scoring.

What separates a build that works from one that fails here?

Make them whiteboard the unit lifecycle before you sign anything: advance, accrual, curtailment schedule version, audit event, exception, cure, payoff allocation, title release, and the dealer agreement governing all of it. A team that has done asset finance draws effective dated rules without being prompted. A team that draws loans and payments has built a consumer lending application and is about to learn wholesale on your budget.

Ask specifically how they will answer what a unit owed on a date in the past after a program change in the interim. If the answer involves recalculating from current rules, stop there, because that single behaviour will cost you every dealer dispute and confuse every audit trail.

Ask what they have integrated by name: which electronic lien and title providers, which dealer management systems, which core banking or general ledger system. Ask for the named provider and the named document rather than a claim about integrations generally.

Ask what they will refuse to automate. Predicting fraud is a good answer. Reading audit documents and remittance advices into structured records is where automation genuinely earns its place, because it is dull, high volume and currently retyped by hand.

Then get code ownership in the contract before kickoff: the repository, the cloud accounts and the unrestricted right to hire another firm. At Digital Heroes the client owns everything from the first commit. In lending, where a regulator, an auditor or a securitisation investor may one day ask how a curtailment number was produced, that ownership is your ability to answer rather than a commercial preference.