When BG Wealth Sharing Ltd and DSJ Exchange Pty Ltd filed false Form ADV and Form D documents with the SEC, they didn't just commit fraud. They raised over $130 million from investors by exploiting a verification gap in many compliance programs.
The question compliance teams now face: Should you verify the authenticity of SEC filings and registrations, or is that someone else's responsibility?
The Question at Hand
Your organization reviews third-party vendors, investment partners, or service providers who claim SEC registration or filing compliance. Do you take those claims at face value, or verify them independently?
This isn't just theoretical. The BG Wealth scheme succeeded because the entities submitted false filings that appeared legitimate in the SEC's public database. Investors assumed legitimacy and invested. The fake filings stayed visible for months, allowing the fraud to continue.
For compliance teams, this creates a practical dilemma. Verification takes time and resources, but accepting claims without checking them creates exposure.
The Case for Building Verification into Your Program
Some argue that compliance teams must verify SEC filings and registrations as part of due diligence.
Their reasoning: You can't outsource accountability. If your organization partners with an entity claiming SEC registration, you're relying on that claim to assess risk. The Securities Act of 1933 and the Securities Exchange Act of 1934 impose liability for fraudulent conduct, and "we trusted their paperwork" isn't a strong defense.
The verification process isn't technically complex. The SEC maintains public databases where you can search for registered investment advisers and check Form D filings. A compliance analyst can typically verify a claim in under 10 minutes by cross-referencing the entity name, filing date, and registration details.
This approach aligns with the Federal Sentencing Guidelines for Organizations: effective compliance programs include due diligence to prevent and detect criminal conduct. If you're not verifying basic regulatory claims, you're not conducting due diligence.
Consider what verification would have caught in the BG Wealth case. The entities claimed to be SEC-registered investment advisers operating a licensed crypto trading platform. A quick check would have revealed inconsistencies in the Form ADV filing, mismatched hedge fund status, and no legitimate registration for DSJ Exchange as a trading platform. Those red flags could have stopped the relationship before any funds changed hands.
The Case for Relying on Existing Oversight
Others argue that building verification processes duplicates work that regulators and auditors already do.
Their view: The SEC maintains filing databases so the public can review them. If a Form ADV or Form D appears in the system, it has been submitted through official channels. While fraudsters can file false information, catching those false filings is the SEC's enforcement function, not a compliance team's responsibility.
This perspective emphasizes resource constraints. Compliance teams are often stretched thin managing training, investigations, policy updates, and regulatory reporting. Adding verification of every third-party SEC filing creates a new workstream that competes with other priorities.
There's also a scope question. If you verify SEC filings, do you also verify state securities registrations? Foreign regulatory filings? Professional licenses? The logic that drives SEC verification applies equally to dozens of other credentials. Where does verification end?
This camp argues for a risk-based approach. Verify claims when the relationship involves significant financial exposure, access to sensitive systems, or high-stakes decision-making. For routine vendor relationships or informational partnerships, accept the filing at face value unless something raises suspicion.
They also note that verification doesn't eliminate fraud risk. The BG Wealth entities submitted their false filings through official SEC channels. A compliance analyst checking the database might have assumed they were legitimate. Sophisticated fraud can survive basic verification.
Where Practitioners Actually Land
Most compliance programs fall somewhere between these positions. They verify SEC registrations for certain categories of relationships but not universally.
Common triggers for verification include:
- Financial relationships above a threshold amount
- Partnerships involving investor funds or fiduciary duties
- Third-party intermediaries who will represent your organization
- Vendors with access to financial systems or sensitive data
For these high-risk relationships, verification becomes part of the onboarding checklist. The compliance team or legal department confirms that the claimed SEC registration exists, matches the entity's actual business, and doesn't show disciplinary history.
For lower-risk relationships, practitioners rely on contract terms that require the counterparty to maintain required licenses and registrations. The contract creates a representation that the organization can enforce if the claim turns out to be false.
Some organizations also build verification into periodic reviews rather than initial onboarding. They check SEC registrations annually or when renewing contracts, catching changes in status that might indicate problems.
Our Take
You should verify SEC filings and registrations for any relationship where you're making decisions based on regulatory status.
Here's why: Verification is cheap, fast, and definitive. The SEC's Investment Adviser Public Disclosure database and EDGAR system let you confirm registrations in minutes. The cost of checking is minimal compared to the exposure you take on if the claim is false.
The BG Wealth case shows that fraudsters will exploit verification gaps. They filed false documents knowing that most people would see the SEC filing and stop asking questions. That's exactly the behavior your compliance program should interrupt.
But verification alone isn't enough. You also need to train your team to recognize red flags in the filings themselves. Does the claimed business model match the filing type? Do the assets under management align with the entity's public profile? Are there disciplinary actions or amendments that suggest problems?
The verification step should prompt questions, not just check a box. When an entity claims to be "the world's largest hedge fund" but shows limited filing history, that's a signal to dig deeper.
Start with your highest-risk relationships and build verification into existing due diligence workflows. You're already collecting formation documents, tax IDs, and insurance certificates. Adding SEC registration confirmation to that list doesn't require a new process. It requires one additional step in a process you already run.
The alternative is accepting that your organization will rely on claims you never verified, creating exposure that regulators and prosecutors will scrutinize if something goes wrong.
