State Investment Adviser Registration

To meet the state investment adviser registration requirement, you must not provide investment advice “in a state” unless your firm is registered under that state’s securities act or you can document a valid exclusion or exemption. Operationally, that means performing a state-by-state jurisdiction analysis, registering through IARD where required, and running an ongoing monitoring process as clients, personnel, and AUM change. (Uniform Securities Act § 403)

Key takeaways:

• If you “transact business” as an investment adviser in a state, registration or a documented exemption is mandatory. (Uniform Securities Act § 403)
• Multi-state operations require a repeatable jurisdiction and “place of business” analysis, not a one-time filing exercise. (Uniform Securities Act § 403)
• Your exam readiness depends on evidence: IARD filings, exemption memos, licensing proof, brochure delivery records, and books-and-records discipline. (Uniform Securities Act § 403)

State investment adviser registration is a gatekeeping requirement: before you advise for compensation, you need to know whether your advisory activity triggers registration in a specific state, and you need to prove you handled that determination correctly. The regulatory risk is straightforward. If you transact business in a state as an investment adviser without being registered (or without a valid exclusion or exemption), you are operating unlawfully under the state securities act. (Uniform Securities Act § 403)

For a CCO or GRC lead, the operational challenge is not filing a form once. It is building a control system that answers three exam questions on demand: (1) where are we required to be registered today, (2) what changed since the last determination, and (3) what evidence shows we delivered required disclosures and maintained required records across the states where we operate. State rules vary, but your program should be consistent: a jurisdictional decision memo, IARD-based filings where required, and ongoing monitoring tied to client location, employee location, AUM, and business footprint. (Uniform Securities Act § 403)

This page gives requirement-level implementation guidance you can execute quickly, with artifacts to retain and the exam hangups that typically cause deficiencies.

Regulatory text

Requirement (operator view): You cannot transact business in a state as an investment adviser unless you are registered under that state’s securities act or you qualify for, and can support, an exclusion or exemption. (Uniform Securities Act § 403)

Regulatory excerpt: “It is unlawful for any person to transact business in a state as an investment adviser unless the person is registered under the state's securities act or is excluded or exempt from the definition of investment adviser.” (Uniform Securities Act § 403)

What this means in practice: Your firm needs a defensible, documented answer for each state implicated by your operations: register, or document why you do not have to register. Treat “transact business” as a facts-and-circumstances trigger tied to where clients are, where advisory personnel sit, and where you maintain a place of business. (Uniform Securities Act § 403)

Plain-English interpretation

This requirement is a licensing and jurisdiction rule. If your advisory firm has clients in a state, solicits in that state, or has an office (or other “place of business”) connected to advisory activity in that state, you should assume state regulators expect either registration or a clearly documented exemption/exclusion analysis. (Uniform Securities Act § 403)

A common operational reality: you may be correctly registered in your home state but still create exposure elsewhere through remote employees, temporary offices, or onboarding clients who reside in another state. If you cannot explain your registration footprint with current data, you should treat that as a compliance gap. (Uniform Securities Act § 403)

Who it applies to

In-scope entities

• State-registered investment advisers and advisers that may be required to register at the state level (for example, firms that generally have less than a material amount million in AUM and are not registered with the SEC). (Uniform Securities Act § 403)
• Financial institutions or advisory affiliates that offer advisory services and need to determine whether the advisory entity itself must register or qualifies for an exclusion/exemption. (Uniform Securities Act § 403)

In-scope activities and operational contexts

• Taking on advisory clients in new states (including digital acquisition).
• Employing investment adviser representatives (IARs) who work from different states (including remote work).
• Opening, closing, or relocating any office used for advisory business.
• Acquisitions or lift-outs that change client distribution.
• Crossing regulatory thresholds that shift registration from state to SEC (or the reverse), which can affect state notice filings and ongoing obligations. (Uniform Securities Act § 403)

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

1) Map your “where we do business” facts (create a living inventory)

