Yikes, that's an annoying glitch. Good find, thank you for highlighting this.

However, keep in mind this isn't a channel for communicating glitches to tech support. This is a peer-resource-sharing platform.

It's annoying, but you have to call support to submit this as a ticket for them to fix it.

I am not sure there is a channel for communicating glitches

MY channel is to bug:

@Kathi_at_Intuit 

How come Lacerte keeps breaking things that were working fine?  I'm to the point I am even double checking that the basic math of the tax liability on EVERY return.  I'm old, I've done returns on paper before (eons ago).  Not being able to depend on/trust even the certain basic functions is, well, disconcerting for such premium software.

(Hi, Bill 😉

I tried to submit this issue through their email communication within the program.  They kicked it back to me saying I need to call the issue in.

So I did.  A really nice person, but this process is not designed with the user in mind.  It took an hour and half to get the next level up to understand and write up the issue.  They agreed it is an "unintended behavior" and will get it fixed.

Unfortunately, I believe their fix will be that a "-1" in the state field will be treated as $0 state basis reduction.  I encouraged them to create a diagnostic.

Without this, there are going to be a lot of taxpayers going forward now with a state basis reduction that never existed before.  And I doubt many tax preparers will notice.

I agree that the reporting process is inefficient. Just had another thought though. Could you press CTRL+E on the field and enter "-1" on one line and "1" on another to net to zero?

Hi @PVcpa8070  I sent you a private message. 

Yeah. Good idea, but that results in the State Basis Reduction being same as Federal