Affiliated Transaction Restrictions

Affiliated transaction restrictions require you to prevent a registered investment company (and its controlled entities) from entering prohibited principal transactions or joint arrangements with affiliates unless a specific SEC rule or exemptive order permits it. Operationally, you need an affiliate map, pre-trade/review gates in trading and operations, and board-ready documentation that shows the transaction was blocked or properly exempted. (15 U.S.C. § 80a-17)

Key takeaways:

• Section 17(a) focuses on principal “sell to / buy from” transactions between a fund and its affiliates. (15 U.S.C. § 80a-17)
• Section 17(d) and Rule 17d-1 focus on “joint arrangements” with affiliates and generally require prior SEC approval absent an exemption. (15 U.S.C. § 80a-17)
• Your control design should combine (1) affiliate identification, (2) transaction screening, and (3) evidence that exemptions were validated before execution. (15 U.S.C. § 80a-17)

“Affiliated transaction restrictions” are one of the most operationally fragile conflict-of-interest requirements in registered fund management because the rule boundary follows relationships, not intent. The same trade can be permissible one day and prohibited the next if ownership, control, or personnel changes create an affiliation. Section 17(a) of the Investment Company Act prohibits certain principal transactions between a registered investment company and its affiliated persons, unless an SEC rule or order provides an exemption. Section 17(d) and Rule 17d-1 extend the concept to joint arrangements or transactions between a fund and its affiliates, generally requiring prior SEC approval. (15 U.S.C. § 80a-17)

For a CCO or GRC lead, the implementation goal is simple: stop prohibited affiliate transactions before they happen, and document the legal basis when you allow an exempted one. That means you need (1) a reliable way to identify affiliates across funds, advisers, subadvisers, and controlled entities, (2) workflow controls that force a review before execution or settlement, and (3) recordkeeping that can survive an exam, board inquiry, or incident review. This page gives you requirement-level steps, artifacts, and common failure modes so you can operationalize quickly. (15 U.S.C. § 80a-17)

Regulatory text

Regulatory excerpt (provided): “Affiliated persons of a registered investment company are prohibited from engaging in certain transactions with the company unless exempted by SEC rule or order.” (15 U.S.C. § 80a-17)

Operator interpretation:
You must implement controls that (a) identify “affiliated persons” and affiliated entities relevant to each registered investment company you support, (b) prevent the fund from knowingly entering prohibited buy/sell principal transactions with those affiliates, and (c) prevent the fund from entering joint arrangements or joint transactions with affiliates unless an SEC rule or exemptive order allows it (and any conditions are met and documented). (15 U.S.C. § 80a-17)

What this means in practice:

• This is not a “disclose and proceed” requirement. It is a transaction restriction with limited carve-outs. (15 U.S.C. § 80a-17)
• You need a pre-execution decision point in the lifecycle. Post-trade detection is a control gap because the prohibition is about engaging in the transaction. (15 U.S.C. § 80a-17)
• Exceptions exist, but your process must identify the exemption, validate eligibility, and retain proof that you satisfied the exemption conditions before executing. (15 U.S.C. § 80a-17)

Plain-English requirement

Do not let the fund trade directly with its affiliates or enter shared deals with affiliates unless you have a clear, documented exemption. “Affiliate” is broader than employees; it can include entities under common control, certain owners, and other defined relationships. If you cannot prove the relationship analysis and exemption basis, treat the transaction as prohibited and block it until legal/compliance clears it. (15 U.S.C. § 80a-17)

Who this applies to (entity and operational context)

In-scope entities

• Registered investment companies (funds) and their operations, trading, and governance functions. (15 U.S.C. § 80a-17)
• Advisers/subadvisers and portfolio management teams executing trades or structuring transactions for registered funds. (15 U.S.C. § 80a-17)

In-scope activities

• Principal transactions where an affiliate is the counterparty to a purchase or sale involving the fund. (15 U.S.C. § 80a-17)
• Joint arrangements/joint transactions involving the fund and affiliates that could align or commingle interests outside ordinary arm’s-length dealing, unless permitted by SEC approval/exemption. (15 U.S.C. § 80a-17)
• Corporate actions and restructurings where an affiliate is on the other side (asset transfers, in-kind activity, cross trades, seeded positions, or special allocations) if structured as affiliate-to-fund dealing. (15 U.S.C. § 80a-17)

Where teams get surprised

• New affiliates created by ownership changes, new control relationships, or reorganizations. The prohibition follows the relationship graph, so your affiliate inventory has to stay current. (15 U.S.C. § 80a-17)

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

1) Define the prohibited transaction universe for your funds

Create a written “Affiliated Transaction Restrictions Standard” that translates Section 17(a) and 17(d)/Rule 17d-1 into operational categories your teams can recognize. Include:

