Configuring and Executing the Standard Period-End Posting Sequence

Explanation

Once the organizational and master data foundation is understood, the next step is learning how period-end closing is actually configured and executed as a sequence of interdependent postings. In most SAP implementations, the standard close follows a broadly consistent order because later steps depend on the completeness of earlier ones. A typical sequence begins with subledger closing activities: accounts payable and receivable teams complete open item processing, then GR/IR (goods receipt/invoice receipt) clearing accounts are analyzed to identify items where goods were received but not yet invoiced, or invoiced but not yet received, both of which require automatic or manual clearing before the balance sheet is considered accurate. Accrual and deferral postings are configured using recurring entry documents or accrual/deferral posting programs that reverse automatically in the following period. This configuration typically relies on a reference document or a recurring entry master record with a defined run schedule (monthly, for example), and the reversal is either automatic on a defined date or performed manually by the closing team. Getting the reversal date configuration wrong is a common source of duplicated or missing expense postings, so consultants must verify the reversal logic against the fiscal year variant's period structure. Foreign currency valuation is another core configuration area: open items and GL balances held in foreign currency are revalued using exchange rate types and valuation methods assigned in the configuration, typically executed through a periodic valuation run that posts unrealized gains and losses to designated adjustment accounts, which then reverse in the following period. The valuation method configuration determines whether valuation is performed at the individual document level or on a summarized balance basis, which affects both the posting volume and the audit trail during close. Asset accounting integrates into the close through the periodic depreciation run, which calculates and posts planned depreciation for each asset based on the depreciation key and useful life maintained in the asset master, then posts the results to the GL accounts mapped in the account determination configuration. This run must be executed and its results validated before the balance sheet is finalized, because unposted depreciation understates expense and overstates asset net book value. On the controlling side, cost center and internal order allocations are executed through assessment and distribution cycles that redistribute overhead costs from collection cost centers to receiving cost objects, following a defined sender/receiver rule and allocation base configured in the cycle. These allocations must run in a specific order relative to settlement of internal orders or projects to fixed assets or cost centers, since settlement often depends on the fully allocated cost base. Only after subledgers, valuations, depreciation, and CO allocations are complete does the GL closing step occur: technical closing operations reconcile CO and FI postings (in classic ECC, reconciliation ledger differences may arise; in S/4HANA, the Universal Journal design significantly reduces such reconciliation breaks because FI and CO postings share the same underlying document table), followed by period lock and, at year-end, balance carryforward. A consultant configuring this process must document each step's prerequisite, owner, and system transaction, then validate the sequence in a test client using representative data before go-live, since errors discovered only in production can force a very costly re-open of a locked period.

Code example

* Simplified illustration of a recurring entry / accrual posting logic* (documentation-style pseudocode, not an actual ABAP program) * Step 1: Recurring entry master data defines:*   - Document type: SA (GL posting)*   - Posting key: 40 (debit expense) / 50 (credit accrual liability)*   - Run frequency: Monthly, first working day of period*   - Amount: Fixed accrual amount, e.g., rent accrual * Step 2: Batch run executes recurring entries for the open period*   -> Creates FI documents from the recurring entry master records*   -> Documents post to expense account (debit) and accrual account (credit) * Step 3: Reversal is scheduled for the accrual document*   -> Reversal reason and reversal date = first day of next period*   -> Ensures the accrual does not persist once actual invoice is received * Step 4: GR/IR clearing review*   -> Identify open items in GR/IR account older than expected threshold*   -> Investigate: goods received, invoice pending -> leave open with note*   -> Invoice received, goods receipt missing -> follow up with procurement * Step 5: Foreign currency valuation run (periodic)*   -> Select valuation method (e.g., lowest value principle or period-end rate)*   -> Post unrealized FX gain/loss to designated adjustment account*   -> Reversal posted automatically in following period

Real project scenario

During a month-end close review, the controlling team found that overhead allocation cycles were being executed before all GR/IR clearing was completed, causing the allocated cost base to exclude some vendor invoices that were posted late. The consultant redesigned the close calendar so GR/IR review and clearing was a hard prerequisite task before the assessment cycle run, added a validation report to flag unallocated GR/IR balances above a threshold, and communicated the revised sequence to the finance and controlling teams to prevent recurring allocation base errors.

Common mistakes

• Running cost allocation cycles before subledger clearing and accrual postings are complete, causing distorted allocation bases • Misconfiguring recurring entry reversal dates, leading to duplicated or missing accrual reversals in the following period • Ignoring GR/IR aging analysis until year-end, allowing large unreconciled balances to accumulate • Selecting the wrong valuation method for foreign currency revaluation, causing inconsistent treatment between individual document and summarized balance valuation • Not validating depreciation run results before finalizing the balance sheet, resulting in understated expense in the closed period

Best practices

• Document a strict sequence of close tasks with clear prerequisites, such as completing subledger clearing before running cost allocations • Test recurring entry and reversal configuration in a non-production client with realistic period boundaries before relying on it in production • Set up aging reports for GR/IR and other clearing accounts to catch problems well before period-end pressure builds • Validate depreciation run output against expected asset registers before allowing the balance sheet to be finalized • Maintain consistent foreign currency valuation method configuration across similar account types to avoid reporting inconsistencies

Interview angle

Candidates are frequently asked to walk through the correct order of period-end closing activities and explain why sequence matters, for example why GR/IR clearing and accrual postings must precede cost allocations. A strong response demonstrates understanding of dependencies between subledgers, controlling allocations, and GL closing, and can explain the role of configuration objects like recurring entry masters, valuation methods, and depreciation keys without confusing them with unrelated concepts.