Close operations

How complete is the month-end close evidence?

A proposed protocol for measuring whether each close task has an owner, a date, and an evidence file.

This research is general operational information, not legal, tax, accounting, employment, benefits, privacy, cybersecurity, insurance, or financial advice.

How complete is the month-end close evidence? evidence review illustration

Question and scope

This is a proposed research protocol, not a report of completed findings. It asks how complete the month-end close evidence is. The result would describe the close file, not the team. Ask whether a new reviewer could act on the record without a conversation.

The protocol does not measure whether the close was fast. It measures whether each task can be verified from the record. Update the template when the same question appears twice. A control that depends on memory is not yet a control.

Population and unit of analysis

Define the population as close tasks during a stated period. The unit is one task, with the owner, the due date, the completion date, and the evidence recorded. Keep the original note beside the corrected version. A short note with four fields is easier to use than a long narrative.

Link the task to the evidence file so the same task is not counted twice. A task without a link is a finding in itself. Write the deadline as a date and a local time. A control that depends on memory is not yet a control.

Definitions and measures

Define completeness as the presence of the owner, the date, and the evidence. Define timeliness as completion on or before the due date. Update the template when the same question appears twice. Record the exception and the person who approved it.

Report completeness and timeliness separately. A task that was completed on time without evidence is complete in one sense and not the other. A short note with four fields is easier to use than a long narrative. Separate what was observed from what was assumed.

Evidence standard

Use the close checklist and the linked evidence. A checklist marked complete without a file is weak. The reviewer should be able to open the evidence from the record. Test the rule on one real transaction before applying it to the run.

Record the date and the reviewer. A later review may need to see what was checked and when. Test the rule on one real transaction before applying it to the run. Ask whether a new reviewer could act on the record without a conversation.

Sampling and collection

Use a census of the close tasks if the period is small. If sampling is necessary, stratify by process area. A sample that excludes the exceptions will overstate completeness. Update the template when the same question appears twice.

Pilot the classification on a few tasks and compare the reviewers. Clarify what counts as evidence for a judgment-based task. Record the exception and the person who approved it. Review the first few notes together before the process expands.

Analysis and reporting

Report completeness and timeliness by process area. Show the tasks without an evidence file. Present the results as a description of the close file, not a judgment about the preparer. A short note with four fields is easier to use than a long narrative.

Limits and sources of error

The evidence may live in a different system. State the systems included. The checklist may be updated after the close, which can make the record look better than it was. Review the first few notes together before the process expands.

Review cadence

Repeat the review after a checklist change or at the same interval each quarter. Compare the same process areas. Assign the follow-up to the close lead and set a date. Review the first few notes together before the process expands.

Useful internal handoffs

Sources