Skip to main content
Level 3
June 12, 2024
Question

Cannot Import QBO file to Proseries

  • June 12, 2024
  • 7 replies
  • 52 views

As the title says, I can no longer import QBO files into Proseries returns. Worked all tax season, but a couple weeks ago it stopped working. I go to import, sign in, select the company, and then nothing happens. I don't get the account mapping and nothing imports into the file.

Does anyone have any insight into resolving the issue? Could I need to reinstall Proseries? Only articles Intuit has are the basic steps to do an import, but nothing on if there is an issue.

7 replies

dascpa
Level 11
June 13, 2024

Intuit, with it's termination of QB 2021 support has stopped QBO imports.  There are 3rd party apps that will convert QBO files into IIF files for import in QB Desktop but no clue what their future plans are for QBO.

Intuit is forcing us to QB Online as they're now going to discontinue all QB desktop products. Stupid marketing but hey, it's Intuit.

I have one client who has 42 real estate companies.  The new Intuit plan offered was for $90/per month per company.  Don't think the client will go for $45,360 in annual subscription fees.  I found today there is a new QB "Ledger" plan for only $10/mo. I'm looking into that. 

The only desktop non-subscription software I found for basic general ledger work is based out of Australia. This all - - - sucks---.

rbmuCPAAuthor
Level 3
June 13, 2024

I'm not trying to import the QBO file into a Desktop file. I am talking about the import feature that is in Proseries to populate a Schedule C, 1120S, 1065, etc. with the data straight from QBO. I was able to do this up until just a week or two ago and now I get to the selection of the company file in Proseries and nothing happens. Anyone have experienced this and fixed it?

Not to get off topic, but to your point about Intuit, Ledger looks to be a basic year end write up product. QBD is not discontinued, though they do seem to be heading that way. Best bet for your client would likely move them to enterprise, though they will then have to buy a new subscription every year. But, a lot cheaper than a QBO subscription for each company

dascpa
Level 11
June 13, 2024

I know you're not trying to import into a Desktop file.  You already said that. At the moment, QBO in general is not available as of May 31st.

Re your 2nd comment:

Q: What products will Intuit no longer be selling and what is the effective date?

Intuit has made a decision that after Sept. 30, 2024, we will no longer sell new subscriptions of the following products:

  • QuickBooks Desktop Pro Plus
  • QuickBooks Desktop Premier Plus
  • QuickBooks Desktop Mac Plus
  • QuickBooks Desktop Enhanced Payroll
PATAX
Level 12
June 15, 2024

I know this sounds archaic, but you know 12 column columnar accounting paper still works. No monthly fees, no annual fees, no import problems, no compatibility problems, no printing problems, Etc. Yes it takes more time. May want to do a cost/benefit analysis.

Level 2
October 30, 2024

were you able to fix this issue?  i have called proseries, and they escalated it to the next level, but i never received a call back.

I still cant get it to work.

 

i get a message "We did not find any quickbooks accounts that have been assigned tax lines."

They're all assigned.  It worked fine earlier in the year, then stopped.

rbmuCPAAuthor
Level 3
January 7, 2025

My issue was elevated to the engineers. They were paying particular attention to the fact that year-end tasks were not populating for particular clients. My theory was that because they were not populating there was a back-end issue affecting the import. But, nothing has fixed and I still can't import those clients and other clients as well. 

This is going to make for a bit of a rough tax season if everything has to be entered manually for all QBO clients.

Level 3
July 3, 2025

Totally agree. Used to be random now its 100% errors.

I got a new ".DLL" file and it did not work either.

Proseries says its QBO problem, QBO says its Proseries issues.

This is bad.

A sales rep got involved and she said the only way to fix it was to go to "HOSTING" of course at a monthly subscription; I declined.

Level 2
February 13, 2025

I found a solution for this!  After several calls to Intuit, a helpful gentleman with ProSeries called me and gave me the solution.  On the "Prep for Taxes" screen in QBO, once you have all the accounts mapped, then you need to toggle back and forth between cash and accrual basis (hitting save each time).  This forces the software to recalculate the numbers.  Then go back to ProSeries and try the import again.  It should work and no more error message.

Level 2
February 13, 2025

Thank you.  I am going to try that for the couple of clients that I had that issue with.  the others were fine.  They never got back to me, even after saying the escalated it.

Fingers crossed, lol.

Level 2
June 24, 2025

This is an ongoing error.  I called QB and ProSeries today and both claimed it was the other's fault and there was nothing they could do.  The ProSeries rep claimed that ProSeries does not look at these online forums.  They only escalate an issue if people call in to report the issue.  The number to call ProSeries is 800-434-6818.

IRonMaN
Level 15
June 24, 2025

"The ProSeries rep claimed that ProSeries does not look at these online forums"

The rep is correct.  For the most part they don't look at it, but they do like to send folks here so that Intuit can keep its support staff as small as possible.

Slava Ukraini!
Level 2
July 8, 2025

FWIW the import did not work for me yesterday evening. I tried it multiple times and did all the fiddling I could think of. 

Next morning (today) I tried again, and it worked.

BTW - I had already called ProSeries support before I tried for the first time today. The support person at ProSeries was getting trained by me .... if you know what I mean ....

Level 3
July 8, 2025

This should be fixed now. Please retry your import workflow. 

Level 3
July 8, 2025

I just imported 2 clients and it worked great.

I have been working with Bert with proseries and he told me it was a "network_error 401" that was causing this issue.

The old QBO import function [written 25 years ago], was updated and the authentication was failing when QBO was asking for Proseries credentials to be able to import the data.

wish this had been made known months ago. I wasted about 50 hour of my time working on this issue; QBO said its Proseries error; Proseries said its QBO. Both INTUIT companies.

Intuit needs to learn to be more responsive for these type of problems. These "techs" who are reading articles are not capable of resolving this and it should immediately be elevated to an engineer that knows the code.

Level 2
September 12, 2025

I believe I may have found the underlying issue and I am asking for some help in confirming. 

I think the issue is related to the type of subscription a client has and the way their profile is created. The issue being Simple Start clients are categorized by their first and last name, and Essentials and Advanced are categorized by their business name.

Could someone check to see if the import works for their clients with Essentials and above, but does not work for clients with Simple Start?

Kathi_at_Intuit
Moderator
September 15, 2025

Hi @almstjne , thanks for posting in the community! Since this involves 2 teams, ProSeries and QBO we would recommend connecting with QuickBooks Online Support and then if need be, ProSeries support. That way you’ll get the most accurate guidance from the right team. 

 

**Click the 👍Thumbs up icon to say thanks on a post, and click Best Answer to mark the post that answered your question.**