• What counts as a principal purchase/sale with an affiliate. (15 U.S.C. § 80a-17)
• What you treat as a joint arrangement/joint transaction and how you route it for review. (15 U.S.C. § 80a-17)
• The rule that a transaction is blocked unless compliance confirms an exemption or SEC order applies. (15 U.S.C. § 80a-17)

Deliverable: a one-page “allowed vs prohibited vs requires escalation” decision table that traders and ops can use without calling Legal for every question.

2) Build and maintain an “affiliate map” you can operationalize

You need a living inventory of affiliated persons/entities relevant to each fund complex. Minimum fields:

• Legal entity name, identifiers (LEI if available), and relationship type (affiliate basis).
• Effective date and end date of the relationship.
• Coverage scope (which funds/advisers it applies to).
• Data owner (who updates it when relationships change).

Practical control: tie affiliate onboarding to your third-party/relationship intake workflow. If the adviser hires a new subadviser, introduces a new broker relationship, or enters a strategic partnership that changes control/ownership, that event must trigger an affiliate review and list refresh. (15 U.S.C. § 80a-17)

Daydream fit (where it earns its place): If you already run third-party due diligence and relationship inventories in Daydream, extend that record to include “fund affiliate” attributes and a compliance gating status so trading/ops can screen counterparties against a single system of record.

3) Put a pre-trade (or pre-commitment) gate in the workflow

Design the control so the business cannot bypass it under time pressure.

For liquid trading (equities/fixed income):

• Add counterparty screening in OMS/EMS or trade blotter controls against the affiliate list.
• Route “affiliate hit” trades to Compliance for disposition: block, approve under exemption, or escalate to counsel. (15 U.S.C. § 80a-17)

For private deals / structured transactions (where “joint arrangement” risk is higher):

• Require an “affiliate and joint arrangement” certification in the deal intake memo before IC approval.
• Compliance signs off on (a) affiliate status analysis, and (b) whether SEC approval/exemption is required. (15 U.S.C. § 80a-17)

Control design note: if you cannot screen pre-trade, build a “no-settlement without clearance” control at operations. That is weaker than pre-trade but still prevents the fund from completing the transaction.

4) Define exemption validation and documentation

The regulatory text provided flags that exemptions may exist via SEC rule or order, but you must treat exemptions as conditions-based. (15 U.S.C. § 80a-17)

Implement an “Exemption Validation Checklist” with:

• Citation to the specific SEC rule or exemptive order your counsel confirms applies. (15 U.S.C. § 80a-17)
• Eligibility criteria and conditions (written by counsel; do not rely on trader assumptions).
• Evidence required (pricing support, best execution support, board notice/approval requirements if applicable to the exemption terms, and any required disclosures).

If you do not have a confirmed exemption path, your procedure should require blocking the transaction and documenting the reason.

5) Surveillance, exceptions, and remediation

Even with a gate, you need detection and trend analysis:

• Weekly or monthly exception reports: affiliate hits, overrides, blocked trades, and near-misses.
• Root cause review for each exception: data quality, stale affiliate list, booking errors, or manual workaround.
• Corrective actions tracked to closure, with ownership and due dates.

If an affiliated transaction occurs without clearance, treat it as a compliance incident: preserve evidence, involve counsel, assess shareholder harm, consider unwind options, and document remediation.

6) Governance and training that matches the risk

• Train portfolio managers, traders, deal teams, and ops on the decision table and escalation triggers.
• Provide the fund board (or relevant governance forum) with periodic reporting on affiliate transactions screened, exceptions, and material relationship changes that affect the affiliate map.

Required evidence and artifacts to retain

Keep artifacts in a form that an examiner can follow end-to-end from relationship identification through transaction outcome.

Core artifacts

• Affiliated Transaction Restrictions policy/standard and procedure documents. (15 U.S.C. § 80a-17)
• Current affiliate map plus change log (who changed what, when, and why).
• Pre-trade screening logs or system reports showing the counterparty screen occurred.
• Compliance disposition tickets for affiliate hits (block/approve/escalate), including rationale and supporting docs.
• Exemption Validation Checklist and counsel sign-off (where applicable).
• Incident records for breaches/near-misses, including corrective actions.

Nice-to-have artifacts

• Training records and role-based training content.
• Periodic management/board reporting pack summarizing activity and exceptions.

Common exam/audit questions and hangups

Expect questions that probe whether your controls prevent violations or just detect them.

1. “Show me your list of affiliated persons and how you keep it current.”
   Hangup: lists maintained in email or spreadsheets without ownership, refresh triggers, or effective dates.

2. “Walk me through a sample affiliate hit from alert to final outcome.”
   Hangup: no case management trail, or approvals in chat with no retained rationale.

3. “How do you handle joint arrangements under Rule 17d-1?”
   Hangup: teams treat everything as a trade restriction and miss the “joint arrangement” structuring risk that arises earlier in the deal lifecycle. (15 U.S.C. § 80a-17)

