MSO Management-Fee Timing: The 12-Month Rule, §267(f), and Controlled-Group Service Payments

TECHNICAL BRIEF · TAX TIMING

How the 12-month rule under Treas. Reg. § 1.263(a)-4(f) and the controlled-group deferral rules of IRC § 267(f) interact in Management Services Organization fee timing.

By Mike Claudio, Co-Founder, Guardian Tax Consultants®. Published May 21, 2026. Last reviewed: June 25, 2026.

This brief outlines the general statutory and regulatory framework for MSO management-fee timing. Application to any specific fact pattern requires independent review by qualified tax counsel. Guardian Tax Consultants® does not issue legal opinions or determine final tax treatment.

Executive summary

No single Code section determines deductibility. The analysis requires consideration of § 162, § 482, § 267(a)(2), § 267(f), Treas. Reg. § 1.263(a)-4(f), Treas. Reg. § 1.461-4, the taxpayer’s accounting method, and the specific facts of the arrangement.

Management Services Organizations and their related operating companies often sit inside the same controlled group. That relationship does not, by itself, prevent the operating company from deducting a management fee or require the MSO to defer income recognition.

The analysis turns on the character and timing of the payment. If the payment is reasonable compensation for actual services, supported by a Management Services Agreement, performed within the applicable service period, and priced under a defensible § 162 and § 482 framework, § 267(f) should not be treated as a categorical bar to deduction. Section 267(f) is aimed primarily at controlled-group property-loss transactions, not bona fide service-fee arrangements.

The more relevant timing questions are whether the 12-month rule under Treas. Reg. § 1.263(a)-4(f) avoids capitalization, whether economic performance and the all-events test are satisfied under § 461, whether § 267(a)(2) defers an unpaid related-party accrual, and whether the MSO recognizes the corresponding income under its accounting method.

What § 267(f) does not do

• Section 267(f) does not automatically disallow an MSO management-fee deduction because the entities are related.
• It does not automatically defer a bona fide service fee merely because the MSO and operating company are in the same controlled group.
• It does not convert a service arrangement into a property transaction.
• It does not replace the separate requirements of § 162, § 482, § 461, § 263, or § 267(a)(2).

The better reading is narrower: § 267(f) is primarily a controlled-group property-loss deferral rule. A reasonable management fee for services actually rendered is tested under the service-fee rules, not treated as a property-loss transaction merely because the parties are related.

What this brief does not say

• This brief does not say every MSO management fee is deductible.
• It does not say a related-party management fee is immune from IRS review.
• It does not say § 267 rarely applies to MSO structures.
• It does not say a prepaid fee can cover services beyond the 12-month rule or next-year deadline.
• It does not say a property transfer can be relabeled as a service fee.

The narrower point is that § 267(f), standing alone, does not preclude deduction and income recognition for a bona fide, reasonable, documented MSO service-fee arrangement.

I. Framework for analysis — six layered authorities

Deduction of a related-party MSO management fee is not authorized by any single Code section. The position survives review by clearing six layered authorities in sequence:

1. IRC § 162 — Is the management fee an ordinary and necessary business expense?
2. IRC § 482 — Is the fee arm’s length and supported by an FMV / transfer-pricing analysis?
3. IRC § 267(a)(2) — Are the related-party matching rules satisfied (deduction by accrual payer deferred until the cash-method payee includes the corresponding amount in income)?
4. IRC § 267(f) and Treas. Reg. § 1.267(f)-1 — Are there controlled-group property-loss timing considerations? Note: this regime targets property transactions, not bona fide service fees.
5. Treas. Reg. § 1.263(a)-4(f) — Does the 12-month rule prevent capitalization of a prepayment?
6. IRC § 461 and Treas. Reg. § 1.461-4 — Does the payer’s accounting method and the economic-performance rule fix the deduction year?

The remainder of this brief walks each step in sequence. The key analytical move: § 267(f) is not the source of authority for deducting prepaid management fees. The deduction authority is § 162 (ordinary/necessary), § 482 (arm’s-length amount), § 263 (capitalization, with the 12-month rule as carve-out), and § 461 (timing). § 267(f) addresses controlled-group property losses; § 267(a)(2) addresses related-party accrual-to-cash matching. Conflating these regimes is the most common technical error in MSO fee planning.

