Product tour ยท 3:23
EzeFlow in 3 minutes.
Follow a payment and a fuel slip from request to bank: the invoice in its window, a new supplier checked by two people, notes and approvals, the Android app, the reports and the FNB batch. A demo company with made-up data.
Transcript
What the tour says.
The narration, chapter by chapter. Click a time to jump there in the video. Captions are in the player too.
-
Introduction
EzeFlow. Payment requests, approvals, and supplier payments, in one place.
-
The dashboard
This is Demo Trading, a company with three branches. The dashboard shows how many payment requests there are, how many are waiting for approval, how many are approved, and how many are paid. You can look at all organizations together, or pick one.
-
Requesting a payment
Thandi, in Johannesburg, needs to pay for new tyres. She clicks Request payment, and enters the amount. Then she picks the supplier from her organization's approved list. The name and bank details come from that list, so nobody types an account number. She adds the reason, puts the tax invoice in its window, and clicks Create and Submit.
-
Straight to approval
Every request has its own page, and this one went straight to approval. The quotation and the purchase order are still marked as outstanding. They can be added at any time, even after approval.
-
A new supplier, checked by two people
New suppliers are checked by two people. Thandi added Waterberg Security, with its bank letter as proof. Two reviewers compare the details with that letter. Pieter sees the full account number while he reviews, says how he checked, and gives the first of the two authorisations.
-
Notes and @tags
Each payment request needs two approvals from different people, and nobody approves their own. Questions go into the notes, where colleagues are tagged and notified, like Lerato asking Thandi for the purchase order.
-
The second approval
On this one, Lerato has already approved. Pieter gives the second approval, and the request is ready to be paid.
-
A fuel slip on the phone
Slips are even quicker on the phone. At the pump, Thandi taps File a slip, and picks petrol and diesel. She enters the kilometre reading, the vehicle registration and the total, and switches on card payment, with the last four digits. Next, she takes a photo of the slip. The camera opens right in the app, and the photo lands in the tax invoice window. She adds the fuel station, and submits it for approval. No signal? Then the slip waits in the outbox, and goes for approval as soon as she is back online.
-
Slips and the vehicle report
On the website, Pieter sees the slip straight away. Fuel slips carry the vehicle registration and the kilometre reading, so you can filter by vehicle, and the vehicle report shows the cost and the distance travelled per vehicle.
-
Reports and the supplier list
Reports show the spending of each organization, and never add different currencies together. The beneficiary list shows every supplier, who authorised it, and what was paid. Everything exports to Excel, PDF and CSV.
-
The FNB bank batch
Approved requests go into an FNB batch. EzeFlow checks every line against the supplier list, the bank details, and FNB's own beneficiary file, and then creates the bulk payment file. FNB's authorisers release the money, so your bank stays the final control.
-
In short
EzeFlow. Every request documented, approved by the right people, and paid through your bank, with a full audit trail.
Read more about what you saw
Approvals & audit trail
Set how many people must approve. Every step is signed in, timestamped and logged.
Supplier control
Requests only pay approved suppliers. Two people check every new supplier and every bank-detail change.
Card & fuel slips
A photo of the slip, the card's last 4 digits, the vehicle and its kilometres. Card and vehicle reports.
FNB bank payments
Supplier master file, checks against your FNB beneficiary list and a ready-to-import FNB CSV.
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.