Skip to content
Dynamic Corporate Transformation

DCT Advisory

ERP and enterprise systems

Advisory on the client's side of the table

From boardroom to system

Transformation is not complete when the strategy changes. It is complete when the enterprise operates differently: when the processes, controls, data, decision rights and management reporting the strategy requires are embedded in the systems the enterprise runs on every day.

DCT decides what the enterprise must become. The ERP is one of the principal mechanisms through which it becomes operational.

  1. Strategy
  2. Enterprise transformation
  3. DCT Helix
  4. Process and operating-model design
  5. ERP enablement
  6. Execution
  7. Data and performance monitoring
  8. Adaptation and re-optimization

The execution architecture gap

The distance between the future state a leadership team has approved and the operating state that its processes, systems, data, controls and reporting still encode.

Executives approve a new strategy, operating model, structure, digital agenda, capital-allocation model or performance framework. The ERP goes on encoding the old workflows, reporting, controls, responsibilities, product structures, cost centers, approval hierarchies and decision processes. The strategy describes one enterprise; the systems still run another.

In DCT terms, the systems are where three of the seven moves meet the real enterprise. What the master data and structures can record limits what can be represented. What the workflows and approvals allow decides what is executed. What the reports compute is what is monitored. When the systems encode the old operating model, the enterprise is represented, executed and monitored as the company it used to be.

That is why a transformation cannot pass gates G5 and G6 while the gap is open. Benefits count as banked only when they show in the income statement, balance sheet or cash flow, and a new equilibrium is certified only when the new KPIs run in business as usual. Both depend on the systems.

  • Represent

    What is the enterprise, honestly?

  • Execute

    Can we deliver the step without breaking the business?

  • Monitor

    Is it working, and what are we not seeing?

  • G5 · Benefits bankedValue that shows in the income statement, balance sheet or cash flow, not in plans; each wave closed with its interfaces intact.
  • G6 · New equilibrium certifiedThe step holds under measurement and the new KPIs run in business as usual.

Signs of the gap

  • The new structure exists on the organization chart but not in the cost centers.
  • The KPIs the board reviews are assembled in spreadsheets outside the system of record.
  • Approvals still follow the old decision rights.
  • The product and customer hierarchies describe the old business.
  • Benefits cannot be traced in the accounts, so no one can say whether they arrived.
  • The close is slow because reconciliation is manual.

The pattern in public cases

Lidl, 2011–2018

Public-company analysis

The reported root cause: Lidl valued inventory at purchase prices while the standard retail software assumed retail prices, and accommodations made the system slower and costlier.

DCT Helix white paper (October 2026), page 11 (verbatim)

Hershey, 1999

Public-company analysis

Hershey moved purchasing and finance onto new SAP-based systems in January 1999, then switched order-taking, billing, warehousing links and receivables together in July, just ahead of its peak season. Order fulfillment broke down: third-quarter sales fell 12% and net income 18.6%, and the 10-K cites lost sales, higher freight and warehousing costs and excess inventory.

DCT Helix white paper (October 2026), page 11 (verbatim)

Target Canada

Public-company analysis

A critical rung far below readiness. Data at roughly 30% accuracy is a weakest link that, in a Helix Readiness Diagnostic, caps the attainable step at “foundation first.”

DCT Helix white paper (October 2026), page 11 (verbatim)

Public-company analyses from published sources, read through DCT Helix. None of these companies used DCT or DCT Helix.

ERP is a rung, not a project

ERP and core systems

SAP, Oracle and the other platforms that many departments share. Well sequenced, ERP gives every strand a common backbone; mistimed, it forces rework across every strand it touches.

ERP programs are where architecture and transformation most often collide. Treated as a rung, an ERP is sequenced to the departments it serves, with a template laid first and each department stepping onto it in its own window, rather than switched on everywhere at once.

DCT Helix white paper (October 2026), page 34 (verbatim)

ERP and core systems

SAP and SAP S/4HANA are trademarks or registered trademarks of SAP SE in Germany and other countries. Oracle and NetSuite are registered trademarks of Oracle and/or its affiliates. Microsoft and Dynamics 365 are trademarks of the Microsoft group of companies. QuickBooks is a trademark of Intuit Inc. These names are used only to identify the platforms; no affiliation with, sponsorship by or endorsement from their owners is implied.

Discuss your ERP environment