You may have sat in enough boardrooms to know what the week before an annual report filing looks like.
Someone is working late. Someone is chasing a version of a file. And somewhere, a very senior person is asking a very simple question that nobody can confidently answer:
“Are we sure these numbers are right?”
This is not a people problem. These are capable, experienced teams.
This is a process problem. And it starts with a fundamental misunderstanding of what an ERP was built to do.
ERPs Capture. They Don’t Communicate.
SAP. Oracle. Dynamics. These are extraordinary systems. They were designed to record transactions, manage operations, and store data at scale. They do that well.
But they were never designed to produce a Board Pack. Or an Annual Report. Or a BRSR filing. Or an investor deck that agrees with everything else in the room.
The moment reporting begins, most organisations quietly walk away from their ERP and open Excel.
And that is where the problem starts — every single time.
The 80/20 That Nobody Talks About
Finance teams spend roughly 80% of their reporting cycle doing one thing: getting the numbers right.
Reconciling. Cross-checking. Chasing confirmations. Fixing formulas. Resolving the fact that three people have three versions of the same file.
That leaves 20% of the time for the actual work — the narrative, the context, the story that turns a set of numbers into something a board, a regulator, or an investor can act on.
Every CFO I speak to knows it should be the other way round.
“I want my team to spend 80% of their time on telling the story and 20% of time running behind fixing their disclosures”
~CFO of a CK Birla
The numbers should be settled early. The story should get the attention.
But the structure of most reporting processes makes this nearly impossible.
What 100 CFOs and Company Secretaries Told Us
We spoke to 100 CFOs and Company Secretaries across organisations in India — people who own the annual reporting process, or co-own it.
We weren’t looking for complaints. We were looking for patterns.
And one came through clearly. Almost word for word, across organisations of different sizes and industries:
“We know the timelines are stringent. There’s not much we can do about it.”
That sentence stayed with me.
Not because it’s wrong — the timelines are real, and the pressure is real. But because it signals something more concerning than a deadline problem.
It signals acceptance.
These organisations have stopped questioning whether the process could be different. The last-minute scramble has become the plan. The quarterly and annual fire drill has become, quietly, the recurring tradition.
The Planning Paradox
Some organisations do plan ahead. They start earlier. They build in buffers.
And yet — the problems repeat.
Because the issues are not in the calendar. They are in the infrastructure.
The data still lives in disconnected tools. The review process still happens over email. Compliance checks still happen manually, at the end, when it is too late for them to be anything other than stressful. The design team still receives content that turns out to be the wrong version.
Starting earlier just means the chaos begins earlier.
Until the underlying process changes, the outcome does not.
The Problem, Team by Team
This is worth being specific about. Because the reporting process involves more than one team — and each team carries its own version of the same burden.
| The CFO and Finance Controller cannot be fully confident that what goes out the door is accurate and consistent. Not because they are not thorough, but because there is no single source of truth. There are spreadsheets, and there are the people managing them. |
| The Company Secretary needs every filing to be compliant and defensible. But when the process runs across email threads and shared drives, there is no audit trail. No record of who approved what, and when. |
| Investor Relations needs the investor deck to agree with the Annual Report. In theory, this should not be a concern. In practice, when two documents are built separately from different source files, it frequently is. |
| Auditors and Big 4 reviewers spend more time chasing current versions of documents than reviewing them. This is not what their time is for. |
| Design agencies receive content at the last minute that turns out not to be final. The pressure compounds into mistakes, misses and exorbitant efforts teams are put into review. Work gets redone. Deadlines compress further. |
Five teams. Five versions of the same frustration.
Two Things Need to Change. In this Order.
The organisations that have genuinely improved their reporting process have done two things. And they have done them in this order.
First, they changed the assumption.
They stopped treating the scramble as inevitable. They asked — seriously, not rhetorically — whether this process could look different. That shift in perspective is what makes everything else possible.
Second, they changed the infrastructure.
Not their ERP. The ERP stays. It does what it does well.
But between the ERP and the filed document, there is a gap. And that gap is where most of the pain lives. Purpose-built disclosure management technology was designed specifically to close it.
In the current environment — where regulatory requirements are expanding, reporting timelines are not getting longer, and AI-led tools are reshaping what is possible — digital maturity in this space is no longer optional. It is becoming the baseline expectation.
The organisations moving now will be better placed. The ones waiting for a crisis to force the change are already behind.
What Purpose-built Looks Like
IRIS CARBON® Disclosure Management was built for this problem — specifically, and deliberately.
It does not replace your ERP. It connects to it. SAP, Oracle, Dynamics, Excel — wherever your data lives, IRIS CARBON pulls from a single source. One version of numbers. Always current.
From there, every team works in one place.
Authors draft. Reviewers comment and approve. Compliance checks are built into the workflow — not added at the end as an afterthought. Design teams receive final, approved content directly, without back-and-forth. Auditors review in a shared, auditable workspace.
The output covers every disclosure the organisation needs — Annual Reports in multiple languages, BRSR and ESG filings, XBRL and iXBRL filings, stock exchange submissions, Board Packs, investor decks, press releases, and internal management reports.
The result is not just a faster process. It is a more defensible one. Less risk of error. Less risk of version mismatch. Less of the reputational exposure that comes from a report that had to be restated.
Not just faster. De-risked.
A Straightforward Conclusion
Your ERP was built to capture data. It does that well. But reporting is not data capture — it is communication. And the gap between those two things is where most organisations lose time, accuracy, and confidence every single cycle.
If the problems described here are familiar — if your teams are having the same conversations every reporting period, reaching the same exhaustion point, and accepting it as normal — that is worth questioning.
The process can be different. The technology exists. And the time to implement it is not the month before your next filing.
If you believe the solution fits the problem, we should talk.
IRIS CARBON is built for exactly this.
