ProSeries Import function

[Revener]

Encountering Error Code 1 when attempting to import data directly from a financial institution. No solution after 2 months. 

[Just-Lisa-Now-]

Seen many complaints, no fixes though, sorry.

@IntuitBettyJo  Im sure this is on someones radar over there, we just havent seen anything official about whats being done to rectify the issue...got any news?

[AshleyatIntuit]

Just saying my two cents here but of the ones I've seen the root cause has typically been unsupported bank. And aside from that have seen Banks that require an MFA secondary step that doesn't come thru with Fido. Note that the import feature is meant to save time and if that's an issue you've had for that long you may want to manually enter. 

[abctax55]

You've sat on a return for two months rather than manually summarize & enter the info?  Wow.

[IRonMaN]

My back would hurt if I sat on something for that long.  What does your client think?  He or she must wonder what is going on.  They might have even read the instructions in the meantime  and found that you can just enter totals.

[Revener]

Multiple returns with many, many details transactions. 

[IRonMaN]

But you can enter totals.

[AshleyatIntuit]

When you say multiple returns, are you producing that error with all of them? And do all use the same bank? Also is this doing scan and importing or is this doing Fido?

[Just-Lisa-Now-]

Many people have asked about it, many different banks, its been at least a month now. That same Error Code 1.

[AshleyatIntuit]

Noted @Just-Lisa-Now- tax scan and importing isn't my forte but figured I'd ask just in case. If all imports do this then I would lean towards software or the specific os. So let me ask this... When was ProSeries last updated and do you have any pending Windows updates not downloaded and or installed? And lastly if on a network can other workstations successfully import?

[AshleyatIntuit]

Slight additional edit: I will look at this Monday too when I get in the office, see if I can locate anything specific. and will report back if i find something specific to this. Promise 🙂  In the mean time i would stick by my recommendation of updating both ProSeries (and/or running Repair/Refresh updates) and checking to see if any Windows updates are pending.

[Revener]

The error code occurs when importing Fido. After the error message appears, the next message is "import has been successful" but the data do not show in the returns.  

ProSeries and Windows are updated.

[BrianG932]

Did you find out anything?

[AshleyatIntuit · Accepted solution]

Hi, sorry for my delay about this, here is what I know.  We have an open Investigation around this unexpected behavior with the following context:

Apex and Betterment , Raymond James , AmeriTrade give an error Code 1 after data is imported into the client file with 1099-B data.

Charles Schwab gives error: You can ask the financial institution if you'll get this form, and return to import it when it's available.(902)

If you already have the info, you can enter it by hand. (902) AmeriTrade Error 1

FIDO Fifth & Third Bank no error code just message forms are unavailable

Based on the information above, we have an update anticipated for 4/22 (today).  If that update goes live, we recommend trying again to re-pull that FIDO , or alternatively use the Scan and Import feature.  Today's update should be live (it typically is provided around 3pm, EST) but if for any reason that update does not go live today, I will reach out to confirm new release date.

[Revener]

Investigation completed. Update released today fixed the problem. Thanks.

[Revener]

The direct import function is on the blink again the same as last year. Don't know why Intuit can't get this fixed. Spent 2 hours on the phone with tech  support to no avail. May have to do a work around. What a bummer. 

[Revener]

The Import function is a problem again this cycle. On the phone with Tech Support for 2 hours, and didn't get a solution. Is this problem being investigated and when can we expect a fix?