When the Numbers Are Right and the Picture Is Still Wrong

Financial reporting tends to evolve around accounting conventions rather than the questions boards need answered. A package can satisfy audit requirements while leaving the operating picture unclear. Is your reporting driving decisions or just fulfilling a routine?


Boards receive far more financial information than they can realistically use. Whether the reporting helps directors understand what is actually happening in the business matters more than whether it satisfies audit requirements."

Financial reporting tends to accumulate over time without anyone making a deliberate decision to add to it. A report gets added to the board package in response to a particular issue. The issue resolves. The report stays. After enough cycles, the package reflects the organization's history of problems rather than the questions the board needs to answer today.

When Reporting Serves the Business

The test for any financial report is whether it helps the board answer the questions that matter most to the business. Where is the organization actually generating margin? Which products, services, or customer segments are carrying the performance? What parts of the operation are consuming management attention without producing acceptable returns?

When reporting is organized around accounting conventions rather than operating drivers, those questions become surprisingly hard to answer even with a full board package in front of you.

Aggregation is one of the more common sources of confusion. Product revenue, service revenue, recurring revenue, project work, and one-time activities get blended together because that is how the system exports the data. The board sees total revenue growth while the underlying economics may be moving in a very different direction.

A related problem is when businesses with fundamentally different economics are allowed to disappear inside a single summary. A common example is services quietly losing money because they are treated as support activity rather than as a business with their own margins, utilization, and pricing discipline. The financials may be technically correct while still failing to provide useful visibility into how the business is actually performing.

The CFO's Obligation to the Board

A CFO's responsibility is more than producing financial statements. It is to give management and the board enough visibility to make sound decisions about the business.

Controllers and audit firms tend to prefer consistency because it simplifies comparison and process control, and that preference is legitimate from an accounting standpoint. It does not always produce reporting that helps a board exercise meaningful oversight.

Restructuring reporting to serve decision-making may require organizing reports around operating drivers instead of accounting categories, consolidating multiple reporting views into a single understandable picture, or separating businesses with different economics so their performance is visible on its own terms. None of that is technically complicated. It requires someone to decide that clarity is the goal, and to push until the reporting reflects it.

Boards that leave that question entirely to the finance organization are accepting the reporting structure they inherited rather than the one they need.

Stepping Back From the Numbers

A useful discipline for boards is to step back periodically and evaluate the reporting package itself rather than just the numbers inside it. They should be asking whether the financials are helping them make sound decisions or simply fulfilling a governance routine.

What reports is management actually using to run the business? How does that compare to what the board receives? Where are the gaps between what management sees and what the board sees, and what do those gaps reveal about how operating performance is being communicated upward?

A reporting package that explains activity without improving understanding does not give directors the visibility required to do their job. The board's responsibility is to keep asking whether the information it receives is genuinely serving that purpose until the answer is yes.

About the author

Andy Tomat

Andy Tomat

Founder

Andy Tomat is a board director and corporate development executive with more than three decades of experience guiding organizations through acquisitions, strategic growth decisions, and financial oversight across industrial technology, automation, robotics, AI, and nonprofit settings.