Accessorial Cost Recovery: Bill Back the Charges You're Eating

The problem this kills

A driver waits four hours at a customer's dock and you owe detention. A container sits past free time at the port and demurrage piles up. A reweigh, a layover, a redelivery, a lumper fee — every week your operation incurs accessorial charges that, under the contract, the customer is supposed to pay. But by the time anyone goes looking, the moment has passed: the proof of delay is buried in a tracking system, nobody remembered which contract terms applied, and the charge quietly gets eaten as a cost of doing business.

That leakage is real money, and it's recoverable money. The information you need is sitting right there — the timestamps, the gate-out records, the carrier invoices, the contract that says "detention beyond two hours is billed to shipper." What's missing is something that catches every incurred accessorial, lines it up against the rule for who pays, assembles the evidence, and puts a ready-to-send bill-back in front of the right person. You do not need to be a developer to build that.

What you'll build

A simple internal web tool for your billing/AR team and account managers. You import your incurred accessorials (the detention, demurrage, layover, lumper, and other charges your company got hit with) and your customer responsibility rules (what your contracts say about who pays what, and the thresholds). The tool matches each accessorial to the customer who owes it, drafts a bill-back with the dollar amount and the supporting evidence attached, and routes it to the responsible account manager. The AM reviews each draft and clicks Approve or Reject — with a reason. Only then is the charge issued: the tool exports a customer charge file in the columns your billing system expects, plus a recovery log of everything billed, held, and why.

What's inside the Implementation Plan

The downloadable plan is a step-by-step file you paste into an AI coding agent. It opens by interviewing you about your business — your current recovery process, the systems and spreadsheets you use, the exact accessorial codes and customer naming in your data, your typical and peak volumes, and the real contract terms for who pays each charge type. It reads a short spec back to you for a thumbs-up, then builds the tool around your answers instead of a generic template. From there it walks the agent through the data model, the CSV imports, the rules engine that assigns responsibility, the evidence attachment, the bill-back drafting, the account-manager approval gate, and the customer-charge and recovery-log exports. Every step ends with a ready-to-copy prompt.

The governance it includes (this is the point)

This isn't a toy. The plan builds in the controls a real billing function needs: login so only your team can use it, row-level security so people only see their own organization's charges, a complete audit trail of every draft, approval, rejection, and override (who, what, when, and why), a hard human-approval gate so no charge reaches a customer until an account manager signs off, and duplicate guards keyed on shipment + accessorial so the same charge can't be billed twice. The whole tool exists to make a careful human decision easy — the AI drafts the bill-back, a person decides whether it goes out.

Who it's for

Billing and AR specialists, account managers, and revenue-recovery leads in trucking, freight forwarding, 3PL, and brokerage who know they're leaving accessorial dollars on the table. If you can describe what your contracts say about who pays detention and demurrage, you can build this.

You've got this — open the plan, paste the first prompt, and you'll be matching your first real accessorials to the customers who owe them this weekend.