Lesson 5 of 5
Sign-off
11 min
Listen to this lesson
Finance sign-off is the moment Dan states, on the record, that the converted books are right and that finance can run the business on the new system. It is not a signature on a summary slide. It rests on criteria agreed long before the weekend, on evidence collected in every mock, and on people who signed their own parts first.
Agree the criteria early
- Reconciliation: G/L balances, open items, assets, inventory and controlling actuals reconciled to zero against the before picture, for every company code and ledger.
- Migration completed: every finance migration activity finished, every error resolved or accepted with a reason, and the migration set to complete.
- Process proof: the regression set passed in the dress rehearsal, including one full period-end close on converted data.
- Reports and extracts: the top reports by use, and every report that feeds banks, tax, consolidation or auditors, match ECC for the same period.
- Smoke test on the weekend: a small set of postings (journal entry, supplier invoice, customer payment, asset acquisition) works in production before users are released.
- Defects: no open critical or high finance defects; medium ones have workarounds, owners and dates.
- Controllers and accountantsEach signs the reconciliation for their area: G/L, AR, AP, assets, inventory, CO
- Test leadPriya confirms regression and close results and open defects
- Finance process ownerDan signs finance acceptance, relying on the signatures below him
- Go/no-goFinance acceptance is one input to the program's decision, chaired by Grace
Sign-off in the mocks, not only on the weekend
Practice the sign-off in every mock. In Mock 1 it will fail, which is useful. By Mock 2 most areas should pass. In the dress rehearsal the full chain should run on time, with the same people and the same templates. On Contoso's weekend, finance reconciliation is due before go/no-go 2 on Sunday at 14:00. If the chain has never run end to end under time pressure, it will be slow on the night.
- Mock 1Method provenReports and templates tried; large differences found and fixed
- Mock 2Mostly passingReconciliations near zero; first close on converted data
- Dress rehearsalTimed sign-offFull chain signed inside the planned slot
- Sunday 14:00Go/no-go 2Finance balances signed on the production weekend
- First month-endHypercare checkFirst real close on SAP S/4HANA reviewed with extra controls
Conditional sign-off
Sometimes one criterion is not fully met but the risk is understood and contained, for example a slow custom report with a standard app as a workaround. A conditional sign-off is legitimate if it names the condition, the workaround, the owner and the date, and if the go/no-go group accepts it explicitly. A difference in balances is never a condition: the books either reconcile or they do not.
Keep the evidence together
After go-live, auditors will ask how finance knew the conversion was right. Answer with one finance conversion file per run: the before-picture reports, the after reports, the reconciliation sheet with reviewers and times, the finance migration log, the SI-Check results from the final run, the regression and close results, the defect list at sign-off and the signed acceptance with any conditions. Store it in the program's test management area in SAP Cloud ALM or the agreed document store, not on someone's laptop. The same file is the starting point for the first month-end in hypercare, when Dan's team checks that the first real close behaves as the rehearsal did.
After sign-off: the first real close
| Close step | Where | Compare with |
|---|---|---|
| Depreciation run | AFAB or the depreciation run app | Planned depreciation per area from the asset history sheet |
| GR/IR analysis and clearing | GR/IR clearing and monitoring apps or classic reports | Open GR/IR balance reconciled at conversion |
| Order settlement | KO88 / CO88 or the settlement apps | Rehearsal close results and run times |
| Material ledger closing | CKMLCP, if actual costing is active | Stock values reconciled at conversion |
| Period open and close | OB52 or Manage Posting Periods | The close calendar used in the dress rehearsal |
Hypercare check of the first real month-end. The rehearsal close is the benchmark for results and timing.
Dan’s team runs the first close with the same checklist as the rehearsal and compares results and timings step by step. A step that takes twice as long, or a balance that moves unexpectedly, is raised as a hypercare incident the same day. Hypercare exit for finance requires this close to pass, which is also when the finance conversion file is closed.
What would you do?
On the conversion weekend, all reconciliations are at zero, but the custom bank payment file extract fails its comparison with ECC. The next payment run is Wednesday. What should Dan recommend at go/no-go 2?
- Agree finance sign-off criteria before Mock 1 and reuse them in every run.
- Criteria: zero reconciliations, completed migration, passed close, matching reports, smoke postings, defects.
- Sign-off is a chain: area owners, test lead, then the finance process owner.
- Conditional sign-off needs a condition, owner, date and explicit acceptance; balances are never conditional.
Check your understanding · not graded
Lesson check
1. Which criterion can never be accepted as a condition in finance sign-off?
2. Why should the finance sign-off be practiced in every mock?
3. What should a conditional sign-off always include?
4. Which evidence shows finance processes, not just data, work after conversion?
5. Why does Dan’s team review the first real month-end close during hypercare?