Reconciliation and reporting · Live · since July 2026
The report discrepancy checker.
Replaced the owner's Excel compare macro: the TMS and the shipper's portal reconciled with a status vocabulary map and seven exception views.
The problem
The owner reconciled the TMS against the shipper's portal export in a macro workbook. Two status vocabularies that never matched, references with suffixes that never joined, and loads present on one side only that never surfaced.
How it works
- A mapping table translates the two status vocabularies instead of comparing strings. Suffixed references join on their base. Loads on either side only are listed, not lost.
- Seven status-gated exception views, specified by the owner, replaced the eyeball pass. Money columns and a no-carrier view came out of his first week of use.
- Since October the portal side arrives by itself from the portal pull bot, and the page says how fresh it is.
// every mismatch is listed with its reason; nothing is auto-corrected on either system
The result
The macro workbook retired. The owner's sample run, 6,386 TMS rows against 604 portal rows, went from a manual afternoon to a page that refreshes itself.
In practice
Schedule of the unattended systems, Central time.
Syncing the Central clock.
Related systems
- Live
The shipper portal pull
The shipper's carrier portal has no feed, so a bot searches it, exports the grid, parses the legacy spreadsheet and feeds two dashboards every 15 minutes.
How it works - Live
The pick tracking board
The shipper's daily tracking sheet lives in the platform now, mirrored against the TMS every 15 minutes and fed by the portal pull.
How it works
Your version of this exists.
Different industry, same shape: a repetitive workflow, a fragile spreadsheet, an inbox someone babysits. Tell me what the manual work looks like and I can usually name the first build in one conversation.