Subsequent sections address the role of § 267(f), the 12-month rule under Treas. Reg. § 1.263(a)-4(f), the accrual-method economic-performance rule, the related-party matching mechanic of § 267(a)(2), and three worked examples covering the principal accounting-method combinations.

II. Why timing matters in MSO controlled-group structures

Management-fee timing is the single most-examined line in an MSO program. The deduction is large by design; the payer and the payee are related parties under IRC § 267; and the entities often close their books on different dates. Each of those features by itself draws scrutiny. Together, they create three distinct timing problems that have to be solved in the same set of facts.

The capitalization problem. A prepayment for services that span more than one year can be required to be capitalized under IRC § 263. If capitalization applies, the operating company loses its current deduction and the structure’s primary economic premise is impaired. The 12-month rule of Treas. Reg. § 1.263(a)-4(f) may avoid capitalization under § 263, but it does not independently establish reasonableness under § 162, arm’s-length pricing under § 482, economic performance under § 461, or matching under § 267(a)(2).

The matching problem. Related-party transactions risk producing an asymmetric tax answer — deduction on one side, deferred income on the other. IRC § 267(a)(2) and § 267(f) are designed to prevent that asymmetry by forcing matching. For property transactions between controlled-group members, § 267(f) defers loss recognition; for accrual deductions to related cash-method payees, § 267(a)(2) defers the deduction until the payee includes the amount in income.

The economic-performance problem. Accrual-method taxpayers cannot deduct a liability until the all-events test of Treas. Reg. § 1.461-1 is satisfied and economic performance has occurred under IRC § 461(h). For services, economic performance generally occurs as the services are provided. A prepayment that anticipates services not yet rendered may fail the all-events test absent the 12-month rule.

An MSO fee program that survives examination has to defend the answer to all three problems on a single, contemporaneous record. Sections II through IV unpack each regime; Sections V through VII translate the framework into the practical questions that recur in MSO documentation review.

III. The 12-month rule under Treas. Reg. § 1.263(a)-4(f)

Treas. Reg. § 1.263(a)-4 is the principal capitalization regulation for amounts paid to acquire or create intangibles. Subsection (f) carves out a critical safe harbor: a taxpayer is not required to capitalize amounts paid to create (or facilitate the creation of) any right or benefit for the taxpayer that does not extend beyond the earlier of (i) 12 months after the first date on which the taxpayer realizes the right or benefit, or (ii) the end of the taxable year following the taxable year in which the payment is made.

The rule has two limbs. The first — the 12-month limb — is a duration cap. The benefit period cannot exceed 12 months measured from the first date of realization. The second — the next-year limb — is a deadline cap. The benefit must not extend beyond the end of the taxable year following the year of payment. A prepayment satisfies the rule only if it clears both limbs.

Application to service payments

For service payments specifically, Treas. Reg. § 1.263(a)-4(b)(3)(iii) clarifies that amounts paid in performing services under an agreement are not treated as creating a separate and distinct intangible asset, regardless of whether the amounts result in the creation of an income stream under the agreement. For taxpayers otherwise eligible to deduct prepaid service expenses, the 12-month rule may prevent capitalization and support current deduction, subject to accounting-method and economic-performance rules.

That clarification matters for MSO design. A management-fee payment is not the acquisition of an intangible; it is consideration for ordinary administrative, back-office, advisory, and operational services. The 12-month rule applies on its terms, and the operating company can deduct the fee in the year of payment so long as the services are rendered within the 12-month period and the duration of the engagement does not push the benefit past the next year-end.

The all-events test and economic performance

The 12-month rule does not stand alone. For an accrual-method operating company, the deduction also has to satisfy the all-events test of Treas. Reg. § 1.461-1(a)(2) and the economic-performance requirement of IRC § 461(h). The all-events test is met when the fact of liability is fixed and the amount can be determined with reasonable accuracy. Economic performance, for services provided to the taxpayer, generally occurs as the service provider performs (Treas. Reg. § 1.461-4(d)(2)).

The recurring-item exception under IRC § 461(h)(3) and Treas. Reg. § 1.461-5 may also apply for recurring service liabilities that are economically performed within the shorter of 8½ months or a reasonable period after year-end. The recurring-item exception and the 12-month rule are separate doctrines with different conditions; they can support the same accrual but should be analyzed independently.

