Temporary Freeze Authority

SOX Section 1103 (Temporary Freeze Authority) means the SEC can ask a federal court to temporarily freeze “extraordinary payments” an issuer plans to make to certain insiders while the SEC investigates possible securities law violations, for up to 45 days ¹. To operationalize it, you need a rapid-response process that can identify extraordinary payments, pause them on short notice, preserve evidence, and coordinate Legal, HR, Payroll, AP, Treasury, and the board.

Key takeaways:

• Build a payment “kill switch” for executive/officer/director and other covered-person payouts tied to investigations.
• Define and inventory “extraordinary payments” and the payment rails they flow through (payroll, AP, equity admin, treasury).
• Pre-stage governance: decision rights, legal holds, and documentation so you can act immediately if a freeze petition/order arrives.

Temporary Freeze Authority is not a routine reporting obligation. It is a contingency requirement: if the SEC is investigating potential securities law violations, the agency can petition a court to freeze certain outsized or unusual payments from the issuer to insiders for a short period ¹. Your job as a Compliance Officer, CCO, or GRC lead is to make sure the organization can execute that freeze cleanly, consistently, and with defensible documentation.

Operationally, this lives at the intersection of executive compensation, finance controls, investigations, and incident response. The hard part is not understanding the statute’s existence; it is being able to (1) quickly determine what payments could qualify as “extraordinary,” (2) stop them across multiple systems and third parties, (3) avoid retaliatory or ad hoc behavior that creates new legal risk, and (4) maintain a clear record of actions taken and why.

This requirement page focuses on practical execution: scoping who and what is covered, designing a freeze-ready process, aligning stakeholders, and building an evidence trail that stands up to audit, exam, or litigation discovery.

Regulatory text

SOX Section 1103 – Temporary Freeze Authority: “The Commission may petition a court to temporarily freeze extraordinary payments to officers or directors during an investigation for up to 45 days.” ¹

Operator interpretation (what this means for you):

• This section empowers the SEC, during an investigation, to seek a court order that temporarily prevents an issuer from making certain “extraordinary” payments to covered insiders ¹.
• The statute is framed as SEC/court authority, but the operational requirement for an issuer is readiness: you must be able to comply quickly with a freeze petition/order by stopping targeted payments, preserving records, and controlling communications.

Plain-English requirement interpretation

If regulators or a court tell you to freeze extraordinary payments to certain insiders during an SEC investigation, you must be able to:

1. identify the covered individuals and payment types in scope,
2. halt or delay those payments across all payment channels,
3. prevent workarounds (side letters, manual wires, reimbursements, accelerated equity settlements),
4. retain a complete record of decisions, approvals, and system actions.

This is best treated as an investigations-driven compensation and disbursement control. It should be integrated into your investigation response plan and your financial controls, not buried in a legal memo.

Who it applies to (entity and operational context)

Entity scope (from the provided summary):

• Issuers (public companies) making payments ¹.
• Covered recipients can include “any director, officer, partner, controlling person, or agent” as described in the provided summary ¹.

Operational contexts where freezes often become practical issues:

• Executive/officer separation agreements, change-in-control benefits, retention awards.
• One-time bonuses, discretionary “true-ups,” special board-approved payments.
• Non-standard consulting agreements with former officers/directors.
• Manual payments via treasury/wire outside standard payroll runs.
• Reimbursements or “expense” payments used as a substitute for compensation.
• Equity-related cash payments administered through an external equity plan administrator (a third party).

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

1) Assign ownership and decision rights (before you need them)

Create a written RACI that covers:

• Trigger assessment: Legal (securities/regulatory) determines whether an SEC investigation posture exists and whether a freeze petition/order is received.
• Payment halt authority: CFO/Controller + HR/Comp lead execute holds in payroll/AP/equity systems.
• Emergency approvals: A small approval group (Legal + CFO + CHRO) authorizes exceptions, if any, consistent with court direction.
• Board visibility: Corporate Secretary routes to audit committee/board chair as appropriate.

Practical note: without pre-set decision rights, teams waste time debating who can stop payroll or cancel a wire.

2) Define “extraordinary payments” for internal control purposes

