Welcome back! Ask questions, get answers, and join our large community of tax professionals.
- Topics
- Training
- Community
- Product Help
- Industry Discussions
- User Groups
- Discover
- Resources
In anticipation of the upcoming May 15th deadline, we've compiled a list of the most common questions here.
In anticipation of the upcoming May 15th deadline, we've compiled a list of the most common questions here.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Intuit Accountants Community
- :
- ProSeries Tax
- :
- ProSeries Tax Discussions
- :
- Nebraska 1120S error
Nebraska 1120S error
Options
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
SBBCPA
Level 2
02-02-2022
10:37 AM
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
I finished preparing an S corporation return for a business located in Nebraska. Both shareholders are Nebraska residents, so no withholding is required. However, Pro Series has an error on Schedule II, which states that Column F total must equal line 5 on the 1120-SN itself multiplied by the shareholder ownership percentage. I did not make any input on the Schedule II, in fact Pro Series generated it apparently automatically. Does anyone know of a work-around for this?
Labels
2 Comments 2
IntuitMark304
Employee
02-02-2022
03:12 PM
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
SBBCPA,
I am having difficulty replicating the error you are experiencing. Can you provide more detail on the scenario? Additionally a question to other users, are you also running into this issue?
If there is a problem in the software, I am interested in identifying as soon as possible so we can remidiate it immediately for our users.
SBBCPA
Level 2
02-03-2022
08:34 AM
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
I called your support line and Shanetta helped me upload a sanitized version of the client file with this issue. She also replicated my issue & has referred it to a higher level to discover the programming flaw. See case #1575992719.
