DEMURRAGE COURT
What it's designed to do: Audits railroad demurrage invoices car by car against your own records, and shows exactly where they disagree.
[ THE PROBLEM IN THE FIELD ] internal · product spec
Railroads bill demurrage when cars sit past free time. The invoice arrives with placement and release times for each car, but the records to check it against sit with the terminal, the plant and the car traces, in pieces. Lines nobody checks get paid. A dispute that does get raised is an email with a spreadsheet, and the railroad can't tell which numbers came from where.
What it's designed to do.
internal · product spec and gate record
- Designed to read the railroad's invoice next to your own car events.
- The engine recomputes each car's clock under the tariff terms.
- The engine audits each invoice line car by car against your car events, and names the differences it finds.
- Designed to keep records that came from the railroad marked as the railroad's, so they don't count as independent proof.
- Dispute handling exists in the engine; the app is not built yet.
[ WHO IT'S DESIGNED FOR ] by role · internal · product spec
Rail logistics analyst
Will own the audit: bring in invoices and car events, review every difference and draft the case.
Fleet manager
Will keep the roster of leased cars and check which of them were billed, and how.
Accounts payable
Will see what each invoice says is owed, what the record computes, and what is in question.
Controller
Will approve the tariff terms and what leaves the building.
Auditor
Will check that the record and every exported figure verify.
[ WHAT'S PROVEN ] internal · gate record
A second implementation, built separately on a different AI model, agreed on 1,000 of 1,000 clock cases and on every finding in eight test audits.
[ HONEST STATUS ]
Audit engine proven. The app is not built yet.
[ SCREENS ]
No screens are published for DEMURRAGE COURT on this site.