Study of Investment Banks

SOX Section 705 (“Study of Investment Banks”) is not a control requirement you “comply” with directly; it is a statutory mandate for the Comptroller General to study whether investment banks helped companies manipulate earnings. For a CCO or GRC lead, the operational response is to harden governance over investment bank engagements, transaction accounting, and disclosure review so your firm cannot be perceived as using advisers to obfuscate financial condition. (Public Law 107-204)

Key takeaways:

• SOX 705 is a government study mandate, but it signals regulator focus on adviser-enabled earnings manipulation risk. (Public Law 107-204)
• Operationalize it through tighter third-party oversight of investment banks and financial advisers plus stronger transaction accounting and disclosure controls.
• Build an evidence trail that links banker activities to approved scope, documented accounting positions, and disclosure committee review.

“Study of Investment Banks” sounds like a compliance checkbox, but SOX Section 705 is written as a directive to the Comptroller General to study whether investment banks assisted companies in manipulating earnings. (Public Law 107-204) That matters to you because it frames a specific regulator concern: complex transactions and advisory relationships can be used to make earnings look better than they are, or to obscure the company’s true financial condition.

As an operator, treat SOX 705 as a risk signal that should shape your controls over (1) engaging investment banks and financial advisers as third parties, (2) approving and documenting complex financing or structured transactions, and (3) reviewing disclosures and non-GAAP adjustments with appropriate governance. If you already run SOX 404 internal control programs, you will recognize the “pressure point” this requirement highlights: the intersection of deal teams, bankers, and accounting judgments.

This page gives you requirement-level implementation guidance you can apply quickly: who should own what, what workflows to stand up, what artifacts to retain, where audits get stuck, and how to prepare for questions about whether your advisers influenced accounting outcomes.

Regulatory text

Text (excerpt): “The Comptroller General shall study whether investment banks assisted companies in manipulating earnings.” (Public Law 107-204)

What this means for an operator:
This section does not impose a direct action on issuers. Your company is not required by SOX 705 to file a report or conduct a study. The practical expectation is indirect: regulators, auditors, and plaintiffs may scrutinize whether third parties (investment banks, financial advisers) contributed to earnings manipulation or misleading presentation. Your job is to prevent, detect, and document decisions so the record shows your accounting and disclosures were governed internally, not engineered by advisers to achieve a desired earnings result.

Plain-English interpretation (what the requirement is getting at)

SOX 705 points at a recurring failure mode: management pressure to “make the numbers,” paired with complex transactions and sophisticated advisers who can structure deals that change timing, classification, or presentation of financial results. A compliant posture is not “avoid investment banks.” It is:

• define what advisers can do,
• require internal review of accounting conclusions,
• control how transaction economics flow into GAAP reporting and public disclosures,
• maintain documentation that supports judgments.

Who it applies to (entity + operational context)

Entity types: Public companies (issuers). (Public Law 107-204)

Operational contexts where this becomes real:

• Capital markets transactions (debt/equity issuance, refinancing, tender offers)
• M&A and divestitures, including earn-outs and contingent consideration
• Structured finance or off-balance-sheet adjacent arrangements
• Significant revenue, expense, reserve, or impairment judgments that could be “influenced” by deal structuring
• Non-GAAP metrics and adjustments that could be framed to meet targets
• Any engagement where compensation incentives (success fees) could bias advice toward transactions that improve near-term earnings optics

Primary stakeholders you need in the loop:

• CFO / Controller / Chief Accounting Officer
• Treasury (for financing)
• Legal (securities and disclosure counsel)
• Disclosure committee (or equivalent)
• Internal audit / SOX PMO
• Procurement / third-party risk management (for onboarding and contracting)
• Deal sponsors (corporate development, business unit leaders)

What you actually need to do (step-by-step)

Below is an implementation approach that turns the SOX 705 “risk signal” into concrete governance. Treat these as minimum operational moves for transactions where an investment bank or financial adviser is involved.

1) Inventory and classify investment bank and adviser engagements

1. Pull a list of all investment banks, placement agents, financial advisers, and similar third parties engaged in the last reporting cycle.
2. Classify each engagement by risk (high/medium/low) using practical triggers:
   • complex accounting impact expected,
   • success fee or contingent compensation,
   • aggressive timing objectives (quarter-end closings),
   • unusual structures, side letters, or bespoke terms.
