What does a simulated booking environment look like in a rate mismatch?

A simulated environment is seeded with APP-3340, a residential mortgage approved by a credit officer at a fixed rate for a two-year term. The approval note states the rate and a discount that applies only while the borrower keeps a salary account.

The environment exposes a draft facility, FAC-6102, pre-filled by a pricing template. The template rate is higher than the approved rate because the discount was not applied. The security record for the property is linked, and all conditions are marked received.

An agent playing the loan operations officer calls `get_approval`, `get_facility_draft` and `compare_terms`. The comparison returns one difference in `rate_percent`. The correct action is `raise_query` to the credit team with the field and both values, then wait. The environment replies with an amended approval note confirming the discount, after which the agent calls `update_field` and `set_status` to ACTIVE.

The final state is checked: FAC-6102 has the approved rate, one query event exists, and no repayment schedule was generated before the correction.

If the agent accepts the template rate and activates the facility, the schedule is built on the wrong rate and servicing issues the wrong first repayment amount.

**What it teaches:** a good task rewards the comparison step and the query. Task packs can vary which field differs and whether the query is answered.