Payment Approval Bottlenecks When Owners Approve

A supplier calls at 10:30 on a Friday. The goods arrived on Tuesday, the invoice matches the order, and the accounts team has prepared the payment. Nobody can release it because the owner is travelling, their phone has no signal, and every payment waits in the same queue.

Payment approval bottlenecks often begin as an owner’s sensible attempt to protect cash. As the enterprise grows, however, owner-only approval can delay suppliers, payroll taxes and essential operations while still leaving the owner with full legal accountability.

The answer is not to remove owner oversight. We recommend a written delegation structure, clear evidence for each payment and segregation of duties that prevents one person from controlling the entire transaction.

Why owner-only approval stops working

An owner knows the business better than anyone else in its early stages. When there are five payments a week, checking each invoice can reveal waste, duplicate charges or purchases outside the plan.

The workload changes when the business has multiple sites, recurring suppliers, staff expenses and statutory remittances. Every invoice then competes for the same decision-maker’s attention, even where the payment is routine, budgeted and supported by complete records.

Zimbabwe company law requires companies to keep records of money received and spent, sales, purchases, assets and liabilities. Those records must give a true and fair view and explain transactions. Directors must also take reasonable steps to ensure compliance, effective 13 February 2020.

That requirement does not say an owner must personally approve every payment. It requires an audit trail that explains why the company spent the money, who had authority and how the company recorded the transaction.

Owner-only approval creates four practical risks:

1. Delayed obligations. PAYE returns and payments fall due by the 10th of the following month, using Form P2. A director’s travel schedule should not determine whether the finance team meets a ZIMRA deadline.

2. Poor supplier discipline. A valid invoice can sit unpaid because it waits with dozens of low-value requests. Suppliers then spend time chasing payment instead of serving the business.

3. Informal workarounds. Staff under pressure may ask the owner to approve a payment through a message, without the purchase order, invoice or goods-received evidence attached. That weakens the record even when the payment itself is legitimate.

4. Concentrated control. If the same employee can amend supplier details, approve an invoice and release funds, the business cannot independently check whether the supplier and bank account are genuine.

The most common mistake is to treat delegation as a loss of control. Delegation assigns routine authority. It does not transfer the director’s legal responsibility or accountability.

Step 1: Map where approvals actually stall

Before setting limits, list every payment type from the prior 60 to 90 days. Include stock purchases, rent, utilities, payroll, reimbursements, professional fees, tax payments, emergency repairs and transfers to related parties.

For each payment, record who requested it, who checked the documents, who approved it, who released it through the bank and who completed the bank reconciliation. This exercise often shows that the stated process and the real process differ.

Ask three direct questions:

• Which payments waited more than two business days for approval?

• Which payments lacked a purchase order, delivery evidence or a clear budget reference?

• Can any one employee create or amend supplier details and also release a bank payment?

A payment register should capture the supplier name, invoice number, amount, currency, due date, budget line, approver and payment reference. It gives the owner exception reporting rather than a pile of invoices with no context.

Worked example: a retailer waiting on one inbox

Take a Bulawayo hardware retailer with twelve staff, a monthly payroll and about 80 supplier invoices each month. The owner approves every invoice from a phone, including small regular stock orders and utility bills that recur each month.

In one month, the owner travels for six business days. The accounts clerk prepares a PAYE payment but waits for approval, while two stock suppliers place new deliveries on hold because older invoices remain in the queue. The business avoids an unauthorised payment, but it also risks missing ZIMRA’s 10th-of-the-month PAYE deadline.

The retailer could retain owner approval for new suppliers, non-budgeted spend and payments above a stated ceiling. It could allow a finance manager to approve recurring, budgeted payments up to an agreed limit once the accounts team completes the required matching. The owner would receive a weekly exceptions report showing all payments, overdue invoices and any payment that fell outside policy.

The better judgement call is not to add another layer to every routine invoice. It is to reserve owner attention for payments where the risk, amount or commercial decision justifies it.

Step 2: Set a delegation-of-authority matrix

Zimbabwe has no general statutory Zimbabwe-dollar or US-dollar payment-approval threshold for ordinary private companies. Each enterprise should set limits that reflect its turnover, cash reserves, industry and the people available to review transactions.

A practical starting point might look like this:

These bands are internal policy examples, not legal thresholds. A business may classify a large monthly rent invoice as recurring and budgeted, while a small payment to an untested supplier may still require owner review.

If annual turnover is modest and the owner still knows every supplier personally, do not build a complicated approval hierarchy. Start with two approval levels, a deputy approver and a clear list of transactions that always return to the owner or board.

Review the matrix every six months and after any major change in turnover, banking arrangements or senior staff. A limit that made sense at a modest monthly spend can become meaningless when the enterprise processes ten times as much.

