CPA Mobility Has Limits

CPA mobility is a powerful tool — but it has limits. Understanding the relationship between your CPAs’ residence, their principal place of business, and licensure is foundational to keeping your firm in good standing.

When firm administrators think about CPA licensing compliance, they tend to focus on whether a staff member holds a valid license. That’s the right instinct. But there’s a dimension of compliance that often gets overlooked: where a CPA actually lives and is assigned to work.

CPA mobility gives out-of-state practitioners a temporary practice privilege in other states. It’s a legitimate and widely-used mechanism, but it was never designed to be a substitute for holding a license where you reside and primarily work. Treating mobility as a catch-all solution for licensure gaps is one of the more common — and more consequential — compliance mistakes firms make.

The Residence Question

Most states have “holding out” provisions that restrict who can use the CPA title or represent themselves as a CPA within state borders. These rules generally expect anyone who permanently lives and practices in a state to hold a license there — not just benefit from a mobility provision designed for temporary, cross-border work.

As a general rule, CPAs should hold a license in their principal place of business, which may not always be the same as where they live. That distinction matters.

Example

Consider a CPA who lives in Virginia but works for a firm headquartered in Washington, D.C. If their primary office is in D.C., a D.C. license may be appropriate — and a Virginia license may not be required. But if that same person begins practicing out of the firm’s Virginia office, or starts regularly serving Virginia-based clients, the calculus changes. Because they reside in Virginia, they would not be covered by a temporary mobility privilege and would need to obtain a Virginia license.

It’s a scenario that plays out more often than firms expect — especially as remote and hybrid work has made the line between “where someone works” and “where someone lives” much blurrier than it used to be. 

What “Principal Place of Business” Actually Means

Each state defines the term slightly differently, but principal place of business generally refers to the location where a CPA primarily practices. In many states, this is the office to which the individual is formally assigned — not necessarily where they happen to log in on a given day.

That definition has real implications. A CPA who is assigned to a Chicago office but splits time between client sites in three states has a principal place of business in Illinois. Their mobility coverage in other states flows from that anchor. If their licensure doesn’t reflect that anchor accurately, their mobility status in other jurisdictions may be indeterminate. It’s not a technicality — it’s the foundation the entire mobility framework is built on.

Why This Creates Compliance Risk for Firms

The challenge for firm administrators is that this kind of mismatch is easy to miss. Staff members may have moved without updating their records. Work assignments may have shifted. Someone may have transferred from one office to another. None of these changes automatically triggers a licensing review.

Without a systematic way to surface these discrepancies, firms often don’t know there’s a problem until an audit, a client engagement question, or a state board inquiry forces the issue. By that point, the exposure is already there.

That’s why checking a staff member’s residence jurisdiction and confirming her principal place of business — not just her license status — is part of a complete compliance picture. A CPA can hold a perfectly valid license in one state and still be out of compliance simply because she’s moved and that state’s board expects her to be licensed locally.

How CPA QualityPro Helps Surface the Gap

When you check a staff member’s mobility status in CPA QualityPro, the system evaluates whether her residence jurisdiction aligns with her current licensure. If there’s a mismatch — if someone lives in a state where they don’t hold a license — the system will flag that she does not have mobility privileges to serve clients in that state. 

Similarly, if a staff member’s profile doesn’t include a license that matches his principal place of business, mobility determinations won’t be available for that individual until the underlying licensure issue is addressed. That’s intentional: the system is built to reflect the actual requirements of the mobility framework, not to paper over gaps that could create real exposure.

Residence jurisdiction and principal place of business aren’t just data fields. They’re the foundation that mobility is built on — and making sure they’re accurate is one of the most important things a firm can do to remain in compliance.