Cognatum

Financial services

A representation letter asserts what isn't there

A management representation letter is mostly a list of things management swears are not there. Retrieval answers from what it can reach, so an empty result and an empty world look identical. That gap is where the signature is exposed.

Cognatum Team · Nov 19, 2026 · 6 min read

The last document in an audit is not a number. It is a letter. Someone signs it, and the audit can close.

Served to one approved entry
AI assistants & agents
Proposal tools
Internal search & chat
Customer portals
Compliance & audit

Cognatum governs the entry

source · version · approver · permissions

The letter says that what you handed over is everything. Not that it is correct. That there is nothing else.

That is a harder thing to promise than it sounds. You can show someone a file. You cannot show someone a file that does not exist.

An assistant that searched and came back with nothing has not told you there is nothing. It has told you it found nothing. Those are different sentences.

The letter that closes the audit

Under PCAOB standards an auditor must obtain written representations from management before issuing a report. The letter is dated as of the date of the auditor's report.

It is signed by the people with overall responsibility for financial and operating matters, normally the chief executive and the chief financial officer.

Declining is not an option

AS 2805 treats a refusal to furnish the letter as a limitation on the scope of the audit sufficient to preclude an unqualified opinion, and ordinarily enough to make the auditor disclaim or withdraw.

So this is not a formality anyone can quietly skip. It is the hinge the opinion turns on.

Evidence that is never enough on its own

The standard is unusually candid about what the letter is worth. Representations are part of the evidential matter, but they are “not a substitute for the application of those auditing procedures necessary to afford a reasonable basis for an opinion.”

Evidence, then, and never sufficient evidence. The signature settles nothing by itself. It records who said it, and when.

What the letter actually asks

Read the list of required representations and a pattern appears. A large share of them are not claims about what is in the records. They are claims about what is not.

A list of absences

Management confirms the absence of unrecorded transactions. The absence of side agreements, written or oral, that were not disclosed to the auditor. The availability of all financial records and related data.

The illustrative letter puts one of them plainly: “There are no material transactions that have not been properly recorded in the accounting records underlying the financial statements.”

Knowledge and belief

Every one of those is qualified the same way. The letter confirms them “to the best of our knowledge and belief.”

That phrase does real work. It does not claim the world is a certain way. It claims the signer believes it is, having looked.

Which raises a question nobody had to ask ten years ago. If the signer formed that belief by reading an answer a system assembled, what exactly did they look at?

Retrieval cannot prove absence

Here is the structural problem. A retrieval system answers from what it can reach. When it reaches nothing, it reports nothing.

Four causes, one screen

An empty result has at least four causes, and the system cannot tell them apart. The record does not exist. The record sits outside the indexed sources. The query missed it. Or permissions hid it from the person asking.

Only the first supports a representation about completeness. The other three look identical to the reader.

The silent gap

A wrong figure is visible. Somebody checks it against a source and the mismatch shows. An absence has no source to check it against.

Nothing on the page says there may be a side letter in a mailbox the assistant cannot read. The answer simply does not mention it, which is what it would also do if no such letter existed.

Grounding is not coverage

Anchoring output to a source corpus reduces invention. It does not establish reach. The first preregistered evaluation of retrieval based legal research tools found they still hallucinated between 17 and 33 percent of the time, against vendor claims of eliminating the problem.

If grounded systems are wrong that often on questions with a right answer on file, a question whose answer is supposed to be nothing deserves more care, not less.

One representation reaches the others

AS 2805 carries a provision that deserves more attention than it gets. Where a representation is contradicted by other audit evidence, the auditor investigates the circumstances and weighs the reliability of what was said.

Then the auditor considers whether reliance on management's representations about other aspects of the financial statements is still appropriate and justified.

Nothing fails alone

One unsupported sentence does not fail by itself. It puts the rest of the letter in question.

That is the right instinct. It is also what makes an untraceable input dangerous here. A representation formed from an answer nobody can source is not a contained problem.

Signing for a year you were not there

A further requirement lands directly on institutional knowledge. Where current management was not present for all the periods the report covers, the auditor must still obtain written representations from current management for those periods.

Belief assembled from the record

A finance chief who arrived in March signs for the year before. Their belief about that year comes entirely from the record, and from the people still in the building.

That is a knowledge problem wearing an audit label. The quality of the signature depends on whether the organization can still show what it knew, who approved it, and when.

What the answer has to carry

None of this argues against using an assistant in a close. Regulators assume firms will. FINRA has described this exact use, noting such tools may let a person locate and query a firm's own policies, procedures and forms.

The furniture a record already has

The question is what comes back alongside the answer. An approved record names the person who approved it, the date, the version and the source it came from. A derived answer, by default, names none of those.

Cognatum is a knowledge base built on that difference. Knowledge is governed in one place and served to people and to AI systems, with a named approver, a timestamp and a source on every entry.

Gaps recorded rather than papered over

It does not quietly correct itself. When a source changes, it notifies, and the answers built on that source are flagged for re-check rather than rewritten behind you.

On absence it is equally plain. A question asked with no approved record behind it is logged as an open gap rather than answered into the void. Where two approved sources disagree, both go to a person instead of being merged into one confident reply.

A person still decides

Oversight is the design, not an afterthought. The EU AI Act requires high-risk systems to be built so people can effectively oversee them. Software does not confer compliance with that, but the shape of the obligation is familiar to anyone who has signed one of these letters.

A named person approves the entry. The system does the finding and the surfacing, and the judgment stays where the signature is.

Where the belief came from

Professional skepticism, as the auditing standards frame it, means a questioning mind and a critical assessment of the evidence obtained. It asks the auditor not to assume management is either honest or dishonest.

The letter is going to be signed either way. The only question worth settling beforehand is whether the person signing it can say where their belief came from.

Common questions

Questions this raises.

What is a management representation letter?

It is a letter from management to the external auditor, confirming in writing the representations made during the audit. PCAOB AS 2805 requires the auditor to obtain one for all financial statements and periods covered by the report. It is dated as of the date of the auditor's report and signed by those with overall responsibility for financial and operating matters, normally the chief executive and chief financial officer.

Can an AI assistant be used to prepare representations?

Nothing bars it, and regulators assume firms are already using these tools internally. The issue is not the assistant, it is what travels with its output. A representation rests on management's knowledge and belief, so the signer needs to be able to say which records that belief came from, which version was in force, and who approved them.

Why is completeness harder for an AI answer than accuracy?

An inaccurate answer can be checked against a source. An incomplete one cannot, because the missing record produces no evidence of itself. A retrieval system that returns nothing has established only that it found nothing within what it could reach. The record may sit outside the indexed sources, may have been missed by the query, or may be hidden by permissions.

What happens if one representation turns out to be unsupported?

AS 2805 directs the auditor to investigate the circumstances and consider the reliability of the representation. It then directs the auditor to consider whether reliance on management's representations about other aspects of the financial statements remains appropriate and justified. A single unsupported assertion puts the rest of the letter in question.

Does a governed knowledge base make a company compliant?

No. Software aligns with a framework and supplies evidence to the people who have to demonstrate compliance, it does not confer compliance itself. What a governed knowledge base can do is make the underlying question answerable: who approved this, when, from which source, and what has changed since.

Knowledge governed. Intelligence everywhere.

See it on your own content, in your own environment.