Form 7203 - During the checking of entries it keeps thinking that line 2 is for number of days you provided services to someone

[Csherer]

Form 7203 - During the checking of entries it keeps telling me to fix this entry.  It is on Part 1 line 2 and the error that comes up is for "Number of days you provided services to someone else shouldn't be less than zero.", but the actual item for number 2 asks for:

"Basis from any capital contributions made or additional stock acquired during the tax year."  I am not sure if I can still submit my taxes with this error that keeps coming up.  Is anyone else having this issue?  I don't see any other place on the form to enter the number of days service is provided.

[PatriciaV]

We have tested entries for Form 7203 but are unable to reproduce the experience you have seen. It would be helpful to have a TurboTax ".tax2025" file to test this issue further.

If you would be willing to send us a “diagnostic” file that has your “numbers” but not your personal information, please follow these instructions: 

In TurboTax Desktop, open your return and go to Online in the TurboTax header. (On a Mac computer, choose Share or Help.)

1. Choose Send Tax File to Agent.
2. You will see a message explaining what the diagnostic copy is.  Click Send on this screen and wait for the Token number to appear.
3. Reply to this thread with a screenshot of your Token number (this avoids Community filters for numbers with a dash) and tag (@) the Expert requesting the token from you.
4. Please include any States that are part of your return - this is VERY important.

We will then be able to see the same experience you are having. If we are able to determine the cause, we'll reply here and provide you with a resolution. 

[user17712746489]

I found a work around.  I was able to move the amount I was trying to add to a different line and the error message went a way.  It seems the tax software my CPA uses allows a negative number to be added in the field I was using but turbo tax does not.  The negative number was creating the error and it no longer does now.

Thanks for looking into this.