Skip to content
MirrorFirm

What does a sufficiency decision look like on a real lending case?

A credit officer at Aster Financial finds a payslip too old to support an income assessment, pauses the application and issues a specific request, which shows what labelled outcomes should capture.

A credit officer at Aster Financial opens application `APP-2187`, a personal loan. The applicant has supplied a photo identity document, a payslip and the first page of a bank statement.

The officer checks the set against the income verification policy for unsecured lending. Three things stand out:

- the payslip covers a period well outside the policy's recency window - the bank statement is missing its second page, so the salary credit cannot be seen - the identity document is valid and matches the application

The officer does not decline and does not approve. The application moves from `assessment` to `awaiting-documents`, and request `REQ-0412` is created. It names two items: a payslip within the recency window and the second statement page. It carries a response-by point and states that the application will lapse to `withdrawn` if nothing is supplied.

The consequence of getting this wrong is concrete. Approving on the stale payslip would put an income figure on file that the policy does not accept, and the file would fail later review. Asking for everything again would irritate an applicant who has already supplied valid identity.

**What it teaches:** a useful record separates what was sufficient (identity), what was unusable (the payslip), and what was absent (the page). It also records the state change and the exact wording of the request. A model can be scored on each of those separately.

A good sufficiency record shows the exact gap, the request issued and the state change, so your customers can score each step separately.

Audience:
Licensed resellers
Content type:
Scenario
Buyer question:
What it is and why it matters

Content release: r-a220eb6e099b243b

More on Document sufficiency