Lesson 3 of 5
Handoffs and RACI
7 min
Processes rarely fail inside a department. They fail at handoffs: where sales passes an order to the warehouse, where the warehouse's goods issue triggers billing, where billing hands receivables to finance. Each side assumes the other is responsible. The process owner's job is to make responsibility at every handoff explicit.
Order-to-cash handoffs at Contoso
- Sales → creditOrder for Great Lakes Fleet Services exceeds limit; credit team must release or reject
- Sales → warehouseReleased order becomes a delivery due list item at shipping point 1710
- Warehouse → billingGoods issue posted; delivery appears in the billing due list
- Billing → financeBilling document posts to accounting; receivable is open
- Finance → salesOverdue receivable triggers dunning and may block new orders
The RACI matrix
A RACI matrix assigns, for each activity, who is Responsible (does the work), Accountable (owns the outcome and approves; exactly one per activity), Consulted (gives input before) and Informed (told after). The discipline of "one A per row" is what makes it useful.
| Activity | Sales | Credit | Warehouse | Billing | Finance (AR) | O2C process owner |
|---|---|---|---|---|---|---|
| Create sales order | R | I | I | A | ||
| Release credit-blocked order | C | R | C | A | ||
| Create delivery and post goods issue | I | R | I | A | ||
| Process billing due list daily | C | R | I | A | ||
| Release billing documents blocked for accounting | R | C | A | |||
| Clear incoming payments | I | R | A | |||
| Maintain customer credit limits | C | R | C | A | ||
| Approve change to pricing procedure | C | C | C | A |
Extract of Contoso's order-to-cash RACI. The process owner is accountable end to end; departments are responsible for their steps.
Common RACI problems
| Problem in the matrix | What it causes | Fix |
|---|---|---|
| No A on a row | Nobody decides when the step fails | Assign one accountable role |
| Two or more A's | Decisions stall or conflict | Keep one; make the others C |
| Too many C's | Slow decisions; everyone must be asked | Consult only those whose input changes the decision |
| R without the SAP role | Responsible people cannot perform the step in the system | Align business roles in SAP with the RACI |
| RACI never updated | Matrix no longer matches reality | Review at each release and organizational change |
Making handoffs visible in SAP
Most handoffs in SAP S/4HANA show up as a work list: blocked orders waiting for credit release, the delivery due list, the billing due list, billing documents not yet posted to accounting, unapplied incoming payments. Each list is a queue between two teams. Give each queue an owner, a frequency and a limit, such as "billing due list processed daily; nothing older than one working day". Then measure it. A queue that grows is an early sign the handoff is failing, long before a customer or an auditor notices.
| Queue | Between | Rule at Contoso |
|---|---|---|
| Credit-blocked orders | Sales and credit | Released or rejected within four business hours |
| Billing due list | Warehouse and billing | Processed daily; nothing older than one working day |
| Billing not posted to accounting | Billing and finance | Zero at day end; exceptions explained |
| Unapplied incoming payments | Bank and AR | Applied within two days |
Handoff queues with owners and limits.
Align RACI with SAP roles and controls
A RACI on paper must match access in the system. If the credit team is responsible for releasing blocked orders, their business role must contain the credit release app, and sales should not have it. That is a control as well as a convenience: separating order entry from credit release is a segregation-of-duties decision the process owner approves. Test it in UAT with the real roles.
What would you do?
In Contoso's UAT, billing documents for several deliveries sat unbilled for four days. The warehouse says it posted goods issue; billing says nothing appeared on its list; finance noticed the gap in receivables. What should the process owner do first?
- Processes fail most often at handoffs between departments.
- A RACI matrix assigns Responsible, Accountable, Consulted and Informed per activity, with exactly one A.
- Delegated accountability must be written into the matrix.
- RACI responsibilities must match SAP business roles and segregation-of-duties controls.
- Test each handoff end to end with real roles before signing the design.
Check your understanding · not graded
Lesson check
1. In a RACI matrix, how many roles should be Accountable per activity?
2. What does "C" mean in RACI?
3. The credit team is responsible for releasing blocked orders. What must be true in SAP?
4. Where do processes most often fail?