Covenant monitoring
Extract reported figures from compliance certificates and financial statements, recalculate each covenant on the agreement's own definitions, and flag borrowers trending toward a breach.
Banking & Financial Services · Canada
Credit, compliance and audit teams spend their week reading borrower packages and customer files. We build AI that extracts the figures, applies your definitions and shows its sources, so analysts review instead of rekeying.
Why now
Commercial lending, compliance and audit work depends on documents that arrive on their own schedule: quarterly compliance certificates, audited and interim statements, appraisals, beneficial ownership records, examination letters and audit findings. The numbers that matter sit in PDFs from hundreds of borrowers, each formatted differently. Language models are now good enough to extract those figures, apply the covenant definitions written into each credit agreement and draft the first version of a memo or alert, with every figure tied to its source page. Credit decisions, risk ratings and suspicious transaction reporting stay with credit officers and compliance staff.
Use cases
Extract reported figures from compliance certificates and financial statements, recalculate each covenant on the agreement's own definitions, and flag borrowers trending toward a breach.
Assemble borrower background, financial spreads, security and the relevant credit policy sections into a draft annual review that the account manager edits and the credit officer approves.
Resolve guarantors, subsidiaries and directors across loan files into one view of total exposure to a related group.
Read incorporation documents, share registers and ownership charts, list beneficial owners, and highlight what is missing or out of date for the periodic review.
Compare a potential sanctions or watchlist hit with customer details such as date of birth, nationality, addresses and known aliases, and draft a disposition rationale the analyst accepts or rejects.
Pull findings from internal audit reports and regulator letters into one register with owners, due dates and evidence of remediation.
Example workflow
Borrowers' compliance certificates and interim statements arrive in the shared mailbox or document system.
The agent extracts each reported figure (debt service coverage, leverage, working capital) and records the page it came from.
It reads the covenant definitions and any amendments in each credit agreement and recalculates the ratios on that basis.
It ranks borrowers by headroom, lists missing certificates and drafts a short note for every borrower near or past a threshold.
The account manager reviews the flagged files and the credit officer decides on waivers, watch-list moves or follow-up. The AI never changes a risk rating.
Decisions and the cited figures are saved with the credit file for the next review and for audit.
From our work
Resolves aliases, transliterations and shell entities from public watchlists into one graph, with a local open-weight model making the judgment calls.
Data and privacy
Who regulates a Canadian financial institution depends on its charter: banks and federally regulated trust and loan companies are supervised by OSFI, whose guidance covers third-party, technology and model risk, while most credit unions answer to provincial regulators (FSRA, in Ontario's case). Customer information is also covered by PIPEDA, and KYC and AML work by FINTRAC requirements. For lenders and wealth firms we can keep the whole system inside your environment, run open-weight models for sensitive files, document how each model is used and tested so model risk and vendor reviews have what they need, and log every output. We don't give regulatory advice; your compliance team sets the rules the system follows.
Kitchener-Waterloo
Waterloo Region's financial sector includes credit unions, wealth managers, fintech start-ups and regional teams of national lenders. We work with them from Kitchener, in person for discovery and remotely for the build.
It can do most of the extraction. Models read balance sheets, income statements and notes from PDFs, map line items to your spreading template and show the page behind each number. Unusual items, restatements and figures the model is unsure about are flagged for the analyst, who checks the spread before it feeds a ratio, a risk rating or a memo.
Yes, and that is the main reason to use a language model here. Agreements define EBITDA, funded debt and permitted add-backs in their own words, and amendments change them. The system reads the definitions for each borrower and applies them, citing the clause, instead of using one generic formula. The analyst can see exactly which definition produced each ratio.
Usually a clear statement of what the model does and does not decide, the data it uses, how it was tested on your own files, its known limitations and how its outputs are monitored over time. We provide that documentation, a test set built from historical files and logs of every answer, so validation can review it like any other model in your inventory.
Yes. Many credit unions run banking and document systems through vendors, so the AI layer connects to exports, shared drives or vendor APIs rather than replacing anything. It can be hosted in a Canadian cloud region or on a server you control, and we can handle monitoring after launch so staff use the system rather than maintain it.
Related
Sanctions screening, entity resolution, ownership graphs and financial-filings pipelines that turn public records into alerts.
Learn moreCited answers over contracts, policies, filings, tickets and internal knowledge, including questions that span many documents.
Learn moreOpen-weight models running in Canadian cloud regions or on your own hardware, for data that can't leave your control.
Learn more7 min read
Agentic AI explained for business leaders: how AI agents work, where they succeed and fail, guardrails, evaluation, approvals and examples by department.
Read the guide7 min read
Microsoft 365 Copilot and ChatGPT Enterprise vs custom AI agents: what each does well, where each falls short, a decision table and how to use both.
Read the guide7 min read
How to run AI on sensitive data in Canada: PIPEDA, Quebec Law 25, PHIPA, Canadian cloud regions, private LLM options and a practical data residency checklist.
Read the guideA 30-minute call is enough to tell whether AI is a fit, what a first project would look like and what it would take to run it in production.