Skip to content
← All case studies
ERP & group data architecture Internal work sample

Multi-ERP reporting router

Unified roughly twenty entity types for 128 live companies through one metadata-driven engine, reconciling three ERP API generations into a controlled reporting model.

128
Companies live
~20
Entity types unified
3 reconciled
API generations

Evidence inputs

  • 128 operating companies use the router across legacy Web Services, OData v2 and an Advanced Analytics beta API.
  • Power Query (M) · TMDL · DAX

Transformation

  • Built one parameter-driven function that resolves source, company and entity type from metadata.
  • Loaded the output into a conformed TMDL star schema for consistent measures.
  • Added a Benford leading-digit anomaly check to the general-ledger fact.

Controls & assurance

  • Added companies and entity types through configuration rather than new queries.
  • Isolated API differences behind the router so source changes remain contained.

Output

  • A single engine serves roughly twenty entity types for 128 companies across three reconciled API generations, feeding one conformed star.

Business value

  • Turns fragmented ERP access into one maintainable, auditable source for group reporting.
  1. Problem

    Group reporting had to reconcile the same entity types across three API generations without multiplying queries by company and source.

  2. Approach

    Built one parameter-driven function that resolves source, company and entity type from metadata.

  3. Outcome

    A single engine serves roughly twenty entity types for 128 companies across three reconciled API generations, feeding one conformed star.

Business value

Turns fragmented ERP access into one maintainable, auditable source for group reporting.

Transformation route

  1. 01

    Built one parameter-driven function that resolves source, company and entity type from metadata.

  2. 02

    Loaded the output into a conformed TMDL star schema for consistent measures.

  3. 03

    Added a Benford leading-digit anomaly check to the general-ledger fact.

Decision log

  • Added companies and entity types through configuration rather than new queries.
  • Isolated API differences behind the router so source changes remain contained.

This case study proves

  • Forensic analytics (Benford's Law) Data & Reporting Applied

Full skill evidence →

What I learned

  • Source decoupling lets the group add companies and absorb API changes without rebuilding reports.

Future improvements

  • Promote the beta API path after stabilisation and extend anomaly controls.

← All case studies · Discuss this work →