PRODUCT CAPABILITIES
What’s in scope.
01
Creditor-payment export
Export approved payment-journal information in the supported FNB format. Confirm the bank-side import, approval and exception process; file export alone does not establish a returned paid status in Business Central.
02
Debit-order management
03
Bank-statement import
Bring FNB statements into Business Central’s bank reconciliation. The imported transactions support matching and investigation within the same environment as the underlying financial records.
04
Connected banking data
Use supported file formats and separately configured API functions for the required banking workflow. Define bank-side approval, response checks and exception ownership for each connection.
Configure the connection around finance controls
The published requirements are Microsoft Dynamics 365 Business Central and FNB online banking. Bank access, supported functions and the approval process should be confirmed for the accounts and environment being connected.
✓
Identify the Business Central company and FNB banking accounts.
✓
Confirm the required access and bank-side setup.
✓
Define responsibility for preparation, approval and exception follow-up.
✓
Test payment responses and statement reconciliation before operational use.
THE PRODUCT IN PRACTICE
Review the bank connection setup
The FNB setup example shows the currency and integration settings. Bank onboarding and the applicable authentication requirements are part of the implementation.
Read the workflow guide
01
Match each banking task to its connection
FNB Bank Integration extends Business Central with bank-specific payment, collection and statement workflows. The product page presents creditor payments, debit orders and bank-statement import. The detailed Help guide distinguishes file-based statement import, payment export formats and an API integration for direct-debit management. The configuration should identify the method used for each account and workflow so that direct connectivity is not assumed for every function.
On the Bank Account card, the selected statement-import and payment-export formats determine how the applicable files are handled. API services require bank-side activation. Braintree can scope these elements against the organisation’s FNB arrangement and the extension version, including any existing process that needs to remain in use.
02
Prepare collections with the required mandates
The FNB direct-debit guide documents support for instructions to South African banks in South African rand. It requires the appropriate bank account information and an active mandate in the Business Central direct-debit structure. The bank provides the client credentials and enables the account for integration. Sandbox and production settings are separate, with production activation prevented in a Business Central sandbox.
Collections can use itemised or consolidated bank booking, according to the configured account setting. The guide describes optional automatic posting once the collection report has been received and no entries remain pending. Background jobs retrieve collection updates and unpaid information. Their status and ownership need to be included in operational handover rather than assumed to run simply because the extension is installed.
03
Check customer and vendor banking details
The published FNB Help guide includes an Account Verification Service for customer and vendor bank accounts. A request sends account and account-holder details to FNB, then a background job retrieves the result. The latest result appears against the bank account while earlier requests remain available in a request history.
Verification is evaluated against configurable acceptance criteria. The organisation selects the criteria that matter for the account, such as account-holder identification, company name, whether the account is open, or whether credits and debits are permitted. At least one criterion must be enabled, and every enabled criterion must receive the required positive response before the account is marked verified. A completed request can therefore still fail the configured verification test.
04
Make background processing visible to finance
Account verification depends on an operational Business Central job queue, the relevant user permissions and correctly linked contact information. The account-holder contact must relate to the same customer or vendor as the bank account. For a company contact, registration details form part of preparation; for a person contact, identification details are required by the documented process.
Email notification is a configured option using an email account and the AVS email scenario. If no recipient address is available, the result remains accessible in Business Central. A practical support process therefore starts with the request status and response details, then checks the job queue, missing data or notification configuration. Sending another request creates a new history entry.
05
Define the finance handover
Before deployment, Braintree should confirm the enabled bank services and demonstrate both normal processing and exceptions using the agreed environment. The engagement should name the people who maintain banking data, authorise collections, review unpaid items and investigate verification failures.
Confirm FNB activation, the required credentials and the rand-based collection scope.
Review mandates, customer bank details and account-holder contact relationships.
Choose verification acceptance criteria and assign suitable permissions.
Test response retrieval, unpaid handling, notifications and the proposed posting settings.
EVIDENCE & DOCUMENTATION
See the work in context.
FNB workflow and verification documentation
The detailed guide documents bank activation, direct-debit configuration, account verification acceptance criteria and the distinction between submitted, completed and failed requests.
Explore the documentation
BEFORE YOU DECIDE