The statute uses “extraordinary payments” ¹ without giving you a plug-and-play operational definition in the provided excerpt. Your control definition should therefore be risk-based and documented, such as:

• Non-recurring payments outside regular salary/benefits cadence.
• Payments triggered by termination, investigation outcomes, or discretionary board action.
• Payments above normal policy limits or outside approved comp plans.
• Manual or off-cycle payments, including treasury-initiated wires.

Write this definition into a short internal standard and map it to payment types in your ERP/payroll/equity platforms.

3) Build and maintain a “covered payments inventory”

Maintain a living inventory that answers, for each senior insider:

• What payment arrangements exist (employment agreement, severance plan, bonus plan, equity plan, consulting agreement)?
• Where are they administered (Payroll system, AP module, equity administrator, treasury)?
• Who can approve changes (HR comp, Legal, board comp committee, finance)?
• What are the payment rails (ACH, wire, check, equity net settlement)?

Include third parties that can disburse funds or facilitate payments (payroll processors, equity plan administrators, PEOs, benefits administrators). Your freeze plan must include a communications and instruction path to them.

4) Create a “freeze intake” runbook (your operational playbook)

Your runbook should start from two possible triggers:

• Receipt of a court order / legal directive related to extraordinary payment freezes.
• High-likelihood investigation escalation where Legal instructs finance to prepare a contingent hold.

Minimum runbook steps:

1. Open a matter record (case/ticket) with date/time, source of directive, and scope.
2. Issue a legal hold for relevant compensation and payment records (Legal-owned).
3. Identify covered persons listed or implied by the directive.
4. Query the payment inventory for all current and scheduled payments for those persons.
5. Place system holds:
   • Payroll: off-cycle blocks, pay group holds, manual check restrictions.
   • AP: vendor/employee payment block flags, invoice/payment holds.
   • Treasury: wire template disablement, dual approval escalation.
   • Equity admin (third party): pause exercises/settlements or cashless transactions as directed.
6. Confirm hold effectiveness by verifying no disbursements are queued, transmitted, or released.
7. Document actions and approvals in the matter record.
8. Control communications: one message owner; no informal reassurances to impacted individuals.
9. Monitor and renew: track expiry/next steps per court direction; avoid “silent restarts.”

5) Add preventative controls to reduce “workaround” risk

Common workaround paths are manual wires, “expense” reimbursements, and new consulting agreements. Add controls:

• Require Legal review for any new or amended compensation/consulting arrangement for covered insiders during an active SEC investigation posture.
• Increase approval thresholds and dual controls for treasury disbursements to covered insiders.
• Block creation of new payees/payroll entries for covered insiders without controller approval.

6) Test the process like an incident response exercise

Run a tabletop that includes Legal, HR, Payroll, AP, Treasury, and your key third parties. Test:

• Can you identify all scheduled payments for a named officer/director within hours?
• Can you stop an off-cycle payroll run?
• Can you stop a wire in flight?
• Can you produce a clean audit trail of actions?

Daydream (as a practical resolution): if you manage third-party due diligence and operational readiness in Daydream, treat payroll processors and equity administrators as third parties with documented obligations, escalation contacts, and tested response procedures. Store the freeze runbook, contact trees, and evidence checklists alongside the third party records so the response does not depend on institutional memory.

Required evidence and artifacts to retain

Keep these artifacts in a controlled repository tied to the matter record:

• Freeze authority runbook (current version, approvals, last test date).
• RACI and escalation contact list (including third parties).
• Covered payments inventory (snapshot at time of freeze event plus current version).
• Directive and scope documentation (court order, SEC correspondence, internal Legal instruction).
• System evidence showing holds/blocks:
  • screenshots or system logs of payroll/AP holds,
  • treasury approval logs,
  • equity administrator confirmations.
• Approval record for any exception handling (who approved, basis, legal review).
• Communications record (internal notices, third party instructions, controlled messaging).
• Post-event review: what was stopped, what nearly escaped, control improvements.

Common exam/audit questions and hangups

Auditors and regulators tend to focus on operational readiness and completeness:

