Alternative Lenders. Make specialist credit explainable.

The market and the decision.

CMHC’s Fall 2026 report shows Q2 2026 mortgage delinquency at 90 days or more of 2.57% for mortgage investment entities, 0.28% for chartered banks, 0.14% for credit unions and 0.27% for other non-bank lenders. These reported populations and sources differ; they are not a controlled comparison. ^[1]

The practical lesson is to match the benchmark to the actual product. A mortgage-investment-entity observation cannot establish loss rates for merchant advances or unsecured installment lending. A specialist lender needs its own eligible cohort, contractual definition and mature outcome history.

What Amlok brings to the workflow.

Insights can structure an authorized underwriting workflow around the actual application and available evidence. The lender specifies the product, intended decision and supported calculations. Verification and analytical investigation operate within that agreed product context, producing an assessment with traceable inputs and explicit unavailability where evidence is insufficient. ^{[2] [3]}

Specialist teams can use that structure to examine irregular income, shorter terms, broker-supplied files or complex business cash flows without pretending the evidence is identical to a mainstream bank application. Signal follows supported changes from an approved baseline. The lender retains pricing, policy, final decisions, funding and servicing actions.

Connect the evidence that matters.

Agree the evidence perimeter before asking for an assessment. Each record needs a subject, source, observation date, currency where applicable, and coverage window. Resolve conflicting statements explicitly; the most recently uploaded file is not necessarily the most recent financial position. ^[3]

Measures your team can review.

Use the definitions below as an assessment specification. Your institution selects policy thresholds and permitted adjustments. These measures are useful only when their inputs, time periods and contractual meanings align. ^[4]

• Contractual burden: installments or remittances relative to the appropriate supported cash-flow measure.
• Vintage outcomes: mature arrears, cures, charge-offs and recovery by term and origination date.
• Channel concentration: exposure by broker, originator and supported related group.
• Evidence completeness: usable history, verified fields and unresolved reconciliation differences.
• Monitoring relevance: confirmed financial changes at a fixed observation horizon with false-alert burden.

Worked example: current interest does not repay a balloon.

Consider an illustrative CAD 300,000 interest-only bridge loan with a 10% nominal annual rate and monthly interest of CAD 2,500. Twelve on-time interest payments total CAD 30,000, but principal remains CAD 300,000 at maturity if no principal repayments occurred.

A file can therefore show perfect interest-payment continuity while the principal exit remains unresolved. An assessment should inspect the supported repayment route, dates and dependencies. A proposed refinance or property sale is not realized cash. The scenario is not a recommendation for a product, rate or extension.

Keep the original decision in view.

Monitoring should follow both recurring obligations and the events on which repayment depends. For a bridge facility, that may include a documented maturity and newly supplied exit evidence; for a receivables product, collection and eligibility changes matter. Keep each monitoring rule tied to the actual agreement and approved baseline.

Explain whether an alert reflects a changed financial condition, an expiring term or missing evidence. Signal supplies the supporting assessment; the institution determines extensions, contact, enforcement and collections. No automated customer action is implied by receiving an alert. ^[3]

Build it into your operating model.

Start with one defined use case, your current decision policy and the output your reviewers need. Confirm which source connections, document types, calculations and verification stages are available within the agreed workflow. Create the subject and application, obtain the required authorization, synchronize permitted records and inspect the ready input manifest. Freeze that evidence window before launching an Insights underwriting run. ^[3]

Store the completed risk snapshot with the lender’s actual decision and its reasons. For ongoing monitoring, use a ready approved baseline from the completed assessment or the agreed existing-portfolio onboarding process. Signal compares newly available evidence with that baseline. Signed webhooks notify your systems; source cadence and consent determine freshness. A requested daily check does not guarantee daily source data. ^[3]

Design separate routes for a supported risk change, a source outage and an unresolved discrepancy. Retain source references and reviewer corrections. Borrower outreach, payments, limit changes, collections and insurance administration remain in your authorized systems. Verification and analytical investigation are included stages within an entitled Insights or Signal workflow, not independent Amlok products. ^[2]

Prove the fit before expanding.

Stratify evaluation by product, term, channel and evidence completeness. Use later vintages and, if feasible, a held-out originator. A higher-risk borrower mix must not be mistaken for weaker workflow quality. ^[4]

Validate contract interpretation and payment reconciliation before prediction. Report calibration and errors on the lender’s actual eligible population, keeping modified and refinanced facilities distinct. Include the cases where the correct output is insufficient evidence, and measure how those cases are resolved in practice.

Agree success criteria before reviewing the test results. Compare the current process and the Amlok-supported process on the same permitted evidence, recording analyst time, corrections, unresolved cases and completed outputs. Report coverage alongside speed so incomplete files cannot make the workflow appear faster. Monitor quality by source availability and relevant customer cohorts, with uncertainty where samples are small.

Amlok’s public results currently document specific structured-loan and financial-evidence retrieval experiments. Those results are useful evidence about those tasks; they do not validate every product, institution or industry in this guide. A deployment claim needs a representative evaluation of your use case. ^[5]

• Scope: choose one product, one decision moment, required evidence and a clearly accountable reviewer.
• Replay: use dated historical snapshots with later outcomes kept out of the input evidence.
• Shadow: compare outputs alongside your existing process before relying on them operationally.
• Expand: review quality, data continuity and monitoring relevance before adding further cohorts or sources.