In any lender, leasing company or microfinance institution, a surprising share of processing time is not spent deciding anything. It is spent chasing. The application arrives without the second guarantor’s signature. The utility bill is older than three months. The National Identity Card number on the form does not match the copy attached. Each gap means a call to the branch, a call to the customer, and a file that sits for days. An agent that checks completeness before a file moves forward can remove much of that back and forth, without going anywhere near the credit decision itself.
Completeness is not credit
Be precise about the job from the start, because the line matters in a regulated business.
- The agent checks: are all required documents present, are required fields filled, are signatures where they should be, do names, numbers and addresses agree across documents, are documents within their validity period.
- The agent does not: assess repayment capacity, recommend approval or rejection, score the applicant, or judge whether the customer is trustworthy.
This separation keeps the tool out of the hardest questions about fairness and explainability in lending. A completeness check produces a list of facts that anyone can verify by looking at the file. A credit decision involves judgement, and it belongs with trained officers and committees who can be held to account for it.
Turning your checklist into rules
Every lender already has a checklist, often a printed sheet stapled to the front of the file. That sheet is the starting point. Go through it line by line and rewrite each item so it can be checked without judgement.
- “NIC copy attached” becomes: a document identified as a National Identity Card is present, both sides are visible, and the number matches the number on the application form.
- “Proof of address” becomes: a utility bill, bank statement or Grama Niladhari certificate is present, dated within the last three months, and the name and address match the form.
- “Guarantor signed” becomes: the guarantor section has a signature, the guarantor’s name is filled, and a guarantor NIC copy is present.
Different products need different checklists. A gold loan, a leasing facility and a group microfinance loan have very different files. Keep a separate list for each product type, written down and owned by the credit or operations team, not buried in the software.
What the agent’s output looks like
For each file, the agent produces a short, fixed report rather than a paragraph of opinion:
- A status: complete, or incomplete with the number of issues.
- A list of each issue, with the document and page it refers to. “Utility bill dated five months before application date.” “Signature missing on page 3, guarantor declaration.”
- A list of items it could not check, for example a page too blurred to read.
The branch officer receives the list the same day and can call the customer once with everything needed, instead of three times over a week. That alone changes the customer’s experience. The file only moves to the credit team when it is complete, so credit officers spend their time on judgement, which is what they are paid for.
A worked example of the time saved
Say a regional office receives 60 applications a day and a checker spends ten minutes per file going through the checklist. That is ten hours of checking a day across the team. If one file in three comes back incomplete, those files are checked again when the missing papers arrive. If the agent does the first pass and staff only confirm its findings, perhaps two or three minutes per file, most of that time returns to the team. The actual figures depend on your products and file quality, so measure your own before and after.
Where it slips, and the safeguards
There are real limits, and they should shape how you use the tool.
- Scans and photos. Files photographed at branches on phones vary widely in quality. The agent should mark unclear pages as “could not check”, never as passed.
- Handwritten forms. Many applications are still filled by hand, sometimes in Sinhala or Tamil. Reading handwriting is unreliable, so name and number matching on handwritten fields needs a person to confirm.
- Signatures. The agent can tell whether something that looks like a signature is present. It cannot tell whether the signature is genuine. That is a fraud control matter and stays with people.
- False confidence. An agent can report a document as present when it has misidentified a different page. Staff should spot-check a sample of “complete” files every week.
Every check, every result and every override by a staff member should be logged. If an auditor or regulator later asks why a file went forward, you can show exactly what was checked and who confirmed it. Customer documents are sensitive personal data, so decide in advance where they are processed and stored, and make sure no file leaves systems you control without that being agreed.
If your volumes are small, a well-designed paper checklist and a careful officer will do this job perfectly well. The agent is worth considering when files pile up, when incomplete files are a regular cause of delay, or when branches are spread out and each round trip costs days. A good first step is to pull last month’s returned files and count the reasons they came back. If the same five reasons account for most of them, you already know what the agent’s first checklist should be.
