November 16, 2026 in Thought leadership
Stop Asking for Paystubs First: Why Income Verification Is a Sequencing Problem
What changes when lenders verify income before asking borrowers for documents.
Requesting W2s and paystubs at the start of a mortgage file is standard practice at many lenders, and it was at M&T Bank. The LO asked, the borrower found the documents and uploaded them, and operations sorted out what had arrived. Verifications were ordered too, and when one failed, the file could go back to the borrower for more documents.

When the bank analyzed its application codes, it found multiple income and employment verification providers in use. Joseph Semrani, M&T’s SVP of Digital Platforms, Transformation and Product Strategy, described a process that had become fragmented as it varied by channel, across consumer direct, retail branches, self-serve applications, and LO-started files.
The order of those steps drives much of the cost. When documents are requested first and verification runs later, lenders pay twice: once to collect and review paperwork, and again for a verification that could have made the paperwork unnecessary. A better vendor price reduces the second cost. Moving verification ahead of the document request addresses the first.
Verification quietly became a margin problem
Tim Watkins, a sales engineer at Blend with more than two decades in mortgage, says the executives he talks with share one priority right now: protecting loan margins. When they audit their pipelines, verification stands out. In his words, income and employment verification “has quietly become one of the most expensive and fragmented items on the P&L.”
Part of that expense is rework. When verifications run through several vendors, two people working on the same file can each order one without knowing the other already did, and the lender pays twice for the same borrower. A waterfall fails partway through, and processors go back to borrowers for documents the LO already requested. Semrani calls this the “round trip.” A failed verification or incomplete document sends the file from borrower to LO to operations and back, and each trip adds conditions, hand-offs, and days.
Moving verification to the front of the file
When verification costs climb, the instinct is often to swap vendors. A new vendor may charge less per verification, but the order of operations stays the same. Documents are still requested up front, verification still comes later, and teams still reconcile the two.
M&T chose not to treat the project as a vendor swap or a technology initiative. Semrani framed it as modernizing the workflow, and the team moved verification to the point of sale, where the borrower is already filling out the application. Verifying there let the bank prefill the application, send files to LOs and underwriters with income already verified, and reduce the number of income documents to review.
He described the change this way: “We flipped it. If we don’t need the documentation, why do we need it?”
Verification became the first step in the file. Its result now decides whether anyone asks the borrower for documents.
How each role’s work changed
LOs no longer start every file with a paystub request. They run an instant verification, check whether it returned usable data, and request documents only if it didn’t. Semrani said this freed LOs from coordinating documents so they could spend that time advising borrowers. Borrowers with an instant match confirmed their employer and income and continued. Those without a match could log in to their payroll provider inside the application instead of finding and uploading files.
Underwriters review fewer W2s and paystubs and clear fewer income conditions because the file arrives with verified income.
Earlier verification also made more loans eligible for Day 1 Certainty and rep and warrant relief. Semrani said the bank hadn’t taken much advantage of that relief before, because verification typically came after the documents were already in the file.
Operations teams still manage exceptions and still decide when a file needs documentation. Semrani said the benefit for those teams was being able to apply their expertise to the exceptions, rather than spending time on loans that didn’t need it.
Adoption depended on certainty
Semrani said “the technology piece was the easiest.” The harder work was getting LOs, processors, and underwriters to rely on an automated result after more than 20 years of working from documents. He summed up a lesson from earlier in his career: “people don’t resist change, they resist uncertainty, they resist complexity.”
Early on, LOs and operations teams had practical questions about the data and how it would hold up downstream. Semrani said the bank addressed those concerns openly, then focused on making the process predictable.
- They tested the full experience end to end. That meant confirming the report landed in the right place in the LOS with the right permissions, in addition to confirming the verification ran.
- They set a fixed order of operations. Automation runs first, teams review results, and documents are requested only when needed. Where possible, the system enforced that order.
- They trained by role. LOs learned the borrower experience so they could walk borrowers through it. Operations learned where to find the report, how to read it, and how to re-verify.
- They suppressed document requests in the system. A successful automated verification removes the income document task, whether the borrower completed the application or the LO ran the verification from the lender toolkit.
- They brought user feedback back to the product team. After the enhancements that followed, he said, he no longer hears complaints about the process.
Semrani described the months after launch as a collaboration across teams. If an underwriter asks for income documents on a file that was already verified, the LO, who did that verification up front, can confirm they aren’t needed. Over time, he said, the teams challenged one another and settled into a consistent rhythm.
Measure whether the verification report was usable
Semrani said he doubted the results were achievable when the initiative was first presented, so the team measured closely. They tracked direct verification spend, duplicate orders, turnaround time, manual handling, borrower feedback, and the number of providers under vendor management.
After launch, the bank’s verification costs declined materially, and the savings grew month over month as adoption increased. The large majority of its verifications now run through a single integrated ecosystem. When the bank compared loans with automated verification to loans without it, the automated files reached clear to close six to seven days faster in the months he cited.
On measurement, his advice was specific: “Don’t measure success by whether the integration worked or returned a report. Measure by whether the report was usable.” In practice, a usable report means the LO didn’t request the paystub, the underwriter didn’t condition for it, and no one ordered a second verification. The bank now tracks adoption by LO, processor, and underwriter, and reviews verifications per loan number to find re-orders that shouldn’t have happened.
M&T runs this process on Blend’s mortgage point of sale, with Truework verification embedded in the application. The instant lookup, payroll login, and VOI report happen inside the borrower’s workflow, and the data goes to the LOS.
Map the journey before choosing a vendor
His advice to other lenders is to decide on the operating model before evaluating technology. Start by mapping the journey from application through LO review, fulfillment, verification, and re-verification. Look for places where the same information is requested twice, where users move between systems, and where exceptions occur. From there, decide where verification runs, which method runs first, who reviews the results, and which documents are needed and when.
A few questions for your next operations review:
- How many verification providers show up in your application codes, and could anyone defend each one?
- On what share of files does an LO request income documents before anyone attempts a verification?
- When automation does verify income, what stops a processor or underwriter from asking for the paystub anyway?
- Are you measuring whether integrations return reports, or whether those reports remove work?
If the answers show documents being requested before anyone checks whether they’re needed, the sequence is the place to start. M&T’s results came from changing that order first, then giving its LOs, processors, and underwriters a process they could rely on. To hear the full conversation between M&T Bank, Truework, and Blend, watch the on-demand webinar, “How to Eliminate Verification Bottlenecks and Protect Your Margins.”
Find out what we're up to!
Subscribe to get Blend news, customer stories, events, and industry insights.