Pre-Shipment PO Financing: A Risk Signals Case Study

How three-party screening surfaces the collusion, capacity, and double-financing exposures that drive pre-shipment defaults — drawn from real patterns in Indian MSME trade finance.

Case StudyAssureLocker Team·11 min read
Published: 21 January 2026Last updated: 14 April 2026Sources reviewed as of: 27 May 2026

The Deal That Looks Fine on Paper

An NBFC is asked to lend ₹50 lakhs against a Purchase Order. A well-known buyer (call it Party A) has issued a PO to an MSME borrower (Party B) for ₹60 lakhs of goods, due in 120 days. Party B will subcontract part of the manufacturing to Party C. The paperwork is clean: a valid GSTIN, an Udyam registration, a signed PO, a plausible delivery date.

On a conventional KYB report, this deal passes. And yet pre-shipment default rates in MSME trade finance run at 8–12%, and most of those defaults were detectable before disbursement. The reason a standard report misses them is simple: it looks at one company. The risk lives in the relationships between three.

The Four Exposures Conventional KYB Misses

Drawing together the recurring failure patterns in Indian pre-shipment lending, four exposures account for the majority of avoidable defaults — and none of them are visible from a single-entity check.

1. Related-Party Collusion

The subcontractor (Party C) turns out to be controlled by the same people as the borrower (Party B) — a shared director, a common registered address, a family link by PAN. The "subcontract" is a mechanism to siphon the loan, not to manufacture goods. Or the buyer (Party A) and borrower (Party B) share directors, meaning the PO that justifies the loan is self-issued.

2. Capacity Shortfall

The subcontractor physically cannot fulfil the order. A firm with three employees and ₹40 lakhs of annual turnover is contracted for ₹18 lakhs of precision manufacturing in 90 days. The bill of materials is not viable. The order will slip, and the loan with it.

3. Double Financing

The same Purchase Order has already been pledged to another lender. Both NBFCs believe they have first claim on the receivable. When the goods ship, only one can be repaid.

4. Post-Disbursement Diversion

The deal is genuine, but once funds land in the borrower's open account, they are diverted to a different obligation. By the time the PO is fulfilled, the cash to repay is gone.

How the Risk Signals Pack Screens the Deal

AssureLocker screens all three parties simultaneously and assembles a single Risk Signals Pack before the credit officer opens the file. Each exposure above maps to a specific, source-cited check.

ExposureSignalSource
Trade relationship real?Invoice history between A↔B and B↔CGST e-Invoice / GSTR-1
Related-party collusionDirector (DIN) overlap + registered-address co-location across all threeMCA21 + GSTN
Capacity shortfallSubcontract value vs. EPFO headcount and 36-month GSTN turnoverEPFO + GSTN
Double / partial financingPre-disbursement registry check + lien registered as funds releaseShared lien registry, recorded in an immutable registry
Diversion (at repayment)Repayment routed through settlement on confirmed deliveryLender-operated escrow

Worked Example: The Hidden Subcontractor

Return to the ₹50 lakh deal. On the surface, Party B and Party C are unrelated firms with distinct GSTINs. But when AssureLocker screens all three:

  • Director overlap: the MCA21 director register shows a DIN that appears on both Party B and Party C. They share a director.
  • Address co-location: the registered place of business for both entities resolves to the same PIN code and building.
  • Capacity: Party C's EPFO record shows four active employees against an ₹18 lakh precision subcontract — flagged as borderline-to-insufficient.
Three-party scorecard for the illustrative ₹50 lakh pre-shipment dealBuyer Party A issues a purchase order to borrower Party B, who subcontracts to Party C. Of five checks, the trade-relationship history is thin, director overlap and address co-location and capacity are flagged, and the lien registry is clean — the pack reads overall FLAGGED. All values are illustrative sandbox data, not a real borrower.Party ABuyer · issues POParty BBorrower · MSMEParty CSubcontractorPOsubshared director + addressRISK SIGNALS PACK · ILLUSTRATIVETrade-relationship history (A↔B, B↔C)THINDirector (DIN) overlap across B & CFLAGRegistered-address co-locationFLAGCapacity: EPFO headcount vs subcontractBORDERLINELien registry (pre-disbursement)CLEANOverall readFLAGGEDDirector overlap is the decisive flag; the lender decides on the assembled evidence.
Illustrative sandbox scorecard — no real borrower. Three separate single-entity reports would clear A, B and C individually; the whole-deal view is what surfaces the related-party loop.

The pack returns an overall risk of HIGH, with the director overlap as the decisive flag. The credit officer sees, in one screen, that the "arm's length subcontract" is a related-party loop — before any money moves. Conventional KYB, looking at each entity alone, would have cleared all three.

