Has Last Month's Ledger Been Properly Locked?

After the prior month's financial statements are complete, a CFO should know whether the underlying ledger can still accept postings.

Executive summary

Posting-period status determines which periods remain open, which accept only authorized closing entries, and which no longer accept postings. CFO oversight should focus on three controls: advancing period status with the close, separating period-reopening authority from routine posting, and reviewing period status across legal entities before consolidation.

Posting periods establish the time boundary for financial data

SAP Business One assigns a document to a period according to its posting date. Each period has defined date ranges and a status that determines whether users can continue to post to it.[1]

Posting-period management is often treated as a setup task performed when a fiscal year is created or closed. Its continuing control purpose is to stabilize historical data. Once adjustments are complete and a period is set to Locked, SAP Business One no longer accepts transactions or documents for that period.[1][3]

Close-cycle time is also a common measure of finance operations. In Ledge's 2025 survey of 100 finance professionals, 18% of respondents reported closing in one to three business days, while 27% required more than seven business days.[4] Period controls do not determine close speed on their own, but they can reduce rework caused by out-of-period postings and changes to historical data.

For multi-entity groups, period control also affects the consistency of the consolidation basis. Each entity may close according to local operating and reporting requirements, while the group defines a common close calendar, locking standard, and exception process.

Manage Period Status in Line with the Close

Control requirement

SAP Business One provides four commonly used posting-period statuses:[1]

Status should become more restrictive as the close progresses. The current period normally remains Unlocked. After routine activity is complete, it can move to Closing Period so that only authorized adjustments remain. Once adjustments and review are finished, an authorized user changes the period to Locked.

SAP Business One can automatically change an ended period to Closing Period after a defined number of days. The final change to Locked is performed by an authorized user. The system records the locking date and the user who performed the action.[2][3]

When posting-date validation is combined with period status, a transaction dated within a Locked period is rejected at entry. This moves part of the out-of-period review from month end to transaction processing.[1]

Regulatory data illustrates the importance of controlling historical errors. Of 5,354 A-share listed companies reporting for 2023, 209 received modified audit opinions. The regulator also identified continuing issues involving revenue recognition, prior-period error correction, and the application of accounting policies.[16] Chinese Accounting Standard for Business Enterprises No. 28 requires material prior-period errors to be corrected retrospectively, unless determining the cumulative effect is impracticable.[18]

SAP Business One configuration and validation

1. 1.Create the period structure: Define fiscal-year and monthly periods and verify posting-date ranges.
2. 2.Define status criteria: Document when a period moves between Unlocked, Closing Period, and Locked and identify the responsible role.
3. 3.Configure the timing for Closing Period: Set the approved number of days after period end for the automatic status change.[2]
4. 4.Require an authorized final lock: After adjustments, reconciliations, and approvals are complete, change the period to Locked.[3]
5. 5.Test the control: Confirm that a Locked period rejects postings and that the locking record is available for review.

Validation should also cover inaccurate date ranges, future periods opened outside policy, and excessive access to post during Closing Period.

Separate Period-Reopening Authority from Routine Posting

Control requirement

A period lock is effective only when reopening authority is controlled. SAP Business One provides separate authorization settings for changing period status and posting during a Closing Period, allowing access to be assigned by job responsibility.[13]

Routine accounting users may process transactions within their business authorizations, but they should not automatically be able to change a Locked period back to Unlocked. Reopening should have a defined approver, a documented business reason, and a record of the adjustment. The period status should be reconfirmed after the adjustment is complete.

Public regulatory cases illustrate the importance of segregation of duties and independent review:

CIRCOR overseas business-unit case

The U.S. Securities and Exchange Commission reported that a former finance director at a CIRCOR business unit in the United Kingdom manipulated financial results through false accounting records, reconciliations, and bank-confirmation documents. The resulting overstatement amounted to millions of dollars. The SEC identified deficiencies in controls over financial-statement preparation, reconciliations, and access to bank accounts.[6]

Macy's expense-accounting case

Macy's disclosed that an employee responsible for small-package delivery expense accounting used erroneous accrual entries and falsified supporting documentation to conceal approximately US$151 million of delivery expenses from the fourth quarter of 2021 through the third quarter of 2024.[8]

