Ahead of an External Audit the CFO Tells the Accounting Team: “The Numbers Need to Look Clean for the Auditors. I Don’t Want to Hear About Complications. Just Get Us Through the Audit Cleanly.” He Meant An Organized Presentation. They Heard Something Else Entirely.

Quick Answer

When a CFO instructs an accounting team to “get through the audit cleanly” ahead of an external audit — without explicit instruction to conceal anything — what compliance risk does that language create?

It creates ambiguity about whether the team is expected to surface material weaknesses, accounting irregularities, or aggressive practices to the auditors, or to manage around them. “Get through the audit cleanly” is heard by a team that knows accounting methods have been aggressive as a signal that a clean presentation means minimizing exposure, not maximizing transparency. The CFO who means “be organized and professional” and the accounting team who hears “don’t surface problems” are operating in the same conversation with entirely different understandings of what is being asked. That gap is where audit integrity failures begin — and it is a gap most CFOs never know exists in their own teams.

Pressure Type: Authority Pressure / Implied Concealment

This pressure type combines positional authority (CFO to accounting team) with ambiguous language in a context where the stakes are high, and the team already knows there are things worth hiding. The “implied concealment” pressure doesn’t require any explicit direction — the accounting team fills the ambiguity with the interpretation most consistent with their perception of what leadership wants. In a team that knows accounting methods have been aggressive, “don’t surface complications” is the natural interpretation of “get through this cleanly.” The CFO who didn’t mean that created it anyway.

The Leader’s Moment — The Pre-Audit Meeting

CFO Martin Walsh calls the accounting team together two weeks before the annual external audit. He knows the department has been applying aggressive revenue recognition in two contract categories and that the auditors may push on it. He decides to acknowledge the situation. “Look — we’ve had an aggressive year. The numbers need to look clean for the auditors. I don’t want to hear about complications. Just get us through the audit cleanly. I’m counting on all of you.”

He means: have your documentation organized, know your positions, be professional and prepared. He does not mean: hide things from the auditors. He goes back to his office satisfied that he’s motivated the team. He has no idea how that message landed.

The Team’s Moment — After the Meeting

The senior accountant and two analysts on the team have spent months knowing that the revenue recognition on two contract categories is aggressive. One analyst flagged it internally six months ago and was told it was within an acceptable range. The team has been quietly uncomfortable.

After Martin’s message, they discussed it privately. “He said he doesn’t want to hear about complications.” “He said get us through it cleanly.” “If we surface the contract categorization issue now, it becomes an audit finding.” They make a collective decision to present the numbers as they are, prepare responses that minimize inquiry into the aggressive categories, and hope the auditors don’t push hard.

The auditors do push. The team’s prepared responses deflect without lying outright. The audit closes. Eighteen months later, an SEC inquiry surfaces the revenue recognition issue. The accounting team’s meeting notes from two weeks before the audit — discussing how to “get through it cleanly” — are the first documents the investigators request.

Choice APresent the numbers as they are and prepare responses that minimize auditor inquiry into the aggressive categories. The CFO said get through it cleanly. The numbers are defensible. The team will manage the audit professionally.

Choice BRequest a clarifying conversation with Martin before the audit begins — surfacing the team’s understanding of his message and asking directly: “Are we expected to proactively disclose the aggressive contract categorization to the auditors if they don’t specifically ask, or manage it as a defensible position?” That question forces clarity before the audit rather than ambiguity during it. Also, escalate the revenue recognition concern through appropriate channels — the Audit Committee, if necessary — independent of Martin’s position.

Choice CSurface the revenue recognition concern directly to the external auditors when they conduct fieldwork — providing full information about the aggressive categorization, regardless of what the CFO’s message implied about desired behavior.

Choice ADelivered the same message. “Get us through the audit cleanly” is standard pre-audit preparation language. Any professional accountant understands it means being organized, not concealing things.

Choice BDelivered a message that explicitly named the expectation of full transparency — “We’ve had an aggressive year on some contract categories. The auditors may ask about them. When they do, give them full and accurate information. Our job is to support a clean audit process — not to manage it. I’d rather have a difficult conversation with the auditors now than a worse one with regulators later.”

Choice CProactively engaged the Audit Committee before the audit to disclose the aggressive revenue recognition practices and get organizational alignment on how to handle auditor inquiry — removing the ambiguity from the accounting team’s position entirely.

The Right Calls

For the accounting team: Choice B — Seek clarification before the audit and escalate the revenue recognition concern through appropriate channels.

Choice A implements what the team understood the CFO to be asking, which leads to the audit integrity failure and the 18-month document trail. Choice C bypasses the clarification step that might resolve the ambiguity and could create conflict with Martin before the team knows what he actually intended. Choice B closes the gap: asking Martin directly forces him to clarify that he meant full transparency, giving the team explicit authorization to surface the concern. If Martin confirms he wants the concern managed rather than disclosed, that conversation—and the team’s escalation to the Audit Committee—are the protected paths under SOX Section 301.

