Approvals & audit trail
Payment approvals with a trail your auditor can follow
Decide how many different people must approve a payment. EzeFlow shows the request as partially approved until enough people have signed off, sends rejections back with a reason, and records every step.
Included in every plan · see plans
What you get
You set the number of approvers
From one to ten different people. The same person cannot count twice, and a request shows "partially approved" until the number is reached.
Rejections with a reason
A rejected request goes back to the requester as a draft, with the reason attached. The rejection history stays on the request.
Rules for paying
Switch on "enforce approvers" so nothing can be marked paid before it has enough approvals. Or allow finance to pay directly when that suits you.
Evidence before submitting
Require a minimum number of documents, such as the invoice and the order, before a request can be submitted.
Approvers stay in their lane
People only approve payments of the organizations they are assigned to, with the permissions of their role.
A complete record
Who created, edited, approved, rejected and paid each request, and when. Searchable in the audit log and exportable to CSV.
How it works
-
1
Submit
A staff member captures the payment on the web or the Android app: supplier, amount, currency, organization, reason, and the documents.
-
2
Approve
Approvers with the right permission open the request, check the documents and approve. Each approval is recorded with name and time.
-
3
Query or reject
Questions go in the reviewer notes. If something is wrong, reject it with a reason and it returns to the requester.
-
4
Pay and archive
Once approved, finance marks it paid, or it goes into an FNB bank batch. Paid requests can archive themselves after a number of days.
Can I set different approvers for large amounts?
Not today. EzeFlow uses one rule per company: the number of different people who must approve. Who can approve is decided by role permissions and organization access.
Can someone approve from their phone?
Yes. Approvers can open and approve requests in the Android app or in the browser on any phone.
What happens when a request is rejected?
It goes back to draft with the rejection reason, and the requester can fix it and submit again. Each rejection stays in the history.
Is there a record of who approved what?
Yes. Every approval, rejection, edit, payment and export is logged with the person and the time, and the audit log can be filtered and exported.
Related features
Notes, @tags & alerts
Reviewer and requester notes, @tag a colleague, and a notification bell instead of WhatsApp.
FNB bank payments
Supplier master file, checks against your FNB beneficiary list and a ready-to-import FNB CSV.
Reports & exports
Turnaround times, trends and red flags. Totals per currency. CSV, PDF and Excel.
See it with your own payments.
Start a 7-day free trial without a card, or look around a demo company with sample data first.