Contact Info
Which Business Central points need checking before a South African go-live?
Before a Business Central go-live, a South African company should confirm which local app or partner extension supplies VAT reporting and document layouts, test that VAT posting setup produces the figures your practitioner needs for SARS, agree dimensions for divisions and branches, prove EFT payment and collection files with each bank, and check the partner's scope covers all of it. I do this independently, holding no Microsoft partner status.
Last reviewed by Vikas Saroj
South African companies usually arrive at Business Central from Sage accounting products or a mix of packages that no longer scales, often with a partner already recommending it. The demo looks convincing. The difficult parts come later: VAT setup that nobody on the finance team can explain, bank files that the bank rejects, and reports that need dimensions nobody planned.
I work remotely as the client-side reviewer on these projects. Since I sell neither licenses nor implementation days, I can concentrate on whether the system and the scope serve your business.
This page goes into product detail; the wider Dynamics family is covered elsewhere.
These are the areas where a South African Business Central project most often needs an independent check before money and time are committed.
A comparison of what the proposed South African localization app or partner extension provides against your practitioner's checklist, covering VAT reports, tax invoice layouts, bank formats and who maintains it through updates.
VAT business and product groups designed with your practitioner for local, export, exempt and import scenarios, then every combination tested so the return figures can be traced to entries.
Item charges for freight, duty and clearing fees assigned to receipts, and customs VAT posted from clearing documents on its own, so stock cost and input VAT both hold up.
Global and shortcut dimensions for division, branch, project or sales channel, with defaults and mandatory rules where management reports depend on them, agreed before data is migrated.
EFT supplier payment files, debit order collection files where you collect from customers, and statement imports tested with each South African bank before cutover, including rejections.
A close read of the partner's statement of work, checking that local features, migration reconciliation, bank formats, training and acceptance criteria are written in, not left as assumptions.
Scope matches requirements
Design decisions documented
Evidence, not assurances
Business Central is built on a worldwide base that Microsoft localizes itself for some countries. For others, local functionality comes from partners and independent publishers through AppSource. Whether a Microsoft localization exists for South Africa at the moment you buy should be confirmed with Microsoft's current documentation, because coverage changes. In many South African proposals, a partner or publisher app supplies the local layer.
That app matters more than most line items in the proposal, because you depend on it for as long as you run the system. Before signing, I ask for written answers on:
Unclear answers become tracked risks, not footnotes. The Business Central page describes the product in general terms.
On every line, Business Central derives VAT by pairing two codes: one describing the customer or supplier, one describing the item, resource or ledger account. The VAT posting setup table defines the rate, the accounts and how each combination is reported. A missing line stops posting; a wrong line quietly misstates the return.
Working through it with your tax practitioner, I set up:
The test is a recent VAT period re-posted in a sandbox and compared with what was submitted. Submissions stay with your practitioner. The fit-gap approach is described under gap analysis.
Many South African mid-sized businesses run several divisions or branches under one company, and some belong to groups with entities in neighboring countries. Management wants profit by division and branch; the group wants consistent reporting across entities. Business Central handles both through dimensions, if they are designed before data is loaded.
My recommendations usually follow this pattern:
Payroll journals from your local provider are tagged with the same values, and intercompany postings between entities use agreed partner codes. Reports are then built in Business Central or Power BI from one set of postings. For reporting design, see management dashboards.
South African businesses pay suppliers by EFT from bank-specific file formats or online banking, and many collect from customers by debit order. Business Central can export payment files and import statements, but whether your banks' formats are supported depends on the local app, a bank connector or custom work. This should be settled in the scope, not discovered at go-live.
What I check:
Each format is tested with a small live batch before cutover, including a deliberately rejected item. If you are leaving Sage or another package, open supplier and customer balances are migrated at a clean cutover, as described under data migration.
Business Central reaches South African customers through Microsoft's partner channel, so the firm scoping your project typically sells the subscriptions too. A second reader who gains nothing from either is useful. I hold no Microsoft partner status and take no license income.
In a South African proposal, I look for:
I also say when another route is better: a small service firm may be well served by Zoho, a manufacturer wanting one integrated suite at a different cost profile might weigh Odoo, and a complex group may need the larger Dynamics apps covered on Dynamics 365 consultant South Africa. For a full comparison, start at ERP consultant South Africa or the South Africa hub. All reviews are remote, in your working hours.
Tell me about your business and current systems. I’ll suggest the most sensible first step.
Book a Consultation
Not sure which ERP you need?
Share your business requirements with me and I will help you understand the right process, architecture and platform before implementation.
Microsoft's own list of localized countries is revised from time to time, so verify it close to purchase. Where Microsoft does not localize, partners and AppSource publishers provide local features. For each local function in the proposal, I establish who built it and who will keep it working.
Each transaction pairs the VAT group of the trading party with the VAT group of what is being sold or bought, and the VAT posting setup table says what rate, accounts and reporting apply to that pair. I design that matrix with your practitioner and test every combination with real documents.
It can support them, usually through a local app, a bank connector or a collection service provider, rather than entirely out of the box. I check how mandates, batches, unpaid returns and resubmissions will work and make sure the chosen route is scoped and tested.
No. I have no partner status, no license sales and no commission arrangements. I represent your company: writing requirements, reviewing proposals and configurations, and running acceptance testing, while your chosen partner handles subscriptions and the build.
Every business is different. Share where you are today and what you want to fix, and I’ll tell you honestly whether and how I can help.
Book a Consultation
Book a consultation to talk through your processes, systems and goals. I’ll reply with practical next steps - no obligation.