Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table

Lesson 1 of 6

The close calendar

8 min

A month-end close is not one job. It is a chain of forty to a hundred tasks owned by different teams, and most of them only produce the right answer if the task before them has finished. The finance team cannot value foreign currency open items until the last supplier invoices are posted. Controlling cannot settle production orders until inventory postings for the period are complete. The close calendar is the plan that puts those tasks in order, names an owner for each, and says what "done" looks like.

In SAP S/4HANA, financial accounting and controlling share the Universal Journal, so many tasks that were separate reconciliations in SAP ECC are gone. The FI-CO reconciliation ledger, for example, is no longer needed because cost elements are G/L accounts. But the dependencies did not disappear. They moved: logistics, controlling and finance still have to run in the right order, and the posting period has to be open for each of them at the right time.

  1. Day -1 to 0: logistics cut-offLast goods receipts, goods issues and billing for the period; open the next materials period
  2. Day 1: subledgersPost remaining supplier and customer invoices, payments, asset acquisitions; run depreciation
  3. Day 1-2: accruals and GR/IRPost accruals and deferrals; analyze GR/IR; clear what can be cleared
  4. Day 2: controllingOverhead allocations, work in process, variances, order settlement
  5. Day 3: valuation and reclassificationForeign currency valuation, regrouping of receivables and payables
  6. Day 3-4: close and reportLock the period, run trial balance and statements, review and sign
A typical month-end sequence. Each band waits for the one before it.
The Sign-Off Table · thesignofftable.com/academy/sap-fin-301

Posting periods: the gate

Every journal entry needs an open posting period. Periods are controlled by the posting period variant, which is assigned to company codes, so one change can open or close a period for many companies at once. Within the variant you can open different ranges by account type: + for all accounts, then separate lines for assets (A), customers (D), suppliers (K), materials (M) and G/L accounts (S). That lets you close supplier postings for May while G/L accountants still post May accruals. Users maintain it with the Manage Posting Periods app or transaction OB52.

Logistics has its own gate. The materials period (transaction MMPV) moves inventory management to the next period, and controlling has a period lock per business transaction. The close calendar should state exactly when each gate moves and who moves it. A surprising share of close-day incidents come down to a period opened too late or closed too early.

FI posting periodsPosting period variant by company code; separate ranges per account type; special periods 13-16 for year-end
Materials periodCurrent and previous materials period; moved forward at month start
Controlling period lockLocks business transactions such as allocations or settlement per period and version
Three gates control what can post in a period.
The Sign-Off Table · thesignofftable.com/academy/sap-fin-301

Closing task lists

Larger organizations do not run the close from a spreadsheet. SAP offers the SAP S/4HANA Financial Closing cockpit inside the system, and SAP Advanced Financial Closing as a cloud service that orchestrates tasks across one or many systems. Both follow the same idea: you build a template of tasks with dependencies, owners and program variants; each period the template generates a task list for a key date; tasks run in order and each result (log, spool, status) is stored against the task. A task cannot start until its predecessors are complete.

Even if Contoso keeps its close in a shared spreadsheet for go-live, the structure is the same and you should design the spreadsheet as if it were a task list: an ID per task, predecessor IDs, owner, system step (app or program and variant), expected output, and the evidence to keep.

TaskPredecessorOwnerOutput
Post last supplier invoicesGoods receipt cut-offAP teamInvoice backlog = 0
Run depreciationAsset acquisitions postedAsset accountantDepreciation run log, no errors
Foreign currency valuationAll AP/AR postings doneG/L accountantValuation log per ledger
Settle production ordersVariances calculatedCost accountantSettlement log; orders at zero
Close FI periodAll aboveClose leadPeriod table updated

Extract from Contoso's close task list for company code 1710.

What would you do?

It is day 2 of the May close at Contoso. The cost accountant wants to settle production orders, but the Chicago plant is still posting late goods receipts for May. What should the close lead do?

Key points
  • The close calendar sequences tasks by dependency: logistics, subledgers, accruals, controlling, valuation, reporting.
  • Posting periods, the materials period and controlling period locks are three separate gates.
  • Closing task lists (Financial Closing cockpit or Advanced Financial Closing) turn a template into a dated, dependency-driven task list.
  • Every task needs one owner, a system step and an expected output you can keep as evidence.

Check your understanding · not graded

Lesson check

  1. 1. Which object lets you open a period for many company codes at once?

  2. 2. Why should foreign currency valuation run after the last supplier invoices are posted?

  3. 3. In a closing task list, what does a predecessor relationship do?