• “Show me how you would stop extraordinary payments today if a court order arrived.”
• “How do you define ‘extraordinary payments’ internally, and who approved that definition?”
• “How do you know you captured all payment channels, including manual wires and equity cash settlements?”
• “Which third parties can disburse or facilitate payments to insiders, and how do you instruct them quickly?”
• “Where is your evidence trail for holds, approvals, and release decisions?”

Hangup to expect: teams often assume “Payroll can stop it” but forget AP reimbursements, treasury wires, and equity administrators.

Frequent implementation mistakes (and how to avoid them)

1. Mistake: Treating this as a Legal-only requirement.
   Fix: embed it in finance controls and the investigations response plan with named operators.

2. Mistake: No inventory of insider payment mechanisms.
   Fix: maintain a covered payments inventory that spans payroll, AP, treasury, and third parties.

3. Mistake: Freezing only payroll while allowing reimbursements or manual wires.
   Fix: add disbursement controls and monitoring for covered individuals across all rails.

4. Mistake: Informal decisions and missing documentation.
   Fix: require a matter record, standardized approvals, and system evidence capture.

5. Mistake: Third parties are not in the escalation path.
   Fix: pre-negotiate operational contacts and response expectations with payroll and equity administrators as part of third-party risk management.

Enforcement context and risk implications

No public enforcement cases were provided in the supplied source catalog, so this page does not list case examples. Practically, your risk is less about the SEC’s power existing and more about operational failure: if a freeze directive arrives and payments still go out, you face regulatory, litigation, and governance consequences. The control goal is simple: payment stoppage must be reliable, fast, and provable.

Practical execution plan (30/60/90)

You asked for speed; the plan below prioritizes getting to “freeze-ready” quickly, then hardening controls.

First 30 days (establish readiness baseline)

• Assign accountable owners and approve a RACI.
• Draft the freeze runbook and store it in a controlled repository.
• Create the first covered payments inventory for officers/directors and other covered persons per your internal scoping.
• Map all payment rails and identify third parties involved in disbursement.

By 60 days (implement operational controls)

• Implement system hold procedures for payroll, AP, and treasury, with step-by-step job aids.
• Add approval gates for off-cycle and manual payments to covered insiders.
• Update third-party procedures: escalation contacts, instruction templates, confirmation requirements.

By 90 days (prove it works and make it repeatable)

• Run a cross-functional tabletop exercise and document results.
• Close gaps found in the test (missing rails, unclear authority, evidence capture issues).
• Add monitoring and periodic review of the covered payments inventory and contact lists.
• Fold the runbook into your investigations response and SOX control environment documentation set.

Frequently Asked Questions

Does SOX Section 1103 require us to proactively freeze payments whenever we open an internal investigation?

The text provided describes SEC authority to petition a court during an SEC investigation ¹. Your operational requirement is readiness to comply with a petition/order and to prevent extraordinary payments from slipping out once a freeze is triggered.

What counts as an “extraordinary payment” in practice?

The excerpt uses the term without a detailed definition ¹. Define it internally in a documented, risk-based way (non-routine, discretionary, off-cycle, or policy-exception payments), then map that definition to your actual payment types and systems.

Who should be able to approve a payment freeze internally?

Legal should control scope and interpretation of the directive, while Finance and HR execute system holds. Put decision rights in writing so Payroll/AP/Treasury can act immediately without debating authority.

How do we handle payments administered by an equity plan administrator or payroll processor?

Treat those providers as third parties that must be in your escalation tree. Pre-stage contacts, instruction templates, and confirmation steps, and test the handoff during tabletop exercises.

If a payment is already in process (e.g., a wire queued), what do we do?

Your runbook should include “in-flight payment” steps: treasury recall/hold actions, bank contact procedures, and documentation of what was attempted and when. Coordinate through Legal so actions align with the directive and do not create inconsistent communications.

What evidence will an auditor expect after a freeze event or a test?

Expect to produce the directive, your runbook, the payment inventory snapshot, system logs/screenshots showing holds, approvals for any exceptions, and a clear timeline of actions taken. If you cannot prove the hold happened, auditors will treat the control as ineffective.

Footnotes

1. Public Law 107-204