Last month’s work should not become an oral tradition. If repeating a report requires asking someone what every column meant, the process needs a better memory.
Keep the original before fixing it
Retain the received file with its origin, extraction date, company and period. Clean a separate version and record the transformations. This lets you distinguish a change in the source from a correction made during preparation. Renaming a worksheet needs little ceremony; deleting rows or reversing signs deserves an explanation.
Agree on expected fields and their meaning before importing. A code identifies an account; an amount measures a quantity; a date might mean due date or posting date. Mixing these roles allows apparently clean columns to tell different stories. Documenting their meaning is often more useful than introducing another colour convention.
Identifiers have no need to add up
Microsoft explains that Excel can remove leading zeros and automatically convert large numbers. Keeping codes and identifiers as text avoids those conversions; display formatting alone cannot restore characters already lost.
Set column types before loading and check a sample against the original. Preserve complete codes when joining files or mapping accounts. If an identifier changed at the source, record the relationship and its validity period rather than guessing that two similar names mean the same account.
Distinguish zero from an unanswered question
A confirmed zero is an observation. A blank cell might mean missing data, not applicable or an import problem. These meanings are different. Decide how to represent each and avoid turning every blank into zero just to finish the table. When a required component is absent, the total should disclose the limitation.
Apply the same discipline to signs, currencies and units. A figure in thousands and one in units require an explicit conversion before comparison. Document the rule, retain the received value and check the transformation. A tidy table can still contain a scale error repeated throughout the report.
Reuse classifications with a date and a reason
An account classification deserves an owner, a version, a rationale and a scope. It can be proposed as next period’s starting point, but new accounts and chart changes need review. Continuity means reusing what remains valid, not deciding that the past must always be right.
Keep classification rules separate from the file using them. That makes differences between two report versions easier to explain. Retain the link between output, source and applied rule too. A later reviewer should be able to find that path without reconstructing it from screenshots.
Keep versions and record the review decision
OneDrive provides history for viewing or restoring file versions. That helps recover changes, but identifying which version the team reviewed still requires recording the decision and its scope.
For the next month, retain structure and valid rules, request new sources and compare changes. A short handover note can capture new fields, revised criteria and carried-forward questions. The previous report should remain recognizable as delivered, even when the current process has improved.
A continuity check
- Choose one code and verify that it matches the original exactly.
- Find a blank cell and document its meaning without assuming zero.
- Locate a reused classification and confirm who reviewed it and for which period.
Reusable data retains its meaning, sources and changes. That is the memory the next report needs.
General operational guidance. Adapt the process to your company’s context and applicable reporting framework.