Hacker News new | past | comments | ask | show | jobs | submit login

This is a bad take in my opinion. First of all, we already have W-4 forms today, where you report your intentions to the government, vis-à-vis married, single, etc — they just need to be updated so that you send it in to the government (a joint one for couples) when you make a change (birth, marriage, divorce, deaths). Most people are not eligible for child care deductions, nor healthcare deductions, other than the ones that come through an employer program which can already be reported to the government without your interaction. Education tax credits are based on 1098(?) forms the government should already have their copy of. Also most people don’t give enough charity to bother with those either.

You could log into a website occasionally and upload charity receipts or click through a wizard to apply for a deduction for one of those deductions most people don’t use, but the flow for basically 80% of taxpayers, and essentially 100% of the bottom 70% of earners, should be a quick form update when life changes happen, and a yearly EITC-funded refund check that just shows up.




This is a lot like the argument that Microsoft’s Office products could be so much simpler: 80% of users use only 20% of the features.

But of course everyone in that 80% uses a different 20%. When you consolidate the overlapping deductions, credits, exceptions, exemptions, … you end up with a staggering amount of data required to accurately “pre-compute” income tax bills for even 80% of taxpayers.

“Quick form update when life changes happen” is, I think, an overly sanguine way to express a requirement that grieving parents file paperwork with the revenue service when a child has passed. That’s a bit melodramatic, but my point is that centralizing the execution of a complex tax code inside a state bureaucracy creates a perverse relationship with the folks who are supposedly in charge.

Once all the calculations are taking place in an opaque, voracious IRS database, what constraint is there on even more complex taxes and exemptions? Your doctor knows you’re a smoker. Should you pay a Medicare surcharge? ACA plan purchasers already do, in contrast with most private employer plan members.


> everyone in that 80% uses a different 20%.

No, no they don’t. Because we already have determined what most people use and made a special form for them called 1040EZ. It only offers simple things but is enough for most people. Then there’s the 1040A which goes a few steps further but is still simple. Millions and millions of returns are submitted on these short forms every year. These filers are proving that they don’t need complicated deductions and stuff because they already don’t use them.

> grieving parents file paperwork with the revenue service when a child has passed.

What are you talking about, in our current system you’d be filing next April and omitting the deceased person from the list of dependents. Your grieving strawmen would be able to take many months to go update the info before the cutoff when they print your check/bill (likely it would be minimum 4 months after year end like it is today).

> Once all the calculations are taking place in an opaque, voracious IRS database, what constraint is there on even more complex taxes and exemptions?

I don’t really want to talk politics on here, but I think this is a separate battle to fight. The tax system is already ridiculously complex because it’s trying to use the tax system to incentivize/punish behavior and at least two parties/factions have engineered it, so it’s quite confused. All politicians will continue to use this to scam the people who they like less, for the benefit of whoever they like more (campaign contributors) and they obviously don’t mind complexity even when it’s on taxpayers to compute. All things equal I’d rather force a computer to compute it and know that I can’t be audited for not understanding tax code.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: