Introduction
Procurement is rarely just a purchasing department activity.
A business may identify a material requirement in one department, request approval, source suppliers, negotiate pricing, create a purchase order, receive the goods, verify the vendor invoice and finally process payment through finance. Each step involves different people, documents, controls and systems.
When these activities operate independently, procurement can become slow and difficult to monitor. Purchase requests may remain in email inboxes, buyers may not have reliable demand information, warehouse teams may receive goods without knowing the expected quantities and finance may spend significant time reconciling invoices against purchase transactions.
A well-designed Odoo procure-to-pay process connects these activities into a coordinated workflow.
The objective is not simply to automate purchase orders. It is to establish a controlled process that connects demand, purchasing, inventory and accounting while maintaining visibility from the original requirement through supplier payment.
This guide explains how to design a practical procure-to-pay workflow in Odoo, including the roles, controls, exceptions and KPIs that organizations should consider.
What Is the Procure-to-Pay Process?
| P2P Stage | Main Activity | Primary Owner | Odoo Area | Key Output |
|---|---|---|---|---|
| Demand Identification | Identify purchasing requirement | Department / Planning | Inventory / Manufacturing | Purchase demand |
| Requisition | Submit purchase request | Requester | Purchase | Purchase requisition |
| Approval | Review and authorize spending | Manager | Purchase | Approved request |
| Supplier Selection | Evaluate suppliers | Procurement | Purchase | Selected supplier |
| RFQ | Request supplier quotation | Procurement | Purchase | Supplier quotation |
| Purchase Order | Confirm supplier commitment | Procurement | Purchase | Confirmed PO |
| Goods Receipt | Receive and verify goods | Warehouse | Inventory | Receipt |
| Vendor Invoice | Record supplier bill | Finance | Accounting | Vendor bill |
| Invoice Verification | Match order, receipt and invoice | Finance | Accounting | Validated invoice |
| Payment | Pay supplier | Finance | Accounting | Vendor payment |
| Supplier Review | Evaluate supplier performance | Procurement | Purchase / Reporting | Supplier KPI data |
Procure-to-pay, often abbreviated as P2P, covers the process from identifying a purchasing requirement through paying the supplier.
A typical process includes:
- Demand identification
- Purchase requisition
- Approval
- Supplier selection
- Request for quotation
- Purchase order
- Goods or service receipt
- Vendor invoice
- Invoice verification
- Payment
- Supplier performance evaluation
The exact process differs between organizations.
A manufacturing company may generate procurement requirements from production planning.
A distributor may replenish inventory based on stock levels.
A service company may purchase consulting or operational services.
The Odoo workflow should therefore reflect the organization's actual procurement model.
Why Procure-to-Pay Integration Matters
A disconnected procurement process creates several risks.
Financial Risk
Invoices may be paid without sufficient validation.
Inventory Risk
Received quantities may not match ordered quantities.
Purchasing Risk
Employees may buy outside approved supplier or pricing arrangements.
Operational Risk
Materials may arrive late and affect production or customer fulfillment.
Visibility Risk
Management may not know where a purchase is stuck.
A connected P2P process gives different teams visibility into the same transaction.
Step 1 : Identify the Demand
Procurement should begin with a legitimate business requirement.
Demand can originate from:
- Inventory replenishment
- Manufacturing requirements
- Sales commitments
- Project requirements
- Maintenance
- Internal departments
- Minimum stock rules
- Forecast demand
The first question should be:
Why does the organization need to purchase this item or service?
That establishes the business context for the transaction.
Inventory-Driven Procurement
For stocked products, replenishment rules can help generate procurement requirements.
For example, when available stock approaches a defined threshold, the system can identify a replenishment requirement.
However, organizations should not blindly automate every purchase.
Consider:
- Current stock
- Incoming quantities
- Open sales orders
- Forecast demand
- Supplier lead time
- Minimum order quantity
- Safety stock
The objective is to purchase according to actual demand rather than simply reacting to one inventory number.
Manufacturing-Driven Procurement
Manufacturing businesses may have a more structured demand chain.
A production requirement can create demand for components or raw materials.
The procurement process should therefore consider:
- Bill of materials
- Manufacturing schedule
- Component availability
- Supplier lead time
- Existing purchase orders
- Expected receipts
This connects purchasing decisions to production planning.
Step 2 : Create a Purchase Requisition
A requisition establishes that a department or employee needs something.
The requisition should capture relevant information such as:
- Product or service
- Quantity
- Required date
- Requesting department
- Warehouse or location
- Estimated cost
- Business justification
- Preferred supplier, where appropriate
Not every organization needs a formal requisition for every purchase.
The control should match the organization's purchasing policy.
Different Purchase Types Need Different Controls
| Purchase Type | Example | Recommended Control | Typical Approval |
|---|---|---|---|
| Stock Purchase | Raw materials, finished goods | Quantity and supplier validation | Department Manager |
| Service Purchase | Consulting, maintenance | Service confirmation | Department Manager |
| Capital Purchase | Machinery, equipment | Budget and CAPEX approval | Finance / Management |
| Recurring Purchase | Software, subscriptions | Contract and renewal control | Department Manager |
| Emergency Purchase | Urgent material | Exception approval | Manager / Management |
A procurement workflow may distinguish between:
Stock Purchases
Products entering inventory.
Service Purchases
Consulting, maintenance or professional services.
Capital Purchases
Assets requiring additional financial approval.
Recurring Purchases
Regularly purchased services or supplies.
Emergency Purchases
Exceptions requiring expedited handling.
Each category may require different approval rules.
Step 3 : Apply Purchase Approvals
| Purchase Value | Approval Level | Additional Control | Example |
|---|---|---|---|
| Low Value | Department Manager | Budget availability | Office supplies |
| Medium Value | Department Manager + Procurement | Supplier validation | Production materials |
| High Value | Finance / Senior Management | Budget and commercial review | Major equipment |
| Capital Purchase | Finance + Management | CAPEX authorization | Machinery |
| Exceptional Purchase | Authorized Manager | Exception justification | Emergency procurement |
Approval should depend on business risk.
For example:
- Low-value purchases may require department approval.
- Medium-value purchases may require manager approval.
- High-value purchases may require finance or executive approval.
- Capital purchases may require a separate authorization process.
The exact thresholds should be defined by company policy.
Avoid Approval for Approval's Sake
Too many approval layers can make procurement unnecessarily slow.
The objective is to control risk, not create administrative friction.
For each approval, ask:
What risk is this approval intended to control?
Possible answers include:
- Spending authority
- Budget availability
- Supplier risk
- Compliance
- Capital expenditure
- Contractual commitment
If an approval has no clear purpose, it may be unnecessary.
Step 4 : Supplier Selection
Once the requirement is approved, purchasing determines the appropriate supplier.
Selection may consider:
- Price
- Quality
- Lead time
- Payment terms
- Minimum order quantity
- Delivery performance
- Historical reliability
- Contract terms
Odoo can maintain supplier information and purchasing history to support these decisions.
The objective is not always to choose the lowest price.
A cheaper supplier with poor delivery performance may create greater total cost.
Supplier Performance Should Be Visible
Procurement teams should track supplier performance using measurable indicators.
Potential KPIs include:
- On-time delivery
- Quantity accuracy
- Defect rate
- Price variance
- Lead-time reliability
- Invoice accuracy
This transforms supplier management from subjective judgment into measurable performance management.
Step 5 : Request for Quotation
For purchases requiring competitive sourcing, buyers may request quotations from suppliers.
The organization should establish when competitive quotation is required.
For example:
- Purchases above a threshold
- New suppliers
- Strategic materials
- High-value services
The quotation process can capture:
- Supplier
- Products
- Quantities
- Prices
- Delivery dates
- Payment terms
Comparing supplier responses can support better purchasing decisions.
Step 6 : Create the Purchase Order
Once the supplier has been selected, the purchase order formalizes the commitment.
A purchase order should provide enough information to support downstream operations.
Typical information includes:
- Supplier
- Products/services
- Quantities
- Prices
- Taxes
- Delivery location
- Expected delivery date
- Payment terms
- Incoterms where applicable
- Reference information
The purchase order becomes an important reference for both warehouse and finance.
Purchase Order Controls
Depending on the organization, controls may include:
- Approval before confirmation
- Price tolerance
- Supplier restrictions
- Budget checks
- Purchase limits
- Required documentation
These controls should be designed according to business risk.
Step 7 : Receive the Goods
Once the supplier delivers the goods, warehouse personnel should verify the receipt against the purchase order.
They may check:
- Product
- Quantity
- Condition
- Packaging
- Lot or serial number
- Expiry date
- Delivery documentation
This is where purchasing and inventory become directly connected.
Partial Receipts Are Important
Real-world suppliers do not always deliver the exact quantity ordered.
For example:
Ordered: 1,000 units
Delivered: 850 units
The remaining 150 units may be delivered later.
The ERP should preserve visibility into:
- Ordered quantity
- Received quantity
- Remaining quantity
- Expected delivery
This prevents premature closure of purchase orders.
Quality Inspection
For regulated or quality-sensitive businesses, receiving may include inspection.
Examples include:
- Raw materials
- Pharmaceuticals
- Food products
- Industrial components
The workflow may require:
Receipt → Quality Check → Accept / Reject
Rejected goods should have a defined disposition process.
Step 8 : Record the Vendor Invoice
After goods or services are received, the supplier invoice enters the accounting workflow.
Finance needs to determine whether:
- Supplier is correct
- Invoice number is valid
- Quantities are reasonable
- Prices match
- Taxes are correct
- Purchase order exists
- Receipt exists
This is where invoice matching becomes important.
Three-Way Matching
| Document | Key Question | Example Data | Validation |
|---|---|---|---|
| Purchase Order | What was ordered? | 500 units @ $100 | Order quantity and price |
| Goods Receipt | What was received? | 500 units | Received quantity |
| Vendor Invoice | What is being billed? | 500 units @ $100 | Invoice quantity and price |
| Payment | What was paid? | $50,000 | Approved invoice |
A common procurement control is three-way matching.
The three documents are:
Purchase Order
What was ordered?
Receipt
What was received?
Vendor Invoice
What is being billed?
The organization compares these records before approving payment.
For example:
Ordered: 500 units
Received: 500 units
Invoiced: 500 units
This is straightforward.
But if:
Ordered: 500
Received: 450
Invoiced: 500
the discrepancy should be investigated.
Price Variances
Quantity is not the only possible mismatch.
Suppose:
Purchase Order: $100/unit
Invoice: $115/unit
The system or finance process should identify the variance according to the organization's tolerance rules.
Possible actions include:
- Automatic acceptance within tolerance
- Manual approval
- Invoice correction
- Supplier clarification
Step 9 : Handle Invoice Exceptions
Exceptions are inevitable.
Examples include:
- Invoice received before goods
- Partial receipt
- Price mismatch
- Duplicate invoice
- Incorrect tax
- Wrong supplier
- Missing purchase order
- Damaged goods
The process should define what happens in each situation.
An exception should not simply disappear into someone's inbox.
Duplicate Invoice Prevention
Duplicate vendor invoices can create direct financial loss.
The organization should consider controls around:
- Vendor
- Invoice number
- Invoice date
- Amount
- Purchase order
- Existing invoice records
Where possible, duplicate detection should be supported through system controls and accounting review.
Step 10 : Approve the Invoice
Once the invoice has passed the required checks, it can move toward payment.
Depending on the organization's controls, invoice approval may depend on:
- Purchase order approval
- Receipt confirmation
- Matching status
- Budget
- Department
- Amount
- Vendor risk
The approval structure should be aligned with financial governance.
Step 11 : Process the Vendor Payment
The final stage is payment.
Finance should consider:
- Payment due date
- Payment terms
- Cash availability
- Payment method
- Bank information
- Payment approval
Payment should reference the underlying accounting transaction.
This provides a complete financial trail from purchase request through settlement.
Procurement and Accounting Must Share the Same Transaction Context
One of the major benefits of an integrated ERP is that purchasing and accounting can work from connected records.
The organization can move from:
Purchase Order
to
Receipt
to
Vendor Bill
to
Payment
without relying on disconnected spreadsheets or manual reconciliation between systems.
The exact accounting configuration depends on the organization's financial policies and Odoo setup.
Roles and Responsibilities
A successful P2P process should clearly define ownership.
| Activity | Procurement | Warehouse | Finance | Requester | Manager |
|---|---|---|---|---|---|
| Create request | Support | — | — | Own | — |
| Approve request | — | — | — | — | Own |
| Source supplier | Own | — | Support | — | — |
| Create PO | Own | — | Review | — | Approve where required |
| Receive goods | — | Own | — | Support | — |
| Inspect goods | Support | Own | — | — | — |
| Verify invoice | Support | Support | Own | — | — |
| Approve payment | — | — | Own | — | As required |
| Supplier review | Own | Support | Support | — | Review |
The exact responsibility model should reflect organizational structure.
Procurement Controls
A mature Odoo P2P process should consider controls such as:
Approval Authority
Who can approve spending?
Segregation of Duties
Can the same person request, approve, receive and pay?
Supplier Controls
Who can create or modify suppliers?
Price Controls
What variance is acceptable?
Quantity Controls
What receipt variance is permitted?
Invoice Controls
How are duplicates identified?
Payment Controls
Who authorizes payment?
These controls reduce operational and financial risk.
Exception Management
A strong P2P process should define exception paths.
Scenario 1 : Quantity Shortage
Received quantity is lower than ordered.
Action: Keep remaining quantity open or investigate.
Scenario 2 : Over-Delivery
Supplier delivers more than ordered.
Action: Apply defined tolerance or require approval.
Scenario 3 : Price Difference
Invoice price differs from purchase order.
Action: Route for review based on tolerance.
Scenario 4 : No Purchase Order
Invoice arrives without an approved purchase transaction.
Action: Route through an exception process.
Scenario 5 : Damaged Goods
Warehouse rejects part of the delivery.
Action: Record the discrepancy and manage replacement or credit.
Scenario 6 : Duplicate Invoice
Potential duplicate detected.
Action: Hold payment pending validation.
KPIs for Procure-to-Pay
The P2P process should be measured end-to-end.
Purchase Cycle Time
Time from approved requirement to purchase order.
Supplier Lead Time
Time between order placement and receipt.
On-Time Delivery Rate
Percentage of supplier deliveries received on schedule.
Purchase Price Variance
Difference between expected and actual purchase cost.
Invoice Exception Rate
Percentage of invoices requiring manual intervention.
First-Time Match Rate
Percentage of invoices that pass matching without exception.
Invoice Processing Time
Time from invoice receipt to approval.
Payment Cycle Time
Time from invoice approval to payment.
Spend Under Management
Percentage of organizational spend processed through controlled procurement.
These KPIs help identify bottlenecks.
Example: A Manufacturing P2P Workflow
Consider a manufacturer that needs raw material.
Demand
Production planning identifies a requirement.
Requisition
The purchasing requirement is generated.
Approval
The appropriate manager approves the purchase.
Sourcing
Procurement selects an approved supplier.
Purchase Order
The order is confirmed.
Receipt
Warehouse receives the raw material.
Quality
Required inspection is completed.
Invoice
Finance receives the supplier bill.
Matching
Purchase order, receipt and invoice are compared.
Payment
Approved invoice is scheduled for payment.
Supplier Review
Delivery and quality performance are recorded.
This creates traceability across the entire process.
Barcode and Warehouse Integration
For inventory-intensive organizations, warehouse execution can be improved through barcode-supported processes.
Barcode workflows can help users:
- Identify products
- Process receipts
- Record quantities
- Manage locations
- Track lots or serial numbers
- Reduce manual entry
The objective is not simply to introduce barcode scanning.
The process should determine:
Where does scanning create meaningful operational value?
Purchase and Inventory Data Must Be Consistent
Product configuration affects procurement.
Important product attributes can include:
- Units of measure
- Vendor information
- Lead time
- Purchase price
- Routes
- Reordering rules
- Product type
- Tracking requirements
Poor product master data can produce incorrect procurement recommendations.
Master-data governance should therefore be part of the P2P strategy.
Procure-to-Pay and Automation
Automation opportunities can exist throughout the process.
Examples include:
- Replenishment triggers
- Purchase order generation
- Approval routing
- Invoice matching
- Exception alerts
- Scheduled activities
- Payment reminders
Automation should focus on repetitive, predictable tasks.
Human review should remain where business judgment or risk assessment is required.
AI Opportunities in P2P
AI can potentially assist with:
- Supplier classification
- Invoice data extraction
- Anomaly detection
- Spend analysis
- Supplier performance analysis
- Demand forecasting
- Exception prioritization
For example, AI could identify an invoice that appears unusual because its amount is significantly different from historical supplier behavior.
The system could then flag the transaction for human review.
AI Should Complement Procurement Controls
AI should not bypass financial governance.
For AI-assisted workflows, define:
- Data sources
- Decision boundaries
- Human approval points
- Auditability
- Error handling
- Performance measurement
The objective is not to make procurement completely autonomous.
It is to reduce repetitive work while improving decision quality.
Common Procure-to-Pay Mistakes
1. Automating a Poor Process
Automation can make a bad workflow faster without making it better.
2. No Requisition Governance
Employees can commit spend without appropriate approval.
3. Weak Supplier Data
Incorrect supplier information creates downstream problems.
4. Ignoring Partial Receipts
Real deliveries rarely match every purchase order perfectly.
5. No Invoice Matching
Finance may pay invoices without sufficient verification.
6. Too Many Manual Steps
Excessive manual entry increases errors.
7. No Exception Workflow
Problems become email conversations rather than managed ERP events.
8. Measuring Only Purchase Price
Low price does not guarantee good supplier performance.
How BrowseInfo Can Support Odoo Supply Chain Transformation
BrowseInfo can support organizations across procurement and supply-chain workflows, including:
- Odoo Purchase implementation
- Odoo Inventory implementation
- Warehouse management
- Barcode workflows
- Supply-chain process design
- Procurement automation
- Vendor management
- Data migration
- Third-party integrations
- Manufacturing workflows
- Accounting integration
- Workflow automation
- AI-enabled ERP workflows
- Multi-company implementation
- Odoo upgrades
- Testing and UAT
- Post-go-live support
The appropriate implementation approach depends on procurement complexity, inventory structure, supplier network, accounting requirements, integrations and business controls.
A supply-chain workflow assessment can help identify bottlenecks and define the appropriate Odoo process before implementation.
Procure-to-Pay Implementation Checklist
Before implementing the workflow, confirm:
Demand
- Demand sources identified
- Replenishment rules reviewed
- Production requirements considered
Requisition
- Request process defined
- Required fields established
- Business justification identified where necessary
Approval
- Approval thresholds defined
- Approvers assigned
- Exceptions documented
Purchasing
- Supplier-selection process defined
- RFQ requirements established
- Purchase-order controls defined
Inventory
- Receipt process documented
- Partial receipts supported
- Quality requirements identified
- Barcode requirements evaluated
Accounting
- Vendor-bill process defined
- Matching rules established
- Invoice exceptions documented
- Payment approval defined
Supplier Management
- Supplier KPIs identified
- Delivery performance measured
- Quality performance measured
Reporting
- P2P KPIs defined
- Exception reporting established
- Spend visibility established
Automation
- Automation opportunities identified
- AI use cases evaluated
- Human approval points retained
Executive Questions Before Automating P2P
Management should be able to answer:
- Where does purchasing demand originate?
- Who can request purchases?
- Who can approve them?
- How are suppliers selected?
- Which purchases require competitive quotes?
- How are goods and services verified?
- How are invoices matched?
- How are exceptions handled?
- Who authorizes payment?
- Which KPIs determine procurement performance?
If these questions are unclear, automation should not be the first priority.
Frequently Asked Questions
1. What is procure-to-pay in Odoo?
Procure-to-pay is the end-to-end purchasing process covering demand, requisition, approval, supplier selection, purchase order, receipt, vendor invoice, verification and payment.
2. Why is three-way matching important?
Three-way matching compares the purchase order, receipt and vendor invoice to identify quantity or pricing discrepancies before payment.
3. Can Odoo automate purchase approvals?
Odoo can support purchasing workflows and approval processes, with the exact implementation depending on business rules, configuration and any required customization.
4. How should partial deliveries be handled?
The process should preserve visibility into ordered, received and remaining quantities rather than treating the purchase as completely received after the first delivery.
5. Should every purchase require approval?
Not necessarily. Approval requirements should be based on factors such as spending thresholds, purchase categories, risk and company policy.
6. How can procurement KPIs be measured?
Useful metrics include purchase cycle time, supplier lead time, on-time delivery, purchase price variance, invoice exception rate, first-time match rate and invoice processing time.
7. Can AI be used in procure-to-pay?
Yes. Potential applications include invoice extraction, anomaly detection, supplier analysis and demand forecasting. AI should operate within defined controls and human-review processes.
8. How can I improve my existing procure-to-pay process?
Start by mapping the current process, identifying manual steps and exceptions, defining approval and matching controls, establishing KPIs and then determining which Odoo capabilities can address the identified problems.
Conclusion
A well-designed procure-to-pay process in Odoo connects purchasing, inventory and finance around one controlled business workflow. From the initial demand signal through requisition, approval, supplier selection, purchase order, receipt, invoice verification and payment, each stage should have a clear owner, appropriate controls and measurable outcomes.
The greatest value does not come from simply automating purchase orders. It comes from creating end-to-end visibility and control. Organizations should know why something is being purchased, who approved it, what was ordered, what was received, what was invoiced, what exceptions occurred and when the supplier was paid. That traceability can reduce manual work while strengthening procurement and financial governance.
Before automating the process, map the current procure-to-pay workflow and identify its bottlenecks, exceptions, data dependencies and KPIs. If your organization wants to connect purchasing, warehouse operations and finance through a more controlled Odoo workflow, a supply-chain workflow assessment can help define the right process, automation opportunities and implementation priorities.
