Native BI Inside an LMS Ecosystem. I Didn’t Think That Existed

When reporting stops being an integration problem and becomes part of the core platform

This conversation emerged during internal CODIX discussion following a recent review of iMX Analysis and Decision (iMX AD) between Chris Coleman, Sales Director, and Hirisha Bayramovska, Lead Business Intelligence Analyst. What started as a comment on reporting architecture turned into a broader exchange on how lenders typically build - and maintain - their BI stacks inside lending environments. And whether the industry’s standard separation between core systems and BI tools is still justified.

Chris:

A few things stood out when I joined CODIX. This one genuinely surprised me.

In asset-based lending, factoring, and receivables finance, the reporting model is almost always the same: the lending platform runs operations, and a separate business intelligence stack handles reporting. A data warehouse sits in between, pulling data out, transforming it, and feeding tools like Power BI. Then someone owns the pipeline that keeps it all working.

It’s become accepted as just “how it’s done,” but it’s a significant operational burden.

Every change in the business means changes in the data model, the integrations, and the reporting logic. Over time, maintaining that pipeline becomes a permanent function in itself.

Where it becomes even more critical is funder reporting. Non-bank lenders are constantly required to produce tailored views of the book for different capital partners, in different formats and cycles. That’s not a one-off exercise - it scales with the business.

So, when I saw how CODIX handles this inside iMX, I had not seen it done this way before. Instead of a fragmented architecture, reporting sits inside the same ecosystem as the core system.

Hirisha, you live in this every day - can you explain how it actually works?

Hirisha:

Sure. And I’ll admit I tend to get a bit evangelical about this part.

The capability is called iMX Analysis and Decision, or iMX AD. It is a centralised business intelligence and reporting platform that sits within the iMX ecosystem rather than alongside it.

In a typical setup, data has to move through several layers: extraction from the lending system, transformation, loading into a warehouse, and then consumption by a separate BI tool. Each layer adds complexity and maintenance overhead.

In practice, the hardest part is rarely the dashboard itself but keeping the data pipeline stable and aligned as the business evolves.

iMX AD removes that dependency by embedding the ETL framework directly into the platform. Operational data flows into a dedicated analytical model as part of the system itself, so teams work on a governed dataset instead of maintaining integrations.

That shifts the effort away from infrastructure and toward analysis.

Take an ageing report. In most organisations, that becomes multiple versions depending on who is using it - management, credit teams, funders. In iMX AD, it is one dataset that can be adapted: ageing bands defined by policy, different date bases, dynamic currency selection, and drill-down from portfolio to invoice level without rebuilding anything.

One model, multiple perspectives.

And it doesn’t come at the cost of usability. The dashboards are interactive, designed for day-to-day decision-making, with full drill-down and filtering without technical support.

Chris:

And that’s the key commercial point.

As lenders scale, reporting complexity scales with them - especially funder reporting. New capital partners typically bring new requirements, new logic, and more reconciliation work.

In most architectures, that translates directly into more warehouse development and integration overhead.

Here, the reporting pipeline is already part of the core system. New requirements are configured, not engineered. What used to be a project becomes a setting.

Hirisha:

And it also fits into daily operations.

Common questions - what was collected today, what moved on a facility this month - can be answered directly inside iMX without switching to a BI tool.

More structured reporting can be scheduled and distributed automatically via email, shared folders, or intranet/extranet delivery depending on the organisation’s setup.

And when deeper analysis is needed, reports can be embedded directly into the iMX interface so users stay within the operational workflow.

It is also open. SQL users can query the analytical model directly, while business users can build reports through a guided interface. A full metadata layer documents every field and relationship, making the model transparent and extendable.

Chris:

That’s what makes it commercially meaningful.

Most organisations accept reporting as a distributed architecture: core system, warehouse, BI tool, integration layer - all stitched together and maintained internally.

With iMX AD, that stack is unified at the source. The ETL, data model, and reporting layer sit inside the same platform, maintained by the same vendor, aligned by design rather than integration effort.

It doesn’t eliminate analytical complexity - but it removes the infrastructure burden of holding everything together.

And compared to the market, that difference matters.

It may not be a single login. But it is a single architectural truth.

And that’s what we mean when we say convergence isn’t a slogan. It’s architecture.

STOP INTEGRATING. START CONVERGING.