The programme is ready. The base isn’t.
Ask a corporate treasury team why a supplier-finance or reverse-factoring programme is running below its limit and the answer is rarely lack of appetite. The lender is willing; the anchor is willing. What stalls is further down: a supplier with no verified business identity, a vendor that has never once responded to an early-payment offer, a cluster of names the programme has simply never assessed. The financing conversation reaches each of those and stops — not on a credit judgement, but for want of evidence that the counterparty is who and what it claims to be.
The frustrating part is that most of that evidence already exists. It sits inside the anchor’s own records — the relationships it transacts with, the programmes it runs, the payment behaviour it has already observed. It is just scattered across a vendor master, a payments system and an inbox, and nobody has assembled it into one picture.
Why a readiness “score” fails the lender
The instinct is to reduce all of that to a number — a supplier readiness score. It is the wrong instrument, for the same reason a blended credit number is: a single figure hides the one thing a lender needs, which is the reason. “Supplier X: 62” tells a credit officer nothing they can act on. Is it 62 because the identity is unverified, because the vendor has never participated, or because the anchor concentrates half its spend on that one name? Each is a different problem with a different fix, and a score collapses them into noise with a decimal point.
Evidence behaves the opposite way. A readiness band that reads “Limited — no verified DigiKYB identity, three early-payment offers made and never accepted” is something a lender can weigh and an anchor can act on. It carries its own justification. And because it is built from named, dated, source-linked records rather than a model, it can be re-checked — and trusted by a party that did not compute it.
What the anchor uniquely holds
An anchor sits on a vantage no lender and no bureau has: the records of its own trade. It knows which suppliers it actually transacts with, how much and how recently; which ones took an early payment and which ignored every offer; where its own reverse-factoring programmes stand. Layer a consented DigiKYB verification status on top — is this supplier a verified business identity or not — and the anchor can answer the first question any financing conversation asks, before it is even asked.
Read as a graph rather than a spreadsheet, that base shows what a list cannot: node size for observed face value, edges for participation, dashed where a supplier has never engaged, and top-1 / top-3 concentration surfaced when the base leans too hard on too few names. The readiness gaps stop being a vague worry and become named suppliers you can do something about — nudge the non-responders, invite the unverified to complete DigiKYB, and watch the bands move as evidence accrues.
Evidence, not funds — and not a decision
One boundary matters, and it is deliberate. Turning a supplier base into an evidence map does not turn the anchor into a lender. The map is computed only from records the anchor is a party to — its own relationships, its own programmes, consented DigiKYB status. No lender’s consented data, borrower intelligence or workflow state leaks into it. Readiness bands are signals, not decisions; every credit and payment call stays with the anchor and its lenders. The aim is not to price risk or move money — it is to make the suppliers a programme could reach visible, and the ones it stalls on fixable.
That is what AssureSupplierGraph does: it assembles the picture an anchor already half-holds into one evidence-backed map, so a financeable supplier base stops being an aspiration and becomes something you can see, close the gaps on, and hand to a lender with the reasons attached. The quickest way to grasp it is to click through the network explorer on representative data.