Bowfinger
Lifer
- Nov 17, 2002
- 15,776
- 392
- 126
Sorry, that sounds unlikely to me. I'd bet their accountant doesn't know what he's talking about if you're truly looking at a relatively short-term contract for a specific project requiring special expertise (though I agree anything longer than six months raises a flag). Nonetheless, assuming the accountant is simply being reasonably cautious, there are all sorts of contracting companies out there that exist largely for situations like yours. You become an employee of the contracting company; they in turn contract you to your client. At the end of your contract, your employment is over and the IRS is happy as a clam. The contracting company gets a cut, of course, but that's the way capitalism works.Here's a good one that's I'm currently contending with.
A small company I worked for a number of years back approached me recently about fixing some of their software that has had some growing pains. I've met with them a couple of times, done some research into replacements, and put together a presentation explaining my solution. Everything looks great, other than the fact that regulation is getting in the way of me simply going in and doing the work.
They're running into a headcount problem. As soon as a company has 50 employees there's a lot of additional regulation that kicks in, which means additional expense for the company. Since I'd only be coming on for a single project and then leaving, it hardly makes sense to go to that trouble for the 9 to 12 months I'd be there. If the company has to absorb the cost of compliance and top of what they actually pay me to do the job, the ROI simply isn't there.
Well, then the next obvious solution is for me to do the work as an independent contractor, right? Not so fast. Their accountant quickly put the smack down on that idea. Due to the nature of the project, my work for them would fail most of the 20 Questions. If you're not familiar with the 20 Questions, go look them up. They're the rules that the IRS uses to determine if someones position actually qualifies as an independent contractor or not. For various reasons such as security, proximity to data, collaboration with their developers, etc. the IRS, should it choose to investigate, would probably classify me as an employee and levy fines against the company for mis-classifying me. Be aware that Obama has increased the number of positions for tracking down mis-classified employees, so the IRS is on the warpath. Now I'm sure these rules were done with the good intention of preventing some sleazebag from paying people $6/hr and calling them contractors so they don't have to provide benefits. In this particular case though, the IRS is protecting me from billing $65/hr. Oh, the horror.
So while we hash out our options and try to figure out a simple thing like me doing some work and the company paying me, I'll just continue to draw unemployment instead.
Now that's good regulation.
It is a good regulation, much as it complicates my life at times. It arose during the tech boom, when there were countless companies who abused the "contractor" status to save themselves money and to allow their de facto employees to under-report income and misuse Schedule C business deductions. These "contracts" often ran for years, with the "contractors" being treated exactly like the rest of the employees ... except on payday. It was being abused and it was reasonable to shut it down.