Procure to Pay (P2P) Cycle

The Procure to Pay cycle is the full lifecycle of government purchasing, starting when someone in your department identifies a need and ending when the Receiver General cuts the cheque. If you're tracking federal contracts or trying to understand where a particular opportunity sits in the procurement timeline, this is your roadmap.

How It Works

According to the Treasury Board Secretariat's Guideline on Common Financial Management Business Process 3.1, the Manage Procure to Payment process breaks down into nine subprocesses arranged in six groups: Manage Requirements, Control Commitments, Manage Contracts, Administer Contracts and Deliverables, Manage Payables, and Manage Payments. Each stage has its own controls and approvals.

Here's how it typically flows. A responsibility centre manager with delegated expenditure initiation authority identifies a need—maybe DND needs new radios or SSC requires cloud services. That manager creates a requisition, which triggers commitment controls to ensure budget availability (linked to Business Process 1.1 - Manage Planning and Budgeting). Then comes supplier selection and contract award, governed by the policies in the Supply Manual. After award, you move into contract administration: receiving goods or services, verifying they meet specs, processing invoices, and ultimately authorizing payment under Section 33 of the Financial Administration Act.

In practice, PSPC handles much of this for common goods and services, but individual departments manage their own cycles for specialized needs. The Supply Manual follows the chronological phases of the procurement cycle, which means its structure mirrors how you'd actually execute these steps. Worth noting: the guideline specifically applies to operational or capital procurement using a purchase order or other type of contract—so not grants, contributions, or salary payments.

Key Considerations

• Commitment versus payment: Money gets committed (reserved) early in the cycle, often before a contract is even signed. Payment comes much later. If you're tracking departmental spending, understanding this lag matters.

• Section 33 authority: Someone with proper delegation must certify that work was done and goods received before payment can be authorized. This is the checkpoint that catches invoices arriving before delivery is complete.

• Multiple subprocess owners: Requirements management might sit with program staff, contracting with procurement officers, and payment processing with finance. Handoffs between these groups are where delays typically happen.

• The cycle doesn't always start at the beginning: Standing offers and supply arrangements compress the early stages, letting departments jump straight to contract issuance when they have pre-qualified suppliers.

Related Terms

Expenditure Initiation, Contract Award, Section 32 and Section 33, Standing Offer, Purchase Order

Sources

• Treasury Board Secretariat - Guideline on Common Financial Management Business Process 3.1 - Manage Procure to Payment

• Government of Canada Supply Manual

• Supply Manual - Prepared by Policy and Process Directorate

When you're analyzing procurement data or trying to predict payment timing, remember that this cycle can stretch over months from need identification to final payment. Plan accordingly.