Contact Info
What should a South African firm clarify before signing a Dynamics 365 proposal?
A South African firm should clarify where local features in the proposal come from, Microsoft or a partner extension, and who maintains them through updates; how VAT data for SARS returns is configured and tested; how supplier data for B-BBEE reporting is held; what hosting and POPIA mean for your data; and how users keep working during outages. I review these points independently, with no Microsoft partner status or license income.
Last reviewed by Vikas Saroj
Dynamics 365 is often on the shortlist when a South African company already lives in Microsoft tools, belongs to an international group, or has outgrown a desktop accounting package and wants a mainstream vendor its board recognizes. Wholesalers, manufacturers, financial services firms and mining suppliers all appear in this group. I work remotely with them as an independent reviewer of fit, scope and proposals.
Familiarity with Microsoft is a reasonable starting point, but it is not a requirement list. The local questions decide the project: how VAT data supports returns, how supplier records feed procurement reporting, how POPIA shapes access and hosting, and how a cloud system serves sites that lose power. A proposal that glosses over any of these needs to be challenged before it is signed.
I work alongside the implementer you appoint, focusing on requirements, proposal quality and acceptance, so the project stays aligned with what the business needs.
Business Central against Dynamics 365 Finance and Supply Chain, compared on your size, complexity, group structure and internal capability rather than on what a proposal happens to lead with.
I trace each South African requirement to its source in the proposal, whether standard, an AppSource extension or partner code, and confirm who maintains it through Microsoft's update cycle.
VAT posting setup and reports tested with your tax practitioner's scenarios, plus Power BI and financial reports designed for management in rand and, where needed, a parent's currency.
Supplier classification, document storage, expiry alerts and spend reporting for B-BBEE purposes, specified in writing for the implementer to build through configuration or a small extension, then tested with buyers.
Questions on data location, backup, mobile access and fallback routines raised with Microsoft's documentation and your implementer, so outages and POPIA duties are designed for, not discovered.
Statements of work, license counts and change requests checked against documented requirements, with gaps, overlaps, unclear assumptions and inflated estimates raised in writing before you approve them.
Requirements before proposals
Compare and negotiate scope
Oversight through go-live
Most South African mid-sized companies considering Microsoft ERP look at Business Central. Larger organizations with complex supply chains, many legal entities or heavy manufacturing may be offered Dynamics 365 Finance and Supply Chain Management instead. I compare both on your scenarios, because proposals sometimes pitch the larger product where Business Central would serve, or the reverse.
The next question is localization. Microsoft delivers its own country localizations for a list of markets and leaves others to partners and AppSource publishers. Check which applies to South Africa for the product and timing you are considering, rather than assuming either way. Then ask the implementer to show, for each local requirement, whether it is met by standard features, a published extension or their own code.
That matters because Microsoft updates its cloud ERP on a regular cycle. An extension that is not kept current can break after an update, and if the publisher is a small firm, your continuity depends on them. I record the source and maintainer for every local feature and include it in the risk register. My Microsoft Dynamics consulting overview treats the product family without a country lens.
Dynamics 365 handles VAT through posting groups and setup tables that combine customer or vendor settings with item or service settings. Done well, this produces consistent VAT data for your tax practitioner. Done carelessly, it produces a return that needs manual adjustment every period. I bring your practitioner into the design early and test agreed scenarios: local sales, exports, credit notes, imported goods and services, and purchases with non-claimable input tax.
Supplier records need similar care if your company tracks its B-BBEE position. I specify the fields your verification advisor requires, such as the supplier's category, the evidence on file and when that evidence lapses, plus an alert for lapsing documents and a spend report grouped by classification. Your implementer builds it through configuration or a small extension; your advisor interprets the results.
Both pieces depend on clean master data, so migration matters. Moving from a desktop accounting package or an older Microsoft product is a chance to deduplicate suppliers, retire dead items and confirm VAT numbers before load. My data migration approach includes trial loads and reconciliation sign-off. For context on how I support this market, see the South Africa overview.
Business Central and the Finance apps are generally delivered as Microsoft cloud services, with an on-premise option for Business Central in some licensing scenarios. Microsoft operates data center regions in South Africa for some of its services; ask the implementer and Microsoft's documentation which region your ERP environment would actually use, and whether that suits the guidance from your information officer under POPIA.
Cloud hosting removes your server room from the equation but not your sites. When an office or warehouse loses power or connectivity, users lose access. I work through continuity with your IT lead:
Access design follows POPIA guidance: security roles aligned to job functions, restricted fields for sensitive data and logging of changes to master records. These decisions are written into the design documents I produce as part of my solution design work.
Dynamics 365 reaches South African companies through Microsoft's partner channel. A partner typically sells subscriptions, designs the solution, builds extensions and provides support afterward. Some are large and multi-national, others small and specialist. The arrangement works, but it means your main advisor also has commercial interests in licenses and services.
My position is different. I hold no partner status with Microsoft, resell nothing and take no referral fees, so my only interest is whether the project meets your documented requirements at a sensible cost. In practice I help at each stage. Before bids, I write requirements and a request for proposal so partners price the same scope. During selection, I score proposals side by side, check license counts against real roles and question estimates that look thin or padded. During delivery, I attend design sessions, review change requests and run user acceptance testing with your finance and operations teams.
Work is remote and in English, with workshops scheduled during South African business hours, which overlap with mine for most of the day. More on this work appears under ERP RFP consulting and vendor selection.
Microsoft's ERP is a credible option, but I advise against it, or push for a harder test, in these cases:
I put these concerns to the test in an ERP evaluation built on South African scenarios. For the other platforms in this market, see my South Africa ERP consultant page.
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.
Check this for the product and timing you are considering. Some markets get localization from Microsoft itself, while others depend on extensions published by partners or independent vendors. I confirm where each South African feature in your proposal comes from and who keeps it working through Microsoft's update cycle.
No. I do not resell any software or take commissions. Subscriptions are bought through the implementer or another channel you select. I help by checking that license types and counts match the roles that will use the system, so you neither overbuy nor end up short at go-live.
Microsoft runs regions in several countries and the location for your environment depends on the product and how it is provisioned. Ask your implementer and Microsoft's documentation for the specific answer, and have your information officer confirm it meets your POPIA obligations before go-live.
It can hold the data: supplier classifications, documents, expiry dates and spend by category, through configuration or a small extension. The scorecard calculation and interpretation stay with your B-BBEE advisor. I specify the data design so the figures your advisor needs come straight from posted transactions.
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.