Verkflo is in early access. Book a demo

Automate credit limit increase reviews against your policy

The agent gathers the account history and bureau data, runs the exposure and account-conduct checks in your policy, and sends any exception or decline to a person.

Book a demoSee how it runs

Works with

  • Card processor · via Custom REST
  • Credit bureau · via Custom REST

and any system with an API via Custom REST

What is a credit limit increase review?

  • The procedure

    A credit limit increase review decides whether a business card account can carry a higher limit under your credit policy. The analyst looks at account conduct, current exposure and bureau data, and asks for financial statements where the policy needs them. Declines and exceptions need a clear, recorded reason.

  • What the agent does

    • Pulls the account history from the card processor through Custom REST

    • Pulls the bureau file through Custom REST

    • Runs the account conduct and exposure checks in your policy

    • Drafts the request for financial statements when they are missing

  • What your team decides

    • Each decline, with the reason recorded

    • Exceptions to the policy ratio

    • Whether a request for documents goes to the customer

    • Increases above the limits your policy sets for analysts

Example runs for credit analysts, card operations and credit risk teams

Sample data

Limit Review Agent

Reviews each limit increase request against your credit policy.

  • API
  • Google Drive
  • +1

Trigger: Inbound webhook · limit request

From a procedure Limit review · v1.3

Lena

Review the limit increase request on the Halden Trading card.

Limit Review Agent

  1. Pulled the account history from the card processor through Custom REST
  2. Pulled the bureau file through Custom REST
  3. Account conduct is within your policy
  4. Exposure is inside the policy ratio exposure.ratio <= policy.max_ratio

Increase recommended. The request is within the limits your credit policy sets for analysts under v1.3.

4 steps · 0 reviews

Limit Review Agent

Reviews each limit increase request against your credit policy.

  • API
  • Google Drive
  • +1

Trigger: Inbound webhook · limit request

From a procedure Limit review · v1.3

Marcus

Review the limit increase request on the Corvid Freight card.

Limit Review Agent

  1. Pulled the account history from the card processor through Custom REST
  2. Pulled the bureau file through Custom REST
  3. Exposure is above the policy ratio exposure.ratio > policy.max_ratio
  4. Proposed a decline and paused for a reviewer Waiting for a reviewerPriya: decline confirmed, reason recorded

Declined after review. Priya confirmed the decline and recorded the reason. The audit log holds the checks the decision rests on.

4 steps · 1 review

Limit Review Agent

Reviews each limit increase request against your credit policy.

  • API
  • Google Drive
  • +1

Trigger: Inbound webhook · limit request

From a procedure Limit review · v1.3

Tom

Review the limit increase request on the Harbor Lane card.

Limit Review Agent

  1. Pulled the account history through Custom REST
  2. Looked for recent financial statements in the case folder: none on file
  3. Your policy needs recent financial statements for this request financials.latest == null
  4. Asked a reviewer to approve the request for documents Waiting for a reviewerMaya: approved, your team sends it

Waiting on documents. The request for financial statements was approved and handed to your team to send. The review resumes when the documents arrive.

4 steps · 1 review

Setting up the Limit Review Agent

Connect your systems

Read account history from your card processor and bureau files from your credit bureau through Custom REST, and keep financial statements in Google Drive.

  • Google Drive
  • Sumsub
  • ComplyAdvantage
  • Card processor · via Custom REST
  • Credit bureau · via Custom REST

Write the rules

Your exposure limits and exceptions are CEL conditions. A decline always goes to a person before it is final.

Sample data
exposure.ratio > policy.max_ratioAsk a reviewer
financials.latest == nullRequest documents
exposure.ratio <= policy.max_ratioRecommend increase

Add reviewers where the procedure says

The reviewer sees the checks side by side and records the decision and the reason behind it.

Sample data

Review requested: Corvid Freight limit

Reason
Exposure above the policy ratio
Rule
exposure.ratio > policy.max_ratio
Procedure
Limit review · v1.3

Confirm declineApprove exception

Start it from the event

A limit request from your card processor starts the review by webhook, and another webhook fires when documents are uploaded. A daily schedule lists requests still waiting on statements.

  • Inbound webhook · limit request
  • Daily at 06:00 · requests awaiting documents
  • Inbound webhook · documents uploaded

Version and evaluate

Scenarios for a request inside policy, one above the exposure ratio and one with no financial statements run against each new version. A version with a failing scenario cannot be published.

Sample data

Limit review · v1.3Published

12/12 scenarios passed

Limit review · v1.2 Superseded

Limit review · v1.1 Superseded

Share with the team

Credit analysts review declines and exceptions, credit risk authors the policy checks, and card operations can follow each request through its run. Auditors read the decisions and reasons.

  • Admin
  • Author
  • Reviewer
  • Auditor

Questions about credit limit increase reviews

Can the agent approve an increase?

It can recommend one when the request is inside the limits your policy sets, as in the first example. Your procedure sets who signs off.

What does a reviewer see on a decline?

The exposure ratio, the account conduct checks and the policy version, side by side. They confirm the decline or approve an exception, and record the reason.

Which credit bureau does it use?

The bureau you already use, through Custom REST. Verkflo has no built-in bureau connector.

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