IV. IRC § 267(f) — deferred loss recognition between controlled-group members

IRC § 267 is the related-party disallowance and deferral regime. Three of its subsections matter here.

Subsection (a)(1) disallows losses from sales or exchanges of property between related parties as defined in subsection (b). Subsection (a)(2) defers an accrual-method payer’s deduction for an amount payable to a related cash-method payee until the payee includes the amount in income. Subsection (b) lists the categories of related parties — including, at (b)(3), two corporations that are members of the same controlled group as defined by reference to IRC § 267(f).

Subsection (f) is the controlled-group rule. It supplies the controlled-group definition for § 267(b)(3) and, more consequentially, overrides the outright loss disallowance of § 267(a)(1) with a deferral regime for losses on intercompany transactions. Where members of the same controlled group recognize a loss on a sale or exchange of property between them, the loss is not disallowed; it is deferred until the property leaves the group or another triggering event occurs. The deferral mechanic borrows from the consolidated-return matching rules.

Controlled-group definition

The controlled-group definition for § 267(f) draws from IRC § 1563, with modifications. A parent-subsidiary controlled group exists where a common parent owns more than 50% (the § 1563(a)(1) parent-subsidiary threshold of 80% is reduced under § 267(f)) of the voting power or value of one or more subsidiaries. A brother-sister controlled group exists where five or fewer persons own two or more corporations under the § 1563(a)(2) tests — 80% identical voting-power-or-value ownership and more than 50% effective-control ownership. For closely held MSOs with a single common owner (a founder who owns OpCo and the MSO directly, or through trusts that satisfy the attribution rules), the brother-sister test is satisfied without further analysis. Most closely held MSO structures — where a founder owns the operating company and the MSO directly, or through trusts that satisfy the attribution rules — fall within the brother-sister definition.

The intercompany-transaction regulations

Treas. Reg. § 1.267(f)-1 implements the controlled-group deferral rule. The regulation applies the consolidated-return matching and acceleration principles of Treas. Reg. § 1.1502-13 to controlled groups that do not file consolidated returns. The structural result is symmetric tax treatment: the seller’s loss is deferred until the buyer disposes of the property outside the group, at which point the loss is recognized by the seller and matched against the buyer’s gain or loss.

The critical observation for MSO planning is the scope of § 267(f) and Treas. Reg. § 1.267(f)-1: both focus on property transactions — sales, exchanges, transfers of property (including certain intangibles) — and not on ordinary service arrangements for reasonable compensation. The deferral mechanism is designed to prevent acceleration of property losses inside a group whose economic position has not changed. A management-fee payment for services rendered is neither a sale of property nor a loss, and it does not implicate the consolidated-return matching architecture that § 267(f) is built on.

The role of § 267(a)(2) for accrual-to-cash service payments

Where § 267(f) is not the relevant matching rule for a service payment, § 267(a)(2) frequently is. If the operating company is on the accrual method and the MSO is on the cash method, an accrued but unpaid management fee at year-end cannot be deducted by OpCo until the MSO includes the corresponding amount in income. The matching is automatic when the fee is actually paid before year-end — payment satisfies both the deduction trigger for OpCo and the income trigger for MSO. The structural lesson is that fees should be paid, not merely accrued, by the operating company’s year-end if both entities sit inside § 267(b).

V. How the two regimes interact in MSO management-fee timing

§ 267(f) versus § 267(a)(2). Section 267(f) generally is not the issue for reasonable service fees. Section 267(a)(2) may be the issue if the payer is accrual method, the related payee is cash method, and the fee is accrued but unpaid at year-end. In that case, the payer’s deduction is generally deferred until the payee includes the amount in income. Payment before year-end generally solves the matching problem because the payee has income and the payer has the payment record. The clearer framing is: § 267(f) generally does not preclude the deduction for a bona fide service fee, but § 267(a)(2) can affect timing when there is an unpaid related-party accrual.

Timing matrix — accounting-method combinations

Not a disguised property transfer. If the fee embeds a transfer of customer lists, goodwill, know-how, software, IP, or another intangible, that component should be carved out and separately analyzed. A property element hidden inside a service invoice is where § 267(f) risk can re-enter the analysis.

