Your KPIs Are Working — Your Processes Aren’t
Here is why and what it takes to resolve it
Most organizations that have invested in process improvement know these four names. Procure-to-Pay. Order-to-Cash. Record-to-Report. Hire-to-Retire. They appear in ERP implementations, shared service designs, and process maturity assessments across industries and geographies. What is less commonly understood is why all four remain stubbornly resistant to improvement, not in isolated organizations, but systematically, across the sector.
This article maps the four process families, explains what makes each one structurally distinctive, and identifies the governance pattern they share. It is the second in a series on why BPM investment stalls at mid-level maturity.
Two Problems You Have Seen Before
Consider a familiar sales problem. A customer complains about a late delivery and a missing invoice. Sales confirms the order was placed correctly. Production confirms it was manufactured on time. Logistics confirms the shipment went as planned. Finance confirms the invoice was issued according to procedure.
In most organizations, no one owns the problem as a whole. Every function has performed correctly within its own perimeter. No one has seen the end-to-end timeline, from order confirmation to payment, that would show where the cycle actually broke down.
The incentive misalignment surfaces next. The customer does not pay on time. Finance applies a late payment fee according to policy. Sales is furious, this is a strategic account, and the fee risks the relationship. Finance points out that days sales outstanding is already above target and that someone has to enforce payment terms. The dispute escalates to management.
What goes unnoticed is that Sales hit its invoicing target on time. The revenue was booked. The sales bonus was earned. Whether the cash actually arrived, and when, is someone else’s problem.
This is not cynicism, it is rational behavior. Sales measures what it controls: the invoice went out, the order was correct, the revenue was booked. Whether the customer pays depends on credit terms and collection processes owned by other functions. The problem is not the metric. The problem is that no one holds the end-to-end metric.
It is not a sales problem. It is not a finance problem. It is an Order-to-Cash problem. And no one owns Order-to-Cash.
The KPI structure makes the conflict inevitable. Sales is typically measured on invoiced revenue. The moment the invoice goes out, the target is hit and the bonus is earned. Logistics on OTIF, on-time, in-full delivery, which ends when the goods leave the warehouse. Finance on DSO, which begins when the invoice is issued. Three functions, three clocks, none running on the same timeline. In most cases, no one is measured on whether the cash actually arrived, or how long the full cycle took.
A process-oriented KPI would make the failure visible, order-to-cash cycle time, or the percentage of orders fulfilled, invoiced, and collected without exception. That is a metric no single function can own. A process owner can. There is no process owner.
Now consider a familiar procurement problem. Purchasing has negotiated framework agreements with lower prices. Total procurement cost is not falling. Purchasing blames Finance — invoices paid outside agreements. Finance blames Production — orders placed without purchase requisitions. Production blames Purchasing — the agreements do not cover what they actually need.
Maverick spend is invisible at the process level because no one measures Procure-to-Pay as an integrated flow. Purchase requisitions are skipped because no one owns the process to enforce them. When this surfaces in a budget review, it looks like a discipline problem. It is not.
Here too, the KPI structure drives the outcome, and in one case actively rewards the wrong behavior. Purchasing is commonly measured on price variance: registers nothing when the contract is bypassed. Production on supplier delivery precision: creates pressure to order through the fastest channel, agreements optional. Finance on cost per invoice processed: a legitimate efficiency metric that is, perversely, improved by maverick spend, fewer purchase orders means a simpler processing flow. Finance is not optimizing incorrectly. The metric is correctly designed for what Finance controls. The problem is what all three optimized simultaneously produce. Each KPI is locally rational. Together they form a system that rewards bypassing the process.
A process-level KPI, maverick spend rate or the percentage of orders initiated with a purchase requisition, would expose the gap immediately. That metric belongs to a process owner. In most organizations, there is none.
These are not edge cases. They are the default state in organizations that have strong functional structures but lack process owners with real authority, real visibility, and real accountability for end-to-end outcomes. Understanding why requires a precise definition of what a process family actually is.
What a Process Family Is and Isn’t
A process family is not a department or a function. It is an end-to-end flow of work that crosses multiple functional boundaries — beginning with a trigger and ending with an outcome. Large organizations typically organize around a small number of core functions such as Sales, Production (or Service Delivery), Logistics, Procurement, Finance, and HR, each optimized for within-function performance, each with its own KPIs and reporting lines. The process families cut across all of them. In day-to-day operations, a process functions not as an integrated whole but as a sequence of hand-offs between units that optimize locally. Which is precisely why the problems above are so persistent — and why the structural properties of each family
The Four Families
Each process family shares one structural property: it spans the functional configurations large organizations actually use in a way that makes integrated accountability predictably fragile.
Procure-to-Pay covers the full cycle from need identification through supplier selection, purchase order creation, goods receipt, and payment. It typically involves five to eight contributing units. The accountability gap is predictable: procurement targets price variance, finance targets processing cost, and operations targets delivery compliance. These are three separate metrics for one integrated process and no single actor is accountable for the whole. The reason is the same as in the O2C case: no one has a process-level view.
Order-to-Cash connects a customer order to cash receipt, passing through order management, fulfillment, logistics, billing, and collections. Sales is measured on order intake. Logistics on delivery performance. Finance on days sales outstanding. Three separate targets, three separate reporting lines, one process. Order-to-delivery cycle time — the metric that would reveal end-to-end performance is often not tracked or managed cross-functionally.
Record-to-Report is the most structurally complex of the four. It integrates transactional accounting from every business unit in the organization with group-level consolidation, reporting, and external disclosure. The number of contributing units can reach twenty or more. The accountability gap here is inverted compared to the others: business units own the transactions but have no stake in reporting outcomes. Group finance owns the reporting but does not control the transactions. In many large organizations, no single actor is effectively accountable for the data quality that determines whether the financial statements can be trusted. Close cycle time, the clearest end-to-end metric, is often not managed as an integrated process outcome.
Hire-to-Retire spans the full employee lifecycle from workforce planning and talent acquisition through payroll, development, and offboarding. HR sub-functions hold separate metrics: time-to-hire, payroll accuracy, training completion rates. Line managers are accountable for headcount outcomes but not for the HR process performance that underpins them. End-to-end workforce lifecycle cost is often not visible to any single actor.
These four families appear in virtually every large organization, regardless of industry. Other process families follow the same structural logic — the names change, the pattern does not. Issue-to-Resolution spans customer service, technical support, and back-office: customer service typically measured on first-contact resolution, technical support on ticket closure time, back-office on SLA compliance, three clocks for one customer experience. Bid-to-Bill, common in project-based organizations, runs from commercial proposal to final invoice: Sales owns the margin at bid, Delivery owns the cost at execution, Finance owns the invoicing, and no one owns the gap between bid margin and realized margin. The specific families vary by industry. The structural pattern does not, which is what the next section establishes.
The Pattern They Share
That pattern is striking not for the differences between these families, but for their similarity. In each case the contributing units are known, the accountability gaps are known, the missing metrics are known. And yet the gaps persist, year after year, across organizations that have invested seriously in process improvement.
These organizations are not unaware of the problem, they are unable to resolve it through their current tools. APQC has tracked “defining and mapping end-to-end processes” as the top process management priority for several consecutive years, cited by around 40% of organizations in its 2025 survey (APQC, 2025). The priority has not translated into resolution.
That observation points to something structural. The four process families are not difficult to improve because of insufficient effort, weak methodology, or lack of executive attention. They are difficult because each cuts across the coordination logic of the units it spans. Each unit is optimized for within-function performance. The process requires cross-function accountability. By design, the two are in tension. What changes when an organization moves beyond that constraint is the subject of the next section.
What Advancing Beyond Level 3 Would Change
Both cases share the same underlying condition: functional KPIs present and functioning, process-level accountability absent. This is a defining characteristic of Level 3 and precisely what Level 4 requires an organization to resolve.
At Level 3, the O2C scenario plays out as described: the dispute lands in a management meeting that should never have been necessary. The process owner exists on the organisation chart but has no consolidated view of order-to-cash cycle time, no authority to realign incentive structures across Sales and Finance, and no personal stake in whether cash arrives on time. The role exists. The governance does not.
At Level 4, the same scenario unfolds differently. The process owner receives integrated performance data, order-to-cash cycle time, first-time-right rate, percentage collected within terms, across all contributing functions, at least monthly. When DSO deteriorates, the root cause is visible in the data: is it a credit issue, a billing error, or a handoff failure between logistics and invoicing? The process owner has authority to convene the relevant functions and mandate a fix, without escalating to the CFO. And because the process owner’s performance evaluation includes an end-to-end process KPI, the incentive to act is structural, not discretionary.
For the sales team, this changes one thing that matters: the late-payment dispute stops landing in their lap. When a strategic customer does not pay on time, the process owner, not the sales director, owns the investigation and the resolution. Sales retains its invoicing metric. What changes is that someone else now holds the end-to-end metric and has both the visibility and the mandate to act on it. The conflict does not disappear. It gets routed to the right level.
At Level 3 in P2P, maverick spend is invisible because no one measures Procure-to-Pay as a whole. Purchase requisitions are unenforced because the process owner lacks authority over Production’s ordering behavior. At Level 4, the maverick spend rate is a visible metric owned by a specific actor who has both the data to detect it and the mandate to address it, including the authority to work with Finance to restructure the cost-per-invoice KPI that currently rewards bypassing the process.
At Level 3 in R2R, the most structurally complex case, close cycle time is not managed end-to-end. It is the sum of whatever each business unit delivers, with group finance unable to enforce data quality standards it has no authority to set. At Level 4, the process owner holds a first-time-right rate per entity: the percentage of submissions requiring no restatement. That metric makes data quality problems visible before they become consolidation problems, and gives the process owner a concrete basis for working with business unit CFOs on close procedures, structurally, not through quarterly CFO intervention.
Advancing from Level 3 to Level 4 does not require a new methodology or a new governance framework. It requires that the existing process owner role be made structurally operative: end-to-end visibility, cross-functional authority, and incentive alignment with process outcomes. Without all three, the KPI conflicts described above are not management failures waiting to be resolved. They are structural features of the organization as predictable as the processes themselves.
What This Means Before Your Next Process Investment
Before investing further in any of these process families, new governance structure, new system, new operating model, the prior question is whether the structural conditions for cross-functional accountability exist.
If you have read the first article in this series, these three questions are familiar. They are repeated here deliberately, because they apply to every process family described above, and because the answer is often different for each one. An organization can have the conditions in place for P2P and not for R2R. The diagnosis is process-specific.
Three questions determine this:
1. Does the process owner have integrated performance data spanning all contributing units, not functional reports, but a consolidated end-to-end view?
2. Does the process owner have authority to approve an improvement that requires changes in more than one function, without separate sign-off from each function head?
3. Does the process owner’s performance evaluation include at least one end-to-end process KPI with meaningful weight?
If the answer to any of these is no for a given process family, the structural conditions for governance are absent. More investment will produce more infrastructure. It will not produce more maturity.
#BPM #ProcessManagement #OperationalExcellence #ProcessImprovement #BusinessTransformation #P2P #O2C #R2R #H2R