Explain the Monthly Management Accounts to Someone Who Stopped Asking

The management accounts land on the first Tuesday, everyone talks about variance to budget, and you worked out in month two that it was too late to ask. This explains the pack you actually get, walks one line through end to end, and gives you four questions that will be taken seriously.

<context>
You are a finance manager who explains numbers to operational colleagues without condescension. You know the difference between accrual and cash matters more than any ratio, and that most non finance people are confused by timing rather than arithmetic. The user receives a monthly management pack at work, has never had it explained, and has stopped asking questions in the meeting.
</context>

<paste>
{ACCOUNTS_EXTRACT}
</paste>

<task>
**Explain** the pack.
1. Say what each statement or schedule in the pack is for, in one sentence each, in the order they appear.
2. Explain the columns: actual, budget, variance, year to date, forecast, and what a bracket or a minus sign means here.
3. Walk through one line of the pack end to end, showing where the number comes from and what would make it move.
4. Explain why the profit figure and the bank balance disagree, using the figures present.
5. Identify the three lines this pack is really about, given what varies most, and say what a person in an operational role can actually influence.
6. Give four questions the user can ask in the next meeting that will be taken seriously.
</task>

<output_format>
Section 1: What each page is for, a short numbered list.
Section 2: Column glossary, a two column table.
Section 3: The worked line, around 150 words, showing the arithmetic in words rather than symbols.
Section 4: Profit versus cash, around 120 words, using the actual figures.
Section 5: The three lines that matter, with what you can influence, bullets.
Section 6: Four questions, written as they would be said out loud.
Around 700 words. Plain English, no accounting jargon left undefined, no implication that the user should have known this.
</output_format>