Skip to content
MirrorFirm

What happens when an approval changes while a facility is being set up?

A scenario at Aster Financial in which a pricing amendment and a pending security interest collide during setup, showing why booking state cannot be treated as static.

At Aster Financial, a credit officer approves APP-2187: a commercial term loan of AUD 450,000 over 60 months, secured by a registered charge over a warehouse fit-out. The approval carries two conditions, a signed facility agreement and a lodged security interest.

A loan operations officer opens the booking queue and starts creating facility FAC-5521. The core lending platform accepts the draft, but the security register shows the charge, COL-0931, still in a pending state. The officer notes that drawdown cannot be enabled until the interest is confirmed.

Meanwhile the approval record is amended: the pricing margin is reduced after a relationship review. The officer's draft now carries the old margin. If the facility were activated as drafted, the repayment schedule would be generated on the wrong rate and the first instalment notice would be incorrect, creating a remediation case for the servicing team.

The officer instead refreshes the approval, corrects the margin, waits for COL-0931 to move to confirmed, then enables drawdown and releases the schedule.

**What it teaches:** booking state is not static. A good environment lets the source record change mid-task, and an evaluation should check that the agent re-reads the approval, respects the security dependency and does not activate early.

Environments that let source records change mid-task reveal whether an agent re-reads the approval before activating a facility.

Audience:
Environment builders
Content type:
Scenario
Buyer question:
What it is and why it matters

Content release: r-a220eb6e099b243b

More on Loan booking