Blog / Concepts 6 min read ·

P2P, O2C and R2R: the end-to-end processes explained

Every ERP project, shared service centre and finance transformation talks in the same shorthand: P2P, O2C, R2R, H2R. Each name is an end-to-end process, a chain of work that starts with a trigger outside the company or a department and ends with a result someone can measure. Here is what each one covers, and how to map it so the handovers are visible.

What makes a process end-to-end

A departmental process stops at the edge of the department: purchasing raises the order, accounts payable pays the invoice. An end-to-end process follows the work across those edges, from the trigger to the outcome, regardless of who does each step. That is why the names are always 'X to Y': they name the first event and the last one.

The reason ERP vendors, consultants and auditors all organise around them is that the expensive problems sit between departments. An invoice that cannot be paid because nobody recorded the goods receipt is not an accounts payable problem or a warehouse problem; it is a procure-to-pay problem, and only a map of the whole cycle shows it.

The four you will hear most

Most companies describe their core operations with four or five end-to-end processes. The names vary slightly by vendor and consultancy, but the scopes are stable:

  • Procure-to-pay (P2P): from identifying a need for goods or services to paying the supplier. Requisition, approval, purchase order, goods receipt, invoice, three-way match, payment. Owned jointly by procurement and accounts payable. Sometimes called purchase-to-pay.
  • Order-to-cash (O2C or OTC): from receiving a customer order to collecting the cash. Order entry, credit check, fulfilment and delivery, invoicing, cash application, collections. Owned jointly by sales or customer service, logistics and accounts receivable.
  • Record-to-report (R2R): from recording financial transactions to publishing the reports. Journal entries, sub-ledger close, accruals, reconciliations, consolidation, management and statutory reporting. Owned by the controller and the general ledger team.
  • Hire-to-retire (H2R): from recruiting an employee to their exit. Hiring, onboarding, payroll, performance, changes, offboarding. Owned by HR with payroll and IT. Sometimes called recruit-to-retire.

The others on the list

Larger process catalogues go further. You will also see these, especially in manufacturing and asset-heavy businesses:

  • Plan-to-produce (or plan-to-make): from demand planning to finished goods.
  • Acquire-to-retire (or acquire-to-dispose): the life of a fixed asset, from purchase to disposal.
  • Lead-to-cash and quote-to-cash: order-to-cash extended backwards to include the sales pipeline and quoting.
  • Source-to-contract and source-to-pay: procure-to-pay extended backwards to include sourcing and supplier selection.
  • Design-to-retire, issue-to-resolution, request-to-service: product lifecycle, customer service and IT service processes.

How to map an end-to-end process

The format that works is a swimlane map: one lane per role or team, phases across the top, and every decision drawn with its real branch labels. Swimlanes matter more for end-to-end processes than for any other kind, because the handovers between lanes are the whole point.

Keep one map per end-to-end process, and keep it at a level where the whole cycle fits: twenty to thirty steps. When a phase needs more detail, such as invoice approval inside P2P, give it its own map and link the two. Building the map from a spreadsheet, one row per step, makes it easy to reorder and to review with the people who own each lane.

Free maps to start from

These vendor-neutral maps are free to open and edit, no signup. They are the right starting point for a workshop with the business, before anyone talks about how a particular system implements the process.

If you are implementing SAP, Oracle, Dynamics 365 or NetSuite

The same cycles look different in each ERP: different screens, different approval mechanisms, different names for the same document. QueryChart, our sister product for controlled process documentation, publishes system-specific versions with the transaction codes and screens on each step:

Frequently asked questions

What is the difference between P2P and S2P?

Procure-to-pay starts when someone needs to buy something and the supplier is usually already known. Source-to-pay adds the sourcing work before it: market analysis, tendering, supplier selection and contracting. Companies with a strategic sourcing team tend to use S2P; most process maps start with P2P.

Is order-to-cash the same as quote-to-cash?

No. Quote-to-cash starts earlier, with pricing, quoting and contract negotiation, and ends at the same place. Order-to-cash starts when the order is placed. If quoting is complex in your business, map it as its own process that hands an accepted order to order-to-cash.

How many end-to-end processes does a company have?

Most describe their operations with eight to fifteen. Microsoft's Dynamics 365 business process catalog uses about fifteen end-to-end processes; SAP and the APQC Process Classification Framework use similar top-level lists. Start by mapping the three or four that carry the most money and the most handovers, usually P2P, O2C and R2R.

Try it on your own process

The editor is free and opens with a starter template. One row per step — the swimlane diagram renders as you type. No signup required.

Start Process Mapping Free