The whole business, one flow at a time
Every previous module taught one part. This module connects the parts. You will run a complete order-to-cash cycle and a complete procure-to-pay cycle, with the same team that will run them after go-live.
The goal is not to learn a new screen. The goal is to practice the handoffs. The salesperson confirms the order. The warehouse ships it. The bookkeeper invoices it and records the payment. In the other direction, purchasing orders, the warehouse receives, and the bookkeeper pays the vendor.
Practice the handoff, not just the click: the most common go-live problems happen between roles, not inside a screen. This module is designed to surface those problems while the sandbox is still disposable.
Learning objectives
By the end of this module, you should be able to:
- Run a complete order-to-cash cycle from quotation to reconciled payment.
- Run a complete procure-to-pay cycle from RFQ to paid vendor bill.
- Handle a customer return and a vendor return within the flow.
- Identify the handoff points between sales, warehouse, and accounting.
- Use the status of each document to decide the next action.
Core concepts
Order-to-cash
| Step | Document | Owner | Next action |
|---|---|---|---|
| 1. Quote | Quotation | Sales | Confirm when the customer accepts. |
| 2. Order | Sales order | Sales | Warehouse prepares the delivery. |
| 3. Deliver | Delivery order | Warehouse | Validate when the goods ship. |
| 4. Invoice | Customer invoice | Bookkeeper | Post and send the invoice. |
| 5. Pay | Payment | Bookkeeper | Register and reconcile the payment. |
Procure-to-pay
| Step | Document | Owner | Next action |
|---|---|---|---|
| 1. Request | Request for quotation | Purchasing | Confirm when the vendor accepts. |
| 2. Order | Purchase order | Purchasing | Warehouse expects the receipt. |
| 3. Receive | Receipt | Warehouse | Validate when the goods arrive. |
| 4. Bill | Vendor bill | Bookkeeper | Post the bill. |
| 5. Pay | Vendor payment | Bookkeeper | Register and reconcile the payment. |
Handoff points to watch
- Sales to warehouse: the sales order must be confirmed and the delivery must be ready. A draft quotation does not create a shipment.
- Warehouse to bookkeeper: the delivery must be validated before the invoice is based on delivered quantities. A receipt must be validated before the vendor bill is matched.
- Bookkeeper to owners: the reports are only useful if the documents are posted and reconciled. A month-end report built on drafts is misleading.
- Returns: a return creates a reverse stock movement and a credit note. Both sides must be completed, or the stock and the accounting will disagree.
Do not skip the status check. Before you act, read the document status. A delivery that is still waiting cannot be validated as shipped. A bill that is still draft cannot be paid. The status tells you what is possible.
Walkthrough
This is a team exercise. Assign roles before you start: sales, warehouse, bookkeeper, and an observer or facilitator. The observer watches the handoffs and notes where the process stalls.
Order-to-cash simulation
-
Sales creates and confirms the quotation
The salesperson creates a quotation for a practice customer with two products. Confirm the price, the tax, and the payment term. Confirm the quotation into a sales order. Announce that the order is ready for the warehouse.
-
Warehouse ships the order
The warehouse opens the delivery, reserves the stock, picks, packs, and validates the shipment. If stock is short, create a backorder and tell the salesperson. Announce that the delivery is done.
-
Bookkeeper invoices and collects
The bookkeeper creates or reviews the invoice, posts it, and registers the customer payment. Confirm that the invoice is paid. Announce that the order-to-cash cycle is complete.
-
Handle a customer return
The salesperson requests a return for one line. The warehouse validates the reverse delivery. The bookkeeper creates and posts a credit note. Confirm that the stock is back and the customer balance is reduced.
Procure-to-pay simulation
-
Purchasing creates and confirms the RFQ
The purchasing owner creates an RFQ for a practice vendor with two products. Confirm the price, the tax, and the expected arrival date. Confirm the RFQ into a purchase order. Announce that the warehouse should expect a receipt.
-
Warehouse receives the goods
The warehouse opens the receipt, counts the goods, and validates the receipt. If the shipment is short, create a backorder and tell purchasing. Announce that the receipt is done.
-
Bookkeeper bills and pays
The bookkeeper creates or reviews the vendor bill, posts it, and registers the vendor payment. Confirm that the bill is paid. Announce that the procure-to-pay cycle is complete.
-
Handle a vendor return
The warehouse creates a return to vendor for one line. The bookkeeper creates and posts a vendor credit. Confirm that the stock is reduced and the vendor balance is adjusted.
-
Review the results together
Run a sales report, a purchase report, a stock report, and a profit and loss for the practice period. Compare the numbers with what the team expected. Note any discrepancy and trace it to the document that caused it.
Exercise
Team simulation
Work in teams of three or four. Assign a salesperson, a warehouse person, and a bookkeeper. The facilitator observes and keeps time.
- Complete one order-to-cash cycle from quotation to paid invoice.
- Complete one customer return with a reverse delivery and a credit note.
- Complete one procure-to-pay cycle from RFQ to paid vendor bill.
- Complete one vendor return with a reverse receipt and a vendor credit.
- Run the sales, purchase, stock, and profit and loss reports for the period.
- List the handoff points where the team had to wait or ask a question.
Expected result: both cycles are complete, both returns are handled, and the reports reflect the transactions. The team can name the handoff points and the status that triggers each handoff.
Check your understanding
Answer these questions before the go-live module. Open each answer to check yourself.
1. What are the five steps of order-to-cash?
Quote, order, deliver, invoice, and pay. The quotation becomes a sales order, the warehouse delivers, the bookkeeper invoices, and the payment is registered and reconciled.
2. What are the five steps of procure-to-pay?
Request, order, receive, bill, and pay. The RFQ becomes a purchase order, the warehouse receives, the bookkeeper posts the vendor bill, and the payment is registered and reconciled.
3. What is the most common handoff problem between sales and warehouse?
A delivery that is not ready or a quotation that was never confirmed. The warehouse cannot ship a draft quotation, and the sales team needs to know when the delivery is done.
4. Why must both the stock side and the accounting side of a return be completed?
If only one side is done, the stock and the accounting disagree. The reverse delivery corrects the stock, and the credit note corrects the balance. Both are needed.
5. Why should you check the document status before acting?
The status tells you what is possible. A waiting delivery cannot be validated as shipped, and a draft bill cannot be paid. Acting without checking the status causes errors and rework.
Facilitator notes
Suggested timing: 10 minutes setup and roles, 40 minutes order-to-cash, 40 minutes procure-to-pay, 20 minutes returns and report review, 10 minutes debrief. Keep the teams small and the roles rotating.
- Prepare two practice customers, two practice vendors, and enough stock for both cycles. Reset the sandbox between runs if needed.
- Assign an observer to each team. The observer's notes on handoffs are the most valuable output of the module.
- Do not rescue the team too quickly. Let them discover the status problem, then ask them what the document was telling them.
- Debrief with three questions: where did you wait, what status did you need, and who owned the next step?
- Record the handoff problems. They become the go-live checklist items in the next module.
Next steps
You have run the whole business in the sandbox. The final module covers go-live readiness: the checklist, the data validation, the support model, and the first weeks after launch.