Income recognition is not optional. The deduction position and income position should be symmetrical. If OpCo claims a deduction for a management-fee payment, the MSO should have a corresponding income-recognition position under its accounting method. The article’s conclusion is not that income disappears; it is that § 267(f) does not recharacterize a bona fide service payment into a deferred property-loss transaction.

The technical answer for a properly structured management-fee arrangement is straightforward but layered. Three propositions are doing the work.

First — the 12-month rule applies to the prepayment question. A management-fee prepayment for services rendered within 12 months and not extending past the end of the year following payment is deductible currently under Treas. Reg. § 1.263(a)-4(f). Treas. Reg. § 1.263(a)-4(b)(3)(iii) confirms that service payments are not treated as creating a separate intangible. Capitalization under § 263 is not required.

Second — the all-events and economic-performance tests are satisfied by performance. For an accrual-method operating company, the liability is fixed when the management-services agreement obligates payment for a defined service period; the amount is determinable when the agreed fee or formula is specified; and economic performance occurs as services are rendered. A prepayment that funds a 12-month service period does not, by itself, determine the deduction year. Under § 461(h), an accrual-method payer’s deduction follows economic performance — which, for services, occurs as the services are provided. The 12-month rule of Treas. Reg. § 1.263(a)-4(f) is a § 263 capitalization safe harbor; it does not collapse a 12-month performance period into the year of payment.

Third — § 267(f) does not apply because the transaction is not a property loss. The provision is, by its terms and through Treas. Reg. § 1.267(f)-1, focused on sales, exchanges, and transfers of property between controlled-group members. Reasonable compensation for services actually rendered falls outside that scope. The reasonable-compensation analysis — required under IRC § 162 and the general transfer-pricing standards of IRC § 482 for related-party service charges — remains independently required, but it is a deduction-validity question, not a § 267(f) deferral question.

The combined result is that a properly designed management-fee arrangement — reasonable in amount, supported by an arm’s-length services agreement, paid for services actually rendered within a 12-month window — produces a current deduction at the operating company and current income recognition at the MSO, even when the entities operate on different fiscal years. The fiscal-year mismatch by itself does not trigger § 267(f) deferral; the regime is not aimed at the timing of ordinary service compensation.

VI. Common pitfalls in fiscal-year mismatches

Fiscal-year mismatches between OpCo and MSO produce predictable failure modes. Five recur often enough to warrant a checklist.

Pitfall 1 — Prepayments that stretch past the next year-end

The next-year deadline under Treas. Reg. § 1.263(a)-4(f)(1)(ii) is a hard cap. A November payment by a calendar-year OpCo for services running through the following December clears the 12-month duration limb but tests the deadline limb closely; a payment for services running into the year-after-next fails it. The drafting answer is short. Service periods should align with the payer’s tax year, or with a 12-month window that closes inside the year following payment.

Pitfall 2 — Accrual without payment under § 267(a)(2)

If the MSO is on the cash method and OpCo accrues a year-end management fee without making payment, § 267(a)(2) defers OpCo’s deduction until the MSO includes the corresponding amount in income. The practical fix is payment by OpCo’s year-end. Where cash-management constraints make that difficult, both entities are usually better served by aligning methods (both accrual) or by structuring the engagement so that the fee accrues and is paid before year-end.

Pitfall 3 — Drift between invoice description and services actually rendered

The 12-month rule is conditioned on services realized within the 12-month window. An invoice that recites “management services for fiscal year 2026” but is unsupported by service logs, deliverable schedules, time records, or board minutes describing the work done is vulnerable. The reasonable-compensation defense and the 12-month timing defense both depend on the same contemporaneous service record.

Pitfall 4 — Fee formulas that re-trace as property transfers

A “management fee” that is in substance a transfer of intangible property — an assignment of customer lists, a transfer of know-how packaged as a service charge, an embedded royalty for use of intellectual property — lands inside § 267(f) territory. The label on the invoice is not controlling. Where the underlying arrangement includes property elements, those elements should be carved out, separately priced, and analyzed under the controlled-group property rules — not buried inside the service charge.

Pitfall 5 — Cost-plus formulas that produce excess return

