Split a MFJ to MFS return with correct last names

[benadlercpa]

Splitting a MFJ to MFS returns is a great feature. Unfortunately, the current implementation defaults to using the last name of the Taxpayer from the MFJ tax return for both of the MFS returns even when the Spouse in the MFJ return has a different last name. This should be an incredibly easy fix.

[sjrcpa]

True. But fixing it on your end is also incredibly easy.

[Anonymous]

Thanks for the idea to default the last name on MFJ split to MFS return to the Spouse last name instead of the Taxpayer last name. We are changing the status to "Open for voting". 

Continue to vote and comment on enhancements by going to the Idea Exchange Home page and select "Status": Open for voting, "Sort by": Most Popular. >> ProConnect Idea Exchange

If you have any questions on the life cycle of an idea, check out our Idea Exchange Getting Started Guide for more information.

[KenGreenberg]

This is a good start. But it needs to go further. I just split a return for a couple that divorced.

The last names are the same so far, so no issue there.

But now both returns show up as attached to the husband's client record. When splitting returns, the returns need to go to each taxpayer's client record. If one already exists for the spouse, assign that one there. If not, create a spouse record.

Expressed another way, a MFJ return has taxpayer 1 & 2. When split, the client record for both is now Taxpayer 1. But that's not correct. The return needs to split clients as well to Clients 1 & 2.

[KenGreenberg]

One other problem in not splitting to individual clients: the Pro Intuit Link organizer has the original primary taxpayer name - the husband - since he was the original client.

If I send this organizer to the wife it's going to show the divorced husband's name. 

This won't be acceptable, and I'll have to create a separate client and double check all carryovers.

Sadly, this solution is useless in its current state since we don't have a way to reassign a return to a different client.

The solution is a great concept. The execution needs fixing... pronto!