A need becomes a requisition, a requisition becomes a PO, a PO becomes a receipt, and the first journal entry of the whole P2P is born. This page is Procurement's home base: learn the flow animated, fix it when it jams, see what 26C is about to change, and drill the questions panels open with.
The complete procure-to-pay with every call yours: inventory or expense destination, negotiation or direct PO, accrue at receipt or period end, while a living ledger books every entry in front of you. Six route combinations.
⚙️Watch one purchase pulse from Procurement through Receiving into Inventory while the accounting engines fire underneath. The ninety-second mental model before you ride the full flow.
Employees order for themselves: requisitioning BU, catalogs, smart forms, content zones, approvals, and the Redwood application with its search setup.
📄Requisitions become purchase orders that create, approve and email themselves: BU options, document styles, buyer rules, touchless agreements.
🗂️One clean record per supplier: numbering, self-service registration with approvals, sites and assignments, controls on bank details.
🚪Suppliers see their own orders and maintain their own profiles under your approval: provisioning roles, account flows, a pilot rollout.
🔨Run a real competition: styles, enforced templates, scored requirements, award approvals, and the agreement that comes out the other end.
Stuck requisitions with silent approval rules, POs that won't receive, and every other common error. All the fixes, one door.
✅Month-end in dependency order: warehouse cutoff, receipt accounting, the cost processor, the GL handoff, with the why behind every step.
The full 26C deck opens already filtered to Procurement features, enablement flags, scale badges, and your read/priority tracking on every card.
🧪Executable test cases for the wave's riskiest changes, preconditions, steps, expected results. Track pass/fail/blocked as you go, export the evidence.
One question a day, spaced-repetition boxes, and a streak. The P2P scenarios here are the exact shape panels use to separate juniors from seniors.
🎧Three AI interviewers run a live Procurement scenario and score what a real panel would hear. Ten minutes.
Senior tip the docs skip: in interviews, Procurement questions are rarely about Procurement, they're about what books where, and when. If you can narrate receipt → accrual → validation → payment with the entries, you've answered three modules at once. That story lives in P2P Live; the costing half deepens in Cost Management.
Three common paths: a buyer creates it in the Purchase Orders work area; an approved requisition turns into one automatically when the agreement allows it; or it comes through an integration. To see the whole journey with the accounting behind it, follow the P2P flow, step by step. To set up the automatic path, use the Purchasing implementation guide.
The module family where buying happens: requisitions (internal requests), purchase orders (the commitment to a supplier), agreements (negotiated prices), receiving, and the supplier records behind them. This page collects everything we have for it.
Setup and Maintenance, the Manage Procurement Agents task: each buyer or catalog administrator gets an agent record per procurement business unit with switches for what they may manage. The Purchasing guide covers it step by step.