Know what was requested
Keep the verification product and the borrower authorization in context. A returned result should be read within the scope of the order that produced it.
Evidence for the borrower file
Verification evidence.
Clear enough to review.
A useful verification is more than a status. Give your reviewers the source context, supporting records, and timing they need to understand the result.
Verification evidenceSOURCE RECORD
The borrower file
From resultto review.
- 01Defined requestProduct and borrower permission
- 02Returned factsSource context and record date
- 03Supporting recordAvailable report or deliverable
Keep the contextRequest · Record · Review
The record behind the result
A clearer file.
A more informed review.
A result is easier to use when the reviewer can understand the request behind it. Which product was ordered? What information came back? Which source and date give the facts their context? Fintegral keeps the verification experience centered on those practical questions.
Bring the returned evidence into the loan file where your team works. Keep income, employment, asset, and tax records connected to their purpose, and preserve the distinctions between them. Your team remains responsible for interpretation, policy, and the lending decision.
Keep the source visible
Review the available source information and dates alongside the facts. Context helps another reviewer understand what the record supports.
Retain the deliverable
Use the result and available report or supporting records in your file. Product-specific deliverables are described in the integration guide.
Details that matter
Four parts of
a reviewable record.
Keep the request, the returned facts, and your team’s assessment connected.
Review the integration guide- 01
The request
The product and purpose behind the verification.
- 02
The returned facts
The information available within that product’s scope.
- 03
Source and timing
The context needed to read the record appropriately.
- 04
Your team’s review
The assessment and follow-up required by your own process.
A connected workflow
A clear path.
From request to review.
- 01
Order a defined verification
Choose the product that answers the borrower-file question.
- 02
Receive the scoped result
Read the returned facts with their available source context and supporting records.
- 03
Bring it into review
Retain the deliverable in your workflow and record your team’s follow-up as appropriate.
Your institution sets its policies and makes the lending decision. Product scope, source availability, and authorization requirements apply.
A closer look
Verification evidence.
Your questions, answered.
Useful details for planning the request and reviewing the records.
Talk through your requirementsAre all verification reports the same?
No. Deliverables and returned fields vary by product. The current integration guide describes a PDF report for supported asset verification orders; employment and income workflows have their own result scopes.
How does a report seal work?
The integration guide explains the public check for supported report seals and the distinction between an issued seal and a content-digest confirmation. Your team should follow the documented verification process for the report it receives.
Does evidence replace the underwriter’s review?
Fintegral provides verification results and supporting records. Your team interprets the evidence, resolves questions, applies policy, and makes the lending decision.
Can developers bring results into an existing system?
Review the integration guide for result delivery, supported response fields, webhooks, and report availability. Our team can confirm the workflow and partner access requirements for your implementation.
Make the next request a clearer one.
Bring your records, sources, and workflow requirements. We’ll help you define the verification that fits.