Blog/Core feature
Core feature

Approval workflow: why your procurement cycle takes 40 days and how to cut it to 5

Approvals are the number-one bottleneck in Procure-to-Pay. Here's how configurable workflows and automatic escalations fix it.

Procura team · May 2026 · 7 min read
01 · Anatomy of a 40-day cycle02 · The four frictions to eliminate03 · The pieces of a workflow that performs04 · Amount thresholds05 · Segregation of duties and the outcome
5 frictions
Typical drivers of cycle extension
5 mechanisms
Routing, delegation, context, SLA, email
4 tiers
Typical amount-based tiers
SoD
Structuring segregation of duties
Back to the blog
01

Anatomy of a 40-day cycle

Walk through a typical case. A requester has a need. They draft a requisition in Excel. They send it to their manager, who approves in 5 days. The CFO approves 5 days later (month-end close in progress). Procurement requests 3 quotes that take 10 days to come back. The CEO signs off on the selection in 3 days. Total: 28 days of approvals, on top of variable lead times to receive quotes.

This process is completely disproportionate for routine purchases (office supplies, telecom, recurring services). And yet it's the actual scenario at a majority of African SMEs that haven't digitized.

02

The four frictions to eliminate

First friction: paper or email routing. A requisition in an attachment gets lost, sits in an inbox, doesn't get seen, doesn't get a reminder.

Second friction: no delegation during time off. When the approver is on leave, requests pile up.

Third friction: approvers signing off blind, with no context — remaining budget, history, urgency.

Fourth friction: no escalation. A request forgotten for 5 days stays forgotten.

03

The pieces of a workflow that performs

Five complementary mechanisms. Native routing inside the tool (no email, no lost paper trail). Configurable delegation (before going on leave, the approver sets up a temporary delegate). Inline context (at decision time, the approver sees budget, history, supporting documents).

Automatic escalation: if a request isn't actioned within the configured SLA, the approver gets a reminder, then their manager if there's still no answer.

Email approval: for approvers on the move, two buttons (Approve / Reject) right from the phone, tracked exactly as if they had used the app.

04

Amount thresholds

For a 50,000 XOF purchase, a 5-level approval chain is absurd. For a 50 million XOF purchase, it's necessary.

Four typical tiers. Tier 1 (< 500K XOF): manager only, expected cycle < 24h. Tier 2 (500K-5M): manager then Office Manager, 2-3 days. Tier 3 (5M-25M): three approvers, 5-7 days. Tier 4 (> 25M): four approvers including the CEO, 10-15 days.

This segmentation frees 80% of the volume from heaviness, and concentrates attention on the 20% that actually matter.

05

Segregation of duties and the outcome

Three foundational rules. The creator of a request cannot approve it. The approver of a request cannot sign off on its invoice. For critical-amount payments, triple validation across three different people.

An organization that implements this properly cuts its average cycle from 40 days to between 5 and 10 days. The time saved shows up on three fronts: operational (orders go out faster), financial (fewer late payments and penalties), and cultural (requesters regain trust in the formal process).

Ready to see Procura on your real data?

See how Procura digitizes your SYSCOHADA procurement cycle, from request to payment.

Sources & references

Free guide

The P2P Playbook for Africa.

Seven concrete levers to digitise your procure-to-pay cycle, SYSCOHADA, MeCEF, FNE, Mobile Money. PDF, 16 pages, free.

No spam, ever. One-click unsubscribe.