Period-End Close in S/4HANA: Prevent the Last-Day Fire on Day -3
The month-end fire on the last day is prevented three days earlier, with a short FI checklist.
The tip
The month-end fire on the last day is prevented on day -3. FI checklist:
- Posting periods open only where they need to be
- GR/IR and open items analyzed and cleaned up
- Accruals and deferrals posted
- If document splitting is active: the zero-balance clearing account and the balance sheet by segment or profit center reviewed
If you start on day 0, you are already late.
Why it matters
Most closing problems come from preclosing work that was not done: open periods that let postings land late, GR/IR balances nobody analyzed, and missing accruals. Doing these three days before the end of the period turns the last day into a review instead of an investigation.
Steps and configuration
- Open and close FI posting periods with transaction OB52 or the Manage Posting Periods app. Since SAP S/4HANA 1809 the app maintains the same table as OB52.
- Remember the CO period lock (OKP1) for CO postings that are relevant to FI.
- Preclosing in FI: process purchase order accruals, enter manual accruals and deferrals, and process recurring entries.
- Analyze the GR/IR clearing account and reclassify receivables and payables as part of closing for external reporting.
Edition differences
- Private Cloud and On-Premise: OB52 or the Manage Posting Periods app.
- Public Cloud: the Manage Posting Periods app, which can also schedule recurring opening and closing of periods (KBA 3786415).
Official sources
- SAP Learning: Managing Posting Periods
- SAP Learning: Explaining the Periodic Closing Process
- SAP KBA 3786415: Schedule Recurrence in the Manage Posting Periods app (Public Cloud)
- SAP KBA 2607276: Master data for zero-balance clearing account
Validated against: SAP S/4HANA 2025 FPS02 (Private/On-Prem) and Public Cloud 2608, reviewed 21 Nov 2026.
Originally shared on X (5 Nov 2026, in Spanish): view the post. More tips: SAP Tips.