Verification of assets · VOA

Asset verification.
A clearer view of funds.

Bring bank balances, account ownership, and supporting activity into one review. See the funds behind the application, with the records close at hand.

Asset recordSOURCE RECORD

Reported account balance

$84,260.00
Account
Checking · 4821
Record date
October 01, 2026
Balance and source date together
Account assetsBalance · Ownership · Activity
Illustrative records · not borrower data

The record behind the result

Understand the account.
Then review the funds.

An account balance is useful when your team can place it in context: who owns the account, when the record was obtained, and what activity supports it. Fintegral’s verification of assets helps lenders bring those details into the borrower file through an authorized connection.

Use the returned records alongside your institution’s review of down payments, reserves, and funds for closing. Your team decides which accounts, dates, and supporting explanations the application requires. The verification gives your reviewers a clearer starting point.

01

Balances with a date

Review the reported account balance and the date of the supporting record. Keep the point-in-time nature of the evidence visible as the loan file progresses.

02

Ownership in context

Bring available account-holder information alongside the balance. An account’s name and ownership details matter when your team is reviewing whose funds are available.

03

Activity for the review

Look at supporting transaction activity where available. Give reviewers a way to follow deposits, transfers, and other changes that need context under your policies.

Details that matter

A useful asset review
starts with four questions.

Keep the request, the returned facts, and your team’s assessment connected.

Review the integration guide
  1. 01

    Whose account is it?

    Review account ownership information against the borrower file.

  2. 02

    What balance is shown?

    Read the returned amount and the date of the source record together.

  3. 03

    What changed?

    Use available activity to understand movements that merit an explanation.

  4. 04

    What can we retain?

    Keep the verification result and available supporting records with the file.

A connected workflow

A clear path.
From request to review.

  1. 01

    Define the asset request

    Choose the account information and review period your lending workflow needs.

  2. 02

    Obtain borrower authorization

    Guide the borrower through the applicable source connection and permission steps.

  3. 03

    Review the returned evidence

    Bring the result into your loan file and assess it using your own underwriting policy.

Your institution sets its policies and makes the lending decision. Product scope, source availability, and authorization requirements apply.

A closer look

Asset verification.
Your questions, answered.

Useful details for planning the request and reviewing the records.

Talk through your requirements
What is verification of assets?

Verification of assets, often called VOA, brings information about a borrower’s financial accounts into a lending review. Relevant records can include balances, ownership information, and supporting activity. Availability depends on the source, account, and product scope.

Is asset verification the same as proof of funds?

Asset verification supplies records your team can use in a proof-of-funds review. That review still needs the account owner, record date, intended purpose, and any supporting context required by your institution. Explore our proof-of-funds workflow for that use case.

Does every product include a PDF report?

The current integration guide describes a PDF report for supported VOA orders, in addition to the returned result. Confirm report availability and required fields for your implementation. The guide explains how report seals can be checked.

How do we confirm bank and account coverage?

Share the institutions, account types, records, and connection experience your borrowers need. Our team can confirm the source requirements for your use case before you plan an integration.

Make the next request a clearer one.

Bring your records, sources, and workflow requirements. We’ll help you define the verification that fits.

Discuss asset verification