Income Verification Documents: Payslip, Tax and Bank Checks

Income verification documents are consistent when the same person, employer, amounts and dates can be traced from the payslip to the tax document and on to the bank statement. A payslip that looks fine on its own proves little; a payslip whose net pay appears as a credit on the statement, whose year-to-date gross lands close to the P60 and whose employer name matches the payer on the account is a file a reviewer can sign off. This guide lists the exact field-to-field comparisons, what a mismatch looks like, and what the reviewer does next.

This article is for informational purposes only and does not constitute legal, financial, or regulatory advice. Regulatory references are accurate as of the publication date. Consult a qualified professional for guidance specific to your situation.

Why three documents beat one

Each income document is produced by a different party, so each one can only contradict the others in ways that a single document cannot. The payslip comes from the employer, the tax document from HMRC or the employer's year-end return, the bank statement from the applicant's bank.

In the UK, employers must give every worker an itemised payslip on or before payday, showing gross pay, deductions and net pay (GOV.UK, Payslips). That makes the payslip the most detailed record of a single pay period. It says nothing about whether the money arrived, or about the rest of the year.

The tax document fills the year-level gap. HMRC's specification says employers must give the P60 to employees still employed on 5 April by 31 May (HMRC, P60 specification). For self-employed applicants, the equivalent is the SA302 tax calculation, which GOV.UK explains how to get from the HMRC online account. The bank statement closes the loop by showing what actually landed.

For the wider checklist of documents and validity tests, see our document verification guide. For the lender-side view of the same problem, read how UK lenders validate income documents before a credit decision.

The cross-check matrix

A cross-check names one field on one document and compares it with one field on another. Write these into the review procedure so every analyst runs the same ones.

Check 1 and 2: payslip net pay against the salary credit

The net pay on the payslip should appear on the bank statement within a day or two of the pay date, from a payer whose name matches the employer. This is the single most useful check because it ties a document the employer produced to money a bank recorded.

Work through it in three steps. Take the net pay figure and pay date from the payslip. Find the credit on the statement with the same amount, allowing for weekends and bank holidays. Then read the payer reference: payroll credits usually carry the employer name or a payroll bureau name.

Differences are not automatically a red flag. A bureau can pay on behalf of the employer under another name, pay can be split across two accounts, and a salary-sacrifice or student-loan deduction should already be inside the net figure. The red flags are a credit that never appears, an amount that is round while the payslip net is not, or the same credit repeated with different payslip figures.

Next step for the reviewer: ask for the statement page covering the pay date, not a summary page; ask which account receives the split if pay is divided; and ask for one more payslip and its matching credit before deciding.

Check 3 and 4: payslip year-to-date against the P60

The year-to-date gross on the last payslip of the tax year should be close to the total pay on the P60, and the tax code and employer should match. The P60 is issued per employer, so an applicant with two jobs will hold two.

Compare "pay to date" and "tax to date" on the final March payslip with the P60 "total pay in this employment" and "total tax in this employment". They are expected to be very close because both come from the same payroll. A large gap points to a payslip from a different period, a bonus paid after the payslip, or a document that did not come from the same payroll run.

Also compare the tax code. A change from 1257L to a different code mid-year is normal after HMRC instructions, so ask for the reason rather than reject the file. A P60 that is a year or more old only shows what the person earned then; it is not evidence that the job continues. Pair it with a recent payslip and the statement credit.

Check 5: tax document against what the account shows

The total income on the SA302 or P60 should be of the same order as twelve months of salary credits and other income on the statements. For employed applicants with a stable job, the annual P60 total divided by twelve should be near the average gross monthly pay, and the net credits near the average net pay.

Self-employed applicants are different. Profit on the SA302 is after expenses and before tax, while the account shows takings, drawings and tax payments. Do not expect arithmetic equality. Look at direction and scale: an SA302 showing £38,000 of profit against statements showing a few hundred pounds of monthly credits needs an explanation, such as income paid into another account or a very recent business.

Next step for the reviewer: ask for the SA302 and the matching tax year overview from the applicant's HMRC online account, downloaded during the review. Ask the self-employed applicant for accounts or an accountant's reference when the statements and the SA302 differ materially.

Check 6 and 7: names, addresses, account holders

Name, address and account details must match across all three documents and the application, with tolerance only for formatting. Initials versus a full first name, a flat number written differently or a missing middle name are formatting. A different surname, a different postcode with no house move, or a joint account where only one holder earns are substantive.

Set the rule in the procedure: formatting differences are accepted and noted, substantive ones trigger a request. For address matching specifically, see how teams handle the formatting side in our guide on matching addresses across documents.

What this check proves, and what it does not

A consistent file shows that three documents agree with each other; it does not show that any of them is genuine. Agreement raises confidence because an altered document would also have to be altered consistently in two others. It is a validation step, and a lender that needs assurance about authenticity adds separate controls, such as asking the applicant to download a document live from their own online account.

Tolerances belong in policy, not in the analyst's head. A workable policy states for each check the accepted gap, the documents requested when it is exceeded, and who may approve an exception.

What applicants and forum users keep asking

People asking in personal finance and landlord forums raise the same questions every time, and they point to where files stall.

"Why doesn't my payslip match what hit my bank account?" Usually because the payslip net already includes pension, student loan and salary-sacrifice deductions, or because pay is split across two accounts. The fix is to send both statements, not to explain in a covering note.

"I'm self-employed and have no payslips. What do I send?" The SA302 and tax year overview from the HMRC online account, plus six to twelve months of business and personal statements. Reviewers then look at direction and scale, as in check 5.

"Will they accept a payslip from last month with a P60 from two years ago?" Often not, because the P60 does not cover the current year. A recent payslip and the latest P60 together tell a better story.

"My new job has only one payslip." Then there is no year-to-date history to compare. Ask for the offer letter or contract and treat the file as provisional until a second pay date has landed.

Run these checks without re-keying every field

Reading seven comparisons by eye on every file does not scale, and the comparisons are the part machines do well: extracting named fields, normalising names and dates, and flagging gaps against the thresholds you set. CheckFile compares fields across the documents in a file and shows the reviewer which comparisons passed, which failed and which are missing. It checks consistency and completeness; it does not certify that a document is authentic. For lenders and leasing teams, the financing and leasing solution shows how this fits a file review, the security page explains data handling, and pricing lists plans.

FAQ

Which income verification documents should a file contain?

At minimum, the latest payslips, the latest P60 or SA302, and three to six months of bank statements showing the salary credit. The mix depends on the product and on how the applicant earns. Always add the application form, since it is the source for names and account details.

How close should the payslip year-to-date be to the P60?

They come from the same payroll, so on the final payslip of the tax year they should be very close. Set a numeric tolerance in policy and request an explanation outside it. A gap is a prompt for a question, not proof of anything.

Is a bank statement enough to prove income?

No. It shows credits but not their source or whether they recur on a contract. Pair it with a payslip or tax document so the credit can be traced to an employer.

What if the applicant is paid in cash or by several clients?

Use the SA302 or the tax year overview as the anchor and compare it with the statements for direction and scale. Cash income that never reaches an account cannot be cross-checked, and the policy should say how much weight it carries.