Data Platform, Power BI & Power Platform Engineering Nordic & EU delivery Direct email access

Turn ERP Data Into Governed Reporting and Workflow

DevNord builds EDW architecture and ETL pipelines that feed Power BI dashboards & financial reporting, Power Apps (Canvas & Model-driven), Power Automate and Dataverse connected to D365/AX. We add SharePoint integration, custom portals and automated document workflows, with one governed reporting model and Playwright regression coverage for the journeys that finance relies on.

1Governed reporting model
90%+Automated regression coverage
30 daysPost-launch hypercare included
System architecture

Input layers → DevNord pipeline → multi-cloud infrastructure → security & observability

This is the service-specific architecture we design and operate. Inspect any node to see its role, the engineering or QA control around it, and how risk is contained.

01 / INPUT & CURRENT STATE02 / DEVNORD ENGINEERING + QA PIPELINE03 / MULTI-CLOUD INFRASTRUCTURE04 / SECURITY & OBSERVABILITYScattered ERP Data — Finance, HR and operations data sits in separate ERP tables, exports and file shares with no agreed definition of a metric.Scattered ERP DataERP silos & exportsSpreadsheet Workflows — Spreadsheet workflows pass between teams by email, hiding approvals and making every version a new source of truth.Spreadsheet WorkflowsManual handoffsManual Financial Reports — Manual financial reports are rebuilt each month, so close depends on copying figures rather than reconciling them.Manual FinancialReportsMonth-end close delaysEDW Model — EDW architecture defines conformed dimensions, financial hierarchies and one governed reporting model across ERP sources.EDW ModelGoverned data modelETL Pipelines — ETL pipelines load incrementally with schema checks, row counts and reconciliation against the source before publication.ETL PipelinesIncremental loads & validationDataverse Connections — Dataverse connected to D365/AX carries workflow state and metadata without duplicating the ERP as a second system of record.Dataverse ConnectionsDataverse connected to D365/AXPower BI Dashboards — Power BI dashboards and financial reporting read the governed model, giving finance and operations the same numbers.Power BI DashboardsFinancial dashboardsPower Apps & Automate — Power Apps (Canvas & Model-driven) and Power Automate replace email approvals with automated document workflows and auditable state.Power Apps & AutomateCanvas & model-drivenSharePoint Portals — SharePoint integration and custom portals give partners a single entry point for documents, tasks and published reports.SharePoint PortalsSharePoint integrationIAM & Least Privilege — Role-based access, managed identities and short-lived credentials are applied to every environment in this engagement. This is applied to the Data Platform, Power BI & Power Platform Engineering delivery.IAM & Least PrivilegeAzure Entra ID / AWS IAMNIS2 & GDPR Controls — Encryption, residency, retention and evidence are encoded as controls so the architecture can be audited, not just described. This is applied to the Data Platform, Power BI & Power Platform Engineering delivery.NIS2 & GDPR ControlsPolicy as code · EU regionsObservability & Audit Trails — Dashboards and alerting cover the paths changed by this service, with immutable audit trails for release and access decisions. This is applied to the Data Platform, Power BI & Power Platform Engineering delivery.Observability & AuditTrailsLogs · metrics · traces · alerts
01 / INPUT & CURRENT STATE
02 / DEVNORD ENGINEERING + QA PIPELINE
03 / MULTI-CLOUD INFRASTRUCTURE
04 / SECURITY & OBSERVABILITY

Tap any node to inspect it.

Hover over a node to inspect it.

Node inspectorSelect any component to see what it does, which control protects it and how we hand it over.

Development plan

Week-by-week roadmap to production

An indicative 12-week cadence for a full engagement. The exact calendar, milestones and price are fixed in your EUR (€) or SEK (kr) proposal after discovery.

Indicative cadence — finalised in your fixed-scope proposal

01
Week 1–2

Phase 1: Discovery, Requirements & Architecture Blueprint

ERP sources, spreadsheet workflows and manual financial reports are inventoried before the EDW architecture is designed.

02
Week 3–6

Phase 2: Core Sprint Engineering & Iterative Milestones

One governed reporting model and the first ETL pipelines land with row counts and source reconciliation.

03
Week 7–9

Phase 3: Hybrid QA Validation (Manual UAT + Automated Regression)

Dataverse connected to D365/AX carries workflow state for Power Apps (Canvas & Model-driven), Power Automate and automated document workflows.

04
Week 10–12

