The compliance architecture for a fund operating in both the United States and the European Union is often described as complex. That's technically accurate but not particularly useful. The more precise description: it's a problem of mapping two regulatory regimes — SEC and FINRA on one side, ESMA and national competent authorities on the other — that use different vocabulary to describe overlapping obligations, run on different amendment cycles, and have fundamentally different expectations for what compliance documentation looks like.
This post describes the structural approach we've developed for thinking about multi-jurisdiction compliance manual design. The scenario we'll use throughout: a registered investment adviser with SEC registration, FINRA-member broker-dealer affiliate, and marketing presence in three EU member states under the AIFMD marketing passport regime. This profile is realistic for a growing alternative fund manager with institutional investors on both sides of the Atlantic.
The Parallel-Manual Problem and Why It Fails
The default approach most mid-size asset managers take to multi-jurisdiction compliance is to maintain parallel compliance manuals: one covering SEC and FINRA obligations, a separate document covering EU-facing activities. This approach is operationally intuitive — the regulatory regimes look different, so keeping separate documents feels logical — but it creates serious maintenance problems at scale.
When the SEC publishes guidance that affects your conflicts of interest disclosures, the compliance team updates the US compliance manual. But conflicts of interest under the Investment Advisers Act and conflicts of interest under AIFMD Article 14 are addressing the same underlying obligation: disclosing and managing situations where the interests of the manager and the investor may diverge. An update to your US conflicts policy almost always has implications for your EU conflicts documentation — but if the two manuals are maintained independently, that connection is only made if someone on the team thinks to make it.
In practice, they often don't. The EU team is focused on ESMA. The US team is focused on the SEC. The gap accumulates quietly until the EU marketing compliance review, which typically happens annually or semi-annually, surfaces the divergence.
The Obligation-First Framework: A Different Way to Structure the Manual
The architecture we recommend — and that underpins how Pensvyne handles multi-jurisdiction mapping — starts not from the regulatory regime but from the underlying compliance obligation. Before deciding which document a policy lives in, ask: what is the actual obligation this policy addresses? Then: which regulators have rules that express this obligation, in what form, and with what specific requirements?
Fiduciary duty and best interest is a good example. SEC Rule 206(4)-7 under the Investment Advisers Act requires registered investment advisers to adopt written policies and procedures reasonably designed to prevent violations of the Advisers Act. The EU's AIFMD and MiFID II have their own frameworks for client best interest and suitability. Both regimes express a fiduciary-like obligation. The specific documentation requirements differ — the US framework is principles-based and outcome-oriented; the EU frameworks tend toward more prescriptive documentation standards — but the underlying obligation is the same.
In an obligation-first compliance manual, your "Conflicts of Interest and Fiduciary Duty" section addresses this obligation once, with sub-sections that map the specific requirements of each applicable regulatory regime. When the SEC updates its conflicts guidance, you're updating one section that has an explicit EU mapping, rather than two disconnected sections that will drift apart.
Constructing the Jurisdiction Applicability Matrix
The practical foundation for an obligation-first compliance manual is a jurisdiction applicability matrix: a document that lists every material compliance obligation in your manual and identifies which regulatory regimes apply to each, with the specific regulatory citation for each regime's version of the obligation.
For the hypothetical fund manager described above, the matrix would include rows like:
Conflicts of interest disclosure: US — Investment Advisers Act §206, Rule 206(4)-7, Form ADV Part 2A Item 10 | EU — AIFMD Article 14, Commission Delegated Regulation Article 30, ESMA Q&A on conflicts of interest under AIFMD.
Marketing materials review: US — Investment Advisers Act §206(4)(b), Rule 206(4)-1 (Marketing Rule) | EU — AIFMD Article 31/32 marketing passport regime, national competent authority marketing notification requirements per member state.
Record keeping: US — Investment Advisers Act Rule 204-2 (5-year retention, electronic records requirements) | EU — AIFMD Article 20, national competent authority-specific retention periods which vary.
The matrix itself isn't the compliance policy — it's the navigational infrastructure that makes the policy maintainable. When ESMA publishes guidance on AIFMD marketing, the first question is: which rows of the matrix does this guidance affect? That question can be answered systematically rather than relying on whoever happens to be managing the EU monitoring queue that week.
The Documentation Standard Gap Between US and EU Regimes
One of the most practically difficult aspects of building a unified compliance framework is reconciling documentation standards. US compliance frameworks, particularly under the Investment Advisers Act, tend to describe what documentation must exist and leave the format to the firm's judgment. EU frameworks under AIFMD and MiFID II tend toward more explicit requirements: what specific information must be in a disclosure, in what form, reviewable by the relevant national competent authority on request.
This creates a calibration challenge: your compliance manual can either meet the higher documentation specificity standard (EU) for all obligations across both regimes, or it can flag the documentation standard differences explicitly and maintain different documentation protocols for US and EU obligations.
We're not suggesting there's one correct answer here — the right approach depends on the firm's EU exposure footprint and the cost of maintaining differentiated documentation protocols. But we've observed that firms that adopt the higher documentation standard for all obligations tend to fare better in both US and EU reviews than firms that maintain a minimum-documentation-sufficient-for-each-regime approach. The reasons are partly practical: when an SEC examiner asks for evidence of how a conflict was managed, a detailed EU-standard contemporaneous record is more useful than a US-standard brief internal memo.
Tracking Amendment Cycles: US and EU Move at Different Speeds
The practical reality of US-EU compliance monitoring is that the two regimes don't move in sync. The SEC has its own amendment calendar; ESMA has its own. National competent authority guidelines in individual EU member states have their own update schedules, and marketing passport status can be affected by regulatory changes in a specific member state without any ESMA-level announcement.
For a fund marketing in Germany, France, and Luxembourg, for example, BaFin, AMF, and CSSF each publish guidance relevant to your marketing activities that may not have a counterpart in ESMA-level publications. A compliance monitoring system that only tracks ESMA and SEC will miss the national-level amendments that can affect your marketing compliance position in individual member states.
When we built Pensvyne's multi-jurisdiction capability, this monitoring breadth was the primary design constraint. It's not enough to monitor the headline regulators; the obligation-to-policy mapping has to extend to national competent authority communications for each member state in which the fund has marketing authorization. For a fund in three EU member states, that means monitoring six to eight regulatory bodies on the EU side alone — in addition to the US federal and state-level regulatory environment.
Annual Compliance Review Timing in a Multi-Jurisdiction Environment
The Investment Advisers Act Rule 206(4)-7 annual review requirement is well understood by US-registered advisers. What's less often discussed is how the timing of that annual review interacts with EU-side review obligations. AIFMD doesn't specify an annual compliance review in the same terms as the US framework, but national competent authority expectations — and the marketing passport maintenance obligations — create de facto review trigger points throughout the year.
For a fund with a fiscal year end and a Q1 annual Form ADV update cycle, the practical approach is to run the US compliance annual review in Q1 alongside the Form ADV process, and to run the EU compliance review in Q3 — with a mid-cycle check triggered by any significant regulatory change in either regime. This avoids the situation where a material EU regulatory change published in October doesn't get addressed until the following Q1 US review cycle.
The jurisdiction applicability matrix described earlier is what makes the mid-cycle check efficient. When ESMA publishes new guidance in September, the question is not "does this affect anything?" — it's "which rows of the matrix does this affect, and when is the next scheduled review of those obligation areas?" That's a structured question with a specific answer, rather than a general anxiety that someone might be missing something.