Cincyblogs.com
Showing posts with label marketplace. Show all posts
Showing posts with label marketplace. Show all posts

Monday, June 22, 2020

It’s A Cliff, Not A Slope


It is one of my least favorite areas of individual tax practice.

We are talking about health insurance. More specifically, health insurance purchased through the exchanges, coupled with advance payment of the premiums.

Why?

Because there is a nasty tax trap in there, and I saw the trap again the other day. It caught a client who gets by, but who is hardly in a position to service heavy tax debt.

Let’s set it up.

You can purchase health insurance in the private market or from government-sponsored marketplaces – also called exchanges. The exchanges were created under the Affordable Care Act, more colloquially known as Obamacare.

If you purchase health insurance through the exchange and your income is below a certain level, you can receive government assistance in paying the insurance premiums. Make very little income, for example, and it is possible that the insurance will be free to you. Make a little more and you will be expected to contribute to your own upkeep. Make too much and you are eliminated from the discussion altogether.

The trap has to do with the dividing line of “too much.”

Let’s look at the Abrego case.

Mr and Mrs Abrego lived in California. For 2015 he was a driver for disabled individuals, and he also prepared a few tax returns (between 20 and 30) every year. Mrs Abrego was a housekeeper.

They enrolled in the California exchange. They also did the following:

(1)  They provided an estimate of their income for 2015. Remember, the final subsidy is ultimately based on their 2015 income, which will not be known until 2016. While it is possible that someone would purchase health insurance, pay for it out-of-pocket and eventually get reimbursed by the IRS when filing their 2015 tax return in 2016, it is far more likely that someone will estimate their 2015 income to then estimate their subsidy. One would use the estimated subsidy to offset the very real monthly premiums. Makes sense, as long as all those estimated numbers come in as expected.

(2)  They picked a policy. The monthly premiums were $1,029.

(3)  The exchange cranked their expected 2015 numbers and determined that they could personally pay $108 per month.

(4)  The difference - $ 1,029 minus $108 = $921– was their monthly subsidy.

The Abregos kept this up for 10 months. Their total 2015 subsidy was $9,210 ($921 times 12).

Since the Abregos received a subsidy, they had to file a tax return. One reason is to compare actual numbers to the estimated numbers. If they guessed low on income, they would have to pay back some of the subsidy. If they guessed high, the government would owe them for underestimating the subsidy.

The Abregos filed their 2015 return.

They reported $63,332 of household income.

How much subsidy should they have received?

There is the rub.

The subsidy changes as income climbs. The subsidy gets to zero when one hits 400% of the poverty line.

What was the poverty line in California for 2015?

$15,730 for a married couple.

Four times the poverty line was $62,920.

They reported $63,332.

Which is more than $62,920.

By $412.

They have to pay back the subsidy.

How much do they have to pay back?

All of it - $9,210.

Folks, the tax rate on that last $412 is astronomical.

It is frustrating to see this fact pattern play out. The odds of a heads-up from the client while someone can still do something are – by the way – zero. That leaves retroactive tax planning, whose success rate is also pretty close to zero.

Our client left no room to maneuver. Why did her income go up? Because she sold something. Why did she not call CTG galactic command before selling – you know: just in case? What would we have done? Probably advised her to NOT SELL in the same year she is receiving a government subsidy.

How did it turn out for the Abregos?

They should have been toast, except for one thing.

Remember that he prepared tax returns. He did that on the side, meaning that he had a gig going. He was self-employed.

He got to claim business deductions.

And he had forgotten one.

How much was it?

$662.

It got their income below the magic $69,920 level.

They were on the sliding scale to pay back some of that subsidy. Some - not all.

It was a rare victory in this area.

Our case for the homegamers was Abrego v Commissioner.

Friday, August 7, 2015

TomatoCare And The Supreme Court



Let’s play make believe.

Late on a dark and stormy Saturday night, the Congressional Spartans - urged on by Poppa John's and the National Tomato Growers Association – passed a sweeping vegetable care bill by a vote of 220-215.