Build a single source of truth that ties together:

• Client list with client residency/state and service model (discretionary vs. non-discretionary).
• All advisory personnel locations, including remote work addresses.
• Offices/locations used to meet clients or conduct advisory business (your “place of business” footprint).
• Current AUM and any expected changes that could affect state vs. SEC registration posture. (Uniform Securities Act § 403)

Operator tip: Don’t rely on the CRM alone. Tie this inventory to HR and payroll location data so remote moves trigger compliance review.

2) Perform a state-by-state registration decision (document it)

For each state implicated by the inventory, document one of these outcomes:

• Register required (then list the filing path and owners).
• Exempt/excluded (then cite the specific basis under that state’s approach and retain support).
• Not doing business in the state (then document why your facts do not meet the trigger). (Uniform Securities Act § 403)

Because state rules vary, your memo should be structured for exam defensibility: facts first, conclusion second, and a clear owner for ongoing monitoring.

3) Execute registration filings through IARD where required

State registration “generally” involves filing Form ADV through IARD and meeting state conditions such as qualifying examinations, brochure delivery, and books-and-records readiness. (Uniform Securities Act § 403)

Minimum operational tasks to assign and track:

• Prepare/refresh Form ADV content and approvals workflow.
• Submit filings via IARD for the firm and, as applicable, IARs.
• Track state approvals, effective dates, and renewal requirements.
• Maintain a state-by-state compliance obligations matrix (what differs by state, who owns it). (Uniform Securities Act § 403)

4) Build the disclosure delivery and recordkeeping workflow

State expectations “generally” include:

• Providing client brochures (Form ADV Part 2A) and brochure supplements (Part 2B as applicable).
• Maintaining required books and records.
• Complying with state-specific conduct rules. (Uniform Securities Act § 403)

Operationalize this with controls you can test:

• A pre-contract checklist: no advisory agreement countersignature until the state registration decision is “Register active” or “Exemption approved.”
• An onboarding evidence packet: brochure delivery method and timestamp, executed agreements, and fee schedule.
• A records retention map: which systems store communications, trade instructions (if relevant), client agreements, and disclosures, plus who can retrieve them on request.

5) Implement ongoing monitoring (the part most teams under-build)

Create change triggers that force re-analysis:

• New client in a new state.
• Client move to a new state.
• Employee relocation or new hire in a new state.
• New office/address used for meetings.
• Material AUM changes that could alter registration posture. (Uniform Securities Act § 403)

If you use Daydream to manage third-party risk and compliance workflows, treat registration-impacting vendors as in-scope third parties for controls testing and evidence capture: IARD filing support providers, compliance consultants, recordkeeping platforms, and client onboarding systems. Your risk is operational, but your dependencies are third party-heavy.

Required evidence and artifacts to retain

Keep artifacts in a form you can produce quickly by state and by time period:

• Jurisdiction analysis memo (state-by-state) with date, owner, facts relied on, and decision.
• IARD filing evidence: submission confirmations, approval notices, and amendment history for Form ADV. (Uniform Securities Act § 403)
• Licensing/exam evidence for relevant personnel where applicable (for example, Series 65 or Series 66 proof where your program requires it). (Uniform Securities Act § 403)
• Disclosure delivery logs for brochures and supplements: delivery method, date/time, recipient, and version.
• Books and records index: systems of record, retention ownership, and retrieval procedure. (Uniform Securities Act § 403)
• Change-management tickets showing review of triggers (new state client, employee move, new office).

Common exam/audit questions and hangups

Expect examiners (or internal audit) to probe:

• “Show me how you determined which states require registration.”
• “How do you prevent onboarding a client in a state before you are properly registered or exempt?”
• “How do you monitor remote employees’ work locations and assess ‘place of business’ risk?”
• “Provide evidence that brochures were delivered to clients and that the delivered version matches your filed ADV.”
• “Show me your process for keeping Form ADV current as your business changes.” (Uniform Securities Act § 403)

