Executive Perspective
A supplier payment passes through several stages between approval in Business Central and its appearance on the bank statement. The records retained along that route provide the organisation’s account of what occurred.
Reading time: 4 minutes
Executive overview
- Payment submission: establish whether the bank instruction remains aligned with the approved journal.
- Traceability: confirm that the complete transaction history is available for audit.
- Operational ownership: identify reliance on employees who understand bank-specific procedures.
- South African connectivity: assess where direct integration reduces handling across supported banks.
Once finance approves a payment journal in Microsoft Dynamics 365 Business Central, the instruction must reach the bank in the format required for processing. The route depends on the connection already in place. Where file handling forms part of the procedure, an employee generates the batch and submits it through the banking platform. A rejected entry returns to finance for investigation before the payment proceeds.
Years of repetition make the work familiar and place substantial reliance on the people who know each bank’s requirements. They also understand how to correct an exception, expertise that sits behind the completed transaction reported to executives.
What happens after approval
Business Central applies the organisation’s approval limits and permissions before recording the authorised journal. The payment then enters a banking procedure shaped by the relevant format. Its submission method reflects the access granted to finance employees and the organisation’s established practice.
The resulting instruction should correspond with the approved journal. Establishing that correspondence requires a record of the submission, including any correction made after a bank rejection. Without that history in one place, finance has to reconstruct the transaction when a supplier raises a query or audit requests proof of what occurred.
King V places the governance implications in clear terms. Accountability includes answering for the execution of responsibilities “even when these were delegated”. The assigned task sits with finance employees under the accountability of those responsible for oversight.
The evidence a completed payment leaves behind
The quality of the record depends on how the handover has been designed. Business Central holds the authorised transaction and the banking platform holds the instruction presented for processing. Local files and portal histories supply much of the intervening detail, with retained correspondence adding context. Weak record-keeping turns a straightforward audit request into a reconstruction exercise.
Bank formats and rejection codes also create a practical concentration of knowledge. An employee who understands the routine keeps payments moving. An absence or an unfamiliar problem then exposes the organisation’s reliance on that expertise. Documentation supports continuity within a procedure that relies on manual judgement.
SABRIC recorded 97,975 digital banking fraud incidents in 2024, an increase of 86% from the previous year, with gross losses reaching R1.888 billion. The report linked the incidents to social engineering that exploited human error. Its figures cover a broader field of digital banking activity; for corporate finance, they reinforce the need to govern every employee interaction with a banking platform.
Bank connectivity in the South African environment
South Africa’s payment infrastructure has developed around interoperability and richer payment information. The South African Reserve Bank’s 2025 consultation paper links ISO 20022 with transparency and payment-data automation. South African settlement infrastructure and participating banks adopted the standard in 2022, followed by SADC-RTGS in 2024.
Many Business Central environments were implemented under earlier project scopes, when payment submission remained an accepted finance procedure. A later review gives management an opportunity to assess the routine against current transaction volumes. Banking relationships and the evidence required by audit also belong in that review.
Braintree’s RSA Bank Integrations extension provides a direct connection for supported processes. According to its Microsoft Marketplace listing, the FNB API handles direct payments and debit-order instructions, and also imports statements. CSV payments and statements are available for FNB, ABSA and Standard Bank. Direct-payment APIs for ABSA and Standard Bank appear on the product roadmap.
Customer banking data passes directly to the bank, with Braintree outside the transaction path as a third-party intermediary. Removing file preparation and portal transfer reduces the employee activity that falls outside the Business Central record. It also reduces reliance on knowledge of bank-specific formats.
What management should examine
Integration changes the route taken by payment information and leaves governance over approval and banking access with the organisation. Beneficiary changes remain subject to the controls set by management. Each exception needs a named owner.
The clearest assessment begins with one completed supplier payment. Finance should demonstrate its movement from the approved journal through to reconciliation, supported by the records produced during submission. The walkthrough will reveal where employee judgement enters the procedure and whether the evidence retained supports the responsibility carried by the organisation.
That account gives executives a practical basis for assessing the current arrangement and the case for direct bank connectivity.
Sources
- South African Banking Risk Information Centre: Annual Crime Statistics 2024
- Institute of Directors in South Africa: King V Code on Corporate Governance for South Africa
- South African Reserve Bank: Draft Consultation Paper on Interoperability in the National Payment System
- Microsoft Marketplace: Braintree Bank Integrations
