Manual approval processes cost organizations 3-5 hours per week per manager in routing, chasing, and tracking approvals, according to Gartner research.
Manual approval processes cost organizations 3-5 hours per week per manager in routing, chasing, and tracking approvals, according to Gartner research. The hidden cost is worse — delayed approvals slow down procurement by an average of 4.2 days, block employee expense reimbursements for 2-3 weeks, and create bottlenecks that ripple through operations. Odoo 19 Enterprise Approvals module digitizes the entire approval lifecycle — request submission, routing, multi-level review, delegation, deadline enforcement, and audit trail — reducing average approval cycle time from days to hours. Organizations running structured approval workflows in Odoo report 70% faster approval completion and near-zero lost or forgotten requests.
This guide covers everything from configuring basic approval workflows to building sophisticated multi-level hierarchies with conditional routing, delegation chains, and mobile-first approval experiences.
Key Takeaways
- Design approval categories that match your business processes (purchase, expense, time-off, capital, etc.)
- Build multi-level approval hierarchies with minimum approver requirements and sequential/parallel routing
- Configure delegation rules so approvals never stall when approvers are unavailable
- Set deadline enforcement with automated escalation when approvals are overdue
- Enable mobile approvals for managers who approve on-the-go
- Create custom approval categories for any business process unique to your organization
- Build approval analytics dashboards for cycle time, bottleneck identification, and compliance
- Integrate Approvals with Purchase, Expense, Time Off, and custom modules
Approval Category Design
Built-In Categories
Odoo 19 includes several pre-configured approval categories:
| Category | Default Approver | Typical Use |
|---|---|---|
| Purchase Request | Department Manager | Non-PO purchases (supplies, services) |
| Expense Report | Direct Manager | Employee expense reimbursement |
| Time Off | Team Lead | Leave requests (integrated with Time Off) |
| Business Trip | Department Head | Travel authorization |
| Equipment Request | IT Manager | Hardware/software procurement |
Creating Custom Categories
Navigate to Approvals > Configuration > Approval Types to create categories for any business process:
| Custom Category | Approver(s) | Business Purpose |
|---|---|---|
| Capital Expenditure | CFO + CEO | Large asset purchases |
| Contract Review | Legal + Department Head | New vendor/client contracts |
| Hiring Request | HR Director + VP | New position authorization |
| Price Exception | Sales VP | Discounts above standard authority |
| Policy Change | Department Head + HR | Operational policy modifications |
| Marketing Campaign | Marketing Director | Campaign budget authorization |
| Office Access | Facilities Manager | Building access requests |
| Data Access | IT Security + Manager | Sensitive system access requests |
Category Configuration
Each approval type has detailed configuration options:
Request form fields: Define which fields appear on the request form. Standard fields include: description, amount, date needed, urgency, and attachments. Add custom fields for category-specific data — a capital expenditure request might need "Expected ROI," "Payback Period," and "Budget Line."
Approval rules: Set the minimum number of approvals required and who can approve. Options include: specific users, all managers in a department, users with a specific role, or the requester's direct manager (dynamic routing).
Document requirements: Specify which documents must be attached before submission. A purchase request might require a vendor quote. An expense report requires receipts. A hiring request requires a job description. Missing documents prevent submission, ensuring complete requests arrive for review.
Sequence: Set the display order for approval types in the request creation menu. Put the most commonly used categories first.
Multi-Level Approval Hierarchies
Sequential Approval Chains
Configure approvals that route through multiple levels in sequence:
Employee Submits → Direct Manager (Level 1) → Department Head (Level 2) → CFO (Level 3)
At each level, the approver can: Approve (routes to next level), Refuse (returns to requester with reason), or Request Changes (returns for modification without refusing).
Parallel Approvals
For requests requiring sign-off from multiple independent parties:
Employee Submits →
├── Legal Review (parallel)
├── Finance Review (parallel)
└── Department Approval (parallel)
All three approved → Request Approved
Configure parallel approvals by adding multiple approver rules at the same level with "AND" logic — all must approve for the request to proceed. Alternatively, use "OR" logic where any one of the designated approvers can approve.
Conditional Routing
Route approvals based on request attributes:
| Condition | Routing |
|---|---|
| Amount < $1,000 | Direct Manager only |
| Amount $1,000-$10,000 | Direct Manager → Department Head |
| Amount $10,000-$50,000 | Direct Manager → Department Head → VP |
| Amount > $50,000 | Direct Manager → Department Head → VP → CFO |
| Urgency = "Critical" | Skip to Department Head (expedited) |
| Category = "Legal" | Route to Legal department first |
Implement conditional routing using Odoo's automated actions tied to the approval request's fields. When the amount exceeds a threshold, add additional approvers to the approval chain automatically.
Approval Matrix
For organizations with complex governance, build an approval matrix:
| Category | <$5K | $5K-$25K | $25K-$100K | >$100K |
|---|---|---|---|---|
| Operating Expense | Manager | Director | VP | CFO |
| Capital Expense | Director | VP | CFO | CEO + Board |
| Staff Hiring | HR Manager | HR Director | VP + HR | CEO |
| Contract | Legal | Legal + Director | Legal + VP | Legal + CFO |
Configure this matrix using multiple approval types with amount-based rules. Each cell represents a unique approval workflow with its own approver chain.
Delegation and Substitute Approvers
Out-of-Office Delegation
When an approver is on vacation or otherwise unavailable, delegation ensures approvals keep moving:
Automatic delegation: Configure substitute approvers under each user's settings. When the primary approver is on approved time-off, pending approvals automatically route to the designated substitute. No manual intervention is needed.
Manual delegation: Approvers can delegate specific pending approvals to a colleague. Under My Approvals > Pending, select requests and click "Delegate to..." This creates an activity for the delegate and records the delegation in the approval audit trail.
Escalation Rules
When no delegation is configured and the approver does not respond:
| Time Elapsed | Action |
|---|---|
| 24 hours | Reminder email to approver |
| 48 hours | Reminder with "Overdue" flag in dashboard |
| 72 hours | Escalation to approver's manager |
| 5 business days | Auto-delegate to department head |
| 10 business days | Alert to HR/Operations for intervention |
Configure these timeframes under the approval type settings. Critical categories (safety, legal, customer-facing) should have shorter escalation periods than routine approvals.
Backup Approver Configuration
For critical approval chains where delegation is not sufficient, configure backup approvers at each level. If the primary approver does not act within the deadline, the backup receives the request simultaneously. Either person can approve, preventing single-person bottlenecks.
Deadline Enforcement
Setting Deadlines
Each approval type can have a default deadline:
| Category | Default Deadline | Rationale |
|---|---|---|
| Purchase Request | 3 business days | Avoid procurement delays |
| Expense Report | 5 business days | Monthly reimbursement cycle |
| Time Off | 2 business days | Employee planning needs |
| Capital Expenditure | 10 business days | Complex review required |
| Emergency Purchase | 4 hours | Urgent operational need |
| Contract Review | 5 business days | Legal review SLA |
Deadline Notifications
Configure escalating notifications as deadlines approach:
- At submission: Approver receives request with deadline clearly stated
- 50% of deadline elapsed: Gentle reminder if not yet reviewed
- 24 hours before deadline: Urgent reminder with escalation warning
- At deadline: Mark as overdue, notify requester, escalate to next level
- Post-deadline: Daily overdue summary to approver's manager
SLA Tracking
Track approval SLA compliance across the organization:
- On-time rate: Percentage of approvals completed within deadline
- Average cycle time: Mean time from submission to final approval
- Bottleneck identification: Which approvers consistently delay the process
- Category performance: Which approval types have the best/worst turnaround
Build a monthly approval SLA report and share with department heads to drive accountability.
Mobile Approval Experience
Mobile App Features
Odoo's mobile app provides a streamlined approval experience for managers who rarely sit at desks:
Notification-driven workflow: Push notifications alert managers to pending approvals. Tapping the notification opens the approval request with all details, attachments, and previous approver comments visible.
Swipe actions: On mobile, approve or refuse with a swipe gesture. Swiping right approves, swiping left opens the refuse/comment dialog. This makes reviewing a queue of routine approvals fast and intuitive.
Attachment viewing: Open and review attached documents (PDFs, images, spreadsheets) directly in the mobile app. Pinch-to-zoom on expense receipts or vendor quotes. No need to download files or switch to another app.
Voice comments: Add voice notes as approval comments instead of typing on a small screen. Voice notes are attached to the approval record and accessible to all parties.
Offline support: Approvals made while offline queue locally and sync when connectivity returns. This is essential for managers traveling or working in areas with poor connectivity.
Manager Dashboard (Mobile)
The mobile dashboard shows:
- Pending approvals count: Badge indicator on the app icon
- Overdue approvals: Highlighted in red for immediate attention
- Recent activity: Approvals completed in the last 7 days
- Team requests: Pending requests from your direct reports
Custom Approval Workflows
Beyond Standard Categories
Odoo's Approvals module is extensible for any business process. Examples of custom workflows built by ECOSIRE clients:
Quality deviation approval: When a manufacturing batch fails quality inspection, a deviation report requires approval from Quality Manager, Production Manager, and (if the deviation affects customer deliveries) Sales Manager before the batch can be reclassified, reworked, or scrapped.
Vendor onboarding approval: New vendor registration requires approval from Procurement (vendor qualification), Finance (credit terms), and Legal (contract review). Each department completes their section of the evaluation before the vendor is activated in the system.
IT change management: System changes (software updates, configuration changes, access modifications) require approval from IT Security, the system owner, and the IT Director. Emergency changes follow an expedited path with post-implementation review.
Marketing asset approval: Creative assets (ads, brochures, website content) require Brand Manager review for brand compliance, Legal review for regulatory compliance, and Department Head sign-off before publication.
Building Custom Workflows
To create a custom approval workflow:
- Define the category: Name, description, and form fields specific to the process
- Design the approval chain: Who approves, in what order, with what conditions
- Set rules: Deadlines, document requirements, conditional routing
- Configure notifications: Who gets notified at each stage, via what channel
- Build the dashboard: Tracking views for requesters, approvers, and administrators
- Test the workflow: Run through all paths (approve, refuse, delegate, escalate, timeout)
- Train users: Brief training for both requesters and approvers
Integration with Other Odoo Modules
Approvals + Purchase
When a purchase request is approved, automatically generate a Request for Quotation in the Purchase module. The approved request details (products, quantities, preferred vendor, budget) populate the RFQ. This eliminates the manual step of transferring approved requests to the procurement team.
Approvals + Expense
Odoo Expense module has built-in approval workflows. For organizations that want additional approval layers (e.g., project manager approval before manager approval), the Approvals module extends the expense workflow with custom chains.
Approvals + Time Off
Time off requests route through the Planning module to check scheduling impact before reaching the manager for approval. If approving the time off would create an understaffing situation, the manager sees a warning with affected shifts.
Approvals + HR Recruitment
Hiring requests start as approval requests. Once approved, they automatically create a job position in the Recruitment module, pre-populated with the approved job description, department, and budget. This ensures no hiring begins without proper authorization.
Approvals + Accounting
Budget-dependent approvals can check real-time budget availability before routing. If the requested amount exceeds the remaining departmental budget, the approval either blocks with a warning or routes to a higher authority for budget exception approval.
Approval Analytics and Compliance
Reporting Dashboard
Build approval analytics under Approvals > Reporting:
| Report | Purpose | Audience |
|---|---|---|
| Cycle Time Analysis | Average days from submission to approval by category | Operations |
| Approver Performance | Response time per approver, on-time rate | Management |
| Volume Trends | Request volume by category, department, month | Planning |
| Bottleneck Map | Stages where requests spend the most time | Process improvement |
| Compliance Report | Requests approved outside policy (budget override, skip-level) | Audit |
| Delegation Report | How often delegation is used, by whom | HR/Management |
Audit Trail
Every approval request maintains a complete, tamper-proof audit trail:
- Request creation: who, when, what was requested
- Each approval/refusal: who, when, comments
- Delegations: from, to, reason, timestamp
- Modifications: any changes to the request after submission
- Escalations: automatic escalation events with triggers
- Final outcome: approved/refused with all supporting documentation
This audit trail is essential for regulatory compliance (SOX, ISO, industry regulations) and internal governance reviews.
Process Improvement
Use approval analytics to continuously improve your workflows:
- Identify bottlenecks: If one approver consistently delays the chain, investigate whether their workload needs redistribution or delegation rules need adjustment
- Simplify chains: If 98% of requests under $1,000 are approved, consider raising the auto-approval threshold
- Reduce redundancy: If two approvers in a chain always approve simultaneously, consider making one optional
- Add automation: If certain approval categories have 100% approval rates, consider converting them to notification-only workflows
Frequently Asked Questions
Can approvals be configured to auto-approve based on certain conditions?
Yes. Create automated actions that automatically approve requests meeting specific criteria. For example, expense reports under $50 with receipt attached can be auto-approved, skipping the manual review step. Auto-approved requests still maintain an audit trail showing the automatic approval and the rule that triggered it.
How do I handle approvals that require signatures rather than just clicks?
Integrate the Approvals module with eSignature. For categories that require legal signatures (contracts, policy acknowledgments, high-value purchases), configure the approval step to require an electronic signature instead of a simple approve button. The signed document is attached to the approval record.
Can external parties (vendors, customers) participate in approval workflows?
Yes, through the Odoo portal. External users can submit requests (e.g., vendor submits a change order) and view the status of their submissions. External approval steps are less common but can be configured — for example, a customer signs off on a project milestone before internal billing approval proceeds.
How do I migrate existing approval processes from paper or email to Odoo?
Start by documenting your current approval flows: who requests what, who approves, what conditions trigger escalation, and what the typical timeline is. Map each flow to an Odoo approval type. Run the paper/email process and the Odoo process in parallel for 2-4 weeks to validate. Once validated, retire the manual process and train all users on the digital workflow.
Can I set spending limits per employee that automatically enforce approval requirements?
Yes. Configure spending authority levels on employee records or department settings. When a purchase or expense request exceeds the employee's authority, the system automatically routes to the next approval level. Requests within authority can be auto-approved or require only a single confirmation.
How does Odoo handle approval requests submitted after business hours?
Requests submitted outside business hours queue normally. Deadline timers can be configured to count only business hours (excluding weekends and holidays) so that a Friday evening submission with a 24-hour deadline is due Monday evening, not Saturday evening. Configure your company's business hours calendar under Settings > General > Company.
Can I create approval workflows that span multiple Odoo modules?
Yes. Use automated actions and server actions to trigger cross-module workflows. An approved purchase request can create a PO in Purchase, an approved hiring request can create a job posting in Recruitment, and an approved budget exception can update the budget in Accounting. Each integration point is configured independently for maximum flexibility.
Streamline Your Approvals with ECOSIRE
Every manual approval is a potential bottleneck, a potential lost request, and a potential audit finding. Organizations that digitize their approval workflows see immediate returns in speed, compliance, and employee satisfaction — nobody enjoys chasing managers for signatures.
ECOSIRE's Odoo implementation team has configured approval workflows for companies ranging from 20-person startups (simple 2-level chains) to 5,000-person enterprises (complex matrices with conditional routing, delegation, and cross-module integration). Our implementation includes process analysis, workflow design, system configuration, user training, and 90-day optimization.
Contact ECOSIRE for an approval workflow assessment, or explore our Odoo customization services for specialized approval processes unique to your industry.
Related reading:
Written by
ECOSIRE TeamTechnical Writing
The ECOSIRE technical writing team covers Odoo ERP, Shopify eCommerce, AI agents, Power BI analytics, GoHighLevel automation, and enterprise software best practices. Our guides help businesses make informed technology decisions.
ECOSIRE
Transform Your Business with Odoo ERP
Expert Odoo implementation, customization, and support to streamline your operations.
Related Articles
German E-Invoicing (E-Rechnung) in Odoo: XRechnung, ZUGFeRD and the 2025–2028 Deadlines
Receiving e-invoices is mandatory in Germany since 2025 and issuing follows in 2027/2028: accepted formats, how Odoo produces XRechnung and ZUGFeRD, and what to test.
France's E-Invoicing Reform (2026–2027): What Changes for a Company on Odoo
Receiving e-invoices is mandatory in France since 1 September 2026 and SMEs issue them from 1 September 2027: calendar, approved platforms, Factur-X/UBL/CII and an Odoo checklist.
Odoo 19 to 20 Upgrade Guide: The Official Process, and What to Check in Custom Modules
How to upgrade from Odoo 19 (or 17 and 18) to Odoo 20: the official test-then-production process for Odoo Online, Odoo.sh and on-premise, plus the 20.0 changes that break custom modules.