How a file moves through Mezzura
AI for what should be automated. People for what shouldn't. Here's exactly what happens between the moment you submit a file and the moment a signed underwriting report lands in your inbox.
Mezzura isn't a chatbot you paste a file into. It's a disciplined, repeatable pipeline that separates two very different kinds of work: the arithmetic, which has to be exactly right, and the synthesis, which has to be read by someone who knows what they're looking at. The first runs on deterministic code. The second is assisted by AI and finished by a senior underwriter who signs their name to it.
The split: what's deterministic, what's AI
This is the distinction that matters most, and the one general-purpose AI tools get wrong. Mezzura never asks a language model to do math.
The numbers
Rate calculations, debt-service coverage ratios, covenant math, and cross-document reconciliation run on deterministic code — the same inputs always produce the same output. Correctness isn't a probability.
The synthesis
Document parsing, risk synthesis, and analytical reasoning are AI-assisted to handle the volume — then validated end-to-end by a senior underwriter against the source documents. The judgment is human.
Before your first file: configuration
Underwriting that ignores your policy isn't underwriting — it's a templated checklist. Before we touch a single file, our senior underwriters capture your lending policy, rate parameters, sector logic, security requirements, and risk appetite. This is a one-time setup, with annual reviews and ad-hoc policy updates included. Every report that follows is calibrated to your methodology, not a generic one.
Four stages, three human checkpoints
Every file is touched by a real person at three points. The pipeline handles the synthesis grind so judgment time goes where it matters.
Submit & gap check
You upload a complete file through a secure portal. We catalogue it and run a readiness check — confirming the documents are present and the figures tie together across them. Anything missing comes back to you as a gap list within 48 hours, at no charge.
Structured ingestion & cross-validation
Every document is parsed into a structured manifest. Deterministic checks reconcile the numbers across sources — bank deposits against reported revenue, the NOA against the T2, the AR listing against the balance sheet, registered security against what was disclosed. Discrepancies are surfaced, not smoothed over.
Risk assessment & review
An anchor-based score runs against your policy. Then a senior underwriter reviews the file end-to-end, validates every conclusion against the source documents, adjusts where judgment requires it, and stakes their professional opinion on the recommendation.
Sign-off & delivery
A final review by the principal underwriter. The memo, scorecard, rate recommendation, and board-facing summary are delivered to your inbox with a full audit trail available — in five business days, often as fast as forty-eight hours. You make the call.
How we know a file is ready
Not every file that arrives is ready to underwrite. Before analysis begins, the readiness check resolves each file into one of three states — so you always know where a file stands and why.
Documents complete and consistent. Underwriting proceeds.
Minor gaps that don't block the analysis. The file proceeds with documented conditions.
A material gap or unresolved conflict. We send the gap list and pause until it's resolved — we don't guess.
This is why a Mezzura report doesn't fabricate a number to fill a hole. If a figure can't be supported by a source document, it's flagged — not invented.
The recommendation is ours. The decision is always yours.
Mezzura prepares the analysis and stakes a professional opinion on it. Your loan committee and board make the lending decision — every time. What you get back isn't a model's output; it's our underwriting opinion, with a trail back to every source it rests on.
Want to go deeper? See what's in every underwriting report, or read how we keep borrower data in Canada in our data-residency guide.
See it on a real file.
A twenty-minute call is usually enough to know if Mezzura fits your policy and your file volume. No pitch deck, no hedging.
Book a 20-minute call