Neither case concerns SAP Business One period configuration, and neither can be attributed solely to period-reopening authority. They demonstrate a broader control risk: errors or misconduct can continue across reporting periods when one role can record and adjust transactions without timely independent review.

Article 25 of China's current Accounting Law requires duties and authorities for bookkeeping, approval, transaction execution, and asset custody to be clearly defined, separated, and mutually restrictive.[17] Article 8 of the Measures for the Administration of Accounting Archives also requires effective measures to prevent electronic accounting records from being altered.[19]

SAP Business One configuration and validation

1. 1.Restrict authority to change period status: Grant it only to the finance controller or another designated control role.
2. 2.Configure Closing Period posting separately: Permit only designated users to enter period-end adjustments.
3. 3.Assign access by role or user group: Maintain consistent authorization when personnel change.
4. 4.Document reopening: Record the requester, approver, reason, adjusting entry, and time of relocking.
5. 5.Test access: Confirm that routine accounting users cannot change period status or post during Closing Period.

Review Each Entity's Period Status Before Consolidation

Group Period Management and Cross-Database Review

In a multi-company-database environment, each company database manages its own posting periods. Locking a period in one database does not automatically change the status in another. This separation supports local operating and statutory requirements, while the group still needs a pre-consolidation review of each company's completion status.

The standard SAP Business One posting-period window operates within a company database. If a group needs one dashboard showing period status across multiple databases, cross-database collection, access, and presentation normally need to be designed as a separate integration or BI scope.

A group close standard should define at least:

1. 1.when each legal entity completes local adjustments and review;
2. 2.the criteria for moving to Closing Period and Locked;
3. 3.how material adjustments and accounting-standard conversions are reported;
4. 4.the owner and deadline for each entity that has not locked on schedule; and
5. 5.the pre-consolidation review of period status and adjustments.

The product controls periods within a company database. Group process and implementation scope establish consistency across databases. Both should be addressed explicitly during project design.

How the controls support a faster close

Historical data that continues to change, manual investigation of out-of-period transactions, and inconsistent completion dates across entities all add reconciliation and rework. ERP performance is only one factor affecting the close cycle.

Period status, authorization, and multi-entity review provide a stable close boundary, but they do not guarantee a fixed reduction in close time. A company can use published business-day benchmarks as a reference after defining consistent start and end points for its own close cycle, then set targets that reflect its organizational scale, transaction complexity, and approval requirements.[4]

During project assessment, the team should distinguish work that system controls can reduce from work that still requires approval or is constrained by tax, audit, and local regulatory requirements. That distinction produces a more credible project target and acceptance basis.

Close Measures for the CFO's Monthly Review

Posting-Period Control Checks to Start Now

These checks normally do not require a large systems project and can provide an initial view of current control gaps.

1. 1.Confirm period status: What proportion of the prior month's eligible periods has been set to Locked?
2. 2.Confirm reopening authority: Which users can change period status, and do any of them also perform routine posting?
3. 3.Test the restriction: Enter a test document with a posting date in a Locked period and confirm that the system rejects it.
4. 4.Review entity completion: Before consolidation, can finance obtain each entity's period status, material adjustments, and exception list?

Conclusion

Posting-period management keeps historical data stable after close and ensures that necessary adjustments are authorized and recorded. For a CFO, period status, reopening authority, and multi-entity review are components of one financial-reporting control framework.

System configuration provides the foundation. Approval, segregation of duties, periodic access review, and exception management are required to keep the controls effective.

References

• [1] SAP Help Portal: Posting Period Window
• [2] SAP Help Portal: Posting Periods Window
• [3] SAP Help Portal: Locking Posting Periods
• [4] Ledge: The State of Month-End Close in 2025
• [6] U.S. Securities and Exchange Commission: Press Release 2024-116
• [8] Macy's: Form 8-K filed December 11, 2024
• [13] SAP Help Portal: General Authorizations
• [16] China Securities Regulatory Commission: 2023 Annual Financial Reporting Accounting Supervision Report
• [17] Ministry of Finance of China: Accounting Law of the People's Republic of China
• [18] Ministry of Finance of China: Accounting Standard for Business Enterprises No. 28
• [19] Ministry of Finance and National Archives Administration: Measures for the Administration of Accounting Archives

Source note: this article is based on SAP documentation and public regulatory materials. The project team confirms the period-control design against the selected version, localization configuration and company approval policy.