Microsoft Dynamics 365 Business Central
A fixed-scope Business Central Online implementation for a standard first company.
A bounded implementation route for organisations whose requirements fit standard Business Central Online. Fixed scope. Fixed price after a short eligibility check.
Planned implementation time: 4–8 calendar weeks after the eligibility check, provided client data, decisions and access are available as agreed.
What the standard implementation delivers
- Eligibility
- Setup
- Data
- Training
- Go-live
- Hypercare
What is outside the standard scope
- material process redesign
- custom development
- complex integrations
Complex requirements move to Implementation Discovery or Custom Implementation.
Is Standard Implementation a fit for your situation?
The Standard package is suitable when:
- you are planning Business Central Online;
- you are implementing one first company;
- standard finance and basic purchasing, sales and inventory processes are sufficient;
- no material process redesign is required;
- no mandatory custom integrations or development are required within the Standard package scope;
- data can be prepared in the agreed templates;
- key users can participate in training and UAT.
Next step
-
If all material conditions fit, the next step is a short eligibility check.
Request an eligibility check -
If any material condition does not fit, we define an individual implementation scope.
Review your situation
If the individual scope is not yet sufficiently clear, we start with a paid Implementation Discovery.
A working first Business Central company, not an open-ended ERP programme.
- company and environment setup;
- standard finance setup;
- basic purchase, sales and inventory flows;
- agreed dimensions, locations and bank accounts;
- standard master/opening-data migration from agreed templates;
- key-user training;
- production preparation and go-live;
- short defect-only post-go-live support for the agreed scope.
The package remains standard by keeping non-standard work separate.
- material process redesign;
- custom development;
- complex integrations;
- complex data transformations or historical transaction migration;
- repeated data loads caused by source-data corrections;
- additional training or non-standard process design;
- third-party licences/subscriptions;
- on-premises or hybrid implementation.
The Standard package is not extended through repeated change requests to absorb custom requirements.
Standard implementation requires standard inputs.
- provide correct data in agreed templates;
- clean and correct source data;
- nominate key users;
- perform UAT against agreed scenarios;
- provide timely decisions, access and licences.
Add the local components you actually need.
Latvian Salary, Latvian Localization, Bank Gateway and Baltic EDI can be added through their standard setup route where the required scenario fits. Non-standard payroll, mapping, integration or process requirements are scoped separately.
Check whether the Standard Package fits.
The eligibility check is short. If the standard route fits, implementation can be defined directly. If it does not, we will identify the correct next step.