Inventory Curtailment and Floorplan Payment Tracking Log

This template records floorplan curtailment activity, paydowns tied to sold units, and interest cost by inventory age in one place. It is meant to support monthly or periodic reconciliation between what was scheduled, what was paid, and what still needs follow-up. The log also captures variance reasons and review status so exceptions do not get lost.

Most teams complete it on the same cadence as their lender reporting or floorplan payment cycle, often weekly or monthly. If inventory turns quickly or payment timing varies by location, a shorter cadence helps catch missed paydowns sooner. The reporting period field is there so each entry can be tied to a specific close or statement window.

It is usually maintained by accounting, controller staff, inventory finance, or dealership operations personnel who can verify payment records and unit status. The prepared_by field makes ownership clear, while review_status supports a second set of eyes from finance leadership or a manager. If multiple locations are involved, each site can submit its own log for consolidation.

Scheduled curtailment is the amount expected to be paid under the floorplan schedule, while actual curtailment paid is the amount that was actually remitted. The difference can show timing issues, partial payments, or exceptions that need explanation. This template keeps both fields visible so variance review is straightforward.

When a unit is sold, the log captures the count of units sold, the paydown per sold unit, and the total paydown amount. If a sold unit is exempt from a paydown or handled differently, the paydown_exception and notes fields document why. That helps prevent silent gaps between sales activity and lender remittance.

Yes. The location field can be expanded into store, branch, or lender-specific reporting if needed, and the age bucket section can be adapted to match your internal inventory aging bands. You can also add conditional logic for exception notes, approval fields, or lender-specific payment references without changing the core structure.

Teams often populate it from inventory systems, sales records, lender statements, and payment confirmations. If your workflow supports imports, the age bucket and unit counts can come from inventory reports while payment status and dates come from accounts payable or bank activity. The key is to keep the source of truth clear for each field.

Common issues include mixing scheduled and actual amounts, leaving variance reasons blank, and failing to tie sold-unit paydowns to the correct reporting period. Another frequent problem is using free-text notes instead of clear payment status values, which makes review harder. This template works best when required fields are kept tight and exceptions are documented immediately.