SBSE-CCO Annual Report: SEC Requirements, Timeline, and How to Prepare
If you’re a registered Security-Based Swap Dealer, your annual CCO Report is one of the most important things you file with the SEC each year. It doesn’t have to be complicated — but it does deserve the right attention, the right process, and the right partner. Here’s everything you need to know.
Who Does This Compliance Apply To?
The SBSE-CCO-RPT mandate applies to two categories of entity registered with the SEC under the security-based swap regulatory framework introduced by the Dodd-Frank Act. If your firm falls into either category, this is a mandatory annual obligation.
| Security-Based Swap Dealers (SBSDs) | Major Security-Based Swap Participants (MSBSPs) |
| -An SBSD is any entity that holds itself out as a dealer in security-based swaps, makes a market in them, or regularly enters into security-based swaps as an ordinary course of business — subject to regulatory thresholds and definitions set by the SEC.
-Classification depends on the nature of the dealing activity and applicable de minimis thresholds — not frequency of transactions alone. Examples: broker-dealers, global banks, financial institutions active in the credit default swap market. |
-An MSBSP is an entity that is not an SBSD but holds positions in security-based swaps large enough to pose systemic risk or significant counterparty exposure relative to capital — or whose positions could adversely affect the stability of the U.S. financial system.
-Defined by systemic risk relevance, exposure relative to capital, and potential impact on the U.S. financial system — not simply the size of positions. Examples: large hedge funds or financial entities with significant credit derivative exposures. |
| Registers via: Form SBSE, SBSE-A, or SBSE-BD
(Registration forms — separate from the SBSE-CCO-RPT reporting obligation) |
Registers via: Form SBSE, SBSE-A, or SBSE-BD
(Registration forms — separate from the SBSE-CCO-RPT reporting obligation) |
Both SBSDs and MSBSPs have been subject to Rule 15Fk-1 — and therefore the SBSE-CCO-RPT annual filing obligation — since October 6, 2021, when SEC registration requirements for these entities took effect.
| What this means for your firm
1. Implement and maintain compliance systems: Your CCO establishes and oversees written policies and procedures to ensure compliance with all Section 15F obligations. 2. File the SBSE-CCO-RPT annually: Your CCO prepares, signs, and submits the annual compliance report through EDGAR within 90 days of your fiscal year-end. 3. CCO certification: Your CCO certifies the accuracy and completeness of the report. This carries personal accountability. |
| Does this apply to your firm?
If your firm has registered with the SEC by filing Form SBSE, SBSE-A, or SBSE-BD, the SBSE-CCO-RPT mandate applies to you. Non-U.S. firms relying on substituted compliance under Rule 3a71-6 are also subject — though conditions depend on the applicable substituted compliance order for your jurisdiction. |
What the SEC Expects — Explained Simply
The SBSE-CCO-RPT requirement was introduced under the Dodd-Frank Act in 2010, which brought security-based swaps under formal SEC oversight for the first time. Every registered SBSD must have their CCO prepare an annual report giving the SEC a substantive, honest picture of how the compliance programme is working. That obligation lives in Rule 15Fk-1.
| A well-prepared CCO Annual Report is an opportunity, not just an obligation — your firm’s chance to demonstrate a compliance culture that’s working and improving year on year. |
Five areas to address
What the SEC wants to see1. How effective are your policies and procedures? A genuine assessment of how well your compliance framework works in practice, not just on paper. 2. What has changed since last year? Document material updates to your compliance policies — this builds a clear, year-on-year audit trail. 3. What improvements are you planning? Forward-looking recommendations show a mature, proactive compliance culture that the SEC values. 4. Were there any compliance issues? Material non-compliance matters should be included. Engaging openly here demonstrates genuine transparency. 5. Are your compliance resources adequate? An honest assessment of staffing, budget, and systems — including any gaps — rounds out a credible report. |
Planning around the 90-day window
You have 90 calendar days from fiscal year-end to file. Before it reaches the SEC, the report needs to go to your board of directors, senior officer, and audit committee for review. Building that step in around the midpoint of your window makes everything smoother.
| A comfortable timeline
Days 1–45: Gather data and draft the report. Days 46–60: Board and audit committee review and sign-off. Days 61–90: Finalise and submit through EDGAR. |
Where the SEC Is Taking Structured Reporting
The SBSE-CCO-RPT sits within a wider SEC initiative to make EDGAR filings more structured and data-driven. Right now, the SBSE-CCO-RPT is primarily a narrative PDF filing. But as the SEC’s broader structured data roadmap unfolds across EDGAR, firms that begin building familiarity with Inline XBRL now will find the transition much smoother when fuller requirements arrive.
| What Inline XBRL actually means
Inline XBRL embeds structured data tags into a document so it remains human-readable while also being processable by computers. The document looks exactly the same — but it carries digital labels that let regulators find, compare, and analyse information across filings far more efficiently. It’s already standard for most public company financial filings in the US. |
How Ez-XBRL Helps You Prepare Without Disrupting Your Reporting Workflow
You don’t need to rebuild your reporting process from scratch. Ez-XBRL helps you integrate Inline XBRL preparation into your existing workflows — so your team can meet today’s EDGAR requirements and be ready for structured data obligations as they expand.
Integix — prepare Inline XBRL using your existing documents
With Integix, your team can convert compliance and financial documents into Inline XBRL and apply taxonomy tagging efficiently — without changing how those documents are created.
Using Integix, your team can:
- Convert documents from Excel, Word, or PDF into Inline XBRL
- Automatically map data to the relevant SEC taxonomy
- Identify and resolve validation issues before submission
- Generate Inline XBRL files ready for filing via EDGAR
- Maintain consistent tagging across reporting periods
XOR — review and approve reports with confidence
Before submission, your team — and where relevant, your board and audit committee — can review Inline XBRL reports in a clear, documented workflow.
With XOR, your team can:
- Review Inline XBRL reports in a clear, human-readable format
- Validate taxonomy tagging and confirm completeness
- Track changes and maintain full audit trail visibility
- Approve reports before submission through EDGAR
This gives your team — and your governance stakeholders — confidence that reports are accurate and ready before they reach the SEC.
Choose the Engagement Model That Fits Your Team
Every compliance team is at a different stage of Inline XBRL readiness. You may want full control, expert support, or a combination of both. Ez-XBRL provides three flexible engagement models so you can choose what works best — and adjust as your capabilities grow.
Whichever model you choose, you get the same certified platform infrastructure, ISO 27001:2022 information security, and proven delivery process refined across XBRL mandates in the United States, the United Kingdom, India, the European Union, and South Africa.
How your team can prepare now
Preparing early makes the transition to structured data reporting noticeably smoother. A few straightforward steps go a long way:
Getting started
|
Why Compliance Teams Choose Ez-XBRL
We work with compliance teams because we make their lives genuinely easier — not by adding complexity, but by taking it away. Here’s what our clients consistently tell us makes the difference:
| What our clients value most
1. Certified platforms: both our Integix authoring platform and XOR review portal are certified by XBRL International — the global standard-setter for XBRL — backed by four U.S. patents on our core automation technology. 2. Information security: Ez-XBRL Solutions Inc. is ISO 27001:2022 certified, ensuring your compliance documentation is managed within a rigorously maintained information security framework. 3. Global regulatory experience: we’re recognised by UK HMRC as a managed tagging service provider and are a member of South Africa’s CIPC Software Service Provider Panel. 4. A process built for recurring filings: our roll-forward approach, structured review workflow, and EDGAR test-filing step mean that each year’s filing is smoother than the last. |
Your Next CCO Annual Report Can Be Your Best One Yet
A substantive, well-organised CCO Annual Report reflects a compliance programme that’s genuinely functioning and improving. That’s entirely achievable with the right preparation and the right partner — and Ez-XBRL is here to make it straightforward, whatever engagement model fits your team best.
| Let’s have a conversation
We’d love to show you how Ez-XBRL works in practice and help you think through a filing approach that suits your team. Reach Out to us directly to set up a no-obligation consultation. |
Recent posts
Press Release posts
