Notes from Portland: What Oregon CPAs Are Asking About MSO Adoption

FIELD NOTES · OREGON CPAs

Notes from Portland: What Oregon CPAs Are Asking About MSO Adoption

The Management Services Organization is no longer an unfamiliar acronym in the Pacific Northwest tax community. The unmet need is on the wealth-planning side, and it sits inside Section 482.

By Alex Jones, EA, CFP®, ChFC®, CLU®, CEPA, Founder & CEO, Guardian Tax Consultants® · June 9, 2026 · 8 min read

---

Portland in late January is a serious room. Across a week of firm visits and Oregon Society of CPAs continuing-education sessions in the Portland and Eugene corridors, the pattern that emerged among partner-level practitioners was consistent enough to be worth a note: the Pacific Northwest tax community already understands the Management Services Organization in its private-equity and M&A context. What Oregon CPAs are asking now is how to apply the same structure on the wealth-planning side without taking on Section 482 transfer-pricing risk themselves. The partner-level questions in the Q&A sessions are usually the most instructive part of the day, and this year they pointed in one direction.

Where the MSO conversation has moved

Five years ago, an MSO mention in a Top-100 firm setting prompted a definitional question. That is no longer the prevailing posture. Across the Portland-metro practices we visited, partners described the MSO as a known structure inside the buy-side, the rollup, and the platform-acquisition contexts they read about in Accounting Today and the AICPA trade press. Holland & Knight and other M&A counsel routinely treat the alternative practice structure used by Baker Tilly, Aprio, and Citrin Cooperman as a publicly documented template. CPAs are not asking what an MSO is. They are asking how to position the same structure for a private family, in a closely-held operating business, without inheriting the substantiation work that protects the related-party fee at the heart of it.

That is a different question than the one the M&A literature answers. The deal context turns on enterprise-value mechanics, alternative-practice-structure governance, and licensure firewalls between attest and advisory. The wealth context turns on whether the management fee paid from an operating company to a related Management Services Organization is defensible under Internal Revenue Code §482, deductible as an ordinary and necessary expense under §162, and outside the reach of the personal-service-corporation reallocation authority in §269A. The CPA community in the Pacific Northwest is comfortable with the first set of questions. The second is where the room slowed down.

The distinction matters because the audit posture moves with it. In the platform-acquisition fact pattern, the related-party fee is typically priced inside a transaction governed by negotiated economics and overseen by an outside investor with independent diligence. The substantiation file is built once, at close, and refreshed inside an institutional governance frame. In the private-family fact pattern, there is no outside investor, no closing memorandum, and no diligence team. The substantiation file has to be built by the practitioners on the engagement, and it has to be maintained contemporaneously over the life of the structure. That is the work the Oregon partners we visited said they wanted help with. Not the structure itself. The file behind it.

The wealth-side §482 gap is a substantiation file, not a tax theory

What the Oregon CPAs we met with described, in slightly different words across several conversations, is not a knowledge gap about the underlying tax mechanic. They understand that a Management Services Organization charges a fee for management, administrative, treasury, and back-office services rendered to a related operating company. They understand the deduction sits in §162 and the related-party pricing sits in §482. What they do not want to build, in the middle of busy season, is the contemporaneous substantiation file that supports the position.

That file is materially different from the diligence package an M&A team assembles. Under Treasury Regulation §1.482-9, related-party services pricing is evaluated against an arm's-length standard, with the regulation specifying ordered methods, including the services cost method, the comparable uncontrolled services price method, the gross services margin method, the cost of services plus method, the comparable profits method, and the profit split method. Selecting and supporting the appropriate method requires a functional analysis of the services rendered, an identification of the assets used and risks borne by each party, a benchmarking exercise against comparable transactions, and a written record of the methodology applied. The OECD Transfer Pricing Guidelines, while not binding on U.S. taxpayers, are treated as persuasive authority and follow a similar structure for intra-group services in their Chapter VII.

None of that work is novel for a transfer-pricing economist. None of it is routine for a regional CPA practice. The Oregon partners we spoke with were unambiguous about that line: the §482 file is specialty work, and they would rather coordinate with someone who owns it than carry the labor themselves.

Why the CPA partner does not want to build the §482 file

