Month-end deserves better than final_final_this_one

Agree on the deliverable before requesting files. A monthly management report, an accounting close and an audit package have different scopes. Write down the audience, the decisions it should support, the period and the person allowed to approve it. Otherwise the same word, close, may quietly describe three different jobs.

Make the currency, presentation units, cut-off date and expected comparison visible. If the report needs monthly movements, confirm that the export actually contains them. Renaming a column does not turn a cumulative balance into a monthly movement. Set acceptance criteria before reviewing the output, rather than deciding afterwards that it looks convincing enough.

For each input, record its owner, period, origin, receipt date and review status. Use labels that describe what happened: missing, received, checked and queried. Received only says a file arrived. It may still cover a different period, omit rows or use an unfamiliar classification.

When information is missing, make a precise request: which field you need, which calculation depends on it and whether a narrower scope could move forward. An issue with an owner and a next action is more useful than a red cell whose meaning only the workbook’s creator understands.

ICAEW recommends separating inputs, processes and outputs, with independent review appropriate to workbook risk. That provides a starting point for deciding who prepares the work and who checks it.

Choose a material figure and trace it to its source. Check the period, the calculation and the classification applied. Do the same for a variance: the comparison needs a compatible basis. A total that reconciles is a useful check. It does not, on its own, establish that every transaction is recorded or that a proposed explanation is true.

Keep the report, its input sources, assumptions and review together. Record who decided, when and which version they reviewed. If a correction arrives, create a new revision and retain the earlier deliverable so the change can be explained. A helpful filename provides directions; it does not replace the decision record.

You do not need to launch a large system to start. An index of authorized links, an issue list and a shared rule for approving versions make the work easier to follow. Tools may change. The commitment to identifying exactly what was reviewed should stay.

Reuse the structure, classifications that remain valid and the review checklist. Confirm new-period sources and flag changes in accounts or assumptions. Carrying old figures into gaps undermines the continuity you were trying to build. A useful second cycle reuses process decisions and asks for new evidence.

At the end, record one friction worth fixing: an input that always arrives late, an ambiguous field or a review with no assigned owner. Turn it into a small action with a responsible person. Improving month-end can begin with that conversation, without waiting to buy another tool.