Heck no, why would you want to pay taxes? Just get your friendly neighborhood hacker to rig the numbers so that it looks like your fake self paid. It'll probably cost a lot less. That, or have him cook the numbers in a way so that the tax stuff comes out nearly even, so even if you do pay taxes, it's a trifling amount.
As for getting an income, well, that's a little trickier. Sure, it might be possible to have this person on an actual payroll, but that means they'll be showing up on an employee list in HR, and they've got ways to track productivity that'll eventually show this person isn't coming in to work. For the crunchy bits, I'd say that drawing an income from a fake ID would subject this ID to a test every time the paychecks are written up, with the employer's dice pool based on the size of the company and how much is being paid out. (You don't want to be drawing a fake paycheck from Ares.)
There are ways around this, naturally, but if a company is actually paying money to a non-productive employee, they tend to sit up and take notice eventually. If an employee's on the list, but not impacting the payroll, they would probably assume it's an artifact, or an ex-employee that just didn't get removed from the database. Happens all the time, and if it's not costing them money, who cares?
In addition, this payment would have to go to a bank account, linked to the fake ID or channeled through it to another ID. That would be a point of vulnerability; sure, the account would show regular activity, lowering the chance of the bank asking questions, but if the company writing the check started getting suspicious, then the ID's activity would come into question.
All of this could be covered up, sure, but the hacker doing so would want a cut of the proceeds. Given the risk -- a monthly (or bi-weekly) chance of discovery would mean high risk, and the hacker would ask for a larger percentage as a result.