Usa esta plantilla
Procure to pay touches almost everyone in a business. Someone needs something, a buyer sources it, a manager approves it, the warehouse receives it, accounts payable pays for it. When each step is done differently, the result is maverick spending, purchase orders raised after the invoice arrives, goods that can't be matched and suppliers who aren't paid on time. A procure to pay SOP template gives the whole cycle one documented procedure, from the first request to the final payment.
This free procure to pay SOP template covers the full P2P cycle in eight stages, with roles, controls, KPIs, an exception-handling table and a filled-in example you can copy. Copy the structure below, use the filled example as a guide, or generate your procure to pay SOP with AI from a recording of your own process.
What is a procure to pay SOP template?
A procure to pay SOP template is a ready-made standard operating procedure for the procure to pay (P2P) process. It sets out who does what, in what order and under which controls, from raising a purchase requisition and approving it to selecting a supplier, issuing a purchase order, receiving goods or services, matching the invoice and paying the supplier. A good procure to pay SOP template also covers the exceptions, such as urgent purchases, orders without a PO, partial deliveries and price variances, and the controls auditors expect to see.
Your procurement and finance policies set the rules, such as approval limits and preferred suppliers; the SOP shows how each team applies them, step by step. For a general SOP format you can adapt to any process, see the free SOP template.
Why does procure to pay need an SOP?
P2P controls spending. Without a defined process, purchases bypass approvals and preferred suppliers.
It crosses many teams. Requesters, procurement, approvers, receiving and AP all hand work to each other.
No PO, no match. Purchase orders raised late or not at all make invoices hard to match and pay.
Fraud and errors target P2P. Fake suppliers, duplicate invoices and changed bank details all enter through this cycle.
Auditors test P2P controls. Approvals, segregation of duties and three-way matching need documented procedures.
P2P is a common automation target. You can only automate a process that's clearly defined.
Who uses a procure to pay SOP template?
Procurement and purchasing teams who source suppliers and issue purchase orders.
Requesters and budget holders who raise and approve purchase requests.
Receiving and warehouse teams who confirm deliveries.
Accounts payable teams who match and pay invoices.
Finance controllers and CFOs who own spend controls.
Shared services, BPO and ERP implementation teams documenting P2P across entities or in a new system.
Auditors reviewing purchasing and payment controls.
Preview the procure to pay SOP template
The template opens with document control, purpose and scope, then a roles table for requesters, approvers, procurement, receiving, accounts payable, the vendor master team and treasury. Policies and reference data follow, such as approval limits, buying channels, matching rules and tolerances. The procedure covers the P2P cycle in eight stages, each with numbered steps, owners and expected results. An exception-handling table sets out what to do when a purchase, delivery or invoice doesn't follow the standard path. The template closes with controls, KPIs, records and revision history. A filled-in example shows how one company completed it. Every section is editable, so you can add your ERP's transaction names, change limits or split stages into separate SOPs.
How to customize this template in Trupeer
Step 1: Open the Templates Section
Go to the Templates section from the main navigation.
Step 2: Select and Open a Template
Click on any template you want to work with to open it.
Step 3: Expand the Template View
If needed, expand the template view to see the full layout and details clearly.
Step 4: Edit the Template
Click on Edit to start modifying the selected template.
Within the editor, you can:
Add new sections
Define or update formatting rules
Add a logo and adjust its position and related settings
Step 5: Save Your Customized Template
After making all necessary changes, click Save to store the updated template as your own.
Step 6: Preview and Fine-Tune the Template
When you want to see how your customized template looks, open the Preview.
From the preview screen, you can continue to make adjustments directly if needed, ensuring the template appears exactly as you want.
With a procure to pay SOP template you can:
Control spend: Every purchase follows the same approval and buying rules.
Raise POs before purchases: Fewer invoices arrive without a purchase order.
Match invoices first time: Clean POs and receipts make three-way matching work.
Prevent fraud and duplicate payments: Supplier checks and segregation of duties are built into the steps.
Pass audits with less effort: Show documented approvals, matching and controls.
What a procure to pay SOP template must contain
Section | What it covers |
|---|---|
Document control | SOP ID, version, owner, approver, effective and review dates |
Purpose and scope | Entities, spend categories, systems and buying channels covered |
Roles and responsibilities | Requester, budget approver, procurement, receiving, AP, vendor master team, treasury |
Policies and reference data | Approval limits, buying channels, preferred suppliers, matching rules, tolerances, payment terms |
Requisition | Raising and approving purchase requests |
Sourcing and supplier selection | Quotes, preferred suppliers and new supplier onboarding |
Purchase order | Creating, approving and sending POs |
Receipt | Recording goods received or services delivered |
Invoice processing and matching | Capturing invoices and two- or three-way matching |
Payment | Payment runs, approval and release |
Exceptions | Urgent buys, no-PO invoices, partial deliveries, variances, bank changes |
Controls, KPIs and records | Segregation of duties, metrics and documentation retained |
Free procure to pay SOP template: the structure to copy
Copy the structure below into your own document, or open it in Trupeer and customize it.
1. Document control. SOP ID: [P2P-001]. Version: [x.x]. Owner: [Procurement manager]. Approver: [Finance controller]. Effective date: [date]. Next review: [date].
2. Purpose. This SOP defines how [Company] requests, approves, buys, receives and pays for goods and services, so spending follows policy, suppliers are paid accurately and on time, and controls are applied consistently.
3. Scope. Applies to all purchases of goods and services for [entities] through [ERP or procurement system]. Excludes [purchasing card spend and employee expenses, covered by separate SOPs].
4. Roles and responsibilities.
Role | Responsibility |
|---|---|
Requester | Raises purchase requisitions with complete details |
Budget approver | Approves requisitions within their delegated limit |
Procurement | Sources suppliers, obtains quotes and issues purchase orders |
Receiving | Records goods received or confirms services delivered |
Vendor master team | Creates and changes supplier records, including bank details |
Accounts payable | Captures, matches and posts invoices; prepares payment runs |
Treasury | Approves and releases payments |
Finance controller | Owns P2P controls and approves this SOP |
5. Policies and reference data. Approval limits: [by amount]. Buying channels: [catalogue, PO, contract]. Quotes required: [above amount]. Matching rule: [three-way for goods, two-way for services]. Tolerances: [price and quantity]. Payment terms: [standard terms].
6. Procedure.
Stage 1: Raise the requisition. The requester raises a purchase requisition in [system] with item or service, quantity, estimated cost, cost centre, required date and preferred supplier if known.
Stage 2: Approve the requisition. The system routes the requisition to the budget approver whose limit covers the amount. The approver checks need and budget, then approves or rejects it.
Stage 3: Source and select the supplier. Procurement uses a catalogue or contract supplier where one exists. Otherwise, it obtains [number] quotes above [amount] and selects a supplier. New suppliers are onboarded through the vendor master procedure before any order is placed.
Stage 4: Create and send the purchase order. Procurement converts the approved requisition into a purchase order with agreed prices, terms and delivery details, and sends it to the supplier.
Stage 5: Receive goods or confirm services. Receiving records goods against the PO when they arrive, noting any shortages or damage. For services, the requester confirms delivery in [system].
Stage 6: Capture and match the invoice. AP captures the supplier invoice, checks for duplicates and matches it to the PO and receipt. Invoices within tolerance continue; others follow the exception table.
Stage 7: Approve and post. Matched invoices are posted automatically or by AP. Invoices without a PO follow the no-PO exception.
Stage 8: Pay the supplier. AP prepares the payment proposal on the scheduled run day, reviews it and sends it to treasury, which approves and releases payment.
7. Exception handling.
Exception | How to recognise it | Action | Decision owner | Time limit | Escalate to |
|---|---|---|---|---|---|
Urgent purchase | Need can't wait for the standard process | Follow the urgent purchase procedure; raise the PO the same day | Procurement | Same day | Procurement manager |
Invoice without a PO | Supplier invoice with no matching PO | Hold; requester raises a retrospective PO with approver sign-off and a reason | Budget approver | [3 working days] | Finance controller |
Partial delivery | Fewer items received than ordered | Record what arrived; keep the PO open for the rest | Receiving | Same day | Procurement |
Price or quantity variance | Invoice outside tolerance | Hold; procurement confirms with the supplier | Procurement | [2 working days] | AP lead |
New supplier requested | Supplier not in the vendor master | Start supplier onboarding; no order until approved | Procurement | [Per onboarding SOP] | Procurement manager |
Bank details differ | Invoice bank details differ from vendor master | Stop; do not pay; verify through a known supplier contact | Vendor master team | Before next payment run | Finance controller |
Not covered above | Case doesn't match any row | Stop and escalate; do not improvise | Procurement manager | [4 hours] | Finance controller |
8. Controls. Requesters can't approve their own requisitions. The person who creates suppliers can't raise POs or approve payments. Quotes are required above [amount]. Invoices are matched to PO and receipt before payment. Payment runs need two approvers.
9. KPIs. Requisition to PO cycle time, share of spend on PO, share of spend with preferred suppliers, retrospective POs, first-pass match rate, invoice cycle time and on-time payment rate.
10. Records. Requisitions, approvals, quotes, POs, receipts, invoices and payment approvals, retained for [period].
11. Revision history. Version, date, change summary, author and approver.
Procure to pay SOP example: filled-in
Here's how a mid-size manufacturer might fill in the key parts of the template. All names, limits and timings are illustrative.
Scope. All purchases of goods and services for the UK and Germany entities through the company's ERP. Excludes purchasing cards under a set amount and employee expenses.
Approval limits.
Requisition value | Approver |
|---|---|
Up to the team limit | Team manager |
Up to the department limit | Department head |
Up to the finance limit | Finance controller |
Above the finance limit | CFO |
Policies. Catalogue first for office supplies and IT accessories. Three quotes for any non-catalogue purchase above the quote threshold. Three-way match for goods, two-way for services. Payment runs every Tuesday and Friday.
Filled exception example. A supplier sends an invoice for maintenance work with no PO. AP puts it on hold and emails the requester. The requester raises a retrospective PO with a reason, the department head approves it within three working days, and the case is logged. Because retrospective POs are tracked as a KPI, the procurement manager reviews the log monthly and contacts teams with repeat cases.
KPI targets the team set. Most spend on PO, most catalogue spend with preferred suppliers, retrospective POs falling each quarter and payments on time.
Use the example to see the level of detail needed, then replace it with your own limits, channels and timings.
Which procure to pay procedures need their own SOP?
P2P procedure | What it covers |
|---|---|
Purchase requisitions and approvals | Raising, routing and approving requests |
Sourcing and quotes | When quotes are needed and how suppliers are selected |
Supplier onboarding | New supplier checks, approval and vendor master setup |
Purchase orders | Creating, changing and closing POs |
Goods receipt and service confirmation | Recording deliveries and confirming services |
Invoice processing | Capture, matching and exceptions |
Payment runs | Proposal, review, approval and release |
Purchasing cards | Card limits, approval and reconciliation |
For the invoice and payment part in more detail, use the accounts payable SOP template.
For a visual walkthrough of the cycle, see the procure to pay process flow.
Procure to pay controls to build into the SOP
Control | Why it matters |
|---|---|
Approval limits | Keeps spending within delegated authority |
Segregation of duties | Stops one person from creating a supplier, ordering and paying |
Quotes and preferred suppliers | Ensures value for money and approved suppliers |
PO before purchase | Gives control over commitments before money is spent |
Three-way matching | Pays only for what was ordered and received |
Supplier onboarding checks | Reduces the risk of fake or high-risk suppliers |
Bank detail verification | Protects against payment fraud |
Procure to pay SOP KPIs
Requisition to PO cycle time: how quickly approved needs become orders.
Spend on PO: share of spend covered by a purchase order.
Preferred supplier spend: share of spend with contracted or catalogue suppliers.
Retrospective POs: POs raised after the invoice arrived.
First-pass match rate: invoices matched without intervention.
On-time payment rate: payments made by the due date.
Set your own targets and baseline them before you change the process.
How to create your procure to pay SOP from recordings
Choose a stage, such as requisition approval, PO creation or goods receipt.
Record the person who does it best in your ERP or procurement system, narrating each step, check and decision, including at least one exception.
Generate the SOP and video with Trupeer, then review the steps and add your limits, channels and tolerances.
Fill in the exception table from the recordings, your hold reasons and audit findings.
Get approval from the procurement manager and finance controller.
Publish and train, linking each step to its video, and update the SOP whenever the system or policy changes; see SOP version control.
Formats for a procure to pay SOP
Step-by-step with an exception table suits most P2P procedures, such as requisitions, POs and invoice processing. This is the format the template above uses.
Swimlane flowchart suits the end-to-end view, showing how a purchase passes between requester, approver, procurement, receiving and AP.
Approval matrix suits approval limits, kept as a reference table the SOP links to.
Checklist suits supplier onboarding and payment run reviews.
Best practices for procure to pay SOPs
Write the SOP around handoffs, since most delays happen between teams.
Make "no PO, no pay" explicit, with a clear retrospective PO exception.
Keep limits and tolerances in one reference table.
Use your system's real screen and transaction names.
Pair every SOP with short videos for requesters, who use the process least often.
Review the SOP after every system change, policy change and audit.
Common mistakes to avoid
Writing the SOP for procurement only, when requesters and receiving drive most issues.
Leaving out exceptions, so urgent buys and no-PO invoices are handled inconsistently.
Weak supplier onboarding, which lets unapproved or fake suppliers in.
Same person creating suppliers and approving payments.
Never updating the SOP after a system or policy change.
Procure to pay SOP checklist
Document control is complete, with owner and review date.
Roles cover requesters, approvers, procurement, receiving, AP, the vendor master team and treasury.
Approval limits, buying channels, quote rules, matching rules and tolerances are documented.
Every stage from requisition to payment has numbered steps.
The exception table covers urgent buys, no-PO invoices, partial deliveries, variances, new suppliers and bank changes.
Segregation of duties and approvals are defined.
KPIs and records are specified.
Videos are linked for key steps, especially for requesters.
How Trupeer helps you build and maintain your procure to pay SOP
P2P SOP challenge | How Trupeer helps |
|---|---|
P2P knowledge is spread across many teams | Record each team doing its part, and Trupeer's SOP creator turns each recording into a step-by-step SOP and video |
Requesters rarely use the system and forget the steps | Short videos and guides show exactly how to raise a requisition or confirm a receipt |
Teams in different countries need their own language | Translate SOPs and videos from one source into 65+ languages |
The ERP or procurement system changes | Update videos by editing the script, and replace a single step instead of re-recording |
Writing SOPs from scratch takes weeks | Generate a draft SOP with AI from a recording, then review and approve it |
Genpact used this recording-first approach for a company-wide Workday rollout, turning recorded process sessions into more than 500 training collaterals across 20 workstreams in five languages, for 140,000 employees in 40 countries, in 3 months instead of 12. Read the Genpact customer story.
Download the free procure to pay SOP template
Open the template in Trupeer, apply your brand kit, add your limits, channels and system steps, and share it with every team in the P2P process. Get the free procure to pay SOP template.
Related templates
Frequently Asked Questions
What is a procure to pay SOP template?
It's a ready-made standard operating procedure for the P2P process, covering roles, policies, requisitions, approvals, sourcing, purchase orders, receipts, invoice matching, payment, exceptions and controls.
What are the steps in the procure to pay process?
Raise a requisition, approve it, source and select the supplier, create and send the purchase order, receive the goods or confirm the service, capture and match the invoice, approve and post it, and pay the supplier.
What should a procure to pay SOP include?
Document control, purpose and scope, roles, policies and reference data, step-by-step procedures for each P2P stage, an exception-handling table, controls, KPIs, records and revision history.
What's the difference between procure to pay and accounts payable?
Accounts payable covers invoice processing and payment. Procure to pay is the wider end-to-end process, starting with the requisition and including approvals, sourcing, purchase orders and receipt.
How do you handle exceptions in a P2P SOP?
Use an exception table that lists each exception, how to recognise it, the action, the decision owner, a time limit and where to escalate, plus a catch-all row for anything not listed.
What KPIs measure procure to pay performance?
Common KPIs include requisition to PO cycle time, spend on PO, preferred supplier spend, retrospective POs, first-pass match rate and on-time payment rate.
Can I generate a procure to pay SOP with AI?
Yes. Record your P2P process and use Trupeer's AI SOP generator to create a draft SOP and video, then review it against this template and approve it.
Is there a procure to pay SOP template in Word?
Yes. Word suits the P2P SOP because it combines tables, such as roles, approval limits and exceptions, with step-by-step procedures. Open the template in Trupeer, customize it and export it in the format you need.
Is there a procure to pay SOP template in Excel?
The SOP itself works best as a document, but many teams keep the approval matrix, exception log and KPIs in Excel alongside it.
Is there a procure to pay SOP template PDF?
Yes. Export the customized SOP as a PDF for read-only distribution, and keep the editable version as the master.
Is the procure to pay SOP template free?
Yes. Sign up free to open the template in Trupeer, customize it and export it.
How often should a P2P SOP be reviewed?
At least annually, and whenever your ERP or procurement system, approval limits, buying channels or payment processes change, or after an audit finding.
Understand how work happens.
Carry it into your next transition.
Start Free Trial
Book a Demo
Características
competidores
