DR DYNAMICSE-invoicing in Norway: what CFOs and CIOs need to know before January 2027
Norway's B2B e-invoicing law is adopted: issue from 1 Jan 2027, digital bookkeeping by 2030. EHF over Peppol, no clearance — and where the D365 F&O work sits.
Delivery that improves D365 F&O — without the full-scale implementation circus
In short
Focused D365 F&O delivery workstreams: enhancements, additional module rollouts, process redesign, automation, and sensible customisations — without a big-bang programme. We also do the higher-ROI job of removing customisations and replacing them with standard D365 where it genuinely fits, and we slot in alongside your prime SI to accelerate delivery and keep the solution clean.
Engagement options
You don’t always need a “big-bang” programme (and 47 weekly steering meetings) to get real value from Dynamics 365 Finance & Operations.
Dr Dynamics delivers focused D365 F&O workstreams: enhancements, additional module rollouts, process redesign, automation, and sensible customisations. We also do the less glamorous (but higher ROI) job: removing customisations and replacing them with standard D365 where it genuinely fits.
If you already have a prime SI, we slot in alongside them to accelerate delivery, unblock bottlenecks, and keep the solution clean.
What we deliver
- Enhancements and continuous improvement. Targeted changes that remove pain points, reduce manual work, and improve adoption — without breaking month-end.
- Additional module implementation. Adding new capability to an existing D365 estate (end-to-end, or as a workstream lead), such as:
- Finance (GL, AP, AR, Cash and Bank, Fixed assets, Budgeting)
- Supply Chain (Procurement, Inventory, Master planning)
- Projects (Project management and accounting)
- Localisations and compliance-driven features (where applicable)
- Process redesign and automation. We map the real process (not the PowerPoint version), redesign it around standard D365, then automate the boring bits using the right tool:
- D365 workflows and approvals
- Power Automate where it makes sense
- Integration patterns that don’t turn into a support nightmare
- Customisations (only when justified). When standard won’t do the job, we build what you need with discipline:
- Clear design and impact assessment
- Extension-first approach (keep the upgrade path sane)
- X++ and integrations with proper ALM and testing
- De-customisation (yes, really). A lot of D365 estates are carrying “legacy habits” as code. We help you unwind them safely:
- Customisations review (what to keep, retire, or replace)
- Replace with standard features and configuration
- Reduce maintenance cost and upgrade friction
- Integrations and reporting delivery.
- Integrations via OData/DMF, Azure integration services, Logic Apps / Functions (fit-for-purpose)
- Data entities and data quality controls
- Reporting improvements (financial statements, operational reporting, Power BI hand-off or build)
Delivery engagement options
Choose the model that fits your needs.
- Delivery Sprints (2–6 weeks). Fixed objective, clear scope, working output. Ideal for enhancements, process fixes, and automation.
- Workstream Lead. You keep overall programme control. We lead a stream (e.g., AP automation, inventory redesign, projects) and deliver it end-to-end.
- Rescue and Recovery. Rapid triage, root cause analysis, pragmatic plan to stabilise and ship when the project is “nearly there” for the third month in a row.
- Embedded Architect / Senior Consultant. Hands-on design and build support inside your team, with strong governance and straightforward communication.
- Add-on Services & Packs. Targeted packs such as Enhancement Backlog Triage, De-customisation Audit, Month-End Close Accelerator, Environment & ALM Setup, Integration Health Check, and Training for new features.
How we work
- Diagnose. We start with a short discovery to identify the real constraint: process, data, security, configuration, code, or environment.
- Design for standard first. We aim for standard D365, then extend only where it creates genuine advantage.
- Build with discipline. Clean configuration, controlled extensions, and no surprise side effects.
- Prove it works. Fit-for-purpose testing, pragmatic UAT support, and release planning that respects business cycles.
- Hand over properly. Documentation, knowledge transfer, and a backlog you can actually use.
What you can expect
- Clear scope & outcomes. Define objectives and metrics you can actually track and deliver; no fluff.
- Senior, hands-on delivery. Work directly with experienced consultants; no layers or delays.
- A solution that survives upgrades & audits. Reduced manual effort & fewer support tickets; less custom code — more standard capability.
“Dr Dynamics delivered our D365 F&O e-invoicing setup across 6 countries. Clear approach, fast execution, and a compliant solution with solid monitoring.”
FAQ
How long does a Dynamics 365 Finance & Operations implementation take?
For a single-entity finance implementation with modest integration and no major customisation, six to nine months is realistic. Multi-country, multi-company rollouts with integration and data migration complexity usually take twelve to eighteen months per wave. Aggressive timelines are possible but typically pay for themselves in technical debt afterwards.
Should we customise Dynamics 365 or stay standard?
Stay standard wherever the process can be adapted. Customise where the business genuinely differentiates, compliance demands it, or standard capability creates unacceptable manual work. Every extension is a future upgrade cost — so the bar should be real business value, not executive preference. We document the decision so nobody wonders later why the code exists.
What is the best implementation methodology for Dynamics 365 F&O?
Microsoft Success by Design provides a sound framework — particularly the solution blueprint, design reviews, data migration strategy and go-live readiness checkpoints. The method matters less than the discipline of using it honestly: real risks logged, real decisions documented, and reviews used to change behaviour rather than tick boxes.
How do we scope a Dynamics 365 rollout without scope creep?
Anchor scope to business outcomes rather than feature lists, freeze the process scope after fit-to-standard workshops, use a formal change board for in-flight changes, and keep a 'not now' list for ideas that belong in a later wave. The biggest killer of rollouts is comfortable ambiguity — we work to remove it early.
How many environments do we need for a D365 F&O project?
At minimum: DEV, BUILD, TEST and a production tier (Sandbox + Production). Larger programmes add dedicated environments for data migration, performance testing, training and hypercare. Environment strategy should be defined before development starts — retro-fitting it later is painful and slows the team.
Get your fastest-path plan
Bring the state of your programme — your Dynamics version, your go-live date and what's worrying you. We'll come back with a one-page fastest-path plan within 48 hours.