There’s a growing expectation across our sector that housing providers should be able to produce accurate, timely and audit-ready reports on demand. Whether for regulatory returns, compliance monitoring or internal assurance, reporting is often viewed as a technical problem which can just be solved with the right dashboards, platforms or integrations.
But in practice, that’s rarely where the real problem lies. A lot of the challenges I’ve seen around regulatory reporting don’t come from a lack of technology; they come from far more fundamental aspects such as unclear data definitions, inconsistent logic and a lack of ownership over what the data actually represents.
This is particularly timely as housing providers continue to modernise their data platforms while facing higher expectations around auditability, regulatory reporting and data quality.
The illusion of accurate reporting
Most housing providers already have multiple reporting tools; SQL reports, Power BI dashboards and HMS extracts all produce outputs. The problem is that these outputs don’t always agree, so you might have:
- Two reports showing the same KPI but with different results;
- A compliance report that doesn’t match operational figures;
- A regulatory return that requires manual adjustments before being submitted.
At that point, the question becomes: which one is correct? What’s often uncovered is that the discrepancy isn’t caused by the tool but by the logic behind the data. Hidden filters, undocumented assumptions and legacy calculations all play much bigger roles than most people realise.
Buried logic & lack of trust
In one piece of work, we looked at a set of KPIs being reported across both SQL-based reports and a newer analytics platform. On the surface, both outputs appeared to be valid but when you compared them side by side, the numbers didn’t correspond. The immediate reaction was to question the newer platform but the deeper we went, the clearer it became that the problem wasn’t the platform, it was the lack of a shared understanding of the underlying definitions. For example:
- Certain property types were excluded in one report but not the other;
- Historical rules had been applied in the SQL procedures but had never been documented;
- The business logic had evolved over time without being formally updated.
All of this meant that each report was technically ‘correct’ but based on different interpretations of the same data, and that’s a significant problem in a regulatory context.
Audit-readiness – definitions, not dashboards
When we talk about being ‘audit-ready’, the focus is often on the ability to collate evidence quickly or generate reports on demand. But true audit-readiness requires more than that. It depends on the ability to clearly explain:
- What each metric represents;
- How it is calculated;
- What is included and excluded;
- Who is responsible for its accuracy.
Without this clarity, even the most sophisticated reporting solutions will struggle to stand up to scrutiny.
One of the most effective steps taken in improving reporting reliability isn’t technical at all. It involves translating complex system logic into plain English definitions. Instead of relying solely on SQL scripts or stored procedures, this means documenting:
- The exact rules behind each KPI;
- The data sources being used;
- Exceptions and edge cases;
- The rationale behind each inclusion or exclusion.
This creates a shared reference point that both technical teams and business stakeholders can understand and agree on.
Ownership is real governance
Another recurring challenge in regulatory reporting is ownership.
It’s easy to assume that responsibility sits with the data or IT teams, particularly where they manage the reporting platforms. In reality, they’re often working with logic that originates from different parts of the business.
For reporting to be reliable, ownership needs to sit with the business, not just the system. This means:
- Data owners confirming that the correct fields are being used;
- Data stewards validating that the definitions reflect real-world processes;
- Formal sign-off on KPI logic, not just the output of the final report.
In practice, this moves the conversation from “why does the report look wrong?” to “are we all aligned on what this metric should represent?”, and that shift is where meaningful progress takes place.
From reactive fixes to structured governance
A lot of the work around regulatory reporting ends up being reactive, such as investigating discrepancies, explaining differences or making last-minute adjustments ahead of submission deadlines.
Organisations that move beyond this tend to take a more structured approach to governance, including:
- Maintaining a central definition log for KPIs and reports;
- Explicitly documenting all filters, rules and assumptions;
- Aligning logic across systems before building new reports;
- Managing changes to definitions through a controlled process.
This work isn’t always fast but it significantly reduces the need for repeated investigations and builds confidence in the reporting outputs.
Closing the gap between data & compliance
There is a clear push across the sector towards better data practices, more integration, modern platforms and stronger governance frameworks. But technology alone won’t close the gap between operational data and regulatory reporting. That gap is often created by:
- Misaligned definitions;
- Undocumented logic;
- A lack of clarity around ownership.
Addressing these challenges doesn’t always require new tools but it does require a shift in how housing providers approach data and treating definitions and governance as a core part of their reporting processes instead of as an afterthought.
Conclusion
Regulatory reporting doesn’t usually fail because housing providers lack the necessary data or the right reporting tools; it fails when there’s no shared understanding of what the data represents.
Modernisation programmes offer a valuable opportunity to address this, not only by improving platforms, but also by aligning definitions, governance and ownership. Because ultimately, a report is only as reliable as the logic behind it.
Adejoke Ajao is a business intelligence and applications analyst at South Liverpool Homes.
