- Modernise ERP · Enterprise · Dynamics 365 Finance & Operations
Human-led. Agent-operated. On Microsoft Dynamics 365.
- Approvals Agent · approval cycle cleared in Teams
Time Entry Agent
timesheets drafted for review
Product Content Agent
catalogue enriched for merchandiser edit
Lease Agent
IFRS 16 schedules current
Payflow Agent
payment run verified, journals posted
Reconciliation Agent
bank to ledger matched, exceptions flagged
Supplier Comms Agent
confirmations chased, late responses flagged
Expense Agent
receipts converted and routed to policy
Approvals Agent cycle cleared in Teams
receipts converted and routed to policy
- The wedge SAP and Oracle cannot match
Your financial record stays in South Africa.
- The platform you land on
The Microsoft stack you'll run. The Dynamics 365 finance and operations apps.
Dynamics 365 Finance
General ledger, payables, receivables, fixed assets and multi-entity close. SARS VAT and SARB reporting localised.
Payflow, Reconciliation and Lease agents inside
SARS VAT and SARB BOP localised
Hosted on the South African Azure regions
Dynamics 365 Supply Chain Management
Procurement, inventory, warehouse and manufacturing in one app. Supplier Communications Agent inside.
Dynamics 365 Project Operations
Project contracts, costing, WIP and revenue recognition. Time Entry, Expense and Approvals agents.
Dynamics 365 Commerce
Unified retail, e-commerce and call centre. Copilot enriches product content at catalogue scale.
Microsoft Foundry. Built by Braintree
Custom domain agents where Microsoft does not yet ship a named one. Built on Copilot Studio and Azure.
- The AI-operated enterprise
Microsoft Dynamics 365 powers the AI-driven enterprise
Custom agents. Built by Braintree on Microsoft Foundry
For the operations where Microsoft does not yet ship a named agent. Copilot Studio, Azure OpenAI and the Dynamics 365 ERP MCP Server. Bioforum's "Brian" is the reference pattern: reviewed by the U.S. FDA, SA-grounded, in production.
Built by Braintree
No named HR agents at finance and operations parity yet. Microsoft 365 Copilot works at role level. Custom agents enter through the AI Value Framework. Same business case discipline as the named agents above. Braintree doesn't deploy AI agents by default. We deploy them where the TCO case is proven.
- How we migrate
Evaluate, Architect, Migrate, Operate.
Evaluate
Scoped migration response inside 5 business days. F&O apps shortlisted from the decision matrix. TCO and payback modelled for the board.
$ Board sign-off gate
02
Architect
Target solution designed. Data model mapped. The lift-and-shift versus re-architect fork decided. The plan the board signs off.
03
Migrate
Environment provisioned in the Power Platform admin center. Data migrated, reconciled, signed off. TCO-approved agents live at go-live.
04
Operate
Run-state on one SLA. Release-wave adoption every six months. Custom agent builds where the AI Value Framework proves the case.
- The AI Value Framework is the gate
Braintree doesn't deploy AI agents by default. We deploy them where the TCO case is proven.
- Two paths. One destination.
The fork is how you get there, not where you land.
Dynamics AX lineage port
- Code patterns port. The data model maps. X++ extensions refactor.
- Microsoft-to-Microsoft lineage. Lower scope risk, same process shape.
- Named agents enabled at go-live where the business case proves out.
Greenfield re-architect
- Greenfield build in the finance and operations apps. Process redesign opportunity.
- Data re-architected, not lifted. Legacy records archived to OneLake.
- Agents deployed from day one on clean process design. Proper modernisation.
Both roads run the AI Value Framework. The destination is the same.
- One agreement. The commercial case.
One Microsoft Partner. One Intelligent Agreement. One Business Central estate.
Before. Three to six contracts.
- Separate ERP vendor master agreement
- Separate cloud hosting, security, Microsoft 365 reseller and integrations house
- Conflicting roadmaps. Finger-pointing when a close runs long. POPIA Section 72 cross-border transfer paperwork.
After. One Intelligent Agreement.
- One agreement: Dynamics 365 Finance, SCM, Commerce, Project Operations and HR
- One SLA across migration, run-state and the agent layer. One escalation path. One accountable partner
- POPIA-aligned by default. Financial data on the South African Azure regions
- Proof, not promises
200%+
Three Gartner Magic Quadrants
Dynamics 365 was named in three 2025 Gartner Cloud ERP Magic Quadrants.
Bioforum's "Brian"
Custom agent on Microsoft Foundry. Reviewed by the U.S. FDA, SA-grounded, in production.
- The honest comparison
Staying on legacy, moving to Dynamics 365, and the practical winner.
| The work | Staying on legacy ERP | Dynamics 365 Finance & Operations |
|---|---|---|
| Lifecycle | AX 2012 out of support. SAP ECC mainstream ends 2027. Oracle and JDE frozen |
✓
Microsoft's modern lifecycle. Two release waves a year. No cliff
|
| AI agents | External bolt-ons only. Agentic workflows not possible on-prem |
✓
Named F&O agents in-product. Copilot Studio for custom builds
|
| SA localisation and data residency | Custom-built, ageing with every SARS and SARB update |
✓
POPIA-aligned. SARS VAT and SARB BOP localised, on SA Azure
|
| Upgrade model | Big-bang upgrade every three to five years. Risk concentrated |
✓
Two Microsoft release waves a year. Risk distributed
|
| Vendor model | Three to six vendors. Multiple contracts. Conflicting roadmaps |
✓
One Braintree agreement. One SLA. One escalation path
|
| Near-term spend | No migration project. Zero near-term spend while you remain in support | A funded, scoped migration programme |
| 5 to 1 for Dynamics 365. Staying costs less this quarter. It costs more every quarter after. Honest. | ||