Six weeks after the close. The audit committee meets to recommend the year-end accounts to the board and to approve the revised budget. The chair has read every paper, including the risk committee minutes. The team answers for the credit notes, the auditor confirms who found them, and the committee reaches its decision: approve, with conditions.
Good afternoon, everyone. Three items: the auditor's report, the year-end accounts, and the revised budget. I've read the papers, all of them, so please don't present them. I'll go straight to questions.
Catherine tells the room she has read the pack and wants questions, not presentations. At board level this is common. Prepare for questions about any page, not for the slides you planned to show.
Understood. We're ready for them.
Alan, I'll start with you. In one sentence, what is your opinion going to be?
An unmodified opinion, subject to the board approving the accounts next week. The accounts give a true and fair view.
Catherine asks for the conclusion before the detail. "Unmodified" is the clean result: the auditor has no reservations about the accounts. The rest of the meeting can then be about why, and about what comes next.
Good. And yet your letter to management has a significant deficiency in it. Those two sentences don't usually sit together comfortably. Help me with that.
The accounts are right. The control that should have kept them right didn't exist. The error was found and corrected before the accounts were finalised, so the numbers are clean. The process wasn't.
Alan separates two questions the committee must ask: are the accounts correct, and can we trust the process that produced them? Both answers matter. A good auditor answers each one directly.
"Clean numbers, weak process." I'd like that in our minutes.
Nadia, the credit notes. I've read the summary. I have three questions. What happened, who found it, and why wasn't it found earlier?
What happened: eleven supplier credit notes for December were recorded in January. The profit effect was a hundred and sixty-eight thousand, above materiality. Who found it: our team, during the close. Aisha noticed the first one when an account didn't reconcile.
Catherine asks three questions, and Nadia answers them in the same order, starting each answer with the question. It sounds formal, but it makes long answers easy to follow and shows nothing is being avoided.
Go on.
Why not earlier: because there was no control that checked the period of a credit note. It happened last year too, on a smaller scale, and nobody saw it.
Thank you. That last part is the one I was looking for. Most people stop after "who found it".
The third question is the uncomfortable one: why didn't you see it sooner? Nadia answers it with a fact that does not flatter the team, a repeat from last year. Committees trust people who answer the hard question, not only the easy ones.
Alan, is that how you saw it?
Yes. Management identified it and told us before our fieldwork began. That's in the letter, and I'd like the committee to know it was my wording, not theirs.
Months ago, Graham's rule was "no surprises: tell people early". Here the auditor confirms it in front of the board. Disclosing a problem before someone finds it changes how the whole story is told.
Then a question for you, Alan. Last year there were six of them. Why didn't your audit find those?
Our cut-off testing used a sample, and none of the six were in it. That's on us as well. This year we tested twenty-five credit notes from January and February, from any supplier, and we reviewed management's own check of last year.
Alan does not defend his firm's earlier work. He explains why it missed the problem and what changed. Owning your part of a failure, briefly and with a fact, makes everything else you say more credible.
Noted. Graham, who decided to tell the auditors before they arrived?
Nadia brought it to me on day three. We agreed it together the same afternoon. I'd rather the auditors heard it from us than found it themselves.
It's the right instinct. I wish I saw it more often.
Now the question I care about most. What stops it happening again?
Three actions. A quarterly review of credit notes, starting in April. A label check by payables for anything above five thousand. And a decision on a system warning by the half-year.
The risk committee minutes say the label check is "in progress", not done. I appreciated that. Most minutes I read say "done".
It hasn't been tested yet. Done means tested.
The phrase "in progress" in the risk committee minutes is noticed by the chair of the audit committee. An honest status costs nothing and builds trust. An optimistic one is remembered when it turns out to be wrong.
Twenty-five thousand for a system warning. Why not simply buy it?
Because we don't know yet if the manual checks are enough. If the April review is clean, we may not need it. If it isn't, the decision becomes easy.
Fine. But I'd rather see it decided early than late. Please don't wait for the half-year if April already gives you the answer.
Understood. If April gives us the answer, you'll hear it in May.
Who owns the quarterly review?
I do. Nadia signs it off.
You wrote the risk committee minutes too, I think.
Yes, that was me.
They were clear. Can I ask you one question directly? When you do the first review in April, what would make you worried?
A credit note dated in March that arrives in April and doesn't get flagged. If that happens, the label check isn't working, and I'd tell Nadia the same day.
Board members sometimes question the person who does the work, not the manager. Aisha answers with one specific example and what she would do. A concrete answer is more convincing than a confident one.
That's exactly the right worry. Thank you.
The budget. Matteo, I understand you're here for the rebate.
Yes. Operating profit in the revised budget is four point zero three million. Sixty thousand of that is a supplier rebate that depends on volume.
What's that number based on?
On buying four point one million from Ferrand, the same as last year. The higher rate starts at four million. If we buy three per cent less, we lose all sixty. It's not a slope. It's a cliff.
Catherine asks the same question Graham asked at the budget review, and Matteo is ready. Number, basis, threshold, risk: four facts in four short sentences. Preparing for the obvious question is what makes an answer sound easy.
How confident are you?
Medium. The first quarter is on track. The risk is one large customer whose contract is reviewed in the summer. If purchases fall below one million in any quarter, I tell Graham that week.
And if you lose it, what happens to the four point zero three?
It becomes three point nine seven. That's why the rebate is on its own line. You can see it, and you can take it out.
Matteo shows the committee the number with and without the rebate. Putting an uncertain item on its own line lets the reader do their own "what if". It is the same rule as at the kickoff: a number with a label on it.
Clear. Two smaller questions. The returns are ninety thousand worse. Is that one bad December?
No. Two of the last three Decembers were like this one. All three are in the appendix.
I saw them. And the freight is simply the new contract?
Yes, rates up eight per cent. It's signed, so there's nothing to debate.
I said the same at the budget review. I don't like it, but I have no questions.
And the euro? I see it's coming to the risk committee.
Yes. About seventy thousand for a five per cent move. I'll bring a paper to the next meeting.
One more thing from the risk committee minutes. Moving an order between years to reach the rebate needs Graham's approval. I'd like to know if that is ever used.
You will. If I approve one, it goes in the next report to this committee, with the amount and the reason.
Catherine does not forbid the order timing. She asks to be informed if it happens. For a board, visibility is often enough: a sensitive decision that is reported is very different from one that is not.
Before we decide: Graham, is there anything we should know that isn't in the papers?
No. And if there were, you'd have heard it before this meeting, not in it.
The first rule of the series was "no surprises". Here Graham can answer the chair's last question with one word, because everything already went into the papers. That is the reward for telling people early: the final meeting is calm.
Then here is the decision. On the accounts, the committee recommends them to the board for approval. On the budget, we approve it, with two conditions.
First, the rebate stays on its own line, and Matteo reports to us after the second quarter whether it still looks safe. Second, the first quarterly review is completed in April, and the label check is tested, and Nadia reports both to this committee before the half-year.
"Approve with conditions" is a yes with a follow-up. Each condition says what, who and when, so the committee can check it later. A good condition is something the team already planned to do, written down where the board can see it.
We accept both. They're conditions we can meet, because they're what we'd planned anyway.
One request. Could the minutes say the second condition is reported by Nadia and Aisha? The review is hers.
Yes. Nadia and Aisha. Aisha, are you comfortable reporting to this committee?
A little nervous. But I'd rather explain my own work than have someone explain it for me.
That's the right answer. Alan, anything before we close?
Only that I'll look at the April review at the interim audit in July. I'd like it to be boring.
So would I. Thank you, all. This is the clearest year-end I've seen at this company.
In finance, "boring" is the highest praise for a control: nothing unusual, nothing to report. Alan's dry joke says what everyone wants from the next audit.
Aisha, at the kickoff you asked what "done" meant.
And now I'm the one who has to prove it.
That's how it works. Well done, everyone. No surprises.
Graham ends with the first rule he set at the kickoff. Six weeks ago, Aisha asked what words like "close" and "done" meant. Now she owns a control and answers questions from the board. The rule that started the close also ends it.