Procure-to-Pay Process Redesign on Odoo 17
An end-to-end IS consulting engagement on the Procure-to-Pay process, run on a fictional Moroccan distributor. It goes from interviews and process models to a working, tested Odoo module and a change-management plan — the full path a Consultant SI follows on an ERP project.
View the code on GitHub- Role
- IS consultant & Odoo developer
- Context
- Personal consulting case study — fictional distributor 'Atlas Distribution'
- Period
- 2026
Screenshots & diagrams
Captured from the running project. Click to view full screen.
The problem
Purchases were requested over WhatsApp, written in Excel and signed on paper by one director; bills were paid without checking what was received.
The solution
Ran a full consulting cycle — As-Is/To-Be BPMN, gap analysis, functional spec — then built an Odoo 17 module adding an approval matrix and a three-way-match control on vendor bills.
The impact
Every PO follows amount-based approval rules with an audit trail, and a bill that doesn't match the PO and the receipt can no longer be posted.
What I did
- 01
Mapped the As-Is process in BPMN 2.0 and identified 6 pain points and their root causes.
- 02
Ran a gap analysis of standard Odoo 17 vs the need, applying 'configure first, customise only where needed'.
- 03
Designed the To-Be process with 7 business rules, a RACI and segregation of duties.
- 04
Wrote the functional specification: 7 requirements, data model, security matrix, screens.
- 05
Built the p2p_approval_matrix module: approval bands per amount, approval log with lead-time KPI, three-way match blocking bill posting, finance-manager exception approval with a written reason.
- 06
Wrote a test plan of 15 scenarios with a traceability matrix — every scenario automated as an Odoo test.
- 07
Produced an ADKAR change-management plan with go-live checklist and adoption KPIs.
Key challenges
Customise as little as possible
Odoo already has a single approval threshold. The module extends that mechanism instead of replacing the purchase flow, so it stays upgrade-friendly and falls back to standard behaviour when no matrix is set.
A control people will accept
Blocking bills can frustrate accounting, so every block explains the exact issue and there is a controlled, logged exception path for the finance manager.
Results
- Complete deliverable set: scope & RACI, As-Is & gap analysis, To-Be, functional spec, test plan, change plan.
- Installable Odoo 17 module with approval matrix, approval analysis (pivot/graph) and three-way match.
- 15 automated test scenarios traced to every requirement and business rule — 15 / 15 passing on Odoo 17.
Tech stack
Skills demonstrated
Want this kind of work on your team?
Available for a 6-month PFE internship from January 2027.