02 — The solution
We build the story that connects the invoice to the anchor — and the funder lends against the story.
Instead of a program, we assemble evidence. With permissioned access to the documents
already moving between ERP systems, we reconstruct the chain behind a single invoice: anchor purchase
order to tier 1, tier 1 purchase order to tier 2, goods delivered, invoice raised. That linked record
is what a funder bank underwrites — the transaction, not the tier 2's balance sheet alone.
Anchor / OEM
Demand originates
A build plan turns into a purchase order or contract issued to tier 1. Investment-grade credit,
documented commitment.
↓ PO / contract — via ERP
Tier 1
Demand cascades
Tier 1 issues its own purchase order to tier 2 for the parts, castings or material it needs to
fulfil the anchor's order.
↓ PO — via ERP
Tier 2+
The financeable event
Tier 2 delivers and raises an invoice on tier 1. That invoice traces directly back to tier 1's
purchase order — and through it, to anchor demand.
→ Funder finances this invoice
No program to stand up
Neither the anchor nor tier 1 contracts a facility, opens a treasury workstream, or takes the
obligation onto its books. Participation is data permission, not a credit commitment.
Verification, not self-declaration
We sit between the parties as an independent layer, corroborating that the invoice, the purchase
orders and the delivery describe one real transaction — and flagging when they don't.
Data flows both ways
In exchange for ERP visibility, the anchor and tier 1 get back what they never had: a mapped
deeper supply base with financial-health and criticality signals on the firms inside it.