Verkflo is in early access. Book a demo

Credit file review automation before underwriting

The agent pulls the bureau file, compares it with what the applicant declared, applies the flags in your policy and sends differences or adverse findings to an underwriter with the comparison laid out.

Book a demoSee how it runs

Works with

  • Credit bureau · via Custom REST
  • Loan origination system · via Custom REST

and any system with an API via Custom REST

What is a credit file review?

  • The procedure

    Before an underwriter decides, someone compares what the applicant declared with what the credit bureau reports. Undeclared obligations, thin histories and adverse entries all change the case. The review ends in a comparison and a list of flags for the underwriter to weigh.

  • What the agent does

    • Pulls the application from your loan origination system

    • Pulls the bureau file through Custom REST

    • Compares declared obligations with the ones the bureau reports

    • Applies the flags in your credit policy and saves the comparison

  • What your team decides

    • The credit decision

    • Any adverse action, with the reason recorded

    • Whether to ask the applicant about a difference

    • What other evidence a thin file needs

Example runs for underwriters, credit analysts and lending operations

Sample data

Credit File Agent

Checks each credit file against the application and your policy.

  • API
  • Google Drive
  • +1

Trigger: Inbound webhook · application received

From a procedure Credit file check · v1.4

Priya

Check the credit file for the Halden Trading application.

Credit File Agent

  1. Pulled the application from the loan origination system through Custom REST
  2. Pulled the bureau file through Custom REST
  3. Declared obligations agree with the bureau file
  4. No flags from your policy on the file flags.size() == 0

Check passed. The file is consistent with the application and carries no policy flags. The comparison is saved for the underwriter.

4 steps · 0 reviews

Credit File Agent

Checks each credit file against the application and your policy.

  • API
  • Google Drive
  • +1

Trigger: Inbound webhook · application received

From a procedure Credit file check · v1.4

Marcus

Check the credit file for the Corvid Freight application.

Credit File Agent

  1. Pulled the application and the bureau file through Custom REST
  2. The bureau file shows an obligation the application does not declare bureau.obligations.exists(o, !(o in declared.obligations))
  3. Saved the comparison to the case folder
  4. Referred the difference to an underwriter Waiting for a reviewerLena: asked the applicant to explain the difference

Referred. Lena decided to ask the applicant for an explanation, and your team sends the question.

4 steps · 1 review

Credit File Agent

Checks each credit file against the application and your policy.

  • API
  • Google Drive
  • +1

Trigger: Inbound webhook · application received

From a procedure Credit file check · v1.4

Diego

Check the credit file for the Lumen Print application.

Credit File Agent

  1. Pulled the bureau file through Custom REST
  2. The file has too little history for your scoring policy bureau.history_months < policy.min_history
  3. Asked an underwriter, because your policy sends thin files to a person Waiting for a reviewerTom: request bank statements instead
  4. Recorded the alternative evidence requested in the case folder

Alternative evidence requested. Tom chose bank statements as the alternative under your policy. The request is recorded with the application.

4 steps · 1 review

Setting up the Credit File Agent

Connect your systems

Read applications and bureau files from your systems through Custom REST, and keep each comparison and note in Google Drive.

  • Google Drive
  • Sumsub
  • ComplyAdvantage
  • Credit bureau · via Custom REST
  • Loan origination system · via Custom REST

Write the rules

The flags in your credit policy become CEL conditions. The agent reports what it found, and an underwriter makes any adverse decision.

Sample data
bureau.obligations.exists(o, !(o in declared.obligations))Ask an underwriter
bureau.history_months < policy.min_historyAsk an underwriter
flags.size() == 0Check passed

Add reviewers where the procedure says

The underwriter sees the application and the bureau file side by side, with the difference marked, and the decision is logged.

Sample data

Review requested: Corvid Freight file

Reason
Declared and reported obligations differ
Rule
bureau.obligations.exists(o, !(o in declared.obligations))
Procedure
Credit file check · v1.4

Ask applicantAccept explanation

Start it from the event

A new application in your loan origination system starts the check by webhook, and a refreshed bureau file starts another. A daily schedule lists files still waiting on a decision.

  • Inbound webhook · application received
  • Daily at 06:00 · files awaiting a decision
  • Inbound webhook · bureau file refreshed

Version and evaluate

Test each version on a consistent file, an undeclared obligation and a thin file. When your credit policy changes, the new flags are checked against those cases before publishing.

Sample data

Credit file check · v1.4Published

12/12 scenarios passed

Credit file check · v1.2 Superseded

Credit file check · v1.1 Superseded

Share with the team

Underwriters review the files the agent refers, credit analysts author the flag rules, and lending operations can read where each application stands. Auditors read the comparisons.

  • Admin
  • Author
  • Reviewer
  • Auditor

Questions about credit file review automation

What does the underwriter see?

The application and the bureau file side by side, with each difference and flag marked, plus the rule that raised it.

How are thin files handled?

Your policy sets the minimum history. A file below it goes to an underwriter, who can ask for other evidence, such as bank statements in the example.

Can a refreshed bureau file restart the check?

Yes. A webhook from your bureau or origination system starts a new check when the file is refreshed.

Which systems does it connect to?

Your loan origination system and credit bureau through Custom REST, and Google Drive for comparisons and notes.

Controls your auditors will ask about

These controls apply to each agent you build. Sample data

Related use cases

See all use cases

Run this procedure as an agent

Book a demo with your own version of this procedure, and we'll show it running with each step logged.

Book a demo