Procure to pay is the end to end cycle that runs from identifying a need to paying the supplier invoice, covering requisition, order, receipt, invoice and payment.
Procure to pay, usually shortened to P2P, is the complete business cycle that starts when someone in the company identifies a need and ends when the supplier has been paid and the transaction is closed in the books. The standard steps are requisition, approval, purchase order, goods or service receipt, invoice receipt, matching, posting and payment. It deliberately spans two departments that are usually measured separately, procurement on the front half and accounts payable on the back half, which is why the handover between them is where most of the trouble lives.
The cycle matters because every break between those steps turns into cash or risk. An order placed without a purchase order leaves accounts payable holding an invoice nobody expected and nothing to match it against, so it sits in a query pile while the payment term runs down. A receipt that is never posted means the goods are in the warehouse but the liability is not in the ledger, so the period closes understated. Late approvals push invoices past the early payment discount window and then past the due date, which costs money on one side and supplier goodwill on the other.
Business Central covers the transactional spine in standard: purchase orders, warehouse or direct receipts, purchase invoices, the ability to pull posted receipt lines into an invoice with Get Receipt Lines, vendor ledger entries, and the payment journal with Suggest Vendor Payments and SEPA payment files. The native approval workflow engine routes purchase documents to approvers defined in Approval User Setup, with amount limits per approver. What is thinner out of the box is the front end and the exception handling: there is no requisition document that a non buyer can raise, no supplier portal, no contract repository, and no queue that lists every blocked invoice with its reason. Teams close those gaps with add ons or with process discipline, and the dedicated guide on procurement automation covers what that looks like in practice.
A maintenance manager needs replacement pumps and raises the need on 3 March. A buyer issues purchase order PO-104217 to Alpine Technik for 6 units at CHF 780, total CHF 4,680, on payment terms of 30 days net. The pumps arrive on 17 March and the receipt is posted the same day. The invoice is dated 18 March, matches the order and the receipt, and posts with a due date of 17 April. From need to cash out the cycle is 45 days: 14 of supplier lead time, one day between receipt and invoice date, and the 30 day payment term the company chose to take.
The recurring failure points are invoices with no purchase order, receipts posted days after the goods physically arrived, and approvers on holiday with no substitute configured. Teams track four numbers rather than one: the share of spend that went through a purchase order, the share of invoices that clear matching without human intervention, the average days from invoice receipt to posting, and the count of invoices currently blocked. A single average cycle time hides all four and tells you nothing about where to intervene.
content[5] = (no sixth element; the array ends after the five real paragraphs, the last being "The recurring failure points are invoices with no purchase order, receipts posted days after the goods physically arrived, and approvers on holiday with no substitute configured. Teams track four numbers rather than one: the share of spend that went through a purchase order, the share of invoices that clear matching without human intervention, the average days from invoice receipt to posting, and the count of invoices currently blocked. A single average cycle time hides all four and tells you nothing about where to intervene." The FAQ block below it comes from the `faq` array, so nothing replaces the placeholder.)
No. Source to pay is wider: it adds the upstream sourcing work, supplier discovery, tendering, negotiation and contract award, in front of the procure to pay cycle. Procure to pay starts once the supplier and the price are already agreed.
Not necessarily. BC handles orders, receipts, invoices and payments natively, so the real question is whether you need requisitioning, supplier self service and exception management on top. Teams with a handful of buyers often run the whole cycle in BC alone.
Zentriq's AI tools automate many of the manual processes around procure to pay (p2p) in Business Central. Learn about the Zentriq Agent or try Zentriq PunchOut to see how AI simplifies procurement in BC.