Open, locked, and closed periods: policy, product, and late evidence

Why period states exist

Month-end work is collaborative. Owners may still be collecting documents while software prepares data and the accounting firm reviews proposals. Without a period control, a reviewer can inspect one set of information while the underlying month changes underneath them.

Period states create a shared answer to three questions:

1. Is routine work still allowed in this period?
2. Is the review set stable enough for professional inspection?
3. If new evidence arrives, what controlled path changes the result?

The state is useful only when permissions and consequences are explicit. A badge saying “closed” does not by itself prevent changes, explain corrections, or satisfy a documentation requirement.

A practical state model

Some systems use additional states such as “review”, “soft close”, or “reopened”. The label matters less than the documented behaviour. For each state, define:

• who can enter and leave it;
• which actions remain allowed;
• whether imports or automated preparation continue;
• how late documents are presented;
• whether downstream export or filing has occurred;
• which event and reason are recorded.

“Open”, “locked”, and “closed” are product and process terms here. They do not determine the legal or tax treatment of a transaction, and they do not prove that a period is professionally complete.

The difference between locking and closing

A lock is usually temporary and review-oriented. It prevents uncontrolled changes while the reviewer works. The month can still contain known questions or items requiring a decision; the point is to keep the review population stable.

A close is a stronger declaration that the agreed month process has reached its handoff or approval point. Closing should require visible prerequisites and should record who performed it and when. Depending on the engagement, it may precede or follow export, posting, filing, or another downstream action. Those actions must not be assumed from the word “closed”.

One useful boundary is:

• lock when the evidence set is ready for concentrated review;
• close only after the required review decisions and accepted exceptions are documented.

The firm should adapt that boundary to its actual process.

Worked example: a late supplier invoice

Assume May was locked for review on 5 June. On 7 June the owner receives a supplier invoice dated 29 May for work performed in May.

A poor workflow silently imports the invoice into May, changes the review totals, and leaves the reviewer unaware. Another poor workflow rejects the file without explaining what the owner should do.

A controlled workflow is:

1. accept the source as late evidence and preserve its receipt time;
2. link it to the May period without silently changing approved work;
3. notify the responsible reviewer that the review set has changed or that an exception awaits a decision;
4. let the accountant determine the correct recognition and correction route;
5. record the decision, affected entry, reason, and resulting period state;
6. repeat affected review and export checks before closing again.

The same pattern applies to a late credit note, corrected sales invoice, missing bank row, or chargeback outcome.

Entry criteria for each state

Before locking

The review population should be identifiable. At minimum, the expected evidence sources are present or named as exceptions, bank data covers the period, material unmatched items are visible, and owner questions have a status.

Before closing

The responsible reviewer should know which exceptions remain, which were accepted, and which require follow-up in a later period. Required professional approvals should be recorded. If an export or handoff is part of the close definition, its version and result should be traceable.

Before reopening

The reason, requester, affected item, and downstream consequence should be known. Reopening should not become a general shortcut for editing history. Once the change is made, affected reconciliation, review, translation of facts, and export checks need to run again.

Permissions should fail closed

An accountant working across many clients needs predictable control. The interface should not rely on a remembered convention such as “please do not edit May”. It should prevent or route disallowed actions and explain why.

Useful controls include:

• role-based authority to lock, close, or reopen;
• a visible period state and last state change;
• a reason for reopening or post-close correction;
• a list of items changed after lock;
• invalidation of affected approvals;
• a clear owner path for late evidence that does not bypass review.

Automation may continue to receive files while a period is locked, but it must not silently convert them into approved changes. The distinction between “received”, “prepared”, and “approved” should remain visible.

Owner, software, and accountant responsibilities

DeinHans can make period state, blockers, evidence, and review decisions visible in one workflow. It must not imply that closing a product period files a return, finalises statutory accounts, or prevents every later professional correction.

Current product behaviour and the firm's operating policy are separate. Before using this article as an instruction, verify which state labels and permissions are visible in the deployed owner and accountant surfaces. Where a lock or reopen action is not available or not identical for both roles, the safe workflow is to preserve the late evidence, flag the affected review and let the responsible accountant control the next step. The article describes that control outcome; it is not a promise of a particular button or permission.

Questions for an accounting firm to settle before rollout

• What exactly can owners do in each state?
• Who can lock, close, reopen, or override?
• Does the lock stop imports, preparation, edits, approvals, or only some of them?
• What evidence is mandatory before lock and before close?
• How are accepted exceptions labelled and revisited?
• What happens when a late item affects a completed export?
• Which approvals become invalid after a material change?
• How will staff distinguish product close, accounting close, and filing status?

Document these answers in the firm’s operating procedure and in user-facing guidance. Period controls work when everyone knows what the state means and the system enforces the same meaning.