Name the purpose
Connect the authorization to the reason for the verification. The request should make sense in the borrower’s application and the institution’s workflow.
Borrower consent and authorization
Borrower consent.
Clear from the start.
Tell the borrower what is being requested, why it is needed, and what they are authorizing. Make consent a clear part of the verification workflow.
Borrower authorizationSOURCE RECORD
A clear request
Know whatyou’re authorizing.
- Purpose
- Mortgage application
- Requested records
- Account assets
- Source
- Selected by the borrower
Clarity before connectionPurpose · Scope · Permission
The record behind the result
A clear request
sets the right expectation.
A borrower should be able to understand a verification request before taking the next step. The purpose, requested records, and relevant source should be clear. Fintegral’s verification workflow ties permission to the work being requested rather than treating it as unrelated paperwork.
Authorization requirements differ by product. IRS transcript requests use the applicable taxpayer authorization process; connected bank and employment workflows have their own requirements. Define those steps with your team before the first request reaches a borrower.
Define the records
Be specific about the product and records required. Tax years, record types, and any follow-up employment request need appropriate scope.
Keep the process traceable
Bring the authorization context into the verification workflow. Plan how your team handles incomplete, expired, or declined requests.
Details that matter
Before asking for permission,
make the request understandable.
Keep the request, the returned facts, and your team’s assessment connected.
Review the integration guideTaxpayer authorization guidance: IRS IVES for taxpayers ↗
- 01
Who is requesting it?
Make the requesting institution and the borrower’s application clear.
- 02
What records are needed?
Identify the verification and its required record scope.
- 03
Why is it needed?
Explain the purpose in language the borrower can understand.
- 04
What happens next?
Set expectations for connection, result delivery, and any follow-up.
A connected workflow
A clear path.
From request to review.
- 01
Define the request
Select the product, purpose, and records your workflow requires.
- 02
Present the authorization
Give the borrower the applicable permission steps and source requirements.
- 03
Proceed within the scope
Request and review records within the authorized workflow, with appropriate follow-up when a new request is needed.
Your institution sets its policies and makes the lending decision. Product scope, source availability, and authorization requirements apply.
A closer look
Borrower consent.
Your questions, answered.
Useful details for planning the request and reviewing the records.
Talk through your requirementsIs one authorization enough for every product?
Authorization requirements depend on the product, source, and intended request. Confirm the relevant consent and record scope for each verification in your implementation.
How are IRS transcript requests authorized?
The IRS describes taxpayer authorization through the applicable IVES process, including Form 4506-C. The requested transcript types and tax years should match the borrower-file need. See the IRS resource linked below for the taxpayer process.
Can consent cover an employment re-check?
The documented employment re-check workflow has requirements for the original borrower grant and permitted window. Confirm those requirements before including re-verification in your closing process.
What should our team do if a borrower does not complete the request?
Use a clear follow-up and exception process appropriate to your institution. Confirm whether a new or corrected authorization is needed before requesting additional records.
Make the next request a clearer one.
Bring your records, sources, and workflow requirements. We’ll help you define the verification that fits.