P2P 505 ยท FROM DISCOVERY TO STABILIZATION
How does a P2P implementation unfold?
Join a fictional operations company as one standard stocked-material purchase moves from workshop questions to production evidence. The walkthrough shows the work, control decisions, compromises, and proof expected at each project phase.
PROJECT PHASE
Discover
Clarify the buying and payment problem
What the team does
Meet Requesting, Purchasing, Warehouse, Accounts Payable, Treasury, Finance, Tax, Security, and IT. Capture categories, channels, volumes, lead times, approvals, exception queues, integrations, controls, and measures of success.
P2P project moment
Northstar Operations chooses one stocked maintenance-material flow first. Services, assets, subcontracting, stock transfers, intercompany procurement, catalogs, and EDI or supplier-network integration remain explicit extensions.
Evidence to leave behind
Approved scope, stakeholder and ownership map, observed process evidence, baseline measures, assumptions, risks, and open questions.
PROJECT PHASE
Fit to standard
Challenge habits without weakening controls
What the team does
Demonstrate standard requisition, approval, source assignment, PO, partial receipt, invoice match, block resolution, and payment using realistic data. Distinguish legal or valuable differences from preferences and workarounds.
P2P project moment
The business accepts standard three-way matching and partial receipt. It retains two-step PO approval and payment maker-checker because authority and cash policy require them.
Evidence to leave behind
Fit decisions, gaps, extension boundary, owners, acceptance criteria, control rationale, and a traceable decision log.
PROJECT PHASE
Design
Connect demand, commitment, receipt, liability, and cash
What the team does
Define the target process, organization, master data, workflow, roles, tolerances, tax, output, accounting, payment channel, reporting, migration, integrations, and non-functional needs before changing isolated settings.
P2P project moment
The design connects company code 1000, plant 1100, purchasing organization 1000, standard PR and PO, supplier/material data, 101 receipt, GR/IR, MIRO tolerances, and a controlled F110 route.
Evidence to leave behind
Signed process and control design, configuration rationale, role concept, interface contracts, migration rules, reconciliation design, and end-to-end test conditions.
PROJECT PHASE
Configure
Build the minimum spine in dependency order
What the team does
Configure the smallest complete scenario, record every consequential decision beside its setting, separate Customizing from master data, transport dependencies together, and prepare controlled test data.
P2P project moment
An approved requisition converts to a PO with the contracted price; nine motors are received, the matching invoice posts, and the payment proposal selects only the eligible liability.
Evidence to leave behind
Configuration workbook, workflow and output evidence, transport sequence, master-data readiness, unit proof, reconciliation checkpoints, and unresolved defects.
PROJECT PHASE
Test
Prove the happy path and the exception path
What the team does
Run unit, string, integration, regression, authorization, workflow, output, payment, and user-acceptance tests. Reconcile quantities, values, statuses, documents, GR/IR, supplier items, and bank clearing.
P2P project moment
The clean nine-unit invoice pays successfully. A ten-unit invoice produces the designed variance block and cannot enter payment until an authorized business resolution is recorded.
Evidence to leave behind
Passed evidence, negative-control proof, defect decisions, retest results, business acceptance, segregation checks, and known residual risk.
PROJECT PHASE
Cut over
Make procurement and payment production-ready
What the team does
Sequence transports, roles, supplier/material/source data, open commitments, balances, interfaces, jobs, forms, workflow responsibility, payment settings, and reconciliation checkpoints. Rehearse timing and contingency decisions.
P2P project moment
The team loads approved suppliers and sources, validates open POs and GR/IR, confirms approvers and payment calendars, enables controlled interfaces, and runs a first-PO smoke test without live bank transmission.
Evidence to leave behind
Approved cutover plan, owners, timings, migrated totals, open-item reconciliation, contingency triggers, payment-control sign-off, and go/no-go decision.
PROJECT PHASE
Go live & stabilize
Operate queues, resolve causes, and hand over
What the team does
Monitor requisition and PO workflow, output, confirmations, overdue receipts, invoice blocks, GR/IR aging, payment proposals, bank status, interfaces, postings, jobs, and support demand. Preserve evidence before changing configuration.
P2P project moment
An invoice block rises for one supplier because its price unit differs from the PO. The team corrects the master and purchasing cause, retests the chain, resolves affected items, and records the support pattern.
Evidence to leave behind
Daily control results, reconciled balances, resolved root causes, accepted backlog, support knowledge, ownership transfer, and stabilization exit.
THE CONNECTING CONTROL
No payment without authorized commitment and received-value evidence
The requirement is not complete because it appears in policy. It must survive fit decisions, workflow and tolerance design, configuration, negative testing, cutover readiness, and production monitoring.
Use P2P 101 for process language, 202 for module topics, 303 for execution, and 404 for configuration dependencies and proof.