Back to home

Mobile Document Capture: A Guide for UK Mortgage Brokers

By Casefile

Mobile Document Capture: A Guide for UK Mortgage Brokers

Mobile document capture means a client photographs or scans a document with their phone and sends it to you as a clean, readable file. For mortgage brokers, the scan itself is the easy part. The harder part is getting files that a lender will accept, that match what the client declared, and that are held in a way that satisfies UK GDPR. This guide covers the built-in phone tools, the common failure points, the compliance checks and a repeatable process for brokerages.

TL;DR

  • Free phone tools can scan a payslip into a PDF in seconds. They do not check that the document is complete, current, genuine or consistent with the rest of the case.
  • Lenders can reject files that are blurred, crumpled, photographed off a screen or poorly named, so capture quality directly affects case speed.
  • Capturing ID with face matching involves biometric data, which is special category data under UK GDPR and needs a DPIA before use.
  • A broker-grade process gives clients a tailored document list, one branded upload route and automatic cross-checks before submission.
  • Casefile does this for UK brokerages, with UK-only data residency and an audit trail.

Table of Contents

What mobile document capture means in a broker's workflow

Search results for this topic split into two groups. The first is consumer scanning apps that turn a photo into a PDF. The second is developer toolkits that add capture, auto-cropping, quality checks and text recognition to other companies' apps. Neither describes what a mortgage broker needs.

A broker needs capture that sits inside a case. The client must know which documents to provide, the files must arrive under the right applicant and category, and someone must be able to see what is missing or inconsistent. Capture is therefore one stage in a chain: request, capture, check, approve, submit.

Five stages of mortgage document capture

The volume is real. Unbiased notes that most lenders ask to see three months of bank statements, alongside payslips and ID. For a joint application, that is a large number of files, and most of them will be photographed or scanned by clients on a phone.

Scanning with a phone: the built-in options

Clients searching for how to scan documents with a phone will usually find one of three routes. Brokers should know what each does, because clients will often use them before sending anything.

iPhone and iPad

Apple's Notes app can scan documents. The client opens a note, taps the attachment button and chooses Scan Documents. The camera finds the page edges and produces a flat scan that can be saved or shared as a PDF.

Android and Google Drive

The Google Drive app on Android and iOS can scan documents into searchable PDFs saved to the user's Drive. Google states that scanning works in the mobile app and not in the web browser. A client who tries to scan from a laptop will not find the feature.

Dedicated scanning apps

Dedicated apps add automatic boundary detection, perspective correction and text recognition. A Wirecutter review updated in June 2026 reports that its top pick offers a free tier with OCR on documents up to 25 pages, while the paid tier raises that to 100 pages.

These tools are good at making a page look tidy. They are not built to know that the page is a payslip, that it belongs to the second applicant, or that the salary on it does not appear in the bank statement.

Where client captures go wrong

Having seen how clients send documents, the failure patterns are predictable. They fall into three groups.

Quality failures

Lender packaging guidance is explicit. HSBC's intermediary packaging requirements ask that documents are captured clearly and not photographed on a computer screen, crumpled or blurred, and that only one document is added per page upload. Other lenders have similar expectations, and a rejected file means a query, a re-request and a delay.

Format and naming failures

The same guidance sets technical limits. Files are generally expected as PDF, JPEG or PNG, and filenames should use only letters, numbers, dots, hyphens or underscores, with no spaces. A phone's default name, or a client's renamed "payslip march (final).pdf", can fail an upload before anyone looks at the content.

Content failures

These are the costly ones, because a clear image does not mean a usable document. Typical problems:

  1. A payslip with a missing page, or one month absent from a run of three.
  2. A bank statement that shows only the first page of a multi-page document.
  3. A wage deposit in the statement that does not match the net pay on the payslip.
  4. A regular payment, such as a loan or credit commitment, that was not declared on the fact find.
  5. A file that has been edited after capture.

None of these are solved by a better camera. They are solved by checking the content against the case.

Five controls for mobile capture in a brokerage