Step 3: Separate the five jobs in a payment

A sound control separates requesting, checking, approving, releasing and reconciling. The Reserve Bank of Zimbabwe’s Risk Management Prudential Standard No. 1 of 2024 requires regulated institutions to maintain segregation of duties, safeguards over assets and records, plus regular transaction and account reconciliations, effective 15 May 2024.

Ordinary private companies should apply the same discipline in a proportionate way. The goal is simple: no employee should control the full route from supplier creation to cash leaving the bank.

A workable flow is:

1. Procurement or the operating team confirms the order and delivery.

2. Accounts matches the supplier invoice to the purchase order and goods-received note.

3. An authorised manager approves the payment within the delegation matrix.

4. A separate bank user releases the payment.

5. Someone independent reviews the bank reconciliation and investigates exceptions.

For services such as rent, legal fees or consulting, there may be no goods-received note. Replace it with evidence that the service was authorised and delivered, such as a signed engagement letter, milestone sign-off or monthly service confirmation.

Keep the payment approval evidence together: the invoice, purchase order, delivery evidence, approval record and bank-payment log. This is what allows the business to explain a transaction months later during an audit, dispute or internal review.

Worked example: the supplier-bank-detail risk

Take a growing construction contractor with a finance officer, a procurement officer and two bank users. The finance officer receives an email that appears to come from a regular supplier, changes the supplier’s bank account, loads a sizeable invoice and asks the owner to approve it before close of business.

If the owner sees only an invoice and a payment total, the approval process may not catch the altered bank details. If the same finance officer also releases the payment, the company has no independent challenge before funds leave its account.

The contractor should require a call-back to a known supplier contact before any bank-detail change. Procurement should confirm the purchase order and delivery, accounts should match the invoice, an authorised manager should approve the payment, and a separate bank user should release it. The owner would receive a report of all supplier master-data changes each week, even when the payment falls below the owner’s approval limit.

The cost of this control is a few minutes for genuine bank-detail changes. The cost of skipping it can be the full value of a payment sent to the wrong account.

Step 4: Treat tax payments as a paired process

Tax payments need special attention because a bank transfer alone does not always complete the compliance task. ZIMRA states that PAYE returns and payment are due by the 10th of the following month, with Form P2.

For payments through ZIMRA TaRMS, money paid into ZIMRA’s bank account does not appear against the taxpayer ledger until the taxpayer submits the related return. ZIMRA reaffirmed this point in a public notice dated 27 February 2026.

Assign a primary approver and a backup approver for statutory payments. The person who prepares the return should attach the payment confirmation, and a reviewer should confirm both the TaRMS return submission and the payment reference.

Do not let the owner’s absence leave a tax payment in a pending folder. A deputy authority for routine, correctly prepared statutory payments protects compliance while the owner retains review through monthly reporting.

Teams can also run payroll numbers through a PAYE calculator before filing. That check does not replace the payroll review or Form P2 process, but it can identify an obvious variance before the due date.

Step 5: Give the owner better oversight, not more invoices

An owner should receive a concise weekly report, not a stream of unstructured approvals. Include total payments by category and currency, payments above the normal limit, new suppliers, changed bank details, related-party payments, off-budget spend and overdue statutory obligations.

Set a monthly review of bank reconciliations and a sample of completed payment packs. The reviewer should look for missing approvals, repeated invoice numbers, unsupported expenses and payments that exceeded delegated limits.

A director cannot delegate accountability, so this review matters. It lets the owner test whether the controls work without becoming the daily processing point for every supplier invoice.

Document exceptions. If an emergency repair requires payment before the usual documents are available, record who authorised it, why the exception was necessary and when the missing evidence will be obtained.

Frequently Asked Questions

Can a Zimbabwe business delegate payment approval?

Yes. Routine payment approval can be delegated through a written authority matrix. The director or owner still retains legal responsibility and accountability, so they should review exceptions and periodic reports.

Does Zimbabwe law set a minimum amount that needs two signatories?

No general statutory payment-approval threshold applies to ordinary private companies. A company should set limits in its own policy based on its risk, cash position and operating model.

Who should approve a new supplier’s bank details?

Do not let the person who enters or changes supplier details approve the related payment. Require independent verification, such as a call-back to a known supplier contact, and report all changes to the owner or board.

What happens if we pay ZIMRA but do not submit the return?

For TaRMS, ZIMRA does not recognise the payment against the taxpayer ledger until the related return is submitted. Check the return submission and payment confirmation together.

Payment approval is a governance decision as much as a finance process. We can help you design delegation limits, payment controls and tax compliance workflows that match the scale of your enterprise. The result is suppliers paid on time, ZIMRA deadlines met without chasing the owner, and oversight focused on the payments that carry real risk. Speak With Our Team and request a quote tailored to your business.