Two reasons surfaced, and in roughly that order. The first is labor. Constructing a defensible related-party services fee, from functional analysis through benchmarking through method selection through contemporaneous documentation, is not a one-afternoon exercise and it is not a deliverable that fits inside a 1040 or 1120 engagement scope. The second is risk. The economic-analysis layer of §482 carries its own examination posture. Practitioners on the wealth side are appropriately cautious about underwriting the statutory basis for the fee in their own working papers when the substantiation methodology sits outside the firm's core competency.

This is the part of the conversation where the partner-with-specialist model is most useful to describe plainly. An independent transfer-pricing economics practice produces the §482 economic analysis for the related-party arrangement, working alongside the CPA on the closely-held engagement. The CPA continues to own the return and the client relationship. The specialist owns the contemporaneous substantiation file. Each party is doing the work it is best positioned to defend. The partners we spoke with did not view this division of labor as a loss of scope. They viewed it as the way the engagement should have been structured from the outset.

What the CPA practice gains when the MSO structure is built properly

Framed as practice economics rather than as a sales pitch, the proposition is straightforward. An MSO structured for a private operating-company client produces a second federal compliance return, which the CPA continues to prepare. The contemporaneous documentation discipline generates ongoing advisory work tied to functional-analysis updates, benchmarking refresh cycles, and the annual review of method selection as facts change. Where the operating-company shareholders are positioning for an eventual exit, the structure can also touch on adjacent planning questions such as §1202 qualified small business stock treatment, which the CPA continues to coordinate at the return level. The CPA refers the client into a structure the firm did not have to underwrite on the economic-analysis side, while continuing to serve as the relationship principal who files the return and signs the engagement letter for the planning work that orbits it. None of that requires the CPA to become a transfer-pricing economist. It requires only that the substantiation deliverable arrive in the form the CPA's workpaper file can accept.

Several partners flagged a related point. When the substantiation file is reviewer-readable and produced contemporaneously, the engagement letter can contemplate the CPA's continuing role without ambiguity. That is the form of co-delivery the CPA community in the Pacific Northwest is asking for. It preserves the compliance relationship. It does not displace it.

A reviewer-readable file, in this context, has a recognizable shape. It opens with a functional analysis describing the services the Management Services Organization actually provides, the personnel rendering them, and the assets and risks borne by each related entity. It identifies the regulatory method selected under Treasury Regulation §1.482-9 and explains why that method is the best measure of an arm's-length result for the services in question. It documents the comparable transactions or benchmarking dataset used to test the fee, with the search methodology disclosed in enough detail to be repeatable. It records the conclusion, ties it back to the intercompany services agreement, and is updated annually as facts change. The CPA workpaper file references the substantiation file as a relied-upon deliverable; the relationship between the two is documented in the engagement letter. None of this is exotic. It is the discipline the regulation contemplates.

What the conversation is not

A framing point. The Portland conversation is not what it can be mistaken for. It is not a critique of the CPA's traditional role. It is not an argument that the practitioners we visited are behind their peers; the opposite was true in every meeting. And it is not a position on how the Internal Revenue Service should treat any particular fact pattern. The Service's audit posture on related-party services is well documented in the regulation and in published guidance. The observation, narrowly, is that the §482 economic-analysis layer is specialty work, and the practices we met with were thoughtful about not absorbing it into a compliance scope built for a different purpose.

The dollar amounts do not appear in this note. The named partners do not appear in this note. The pattern is what was worth recording: a regional CPA community that already understands what an MSO is, asking for a partner who can produce the substantiation file that supports it, in a form the firm's working papers can rely on.

After the Portland conversations, our team reviewed the published record on where the MSO structure now sits in professional-services M&A. Holland & Knight, whose legal-services transactions team has been among the most active in documenting MSO partnerships in the legal market, has observed that the Management Services Organization is no longer an exotic structure on the buy side — it is the architecture sponsors and operators are using to capitalize advisory practices while preserving the licensed function. That observation, framed for legal practice but structurally identical, lines up with what the Oregon CPAs we visited were already describing on the wealth-planning side. The structure has matured; the substantiation discipline is what advisors are now asking for help carrying.

Closing observation

The CPA's role in the MSO conversation has matured from gatekeeper to coordinator. In Portland that shift is already visible: the question on the floor is no longer whether the structure belongs in a private-family tax plan, but who carries the §482 file that makes the planning defensible. The work has not gotten easier. The division of labor has gotten clearer.

---