Past Due Report

Lists every open purchase order line whose delivery date has already passed, worst first, with anything the supplier has said about it.

ReadsERPSupplier email

You get · Table on screen

Problem: Past due POs are found the reactive way: production is already short, or somebody pulls the report by hand to go looking.
Impact: The ERP reflects that a line is past due and nothing more. Someone still has to chase every supplier for a status before any of it means anything.
Solution: Proactively identifies every past due PO instead of waiting for production to raise it, and scans supplier email for what has already been said about each one. The status and the next step are on one screen.

01 · What it looks like

The real screen, from a real run.

Nothing here is a mockup. These are captures of the working app against a live ERP, and the numbers in each caption are the numbers in the picture above it.

The Past Due Report output: 32 lines past due across 15 suppliers, worst first, with days past due, open value, and what the supplier said. — 32 lines past due across 15 suppliers, $67,582.50 still owed, the worst line 29 days out. This is the list that exists nowhere in the ERP: it gets rebuilt by hand, and it is out of date by the time it is built.

The same Past Due run filtered to the five lines the supplier has written about, each showing the message and its date. — The same run, filtered to the five lines the supplier has already written about. A price change on PO-4711, an invoice sent ahead of the shipment on PO-4702. That is the part the ERP does not record, and it is the difference between a list of late lines and knowing which call to make first.

See the other tasks How Ask Mack works →

Which of these is your Monday morning?

Book an assessment and we will map the repeating work in your plant, then show you what the first build looks like against your own systems.

Book an Assessment Explore Project Foundry →