Read one signal at a time, each of these looks survivable. A thin invoice history could just mean a new supplier relationship; a shared PIN code could be a serviced office; four employees could sit atop a subcontracted line. The whole-deal view is what changes the reading: the same DIN on Party B and Party C converts every other soft signal into corroboration. The table below is how the case reads when the signals are placed side by side — every value here is illustrative sandbox data, not a real borrower.

SignalWhat it showed (illustrative)Read
Director (DIN) overlapOne DIN appears on both Party B and Party C's MCA21 recordsRelated-party loop — the decisive flag
Registered-address co-locationBoth entities resolve to the same PIN code and buildingReinforces the collusion signal; not arm’s length
Capacity vs headcountParty C: 4 EPFO employees against an ₹18 lakh precision subcontractBorderline-to-insufficient — order likely to slip
Trade-relationship historyLittle prior A↔B / B↔C invoicing on GSTR-1Relationship looks freshly assembled for the loan
Lien registry (pre-disbursement)No prior charge found on the receivableClean — but the lien must be registered at release

The Decisive Moment: Disbursement Integrity

Screening reduces the risk of a bad deal. But the moment that actually decides whether a receivable gets financed twice is disbursement — when the lender first releases funds. After money moves, the receivable is already charged and any loss is locked in. So this is the only point at which double, partial or over-financing can be prevented, and it is where the safeguard belongs.

The mechanism is pre-disbursement clearance: before funds release, the lender runs — within its own credit rules — the Risk Signals Pack (an overall CLEAR / REVIEW / HOLD on the deal) and a registry check against a shared lien registry to see whether this receivable is already charged, in whole or in part. If it clears, the lien is registered in the same step, so the next lender's pre-disbursement check sees it. The principle is simple: no funds leave until the PO is cleared and the lien is registered. AssureLocker never disburses — the lender wires this clearance into its own release step, and AssureLocker provides the signals and the registry it checks and writes to.

Closing the Loop: Settlement Integrity (secondary, on the roadmap)

Disbursement integrity stops the bad deals; settlement integrity helps a good deal stay good. The design: when Party B fulfils the order and Party A confirms delivery, repayment is routed through a lender-controlled escrow so the loan clears in one step — principal and interest to the lender, the balance to the borrower — leaving the borrower little opportunity to divert funds, because repayment need not pass through an open account first. This is a loop-closer for deals already cleared, not where double-financing is caught. Settlement automation is on our roadmap; today AssureLocker provides the risk signals and the lender operates settlement within its own rails.

Why This Is Structurally Better

The lending decision stays entirely with the institution — AssureLocker never approves or declines a loan. What changes is the evidence the decision rests on. Three separate KYB reports, however thorough, can never show how the parties are connected. The whole-deal view is the product. It turns small-ticket pre-shipment loans — the ones lenders currently turn away because the cost of checking eats the margin — into deals worth doing.

To be precise about the division of labour: AssureLocker’s PO Financing Risk Signals assembles and surfaces the source-cited signals — the director overlap, the co-location, the capacity math, the lien-registry state — and packages them as a single CLEAR / REVIEW / FLAGGED read. It does not lend, does not price the loan, does not hold or move funds, and does not approve or decline. Every one of those calls stays with the lender, made against its own credit policy. What the pack removes is the reason a viable thin-file deal used to be un-checkable: the evidence is now assembled at source, in minutes, so the institution can decide on facts instead of on the cost of gathering them.

See It For Yourself

Run the interactive PO financing demo to watch a three-party deal screened in real time, or book a demo to discuss a pilot against a sample of your own historical deals.

Continue reading

See AssureLocker in action

Book a 30-minute live walkthrough tailored to your lending use case.

Book a demo →
AssureLocker
Right Vectors India
3rd floor, Innov8, SKCL Tech Square,
SIDCO Industrial Estate, Guindy,
Chennai, TN 600032

AssureLocker is a verification & orchestration platform — not a lender. It supplies verified evidence and risk signals checked against authoritative sources (GSTN, MCA21, EPFO, CERSAI, Account Aggregator) and orchestrates the assessment room. It does not lend, hold or move funds, operate escrow, set advance rates, or make the credit decision — the lender's system of record makes that decision and disburses. Right Vectors India, the provider of AssureLocker, operates strictly as a Technology Service Provider. Every signal is labelled by evidence tier — registry-verified, lender-side, issuer-confirmed, document-signed or self-declared (missing where unresolved); some integrations are in sandbox, lender-side or pilot, and records are written to an immutable registry (hashes only — never raw PII). Signals and figures are point-in-time and consent-bound; confidential to the named parties.

Explainable, evidence-tiered signals — auditable on request. Our algorithmic-accountability approach →

© 2026 Right Vectors India. All rights reserved. · Site version: al-20260721-155225-34ff216c8

Aligned with India Stack. Made in India.