Run a close
One front door for the close: load a bundled sample period to see it priced instantly, or upload the month's shipments (and newly arrived invoices, when you have them). The same deterministic engine prices the accrual in your browser — no server, no database. Each close you run is saved with its inputs and the rate-card version in force, so any prior month reproduces to the cent.
Close history
April 2026 ships with the app (build-time engine run). Every close you run here is saved with its inputs and rate-config version, so it can be reproduced bit-for-bit.
- April 2026$93,530tie-outs pass160 shipments · 23 flags · config v0-bundledbundled
Run the next month
Load a bundled sample to see it priced instantly, or upload your own. Shipments CSV is required (the month being accrued); add the invoice CSV for newly invoiced months when it arrives — the engine recalibrates and the window rolls forward. Same schemas as the challenge files; nothing is invented, every fallback is flagged.
Rate source: Peak calibrated · Heartland calibrated · Coastal calibrated — change on the Rates tab
Where the data comes from
Today the close runs on CSV exports (or a bundled sample); the roadmap is direct connectors into the same engine — no spreadsheets in the loop.
The engine is the same either way — only the ingestion changes. CSV keeps the build zero-server and the data on your device today; a direct 3PL / TMS feed (shipments), carrier-portal pulls (rate cards + invoices), and a NetSuite write-back (the journal entry) would make the monthly close fully hands-off.
Import templates
Download a headers-only CSV in the exact schema the engine expects.