3. Assign an internal business owner and a control owner (typically Controller/CAO for accounting-impacting engagements).

Why auditors care: they want to see that high-risk engagements are routed into heightened review, not treated as standard procurement.

2) Standardize contracting terms that reduce “earnings engineering” risk

For higher-risk advisory engagements, require Legal + Finance to include:

• Clear scope of work (what the bank will deliver and what it will not do)
• Prohibition on undisclosed side arrangements (require disclosure of side letters and material communications)
• Information rights and retention (your right to obtain workpapers, models, analyses)
• Conflicts disclosures (bank’s other roles with counterparties where relevant)
• Fee transparency (including contingencies, success fees, and timing)

Keep this lightweight for low-risk engagements, but do not skip it where accounting optics could be affected.

3) Put accounting governance “in front of” the deal, not after it

Create a pre-deal accounting checkpoint for any transaction with potential earnings impact:

1. Deal team submits a short transaction memo: purpose, key terms, expected accounting areas.
2. Controller/CAO assigns an accounting reviewer and sets required consultations (external auditor consultation, technical accounting, valuation).
3. Require a written accounting position memo before signing or closing where feasible, especially when classification or timing could move earnings.

If speed is a constraint, require at least a documented “interim view,” followed by a final memo post-close.

4) Control banker interactions that could be perceived as influencing accounting outcomes

You do not need to wall off bankers, but you do need governance:

• Centralize material communications through the deal lead plus Legal/Finance.
• Document substantive advice that affects structure or reporting outcomes.
• Require internal approval for material term changes late in the process, especially near period-end.

A practical rule: if it changes economics, timing, classification, or disclosure posture, it requires written internal sign-off.

5) Disclosure committee review for transactions and related narratives

For material transactions supported by investment banks:

1. Prepare a disclosure packet: transaction summary, key accounting judgments, sensitivities, non-GAAP impacts, and risk factor considerations.
2. Route through the disclosure committee with minutes capturing challenges and decisions.
3. Confirm consistency across earnings materials, press releases, 8-K language, MD&A, and financial statement footnotes.

6) Evidence retention and “storyline readiness”

Assume scrutiny later. Maintain a coherent storyline:

• What was the business purpose?
• How did you evaluate accounting?
• Who approved it?
• What did the bank advise?
• How did you control conflicts and incentives?

Tools like Daydream can help you keep the engagement intake, risk classification, approvals, and artifact collection in one workflow so your evidence doesn’t end up scattered across email, deal rooms, and shared drives.

Required evidence and artifacts to retain

Keep artifacts in a deal file (or centralized GRC repository) with clear ownership:

Third-party / engagement artifacts

• Engagement letter + amendments; scope and fee terms
• Conflicts disclosures (if provided) and internal review notes
• Deliverables list (fairness opinion, banker presentation, financing deck, model outputs)

Accounting and control artifacts

• Transaction memo (business purpose, terms, timeline)
• Technical accounting memo(s) and approvals
• Auditor consultation materials (if applicable) and outcomes
• Valuation reports (where relevant) and management review evidence
• Disclosure committee packet + minutes

Governance artifacts

• Approval trail for key terms and last-minute changes
• Communications log or curated record of material banker recommendations that affected structure/accounting/disclosure
• Post-close review checklist confirming accounting entries and disclosures tie to approved positions

Common exam/audit questions and hangups

Auditors and examiners tend to probe the “influence pathway” from adviser to financial reporting:

• “Show me how you governed banker involvement in structuring.” They want the approval trail and evidence the company owned the accounting conclusions.
• “Where is the accounting memo, and was it written before the reporting decision?” Post-hoc memos look defensive.
• “Were any side letters or unusual terms present?” Missing side letters is a recurring hangup because they change economics and accounting.
• “Who challenged management’s preferred outcome?” Disclosure committee minutes that show real challenge matter.
• “How did you evaluate non-GAAP impacts?” They look for discipline and consistency, not marketing-driven adjustments.

Frequent implementation mistakes (and how to avoid them)

