An integrity layer is the governed set of rules, tests, and reconciliations between a company's source systems and everything that reads from them. It has four parts: rules that codify business logic, detection that tests every refresh, anchoring that ties every figure to an independent source, and extraction that feeds every audience from one proven source.
Every finance team I've worked with had two things. They had systems: an ERP, subledgers, billing platforms, a folder of workbooks everyone agreed not to touch. And they had reports: the close package, the board deck, the monthly variance review.
What almost none of them had was the thing in between.
Between the systems and the reports sits a layer of work that decides whether the numbers are right. Someone maps accounts. Someone corrects the prices the billing system got wrong. Someone knows one customer is billed through a partner and has to be reclassified. Someone ties the result back to the trial balance before it goes out.
That work exists in every company. The question is where it lives. In most, it lives in people.
The layer nobody designed
When the correction logic lives in people, it looks like this. It's rebuilt every period, a little differently, by whoever has the file that month. It depends on memory. It's checked after the report is assembled, not before. And when the person who knows it leaves, the knowledge leaves with them.
None of this is negligence. It's what happens when a company grows faster than its reporting design. The layer was never designed. It accumulated.
An integrity layer is that same work, designed on purpose.
A working definition
An integrity layer is the governed set of rules, tests, and reconciliations between your source systems and everything that reads from them. It proves your data is right before people or AI rely on it.
It has four parts.
Rules. Your business logic, written once and owned by your team. Account mappings, classifications, corrections, and exceptions live in a rulebook your team can read and edit. A new situation next month becomes a new row, not a new workaround.
Detection. Every refresh tests the data against those rules. The records that break them surface on their own, before they reach a report, instead of turning up during review.
Anchoring. Every figure ties to an independent source: the trial balance, a control total from the source report, a record count from the source file. If it doesn't tie, it doesn't ship. A model that can't prove itself is an opinion.
Extraction. One proven source feeds every audience. Leadership reporting, working papers, and AI tools all read the same data, instead of each one pulling raw from the ERP and cleaning it differently.
The foundation under every report
It's tempting to hear this and picture a reporting tool. A dashboard shows you numbers. An integrity layer is the reason you can trust them.
That distinction matters because most reporting investments start at the top. A company buys a visualization tool or a new ERP module, connects it to the same inputs, and gets the same exceptions in a better-looking format. The problem was never the presentation. It was the missing layer underneath.
The integrity layer is built on the data you already have. Excel stays where it's strong: analysis, rulebooks, working papers. The consolidation, validation, and reporting move into one governed model.
What changes when it exists
The close stops waiting on other departments to correct their data, because the corrections are rules the finance team owns. Review shifts from finding errors to confirming results, because exceptions surfaced before the report was built. Leadership questions get answered from a source that's already proven, instead of a new research project each time.
And the knowledge stops living in one person. It lives in a rulebook anyone on the team can read.
Where to start
You don't start by building. You start by finding out what your integrity layer already is: which rules exist only in someone's head, which reconciliations happen after the fact, which numbers can't be tied to anything outside the file they came from.
That inventory is usually the most valuable document a finance team has never written.
If you want a second set of eyes on yours, that's what the Systems Diagnostic is for. Start with a free 30-minute call.