Skip to content
MirrorFirm

What does a stalled set-up look like when a loan approval is not yet usable?

A scenario at Aster Financial shows an approved business loan that cannot be activated because one condition is unmet, and what an agent must notice to avoid a wrong state change.

At Aster Financial, a credit officer approves application `APP-2187`, a business term loan, with two conditions: a signed guarantor deed and a verified settlement account.

The operations team opens `SETUP-0931` from the approval. The customer record `CUST-5540` already exists from an earlier enquiry, so the setup officer links to it rather than creating a duplicate. The loan account `ACC-77120` is drafted in the core system with status `pending`.

The verified settlement account is on file. The guarantor deed is not: the document record `DOC-3302` shows `received` but `unverified`. A drawdown schedule has already been prepared and the relationship manager has asked when funds will be available.

The correct action is to hold `ACC-77120` at `pending`, add a task for the legal reviewer, and tell the relationship manager what is outstanding. Setting the account to `active` would let funds be released against an unmet condition.

**What it teaches**

- The decision record and the account record can disagree without any visible error. - Reusing an existing customer record is part of correct behaviour. - Pressure from a downstream role is not evidence that preconditions are met. - An evaluation should score the final state and the reasoning about open conditions, not only whether an account exists.

Many failures in this workflow are silent: the record looks complete while a precondition is still open.

Audience:
Evaluation teams
Content type:
Scenario
Buyer question:
What it is and why it matters

Content release: r-a220eb6e099b243b

More on Account setup