Start from a checklist built for the case type. The agent requests and chases each item through your secure portal, then checks every upload for type, date, legibility and matching names. It flags gaps and anything unusual, especially around the deposit. A case handler signs the file off as complete; the agent never judges whether the evidence supports lending.
What does gathering mortgage documents involve, and who owns it?
A mortgage file is long. Identity and address for each applicant, income evidence that differs for employed, self-employed and contract workers, bank statements, proof of where the deposit came from, details of the property and the conveyancer. Many applications stall not on the decision but on the fourth request for a missing page.
That makes document gathering one of the best places for an agent in mortgage lending, and one of the safest, provided it stays gathering. The head of mortgage operations owns the process. Each case handler owns their cases. Financial crime owns the rules on source of deposit. For the wider limits, see our guide to AI agents in banking.
What does the agent do at each step, and at what depth?
- Agent, depth 1: reads the case and builds the checklist. Purchase or remortgage; employed or self-employed; single or joint; gifted deposit or own savings; leasehold or freehold. Each changes the list. Evidence: checklist with the rule that added each item.
- Agent, depth 3: sends requests through the secure portal. Plain-language requests from approved templates, each item explained. Evidence: requests sent, with timestamps.
- Agent, depth 3: chases on a set schedule. Reminders at fixed intervals, capped in number, stopping if the applicant asks for more time. Evidence: chaser log.
- Agent, depth 1: checks each upload. Right document type; within the required date range; readable; names and addresses match the application; all pages present. Evidence: check result per document.
- Agent, depth 1: stamps provenance. An applicant upload is declared; an employer's confirmation received through a verified route can be signed. Evidence: class per document.
- Agent, depth 1: flags anomalies. Inconsistent figures across documents, editing marks, large unexplained credits, a deposit arriving from an unexpected source. Evidence: flag list with reasons.
- Agent, depth 2: drafts the file summary. What is present, what is missing, what is flagged. Evidence: summary.
- Person, case handler: signs the file off as complete and decides any flag. Deposit flags go to financial crime. Evidence: sign-off and flag decisions.
| Step | The agent does | Depth | Stays with a person |
|---|---|---|---|
| Checklist | Builds the list from case type | 1 | Case handler adds unusual items |
| Request | Sends templated requests | 3 | Requests outside the checklist |
| Chase | Sends capped reminders | 3 | Contact after the cap |
| Check | Validates type, date, names, pages | 1 | Nothing |
| Flag | Lists anomalies | 1 | Case handler or financial crime decides |
| Summary | Drafts the file status | 2 | Case handler signs off as complete |
Which controls matter, and what evidence do they leave?
Checklist rules are versioned. When the policy on, say, bank statement periods changes, the change is recorded and applies from a date. Evidence: rule version on each checklist.
Secure channels only. Documents arrive through the portal, not email. A document forwarded by email is external until verified. Evidence: channel recorded per document.
Chaser caps. Applicants under pressure do not need daily reminders. Evidence: chaser counts against the cap.
Deposit flags go to a person. Source of funds is an anti-money laundering question. The FATF Recommendations set the international basis for customer due diligence; your financial crime team applies it. The agent flags; it does not clear. Evidence: flag routed to financial crime and their decision.
No lending judgement. The agent reports whether a document is present and consistent, not whether the income is enough. Evidence: summary template without an affordability field.
Joint applicants kept apart. Each applicant's documents are filed against them. Evidence: document-to-applicant mapping.
What should you measure?
- Time from application to complete file. The main reason to do this.
- Requests per completed file. Many requests for the same item suggest unclear wording.
- Documents rejected at check, by reason.
- Flags raised and upheld.
- Applicant complaints about chasing.
Where does it usually go wrong?
The checklist ignores the case type. A self-employed applicant gets the employed list and the file is incomplete when it reaches the underwriter.
Expired documents are accepted. A statement outside the date range passes because it looked right.
Deposit evidence is waved through. A gift letter from a relative arrives, and the agent marks the deposit as evidenced without the donor's own proof of funds. Flag, do not clear.
Gathering slides into deciding. The agent starts noting "income sufficient" in summaries. That is the underwriter's call, and whether an agent should ever make it is covered in whether an AI agent can approve a mortgage.
The file goes straight to completion. Gathering documents early is a good use of an agent; releasing funds at completion is not. The reasons are argued in mortgage completion is no place for autonomy.
Where Pryme fits
In Pryme, requesting and chasing documents can be certified at depth 3 on your own past mortgage cases, while checking and summarising stay at read and draft. Each document is stamped with its provenance class through the Pryme Context Protocol, so an emailed statement never reads as verified, and every request, check and sign-off is filed. The same pattern underpins preparing credit applications in your origination system.
Questions people ask
Can the agent speak to the applicant's broker?
Yes, if the case came through a broker and your process routes requests through them. The agent uses the broker contact on file and the same templates and caps.
What about the property valuation?
The valuation is instructed by the lender, not gathered from the applicant. The agent can track its status and chase the valuer through your usual route, but cannot instruct or amend it.
Does the same approach work for personal loans?
The pattern is the same, with a much shorter list. See processing personal loan applications with an AI agent.