Ocrolus AIM Check: What Early Assessment Means for Income Relief

Ocrolus announced its integration with Freddie Mac’s AIM Check on September 10, 2026, offering early income assessment within Ocrolus Analyze. The company says lenders can use extracted wage-earner data from W-2s and pay stubs as early as preapproval, before a complete Loan Product Advisor (LPA) submission. Ocrolus launch release

Income representation-and-warranty relief for that preapproval workflow depends on the later LPA submission, feedback and applicable requirements. Freddie Mac describes that sequence in its March 2024 release notes.

For teams evaluating mortgage workflow technology, the handoff to LPA is therefore central to the buying decision. Staff should be able to trace the document data through the early assessment to the eventual relief findings.

What the announced integration covers

Ocrolus’s September 10 product announcement describes an income breakdown covering base pay, overtime, bonus and commission, with AIM eligibility displayed by income type. It also describes a saved AIM Check certificate and expiration date, submission history, and an option to import income values, the report ID and the certificate into Encompass. These capabilities are described by the vendor in its product announcement.

The announced wage-earner scope is narrower than that of some other Freddie Mac offerings. Its July 2026 LPA release notes, posted June 17, describe a separate Income Calculator API supporting paystubs, W-2s, tax returns and tax transcripts. That broader document list does not establish what Ocrolus’s AIM Check integration supports.

Policy eligibility and technical availability also differ. Freddie Mac’s September 2 Bulletin 2026-12 added written verification of employment (VOE) as eligible documentation for automated income calculation assessment, while directing readers to forthcoming October release notes for technical implementation dates. Because the Ocrolus launch announcement names W-2s and pay stubs, buyers should obtain confirmation before assuming written VOE support. Bulletin 2026-12, primary document

How the report ID connects AIM Check to LPA

The report identifier connects the early calculation to the later relief assessment. Freddie Mac describes the sequence as follows:

1. Submit the digitized document data. Data from the borrower’s paystubs and W-2s goes to AIM Check with a report ID.
2. Review the preliminary calculation. AIM Check provides an early view before a full application goes into LPA. The report ID then accompanies the LPA submission for relief assessment. March 2024 LPA release notes
3. Review the Feedback Certificate’s relief finding and requirements. Freddie Mac’s February 2024 message specifications tie the calculation-relief finding to the borrower, employer, submitted income and provider report identifier. Freddie Mac’s digitized-income feedback messages

A provider demonstration should show how this sequence handles changes to a file. Consider a hypothetical borrower file that receives a newer paystub after its first assessment. Ask the provider to demonstrate how the updated data reaches the assessment and how staff trace it through the subsequent LPA submission and feedback. Displaying the earlier calculation would not establish that connection.

Closed loans follow a separate workflow. Freddie Mac’s August 7, 2024, explanation describes a post-close use of the API with a different process. That capability does not establish that Ocrolus’s announced preapproval workflow includes post-close assessment.

What remains the lender’s responsibility

For the digitized paystub and W-2 route, Freddie Mac’s March 2024 notes limit income relief to calculation accuracy; the underlying data is outside that relief.

The lender therefore still needs controls over data accuracy and borrower/employer matching. Freddie Mac’s February 2024 feedback specifications flag cases where income data cannot be linked to the submitted employer and direct users to verify that the documents match the borrower’s employment and application.

Income-document retention instructions have changed since those messages. Bulletin 2026-7, dated June 3, directs sellers to retain the income documentation identified on the last applicable Feedback Certificate or Income Calculator Certificate in place of other Guide-prescribed income documentation. Its separate expansion of data-relief eligibility concerns tax transcripts submitted through the Income Calculator API. Neither change establishes blanket data relief for Ocrolus’s announced wage-earner integration. Bulletin 2026-7, primary document

The lender’s underwriting-policy or compliance specialist should confirm how these requirements apply to its implementation. The distinction between automated findings and remaining loan conditions matters here: an early result leaves the lender with requirements to satisfy and evidence to retain.

Which efficiency claims still need evidence?

Ocrolus says the integration reduces duplicate entry and manual effort, speeds assessment and reduces potential loan defects. Its launch release provides no measured processing-time reduction, defect-rate comparison or evaluation methodology for this integration. Those benefits remain vendor assertions that buyers should test before using them in a business case.

A pilot for lender operations should measure active staff time separately from elapsed turnaround time. It should also count corrections, resubmissions and final relief outcomes across comparable wage-earner files. A quick preliminary response could otherwise obscure work that moves to a later stage.

What to ask before buying

Ask Ocrolus to demonstrate these points using representative files:

• Document coverage: Which wage-earner cases are supported, and what happens when a file needs another income source or document type?
• Report continuity: How does the correct report ID reach LPA after a correction or updated paystub?
• Result visibility: Can staff distinguish the AIM Check response from LPA’s income-relief findings and outstanding requirements?
• Exception handling: Who owns a failed submission, an expired result or a discrepancy between extracted data and the document?
• Measured performance: What sample, comparison workflow and staff-time measurements support any promised savings?

Make a completed-file demonstration part of acceptance. Require the provider to show how staff can trace the document data, early assessment, report ID, subsequent LPA submission and final feedback together.