Are Your Reporting Processes Still Keeping Pace With Your Company?

Some things only become obvious in hindsight. A question from your auditor here, a new subsidiary there, one tricky accounting judgment call somewhere else. In the moment, each of these feels like an isolated event. You deal with it, tick it off, move on. It's only once enough of these have piled up that a pattern emerges: it was never really a series of one-offs. It was the same underlying issue all along.

If any of the following sounds familiar, it's worth taking a closer look.

Three signals that actually belong together

Your auditor keeps asking the same question.

A recurring query on the same balance sheet item, a finding that showed up last year and shows up again this year. Taken one at a time, each instance looks like its own isolated topic to clear up. Looked at over several years, it's often a pattern: a sign that the underlying issue was never really resolved structurally, just answered piecemeal, year after year.

The company has grown, but the processes haven't kept up.

A new subsidiary, a new line of business, more complexity in consolidation while the reporting processes underneath are still, at their core, built for an earlier, simpler stage of the company. This rarely shows up on a single day. It creeps in, until the effort required for closings and reports becomes noticeably higher than it should be.

One tricky edge case exposes how unstructured everything else really is.

A complex contract, an unusual valuation question, you dig deep to resolve the specific issue, and in the process notice that documentation and responsibilities elsewhere have grown just as organically, rather than being deliberately set up.

Why it's never really a one-off

All three signals point to the same underlying issue: reporting processes and structures that fit an earlier stage of the company, but not the one it's in now. That's not unusual in itself. Few companies design their reporting from day one for the size and complexity they'll eventually reach.

It tends to become visible above all when something changes on the team. As long as the same people are handling things day to day, they quietly compensate for a lot of gaps. They know the exceptions, the connections, the unwritten rules. When new colleagues join as the company grows, or when a role changes hands, what was only ever carried in people's heads, never written down, becomes visible for the first time. The team change isn't the cause – it just brings to light what was already there.

And the requirements grow too

Growth doesn't just test how well existing processes still fit – it also raises what's expected of them. That happens on two fronts.

Internally, as the company grows, more stakeholders expect reliable, traceable figures: management, shareholders, over time perhaps investors or an advisory board too. What used to be an informal overview now needs to be delivered systematically and on time, not assembled ad hoc when someone asks.

Externally, growing past certain size thresholds often brings additional statutory reporting obligations: for example around financial statements, the management report, or group-level consolidation. These thresholds rarely announce themselves at short notice. Knowing you'll grow into additional requirements ahead of time means you can prepare for them, rather than reacting once the obligation is already in effect.

What you can check yourself, right now

A first check doesn't require much effort:

• Line up your last two or three audit findings or follow-up questions. Does a pattern emerge: the same item, the same type of question?

• Compare when your reporting processes were last deliberately reviewed against your company's last major growth step. Often, more time has passed than you'd think in the day-to-day.

What this typically involves

An outside perspective usually doesn't just confirm that something's off, it also shows fairly precisely where. In practice, this tends to come down to the following:

Professionalising and documenting processes

Writing down workflows that have so far just been "done the way they're done" and, where it's needed, actually adjusting the substance, not just writing down however things happened to grow.

Defining and documenting responsibilities

Who is accountable for which balance sheet item, which special case in writing, not just known because "that's always been that person's job."

Working through recurring judgment calls properly, once

Valuation assumptions, cut-off questions, recurring special items that get improvised afresh every year instead of being reasoned through once, documented, and then applied consistently.

Adding controls where they're missing

Not as a full-blown internal control system project, but targeted, at the specific points where nobody currently checks what goes through.

Setting up or sharpening a closing calendar

A clear timeline with assigned responsibilities for the monthly or annual close takes out much of the last-minute scramble that otherwise only becomes visible right before the deadline.

Clarifying handoffs between areas

Who delivers what, at what quality, by when, to whom, a common weak spot especially between newly added entities or departments.

Not every issue is equally urgent. In practice, it's about tackling the points that most often cause follow-up questions or extra work first, rather than overhauling everything at once.

Such a stock-take doesn't automatically produce the answer "you need a new tool." More often, it's a mix: in some areas, it genuinely makes sense to think about a suitable reporting tool. In others, the fix is much closer at hand: documenting processes properly, building in controls, clearly defining and recording responsibilities. The two aren't mutually exclusive, but the order matters: without documented processes and clear responsibilities, a new tool won't solve the underlying problems either if anything, it will just reproduce them faster.

A word on digitalisation and AI, since barely any article on finance processes goes without one: for operational tasks, capturing invoices, payment approvals, dunning, automation brings real benefits, no question. For the questions at stake here, something different applies: an automated system only executes the logic and assumptions that were built into it beforehand. If that logic hasn't been properly thought through and documented, errors or inaccuracies just get reproduced faster and less visibly than before. Solid governance and clean process documentation are therefore the precondition for automation in reporting to work reliably at all – not its opposite.

The right time: never too late, but easier earlier

Nobody is ever perfectly prepared nor should that be the goal. But if it's foreseeable that additional reporting obligations are coming your way, or if an exit or a larger financing round is realistically a few years out, it's worth starting to think in that direction now not by overhauling your entire reporting at once, but by starting to look at it deliberately, before the deadline is bearing down on you. The difference is usually not whether you start, but how much calm you still have left when you do.

The value of an outside perspective

Much of this can be initiated internally. At some point, though, an outside view helps not because the knowledge is missing internally, but because proximity to day-to-day work makes it harder to see the bigger picture.

In practice, this looks like the following: instead of a questionnaire, we go through the individual reporting areas together with those responsible: consolidation, provisions, the recurring special items. In conversation, things often come up that would never appear on a form, simply because nobody would know to ask about them. What matters isn't the standard questions, but the critical "why" questions: why is it done this way, what happens if this assumption changes, which are rarely asked internally, because everyone involved shares the same unspoken assumptions. A second component is a systematic look at audit findings from recent years: not just whether they were resolved, but whether a pattern emerges across several years.

The result is not a general impression, but a concrete, prioritised list, which issues are connected, and what a sensible next step would be.