Checkr–Truv Acquisition: Mortgage Verification Continuity

Checkr announced its acquisition of Truv on August 18, 2026, adding consumer-permissioned income, employment and asset verification capabilities. For mortgage lenders using Truv, the immediate task is to verify service continuity. The announcement does not establish improved completion rates or guarantee unchanged integrations; lenders need evidence that borrower authorization, data retrieval and underwriting reports will continue to work together.

How the verification channel shapes the workflow

In Truv’s payroll process, the borrower authenticates access to an employer or payroll account and authorizes retrieval of information for the requesting lender. That can replace collecting and uploading pay documents, but the borrower must complete that step before the lender receives data. Truv described the process in its December 2024 verification explainer.

Other channels obtain evidence differently. An employment database receives information from employers and payroll contributors; Equifax describes that model in its 2025 annual report. Document collection and direct employer contact are separate routes. A bank connection retrieves account information rather than the underlying payroll record, even when deposits help establish income, as Truv’s explanation of the channels describes.

Those differences shape fallback procedures. A failed payroll login requires different follow-up from an unavailable employer record or an incomplete document upload. Consumer permission is not unique to payroll connections: Fannie Mae’s June 2026 workflow guidance starts with borrower consent before ordering a verification report.

What the 96% workforce claim measures

Checkr’s August 18 release says Truv’s network reaches 96% of the U.S. workforce. It does not provide the calculation, measurement date or a mortgage-lender completion sample behind that figure.

Truv’s own May 2023 explanation of coverage and conversion distinguishes people who can connect from those who complete the permissioning process. That distinction remains useful, though its older coverage figures should not be substituted for the acquisition announcement’s claim.

Workforce reach therefore cannot establish how often a lender’s applications produce usable underwriting evidence. Evaluate each stage separately:

Use the same measurement period across stages and identify repeat attempts. A connection rate alone cannot show how much follow-up work a usable report requires. For lender operations, the comparison should include total expense per usable report, staff intervention and fallback costs.

Get continuity commitments for the existing integration

Truv’s February 4, 2026, integration announcement described an expansion into Encompass Consumer Connect, supporting income-and-employment verification, asset verification and document-upload fallback within the application. Truv said the resulting income-and-employment or asset data could move into Encompass with configurable field mapping.

Checkr’s acquisition release does not specify a migration schedule, API changes, contract amendments or pricing commitments. That silence establishes neither a mandatory migration nor a guarantee that existing arrangements remain unchanged.

Request a written continuity statement covering the lender’s actual configuration: application entry point, authentication, report delivery, field mapping, refresh orders and support escalation. Have the provider identify any changes to the contracting entity, assignment provisions, service levels and renewal pricing.

Test the existing configuration and any proposed replacement in the lender’s mortgage workflow technology, including a refreshed report’s path through underwriting. Preserve sample reports and mapping results to document how each configuration behaves. A consolidated provider could simplify support, but that benefit depends on the integration and service commitments delivered.

Approval depends on the report and underwriting workflow

Fannie Mae’s June 2026 integration-and-testing guide included Truv income-and-employment test cases. It describes Desktop Underwriter (DU) retrieving a vendor report using a reference or loan number, performing calculations and returning validation messages. Day 1 Certainty depends on validated components and compliance with the applicable requirements and DU messages.

Fannie Mae also states that eligible vendors and tools remain subject to lenders’ own approval processes. Availability through a combined company does not establish acceptance of every output.

Document the supplier, product, report type, identifier mapping and intended underwriting use separately. If a migration changes any of those elements, require evidence that the new route meets the relevant enterprise and lender requirements before expanding its use.

Confirm permission scope and retention terms

Truv’s privacy policy, marked updated March 2026, permits information transfers in an acquisition as allowed by law or contract. Its retention provision describes service, business and legal purposes without setting one fixed deletion deadline. These provisions leave transaction-specific implementation questions for the provider and lender.

Obtain the actual borrower authorization text and data-processing terms for the mortgage product in use. Compare any proposed recipients, refresh frequency and additional uses with that authorization; shared ownership alone supplies no evidence of permission. The review should establish:

• Access and purpose: which accounts, fields and history are retrieved; which entities receive them; and whether refreshes or additional uses require further authorization.
• Storage and deletion: retention periods for source data, generated reports and backups, including exceptions and what happens when access is revoked.
• Accountability: who handles access logs, incidents, corrections and unresolved disputes after any operational transfer.

Have privacy or legal counsel assess those terms against the lender’s obligations. Keep the borrower’s separate correction process accessible while ownership and support arrangements are reviewed.

Before approving a changed workflow, obtain three records: the provider’s written continuity commitments, a documented comparison of report delivery and underwriting results, and the applicable permission and retention terms. Those records give operations leaders a basis for deciding which changes to accept.