Order to cash: where redesign pays back

Order to cash is the sequence of steps that turns a customer’s order into money in the bank. It starts with a quote or an order, runs through credit checks, fulfilment and delivery, continues with invoicing, and ends when payment is received and matched to the right invoice. Along the way, it passes through sales, customer service, operations, logistics and finance.

The path from customer order to cash collected touches sales, operations and finance. Small gaps add up. A pricing error at order entry leads to an invoice dispute. A missing delivery note delays the invoice by a week. A reminder sent only after the due date adds another fortnight. None of these is dramatic on its own. Together, they tie up working capital, consume staff time and frustrate customers.

Because it crosses so many teams, order to cash is one of the processes where redesign pays back most reliably. This guide focuses on the points where changes usually deliver the fastest return.

Start with an end-to-end view

Most organisations measure each part of order to cash separately. Sales tracks orders, operations tracks on-time delivery, and finance tracks debtor days. Nobody sees the whole flow, so problems that start in one team and surface in another go unresolved.

1. Map the process from first customer contact to cash applied, across every team and system involved.
2. Take a sample of recent orders and measure the elapsed time at each stage: order to dispatch, dispatch to invoice, invoice to payment, payment to application.
3. Count how many orders needed correction, credit notes or manual intervention, and at which stage the problem originated.
4. Identify where invoices are disputed and why.

The results usually show that a large share of delay and rework traces back to a few root causes, often at the very start of the process. That is where redesign should begin.

Do not overlook the final step: applying cash. Payments that arrive without a clear remittance, or that cover several invoices at once, can sit unallocated for weeks. The customer believes they have paid; the ledger shows them as overdue, and the credit team chases them. Asking customers to quote invoice numbers, and using bank tools that match payments automatically, removes much of this confusion.

Fix the quote and the order

Errors entered at the start travel through every later step. Validate early.

An incorrect price, a wrong delivery address, a missing purchase order number or an out-of-date customer record will cause problems at every subsequent stage. The warehouse may ship to the wrong place. The invoice will be wrong. The customer will dispute it. Finance will spend time investigating, issue a credit note and reissue the invoice. Weeks of delay can follow from a few seconds of inaccurate data entry.

• Draw prices from a single, maintained price list or contract record rather than allowing free entry.
• Make mandatory the fields customers need for payment, such as their purchase order number, before an order can be saved.
• Validate delivery and billing addresses against the customer master record.
• Run the credit check at order entry, not after fulfilment, so problems are resolved before goods leave.
• Give sales and customer service a clear, fast route to correct customer master data.

Consider a typical industrial distributor that finds a significant share of its invoice disputes come from customers’ purchase order numbers missing from the invoice. Many large customers will not pay an invoice without one. Making the field mandatory at order entry, and checking it against the customer’s requirements, removes a whole category of disputes at almost no cost.

Link delivery to invoicing

Invoices that wait for paperwork delay cash. Trigger billing from delivery events.

In many businesses, invoicing waits for a document to travel from the warehouse or the field to finance: a signed delivery note, a completed job sheet, a timesheet. The document may sit in a driver’s cab, an engineer’s van or a manager’s inbox for days. Every day of delay before the invoice is issued is a day added to the time before payment.

The redesign is to trigger the invoice from the delivery or completion event itself. Electronic proof of delivery, mobile job completion and system integration between dispatch and billing can all make this possible. Where a manual step is unavoidable, set a clear daily cut-off and make the backlog visible.

• Issue invoices automatically when delivery or completion is confirmed in the system.
• Capture proof of delivery electronically at the point of delivery.
• For service work, require job completion on a mobile device before the engineer leaves site.
• Report daily on completed deliveries or jobs not yet invoiced, with an owner for clearing them.

Chase early

Reminders before due dates reduce late payment more than chasing afterwards.

Traditional credit control starts once an invoice is overdue. By then, problems that prevent payment, such as a missing approval at the customer, a query nobody raised or an invoice sent to the wrong person, have had weeks to sit unresolved. Chasing after the due date discovers them too late.

A short, friendly contact a week or so before the due date changes the dynamic. It confirms the invoice has been received and approved, surfaces any query while there is still time to resolve it, and reminds the customer of the date. For larger customers, a quick call works best. For smaller ones, an automated reminder may be enough.

1. Segment customers by value and payment history, so effort goes where it matters most.
2. Send or make a pre-due-date contact for invoices above an agreed value.
3. Log any queries raised and route them immediately to the team that can resolve them.
4. Follow up promptly on the due date if payment has not arrived, with escalation steps agreed in advance.

Resolve disputes quickly

Disputed invoices are often the longest-outstanding items on the ledger. They wait because nobody owns them: finance believes sales should resolve them, sales believes it is an operations issue, and operations is unaware of the dispute at all.

Assign every dispute an owner within a day, with a target time for resolution. Record the root cause of each one, using a short list of categories such as pricing, quantity, delivery, quality or missing reference. Review the categories monthly and feed the findings back to the start of the process. Every dispute prevented at source is worth more than one resolved quickly.

Once we tracked dispute causes, it was obvious. Nearly half came from two pricing issues at order entry. Fixing those did more for cash than a year of chasing.

Credit manager, wholesale client

Own and measure the whole flow

The most important redesign may be organisational rather than technical. Give one person ownership of order to cash end to end, with authority to change steps across teams. Measure the process as a whole, using elapsed time from order to cash and the share of orders that flow through without correction, alongside the familiar measures for each team.

To begin, take a sample of last month’s orders and trace each from entry to payment. Note where each was delayed or corrected and why. Pick the single cause that appears most often, fix it at source, and measure the effect over the following two months. Then move to the next cause.

Source: Intelliversal analysis.

Frequently asked questions

What is order to cash?

The end-to-end process from receiving a customer order, through fulfilment and invoicing, to collecting and applying payment.

Where do order-to-cash problems usually start?

Often at order entry, with incorrect prices, missing purchase order numbers or out-of-date customer data that cause disputes later.

Why remind customers before invoices are due?

It surfaces queries and missing approvals while there is still time to resolve them, reducing late payment more than chasing afterwards.

Explore Business process reengineering (BPR)