The bill went to the Senate, where its fate was sadly in doubt. The fearless majority leader Harry Leonidas negotiated agreements with several recalcitrant senators, including the slabjacking of New Orleans, an ongoing automatic bid for the Nebraska Cornhuskers to the college Bowl Championship Series and the relocation of Vermont to somewhere between North Carolina and Florida. After passage, the bill was signed by the president while on the back nine at Porcupine Creek in Rancho Mirage, California.

As a consequence of this visionary act, Americans now had access to affordable tomatoes, thanks to market reforms and consumer protections put into place by this law. The law had also begun to curb rising tomato prices across the system by cracking down on waste and fraud and creating powerful incentives for grocery chains to spend their resources more wisely. Americans were now protected from some of the worst industry abuses like out-of-season shortages that could cut off tomato supply when people needed them the most.


California, Vermont and Massachusetts established state exchanges to provide tomato subsidies to individuals whose household income levels were below the threshold triggering the maximum federal individual income tax rate (presently 39.6 percent). The remaining states had refused to establish their own exchanges, prompting the federal government to intervene. The Tax Exempt Organization Division at the IRS, recognized for their expertise in technology integration, data development and retention, was tasked to oversee the installation of federal exchanges in those backwater baronies. IRS Commissioner Koskinen stated that this would require a reallocation of existing budgetary funding and – as a consequence - the IRS would not be collecting taxes from anyone in the Central time zone during the forthcoming year.

The 54 states that did not establish their own exchanges filed a lawsuit (Bling v Ne’er-Do-Well) challenging a key part of the TomatoCare law, which read as follows:

The premium assistance amount determined under this subsection with respect to any vegetable coverage amount is the amount equal to the lesser of the greater…”

These benighted states pointed out that, botanically, a tomato was a fruit. A fruit was defined as a seed-bearing vessel developed from the ovary of a flowering plant. A vegetable, on the other hand, was any other part of the plant. By this standard, seedy growth such as bananas, apples and, yes, tomatoes, were all fruits.

There was great fear upon the land when the Supreme Court decided to hear the case.

Depending upon how the Supreme Court decided, there might be no tomato subsidies because tomatoes were not vegetables, a result clearly, unambiguously and irretrievably-beyond-dispute not the intent of Congress on that dark, hot, stormy, wintery Saturday night as they debated the merits of quitclaiming California to Mexico.

The case began under great susurration. The plaintiffs (the 54 moon landings) read into evidence definitions of the words “fruit” and “vegetables” from Webster’s Dictionary, Worcester’s Dictionary, the Imperial Dictionary and Snoop Dogg’s album “Paid tha Cost to Be da Bo$$.”

The Court acknowledged that the words “fruit” and “vegetable” were indeed words in the English language. As such, the Court was bound to take judicial notice, as it did in regard to all words in its own tongue, especially “oocephalus” and “bumfuzzle.” The Court agreed that a dictionary could be admitted in Court only as an aid to the memory and understanding of the Court and not as evidence of the meaning of words.

The Court went on:

Botanically speaking, tomatoes are the fruit of the vine. But in the common language of the 202 area code, all these are vegetables which are grown in kitchen gardens and, whether eaten cooked, steamed, boiled, roasted or raw, are like potatoes, carrots, turnips and cauliflower, usually served at dinner with, or after, the soup, fish, fowl or beef which constitutes the principal part of the repast.”

The Court decided:

            But it is not served, like fruits generally, as a dessert.”

With that, the Court decided that tomatoes were vegetables and not fruit. The challenge to TomatoCare was courageously halted, and the liberal wing of the Court – in a show of their fierce independence and tenacity of intellect – posed for a selfie and went to Georgetown to get matching tattoos.

Thus ends our make believe.

There was no TomatoCare law, of course, but there WAS an actual Supreme Court decision concerning tomatoes. Oh, you didn’t know?

Back in the 1880s the Port of New York was taxing tomatoes as vegetables. The Nix family, which imported tons of tomatoes, sued. They thought they had the law – and common sense – on their side. After all, science said that tomatoes were fruit. The only party who disagreed was the Collector of the Port of New York, hardly an objective juror.

The tax law in question was The Tariff of 1883, a historical curiosity now long gone, and the case was Nix v Hedden. 

And that is how we came to think of tomatoes as vegetables.

Brilliant legal minds, right?