One approval per spend, not two
An approved PR covers the PO as long as it stays within tolerance. No more double validation.
Most ERPs force a double approval: first the PR, then the PO. The result: one purchase waits for two approvals for a single spend. Procura applies a simple, internationally recognized rule: an approved PR is good for its PO as long as the PO stays within tolerance (±10% by default). Catalogs and framework agreements are auto-approved up to the cap.
How the module works.
PR → PO approval inheritance
The PO inherits the PR approval within ±10% price / ±5% quantity tolerance. Beyond that, automatic re-routing.
Auto-approved catalog
Purchases on a negotiated catalog go straight to issued PO with no re-validation, up to the configured cap.
Auto-approved framework agreements
Call-offs against a negotiated framework agreement are issued without further approval up to the contract cap.
Optional Finance Gate mode
For large commitments, enable an extra finance check. Three modes: smooth, visibility, control.
Day to day, in practice.
Auto-issued PO within tolerance
PR approved at 4.2M CFA → PO of 4.1M CFA → Procura recognizes the tolerance, issues the PO and sends the vendor email, with no re-routing.
Catalog purchase
Item present in a negotiated vendor catalog, under threshold: PO auto-issued, vendor notified, accounting commitment created automatically.
Call-off on framework agreement
Active framework agreement with a 50M CFA cap: each call-off under that cap is auto-approved, with consumption tracking.
Plugged into your tools.
Sage
Odoo
SAP
Email fournisseurs
Portail fournisseurs Procura
Your questions, answered.
The whole cycle, module by module.
See purchase orders in action.
A 30-minute demo, on your own use cases.