Skip to main content

Cash Flow & Funding Velocity

Cash-in-transit is the first quiet leak

Contracts past day seven are not a finance inconvenience. They are a cash-conversion failure with lender, compliance, and management-control consequences.

Dan Douville·COO & Co-CEO, former multi-brand dealership CFO·April 18, 2026·~1160 words

The problem is not the old contract

Most dealerships treat cash-in-transit as an aging report. The finance office submits the deal, accounting watches the receivable, and the controller chases the lender when the number gets ugly. That workflow explains the balance. It does not control it.

CIT is the period where the dealership has delivered the vehicle, recognized the sale operationally, and still has not converted the receivable into cash. In a tight month, the difference between day four and day eleven is not cosmetic. It changes bank-line pressure, floorplan cadence, payroll comfort, and the dealership principal's appetite for taking the next deal.

The dangerous part is that the accounting report usually looks precise. It has deal numbers, dates, lenders, and balances. Precision makes the report feel like control. But most CIT reports answer only one question: how old is this receivable? The operational question is different: why did this deal become old, and what gate would have prevented it?

Aging is a symptom

A contract can sit because a lender is slow. It can sit because a packet is incomplete. It can sit because a rate approval expired, a stip was not collected, a signature page was missed, the lien payout was not validated, the funding desk changed rules, or the F&I office submitted late in the day with no same-day review path.

Those causes require different responses. Calling the lender does not fix packet quality. Coaching packet quality does not fix a lender that has quietly become slower than the store baseline. Escalating every old contract to the CFO burns management time if the underlying delay is a missing field that could have been blocked at submission.

The mistake is treating day count as the control. Day count is only the smoke alarm. The control is cause-coded aging by lender, advisor, product path, stip pattern, approval path, and submission completeness.

The real report is cohort movement

A useful CIT view starts with cohorts. Deals submitted to the same lender under the same approval path should fund inside a tight range. If they do not, the first question is whether the variance follows the lender, the advisor, the product mix, or the documents.

When one lender drifts from a four-day median to an eight-day median, the store needs a routing conversation before the month closes. When one advisor is consistently three days slower than peers across multiple lenders, the store needs a submission-quality conversation. When deals with one product path are slower, the store needs a documentation checklist review. The same receivable balance can point to three different operating fixes.

This is why aggregate CIT is a weak metric. It tells you how much cash is trapped. It does not tell you whether the trap is policy, people, lender behavior, document quality, or timing discipline.

Why this matters to lenders

Slow funding is not only a dealer cash-flow issue. It affects lender confidence. A lender that receives incomplete packets, repeated rework, and late stip responses will not treat the store as operationally clean. That matters when the store wants faster approvals, more consistent funding exceptions, better relationship attention, or a smoother annual review.

The dealership usually experiences lender friction as individual annoyances. The lender sees a pattern. The store needs to see the same pattern before the lender does.

A disciplined CIT workflow gives management a defensible story: here is our median by lender, here is our outlier path, here is the packet error rate, here is the corrective gate, and here is the result after the gate went live. That is stronger than apologizing for old contracts at month end.

The control that changes behavior

A hard gate at day seven is useful only if it carries the reason with it. Escalating every day-seven deal with no cause code creates noise. Escalating a deal with the specific missing item, lender path, advisor code, and prior touch history creates action.

The first level is a submission completeness gate. If required fields, signatures, stip references, payout validation, or lender-specific documents are missing, the packet should not leave as complete. The second level is an aging gate. If the deal crosses day seven, the CFO queue receives a concise record: lender, advisor, contract value, days outstanding, cause code, last action, and next required action.

The third level is management review. Every week, the store reviews only the patterns, not every deal. Which lenders slowed? Which advisors created rework? Which document fields created repeat exceptions? Which overrides were justified and which were habit?

What good looks like

Good does not mean zero old contracts. Some deals legitimately take longer. Good means every old contract has a known reason, a named owner, a timestamped next action, and a management-visible pattern if the same reason repeats.

Good also means the store can separate cash pressure from blame. The purpose is not to turn CIT into a weapon against the finance office. The purpose is to protect cash by making the causes visible early enough to fix them.

When CIT is treated as a control system rather than an aging report, the dealership gets something more valuable than a cleaner month end. It gets a faster cash-conversion culture.

mini-audit

See where this pattern sits in your operation.

Free. Seven business days. No third-party product in the bag. If the paid engagement cannot surface recoverable margin within 90 days, it is refunded.

Launch mini-audit