FIN.20:5.1 - Separate the expectation, the action plan and the spending right

Extend the constructed meeting case above. One unit has a target to collect 100 by day 10. Before the meeting, customer evidence supports an expectation of 60 by that date and 40 by day 25. Treasury must pay 80 on day 12, has opening cash 20 and must retain reserve 10. The manager also has an existing spending authorization of 80 for that payment. These quantities serve different uses.

If the forecast is overwritten with the target of 100 on day 10, the cash account shows 120 before payment and 40 afterward. Using the supported expectation instead gives 80 before payment and zero afterward, exposing a need for net finance of 10 to preserve the reserve. The target can remain 100 and the spending authorization can remain 80 while this gap is addressed. Editing the forecast to 100 has supplied no additional money.

The proposed meeting change preserves three statements: the collection expectation remains 60/40 on its supported dates; the commercial team identifies attainable action that might accelerate the remaining 40; and treasury compares a funded response for the day-12 payment. If a customer later actually agrees and performs an earlier payment, FIN.17 updates the relevant position and forecast. The action plan and expectation change on their own grounds.

Suppose a new platform would reproduce the same manager-imposed date because the meeting still requires target and forecast to agree. It would leave the identified use problem intact. The bounded meeting intervention therefore addresses a different relation from the software replacement. If investigation instead shows that the old date came from a delayed data feed and the manager preserved all information available, the source process is the needed repair; the proposed cultural explanation must change.