Procure-to-Pay (P2P) Cycle Explained with Dynamics 365 Finance

Most businesses discover procurement problems later than they should, a vendor stops shipping because payment is 60 days overdue, or a CRA audit surfaces years of unclaimed Input Tax Credits because invoices were never matched to the right tax codes. 

The Procure-to-Pay cycle runs from an internal purchase request to the final vendor payment in the general ledger. It crosses purchasing, receiving, accounts payable, and finance, four areas that in many organizations run on separate tools with a lot of email coordination holding it together. 

Dynamics 365 Finance puts all of it in one system. Goods receipt posts in the warehouse and the AP matching queue updates. An approver gets a notification and acts from email without opening D365. A duplicate invoice number gets blocked before it posts.  

This article explains every stage of that process including what happens, what D365 does there, and what it means for Canadian businesses managing GST/HST and CRA compliance.

What Procure-to-Pay Covers 

The P2P process lifecycle runs from a purchase requisition to a cleared vendor payment. It is not the same as Source-to-Pay, that covers vendor evaluation, contracts, and sourcing strategy. P2P starts after the vendor are chosen, buying begins. In Dynamics 365, both sit inside the Source to Pay business process catalog but at different operational points.

D365 Finance handles two purchasing categories. Direct procurement covers production input materials tied to manufacturing schedules with tight timing. Indirect covers everything else like IT, professional services, facilities. For most Canadian mid-sized businesses, indirect spend is larger than it looks and far less controlled, which is where off-contract purchasing accumulates.

Hidden Costs of Managing Purchases and Invoices Manually 

Manual invoice processing runs between $12.88 and $19.83 per invoice. AP teams using automation bring it to $2.78, per Ardent Partners benchmarking data in Parseur’s analysis. For a company processing 5,000 invoices a year, that gap is $50,000 to $65,000 annually.

Beyond processing cost, every vendor invoice in Canada is a potential Input Tax Credit under CRA rules, but only if it includes the vendor's GST/HST registration number and is properly documented. When procurement is disorganized, ITCs go unclaimed and audit risk grows. Dynamics 365 Finance handles both sides through the same workflow.

7 Stages of the P2P Cycle in Dynamics 365 Finance 

Stage 1: Purchase Requisition 

The PR is where the procurement cycle begins. An employee submits a Purchase Requisition in D365 under Procurement and Sourcing → All Purchase Requisitions. Nothing external has been committed at this point — the PR exists to get documented internal authorization before any purchase is made. 

The approval workflow is configurable by department, spend category, and amount. A $500 stationery order routes differently than a $75,000 IT services contract. Through D365's Power Automate integration with business events, approvers can act on a PR directly from an email notification i.e., no D365 login required. For managers split across multiple provincial offices, that removes a bottleneck that otherwise adds days to the approval cycle. 

Prerequisites: Product master, Site and Warehouse master, Vendor master, PR user permissions, and an active PR workflow.

Stage 2: Request for Quotation 

When pricing is unconfirmed or the purchase value requires competitive bids, the team issue an RFQ. In D365 it generates directly from an approved PR. Vendors receive and respond through the Vendor Collaboration Portal. Once submissions close, the buyer compares bids inside D365, selects the best offer, and the system rejects the others. The winning bid converts into a Purchase Order.

For Canadian government contractors and construction companies, this stage is often a documented regulatory requirement — not a discretionary step, and D365 maintains the audit trail to prove it ran correctly.

Stage 3: Purchase Order

The PO is the first document in the Microsoft D365 P2P process with external legal weight. Once confirmed and sent to the vendor, it is a binding commitment.

D365 supports four PO creation routes depending on what happened upstream: PR → RFQ → PO when bids were needed; PR → PO when pricing is pre-agreed; RFQ → PO for procurement-initiated purchases; or a Direct PO when all details are already confirmed. After confirmation, Power Automate can send the vendor a copy automatically.

Change management workflows in D365 mean any modification to quantity, price, or delivery date goes through approval before updating the live PO, which matters on contracts where unauthorized changes create financial exposure. For businesses buying from US suppliers, D365 handles multi-currency POs and applies the correct provincial tax treatment per vendor and purchase category.

Stage 4: Goods Receipt 

When the shipment arrives, the warehouse team verifies it against the open PO and posts a Product Receipt in D365 through the Purchase Order Receipt and Follow-up Workspace. 

This step does two things: it triggers the first accounting entry in the procurement cycle — debit inventory or expense, credit the GR/IR clearing account, and it creates the document that three-way matching in AP depends on. Without a posted product receipt, AP has no way to confirm delivery happened. The invoice cannot be approved cleanly. 

For businesses running intercompany accounting across multiple legal entities, D365 generates the corresponding intercompany entries automatically when the product receipt posts mean removing a month-end reconciliation that is easy to get wrong outside the system. 

Stage 5: Vendor Invoice Entry and Matching 

The vendor sends the invoice. AP verifies it before payment is authorized. This is where most P2P breakdowns happen. 

Invoices in D365 are managed through the Vendor Invoice Entry Workspace. Entry is manual or automated through OCR, technology that reads the vendor's PDF and populates D365 fields without anyone keying it in. For a small AP team handling high invoice volumes, OCR is the difference between a function that scales and one that does not. 

Matching runs in two configurations. Two-way matching compares the invoice against the PO, price and quantity within tolerance. Three-way matching adds the Product Receipt, so all three documents must align before the invoice proceeds. For most Canadian mid-sized businesses, three-way matching should be the standard. D365 also blocks invoice submission on duplicate invoice numbers, mismatched totals, or incomplete accounting distributions, system-enforced, not caught manually. 

On compliance: a vendor invoice cannot support a GST/HST Input Tax Credit claim without the vendor's registration number. D365 stores this in the vendor master and flags any invoice where it is missing before posting 

Stage 6: Invoice Approval and Posting 

After matching clears, the invoice moves through a posting approval chain means AP Clerk, AP Supervisor, Controller, configured per organization. Every action is time-to-stamped and logged in D365's Audit Workbench. 

Posting generates the second accounting entry: the GR/IR clearing account is debited, reversing the goods receipt credit, and the vendor liability is credited. The payable is in the books. The Financial Period Close Workspace in D365 tracks invoice posting status as part of month-end tasks, so controllers see what is posted, what is pending, and what is stuck, without chasing the AP team for updates. 

Stage 7: Vendor Payment 

The AP team runs a payment proposal in D365, a system-generated list of invoices due to the vendor payment terms. After reviewing and any adjustments, it is processed as a payment journal. 

D365 Finance supports EFT through Canadian banking rails with file formats for RBC, TD, BMO, and Scotiabank; cheque printing directly from the system; and wire transfers for international vendors. Prepayments are also handled by vendors requiring a deposit upfront, common in construction and capital equipment. 

When payment is posted, the vendor’s liability clears. The complete transaction trail such as PR, PO, product receipt, invoice, approval, payment, is traceable inside D365. That is the documentation a CRA audit requires, and it exists as a byproduct of running the process correctly. 

Additional Capabilities Worth Knowing 

Procurement catalogues and purchasing policies in D365 define approved vendors, products, and spend thresholds by role and department, which largely stops off-contract purchasing before it starts. 

The Vendor Collaboration Portal lets vendors update their own master data, respond to RFQs, and submit invoices directly into D365, reducing inbound AP workload and vendor master errors. 

Dynamics 365 Copilot, expanded in the 2025 Release Wave 2, adds anomaly detection on vendor invoice patterns, spend analysis, and compliance automation including unified tax determination and e-invoicing support, detailed at Logan Consulting's D365 Finance 2026 release notes.