CEDX Procurement · Finance
214 open purchase orders worth $7.18M — and half of issued spend bypassing catalog or contract. Procurement scores the maverick spend, prices the unit-price leakage at $552K, and queues the $99K worth recovering first.
A leak here is not “savings opportunity”. It is PO-9076: $12K over because the unit price missed the contracted tier by $3.59 — recover, renegotiate, or accept, with the delta printed.
Runs on demo data — the leak board prints its own math: “unit variance × qty”.
What it is
181 rows off policy, ranked: a $102K ISP order at 95% breach, a $109K studio buy at 100% — issued without catalog or contract. The policy-cap simulator shows what a $32K free-form cap would do: residual $1.13M, blocked $3.38M.
184 rows where unit price beat the contract — tier miss, price miss, or no contract at all. PO-9041 to a caterer leaks $12K at $836.83 a unit; the recover queue holds 11 rows worth $99K with the decision on the row.
The PO book carries status, amount, need-by date and received percentage per row: a $17K order fully received, a $409 order at 48%, a $52K order on hold. Receipt match across the book: 73%.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/procurement.
01 — Overview
Open POs $7.18M, on-contract share 50%, receipt match 73%, 168 items blocked on approval. Alerts price the leaks: an $18.2K marketing buy issued free-form, a foam rate $4,900 over contract, and 5 contracts expiring soon worth $489K.
02 — Maverick
The ranked board shows 34 rows in view of 181: risk score, tier, PO, vendor, amount, breach percentage and decision. Nine high-tier rows carry $872K — the simulator prices what a stricter cap would stop.
03 — Savings leak
Leakage rows carry score, PO, vendor, leaked dollars, unit delta and reason. A telecom PO leaks $12K on a tier miss; a freight PO leaks $11K at $2.46 a unit; the renegotiate chip is for the rows with no contract to enforce.
04 — Purchase orders
320 POs from draft to received with need-by dates and receipt percentages. The held rows — $103K to one vendor, $52K to another — are visible before they become receiving-dock surprises.
Who runs it
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Works the maverick board and the recover queue — $99K of overcharges with the unit delta already printed, vendor by vendor.
recover queue · $99K
Clears the 168 items blocking issue — $5.3M of buying waiting on a decision, visible instead of buried in an inbox.
168 pending · $5.3M
Reads on-contract share and receipt match as cash truth: 50% and 73% are the numbers the forecast quietly depends on.
50% on-contractThe shape of it
Every figure below is legible in the captures above. Nothing here is a projection of your estate — it is the state of the demo data.
How it runs
Buying starts as a requisition or a PO draft — 36 drafts sit unissued, and 168 items are blocked waiting on approval.
Issued POs become commitments: 214 open worth $7.18M, each with need-by date and receipt percentage from issue onward.
Goods land against the PO: receipt match reads 73% across the book, and partial receipts keep their open commitment visible.
Leakage is priced against the contract — unit variance × quantity — and queued: recover $99K now, renegotiate what has no contract, accept the rest knowingly.
One record
These captures come from one demo workspace — Northline Outfitters — so the vendors and commitments here are the same ones the rest of the finance apps carry.
Where received POs become bills — the invoice-captured, PO-referenced rows on the bills screen start here.
CEDX SpendWhere requests and card spend are cleared or escalated — before they become the maverick rows on this page.
CEDX InventoryWhere the received goods go — stock levels and shelf truth on the other side of receipt match.
Limits
Finding this out on the third call is worse for you than reading it here, and worse for us.
Start
Open it right now
Your vendors, your contracts
Procurement with the rest of it
Questions
Yes. Every screenshot is a capture of the running build and you can open the same build at /app/procurement. It runs on demo data.
Unit variance × quantity, as the screen itself states: what the PO paid per unit against what the contract said, times how many units. 184 rows sum to $552K, and 11 of them — $99K — sit in the recover queue.
Spend issued without catalog or contract — 181 rows worth $4.51M open, each with a breach percentage. The free-form marketing buy at $18.2K is the overview's example, priced on screen.
Quantity received against quantity ordered, per PO — 73% across the demo book. Partial receipts are their own state, so a 60%-received $86K order keeps its open commitment visible.
No certification has been issued. What we can evidence about hosting, encryption, tenant isolation and production access is written up on the security page.
Live build, demo data, no card. Then pull your own unit-price variance and compare the number.