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

Lesson 1 of 5

Close across processes

10 min

Listen to this lesson

0:00 / 8:42

Finance owns the financial statements, so the month-end close is often treated as a finance event. It is not. A large share of the numbers in a manufacturer's statements come from logistics and controlling: inventory, goods received but not invoiced, cost of goods sold, work in process, production variances. If the warehouse posts receipts late, if production confirmations are missing, or if order settlement runs before overhead, finance closes on numbers that are already wrong. Orchestrating the close means treating it as one cross-process chain with owners in every team.

The three families of tasks

FamilyTypical tasksOwner at Contoso
LogisticsGoods movement cut-off; physical inventory differences posted; billing due list complete; materials period moved; GR/IR items reviewed with purchasingPlant managers Detroit and Chicago; Maria for billing
ControllingCost center allocations; overhead; WIP and variances; order settlement; optional actual costing; controlling period lockCost accountant, under Dan
FinanceSupplier invoices posted; accruals; depreciation; foreign currency valuation; GR/IR clearing and regrouping; intercompany reconciliation; posting periods; statements and reviewG/L team and Ana in AP, under Dan

Period-end task families for company codes 1710 and 1810.

The list is longer in practice. A real close calendar at a company like Contoso has between forty and a hundred tasks per company code, many of them small: a report to run, a balance to review, a job to check. The point of mapping them is not the count. It is to see which tasks need the output of which other tasks, because that is where closes go wrong.

Finance reportingStatements, reviews, disclosures: need everything below
Finance valuation and reclassificationFX valuation, regrouping, accruals: need complete subledgers
ControllingAllocations, overhead, WIP, variances, settlement: need complete costs and quantities
LogisticsGoods movements, confirmations, billing, inventory: the base everything else reads
The close as layers: each layer depends on the one beneath it being complete.
The Sign-Off Table · thesignofftable.com/academy/sap-xpr-301

How the families depend on each other

Some dependencies are obvious: settlement needs overhead, statements need settlement. Others are easy to miss. Foreign currency valuation needs all open supplier and customer items, so it waits for the last invoices. GR/IR analysis needs the last goods receipts and the last invoices. Intercompany reconciliation between 1710 and 1810 needs billing in 1710 and invoice receipt in 1810, which are two teams in two company codes. If Contoso runs actual costing later, it needs every movement and settlement of the period to be complete, and its revaluation postings must be in before inventory and COGS are reported.

The hidden dependencies cross teams: valuation, GR/IR and intercompany all wait for postings owned by someone else.
The Sign-Off Table · thesignofftable.com/academy/sap-xpr-301
  1. Logistics cut-offLast receipts, issues, confirmations and billing; materials period moved
  2. Subledgers completeSupplier invoices, customer billing, assets: all postings in
  3. ControllingAllocations, overhead, WIP, variances, settlement
  4. ValuationFX valuation, GR/IR clearing and regrouping, accruals
  5. Reconcile and reportIntercompany, subledger to G/L, margin to P&L, statements
The cross-process chain in its simplest form.
The Sign-Off Table · thesignofftable.com/academy/sap-xpr-301

Gates that hold the period

Three gates decide what can still post into a period, and each belongs to a different team. The materials period (moved with MMPV) controls inventory postings; it is usually moved at the start of the new month so goods movements go to the new period. The FI posting periods, controlled by the posting period variant for the company code, can be opened and closed separately for account types such as assets, customers, suppliers, materials and G/L accounts, so suppliers can be closed for May while G/L accountants still post accruals. The controlling period lock blocks selected controlling transactions such as allocations or settlement for a period and version. A close calendar that does not say who moves each gate, and when, will sooner or later see a gate moved too early (settlement fails) or too late (June documents land in May).

GateOwner at ContosoWhen it moves
Materials periodLogistics, with the plant controllersFirst working day of the new month, after the cut-off
FI posting periods by account typeG/L team under DanSuppliers and customers closed on day 3; G/L on day 4 after review
Controlling period lockCost accountantAfter settlement and allocations to margin analysis are complete

The three gates in Contoso's close and who moves them.

Each gate belongs to a different team and moves at a planned point, so nothing lands in the wrong period and nothing is locked too early.
The Sign-Off Table · thesignofftable.com/academy/sap-xpr-301

What would you do?

On day 1 of the close, finance wants to start foreign currency valuation, but Ana in accounts payable still has 60 supplier invoices in her queue for the period. What should the close lead do?

Key points
  • The close is a cross-process chain: logistics, controlling and finance each own tasks.
  • Map every task with owner, system step, duration and predecessors.
  • Finance tasks depend on complete logistics and controlling postings, not only on finance work.
  • Hidden dependencies (FX valuation, GR/IR, intercompany) cause most close-day surprises.

Check your understanding · not graded

Lesson check

  1. 1. Why is the month-end close a cross-process event?

  2. 2. What must be complete before foreign currency valuation of open items?

  3. 3. Which task links two company codes in Contoso's close?

  4. 4. Which transaction moves the materials period that controls inventory postings?