A brokerage that accepts phone captures from clients should apply a small set of controls. They are listed in the order a case moves.

1. Tell clients exactly what to send

Generic checklists produce over-sending and under-sending. The document list should reflect the client's circumstances: employed, self-employed, contractor, joint applicants, or a mix. Employed applicants need payslips and bank statements. Self-employed applicants need tax calculations and overviews. Our guide to tax return verification sets out what to check on those.

2. Give clients one upload route

Email attachments, messaging apps and photo messages scatter documents and create privacy exposure. A single branded upload link, opened on the phone the client already holds, keeps files in one place and under the correct applicant. It also lets clients see what is still outstanding without calling the office.

3. Set capture instructions at the point of upload

Short prompts reduce rework: place the page on a flat, dark surface, capture all four corners, avoid shadows, and photograph the paper rather than a screen. These mirror the quality conditions lenders set out in their packaging guidance.

4. Check content, not just clarity

Review each document for completeness and consistency: dates, names, amounts, and whether the statement supports the payslip. Manual review of this kind is slow and varies between advisers. Automating the cross-checks removes most of the variation. See our article on mortgage broker automation for what to automate and what to keep with a person.

5. Keep a record of approval and version

When a client re-sends a better scan, the old file should not disappear and should not be submitted by mistake. A clear approval step and version history show who accepted what and when. This is covered in our pieces on document version control and document approval workflow.

Identity capture: the phone as a verification tool

Phones can do more than photograph a passport. They can read the chip in a passport by NFC and compare a selfie with the document. HM Land Registry's Digital Identity Standard, launched in March 2021, set out requirements for conveyancers using digital services to verify a client's identity on a smartphone. It is optional, but it offers legal protection for firms that comply fully if a client's identity is later found to be fraudulent. That is a conveyancing standard, not a mortgage broking rule, but it shows where identity checking by phone has gone.

For brokers, the practical questions are narrower: which ID documents the lender needs, how they are captured, and whether the check goes beyond a photograph. Our guide to identity document verification for UK mortgage brokers goes through these.

UK GDPR and capture: what to settle before you start

A phone camera collects personal data of a sensitive kind: income, spending, addresses and ID. Several points need attention before a brokerage asks clients to upload from their phones.

Data protection by design

The ICO expects a data protection by design and by default approach when mobile apps are launched. It points out that mobile devices have direct access to sensors such as the camera and GPS, and that privacy information must still be communicated clearly on a small screen. In practice: ask only for the permissions the capture needs, and put the privacy notice where the client sees it before uploading.

Biometrics are special category data

If your capture process uses face matching, the ICO treats biometric recognition as processing special category personal information, with strict transparency and consent requirements. The ICO's guidance says that firms must complete a DPIA and identify a valid condition for processing. It also states that explicit consent is likely to be the most appropriate condition for special category biometric data. If you are unsure which applies to your firm, ask your data protection officer or a specialist adviser. Our note on privacy impact assessments for UK mortgage brokers covers the assessment itself.

Biometrics are special category data — overview diagram

Where the data sits

A consumer scanning app saves files to the client's own cloud account. That account is outside the brokerage's control, and the files are not tied to a case. Once the client sends them on, copies live in several places. A brokerage should know where every copy sits, who can open it and how long it is kept.

Evidence of income remains a lender responsibility

The FCA's MCOB 11 rules on responsible lending require lenders to assess affordability and not to rely on self-certification of income. Brokers may use electronic systems to collect and check evidence, but the compliance responsibility rests with the lender. Brokers still have every reason to submit clean, consistent evidence, because it is the broker's name on the case when the query arrives.

Consumer scanner, SDK or case-based platform

The three types of tool answer different questions. This comparison describes them by category.

CriterionConsumer scanning appCapture SDK built into another appCase-based broker platform
Main purposeTurn a photo into a PDFAdd capture and OCR to a productCollect, check and track documents per case
Who sets it upClient, aloneA software developerThe brokerage
Document list per clientNoNoYes, based on the client's circumstances
Cross-checks between documentsNoPossible only if builtYes
BrandingVendor'sDepends on the buildBrokerage's
Audit trailNoDependsYes
Cost to the brokerageNone, but time lost to reworkDevelopment and maintenanceSubscription

