Lesson 5 of 5
Assembling and giving O2C sign-off
11 min
Sign-off is the process owner's formal statement that order to cash works well enough to run the business on, with known exceptions. It is not a celebration of a pass rate. The sign-off package is what lets Dan and Maria make that statement responsibly, and lets an auditor later understand why they made it.
What goes in the package
| Section | Content | Source |
|---|---|---|
| Scope and coverage | Coverage matrix: scope items, variants, interfaces, negative paths; what is out of scope and why | Lesson 1 |
| Execution summary | Scenarios planned, executed, passed, failed, blocked; by cycle | Test management tool |
| Evidence | Per scenario: document numbers, document flow, journal entries, outputs, cash clearing | Attached to each test run |
| Defects | Open defects with impact, rating and decision; closed must-fix defects with retest evidence | Defect log |
| Accepted risks | Each accepted defect or gap with workaround, owner and end date | Risk register |
| Signatures | Process owner, key user, test lead; date and scope signed | Sign-off form |
Contents of Contoso's O2C sign-off package.
Keep tests and evidence in the project's test management tool, such as SAP Cloud ALM or SAP Solution Manager, so that each test run, its evidence and its defects are linked and versioned. The package then becomes a report from that tool plus the signed statement, rather than a folder of screenshots assembled the night before.
- Exit criteria met?All required matrix cells executed; no open must-fix defects; evidence complete
- Evidence samplingProcess owner samples several scenarios and re-displays their documents
- Risk reviewAccepted risks read aloud; owners confirm workarounds and dates
- Sign-off decisionSign, sign with conditions, or decline with reasons
- RecordSigned statement stored with the package; go/no-go input for the PMO
Sampling the evidence
Dan should not sign on summaries alone. During the meeting he picks three or four scenarios, including at least one return and one credit-blocked order, and displays their documents live in the QAS system: the document flow, the journal entries, the cleared customer item. If the sampled evidence holds, the summaries are credible. If it does not, the package goes back.
Conditional sign-off and accepted risks
Most real sign-offs are conditional: "signed, subject to fix of defect 412 before cutover and the freight workaround until release 1.2". That is fine if each condition is specific, owned and dated. Record the accepted risks in the risk register with the owner's name. Luis needs them for the cutover plan, and Grace needs them for the go/no-go decision.
- T−6 weeksUAT cycle 2 endsCoverage complete; defects rated
- T−5 weeksMust-fix retestFixes retested with evidence
- T−4 weeksPackage assembledReport from the test tool, risk register, sign-off form
- T−3 weeksSign-off meetingEvidence sampled; conditional sign-off given
- T−1 weekGo/no-goConditions checked; PMO decision
A sign-off statement that means something
Write the statement in plain words and name its scope: "I, Dan, finance process owner, confirm that the order-to-cash scenarios listed in the coverage matrix version 3 were executed in QAS client 100 for release 1.0, that I have reviewed the evidence and sampled four scenarios, and that order to cash is fit for go-live subject to the conditions listed." A statement like that tells an auditor exactly what was signed and on what basis. It also protects the signer: a later production defect outside the stated scope is a coverage question, not a failure of the sign-off.
What would you do?
The night before the sign-off meeting, Priya realizes the evidence for the third-party scenario is only a screenshot of the billing success message. The scenario was marked "pass". The meeting cannot move. What should she do?
- The sign-off package: coverage, execution summary, evidence, defects, accepted risks and signatures.
- Keep tests, evidence and defects linked in the test management tool (SAP Cloud ALM or Solution Manager).
- The process owner samples evidence live before signing.
- Conditional sign-off is normal; each condition must be specific, owned and dated.
- Be transparent about evidence gaps; rebuild from document numbers or record them as conditions.
Check your understanding · not graded
Lesson check
1. What is O2C sign-off?
2. Why should the process owner sample evidence during the meeting?
3. What must every accepted risk have?
4. Where should tests, evidence and defects be kept linked?