Hangups that often cause findings:

• Registration decisions made verbally or embedded in emails with no formal approval.
• No linkage between HR address changes and compliance review.
• ADV amendments handled ad hoc, without a documented trigger list tied to business events. (Uniform Securities Act § 403)

Frequent implementation mistakes (and how to avoid them)

1. Treating state registration as a one-time launch task
   Fix: Put registration status in your onboarding gate and in your change-management workflow. Every new state touchpoint should create a compliance ticket with evidence. (Uniform Securities Act § 403)

2. No defensible definition of “where we do business”
   Fix: Maintain an inventory that reconciles client address data (CRM), billing data, and advisory personnel locations (HR). Document discrepancies and resolution.

3. Confusing firm registration with IAR coverage
   Fix: Track both at the control level. Your state matrix should have separate columns for firm registration status and IAR registration/licensing status where applicable. (Uniform Securities Act § 403)

4. Weak brochure delivery proof
   Fix: Standardize delivery (portal with logs, e-sign with timestamps, or tracked email) and store a copy of the exact brochure version delivered.

Enforcement context and risk implications

The core risk is statutory: transacting business without registration (or without a valid exemption/exclusion) violates state law. That creates exposure to state regulator actions, business disruption, and client remediation expectations. Your best defense is not a narrative. It is evidence that your firm consistently performs jurisdiction analysis, files through IARD when required, and runs ongoing monitoring as your footprint changes. (Uniform Securities Act § 403)

Practical 30/60/90-day execution plan

First a defined days (stabilize and stop inadvertent violations)

• Assign an accountable owner for state registration decisions and IARD filings.
• Build the “where we do business” inventory (clients, personnel locations, offices).
• Implement a temporary onboarding gate: compliance sign-off required before contracting with any client in a new state. (Uniform Securities Act § 403)

Days 31–60 (formalize decisions and close gaps)

• Produce the state-by-state jurisdiction analysis memo and approvals.
• File needed registrations/amendments through IARD; document the submission and status trail. (Uniform Securities Act § 403)
• Stand up brochure delivery logging and a centralized “version control” repository.

Days 61–90 (make it durable and exam-ready)

• Implement automated triggers from HR/CRM to compliance review (employee moves, new client states).
• Create a state obligations matrix and incorporate it into compliance testing.
• Run an internal mock exam: pick a state, then prove registration status, brochure delivery, and record retrieval end-to-end. (Uniform Securities Act § 403)

Frequently Asked Questions

We are SEC-registered. Do we still have to think about state registration?

This requirement is state-based and turns on whether you transact business in a state as an investment adviser unless you are excluded or exempt. Your program should document how you evaluate state requirements and exemptions as your footprint changes. (Uniform Securities Act § 403)

What is the minimum defensible documentation for claiming an exemption?

Keep a dated jurisdiction memo that states the facts, the exemption/exclusion basis you are relying on, and who approved it. Update it when your client distribution, personnel locations, or offices change. (Uniform Securities Act § 403)

How do remote employees affect state registration risk?

Remote work can create a “place of business” footprint and can change where you are viewed as transacting business. Tie HR location changes to a compliance review ticket and update your state matrix accordingly. (Uniform Securities Act § 403)

What evidence do examiners expect for Form ADV and brochure delivery?

Retain IARD filing confirmations and amendment history for ADV, plus delivery logs showing when each client received the applicable brochure and supplement version. This is part of the “generally” expected state registration package. (Uniform Securities Act § 403)

We only have a handful of clients in another state. Can we ignore it?

Do not guess. Document the state-by-state de minimis and registration analysis and keep support for your conclusion. If you cannot support an exemption, treat it as a registration requirement and escalate. (Uniform Securities Act § 403)

How do we operationalize this across multiple states without losing control?

Use a single state matrix, an onboarding gate, and change triggers tied to client and employee locations. A workflow tool like Daydream can help you track approvals, collect IARD and disclosure artifacts, and show a clean audit trail.