Skip to main content
GullySystem
AI for Finance · Solutions

Repayment history and affordability are laid out so the credit officer can judge.

AI Credit Risk and Scoring reads a borrower’s repayment history, account behaviour and the documents in the file, then ranks applications and open loans for a credit officer’s attention. This is decision support. The tool flags and ranks. A qualified person makes every lending decision. None of it is advice.

What it is

A loan file is mixed evidence. Two bank statements, a pay slip, a guarantor’s signature and the last loan’s repayment record sit in different places, and the officer has an afternoon to weigh them. Habits that matter hide in the detail.

GullySystem sets this up beside your loan or lending software, with scoring rules agreed in writing with your credit head before any file is ranked. Reasons are shown beside every ranking. An officer can overrule any ranking, and the decision and the reason are written to the file for the credit committee and the next review.

Where it goes wrong today

The problems this is meant to ease.

Evidence sits in different places

A loan file is scattered. Statements, pay slips, guarantor papers and the last loan’s record sit in different folders, and the officer has an afternoon to weigh them before the applicant calls again.

Officers rank the same file differently

Judgement varies between officers. One treats a late instalment as a warning and another as noise, so two similar borrowers get different treatment depending on which desk the file reached.

Running loans drift unseen

Trouble starts quietly in the account. Deposits thin out and payment dates slip by a few days, yet nobody opens a running loan until it is badly late.

Portfolio exposure is guessed

The book is seen late. Exposure by branch, product and borrower group is built by hand for the committee, so a growing concentration shows up a quarter after it formed.

Reasons for decisions go unrecorded

Files lack written reasons. When an officer approves against the usual pattern or declines a file that looked fine, the reason lives in memory, and the review team cannot judge it later.

Inside the module

What AI credit risk and scoring does.

Repayment history in one view

Instalments from earlier loans, on time, late or missed, are laid out month by month, with days past due shown against each one. Late is not missed.

Affordability from the statements

Salary credits, existing instalments and recurring bills are read from uploaded bank statements, so the officer sees what is left after fixed commitments each month.

Other data, only with consent

Other data such as utility or mobile payment records is used only where the borrower has agreed and your lender policy allows it. Consent is recorded first.

A ranked queue with reasons

Applications are ordered for review, and the main factors behind each position are listed in plain words that a branch officer can repeat to the borrower. A ranking is a prompt to look. Nothing is decided by score.

Overrides written down

When an officer approves a file the ranking did not favour, or declines one it did, the reason is typed in and kept. The notes show where rules need revisiting.

Open loans and portfolio trends

Running loans are re-read each week, and an account whose balance, deposits or payment dates have drifted is listed for a call. Exposure by branch, product and borrower group is charted month by month, so the credit head sees where the book is thickening before the committee meets.

Policy steps in the workflow

Your credit policy is written in as steps: documents required, limits per officer and committee referral when a file crosses a set threshold. Skipped steps are marked.

Model checks and data quality

Before any ranking is used, the scoring rules are tested against closed loans whose outcomes are known, and gaps in the data are listed. Tests repeat on a schedule.

Where it gets used

What this looks like in a working week.

Microfinance lender

A microfinance lender ranks applications from rural groups, with repayment history and attendance notes beside each, so the field officer knows which visits to make first.

Machinery dealer on instalments

A machinery dealer selling on instalments reads a buyer’s record on earlier machines and recent statements, then hands the credit manager a file with the missing papers listed.

Wholesale distributor on trade credit

A distributor giving trade credit lists customers whose payment days have lengthened over three months, so the credit controller can call before the next large order is released.

Dental clinic with payment plans

A dental clinic offering treatment on payment plans reviews its own patients’ past plan payments before a new plan is agreed, and the practice manager decides on every plan.

Housing finance team

A housing finance team compares collateral valuation notes and income documents with the loan history of the same family, and the committee reads the reasons beside each ranking.

Who touches it

The people who open this every day.

Credit officer

Opens the ranked queue, reads the reasons beside each application, and asks the borrower for the missing statement before forming a view. The file stays open.

Head of lending or credit committee

Reviews cases where officer and ranking disagreed. Uses the written overrides to decide whether a scoring rule still fits the borrowers you actually lend to, or has drifted away from them.

Collections or recovery team

Gets a weekly list of running loans showing early signs of stress, with the last payment dates and contact notes already in front of them.

Risk or compliance officer

Reads the stored reasons and overrides for each decision when an internal review or an outside inspection asks how a file was handled.

How it is set up

