AssureSignal - Pre-Credit Verification Pack
One evidence-linked pack before underwriting: source availability, evidence tiers, risk-signal findings, AI-assisted summaries and lender review actions in a format credit teams can question, accept or challenge.
AssureLocker supplies evidence and risk signals. It does not approve, reject, price, sanction, broker, disburse, hold funds or replace the lender’s own credit process.
What the pack contains
A common spine across PO, invoice, export and collateral workflows
Identity and establishment
Entity identity, GST/MCA/Udyam context, directors or signatories where permitted, and evidence freshness.
Trade and receivable evidence
PO, invoice, IRN, e-way, buyer acceptance, movement and settlement evidence where available.
Capacity and exposure
Borrower and subcontractor capacity signals, concentration prompts, and lender-side cashflow checks.
Conflict and reuse checks
Duplicate-presentation, prior-charge, related-party and inconsistency signals shown for reviewer reconciliation.
Entity strength: assets, ownership & financials
ULI asset-backing and encumbrance, beneficial-ownership (UBO) signals, and financial-strength evidence tiered by source (audited / ITR-filed / self-declared) — each labelled, never a credit verdict.
Financing workflows
One evidence spine, tuned for three lending workflows
Each workflow draws on the same pack structure: source status, evidence tier, cited findings, review prompts and a clear boundary that the lender owns the credit decision.
Pre-shipment PO finance
AssureSignal for Purchase Order Financing
Buyer, borrower and subcontractor evidence; trade relationship, capacity, related-party and duplicate-presentation prompts.
A PO Risk Signals Pack for credit review before commitment.
Explore workflowOff-exchange receivables
AssureSignal for Invoice Factoring
Invoice authenticity, goods movement, party KYB, buyer confirmation, prior charge and duplicate-financing checks.
A Verified Receivables Pack for bilateral factoring review.
Explore workflowExporter and post-shipment evidence
AssureSignal for Export Financing
IEC/DGFT status, exporter identity, overseas-buyer context and lender-side inflow corroboration where available.
An export evidence pack for pre- or post-shipment lender review.
Explore workflowSource availability
Every signal says where it can run
Source status is separate from evidence tier. A signal can be strong when it runs lender-side, unavailable for a specific case, or sandbox-only during pilot testing. The pack should show that state plainly instead of burying it in footnotes.
Available in production through AssureLocker or an authorised production rail.
Runs inside the lender's trust boundary on the lender's own credentials.
Available through an authorised partner, issuer, network, or consented provider.
Available for deterministic testing or synthetic cases before production enablement.
Not available for this case, lender, jurisdiction, or evidence source.
Roadmap source or signal; not relied on as live evidence.
Reviewer workflow · planned
Lender review primitives, not hidden judgement
The pack is built to support normal credit-ops behaviour: accept a signal, challenge it, request more evidence, resolve the treatment, comment, and retain an audit event. Those actions belong to the lender reviewer; AI can summarise but cannot close the review. These review primitives define the intended workflow — on the roadmap — while today’s pack surfaces the tiered signals and an ask-the-pack assistant.
Accept
Reviewer accepts the signal as usable within the lender's own policy.
Challenge
Reviewer disputes the finding or asks for its source/method to be checked.
Request further evidence
Reviewer asks the borrower, anchor, issuer, or connector for more evidence.
Resolve
Reviewer records the final treatment of a challenged or open item.
Comment
Reviewer adds context without changing the signal status.
Audit
System or reviewer records an immutable review/audit event for traceability.
Freshness & reuse
You set the risk appetite. We apply it on every financing event.
Verification isn’t free, and it isn’t permanent. AssureLocker keeps a persistent record of every entity, relationship and check it has done for you — and reuses it whenever your policy allows, so you don’t pay twice for evidence that’s still current. But every financing event still gets a fresh decision: evidence is reused only when it’s within your freshness window and no risk trigger overrides it. Nothing is ever assumed valid just because it was checked once.
Standard
Balanced refresh windows for normal MSME receivables and PO finance.
Most lenders, most books.
Conservative
Shorter windows, more frequent refreshes, stronger assurance.
Higher-risk segments or tighter risk appetite.
Custom
Windows and triggers agreed with your credit, risk and compliance teams.
Enterprise programmes with their own policy.
You buy simple, predictable packs. The freshness policy works in the background to decide — per financing event — whether each piece of evidence is reused, refreshed, or escalated for review. Risk control, not pricing complexity. Platform-level limits ensure evidence is never reused beyond safe windows — you can always choose a stricter policy, never a materially weaker one.
Entity strength
Assets, ownership and financials — as evidence, not a verdict
Some deals turn on the borrower’s balance sheet and what backs it, not just the transaction. AssureSignal folds that in as an entity-strength axis— asset-backing, beneficial ownership and financial-strength signals — each labelled by how strongly it is evidenced. It stays evidence for the lender’s own underwriting; AssureLocker never scores creditworthiness, values an asset, or sets an advance.
Assets & encumbrance
ULI-sourced land and vehicle records — existence, owner-name match and charge/encumbrance — consumed lender-side; the raw record stays inside the lender's boundary.
Registry-verified · lender-side
Beneficial ownership (UBO)
Directors / DIN, significant beneficial owners (MCA SBO) and the ≥10% ownership declaration, cross-checked where the registry allows.
Registry-verified / self-declared
Financial strength
Balance-sheet ratios (leverage, current ratio, interest cover, net worth) computed from the statements the entity provides — tiered by source.
Audited / ITR-filed / self-declared
Where an external credit rating exists (e.g. a CRISIL MSE rating), it can ride along as one more issuer-confirmedsignal — an entity-uploaded rating certificate, verified against the agency’s published listing where possible. It is an input beside the evidence, never a substitute for the deal-level checks (see AssureSignal vs a credit rating).
A note on sourcing: GSTN gives turnover, not a balance sheet, and there is no clean public API for MSME financials today — so financial-strength signals come from what the company and its auditor provide, with ITR-filed figures a tier above a bare upload, and are labelled accordingly.
Not a credit rating
A rating scores the borrower. AssureSignal verifies the deal.
A company credit rating — like a CRISIL MSE rating — is an annual, entity-level opinion of overall creditworthiness. AssureSignal is a transaction-level evidence pack assembled at the moment of financing. A rated borrower can still present a fabricated, unaccepted or already-financed receivable; that is the deal-level question a rating never asks. The two are complementary — a lender can use both.
Read: Pre-Credit Assessment — AssureSignal vs a CRISIL MSME ratingRelated capabilities
Add the checks a deal needs
Some deals need collateral context, first-financing checks, privileged source access or a sample pack for internal review. These capabilities extend the pack without changing the lender’s decision boundary.
Use the pack in shadow mode before production
Start with historical cases, synthetic edge cases, and controlled-live cases. Compare what the pack surfaced, when it surfaced it, and how your team treated it. Then decide whether to wire it into your production workflow.