Cost-plus pricing is a common methodology for related-party service charges and is contemplated by the services regulations under Treas. Reg. § 1.482-9. A cost-plus mark-up that is excessive for the services-risk profile of the MSO — particularly where the MSO bears little economic risk — invites a § 482 reallocation. The capitalization question and the matching question disappear if the deduction itself is reduced. Defensible cost-plus pricing rests on a contemporaneous functional analysis and benchmarking.

VII. Documentation for a defensible timing position

The work product that supports the 12-month / § 267(f) position is a subset of the broader MSO documentation file. It should include, at a minimum:

• Written management services agreement — identifying the parties, describing the categories of services, specifying the service period, and stating the fee methodology (fixed, cost-plus, percentage of revenue, or hybrid). The agreement should be executed before services begin and amended in writing as services or pricing evolve.
• Reasonable-compensation file — a contemporaneous functional analysis identifying the services performed, the risks borne by the MSO, the assets used, and a benchmarking analysis supporting the mark-up. For larger MSO programs, an annual update by a qualified transfer-pricing professional is the standard practice.
• Service deliverable record — calendars, dashboards, periodic reports, board materials, time records, or similar work product that evidences the services actually rendered during the fee period. The record need not be elaborate; it needs to exist contemporaneously.
• Invoice and payment trail — invoices issued on the contractual schedule, payment by check or wire on or before the engagement’s due dates, and ledger entries that match. Where prepayment is used to qualify under the 12-month rule, the payment date and the service-period dates should both appear on the invoice.
• Board approval — minutes of OpCo and MSO boards (or sole-shareholder consents in single-owner structures) approving the management services agreement, any amendments, and any material fee adjustments.
• Method-of-accounting documentation — identification of each entity’s overall accounting method, any elections under § 461 (including the recurring-item exception), and the year-end accruals and payments that satisfy § 267(a)(2) matching.

None of these items is exotic. The discipline that distinguishes a defensible MSO from an exposed one is keeping the file current and complete — before any examination is opened, not in response to one.

VIII. Worked example — year-end prepayment for 12-month MSO services

Consider an illustrative fact pattern. The operating company (OpCo) is a calendar-year, accrual-method C-corporation. The MSO is a calendar-year, accrual-method C-corporation owned by the same individual through revocable trusts. The two entities form a brother-sister controlled group under IRC § 1563. The management services agreement covers calendar year 2026 and provides for a $2,400,000 fixed annual fee, payable in advance on December 15, 2025, for services to be rendered January 1 through December 31, 2026.

12-month rule analysis. The benefit period begins January 1, 2026 (first realization) and ends December 31, 2026. The duration is exactly 12 months — within the duration cap of Treas. Reg. § 1.263(a)-4(f)(1)(i). The benefit ends December 31, 2026 — before the close of the taxable year following payment (the 2026 year). The next-year deadline cap is satisfied. Capitalization is not required.

Accrual-method analysis. The all-events test is met — the liability is fixed by the executed services agreement and the amount is determinate. Economic performance under IRC § 461(h)(2)(A)(i) occurs as the services are provided to OpCo, throughout 2026. OpCo’s deduction therefore falls in 2026, not the 2025 year of prepayment. The 12-month rule of Treas. Reg. § 1.263(a)-4(f) is a § 263 capitalization safe harbor only; it does not override the § 461(h) economic-performance requirement. The recurring-item exception of § 1.461-5 cannot close the gap on these facts because it reaches only liabilities economically performed within 8½ months after year-end (on or before September 15, 2026), not services rendered through December 31, 2026.

§ 267(a)(2) analysis. Because both entities are on the accrual method, § 267(a)(2) does not defer OpCo’s deduction past MSO’s income inclusion. Even if the MSO were on the cash method, payment in advance on December 15, 2025 satisfies the matching requirement — the MSO recognizes the cash receipt in 2025, contemporaneously with OpCo’s claimed deduction.

§ 267(f) analysis. The transaction is the payment of reasonable compensation for services actually rendered. It is not a sale, exchange, or transfer of property. Treas. Reg. § 1.267(f)-1 is not implicated. No deferral applies.

