Procurement Anomalies
Invoices Without Purchase Orders
Flags payments processed without a preceding purchase order, bypassing commitment controls.
Why no-PO payments break the control chain
The purchase order is the commitment control that confirms a need was authorised and budgeted before money was spent. Paying an invoice with no preceding PO bypasses commitment accounting and pre-expenditure approval, weakening the controls the MFMA and COSO frameworks rely on. AuditPro Core flags no-PO payments so after-the-fact spending is challenged rather than quietly absorbed.
The Numbers
AuditPro Core renders this view from your tenant's live, tamper-evident records. The figures below are illustrative sample data.
No-PO Payments
1,376
11% of payments
No-PO Value
R 58.2m
▲ R 11m
Repeat Vendors
44
no-PO 5x+
Confirming Orders
203
PO after invoice
No-PO Payments by Department (count)
Top Vendors Paid Without POs
| Vendor | Payments | Value (R'000) | Main Dept |
|---|---|---|---|
| Vendor 0455 | 41 | 6820 | Facilities |
| Vendor 0782 | 33 | 4910 | IT |
| Vendor 1109 | 28 | 3740 | Fleet |
| Vendor 1366 | 22 | 2980 | HR |
| Vendor 1620 | 19 | 2210 | Finance |
Figures shown are illustrative sample data for demonstration. AuditPro Core renders these views from your own tenant's live, tamper-evident records.
Commitment control
A PO records and reserves budget at the point of ordering, preventing overspending and creating an authorised baseline against which the invoice is later matched.
Three-way matching
Sound payment control matches the PO, the goods-received note and the invoice. With no PO there is nothing to match against, so price, quantity and authorisation go unverified.
After-the-fact procurement
Paying first and documenting later inverts the control sequence and is a common route for unauthorised, split or favoured-supplier spending to enter the ledger.
Legitimate exceptions
Some categories, such as certain utilities or statutory payments, may legitimately lack a PO. The control is distinguishing these defined exceptions from undisciplined no-PO spend.
How AuditPro Core Bridges the Gap
- Reconciliation: AuditPro Core matches payments to purchase orders and isolates invoices paid with no PO on file.
- Exception workflow: No-PO payments outside approved categories raise cases for justification.
- Continuous monitoring: The match runs as payments post, keeping after-the-fact spend visible.
- Traceability to source: Each flag links to the invoice, the payment and the missing commitment.
Key Takeaways
- A PO is the commitment control that authorises spend before it happens.
- No PO means no three-way match and unverified price and quantity.
- Define legitimate no-PO categories so genuine exceptions are not noise.
- Challenge after-the-fact payments rather than absorbing them.
See This on Your Own Data
AuditPro Core renders this dashboard from your tenant's live, tamper-evident records — every figure traceable to source.