Financial disclosure management is undergoing a fundamental shift. For decades, finance teams relied on spreadsheets, email chains, and disconnected tools to prepare disclosures — approaches that once worked but now introduce risk in a more regulated environment. Those tools produced disclosures that were, more often than not, good enough. And the habits built around them became so normalized they stopped looking like habits at all — they just became “how reporting works.” These outdated habits persist in financial disclosure management processes across organizations.
That is changing. Regulatory expectations around disclosure quality, consistency, and governance have moved faster than most internal processes have. What was acceptable practice five years ago now carries more risk — audit friction, inconsistency findings, and governance gaps that were once tolerable are increasingly consequential.
Below are ten of the most common outdated practices still present in finance teams today, why each one is losing ground, and how EcoActive is built to replace it with something better.
01. Rebuilding Financial Statement Notes From Scratch Every Cycle
Most disclosure cycles begin the same way: the prior-year report is opened as a reference and notes are rebuilt from scratch. The result is avoidable rework, subtle language drift between periods, and disclosures that depend entirely on whoever ran last year’s report remembering what they did. Big 4 audit firms and standard-setters consistently emphasize that disclosures should be comparable across periods, with changes explained rather than silently introduced. IFRS 18, replacing IAS 1 from 1 January 2027, raises that bar further.
02. Running Financial Statements and Narrative Commentary as Separate Streams
In many organizations, financial statements are owned by the finance team, management commentary and investor narrative by IR or communications, and ESG disclosures by a separate team altogether. The outputs are reviewed independently and assembled into a single report at the end. Without a connection between these streams, a late change to any figure — a revenue line, a key estimate, a balance sheet item — updates one document but leaves others unchanged.
03. Copying Forward Disclosure Language Without Reviewing Changes
Inconsistent disclosures are the predictable result, not of carelessness, but of a process where the same data exists in multiple places with no formal link between them.Copy-forward is one of the most persistent habits in financial reporting. Prior-year language is pasted in, updated for current dates and numbers, and carried forward with minimal review of whether the underlying reality has changed. Used carefully this is efficient; used without review it produces filings that describe a company as it was, not as it is.
The consequences accumulate across cycles: risk disclosures that still treat a materialised risk as hypothetical, accounting policy descriptions referencing treatments changed two cycles ago, and going concern language unchanged despite a materially different liquidity position. These are exactly the discrepancies auditors and reviewers are trained to find.
04. Reading Prior-Year Audit Findings Only After Drafting Has Already Started
Audit findings from the previous cycle are the most precise, specific feedback the disclosure process ever receives. For many finance teams, those findings are reviewed when the auditors deliver them — and then effectively filed until the auditors return. By the time drafting begins, the habits that generated the findings are still in place and corrections become reactive rather than preventive.
Approximately 30% of financial restatements between 2013 and 2022 involved errors in accruals, reserves and estimates — the category that generates the most repeat audit findings
05. Treating Executive Sign-Off as Document Review Rather Than Data Governance
Most disclosure sign-offs are acts of trust: a senior leader reviews the document, confirms it looks complete, and signs. In most jurisdictions, however, executives who sign off on financial reports are personally certifying that the report does not contain material misstatements or omissions — a legal standard that goes well beyond the document looking right.
When the process is not designed to produce defensible outputs — when data lineage, judgment documentation, and cross-section consistency are not captured — the executive signing the report is certifying something the process has not fully verified.
Approximately 41% of SEC enforcement actions against public companies in FY2024 were disclosure and reporting-related — the single largest enforcement category
06. Keeping Key Judgments and Estimates in People’s Minds Rather Than on Record
Every set of financial statements is built on judgment calls: why a provision was set at that level, why a particular accounting treatment was applied, why an estimate uses these inputs rather than those. In many organizations, those answers live in the memory of the person who made them — which works until that person changes roles, leaves, or cannot recall the reasoning twelve months later.
Under IAS 1, IAS 8 and ASC 275, financial statements must disclose key assumptions, methodologies, and sources of estimation uncertainty. Most teams document the resulting number. The reasoning — data inputs, approach taken, alternatives considered — often remains undocumented. When auditors probe a judgment that has not been recorded, the explanation must be reconstructed from memory, which is both slow and unreliable.
“Estimates and underlying assumptions are reviewed on an ongoing basis. Revisions to estimates are recognized in the period in which they are determined.”
07. Assembling Audit Evidence After the Report Is Complete
In many disclosure cycles, the report is built first and evidence gathered second. Once the document is largely complete, the team turns to locating documentation that supports the numbers, judgments, and estimates disclosed. Contracts are tracked down, approvals traced, and methodology notes written from memory.
This is the natural result of a process designed to produce a document, not to capture evidence along the way. Evidence is assembled afterward, under time pressure, by a team already stretched from producing the report. An audit-ready disclosure is structurally different from an audit-responsive one.
Around half of CFOs without a structured finance partner report being fully ready for their next audit
08. Discovering What Needs to Be Disclosed This Year During Drafting, Not Before
Disclosure requirements change every year. Accounting standards are revised, regulatory frameworks add new obligations, and new transactions create disclosure needs the prior-year template does not cover. For many teams, these changes surface during drafting — when the relevant section is being written — rather than at the start of the cycle when there is still time to plan.
A disclosure requirement discovered during drafting is a reactive correction. It compresses an already tight timeline, forces changes to sections already reviewed, and increases the likelihood of errors introduced under pressure. The same requirement identified at cycle start is simply a planning task.
09. Running Multi-Jurisdiction Reporting as Separate, Unconnected Workstreams
A company with obligations in multiple jurisdictions — ESEF for annual reports in Europe, SEC filings in the US, CSRD sustainability disclosures, ISSB-aligned reporting where applicable, and statutory filings in Asia — typically handles each as a separate project with different teams, tools, and data pulls from the same underlying source systems.
The same company, reported across jurisdictions using independently assembled data, will produce filings that diverge on overlapping metrics. Cross-jurisdiction data comparison is increasingly common among regulators and investors, making these divergences increasingly visible.
10. Treating Disclosure as an Annual Event Rather Than a Continuous Process
This is the habit that underlies all the others. The annual report is treated as a project with a start date, an end date, and a filing deadline. Once it is filed, the process resets. Institutional knowledge disperses. Data is not governed between cycles. The next cycle starts from zero.
Disclosure quality is not determined by how hard teams work in the weeks before a filing deadline. It is determined by how data, judgments, and evidence are governed throughout the year. Teams that treat disclosure as a continuous process produce consistently better outputs with less end-of-cycle pressure.
Significant portion of finance team time is spent collecting and validating data rather than governing or analyzing it
How EcoActive Addresses Each Practice
Practice | The Outdated Way | How EcoActive Helps |
01 Rebuilding notes from scratch every cycle | Notes rebuilt manually each year from prior-year reference documents. | Opens each cycle with notes pre-populated from source data, enabling the team to review and update what has changed. |
02 Financial and narrative streams unconnected | Financial, narrative, and ESG disclosures drafted in parallel with no formal cross-check. | Provides a unified environment where one change to a material figure surfaces all sections that reference it. |
03 Copy-forward without reviewing for accuracy | Prior-year language carried forward with minimal review of whether the underlying situation has changed. | Prior-period language carries forward with structured review prompts flagging what may need updating. |
04 Audit findings read mid-drafting not before | Audit findings are reviewed when delivered, then filed until the next audit cycle begins. | Designed to surface prior-period findings at cycle start, with tracking to resolution before drafting begins. |
05 Sign-off as document review, not governance | CFO reviews documents, asks questions, and signs. Process optimized for output, not defensibility. | Approval workflows capture data-level accountability — who validated which figures, with what evidence. |
06 Judgments in people’s minds, not on record | Reasoning behind estimates and judgments lives in the memory of whoever made them. | Enables capture of key inputs, assumptions, and rationale at the time each judgment is made. |
07 Audit evidence assembled after the report | Audit evidence gathered retrospectively once the report is substantially complete. | Designed to capture supporting evidence as the cycle progresses, so documentation exists when auditors need it. |
08 Disclosure gaps found during drafting | New disclosure requirements surface when the relevant section is being drafted. | AI-driven tools help scan applicable frameworks at cycle start, supporting gap identification as a planning input. |
09 Multi-jurisdiction siloed workstreams | Each regulatory obligation assigned to a separate team with independent data pulls from the same source systems. | Supports a single governed environment across SEC, ESEF, CSRD/ESRS, ISSB, GRI, UK FRC, BRSR and more. |
10 Disclosure as an annual event, not a process | Annual report treated as a project. Process resets between cycles. | Designed as a continuous governed disclosure environment — data current, notes carry forward, evidence accumulates year-round. |
What This Means for Finance Leaders in 2026
Four shifts are worth prioritizing for finance leaders navigating this transition:
01 Move from document ownership to data ownership The finance team’s role is not to produce a document. It is to govern a disclosure. The data behind the report — figures, estimates, judgments, evidence — should be managed as a system, not assembled into a file. |
02 Treat the disclosure cycle as continuous, not annual Infrastructure for continuous disclosure — where notes carry forward, evidence accumulates, and gaps are identified before drafting begins — compounds in value across every cycle that follows. |
03 Align finance and ESG disclosure teams around shared data CSRD has made financial-ESG connectivity a compliance matter. Teams that share a disclosure environment are structurally better positioned for the connected reporting that regulators and investors now expect. |
04 Invest in governance infrastructure, not just reporting tools The more durable investment is in the governance layer: audit trails, judgment documentation, approval accountability, and cross-section consistency. These are what make disclosures defensible, not just complete. |