Reasonable-compensation analysis. Separately, OpCo and the MSO maintain a transfer-pricing file under § 482 supporting the $2,400,000 fee as the arm’s-length charge for the bundle of administrative, advisory, and operational services described in the services agreement. The file includes a functional analysis, a comparables search, and a mark-up benchmarking analysis. The reasonable-compensation defense is the substantive backbone of the deduction.

Worked example B — cash-method OpCo and cash-method MSO

Same fact pattern as Example A, except both entities are on the cash method of accounting.

• 12-month rule analysis. Identical to Example A — duration and next-year deadline both met. Capitalization not required.
• § 267(a)(2) analysis. Cash-method payer’s deduction follows payment. Cash-method payee’s income follows receipt. Matching is automatic on the date the $2.4M is wired (December 15, 2025). OpCo deducts in 2025; MSO recognizes income in 2025.
• § 461 analysis. Cash-method taxpayers are not subject to the all-events / economic-performance regime. Deduction follows payment.
• § 267(f) analysis. Not implicated. Service-fee transaction, not a property loss.
• Reasonable-compensation analysis. Identical to Example A — § 482 file required regardless of accounting method.

The cash-method case is the cleanest factual pattern for MSO fee timing — payment is the trigger for both deduction and income recognition, and the related-party matching rule resolves automatically.

Worked example C — accrual-method OpCo and cash-method MSO (the § 267(a)(2) trap)

Where OpCo is on the accrual method but the MSO is on the cash method, § 267(a)(2) becomes the central timing question. If OpCo accrues the $2.4M management fee at year-end but does not actually pay before December 31, 2025, the deduction is deferred until 2026 (when the cash-method MSO recognizes the receipt as income).

Practical answer: Pay the fee on or before OpCo’s year-end. Payment satisfies the § 267(a)(2) matching rule because the cash-method MSO recognizes the receipt contemporaneously with OpCo’s deduction. An accrued-but-unpaid year-end fee is a deferral, not a denial — but it is rarely the intended outcome.

The accounting-method matrix earlier in this brief catalogs the four combinations and their timing implications.

The role of the FMV report — what it supports, what it does not

A qualified independent FMV study under § 482 supports the amount charged in the management fee. It establishes that the fee is arm’s length under the services regulations of Treas. Reg. § 1.482-9. That is the § 482 deliverable.

What the FMV report does not do: it does not, by itself, determine deduction timing. Timing is governed by § 461 economic performance, § 267(a)(2) related-party matching, and the 12-month rule under Treas. Reg. § 1.263(a)-4(f). A perfectly defensible FMV file still requires independent satisfaction of the timing regime applicable to the payer’s accounting method.

The institutional file therefore contains BOTH the § 482 substantiation work (the FMV report, functional analysis, benchmarking, cost-plus support) AND the timing documentation (invoices showing payment dates, service-period dates, board approvals of fee methodology, evidence of services rendered within the qualifying window).

IX. Frequently asked questions

Does the 12-month rule apply to management-fee prepayments between related parties?

Yes. Treas. Reg. § 1.263(a)-4(f) applies on its terms to any taxpayer-paid amount that creates or facilitates the creation of a right or benefit not extending beyond the 12-month duration cap or the next-year deadline. There is no related-party exclusion in the rule itself. A management-fee prepayment from an operating company to a controlled-group MSO for services rendered within the 12-month window qualifies, provided the prepayment is bona fide reasonable compensation for services and not a disguised property transfer.

Does IRC § 267(f) defer a management-fee deduction within a controlled group?

No. IRC § 267(f) and the intercompany-transaction regulations under Treas. Reg. § 1.267(f)-1 are designed for sales, exchanges, and transfers of property between controlled-group members. They apply consolidated-return matching principles to property losses, not to reasonable compensation for services. A management fee paid for services actually rendered is not within the regulation’s scope.

What if OpCo and MSO use different fiscal years?

A fiscal-year mismatch does not, by itself, trigger § 267(f) for a service payment. The 12-month rule is measured against the payer’s taxable year, and the deduction qualifies if the duration cap and the next-year deadline are met on the payer’s side. The income recognition on the payee side follows the payee’s method of accounting. Matching under § 267(a)(2) becomes important where the payee is on the cash method — OpCo’s deduction is then deferred until the MSO includes the amount in income, which usually means until OpCo actually pays.

