Batchly supports South African payment files for FNB Online Banking Enterprise.
Your organisation pays from its own FNB bank account. Each supplier you are paying has their own receiving bank account, which may be held with FNB or another South African bank.
| Detail | Where it comes from | Who it belongs to |
|---|---|---|
| Pay-from account | Xero bank accounts | Your organisation |
| Supplier account number | Xero contact details | The supplier receiving payment |
| Branch or universal branch code | Confirmed in Batchly | The supplier receiving payment |
| Account type | Confirmed in Batchly | The supplier receiving payment |
Batchly does not let you edit the supplier's bank account number. If the account number is incorrect, update it in Xero and refresh payment readiness in Batchly.
For each supplier included in an FNB payment file, Batchly needs:
Supported account types are:
Use a trusted source that relates to the same supplier bank account recorded in Xero.
If a supplier advises that their bank details have changed, verify the change using your organisation's normal supplier-verification process before updating Xero or confirming new payment details.
Yes. Your organisation can pay from an FNB account while individual suppliers receive funds into accounts held with different South African banks.
Each supplier must have the correct branch or universal branch code and account type for their own receiving account. You do not need to create a separate Batchly payment run simply because suppliers use different banks.
The supplier should become Ready immediately. You do not need to run another Xero sync just to save the branch code and account type.
The branch code and account type are an initial supplier setup requirement. Once confirmed in Batchly, they are saved for that supplier and do not need to be entered again for every bill or payment run.
If you have many suppliers, start with the suppliers you intend to pay in your next batch. Suppliers without confirmed South African payment details remain blocked from the FNB cash file until they are set up.
If the same supplier exists across multiple Xero organisations, payment details are currently confirmed separately for each organisation.
Batchly remembers which Xero bank account the saved branch code and account type were confirmed against.
If the supplier's bank account number later changes in Xero, Batchly will no longer treat the previous confirmation as payment-ready.
The supplier will show: Bank details changed — review required.
The supplier remains blocked from the FNB cash file until the new account has been confirmed.
If you no longer want to use the saved branch code and account type:
Clearing the Batchly payment details does not change or remove the supplier's bank account in Xero.
The supplier will return to Payment details required and cannot be included in an FNB cash payment file until the branch code and account type are confirmed again.
Upload the downloaded CSV to FNB Online Banking Enterprise and review the imported payments before authorising them.
After reviewing and authorising the payments in FNB, return to Batchly to complete the remaining workflow:
| Message | What to do |
|---|---|
| Payment details required | Open Supplier Intelligence → Payment Readiness and confirm the branch code and account type. |
| Bank account missing or invalid in Xero | Correct the supplier's bank account number in Xero, then refresh payment readiness. |
| Bank details changed — review required | Verify the changed account and reconfirm the branch code and account type against the current Xero account. |
| Supplier readiness unavailable — refresh from Xero | Refresh supplier details from Xero before confirming payment details. |
If you are unsure about a supplier's branch code or account type, confirm the details with the supplier or their bank before generating the payment file.
If an FNB import fails, contact Batchly support with the payment date, the exact FNB import error and, where available, the FNB import result.
Need help? Contact Batchly support.