FNB bank payments
From approved payments to a checked FNB payment file
Your bank team selects approved payments, EzeFlow checks every line against your supplier master file and your latest FNB beneficiary list, and produces a file to import into FNB Online Banking Enterprise. EzeFlow never moves money: your FNB authorisers still release the payments.
Professional and Enterprise plans · see plans
What you get
A named bank team
Only the people your administrator chooses can build batches, change supplier bank details or download payment files.
Supplier master file
One list of suppliers (beneficiaries) with their bank details and a history of every change. Account numbers are stored encrypted and shown masked.
Compare with FNB
Upload the beneficiary export from FNB whenever it changes. EzeFlow shows which suppliers are missing in FNB or have different details.
Checks before finalising
Blocking errors and warnings: edited after approval, bank details changed after approval, not on the FNB list, duplicate amounts, unusually large amounts, foreign currency.
FNB file plus a manual list
Download the payment file with its hash total. Payments that cannot go into the file are listed for manual capture in FNB.
Marked paid, with a trail
After FNB releases the batch, mark it paid. Every batch, check and download is recorded.
How it works
-
1
Select
On the payments list or a payment page, the bank team marks approved requests "for payment" and picks the payment date.
-
2
Check
EzeFlow runs its checks. Errors must be fixed, warnings must be looked at, before the batch can be finalised.
-
3
Download
Download the FNB Online Banking Enterprise CSV and the list of manual payments. Downloads are logged.
-
4
Release in FNB
Import the file in FNB. Your FNB authorisers approve and release the payments as they always have.
-
5
Mark paid
Mark the batch paid in EzeFlow and its payment requests move to paid.
Does EzeFlow connect to my bank account?
No. EzeFlow has no access to your bank. It creates a file that your team imports into FNB Online Banking Enterprise, and FNB stays the final control.
Which banks are supported?
The payment file is built for FNB Online Banking Enterprise. Payments to other banks work fine in the file as long as FNB accepts them; anything that cannot go into the file is listed for manual capture.
How does it protect against changed bank details?
Supplier details live in a master file with a full change history. A batch warns when a supplier's details changed after the payment was approved, and when the supplier is not on your latest FNB beneficiary list.
Can each organization pay from its own FNB account?
Yes. Batches are built per organization, and each organization has its own paying account.
Related features
Approvals & audit trail
Set how many people must approve. Every step is signed in, timestamped and logged.
Organizations & roles
Each user sees only their own organizations. Built-in and custom roles with 24 permissions.
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.