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

Lesson 5 of 5

Sign-off

9 min

Listen to this lesson

0:00 / 13:31

Controlling sign-off is a decision by the controller, usually the finance process owner, that the controlling part of the solution is fit to go live, or fit to go live with listed conditions. It is not a feeling and not a meeting. It is a decision based on a sign-off package: evidence that the scenarios in scope were tested, that the numbers were independently validated and reconciled, and that every open issue has an owner and an accepted risk.

What goes into the package

  1. Coverage: the coverage matrix with each controlling scenario linked to its feeding process and test result.
  2. Derivation: positive and negative test results per process, including converted substitutions.
  3. Costing and close: recalculated standard costs, WIP and variances for sampled materials and orders.
  4. Reconciliation: margin analysis versus trial balance for the test periods; the bridge for costing-based CO-PA.
  5. Rehearsal: the controlling close run in order in CMQ, with durations and issues.
  6. Open defects and risks: each with severity, owner, workaround and the controller's acceptance or rejection.
DecisionApprove, approve with conditions, or reject, signed by Dan
Risk acceptancesOpen defects with workarounds, owners and dates
ReconciliationsMargin versus P&L, ledger versus G/L inventory, allocations balanced
ValidationsRecalculated costs, WIP, variances, allocation amounts
Test resultsCoverage matrix and executed test cases in SAP Cloud ALM
The sign-off package as layers: each layer rests on the one below.
The Sign-Off Table · thesignofftable.com/academy/sap-co-304

Conditions and risk acceptance

Few go-lives are clean. The controller's job is to decide which open issues are acceptable. A useful rule: accept an open defect only if it has a workaround that is tested, an owner, a date, and no effect on statutory numbers that cannot be corrected before the period closes. Write the condition so it can be checked: "The custom absorption report (Kenji's team) is replaced by a manual extract until fix release 2; Dan reviews the extract on day 3 of each close" is a condition. "Reports to be fixed later" is not.

An open defect can ride into go-live only as a checkable condition with a tested workaround, an owner and a date.
The Sign-Off Table · thesignofftable.com/academy/sap-co-304
Open itemSeverityWorkaroundDecision
Custom absorption report shows totals onlyMediumManual extract from cost center line items, reviewed day 3Accept until fix release 2 (owner: Kenji)
Customer group blank for 14 new customersMediumDaily exception report; Maria maintains master dataAccept with daily check (owner: Maria)
COGS split account missing in margin reportHighNone that keeps margins correctFix before go-live; retest reconciliation
Costing-based CO-PA bridge differs by $4,100 unexplainedHighNoneInvestigate; blocks retirement of costing-based reports, not go-live

Extract of the risk acceptance log attached to Contoso's controlling sign-off.

  1. SIT endCoverage completeAll scenarios executed at least once; derivation defects fixed
  2. UATValidation and reconciliationCosting, WIP, variances recalculated; margin reconciled for two periods
  3. Dress rehearsalClose rehearsalControlling close run in order on production-like data
  4. Go/no-go minus 5 daysPackage assembledPriya compiles evidence; open items with owners
  5. Go/no-goController decisionDan approves, approves with conditions, or rejects
  6. First close in CMPHypercare checkFirst real close compared with the rehearsal; conditions reviewed
Where controlling sign-off sits on Contoso's timeline.
The Sign-Off Table · thesignofftable.com/academy/sap-co-304

Presenting the package

Keep the presentation short and the evidence deep. Dan does not need to read every test step; he needs a one-page summary he can defend to the CFO and the auditors, with links to the detail. A good summary states the scope (scenarios, company codes, periods), the results by scenario family, the reconciliation results with their differences, the open items with their proposed decisions, and a recommendation from the test lead. Everything on the page should trace to an artifact in SAP Cloud ALM: test plans and executions, defects, and attached reconciliation workbooks. Traceability from requirement to test case to defect is what lets an auditor check the decision months later.

Sign-off does not end responsibility. The first real close in production is the final test: compare its durations and issues with the rehearsal, check each condition on its date, and record the outcome. Grace tracks the conditions in the PMO log so they do not quietly expire.

Each sign-off condition is tracked in Grace's PMO log until it is checked and closed, so none quietly expire.
The Sign-Off Table · thesignofftable.com/academy/sap-co-304

What would you do?

Two days before go/no-go, Priya presents the package. Everything passed except one high-severity defect: the margin report misses the COGS split account. A fix exists but has not been retested. Dan is under pressure to sign. What should he do?

Key points
  • Sign-off is a documented decision: approve, approve with conditions, or reject.
  • The package rests on coverage, validations, reconciliations, a close rehearsal and risk acceptances.
  • Accept open defects only with a tested workaround, owner, date and checkable condition.
  • The first production close is the final test; track conditions until they are closed.

Check your understanding · not graded

Lesson check

  1. 1. Which outcome options does a controlling sign-off have?

  2. 2. Which is a checkable sign-off condition?

  3. 3. What is the final test of controlling after sign-off?