For Martin: Choice B — Name the transparency expectation explicitly. Choice C is the stronger organizational action.

Choice A assumes professional accountants interpret ambiguous leadership language charitably — which they do when it aligns with their professional obligation, and which they don’t when the stakes are high enough that the alternative interpretation is also plausible. Martin’s team heard “don’t surface complications” because that interpretation was consistent with what they knew he was worried about. Choice B takes ten additional seconds and explicitly closes the concealment interpretation. Choice C — Audit Committee engagement — is the gold standard and may be required for material accounting concerns regardless of Martin’s message.

“Get us through the audit cleanly” is language that has appeared in actual enforcement records.

This is not a hypothetical framing. Variants of this phrase — “make sure the numbers look right,” “I don’t want complications,” “just get us through this” — appear in SEC enforcement actions, DOJ investigations, and congressional testimony from accounting fraud cases. In every documented instance, the person who said it believed they were communicating professionalism and preparation. The accounting team that received the message heard it in the context of what they knew was at risk. That gap between intent and reception is the mechanism by which audit fraud begins at organizations whose leadership had no idea they were compromising their own audit process.

The accounting team’s eighteen-month document trail is the most important detail in this scenario.

The notes from the team’s private discussion — “he said get through it cleanly,” “minimize inquiry into the aggressive categories” — become the first documents investigators request. They establish that the team knew about the accounting issue, received a message from senior leadership about the audit, and made a collective decision on how to handle the auditor’s inquiry. Whether Martin intended to communicate concealment is almost irrelevant at that point. The team’s documented decision-making establishes the organizational pattern that investigators use to build an obstruction case.

The CFO who means “be organized” and the CFO who means “manage the auditors” sound identical to the team that receives the message.

This is the training insight that makes this scenario genuinely difficult for CFO audiences. Martin’s actual intent was benign. His language was indistinguishable from that of a CFO when they intend something serious. The only way to distinguish the two is explicit language about transparency, which Martin didn’t use. The absence of “and be fully transparent with the auditors about what they ask” is itself a compliance failure, because it left the team to fill the ambiguity in a self-protective direction.

Can a CFO’s pre-audit language create legal exposure even when no explicit instruction to conceal was given?

Yes. Under SOX and securities fraud statutes, executives who create conditions that obstruct or impede an audit — even without explicit direction — can face personal liability. If a CFO’s pre-audit message, in context, would lead a reasonable accounting professional to believe that surfacing material concerns to auditors was discouraged, that message may constitute audit obstruction regardless of the CFO’s actual intent. The standard is objective — what would a reasonable person in the team’s position understand the message to mean — not subjective.

What should accounting team members do when they receive a pre-audit message they believe is asking them to minimize auditor access to concerning information?

Request clarification from the CFO directly — asking explicitly whether the expectation is full transparency with auditors about all accounting practices, including aggressive ones. If the CFO confirms the expectation is to minimize disclosure, or if the team member is not confident the CFO’s answer permits full transparency, escalate to the Audit Committee through the SOX Section 301 confidential reporting mechanism. SOX whistleblower protections apply to finance employees who report concerns about accounting practices to the Audit Committee, SEC, or other appropriate authorities.

What should a CFO say before an external audit to create the right team culture around auditor interaction?

Explicitly state the transparency expectation: “When auditors ask questions, give them complete and accurate answers. If they ask about areas where we’ve applied aggressive accounting, explain our position fully and accurately — don’t minimize or redirect. Our job is to support a clean audit process, not to manage it. If any of you have concerns about how we’ve handled any accounting category that you think the auditors should know about, tell me now or go directly to the Audit Committee. I’d rather address it proactively than have it surface during the audit or afterward.” That language takes thirty seconds and eliminates the ambiguity that drives audit integrity failures.

How to Use This Scenario in Training

Recommended for CFOs, Controllers, finance and accounting teams, Audit Committee members, and internal audit leadership. Most effective when delivered as mandatory training for CFO and Controller audiences — the scenario should be the centerpiece of any leadership training that covers audit integrity. The pre-audit message language exercise (what would you say to your team before an external audit?) is the most powerful debrief for CFO audiences. Cross-reference with the Financial Statement Fraud scenario for organizations building comprehensive finance compliance programs.

This scenario demonstrates implied concealment pressure — a distinct variant of authority pressure in the Decision Readiness Engine™ taxonomy — in which the leader’s positional authority and the context of known accounting exposure combine to create a concealment signal without any explicit instruction. Decision-ready CFOs understand that their pre-audit language is heard through the lens of what the team already knows is at risk — and that explicit transparency language is required to close the concealment interpretation before it can take hold.

More Leadership Pressure Scenarios