Verify the Name, Not the PDF.
Bank-based name verification against the account record.
Someone asks you for proof of banking details, and the first document you send back gets rejected because the account name is cropped out of the screenshot. That’s not an edge case. That’s most of what goes wrong here.
TL;DR: Proof of banking details means showing that an account name, sort code and account number belong to the person or business claiming them, usually through a statement, a bank letter or a verified check run directly against the bank record. What counts varies by organisation, and not every document that looks right actually is.
This guide draws on Finexer’s work as an FCA-authorised Open Banking infrastructure provider (AISP and PISP, FRN 925695), supplying bank-based verification to UK platforms across proptech, payroll and accounting, where this exact question comes up at almost every onboarding stage.
“People assume there’s one universal standard for what counts as proof,” says Ravi, who works with UK platforms across payroll, lawtech and accounting. “There isn’t. What one landlord accepts, a payroll platform might reject, because they’re managing different risks.”
What Proof of Banking Details Actually Means
Proof of banking details is evidence that a specific account name, sort code and account number belong to the person or business claiming them.
It exists to answer one question: is this really their account? A document with the right numbers but the wrong name attached doesn’t answer that question, no matter how official it looks.
What Is Proof of Bank Statement, and What Else Counts?
A bank statement is the most commonly requested form of proof of banking details: an official document from the bank showing the account holder’s name alongside the sort code and account number, usually issued monthly or on request.
It isn’t the only accepted form. Organisations commonly also accept the following:
- A bank letter: a formal letter from the bank confirming the account details and the name attached to it
- A banking app screenshot: a screen showing the same details, which is increasingly common now that 75% of UK adults use mobile banking as their most common access method (UK Finance, 2024)
What’s accepted varies by organisation. A letting agent’s requirements won’t necessarily match a payroll platform’s, because each is managing a different kind of risk.
What Usually Gets Rejected, and Why?
Certain submissions get turned away consistently, and the reasons are almost always the same.
| What gets rejected | Why |
|---|---|
| Cropped images | The account name is often the part left out |
| Documents with the name obscured | The one detail that matters most is missing |
| Screenshots without account details visible | A balance alone proves nothing about ownership |
| Documents that don’t match the name on file | The whole point of the check is confirming the match |
None of these are arbitrary. Every one of these gets rejected because it fails to answer the actual question being asked: does this account belong to this person or business.
Why Do Firms Ask for This in the First Place?
Organisations aren’t collecting proof of banking details out of habit. They’re managing two specific risks.
The first is paying the wrong account, whether through an ordinary data entry error or because invoice bank details were changed by someone impersonating a supplier. The second is accepting funds from a source that hasn’t actually been confirmed, which creates its own set of problems downstream.
Both risks come down to the same gap: a document shows what someone submitted and not what’s actually true at the bank.
The Better Alternative: Verifying the Name Directly
A submitted document can be edited, cropped or simply outdated. Verifying an account name directly against the bank record removes that uncertainty by checking the actual bank data instead of a file someone uploaded.
This is what an account holder name check does: it compares the expected name against the bank’s own record and returns a result, rather than asking a human to eyeball a PDF and decide if it looks legitimate.
For firms specifically, this replaces the entire document-collection step. A bank account verification run this way confirms the name at the point of onboarding, without a customer needing to find, photograph or upload anything at all.
If You Do Need to Share a Statement
Where a document is still requested, only the relevant details need to be visible. The account name, sort code and account number matter; the transaction history usually doesn’t.
Redacting unrelated transaction details before sharing a statement is worth doing regardless of who’s asking. There’s rarely a reason for a landlord, employer or platform to see a full spending history just to confirm an account belongs to someone.
Where Does This Question Come Up Most?
Proptech platforms and letting agents ask for this from tenants and landlords before deposits or rent payments are set up.
Payroll and invoicing platforms ask new starters and suppliers for it before the first payment run.
Accounting and ERP platforms ask clients for it during onboarding, before any transactions are processed on their behalf.
Finexer’s Approach
Collecting a document and hoping it’s genuine is a weaker check than confirming the account name directly at the source.
Finexer’s banking data API supports this by providing bank-based name verification, confirming the name held at the bank, rather than relying on whatever a customer chooses to submit.
How recent does a bank statement need to be to count as proof?
This varies by organisation although many ask for something issued within the last one to three months to reflect the account’s current status. That’s usually the practical answer to what is proof of a bank statement in a specific context: not only the document type but also how current it needs to be.
Can a mobile banking app screenshot replace a printed statement?
Often, yes, provided the screenshot clearly shows the account name, sort code and account number. Some organisations still prefer an official document or letter instead.
Do firms need proof of banking details from every customer?
Not always. It depends on what the relationship involves, as payments, refunds or payroll typically require it, whereas some interactions never touch bank details at all.
What if someone doesn’t have easy access to a bank statement?
A bank letter requested directly from the branch or through online banking is usually a workable substitute, and a verified check against the bank record avoids the document question altogether.
See how Finexer’s Verification product confirms an account name directly against the bank record, removing document collection from your onboarding flow.
Explore with AI
About the Author
Paul Lucraft
Paul Lucraft is a payments industry strategist and advisor with more than two decades of experience across banking, card networks, and financial services infrastructure. His expertise covers fraud prevention, payment risk management, financial strategy, and the operational development of card payment systems. He previously held senior roles at Mastercard Europe where he served as General Manager for the UK and Ireland, overseeing fraud risk, operational governance, and payment network strategy across the region. Earlier in his career, Paul worked at Lloyds TSB and TSB Bank leading fraud strategy, credit collections, and card business finance operations.