months → weeks
Remediation time
Business Central remediation and integration readiness
ERP & group data architecture Internal work sample
Corrected Business Central data and processes in weeks rather than months, keeping a customer-relationship system integration on track and documenting how the work should be run.
-
The problem
Weak item master, costing and dimension structures put a time-critical CRM integration at risk.
-
My role
Rebuilt item master, costing and dimension structures for consistent posting and reporting.
-
Where it stands
Remediation completed in weeks rather than months, ahead of the live CRM integration.
Results and evidence
Source notes
Accelerated ERP remediation from months to weeks.
Restructured master data and produced operating procedures ahead of CRM go-live.
Business impact
Protected the integration timeline and left a documented, operable system.
How I did it
- 01
Validated expected ledger behaviour before sign-off.
- 02
Produced an operating manual and warehouse procedures to sustain the change.
Tools and working context
Dynamics 365 Business Central / Navision environment within the group.
- Tools
- Dynamics 365 Business Central · Navision · AI-assisted workflow design
- Business area
- ERP · Operations
- Skill type
- ERP & Systems · Automation
Why I made these choices
- Stabilised master data before integration so the connected system used a known-good state.
- Paired remediation with operating procedures so the control would hold after go-live.
Skills used
- Dynamics 365 Business Central / Navision ERP & Systems Strong
- SOPs & runbooks Ways of Working Strong
What I learned
- Master-data remediation lasts only when operating ownership and procedures change with it.
What comes next
- Convert the method into a reusable pre-integration runbook for other entities.