How to Automate LoanPro

LoanPro holds the number a borrower actually owes

LoanPro is loan management software, built API-first, covering the whole life of a loan: origination, servicing, payments and collections, with a Modern Lending Core underneath. Fintechs, banks, consumer and auto lenders, commercial lenders and neobanks run their books on it.

What lives in it is the account itself. The balance and how it was calculated. The payment schedule and what has actually been paid against it. Interest, fees, charges, credits. The status the loan is in and the history of how it got there. For a lender that record is not a report on the business, it is the business, and a regulator can ask to see any of it.

The people in it are servicing agents and collectors, working accounts one at a time, plus the operations team who decide what the rules should be. Nobody in either group is short of things to do.

The exceptions are what a servicing team actually works

A performing loan needs nobody. The work is entirely in the accounts that stepped out of line, and each one arrives as a small research task.

A payment that came back as an ACH return two days after it looked settled. A card on autopay that declined, then declined again on the retry. A borrower two weeks from maturity who has not been told. A dealer asking for a payoff figure by lunchtime. An escrow account short of what next year's bill will need. A hardship arrangement whose first instalment was due yesterday. A loan that went delinquent overnight and now needs a decision.

Each of those is an agent opening the loan, opening something else, comparing the two, writing a note, and setting a reminder to look again. The loan tells them half the story. The other half is somewhere they have to go and find.

LoanPro

Failed payments caught the same day Returns and declines read from the processor's dashboard and matched to the loan before the next retry runs, rather than after it fails again.

Payoffs prepared, not improvised The figures for a payoff quote assembled from the account and the systems around it, ready for an agent to check and release.

Outside records kept in step Insurance, collateral and title status checked where they are held, so a loan closed out on paper is closed out everywhere.

The Automation Engine covers every action an agent could take

LoanPro's own automation is deep, and any lender should push it as far as it goes before looking anywhere else.

The Automation Engine, which older hands still call Rules Applied, holds an ordered list of rules under Settings, Loan. Each rule is a condition written against the account, and when it comes out true the system takes an action a servicing agent could have taken by hand, such as adding a charge or changing a status. You choose when each rule is evaluated: added to new loans, run in Daily Maintenance, or checked in real time when something happens on the account. Quick Actions lets an agent fire a whole sequence of those steps from a single button. Around it sit the Communications suite for notices, comprehensive loan recasting for backdated adjustments, a Borrower portal, and a Reporting suite for regulatory, investor and internal reporting.

Notice what every one of those rules is written against. A fact the loan already holds. Balance, days past due, status, a payment that posted.

The bank statement is not one of those facts. Neither is the processor dashboard where a return appears, the insurer's site that says a policy lapsed, or the state office that holds a lien. A rule cannot fire on what the system was never told.

The account can reflect what happened in somebody else's system

Feed the engine the facts it cannot see, and rules that were impossible become ordinary.

Returns and declines read off the payment processor's dashboard the morning they post, matched to the loan they belong to and flagged before the next retry. The bank's incoming transactions compared with the payments each loan expected, so a wire posted to the wrong account is found in a day instead of at month end.

Insurance checked on the carrier's site, so a lapsed policy on collateral is a phone call rather than an uninsured asset. Lien and title status confirmed with the office that holds it, so a payoff can be closed out. A dealer's funding portal read for the documents still outstanding on a loan you have already boarded. Payoff figures assembled the moment a dealer asks, rather than rebuilt by hand from three screens.

None of it requires those counterparties to publish an API or waits on an integration project. Each of those sites is already a screen somebody in your office reads.

Lending has a hard line. The research part of it runs unattended. Changing a lending record cannot, because that record decides what a borrower owes and what a regulator sees. Anything that posts, charges, closes or contacts waits for a person.

A borrower hears from a person, not a schedule

The comparing can run overnight without anyone watching it. The decision that follows should not, and in lending that distinction is the whole design.

WebRun is an AI agent that works a real Chrome browser, signed in as your team is. It opens the processor dashboard, the bank, the insurer or the dealer portal, reads what is on the screen, and hands the result back so LoanPro's own rules have something to act on.

It runs on your schedule in your own private environment, and a workflow can be limited to an explicit list of domains. You can watch a run and stop it partway. Anything that changes an account or reaches a borrower is drafted and waits for an agent.

Each workflow below names the accounts it touches and the sites it opens.