For most small and mid-sized brokerages, an SDK is the wrong tool. It supplies a camera feature but leaves the whole workflow to be built. A consumer app is fine for the client's own filing, but the broker inherits the problems it does not solve.

A worked example

Take a joint application where one applicant is employed and the other is a contractor.

  1. The adviser records the circumstances. The platform builds two document lists: payslips and bank statements for the first applicant, and contract and bank statement evidence for the second.
  2. Both applicants open the brokerage's upload link on their phones and capture their documents.
  3. The system flags that a deposit on the employed applicant's statement is lower than net pay on the payslip, and that a monthly payment on the contractor's statement is not in the declared commitments.
  4. The adviser raises both with the clients before the case goes to the lender, rather than answering a lender query a week later.
  5. The approved versions are stored with a record of who approved them.

The difference is when the problem is found. A mismatch found by the adviser costs a phone call. The same mismatch found by an underwriter costs days.

Our perspective

We built Casefile because the scan was never the bottleneck. A client can photograph a payslip well enough in seconds. What costs a brokerage time is the chasing: which page is missing, which applicant it belongs to, why the deposit does not match, why a commitment appeared on a statement but not on the fact find.

Our view is that capture should be the quietest part of the process. The client opens a branded link, sees a list that fits their situation and uploads. The checking then happens automatically, so advisers spend their time on judgement rather than on opening files one by one.

We also hold that data location is part of the product. Casefile uses UK-only data residency and no manual or offshore handling of client documents, and keeps clear audit trails. A phone capture that ends up in a personal inbox or messaging thread undoes that. Smaller brokerages feel this most, because they have the least spare time to fix errors afterwards.

— Darren

How Casefile handles mobile capture

Casefile is a cloud-based platform for UK mortgage brokers that collects documents from clients, builds each document list from the client's payment types and cross-checks bank statements, payslips, tax forms, ID and utility bills. It flags discrepancies and undeclared commitments, matches wage deposits, checks authenticity and tampering, supports multiple applicants and carries the brokerage's own branding. See the Casefile platform for the full overview, or read how Casefile handles your documents for data security and residency.

Checklist for a brokerage reviewing its capture process

  • Does every client receive a document list that matches their circumstances?
  • Is there one upload route, and does it work on a phone browser without an app download?
  • Do the capture instructions reflect lender quality and format rules?
  • Are documents cross-checked before submission, and by whom?
  • Can you show who approved each file and which version went to the lender?
  • Is a DPIA in place, particularly where ID or face matching is used?
  • Do you know where every copy of client documents is stored?

For more guidance, the Casefile blog covers each of these topics in more detail.

FAQ

Can I scan documents with my phone for free?

Yes. iPhones can scan through the Notes app, and Android and iOS users can scan through the Google Drive app. Both produce a PDF at no cost. For a mortgage application, check that the scan is clear, complete and in a format the lender accepts.

Will a lender accept a photo taken on a phone?

Often, provided it is clear. Lender guidance such as HSBC's intermediary packaging requirements asks for clear captures, not photographs of a screen, and rejects blurred or crumpled pages. Your broker will confirm the specific rules for your lender.

Where do scanned documents go on an Android phone?

When scanning with the Google Drive app, files are saved to the user's Drive and can be opened on any device signed into the same account. Check the folder shown at the point of saving. If you are sending the file to a broker, use the upload link they provide rather than forwarding it from a personal account.

Is capturing a client's ID with a phone a data protection risk?

An ID image is personal data, and a face match adds biometric data, which is special category data under UK GDPR. The ICO says firms must complete a DPIA and identify a valid condition for processing before using it. A brokerage unsure of its position should speak to its data protection officer.

Sources

This article was generated with AI, and whilst it is our expectation that the article is accurate, it should not be taken as advice.