Money leaks between the contract and the invoice
Leakage found with its evidence, quotes checked against should-cost, and savings counted only when they reach the invoice.
What goes wrong today
Buyers negotiate from memory and last year's price.
Invoices come in above the contracted rate, items are bought off contract from suppliers who were never preferred, and the same invoice is sometimes paid twice. Each leak is small. Together they are a line in the P&L that nobody owns.
When a supplier asks for an increase, there is no independent view of what the item should cost. Volume drifts onto one supplier because it is easy, until that supplier slips and a line stops. Savings announced in review meetings rarely show up in the accounts.
Why existing approaches fall short
- ERP purchasing records each buy faithfully, but it does not compare every PO line with the contract, the preferred-supplier list and past invoices.
- Price benchmarks bought from outside rarely match your specification, grade or region, so buyers fall back on gut feel.
- Savings trackers count a saving when it is agreed, before any invoice proves the new price was paid.
How FLX4 addresses it
-
FLX4 checks purchase data line by line for five leaks: off-contract buying, non-preferred suppliers, prices above the contracted rate, contract-versus-PO overpayment and duplicate invoices. Each finding carries its money impact and the documents behind it. A should-cost band built from your own PO, GRN and invoice history plus public price indices shows whether a quote is fair, and abstains when the history is too thin.
-
RFQs run through a supplier portal with sealed quotes, documents and negotiation rounds on a tamper-evident log. An optimizer proposes the award split within MOQ, share and lead-time limits, and a supplier-health check stops a split that would leave you on one fragile supplier. In OpsNest, shortfalls found against the production schedule become draft POs, and suppliers acknowledge and update dispatch in their own portal. Freight is bought the same way in TransNest, where tenders and spot bids are ranked on price and carrier reliability.
-
SourceNest runs the leakage checks, the should-cost bands and the RFQs. OpsNest runs the PO flow, and TransNest runs the freight tenders. There is no automatic PO. Awards and POs always go to a named approver.
The loop, step by step
- 1 · Predict
Find the leak
Every PO and invoice line is checked against contracts, preferred suppliers and past invoices. Findings are ranked by money, with the evidence attached.
- 2 · Predict
Check the quote
A should-cost band from your own price history and public indices shows how far a quote sits from fair. When history is thin, there is no band, and the tool says so.
- 3 · Decide
Run the RFQ and split the award
Sealed quotes arrive through the supplier portal. The optimizer proposes a split within MOQ, share and lead-time limits, checked against supplier health.
- 4 · Approve
A sourcing approver signs
Awards go to the sourcing approver and escalate above the impact ceiling. POs route by value to the right approver in a maker-checker flow.
- 5 · Execute
Draft, never auto-buy
An approved award becomes a recommendation package, or a draft in your ERP where that connector is configured. Approved POs reach the supplier in the portal, where they are acknowledged and dispatch is updated.
- 6 · Learn
Count only realized savings
Savings are tracked from identified to accepted, implemented and realized. Every human edit to a recommendation is kept with who made it and recalled on similar decisions.
What it helps you work toward
Outcomes are measured against a baseline we agree with you in writing.
Leakage found and recovered
Leakage value identified, disputed and recovered, by detector and supplier
Prices paid against fair
Share of PO value paid above the should-cost band, by category
Savings that reach the P&L
Savings by stage, from identified to realized on the invoice
Supplier reliability
PO acknowledgement time and on-time, in-full delivery, by supplier
What powers this solution
SourceNest
Know whether a quote is fair before you negotiate, and stop paying more than you agreed.
Explore SourceNest →
OpsNest
When a line stops or a vendor slips, the plan and the POs keep up.
Explore OpsNest →
TransNest
See the late truck before your customer does, and pay only the freight your contract allows.
Explore TransNest →Integrations
SourceNest works with ERP purchasing and finance data (e.g. SAP MM and FI, Tally), and OpsNest with your ERP's purchase orders (e.g. SAP); connectors are configured per deployment. Supplier and co-packer portals run inside FLX4. Public price indices are loaded per deployment.
Bring us the decision behind this problem
In two weeks: the decision mapped, where money leaks, a baseline agreed in writing and a ninety-day plan with one target.
Read-only on day one. Your people approve every action. If the number does not move, you do not scale.