Two colleagues reviewing a printed financial report together
Controls · Disclosure

The disclosure controls nobody wrote down

The financial statement controls are documented in detail. The controls over everything around the numbers tend to be a checklist somebody keeps in a personal folder.

Key Takeaways
  • Disclosure controls cover the process that produces the report, not just the ledger that produces the numbers.
  • In most companies the narrative, the subtotals and the non financial content are governed by habit rather than by a documented control.
  • Evidence is the weak point, because a review that happened in a meeting leaves nothing behind unless somebody records it.
  • Any change to reporting frequency or format exposes this immediately, because the habit was tied to the old rhythm.
  • Writing the control down is a short exercise and it is the only version that survives a change of personnel.

Ask for the control over a bank reconciliation and you will get a documented process, a preparer, a reviewer and a date. Ask for the control over how a subtotal in the front half of the report was arrived at and the answer is usually a name.

That name is a real control in practice. It is also unwritten, unevidenced and personal, which means it disappears the day the person moves.

This is not an argument for more bureaucracy. It is an argument for writing down what is already happening, so it can be evidenced and so it survives a change in the reporting cycle.

Disclosure ControlsReportingEvidenceGovernanceReview
01

What disclosure controls actually cover

Controls over financial reporting deal with how a number arrives at the ledger. Disclosure controls deal with how information reaches the report and whether it is complete and timely.

That second population is broader and it is much less standardised. Narrative commentary, subtotals, segment descriptions, subsequent events and non financial content all sit inside it.

Very little of it flows from a system. Most of it is assembled from a mixture of ledger extracts, management commentary and information supplied by people outside finance.

Which is why an interval change of the kind proposed in the semiannual reporting proposal surfaces the gap so quickly.

A finance professional working through figures at a desk
The controls over the numbers are documented. The controls around them often are not.
02

Four controls that exist without being written down

Each of these is performed in most companies and documented in few, and each is a genuine control rather than an administrative step.

Completeness of the reporting pack: Someone knows the full list of items that have to be gathered, including the ones supplied by legal, human resources and operations. That knowledge is usually held rather than written.
Consistency between narrative and numbers: A person reads the commentary against the statements and catches the sentence that no longer matches the figure, which is why the subtotals you will have to defend rarely surprise anyone internally.
Subsequent events sweep: A defined enquiry of defined people, or in practice a set of conversations somebody remembers to have.
Version control on the final document: The control that stops an earlier draft being filed, often nothing more than a naming convention one person applies.
03

Evidence is the part that fails

The performance of these controls is usually real. The evidence of performance is usually thin, because the work happens in meetings, in review comments and in tracked changes that get accepted and disappear.

That distinction matters when an auditor tests the control rather than the outcome. An accurate report is not evidence that a control operated.

The cheapest fix is a record of the review rather than a new process. Who reviewed what, against what, and what changed as a result.

The same principle applies to any automated preparation, which is why evidence that an agent did what you say it did matters as much as the output.


The control operated. Nothing exists to demonstrate that it did.
04

Three levels of documentation

The choice is not between nothing and a control framework, and the middle option covers most of the risk.

LevelWhat existsWhat it survives
HabitA person who knows what to do and does it.Nothing. It survives until that person is on leave at a period end.
Checklist with sign offA list, an owner per item and a date recorded.A personnel change, an audit enquiry and a change in reporting frequency.
Full control documentationDescription, frequency, evidence standard and testing approach.Everything, at a cost that is only justified where the reporting is complex or heavily scrutinised.

Expectations for disclosure controls depend on your regulatory environment and your auditors. Agree the standard with them rather than choosing one unilaterally.

"

A control performed by the same person for nine years is still not documented.

ChatFin
05

Writing it down in an afternoon

This is genuinely a short exercise if it is treated as documentation of existing practice rather than as design of new practice.

List the inputs to the last report

Every item that was gathered, including the ones from outside finance, and who supplied each one.

Name the owner and the check

For each input, who is responsible and what the check on it consists of. One line each is enough to start.

Decide the evidence standard

What has to be retained to show the check happened. An email, a signed checklist or a comment in a workflow all count if they are consistent.

Set the frequency explicitly

Not linked to the filing calendar, because that is the assumption exposed by any change, as thresholds set years ago were exposed by inflation.

An accountant examining documents beside a calculator
A checklist with an owner and a date covers most of the risk at very little cost.
06

Two ways the documentation itself fails

One from over engineering and one from under estimating.

Failure

Building a framework

The exercise turns into a control design project with a matrix, a testing plan and a consultant. Most of the benefit was available from the checklist.

Failure

Documenting the ideal

The written process describes what should happen rather than what does, so the evidence never matches the description and the documentation makes things worse.

07

How ChatFin supports evidence

We work upstream of the report itself, on the numbers and reconciliations that feed it, and the relevant contribution is the record left behind.

A record of every preparation: What was prepared, from which source data, and what changed between the draft and the approved version.
Reviewer actions captured: Approvals, rejections and amendments are retained against the item, which gives a control an evidence trail without anyone maintaining one.
Human sign off preserved: Nothing is asserted or filed by the system. Approval stays with the person accountable, which is the boundary in controls over an autonomous process.

Drafting the report, the narrative and the judgements around them remains firmly with your team and your advisers, and the documentation described here is worth doing whether or not anything is automated, as the document you cannot find is the control argues.

Free tool

AI Cost Estimator for the CFO Office

Four inputs. A first year range, a timeline, and three delivery models compared. No login required.

Frequently Asked Questions

What is the difference between disclosure controls and financial reporting controls?

Financial reporting controls address how a number reaches the ledger and the financial statements. Disclosure controls address whether information required to be disclosed is gathered, evaluated and reported on time, which includes narrative and non financial content assembled from outside finance.

Is a checklist enough?

For many companies, a checklist with a named owner per item, a recorded date and a defined evidence standard covers most of the risk. Full control documentation with a testing plan is proportionate where reporting is complex or heavily scrutinised. Agree the standard with your auditors rather than choosing it alone.

Why does reporting frequency matter here?

Because most of these controls are performed on a rhythm set by the filing calendar rather than by a documented frequency. If the calendar changes, the rhythm changes with it and nobody decided to make that change, which is the definition of drift.

What evidence should we retain?

Enough to show the check happened, consistently applied. An email confirmation, a signed checklist or a comment recorded in a workflow are all acceptable provided the same form is used each period and it is retained somewhere other than a personal mailbox.

Write down what already happens

The control is real. The record of it usually is not.

Listing the inputs, naming the owners and defining the evidence standard turns an unwritten practice into something that survives a personnel change and an audit enquiry.

If you want a first year range for prepared reconciliations with a retained evidence trail, the estimator gives one in about a minute.

Open the estimator
Book a Demo
Put it on your own numbers

See what this looks like in your ERP.

We will walk through the workflow behind this article on the system you already run, using your own data, and show what a first phase would actually cover.

✓Runs on the ERP you already have, on the version you already run
✓Every action prepared as a draft that a person approves before it posts
✓A first phase scoped against your real workflows, not a generic package
Schedule a Demo
Confidential & private

This article is general information for finance and accounting teams. It is not legal, tax, accounting or investment advice. Dates and thresholds are given as published at the time of writing and several of these timelines have moved before, so confirm the current position with your advisers and with the relevant authority before acting.

Photos by Mikhail Nilov, free to use under the Pexels License (commercial use, no attribution required).