← Agent catalogue

AI Agent Profile · LendingIQ · San Francisco

Repayment & ACH Agent AI

Function: ACH Operations ExecutiveInvoked via: ACH operations pipeline — daily debit batch + bounce eventRuntime: AWS Bedrock · us-east-1Model: Claude Sonnet 4Context window: 200K tokens

DivisionLending Operations

Resume

What this agent does

The Repayment & ACH Agent AI operates LendingIQ's ACH mandate infrastructure — setting up mandates at origination, triggering the monthly debit batch, detecting and classifying bounces, executing the configured retry logic, and posting confirmed repayments to the CBS. It is the operational layer that ensures every monthly payment due is attempted, every bounce is correctly classified, and every successful repayment is posted accurately and on time.

Primary functions

ACH Setup

At disbursement — one-time per loan

INVOKED WHEN: Disbursement Agent AI confirms disbursement and triggers the ACH mandate setup

  • Reads the loan account details — borrower's bank account, routing number, monthly payment amount, and debit date — and submits the ACH mandate registration via the Nacha ACH network. Tracks the mandate registration through the processing cycle (typically 7–10 working days) and confirms activation before the first monthly payment due date.
  • Where the first monthly payment due date falls within the mandate processing window, flags this to the Disbursement Agent AI and finance team so an alternative collection arrangement can be made for the first monthly payment.
  • Validates account details via penny drop before mandate submission — a mandate submitted to an incorrect account will fail at activation, delaying setup by a full registration cycle.
Output: ACH mandate submission confirmation with tracking reference. Activation confirmation when mandate is live. First-monthly payment gap flag where applicable.

Bounce Handling & Retry Logic

On every ACH return — same day

INVOKED WHEN: an ACH debit returns with a non-payment reason code

  • Reads the Nacha ACH return reason code and classifies the bounce: Insufficient Funds (R01 — primary collections signal), Technical Failure (R00, R29, bank system errors — retry without collections contact), Invalid Account (R02, R03/R04 — mandate correction required), or Stop Payment / Revoked (R07/R08 — immediate human review, no automated retry).
  • For Insufficient Funds: executes the configured retry schedule — day 3 first retry, day 7 second retry — and routes a bounce notification to the Early Bucket Caller AI for borrower contact. For Technical Failure: retries on the next working day without borrower contact. For Mandate Suspended: routes to collections manager and legal team immediately with no retry.
  • Logs every bounce event with cause classification, retry schedule, and contact routing decision.
Output: Bounce classification — cause code, retry schedule, contact routing decision. Retry execution log. Mandate suspension flag routed immediately to collections manager.

Repayment Posting

On every successful ACH debit

INVOKED WHEN: the ACH network confirms a successful ACH debit for a loan account

  • Reads the successful debit confirmation from the ACH network and posts the repayment to the correct loan account in CBS — allocating the repayment against the oldest outstanding instalment in line with the loan agreement's repayment waterfall.
  • Reconciles the CBS posting against the daily ACH settlement report from the sponsor bank. Any debit confirmed by the ACH network but not settled by the bank within the clearing cycle is flagged to the finance team as a settlement exception.
  • Updates the DPD position in CBS immediately on posting — a successful repayment that clears an overdue instalment reduces the DPD count, which may affect the account's status in the Early Bucket Caller AI's daily work-list.
Output: CBS repayment posting confirmation — account, amount, waterfall allocation, posting timestamp. Daily ACH settlement reconciliation. DPD update trigger to CBS.

Hard guardrails

Will notContact borrowers following a bounce. Borrower contact is routed to the Early Bucket Caller AI.
Will notOverride the retry policy. Retry schedules are configured by the operations team and applied by this agent.
Will notRetry a mandate that has been suspended or cancelled. Mandate suspension is an immediate human review event with no automated retry.

Known limitations

Nacha ACH return reason codes are sometimes ambiguous or incorrectly populated by sponsor banks.A return coded as 'technical failure' may actually reflect insufficient funds. Where a 'technical failure' bounce is not accompanied by any ACH network outage report, flag it for the ops team's review before applying the no-contact retry treatment.
ACH mandate activation timelines vary by bank.Most sponsor banks process mandates in 7–10 working days; some take up to 21 days. For high-volume origination periods, configure the ACH setup trigger earlier — at sanction rather than disbursement — to reduce the gap between disbursement and mandate activation.
Agent Profile · Repayment & ACH Agent AI · LendingIQ · San FranciscoLast updated April 2026 · For internal use

Important Reads

Learn more about how to deploy Repayment & ACH Agent AI to your lending workflow.