4. “What happens if the system is down or the trade is time-sensitive?”
   Hangup: no manual fallback control, so the desk proceeds and “plans to document later.”

Frequent implementation mistakes and how to avoid them

• Mistake: treating “affiliate” as only employees or insider accounts.
  Fix: model affiliation as an entity-relationship problem. Include entities under common control and other relationship categories relevant to your fund complex. (15 U.S.C. § 80a-17)

• Mistake: post-trade reviews only.
  Fix: add a hard gate pre-trade or pre-settlement. Put it in the system people must use to execute. (15 U.S.C. § 80a-17)

• Mistake: “exemption” documented as a sentence with no conditions.
  Fix: require an exemption checklist and counsel-confirmed basis, then attach transaction-specific evidence.

• Mistake: affiliate list drift after reorganizations.
  Fix: integrate updates with legal entity management, M&A, new product launches, and third-party onboarding.

Enforcement context and risk implications

The provided sources do not include public enforcement cases for this page, so this section focuses on risk outcomes rather than case citations. A failure here can create:

• Regulatory risk: prohibited transactions can be treated as statutory violations if they fall within Section 17 restrictions without an exemption. (15 U.S.C. § 80a-17)
• Investor harm and reputational risk: affiliate self-dealing is a high-scrutiny theme because the rule exists to prevent conflicts that could disadvantage fund shareholders. (15 U.S.C. § 80a-17)
• Operational risk: unwind activity, valuation disputes, and board escalations consume time and can affect performance reporting.

Practical 30/60/90-day execution plan

Your pace depends on system complexity and fund strategies. Use this as a sequencing guide.

First 30 days (stabilize and stop the bleeding)

• Assign single ownership for the affiliate map and the transaction restriction procedure.
• Publish an interim decision table: prohibited, requires escalation, allowed with documented exemption. (15 U.S.C. § 80a-17)
• Implement a manual pre-clearance gate for any trade/deal where the counterparty might be an affiliate.
• Start an exception log immediately, even if tooling is basic.

Days 31–60 (systematize and evidence)

• Build the affiliate map with effective dates and change tracking.
• Embed screening into OMS/operations workflow, or implement a formal “no settlement without clearance” step.
• Stand up a lightweight case workflow (ticketing) for affiliate hits with required fields and attachments.
• Draft the exemption validation checklist template and route it through counsel for sign-off. (15 U.S.C. § 80a-17)

Days 61–90 (scale and govern)

• Expand coverage to non-trading scenarios (private deals, in-kind activity, special allocations) where joint arrangements can arise. (15 U.S.C. § 80a-17)
• Build recurring reporting for management/board: volume of screens, hits, blocks, approvals, and incidents.
• Run a tabletop test: simulate an affiliate relationship change and confirm downstream systems update and block/route transactions correctly.
• If you use Daydream for third-party and relationship governance, connect affiliate records to approval workflows and evidence retention so you can produce a clean audit trail quickly.

Frequently Asked Questions

Do affiliated transaction restrictions only apply to registered funds, or also to the adviser?

The prohibition described here is framed around transactions with a registered investment company, so the fund is central. The adviser and its personnel are operationally in-scope because they originate, approve, and execute transactions on the fund’s behalf. (15 U.S.C. § 80a-17)

What is the difference between a Section 17(a) transaction and a Rule 17d-1 issue?

Section 17(a) focuses on principal purchase/sale transactions between a fund and its affiliates. Section 17(d) and Rule 17d-1 address joint arrangements or joint transactions with affiliates, which often show up in deal structuring before any trade ticket exists. (15 U.S.C. § 80a-17)

Can we rely on disclosure or board awareness instead of blocking the transaction?

The provided requirement is a restriction, not a disclosure standard. If you do not have an applicable SEC rule or exemptive order, your process should treat the transaction as prohibited and prevent execution. (15 U.S.C. § 80a-17)

How do we operationalize this if our OMS cannot screen counterparties against an affiliate list?

Put the control at the next enforceable step: pre-settlement operations clearance with documented compliance sign-off. Then plan a system enhancement to move the control earlier in the lifecycle. (15 U.S.C. § 80a-17)

What evidence does an examiner typically expect for an allowed affiliated transaction?

Expect to produce the affiliate analysis, the specific exemption or order your counsel confirmed applies, proof that the exemption conditions were met for that transaction, and an auditable approval trail tied to the trade/deal record. (15 U.S.C. § 80a-17)

How often should we refresh the affiliate list?

Refresh on events that change relationships: new ownership/control information, reorganizations, new subadvisers, new related entities, and onboarding of key third parties that may be affiliates. Also run periodic reconciliation between your legal entity data and the affiliate map so drift is detected early.