Phase 4: Zero-Downtime Production Deployment & Handover

Power BI dashboards, custom portals and SharePoint integration pass manual UAT and a Playwright QA gate; 30 days of hypercare follow go-live.

How We Work

Delivery standards that make outcomes predictable

Every engagement runs with the same operating model: senior squads, transparent ownership and written evidence at every gate.

Two-week sprint cadence with demoable increments and a written decision log.

Transparent Git repository ownership — repositories land in your organisation from day one.

Infrastructure-as-code (Terraform or Bicep) for every environment, reviewed and reproducible.

Fixed-scope proposals in EUR (€) or SEK (kr), with capped B2B consulting retainers when scope is still emerging.

Bilateral NDA signed before source code, architecture data or credentials are shared.

Technical overview

What we actually engineer

Reporting fails when every team defines its own metric. DevNord establishes EDW architecture with one governed reporting model, then builds ETL pipelines that validate schemas, count rows and reconcile against the ERP before anything is published. Power BI dashboards & financial reporting read that model, so finance and operations work from the same figures.

Workflows are implemented inside the platform: Dataverse connected to D365/AX holds state for Power Apps (Canvas & Model-driven) and Power Automate, while SharePoint integration and custom portals deliver automated document workflows to partners. Playwright E2E covers the reporting and approval journeys. Proposals are fixed scope in EUR (€) or SEK (kr), with one governed reporting model as the first milestone.

The bottleneck

Finance and operations rarely report the same number

ERP data is exported into spreadsheets, copied into reports and emailed between teams. Every month-end close repeats the same manual reconciliation, and workflow approvals leave no trace outside an inbox. Without a governed reporting model, nobody can say which figure is authoritative.

  • EDW architecture absent, so each report defines its own metrics
  • ETL pipelines replaced by manual exports and fragile file drops
  • Financial reporting rebuilt in spreadsheets every closing period
  • Document approvals spread across email, SharePoint and custom portals
The DevNord approach

One model, repeatable pipelines, workflows inside the platform

We define EDW architecture and one governed reporting model, then build ETL pipelines with validation and reconciliation from D365/AX and other ERP sources. Power BI dashboards & financial reporting read that model; Dataverse connected to D365/AX carries workflow state for Power Apps (Canvas & Model-driven) and Power Automate, while SharePoint integration and custom portals handle documents.

  • Conformed EDW model with owned definitions for finance and operations
  • Incremental ETL pipelines with row counts and reconciliation checks
  • Dataverse connected to D365/AX for Power Apps and Power Automate flows
  • Automated document workflows, custom portals and Playwright regression gates
Business outcome

What changes after this engagement

01

One reporting model

Power BI dashboards & financial reporting use the same governed figures, ending spreadsheet version wars.

02

Workflows with evidence

Power Automate and automated document workflows record every approval where an auditor can find it.

03

Reusable platform

Dataverse connected to D365/AX, SharePoint integration and custom portals give teams one place to work.

Deliverables checklist

Concrete artefacts you receive at handover

These are service-specific, reviewable assets — not status reports. Your team owns each one.

  • EDW architecture
  • ETL pipelines
  • Power BI dashboards & financial reporting
  • Power Apps (Canvas & Model-driven) & Power Automate
  • Dataverse connected to D365/AX
  • SharePoint integration, custom portals & automated document workflows
Questions, answered

The things decision-makers ask us first

Still unsure? Write to us at [email protected] — we reply in plain language, without a sales script.

Which data sources do you connect?

We build ETL pipelines from Dynamics 365 F&O, AX 2012 R2/R3, SQL sources and file drops into an EDW architecture. Dataverse connected to D365/AX carries workflow data without replacing the ERP as the system of record.

Do you replace our existing financial reports?

We move financial reporting into Power BI dashboards & financial reporting on one governed model. Existing spreadsheet logic is documented first so the close keeps the checks it relies on.

Can you build both canvas and model-driven apps?

Yes. We deliver Power Apps (Canvas & Model-driven) with Power Automate for automated document workflows, backed by SharePoint integration and custom portals where partners need a single entry point.

How is the platform tested after handover?

ETL validation and reconciliation run with every load, while Playwright covers critical reporting and approval journeys to reach 90%+ automated regression coverage on the paths finance uses.

Next step

Put ERP data behind one governed model

Start with a fixed-scope review of sources, reports and workflows, and receive an EDW architecture and Power Platform sequence your finance and operations teams can approve.