Chassis Usage & Billing Reconciler
Log chassis out/in events, compute billable days, and reconcile them against pool invoices so chassis overbilling gets caught before you pay it.
An internal tool that logs every chassis out/in, computes billable days your way, compares them to the pool invoice line by line, flags every variance, and makes an auditor approve a dispute-or-accept decision before anything is paid - with a full audit trail and a dispute log you can hand to the pool.
Before you start
- Your chassis out/in event records (CSV export is fine)
- Your chassis pool invoices (CSV export is fine)
- Free accounts: Vercel, Supabase, Resend
- No coding experience required
The problem this kills
Chassis pool invoices arrive as a wall of line items, and somewhere in that wall you are being overbilled. A chassis got returned on Tuesday but the pool billed through Friday. A free-day window got ignored. An owned chassis got charged as a pool chassis. A move got split-billed across two parties and you ate both halves. Nobody has time to check hundreds of lines against your own gate-out and gate-in records, so the invoice gets paid, and the leakage just keeps leaking.
You already have the truth - your chassis out/in events. You just have no fast, trustworthy way to put your records next to the pool's bill and see exactly where they disagree.
What you'll build
A private internal web app that takes two inputs - your chassis out/in events and the pool invoice - and does the reconciliation for you. It computes the billable days the way your contract says to (free days, owned vs. pool, split-billing), lines those up against what the pool charged, and flags every variance in dollars and days. Then it stops and makes a human auditor decide: dispute or accept. Every approved dispute lands in a clean dispute log you can send straight to the pool.
What's inside the Implementation Plan
The plan opens by interviewing you about your actual operation - your pool providers, your free-day rules, how you tell owned chassis from pool chassis, how split-billing works for you, your real column names and chassis ID formats, and the messy exceptions that trip up every reconciliation. It reads a short tailored spec back to you, you confirm it, and only then does it build. You get a tool shaped to your business, not a generic template.
From there it walks you step by step - in plain language, with a ready-to-paste prompt at the end of every step - through the database, the secure login, the CSV importers, the billable-days engine, the variance flagging, the auditor approval gate, and the dispute log export.
The governance it includes (this is the point)
- Login so only your team can open the tool.
- Row-level security so each company only ever sees its own chassis data.
- A full audit trail - who imported what, who flagged what, who approved which dispute, and when.
- A hard human-in-the-loop gate - the tool drafts the variance findings, but no dispute or acceptance is final until an auditor reviews and approves it. Nothing touches a payment decision automatically.
- Duplicate guards - the same chassis-plus-usage-period can't be imported or billed twice, so re-running an import or a re-sent invoice never double-counts.
Who it's for
Drayage coordinators and freight audit teams who pay chassis pool invoices and suspect (or know) they're leaking money on billable-day errors, free-day mistakes, owned-vs-pool mix-ups, and split-billing. If you can export a CSV and read an invoice, you can build and run this.
You've got this - paste the first prompt and let the agent interview you about your chassis operation.