1. Treating SOX 705 as “not applicable” and doing nothing.
   Fix: record SOX 705 as a risk driver in your SOX/GRC narrative, then map it to existing controls (deal approval, technical accounting, disclosure committee) and show enhancements where gaps exist. (Public Law 107-204)

2. Relying on bankers’ materials as accounting support.
   Fix: bankers can inform, but management must document GAAP conclusions via internal technical accounting memos and approvals.

3. Late-stage term changes with no re-review.
   Fix: require a “material change” trigger that forces accounting and disclosure re-approval.

4. No unified deal file.
   Fix: establish a single repository and a checklist for required artifacts; enforce it at close.

5. Success-fee engagements without conflict controls.
   Fix: document fee structure review, conflicts disclosures (if any), and management’s independent accounting analysis.

Enforcement context and risk implications

No public enforcement cases were provided in the source catalog for this requirement, so this page does not cite specific actions. The risk logic still matters: if a regulator, auditor, or investigator sees patterns consistent with adviser-enabled earnings manipulation, scrutiny will focus on governance, documentation, and whether accounting and disclosure decisions were made independently and supported contemporaneously. SOX 705 is explicit about the concern regulators studied: investment banks assisting earnings manipulation. (Public Law 107-204)

Practical execution plan (30/60/90)

You asked for speed; here is an operator’s rollout plan with concrete outputs. Treat the phases as “first / next / then” and adjust to your transaction volume and reporting calendar.

First phase (immediate)

• Name an owner (Controller/CAO) and a cross-functional working group (Legal, Treasury, Procurement/TPRM, SOX PMO).
• Build the inventory of investment bank and adviser engagements.
• Define the “high-risk engagement” triggers and a mandatory intake form.
• Create a deal file checklist for required artifacts.

Outputs: engagement inventory, risk classification criteria, intake form, artifact checklist.

Second phase (near-term)

• Update template engagement letter language for higher-risk advisory work (scope, conflicts, retention, side-letter controls).
• Stand up the pre-deal accounting checkpoint and memo template.
• Add a disclosure committee routing step for material adviser-supported transactions.
• Pilot the workflow on the next live transaction; collect feedback and tighten.

Outputs: contract templates, accounting memo template, disclosure packet template, pilot evidence pack.

Third phase (ongoing)

• Train deal teams and treasury on the triggers and “material change” re-approval rule.
• Add periodic QA: sample a set of transactions and confirm artifacts exist and approvals align.
• Roll the workflow into your third-party onboarding tool or a dedicated workflow (Daydream can centralize intake, approvals, and evidence retention across third parties and deals).

Outputs: training materials, QA results, continuous improvement log, system-of-record workflow.

Frequently Asked Questions

Is SOX Section 705 a direct compliance requirement for my company?

The text directs the Comptroller General to conduct a study; it does not instruct issuers to perform a specific action. Operationally, treat it as a clear signal to strengthen controls around investment bank engagements, transaction accounting, and disclosures. (Public Law 107-204)

Do we need a “SOX 705 policy”?

Usually no. Most teams implement this through existing policies and controls: third-party engagement governance, technical accounting memo requirements, disclosure committee procedures, and document retention.

What transactions should trigger the heightened workflow?

Trigger it when an investment bank or adviser is involved and the deal could materially affect earnings timing, classification, or disclosure posture. If the deal is complex, rushed near period-end, or includes contingent fees, route it to the high-risk path.

How do we show auditors that bankers did not drive accounting conclusions?

Keep contemporaneous technical accounting memos, documented approvals, and disclosure committee minutes. Banker decks can be supporting context, but your internal accounting analysis must stand on its own.

Procurement owns third-party onboarding. Do they own this control?

Procurement/TPRM should own onboarding hygiene and contract routing, but Finance and Legal must own the accounting and disclosure governance. Assign explicit RACI so no one assumes the other team captured the critical artifacts.

What’s the minimum evidence pack we should be able to produce quickly?

Engagement letter, scope/fees, transaction memo, accounting position memo with approvals, disclosure committee materials/minutes, and a record of material term changes with re-approval. If you can produce that pack on demand, you reduce escalation risk materially.