Amlok
The idea in brief.
Business financing is not one repayment model. An installment loan, an equipment lease, a receivables advance and a revolving line each depend on different evidence and contractual mechanics. This guide shows how to scope an Amlok assessment around the actual financing structure, then preserve the right evidence for monitoring. The goal is a repeatable financial explanation, not a single score applied indiscriminately to every business product.
- Classify the agreement before applying a ratio or delinquency rule.
- For receivables finance, track eligibility, dilution, concentration and collections separately.
- For revolving facilities, distinguish a commitment from available draw capacity.
A practical implementation guide grounded in Amlok’s documented product scope and segment research. Market figures retain their original population and period. Worked examples are invented, reproducible scenarios. They do not represent customer results, underwriting cutoffs or claims of validated model performance.
The market and the decision.
In ISED’s 2024 findings, 49% of debt-financing borrowers intended funds for working or operating capital, 21% for fixed assets and 17% for debt consolidation. These intended-use responses are not shares of loan dollars and need not sum to 100%. [1]
Purpose helps define the evidence request. Equipment finance needs the financed asset and contract; invoice finance needs the debtor and receivable; working capital needs the cash-conversion cycle. Applying the same checklist to all three can collect more documents while answering less of the actual credit question.
Financing purposes call for different evidence
View figure data
| Measure | Value |
|---|---|
| Working / operating capital | 49% |
| Fixed assets | 21% |
| Debt consolidation | 17% |
What Amlok brings to the workflow.
Insights can bring the agreed application, contract and authorized business evidence into a full underwriting assessment. Supported verification, calculations and analytical investigation run within that product context. The implementation should specify the financing structure so each result uses the appropriate contract and eligible evidence. [2] [3]
For a lender, this supports a coherent financial narrative across product teams: what is being financed, how it produces or releases cash, what must be repaid, and which evidence establishes coverage. Signal can follow supported changes in obligations, collections, utilization and financial condition after an approved baseline exists. Product-specific attributes still depend on the configured workflow and available sources.
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]
| Evidence | What it supports | Review requirement |
|---|---|---|
| Term-loan contract and business cash flow | Installment coverage and maturity exposure | Match cash-flow periods with the full scheduled obligation. |
| Equipment invoice and asset evidence | Asset identity, financed cost and supported exposure | Document valuation date and security assumptions. |
| Invoice and debtor ledgers | Eligible receivables, credit notes, disputes and collection | Retain due dates, partial allocations and debtor identity. |
| Revolver agreement and borrowing base | Commitment, advance rates, reserves and draw availability | Apply the documented rules and current drawn balance. |
| Existing facilities and refinancing instructions | Total burden and obligations being replaced | Do not remove old debt until the relevant payoff evidence supports it. |
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]
- Term loans: supported cash available for debt service over scheduled principal and interest.
- Equipment finance: payment coverage and asset exposure, with actual recovery tracked separately.
- Invoice finance: eligible receivables after exclusions; dilution reflects defined credits or disputes, not ordinary collections.
- Revolving credit: current utilization and borrowing-base headroom under the agreement.
- Portfolio outcomes: compare arrears and loss within matched products, terms and origination vintages.
Worked example: invoice face value is not borrowing capacity.
An illustrative invoice facility has CAD 500,000 gross receivables. The agreement excludes CAD 60,000 past its eligibility age and CAD 40,000 disputed. Eligible receivables are therefore CAD 400,000. At an assumed 80% advance rate, the preliminary borrowing base is CAD 320,000.
After a CAD 20,000 contractual reserve, capacity is CAD 300,000. With CAD 250,000 already drawn, remaining headroom is CAD 50,000, subject to any other documented limits. The advance rate and reserve are invented contract assumptions, not recommended terms. A paid invoice reduces outstanding receivables; it is not automatically dilution.
| Component | Amount |
|---|---|
| Gross receivables | 500,000 |
| Age exclusions | −60,000 |
| Disputed receivables | −40,000 |
| Eligible receivables | 400,000 |
| 80% assumed advance rate | 320,000 |
| Contractual reserve | −20,000 |
| Borrowing capacity | 300,000 |
| Already drawn | −250,000 |
| Remaining headroom | 50,000 |
Keep the original decision in view.
Monitoring needs to follow the financed structure. An invoice lender may care about aging, disputes and debtor concentration; an equipment lender needs supplied asset and payment evidence; a revolving lender needs changes in eligibility, reserves and availability. The same business event can affect several measures without being several independent risk events.
Signal can compare new supported records with the approved baseline and preserve the underlying calculation. Keep refinances, restructurings and prepayments distinct from successful full-term repayment in outcome reporting. The lender executes draws, payments, servicing and collections in its own systems. [3]
From evidence to a reviewable change
- 01Classify the agreement
Identify repayment mechanics and eligible evidence.
- 02Calculate the right exposure
Apply contract-specific definitions and exclusions.
- 03Observe financed assets
Follow receivables, obligations and supplied valuations.
- 04Review the difference
Connect changed evidence to the original financing decision.
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.
Build separate test cohorts for term, equipment, invoice and revolving products. Evaluate contract classification, schedule reconstruction, debtor matching and calculation accuracy before predicting credit outcomes. [4]
Use mature repayment or collection outcomes with a stated denominator. Test late invoices, corrected credit notes and changed eligibility rules. Report false availability calculations and unsupported exclusions explicitly; a generic document-extraction average can hide errors that materially change the lending amount.
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.
Sources & methodology.
Figures identify their population, period, and units. Scenarios marked illustrative are Amlok calculations using stated assumptions, not observed customer outcomes.
- 1Small Business Credit Condition Trends, 2014–2024Innovation, Science and Economic Development Canada
2024 survey. Applicant approval, authorized dollars and intended uses have different denominators; intended uses may overlap.
- 2Products and endpoint scopeAmlok
Documented ownership of Insights, Signal and included processing stages. Workflow availability and provider coverage depend on the agreed implementation.
- 3Integration workflowsAmlok
Frozen input manifests, immutable risk snapshots, approved monitoring baselines, source-dependent refresh and institution-owned intervention.
- 4Business Financing benchmark and evaluation definitionsAmlok
Segment-specific research definitions and proposed evaluation tasks. This is a research framework, not a claim of completed segment validation.
- 5Measured research resultsAmlok
Published SBA structured-loan and FinQA retrieval experiments have limited populations and tasks. They do not establish performance for this segment.
