In this article
- Start with authority and risk—not arbitrary monetary bands
- Separate five stages before designing the workflow
- An approval matrix by transaction type
- Write the currency rule alongside the authority rule
- Exceptions must escalate even when the amount is small
- Make fiscal invoice validation a pre-payment checkpoint
- Configure SERPA Odoo ERP around the policy
- Illustration: replacing founder-only approvals
- A management dashboard that tests the matrix
- Frequently asked questions
- Does Zimbabwe prescribe private-company approval amounts?
- Can Odoo enforce every approval rule without custom work?
- Does approving a supplier bill prove input VAT can be claimed?
- Where SERPA can help
A purchasing officer is waiting for stock, the founder is travelling, and an urgent supplier invoice is approved in a messaging app. The payment goes out. At month-end, finance cannot show who checked the budget, the receipt or the ZIMRA fiscal invoice. This is what a missing approval matrix looks like in a growing enterprise.
A sound SERPA Odoo ERP approval matrix sets decision rights by transaction type, responsible role, materiality and exception risk. It should allow routine work to move without the founder while protecting the company against unauthorised commitments, related-party transactions and incomplete evidence.
Start with authority and risk—not arbitrary monetary bands
Zimbabwean law does not prescribe a universal purchase-approval amount for ordinary private companies. The board should adopt authority rules suited to the business’s liquidity, contract exposure, operating currency and capacity to supervise exceptions. Public procurement rules administered by PRAZ are separate and should not be copied into a private company as statutory approval bands.
The Companies and Other Business Entities Act requires directors to act in the company’s interests and preserves their statutory accountability. Management can receive defined operating authority, but a delegation should set its purpose, conditions, duration and reporting duties. The board must also preserve an appropriate process for conflicts of interest.
Separate five stages before designing the workflow
-
Request: a named employee identifies the business need and proposed supplier.
-
Budget check: the budget owner or finance confirms available budget and the full commitment.
-
Approval: a person authorised under the policy approves the commercial commitment before ordering.
-
Receipt and invoice check: someone independent verifies the goods or service and supporting fiscal document.
-
Payment release: treasury uses the approved evidence, with final payment authority separate from vendor-master changes.
A requestor should not be able to create a supplier, approve the purchase, certify the receipt and release the money without independent review. Smaller firms that cannot separate every task should document compensating checks rather than pretend segregation exists.
An approval matrix by transaction type
| Transaction type | Primary review | Escalation / exception |
|---|---|---|
| Procurement / supplier bill | Department budget owner and accounts payable | Unbudgeted spend, sole source, supplier change |
| Customer credit note / refund | Sales or customer service plus finance | Unusual reversal, missing original sale |
| Payroll amendment | HR confirmation and finance review | Changed bank details, advance or late change |
| Inventory write-off | Warehouse / operations and finance | Material loss or unexplained adjustment |
| Contract or related-party deal | Commercial owner, legal or CFO as relevant | Director conflict, guarantee or long-term commitment |
Money still matters—but no article can tell another business what limit to adopt. Use the company’s recent transactions to create internal bands for routine, manager, finance-executive and board decisions. Measure exposure across the complete contract period, not just a single recurring instalment. Aggregate related requests and explicitly prohibit splitting orders to avoid a threshold.
Write the currency rule alongside the authority rule
For a business operating in US dollars and ZiG, state the controlling currency, the exchange-rate source, the date used for conversion and who updates the bands. Retain the applicable rate and approval value with the transaction record. A missing conversion policy makes it possible to manipulate which approver sees a commitment.
Exceptions must escalate even when the amount is small
-
Related-party and conflicted-person transactions, with appropriate disclosure, recusal and recorded approval.
-
Unbudgeted or emergency commitments, with reason, authorised temporary action and ratification date.
-
Sole-source suppliers, material contract changes, guarantees and foreign-currency commitments.
-
Customer credits, employee advances, supplier bank-detail changes and payroll amendments.
-
Backdated approvals and split purchase orders, which should trigger an exception investigation.
A sole-source purchase can be justified. So can an emergency repair. The policy should require evidence and a higher-level review instead of labelling every exception as misconduct. Equally, “urgent” must never become a permanent route around purchase-order controls.
Make fiscal invoice validation a pre-payment checkpoint
ZIMRA’s October 2024 notice explains that non-compliant fiscal invoices cannot support relevant VAT input-tax or income-tax expenditure claims. Its 2026 notices require FDMS-valid invoices with accurate buyer details for domestic input-tax claims through TaRMS. The approval workflow should therefore capture the fiscal invoice, verification status, supplier identity and correction outcome where applicable.
A business should not blindly reject every ordinary payment simply because the same fiscal document is not used in all tax categories. Apply the relevant law to the actual transaction and have finance or a tax professional define the exceptions. The purpose of the pre-payment review is to prevent avoidable unsupported deductions and costly supplier follow-up.
Configure SERPA Odoo ERP around the policy
-
Extract and classify recent spending, refunds, payroll changes and adjustments by department, currency and risk.
-
Agree the company-specific authority bands and reserve unusual or material matters for the correct senior approver.
-
Configure roles, approval states, required documents, substitute approvers and expiry dates.
-
Test real transactions: an approved order, missing fiscal invoice, split order, related-party supplier, absent approver and duplicate payment.
-
Run negative tests: verify that users cannot self-approve, bypass mandatory review or quietly alter an approved payment record.
-
Review monthly exceptions and change access when staff move roles or leave the company.
Illustration: replacing founder-only approvals
An illustrative distributor depends on the founder to approve supplier orders and customer refunds. When the founder travels, staff commit to urgent purchases over the phone and collect signatures afterwards. The redesign assigns ordinary purchasing to budget owners, routes unusual items to finance leadership, separates payment release and keeps a time-bound substitute authority. The founder still receives a clear report of exceptions and material commitments instead of being the approval system.
A management dashboard that tests the matrix
| Monthly measure | What it tells management | Corrective response |
|---|---|---|
| Approval turnaround | Whether routine work is blocked by the process | Review limits, coverage and named delegates |
| Approvals after commitment | How often authority was bypassed | Investigate causes and enforce escalation |
| Purchases with complete evidence | Share with purchase order, receipt, invoice and approval | Improve documents and AP controls |
| Emergency / conflict exceptions | Risk types and repeat users or suppliers | Review planning, policy and conflicts register |
| Change-of-bank-details exceptions | Exposure to unauthorised beneficiary changes | Require independent verification |
These are management indicators, not statutory benchmarks. Use an initial baseline, set a measurable review cycle and investigate repeated exceptions by department, approver and supplier. An approval matrix has failed if the board receives a clean spreadsheet while real decisions continue in unrecorded messages.
“An approval matrix is not a table of spending limits. It is evidence of who made the decision, on what authority, and with which supporting records.”
Frequently asked questions
Does Zimbabwe prescribe private-company approval amounts?
No universal monetary bands apply to ordinary private companies. The board should approve internally appropriate delegations, document risk-based exceptions and retain oversight.
Can Odoo enforce every approval rule without custom work?
Odoo supports role-based approvals and connected procurement workflows, but exact routing, document checks and blocking rules depend on the installed applications, edition and implementation. Test the required scenarios before go-live.
Does approving a supplier bill prove input VAT can be claimed?
No. Finance needs the required supporting fiscal tax invoice and, for relevant domestic claims, validation through ZIMRA’s FDMS/TaRMS process. A management signature cannot replace tax evidence.
Where SERPA can help
SERPA can assess your delegation policy, configure Odoo approval workflows and test the complete request-to-payment trail. Request a consultation for an ERP readiness audit that reduces founder bottlenecks while strengthening governance, tax documentation and operational accountability.