Two lenders, one loan, two systems never built to agree. AssureCLA recomputes the controls that must match — from both partners’ own records — and flags what disagrees while you can still fix it.
Arrangement lifecycle
Every stage keeps its own evidence state — missing inputs stay UNKNOWN, exceptions carry their owner and history to the final dossier.
Pin the identified partner, agreed terms and commitment evidence before origination.
Join both regulated entities' events to the same loan and evidence version.
Test acceptance, reimbursement and partner core-ledger posting inside the regulatory window.
Check flow completeness, statement continuity and two-book balance agreement.
Compare both-RE CIC reporting, DPD and borrower-level classification on each cycle.
Export verdicts, exceptions, remediation and the tamper-evident event trail for review.
Choose your perspective
Validate the partner book independently, surface exceptions early, and carry one cited evidence dossier into risk, compliance and audit review.
AssureCLA does not replace the bank's CBS, LMS, policy or regulatory interpretation.
See the bank workflow →Use one evidence standard across bank partners, shorten onboarding, and make remediation ownership visible without opening one partner's core to another.
Each regulated entity remains responsible for its own records, filings and decisions.
See the NBFC workflow →Inside the suite
The assurance core, a pool layer above it, and an assistive layer that never decides — independent of both lenders’ systems, owning neither book.
The assurance core: independently recomputed controls, blended-rate verification, cryptographically signed arrangement onboarding, and an append-only audit trail where every exception carries an owner and SLA.
Pool assurance for DA/PTC: eligibility screens over the arrangement’s evidence base, a frozen tape under a manifest hash, transfer-diligence rooms and post-close surveillance — computed from both REs’ own events.
Deterministic commentary today, AI analyst narratives ahead — every output is human-approved, and no agent ever creates an approval or an executable value.
The problem
The days your book and your partner’s disagree decide an inspection — and today’s tooling finds them weeks too late.
By the time month-end MIS catches a missed window or single-sided filing, it's a finding — not a fix.
Every mismatch between your book and your partner's becomes a call, an email chain and a spreadsheet.
Retention proof, escrow statements and CIC acknowledgements sit in three places; assembling the trail is its own project.
What changes
Controls recompute inside the 15-day window and the next-working-day deadline, so an exception lands as a task with an owner — not a finding.
One auditor-ready Evidence Dossier per arrangement, on a tamper-evident trail, turns 'show me' into an export.
Recomputed neutrally from both lenders' own records, so reconciliation shrinks to the genuine exceptions.
Add arrangements, partners and asset classes on the same rail, without compliance effort scaling with the book.
Watch it run on a demo arrangement with deliberate breaches, and see what your current process would miss.
Watch it runSee it, not slideware
Executive status at a glance, breaches that can’t be quietly hidden, and evidence an auditor can trace — the running product on a demo arrangement with deliberate breaches.
Swipe screenshots horizontally on smaller screens →
Fits your stack
Those systems each keep one lender’s book; co-lending compliance lives in the gap between two. AssureCLA fills it as a neutral overlay — nothing ripped out, neither partner opening its core to the other.
Both books reconciled by a party with no stake in either — one answer both sides can rely on.
Controls recompute as evidence lands — inside the windows that matter, not after the monthly MIS batch closes them.
Preconfigured intake shims accept the files and feeds you already produce — lifecycle webhooks (Yubi/M2P style), core-banking loan tapes (Finacle/T24 style), bureau filings (CIBIL/Experian style).
Non-maskable checks on a tamper-evident, append-only trail — the spreadsheet era of “adjusted” reconciliations ends here.
Named shims describe supported payload styles, not commercial partnerships, certifications or endorsements by the named vendors.
One rail, every product
The 24 co-lending controls apply to every product. On top of them, an asset class brings its own evidence — and we ship those packs one at a time rather than claiming a shelf we have not built.
Fifteen evidence requirements over and above the common controls: assayer valuation and independence, vault custody, pledge-card delivery, LTV ceiling at origination and through movement, renewal, auction state and notice, insurance, and borrower communication — each held at UNKNOWN until the evidence is supplied, and each with a violation scenario that must be caught.
Housing & LAP · Vehicle & tractor · MSME term · Consumer & personal · Working capital.
Asset-class evidence reaches us through your authorised channels — we do not hold registry credentials of our own.
For your risk & compliance team · RBI Co-Lending Directions, 2025
The headline set. Express requirements cite their paragraph in the Directions; AssureCLA-derived evidence models say so.
Each RE retains at least 10% of every individual loan, checked on both sides through every balance movement; ratio-correct programmes still fail loan by loan.
AssureCLA's derived test verifies all four events — disbursement, partner acceptance, reimbursement and partner core-ledger posting — land inside the 15-calendar-day window. A middleware acknowledgement is not a booking.
The partner's irrevocable commitment must pre-date disbursement with agreed terms pinned; post-origination partner selection fails the Directions (transfer only to the identified partner RE, Para 23).
Borrower-level SMA/NPA classification must converge across both REs by end of the next working day; divergence is a critical, non-maskable exception.
Each RE reports its own share to the credit information companies; single filers, divergent DPD, contradictory statuses and unacknowledged files are caught per cycle.
All flows route through escrow (Para 26); AssureCLA's continuity test chains statement sequences and balances, holding the status at UNKNOWN until any gap is restored or independently explained.
The full catalogue — 24 controls across the Directions, PSL and referenced regimes — lives on AssurePlane. See each one recomputed and proven against a violation.
Frequently asked
An independent compliance operating system and evidence control rail for co-lending. It validates loan tapes, escrow, bureau reporting, booking timelines and retention across gold, housing, vehicle, MSME, consumer and working-capital loans.
A CBS or LMS records only one lender's book, but co-lending involves two regulated entities. AssureCLA reconciles both neutrally, recomputing controls inside the 15-day window instead of waiting for monthly MIS.
An auditor-ready stamped export per arrangement. It carries the Evidence Confidence Score (ECS), non-maskable findings, remediation state and a cryptographic audit proof for risk committees and RBI inspections.
No. They describe supported payload formats (Yubi/M2P webhooks, Finacle/T24 tapes, CIBIL/Experian files) — not partnerships, certifications or endorsements.
From the Learn library
Co-Lending, Audit-Ready: A Quarter in the Life of a Bank–NBFC Pair
The 15-Day Booking Window Is Four Events, Not One
One Loan, Two Lenders, Two Bureau Files — and Four Ways It Goes Wrong
What an Auditor-Ready Co-Lending Evidence Dossier Should Contain
Why Co-Lending Controls Must Be Product-Specific: Gold, Housing, Vehicle, MSME & Working Capital
Co-Lending Marketplace vs Compliance Control Plane: Where AssureCLA Fits
Operating boundary
AssureCLA is a technology service and evidence-control layer. It does not originate loans, hold funds, service loans, make credit decisions, provide legal advice, or guarantee regulatory outcomes. The lender remains responsible for its own policy, controls and regulatory interpretation.
Every capability claim is built and demonstrated, or labelled otherwise. The engine is built and demo-ready; live RE connectivity is at design-partner stage.
A 30-minute walkthrough on a demo arrangement with deliberate breaches, or a shadow pilot on your own data beside your current process.
Also useful: how a control plane differs from a co-lending marketplace.
Status vocabulary
Built — implemented and internally tested.
Synthetic demo — demonstrable with deterministic sample data.
Sandbox — integration surface available without production rails.
Design-partner — controlled institutional connectivity is pending or underway.
In development — partially implemented and not ready for reliance.
Roadmap — designed but not yet implemented.
A status applies to the named capability or connection — not automatically to every module in the suite.
