Business Central Customisation
Extensions, custom reports and workflow changes where the standard system does not fit.
Depends on scope; a report or a focused extension typically takes 1–3 weeks
Business Central covers a great deal as standard, and the first question on any customisation request is whether the requirement can be met by configuration instead. Every customisation is something that must be maintained and tested against future updates.
Where a genuine gap remains, we build it as an extension rather than by modifying the base application, so that Microsoft's updates continue to apply cleanly.
Configuration first
A surprising proportion of customisation requests turn out to be configuration questions — a dimension that was not set up, a report filter nobody knew about, or a posting group arranged differently from how the process actually works.
We work through that before quoting development. It is cheaper for you and leaves less to maintain.
Why extensions rather than modifications
Business Central receives regular updates from Microsoft. Code written as an extension sits alongside the base application and survives those updates; changes made to the base application do not, and accumulate into an upgrade problem.
Everything we build is an extension, with the source handed over so you are not dependent on us to maintain it.
Who needs this
- Businesses with a process the standard system does not support
- Businesses needing reports in a specific format for management or a lender
- Businesses integrating Business Central with another system
- Businesses whose existing customisations are blocking an update
Eligibility and conditions
- A running Business Central environment
- A defined requirement, or willingness to work through one with us
- Access to a sandbox environment for development and testing
What this covers
-
Configuration review first
Whether the requirement can be met without development.
-
Extension development
Built as an upgrade-safe extension, not a base modification.
-
Custom reports
Reports in the format your management or lender needs.
-
Integration
Connections to other systems where required.
-
Source handover
The source code delivered to you.
-
Update testing
Customisations verified against new releases.
How the process works
-
Understand the requirement
What is needed and why the standard system does not do it.
-
Check configuration
Whether it can be met without development.
-
Specify
A written specification agreed before development starts.
-
Build and test
Developed in a sandbox and tested against real cases.
-
Deploy and hand over
Deployed to production, with the source delivered.
Documents required
-
Requirement description
What the process needs to do.
-
Current workaround
How the requirement is handled today.
-
Sample outputs
The report or document format you need.
-
Environment details
Version, and whether cloud or on-premises.
-
Sandbox access
For development and testing.
-
Existing customisation details
Where earlier work has been done.
The list above is indicative. Additional documents may be required depending on your case and the current departmental requirements.
Frequently asked questions
Will customisations break when Business Central is updated?
Not if they are built as extensions. An extension sits alongside the base application and survives Microsoft's regular updates. Changes made directly to the base application do not, and accumulate into an upgrade problem.
Everything we build is delivered as an extension, with the source code handed over to you so that you are not dependent on us to maintain it.
Need something Business Central does not do as standard?
Describe the requirement and we will tell you whether it needs development at all.