What is the difference between § 267(a)(2) and § 267(f)?

Section 267(a)(2) is the accrual-to-cash matching rule for related-party deductions: it defers an accrual payer’s deduction for an amount owed to a related cash-method payee until the payee includes the amount in income. Section 267(f) is the controlled-group property rule: it defers a loss on a sale or exchange of property between members of a controlled group until a later triggering event. Both sit within the broader § 267 architecture, but they address different transactions and operate on different mechanics.

What is the “all-events test” and how does it interact with the 12-month rule?

The all-events test under Treas. Reg. § 1.461-1(a)(2) requires that, for an accrual-method taxpayer, a liability be fixed and determinable before it can be accrued; IRC § 461(h) requires that economic performance also occur. The 12-month rule is a separate safe harbor that, when satisfied, permits current deduction of a prepayment even though the benefit period extends into the next year. Both regimes should be analyzed together: a prepayment that clears the 12-month rule still has to satisfy the underlying accrual-method requirements for the deduction year.

What documentation supports a 12-month-rule deduction for a management fee?

The minimum file is a written management services agreement that identifies the parties, defines the services, sets the service period, and states the fee methodology; invoices that show the payment date and the service-period dates; a service-deliverable record (calendars, reports, time logs, board materials) for the period covered by the fee; payment evidence; and a reasonable-compensation file supporting the fee amount. Where the engagement spans years or the fee is calibrated annually, the file should be updated each year.

Can a management fee be recharacterized as a property transfer under § 267(f)?

Substance prevails over form. A fee labeled as compensation for services but that, in substance, transfers intangible property — intellectual property, customer relationships, goodwill — can be re-traced as a property transfer, with the property elements analyzed under the controlled-group rules. The risk is mitigated by drafting services agreements that describe services as services, by carving out and separately pricing any property elements, and by maintaining a contemporaneous service-deliverable record that supports the services characterization.

How does the recurring-item exception interact with management-fee timing?

The recurring-item exception under IRC § 461(h)(3) and Treas. Reg. § 1.461-5 permits certain recurring liabilities to be accrued in the year incurred even though economic performance occurs after year-end, provided economic performance occurs within the shorter of 8½ months or a reasonable period after year-end and the item is recurring in character. For a recurring annual management fee, the exception can support accrual of the year-end portion of the liability where the services are performed shortly after year-end. The 12-month rule and the recurring-item exception are independent doctrines — either may support the deduction; both should be analyzed.

Platform-memo alignment

Guardian’s platform materials and third-party MSO memorandum support the same general framework: a management fee is not disallowed merely because the MSO and operating company are related. The analysis depends on whether the MSO is a real trade or business, whether services are actually performed, whether the fee is reasonable, and whether the arrangement resembles an arm’s-length service relationship.

The Handler memorandum emphasizes that MSO scrutiny may arise because of common ownership, but also points to the importance of legally distinct entities, professional management activity, profit motive, employees and outside providers, and an arm’s-length relationship between the MSO and the operating companies it serves. The Wells Hall / Nelson Mullins platform-partner memorandum likewise frames the management fee as a § 162 and § 482 issue: management fees should cover the cost of services provided by the MSO, including compensation, payroll taxes, fringe benefits, and deferred compensation, and should be determined under an arm’s-length standard rather than exceeding what would be charged by an unrelated MSO.

GTC’s role

Guardian Tax Consultants® does not determine final tax treatment, issue legal opinions, or replace the client’s CPA or legal counsel. GTC’s role is to help the advisory team document the MSA scope, the service deliverables, the § 162 and § 482 fee support, the prepayment terms relative to the 12-month rule, and the § 461 economic-performance and § 267(a)(2) matching positions — so the client’s tax advisors can evaluate timing positions with a clear file.

X. Disclosures

This brief is published by Guardian Tax Consultants® for general informational and educational purposes only. It is not tax, legal, accounting, or investment advice, and does not establish an advisor-client or attorney-client relationship. The IRC sections, Treasury Regulations, and authorities cited reflect general legal framework as of the date of publication; their application to any particular taxpayer is fact-specific and depends on circumstances not addressed here. Tax law changes; positions described here may be affected by subsequent legislation, regulations, rulings, or case law.