EPIQ Global

EPIQ Global.

A US legal-services firm whose monthly reporting ran on SAP BW with Analysis for Office on top. Every month, analysts rebuilt the same workbooks by hand. The numbers now come from SAP Datasphere, an agent writes and runs the SQL, and the report comes back finished – inside Teams.

EPIQ Global – A reporting agent with SAP Datasphere as its source of truth. It knows the report definitions, writes the SQL against Datasphere and HANA, runs it through DuckDB for the assembly step, and produces the finished report as Excel, PDF or DOCX – versioned, so last month's is still there next to this month's. The analyst asks for the report in the Microsoft Teams app and gets it back there. The spreadsheets stayed; the rebuilding did not.

* Not real data. Names, figures and identifiers are invented, and anything under NDA is stripped from the capture.

What existed

The data was right and the process was manual. BW held the figures, Analysis for Office pulled them into Excel, and a small team spent the first days of every month rebuilding the same set of reports: refresh, reconcile, reformat, redistribute. Any change to a report meant doing it again next month, by hand, in the same way.

What was built

A reporting agent with SAP Datasphere as its source of truth. It knows the report definitions, writes the SQL against Datasphere and HANA, runs it through DuckDB for the assembly step, and produces the finished report as Excel, PDF or DOCX – versioned, so last month's is still there next to this month's. The analyst asks for the report in the Microsoft Teams app and gets it back there. The spreadsheets stayed; the rebuilding did not.

Where it runs

Datasphere, HANA and the agent all sit inside the client's own SAP and Microsoft landscape. The queries run where the data lives. Report output stays in the client's tenant, and the models are called from within it.

Architecture
Checking…
© 2026 atopos GmbH
ImprintPrivacy