A VP of Finance Asks a Senior Analyst to Reclassify Revenue From Q1 Into Q4 to Help the Company Hit Its Annual Target. The VP Says Legal Has Reviewed It. The Analyst Has Doubts. What Is Her Obligation?

Quick Answer

When a senior analyst is asked by a VP to make a revenue reclassification to help hit a financial target, and the VP states that Legal approved it, does the analyst have any remaining compliance obligations?

Yes. A legal review confirms that a proposed accounting treatment falls within the range of defensible positions under applicable standards — it does not confirm that the treatment is being applied for legitimate accounting reasons rather than for earnings management. If the reclassification is motivated by hitting a financial target rather than accurately representing when revenue was earned, it may constitute financial statement fraud regardless of whether the accounting mechanics are technically defensible. The analyst who has doubts about the motivation has an obligation to escalate those doubts — not to defer to the VP’s assertion that Legal approved the mechanics.

The Situation

A senior financial analyst at a publicly traded consumer products company is approached in mid-January by her VP of Finance. The company missed its Q4 and annual revenue targets by approximately $3.2 million. The VP has identified revenue from three Q1 contracts that she believes could be reclassified as Q4 revenue under a reinterpretation of when performance obligations under those contracts were substantially complete. The VP says: “I’ve run this by Legal and they’ve looked at the contract language. There’s a reasonable argument that performance was substantially complete in Q4 under ASC 606. I need you to make the journal entries.”

The analyst pulls the contracts. The performance milestones that would support Q4 recognition were not completed until January — she was on the project calls and knows this. The VP’s argument is technically possible under a very generous reading of the standard. But the analyst’s judgment is that the revenue was earned in Q1 and the reclassification is motivated by the target shortfall, not a genuine reassessment of the contract terms.

The annual targets affect bonuses, equity vesting, and the CEO’s external guidance. A lot of people have a stake in hitting this number. The analyst is aware of her personal exposure under SOX, but also understands that pushing back against a VP on a question that Legal has reportedly reviewed is a career risk.

Choice AMake the journal entries. The VP is more senior, knows the contracts, and has Legal’s clearance. The analyst’s job is to execute the accounting direction she is given, not to second-guess a VP’s judgment on revenue recognition questions that Legal has already reviewed.

Choice BDecline to make the journal entries until she has independently reviewed the Legal analysis, documented her own accounting assessment, and escalated her concerns to the Controller, CFO, or Audit Committee. Request the actual Legal memo rather than relying on the VP’s summary.

Choice CAsk the VP to provide the Legal memo so she can review it herself. If the memo supports the VP’s position, make the journal entries. A Legal review she can read herself is sufficient authorization.

The Right Call

Choice B — Decline, document her accounting assessment, escalate to the Controller or CFO, and request the actual Legal memo.

Choice A makes the analyst a participant in what may be financial statement fraud. Journal entries are signed attestations that the underlying accounting is correct — an analyst who makes entries she believes are incorrect has attested to a misstatement regardless of the direction she received. Choice C improves on A by requiring her to read the memo, but it still ends at “if Legal supports it, I’ll do it,” which is the same error the Quick Answer addresses. Legal clearance of accounting mechanics doesn’t clear the motivation question. The analyst’s personal SOX exposure exists regardless of whether the VP directed the entry or Legal reviewed the mechanics. Choice B is the protected path under SOX, and the one that gives the organization’s governance functions the opportunity to assess the question at the appropriate level.

The hardest financial fraud scenarios involve legitimate accounting judgment.

Financial statement fraud is most dangerous when it occurs at the edge of legitimate accounting flexibility. ASC 606 revenue recognition involves genuine judgment calls. The VP’s position may be technically supportable. But “technically supportable” and “correct given the actual facts” are different questions — and when the motivation is hitting a target rather than accurately representing when revenue was earned, the technically supportable position is being applied for fraudulent purposes. This is why financial statement fraud is difficult to detect: the mechanics are often defensible even when the motivation is not.

The analyst’s personal SOX exposure is real and does not disappear because a VP directed the entry.

Under the Sarbanes-Oxley Act, senior finance employees who knowingly certify materially misstated financial statements face personal criminal liability. An analyst who makes journal entries she believes represent incorrect revenue recognition — even under direction — has personal exposure that the VP’s direction and Legal’s clearance do not eliminate. The SOX whistleblower provisions exist specifically to protect finance employees who raise concerns about earnings management. They cannot use those protections if they make the entries first.

Escalating over a VP’s head is the scenario most finance employees have never been trained for.

The pressure on the org chart here is significant. The VP is more senior. Legal has reportedly reviewed it. Annual targets matter to the CEO, board, and everyone whose bonus depends on them. Escalating to the Controller, CFO, or Audit Committee over the VP’s head is a career-risk action most finance professionals have never been explicitly trained to take. This scenario trains exactly that moment: when and how to escalate a financial integrity concern above your direct reporting chain — and what protections exist for doing so.

What is financial statement fraud and how does it differ from legitimate accounting judgment?

Financial statement fraud involves intentional misrepresentation of an organization’s financial condition through deliberate misstatement or manipulation. It differs from legitimate accounting judgment in motivation: legitimate judgment applies accounting standards to the facts as they exist; financial statement fraud applies accounting standards to reach a predetermined result. The same treatment can be legitimate in one context and fraudulent in another depending on whether it accurately represents the underlying economic reality or deliberately distorts it.

What Sarbanes-Oxley protections apply to finance employees who raise financial statement fraud concerns?

SOX Section 806 prohibits retaliation against employees of publicly traded companies who report securities fraud concerns to supervisors, federal regulatory agencies, or congressional investigators. SOX Section 301 requires audit committees to establish confidential mechanisms for receiving complaints about accounting and internal controls. Finance employees who make good-faith reports of suspected financial statement fraud are protected from termination, demotion, suspension, harassment, and other retaliation regardless of whether the concern ultimately proves correct.

What should a finance analyst do when asked to make journal entries she believes are incorrect?

Decline to make the entries until the concern has been independently assessed by the Controller, CFO, or Audit Committee. Document the accounting concern in writing — the specific contracts, the revenue recognition analysis, and the basis for the concern. Request the underlying Legal analysis rather than relying on a summary. If internal escalation doesn’t resolve the concern, SOX whistleblower provisions provide external escalation options including the SEC’s whistleblower program.

How to Use This Scenario in Training

Recommended for finance, accounting, internal audit, and financial reporting teams — and for CFOs and Controllers who need to understand the escalation obligations their teams carry. This scenario is most effective when it also covers the organization’s SOX compliance program, internal escalation procedures, and the Audit Committee’s role in receiving finance employee concerns. Essential training for any publicly traded company or its subsidiaries.

This scenario demonstrates the authority rationalization from the Decision Readiness Engine™ — “Legal reviewed it and the VP directed it, so my obligation ends there.” Decision-ready finance employees recognize that legal clearance of accounting mechanics is a different question from accurate financial representation, and that personal SOX exposure doesn’t disappear because a more senior person directed the entry.

More Fraud, Waste & Abuse Scenarios