01Why procurement is the primary audit risk
In a tax audit or external audit in the OHADA zone, the procurement cycle is examined first. The reason is structural: procurement concentrates the largest financial commitments, the most interactions with third parties, and the most common fraud risks.
The OHADA Uniform Act on accounting law (AUDCIF) requires companies to be able to justify each expense with adequate supporting documentation. If the document chain between purchase request, purchase order, delivery note and invoice is incomplete or inconsistent, the company is exposed to reassessment.
CIPS and ACFE (Association of Certified Fraud Examiners) document that procurement and supplier payments are among the first risk areas in mid-sized organizations. Auditors know this and begin their examination there.
02The 7 red flags auditors look for
First signal: purchase orders created after the invoice is received. Backdating POs is a classic indicator of unplanned purchases or bypassed approval workflows. Second signal: approvals by the same user who created the purchase request. Segregation of duties requires that requester and approver be distinct people.
Third signal: procurement concentrated on one or two suppliers without documented tender. Tax authorities look for situations of unjustified advantage given to a connected supplier. Fourth signal: invoices paid without a matching purchase order. Fifth signal: amounts repeatedly just below approval thresholds, a potential sign of deliberate splitting.
Sixth signal: unregistered or recently-created suppliers involved in a significant transaction. Seventh signal: the absence of a traceable audit trail, meaning the inability to reconstruct the full chronology of a transaction from system documents.
03The three types of preventive controls
Preventive controls stop an anomaly from occurring, as opposed to detective controls that catch it after the fact. Three types are essential in the procurement cycle.
First type: segregation of duties. The requester cannot approve their own request. The approver cannot create a supplier themselves. The person who receives the goods cannot validate the invoice alone. These rules must be enforced by the system, not just by internal procedure.
Second type: amount-based approval tiers. A request below a configured threshold goes through a single approver. Beyond that, two levels are required. For the highest amounts, the CFO validates directly. Third type: automatic 3-way matching. The system compares purchase request, purchase order and invoice before authorizing payment. Any variance above the tolerance threshold triggers an alert before payment is executed.
04The audit trail as a documentary shield
An audit trail is a chronological, non-modifiable record of every action taken on a transaction: who created the purchase request and at what time, who approved and when, who received the goods, who validated the invoice, who ordered payment.
AUDCIF provides that accounting books and records must allow the reconstruction of operations in chronological order at any time. A digital audit trail directly satisfies this legal requirement.
During a tax audit, presenting a complete and exportable audit trail changes the company's position: instead of searching scattered emails, Excel spreadsheets and verbal approvals, the CFO produces a structured report in a few clicks. This reduces audit duration and reassessment risk.
05How Procura automates internal controls
Procura enforces the seven controls described above natively, without advanced configuration. Segregation of duties is enforced by user role: requester, approver, receiver and accountant are distinct roles whose permissions do not overlap.
Approval tiers are configurable by amount and purchase category. 3-way matching is automatic: Procura compares PR, PO and invoice and blocks payment if the variance exceeds the configured threshold. Every action is recorded in a complete audit trail, exportable to the tax authority or an external auditor.
For a CFO preparing an audit or wishing to strengthen internal controls before annual close, Procura is usually deployed within a week, including approval threshold and segregation-of-duties configuration from day one.