🛡️ Senior Advisor
2026-04-15 22:00
Good morning. I asked for this meeting because I've been reviewing your partnership's recent state tax footprint, and I think we're leaving real money on the table — potentially six figures a year depending on your income allocation.
Here's the issue: your partnership is generating income in seven states, but most of your partners live elsewhere. Under the old rules, those partners were writing personal checks for state income tax in states where they don't even live, and they couldn't deduct those payments on their federal returns because of the $10,000 SALT cap. That's a permanent loss of deduction. But most of these states now offer a partnership-level tax election — what we call PTET — that flips the structure entirely. The partnership pays the state tax as a partnership expense, the partners get a credit on their resident returns, and suddenly that same tax payment becomes fully deductible at the federal level because it's a partnership business expense, not a personal itemized deduction.
I ran a rough calculation based on last year's K-1s, and if we had elected into PTET in the four largest states where you're active, your partners collectively would have saved about $140,000 in federal tax. That's real cash they kept instead of sending to the IRS, just by changing who writes the check to the state. Most of these elections have to be made by March 15th for this tax year, so we need to move quickly if you want to capture the benefit for 2025.
Does this structure make sense so far, or do you want me to walk through a specific state example to show how the mechanics work?
🏢 Client
2026-04-15 22:00
Wait — you're telling me we could have saved a hundred and forty thousand dollars last year and nobody mentioned this until now? That's frustrating. I need to understand why this wasn't on the table earlier before we talk about what to do this year.
And I'm skeptical of the March 15th deadline creating urgency here. We've got operating agreements, we've got quarterly distributions already set, we've got K-1 prep that's halfway done. If we're changing who pays the tax, doesn't that ripple through everything? What's the actual cost to implement this — not just filing fees, but the real cost in terms of accounting complexity, distribution mechanics, and your time to get it right?
Walk me through one state example like you said, but I want to know the catch. This sounds like it works too cleanly, and in my experience when something sounds that good there's either a timing trap or a compliance burden we're not seeing yet.
⚡ Junior Advisor
2026-04-15 22:00
I think the senior's math is right, but I want to flag the implementation risk you're sensing — this isn't a one-time election with zero downstream effect. When the partnership pays the state tax under PTET, that's a partnership expense that reduces your inside basis in the partnership and flows through as a reduction to each partner's distributive share of income. That means if you were planning to distribute $500,000 to the partners this year based on projected net income, and we now have $80,000 of PTET expense hitting the books, either the distributions drop or you're distributing in excess of income, which has its own tax consequences at the partner level. The mechanism works, but it absolutely affects distribution planning and you need to model that with your CFO before the election deadline.
Here's the state example using California, since that's probably your biggest exposure: assume the partnership has $1 million of California-source income and you have five equal partners, none of whom live in California. Under the old structure, each partner reports $200,000 of California income on a nonresident return and pays California tax at 9.3%, so $18,600 per partner, $93,000 total. They pay that personally, and because of the SALT cap, they get maybe $2,000 of federal benefit if they have cap room left, but most high earners are already capped out, so it's a total loss of deduction — $93,000 out the door with no federal offset. Under PTET, the partnership makes the election, pays that same $93,000 as a partnership expense, and each partner's K-1 now shows $200,000 minus their $18,600 share of the PTET expense, so $181,400 of net income. California gives them a credit for the tax the partnership paid on their behalf, so they owe California nothing additionally, and on the federal return, that $18,600 PTET expense is already baked into their distributive share — it reduced their federal taxable income automatically. At a 37% federal rate, that's a $6,882 federal tax savings per partner, $34,410 total, just from recharacterizing the same payment.
The catch you're looking for is this: about half the states with PTET require an irrevocable election by March 15th, and if you get the estimated payment timing wrong, some states disallow the deduction entirely or impose penalties that wipe out the benefit. California's not one of the problem states, but if you're also operating in New York or Massachusetts, the payment schedules are unforgiving and your accounting team needs to be on top of quarterly estimates starting immediately. Is your concern more about the one-time implementation lift this year, or the ongoing compliance cost of managing seven states' worth of PTET filing requirements every quarter going forward?
🏢 Client
2026-04-15 22:00
I'm stuck on two things. First, you're saying this is a federal tax arbitrage that's just sitting there for the taking, which makes me wonder why every partnership in the country isn't doing this — what's the adoption rate, and if it's low, what are sophisticated groups seeing that we're not? Second, you mentioned half the states require irrevocable elections — I need to know exactly which of our seven states lock us in and which ones let us test this for a year and bail if it's a nightmare.
On the cost side, you gave me a federal savings number but you didn't give me an implementation cost. What's your bill going to look like to set this up across seven states, and what's the annual recurring cost once it's in place? I'm not spending forty thousand dollars of your time to save thirty thousand dollars of tax. And when you say the accounting team needs to be on top of quarterly estimates, does that mean we're hiring someone, or does that mean our existing controller can handle this with the systems we have?
Walk me through the seven states we're in — which ones have PTET, which ones are irrevocable, and which ones are the low-hanging fruit where we get ninety percent of the benefit with twenty percent of the hassle.
⚡ Junior Advisor
2026-04-15 22:01
I need to push back on something my colleague implied — the $140,000 savings figure assumes we elect PTET in all available states and that every state's credit mechanism works perfectly, which isn't true. Some of your seven states don't even offer PTET yet, and in at least two states where it exists, the credit your partners receive on their resident returns is partial, not full, which means you're prepaying tax at the partnership level and your partners are still writing a second check to their home state. That's not arbitrage — that's just moving money around and hoping the timing works in your favor. Before we talk about which states are irrevocable, we need to know which states actually deliver a net benefit, because an irrevocable election in a state with a broken credit system is worse than doing nothing.
Here's the breakdown of your seven states: California, New York, Illinois, and Texas. Texas has no income tax, so PTET is irrelevant there — that's one down. California, New York, and Illinois all have PTET regimes, but New York's is a disaster from a compliance standpoint because they require quarterly estimates based on prior-year income and the penalty for underpayment is harsh enough that we'd need to overfund by at least 10% to stay safe, which means your cash is sitting with New York earning nothing while you wait for a refund you might not see for eighteen months. Illinois is cleaner — they allow annual elections, the credit is dollar-for-dollar, and the filing requirements are manageable. California is somewhere in between — the election is annual and revocable, but the estimated payment schedule is aggressive and if your income spikes mid-year, you're scrambling to true up by December 15th or you lose the deduction for that year entirely.
You asked what percentage of partnerships are doing this — adoption is maybe 30% among partnerships with sophisticated advisors, but it's lower in partnerships with multi-state operations because the complexity scales badly. The groups that aren't doing it either have partners in low-tax or no-tax states where the federal benefit is too small to justify the overhead, or they've done the math and realized that in states with partial credits or aggressive penalty regimes, the juice isn't worth the squeeze. Our implementation cost for a seven-state analysis and first-year election setup is probably in the $25,000 to $35,000 range depending on how much state-specific modeling we need to do, and ongoing annual compliance adds maybe $12,000 to $15,000 to your state tax prep bill because we're now filing partnership-level returns and managing quarterly estimates in three or four states instead of just passing through information to partners. Does that cost structure still make sense if the actual federal savings is closer to $80,000 than $140,000, and half of that is locked up in New York where the credit might not clear for two years?
🛡️ Senior Advisor
2026-04-15 22:01
I'm going to disagree with my colleague on the New York characterization — yes, New York's estimated payment requirements are rigid, but calling it "a disaster" overstates the risk if we manage it correctly. The penalty for underpayment in New York is 9% annualized, which sounds scary until you compare it to the 37% federal benefit we're capturing. Even if we get the estimate wrong and pay a penalty on a $20,000 shortfall, that's a $1,800 penalty against a $25,000 federal savings on that same income. The math still works. The refund timing issue is real — New York is slow — but that's a cash flow problem, not a structural flaw in the election. If your partnership has the liquidity to handle payments sitting with New York for twelve to eighteen months, the economics are still strongly in your favor.
Here's where I agree with him: the $140,000 figure I gave you assumes best-case scenarios across all states, and that was sloppy on my part. Let me restate it cleanly. California and Illinois are both strong candidates where the benefit is real and the compliance is manageable — together, those two states probably represent $95,000 of the $140,000 in federal savings. New York adds another $30,000 of benefit but with the cash flow and penalty risk my colleague described, so that's a judgment call based on your liquidity and risk tolerance. The other states in your footprint either don't have PTET or the income allocation is too small to move the needle. So the honest answer is you're looking at $95,000 of relatively clean savings, with an additional $30,000 available in New York if you're willing to manage the quarterly estimate risk and accept slow refunds.
On the implementation cost, $25,000 to $35,000 for first-year setup is the right range, and the $12,000 to $15,000 ongoing annual cost is realistic. That means year one is about a 2-to-1 return on fees, and every year after that is more like 6-to-1. The question is whether your controller can handle quarterly estimates in three states without additional headcount — my experience is that if your controller is already managing multi-state payroll tax or sales tax compliance, adding PTET estimates is not a huge lift, but if this is their first exposure to multi-state quarterly filings, you're going to need either training or outside help for at least the first year.
Given what we now know about the real savings and the real costs, do you want us to model California and Illinois as a definite yes, and then separately model New York as a maybe so you can see the cash flow impact and decide whether that third state is worth the hassle?
⚡ Junior Advisor
2026-04-15 22:01
I'm going to disagree with the senior on the penalty math in New York — the 9% underpayment penalty isn't the only cost we need to worry about. New York's PTET regime under Article 24-A requires the partnership to make quarterly estimated payments based on 90% of the current year's liability or 100% of the prior year's liability to avoid penalties, and if your partnership's New York-source income is volatile year-to-year, you can't safely use the prior-year safe harbor. That means we're estimating current-year liability in real time, and if we undershoot because a deal closes in Q4 that we didn't anticipate in Q1, we're not just paying 9% on the shortfall — we've also potentially disqualified the entire deduction for that year under New York's strict compliance requirements. The statute says the tax must be paid when due to be deductible, and the Department of Tax and Finance has been aggressive in audits about disallowing deductions where estimated payments were materially deficient. That's not a cash flow problem — that's a structural risk that the entire New York election fails if we get the estimates wrong.
Here's what I'd recommend instead of modeling New York as a maybe: let's elect California and Illinois for 2025 where the rules are clear and the savings are certain, and let's punt New York to 2026 after we've seen a full year of how PTET affects your distribution planning and whether your controller can handle the quarterly cadence without errors. You'll still capture $95,000 of the $140,000 benefit this year, and you're not taking execution risk in a state where one mistake can blow up the entire election. If we try to do all three states in year one and something goes wrong with the New York estimates because your team is still learning the system, we've spent $35,000 in fees and created an audit exposure that could cost more than the tax we saved.
Does that phased approach make sense, or are you determined to capture the full $140,000 this year even if it means higher implementation risk?
🛡️ Senior Advisor
2026-04-15 22:02
I need to push back on characterizing New York's enforcement as aggressive enough to disqualify the entire deduction over an estimate shortfall — that's not what the statute says and it's not what we've seen in practice. Article 24-A requires the tax to be "paid" to be deductible, but New York treats the annual reconciliation payment as satisfying that requirement as long as you made a good-faith effort on the estimates. The Department has been strict about partnerships that made zero estimated payments and tried to true up entirely at year-end, but I haven't seen a single case where they disallowed a deduction because a partnership underestimated by 15% or 20% in a year where income spiked unexpectedly. They assess the penalty, you pay it, and the deduction stands. If you're aware of guidance or a specific audit where New York disqualified the deduction over an estimate miss, I'd like to see it, because that would change my advice — but I think you're overstating the risk based on the statutory language without actual enforcement data.
That said, I agree with you that a phased approach is the right answer for a different reason: this is the client's first year implementing PTET, and trying to manage compliance in three states simultaneously when the internal team has no experience with these filings is asking for mistakes. It's not that New York is too risky on the merits — it's that execution risk is real when you're learning a new system, and we should derisk year one by limiting the scope. California and Illinois get you to $95,000 in savings with compliance regimes that are more forgiving of small errors, and that's a clean win. If the controller handles that smoothly and the partnership is comfortable with the distribution impact, we add New York in 2026 and pick up the additional $30,000 then.
So here's what I'm recommending: we move forward with California and Illinois elections for 2025, which need to be made by March 15th. We model the estimated payment schedule for both states today so your controller knows exactly what's going out the door and when, and we build that into your Q1 cash flow forecast. We punt New York to next year, not because the election is structurally flawed, but because we're prioritizing clean execution over maximum savings in year one. Does that give you enough comfort to move forward, or do you still want to see the New York analysis before you decide?
🏢 Client
2026-04-15 22:02
Hold on — you two are giving me completely opposite reads on whether New York disqualifies the deduction if we miss the estimates, and I can't make a decision when my advisors aren't aligned on the basic facts. One of you is saying it's a real risk based on the statute, the other is saying you've never seen it happen in practice. Which is it? Because if there's actual enforcement risk that kills the deduction, I don't care how good the math looks — I'm not doing it. But if this is theoretical risk that nobody's actually seen materialize, then I'm annoyed we're even talking about it.
Here's what I need before we go any further: stop debating each other and give me a single recommendation you both agree on. If you can't agree on New York, fine — we'll do California and Illinois like you're both suggesting and we'll revisit New York next year when we have real data on how this works. But I need to understand the California and Illinois elections clearly enough that I can explain them to my CFO in one paragraph, because she's the one who's going to have to execute on the quarterly estimates and she's going to push back if this sounds complicated.
So walk me through California and Illinois specifically — when do the elections need to be made, when do the quarterly payments go out, and what happens if we miss a payment or get the estimate wrong in one of those two states? I want to know the failure modes before I commit.
⚡ Junior Advisor
2026-04-15 22:02
I'm going to be direct with you — my colleague and I disagree on the New York risk profile, but we agree on the recommendation, so let's focus there. California and Illinois for 2025, New York revisited in 2026 when you have a year of operational experience. Done.
Here's California in one paragraph for your CFO: the election is made annually by March 15th on Form 3893, it's revocable, and the partnership makes quarterly estimated payments on April 15th, June 15th, September 15th, and January 15th based on 90% of the current year's estimated tax or 100% of the prior year's tax. If you underpay, California assesses interest at about 5% annually on the shortfall, but the deduction isn't disallowed — you just pay interest and true up when you file the annual return. The failure mode is purely financial: you either overpay and wait for a refund, or you underpay and pay interest. There's no compliance trap that kills the election.
Illinois is even cleaner: the election is made by the original due date of the partnership return (March 15th for calendar-year partnerships), and Illinois requires only one estimated payment due on the 15th day of the sixth month of the tax year — so June 15th for a calendar-year partnership. If you miss that payment or underpay, Illinois charges interest at 6% annually, but again, the deduction stands and you true up at year-end. The compliance burden is materially lower than California because you're managing one payment instead of four, and the estimated payment is based on the prior year's liability, so there's no mid-year guesswork. Your controller makes one wire to Illinois in June based on last year's numbers, and that's 90% of the work.
Does that level of simplicity on Illinois make you comfortable moving forward there immediately, or do you want us to model what happens if your Illinois-source income doubles this year and we end up with a big true-up payment in April 2026?
🛡️ Senior Advisor
2026-04-15 22:03
I need to correct something my colleague just said about California that could create a real problem for your CFO if she relies on it. California's PTET election under Revenue and Taxation Code
Section 19900 is **not** revocable in the way that term usually means. You can choose not to make the election again the following year, but once you make it for 2025, you're locked in for 2025 — you can't undo it mid-year if your income comes in lower than expected or if the distribution impact turns out to be worse than we modeled. That's different from "revocable," and I want to make sure we're clear on that because if your partnership has a terrible year and ends up with a loss, you've still made the election and you're stuck with whatever compliance burden comes with it even though there's no tax benefit. It's an annual election, not an irrevocable multi-year commitment, but it's also not something you can back out of once the March 15th deadline passes.
Here's where I do agree with him: the failure modes in both California and Illinois are purely financial, not structural. You pay interest if you underpay estimates, but the deduction stands. That's the critical point your CFO needs to understand — this isn't like a late S-election where you miss a deadline and the entire tax structure collapses. If she misses a quarterly payment in California or underestimates the June payment in Illinois, we're talking about a few thousand dollars of interest on a six-figure tax savings. It's a rounding error compared to the benefit.
What I want to focus on now is the distribution mechanics, because that's where this gets real for your CFO and it's the piece we haven't fully worked through. When the partnership pays $95,000 of PTET expense across California and Illinois, that's $95,000 less cash available for distribution unless you're funding distributions from other sources. If your operating agreement says you distribute 90% of net income quarterly and your partners are expecting that cash, we need to model whether the PTET expense causes a distribution shortfall or whether you're comfortable telling partners their Q2 distribution is lighter because we're prepaying their state tax at the entity level. Have you thought through how you're going to message that to your partners, or do you need us to draft language for the Q1 partnership update that explains what's happening and why?
🏢 Client
2026-04-15 22:03
Okay, we're doing California and Illinois for 2025 — I'll have our CFO model the quarterly payment schedule against our distribution forecast so we know if we need to adjust partner expectations in Q2. The risk I'm taking is that we've locked ourselves into compliance in two states for the full year even if our income tanks, and I'm eating a few thousand in interest if we miss an estimate, but that's manageable compared to leaving ninety-five thousand on the table. I'll set up time with her this week to walk through the mechanics and make sure she's comfortable with the March 15th election deadline.
🔍 IRS Examiner
2026-04-15 22:03
# IRS EXAMINATION MEMORANDUM
## ISSUE
Whether the partnership's payment of state pass-through entity taxes under California Revenue and Taxation Code
Section 19900 and comparable Illinois provisions constitutes deductible business expense under IRC
Section 162, or whether the payments should be recharacterized as nondeductible partner-level taxes under the assignment of income doctrine and the substance-over-form principles established in
Revenue Ruling 75-250.
## GOVERNMENT'S POSITION
The Service's position is that the PTET payments, while nominally made by the partnership, represent discharge of the individual partners' state income tax obligations and should be recharacterized as constructive distributions followed by nondeductible personal tax payments under IRC
Section 164(b)(6). The partnership is acting as a paying agent for its partners rather than incurring a genuine business expense. This structure violates the assignment of income doctrine because the partnership is not the taxpayer with respect to the income that generated the state tax liability — the partners are — and state law confirms that the PTET election merely changes the remittance mechanism while preserving partner-level liability for the underlying tax obligation. The economic substance of the transaction is that partners are prepaying their personal state income tax through the partnership rather than directly, and the federal deduction should be disallowed accordingly.
## PROPOSED ADJUSTMENT
Disallow the partnership's claimed IRC
Section 162 deduction for $95,000 of PTET payments made to California and Illinois, treating the payments instead as nondeductible under IRC
Section 164(b)(6). Reallocate the disallowed deduction proportionately to each partner's distributive share, increasing each partner's federal taxable income by their allocable portion of the $95,000. This adjustment increases total federal tax liability across all partners by approximately $35,150 (assuming 37% marginal rate). Additionally, assess accuracy-related penalties under IRC
Section 6662(a) at 20% of any underpayment exceeding $5,000 per partner, on grounds that the position lacks substantial authority given that Notice 2020-75 merely confirmed state PTET elections do not violate the SALT cap but did not affirmatively bless the deduction as ordinary and necessary business expense.
## BEST SUPPORTING AUTHORITY
**IRC
Section 164(b)(6)**: Disallows deduction for "taxes imposed on shareholders, partners, or beneficiaries of pass-through entities as such on their distributive or pro rata share" — the statute's plain language contemplates that the identity of the taxpayer, not the remittance mechanism, controls deductibility. **
Treasury Regulation Section 1.164-1(a)**: Limits deductibility of state taxes to those "imposed on the taxpayer" — here the partners remain the constitutional taxpayers under state law despite elective entity-level payment. **
Revenue Ruling 75-250**: Established that payments made by a partnership on behalf of partners constitute constructive distributions to the extent they discharge personal obligations of the partners, and the form of payment does not control characterization where substance is partner-level liability satisfaction. Courts have consistently held in the withholding context that entity-level remittance does not convert personal tax obligations into business expenses merely because the entity writes the check.
## WEAKNESSES
Notice 2020-75 explicitly states that entity-level PTET payments are not subject to the IRC
Section 164(b)(6) limitation, which substantially undermines any recharacterization argument absent clear guidance distinguishing elective PTET from mandatory withholding structures.
Sign in to join the discussion.
Sign in or Create account