Review guide

Finance Pack Review Before Close: A Working Checklist

A finance pack review is a consistency exercise, not a second close. The value comes from finding the questions the controller has not been asked yet.

Gemma4.net review library Updated 2026-11-13 中文版

Why finance packs resist review

A finance pack is assembled under time pressure from systems that were not designed to explain themselves. The summary is produced late, the schedules are updated after the summary, and the commentary is written by people who already know the answer. Reviewing it is therefore less about checking arithmetic and more about checking that the story, the numbers, and the version all agree.

Set the boundary first. A reviewer can confirm that totals add, that periods are labelled, that variances have explanations, and that the pack is internally consistent. A reviewer cannot re-perform the close, confirm the completeness of accruals, or sign off on a provision without the underlying evidence. Say which role you are playing before you start, because the pack owner will otherwise assume you have done the second.

Size the finance pack before you scope the review

Enter file count, pages, and formats to see whether this is a single-decision packet or a multi-document one, and what to prepare before asking anyone to review it.

Tie the summary to the schedules

Start with the largest three numbers in the summary and trace each one to a schedule and then to a source system export. This is a sample, not a full recomputation, and it is remarkably effective at finding stale versions. If a number cannot be traced in a few minutes, that is a finding about the pack’s construction, not a reason to keep digging on your own.

Check the additions across the pack. Subtotals that were correct in the prior version often break when a line is inserted. Compare the current pack with the previous period’s pack for the same schedules: a line that disappeared without explanation is as important as a line that changed.

Confirm currency, units, and rounding. A schedule in thousands next to a summary in millions produces a plausible-looking error that survives review because both numbers look reasonable. Note the exchange rate date for any translated amounts.

Read flux commentary for cause and durability

Variance commentary is where a reviewer adds the most value per minute. For each material variance, ask three questions: what caused it, is it timing or permanent, and what should we expect next period? Commentary that answers only the first question is incomplete, and commentary that answers none of them is a placeholder.

Look for explanations that restate the number instead of explaining it. “Revenue was up due to higher sales” is a restatement. “Revenue was up because two annual contracts renewed a quarter earlier than planned, which will reverse in Q4” tells the reader what happens next and is the kind of explanation a board or lender can use.

Cut-off, accruals, and the questions worth asking

Cut-off is the classic source of small errors that become large narratives. Ask which invoices around the period end were included, how goods or services received but not invoiced were accrued, and whether any credit notes were issued after the close. You are not testing the answer; you are checking that someone did.

For accruals, ask for the basis and the owner. A single adjusting entry with no supporting calculation is a risk item even when the amount is small, because the same process will produce a larger entry next quarter. For provisions and estimates, ask what changed since the prior period and whether the change is documented.

Payroll, revenue recognition, and inventory are the three areas where a review question is most likely to surface something. Ask what changed in each, and whether the change is reflected in both the numbers and the commentary.

Covenants, lender schedules, and external formats

If the pack feeds a lender, a board, or a regulator, the external format has its own definitions. Check that the covenant calculation uses the defined terms from the facility agreement rather than the management accounts convention. A metric that is right internally and wrong in the covenant schedule is still wrong where it counts.

Check the reporting calendar. A pack delivered after the covenant deadline is a compliance event even if the numbers are correct. Confirm who submits, to whom, in what format, and whether the submission needs a signature or a certificate.

Version labels and the audit trail

Every pack needs a version, a date, an owner, and a status: draft, for review, or final. When a number changes after circulation, record what changed and why. Reviewers who cannot tell which version they are reading will either duplicate work or approve the wrong one.

Keep the review notes with the pack. A short list of questions asked, answers received, and items left open is more useful to the next reviewer than a clean-looking pack with no history. If the answer to a question arrived verbally, write it down and attribute it.

Handoff into close or into the decision

A finance pack usually serves two audiences: the people closing the books and the people making a decision. Separate the two outputs. The close team needs the list of unresolved items with owners and amounts. The decision maker needs the three numbers that matter, the variance explanation, and the risk that could change the answer.

Write the handoff as a one-page memo rather than a chat message. State what was reviewed, what was not, what remains open, and who owns each open item. That memo is the artifact that survives the meeting, and it is the fastest way to answer “what did we know and when” three months later.

Non-financial measures need the same discipline

Finance packs increasingly carry operational measures: pipeline, retention, utilisation, backlog, headcount, or unit economics. These figures often arrive from systems outside the finance function and are rarely reconciled with the same rigour as the ledger. Ask for the definition, the source, and the person accountable for the number.

Check that the definition has not changed since the prior period. A retention figure that moved from logo retention to revenue retention produces a trend that looks like improvement and is actually a definitional break. Where the definition changed, the pack should restate the prior period on the new basis or show both.

Finally, check that the operational measures and the financial statements tell the same story. Rising backlog with flat revenue may be a timing issue or a delivery problem; the pack should say which. When the two narratives conflict, the conflict is the finding.

Keep the review proportionate

The depth of a finance pack review should match the decision. A monthly management pack needs a consistency pass and a short question list. A refinancing, an acquisition, or a covenant waiver needs a deeper review and specialist involvement. Matching effort to consequence is part of the skill; a review that takes three days for a routine month is as much a failure as one that takes an hour for a refinancing.

This guide is a working method, not accounting advice. Recognition, measurement, and disclosure questions belong with the controller and the auditors, and any covenant conclusion belongs with the finance leadership and counsel who own the facility.

Next step

Scope a private review by email

Send the matter, file volume, formats, deadline, and decision question. A person confirms fit, handling, and timing before files move.