From first conversation to daily use.

  1. Write down the credit policy

    Sit with the credit head and write the current lending policy as steps: documents required, limits per officer and committee referral in plain words. Note who decides what. Setup follows that paper.

  2. Check the loan and statement data

    Export applications, repayment schedules and uploaded statements from your lending software, then list missing dates, duplicate borrowers and loans with no recorded outcome. Weak data gives weak rankings.

  3. Trial on closed loans

    Rank a batch of closed loans whose outcomes are known, without showing the outcome to the model, and compare the order it produces with what actually happened to borrowers. Note where the rules misread people.

  4. Review rankings with credit officers

    Put real applications in front of the officers who will use the queue, let them rank by hand first, and then show the software’s reasons beside their own. Every disagreement gets a written note.

  5. Go live with a person on every file

    Switch on the ranked queue for new applications and the weekly list for running loans, while every approval and decline stays with a credit officer under your own policy. Overrides are typed in with reasons.

  6. Review the rules and the data

    After a few reporting cycles, the credit head and the risk officer read the overrides, the late accounts and the data gaps together. Stale rules are rewritten or retired.

Measuring it

How you would know it is working.

Record where you stand before it goes live, so the change is measured against your own figures.

  • Risk model quality is how well past rankings matched the outcomes of closed loans, tested on a hold-out set of records and compared with the officers’ own hand ranking.
  • Portfolio delinquency is the share of running loans past their due date, read from the repayment schedules and compared with the figure recorded just before go-live.
  • Review turnaround time counts the days an application waits between upload and a recorded officer decision. Timestamps in the lending software from before go-live give the starting figure.
  • Override rate is how often officers decided against the ranking and wrote a reason, counted from the decision log, with a baseline set during the trial on closed loans.
  • Data completeness is the share of applications with every required field and statement present on arrival, compared with a sample of files from before go-live.
Used responsibly

Where a person stays in charge.

Indicators for qualified people only

The tool gives risk indicators. A qualified credit officer makes every approval, rejection and pricing decision, and no output should be read as a verdict on a borrower’s creditworthiness or a promise of eligibility.

Reasons stay visible

Every ranking shows its reasons. If a reason cannot be put in plain words, the factor is dropped from the scoring rules, because an officer must be able to explain it to the borrower.

Data quality and fairness are tested

Models drift and data goes stale. Rankings are tested on closed loans before use, retested on a schedule, and reviewed for groups of borrowers who may be treated unfairly by a factor that looked neutral.

Consent and privacy

Borrower data is sensitive. Utility, mobile and similar records are used only where the borrower has agreed and your lending policy allows it, and every consent is stored before the data is read.

Rules differ by country

Lending rules vary by country. Your own lawyer or compliance adviser sets the disclosure duties and the limits on automated decisions. The software only prepares data and gives no legal, regulatory or financial advice.

How it fits

It is one part of a system, not an island.

A module earns its place by what it passes to the next one. These are the connections we set up most often.

  • Loan management or core lending software
  • Customer and borrower records
  • Document upload and statement reading
  • Collections and follow-up screens
  • Approval workflow for the credit committee
Common questions

Questions owners ask about AI credit risk and scoring.

Does the software approve or reject loans?

It approves and rejects nothing. It ranks files and lists the reasons, and a qualified credit officer makes every approval, rejection and pricing decision under your own lending policy.

What does a lender need before this is worth setting up?

A few hundred closed loans with clear outcomes, consistent fields and repayment dates that were recorded when they happened are the minimum for a useful pattern. A young lender has too little history.

Who is responsible if a ranking turns out wrong?

The lender stays responsible. A ranking can be wrong, stale or built on thin data, which is why the reasons are shown beside it and every override is recorded.

Does it give regulatory or legal guidance?

Disclosure and automated decision rules differ between countries. Your lawyer or compliance adviser works them out with you during setup. Legal or financial advice is not something the software offers.

What data does it read, and what does it connect to?

It reads loan applications, repayment schedules, uploaded statements and officer notes from your lending software, so the setup depends on what that software can export. Statements must be legible.

How accurate is a ranking?

Accuracy depends on the history behind it. Rankings are tested on closed loans before use and retested on a schedule, yet a ranking is a prompt to look and can miss a borrower whose situation changed.

What about borrower privacy?

Borrower files hold identity and income data, so access follows officer roles, and nothing leaves your systems unless your security adviser and your compliance officer have agreed it. Other data sources need recorded consent.

How much effort does setup take?

The effort is mostly agreement. Credit officers and your credit head settle the scoring rules in writing, and old loan records are checked before the first file is ranked.

Talk to us

Tell us how you handle AI credit risk and scoring today.

A spreadsheet, a register or another system: say which, and we will tell you plainly what is worth changing.

  • No obligation
  • A reply within one business day
  • Your details stay private

Start with your requirements

Seven short steps that tell us what you need. An engineer reads them before getting in touch.

Share your requirements