Skip to main content
October 23, 2020
Question

Unable to get a Client Ready Payroll report

  • October 23, 2020
  • 6 replies
  • 0 views

Attempted to run client ready payroll reports in QB Desktop 2020.  Only the first tab pulls up.  No box to select reports or tabs, time period ext.  Just the one tab with "Please Turn on Macros".

6 replies

October 23, 2020

Hi @dso0216,

 

I'll handle this query for you. 

 

You'll have to toggle macros for Microsoft Office applications to enable them. You need to click the Enable Content button on your MS Excel file that appears when you run the report, so you can proceed and generate it. 

 

I recommend you view this article: Accountant tools: Review list changes. It allows you to see and review all changes made in your items. 

 

If you have other concerns, share them in the comments below, and I'll get back to you. 

January 5, 2022

This has happened again with the latest payroll update. The Enable Macro or Enable Content button is not there like it usually is. It "broke" overnight with the payroll update.

January 16, 2023

I was able to fix this issue by changing my Microsoft Office to the 64-bit version. I had to uninstall Office and download the 64-bit installation file. None of the other suggestions here worked at all. Updating to the 64-bit version of Excel allowed me to print the Client Ready Payroll Reports again.

January 18, 2023

Colleague and I had the same issue and even after having the latest payroll update downloaded, we both had to Employees>Get Payroll Updates> select radio button "Download entire payroll udpate" and click update button.  This enabled us both to get export the Client Ready Payroll Report that we have done for years.

January 19, 2023

Now on multiple computers we get a message from excel:

Microsoft Visual Basic for Applications

Compile error in hidden module

 

Must be an update from MS365 or QB's

It is true if you re-install QB's and the MS Suite again it works but for a short time.

 

 

 

January 19, 2023

Here is what's happening-  we just had this happen and my son is a long-time IT guy and figured out what's going on (QB tech guys - feel free to share this with your programming team so MAYBE they can fix this):

 

The fact is that Microsoft Office 365 (and through some of their more wonderful glitched updates for the full desktop version), has disabled Visual Basic for Applications (VBA) - (EVEN THOUGH, half of Microsoft Office's advanced functions still rely ENTIRELY on VBA??) Neat, Huh? You can't just "download" VBA and hope for it to work (if you're lucky enough to find it thanks to Microsoft hiding it... because "reasons"???). The problem is this: QB doesn't just employ a simple "export to excel" for this employee payroll report like it does for EVERY OTHER EXPORT TO EXCEL FUNCTION???... no, for some inexplicable, overly-complicated reason, to force the formatting to text function (which is weird the way they do it), they use their own version of a "programmed VBA script" that can only communicate to Excel via a Macro-enabled script instead of just a macro OR a script (soundly needlessly complex? yes it is.), and to communicate with Excels' underlying, advanced programming functions, QB programmers MUST use VBA (and subsequently, the QB programmers didn't feel the need to investigate whether or not this would be a problem with the discontinued support of VBA for MS 365 without some insane work-around NOR inform the world, or even their own front-facing support team, that this was happening).

 

But, Microsoft says, "No!" VBA has vulnerabilities so we shut it down from all the online folks to "protect you from yourself... for your own good (hint hint wink wink)" and "Please ignore the fact that we shut down the function of Excel that Excel needs to function". And, even for those folks who aren't having this problem "yet" thanks to skipped updates or NOT updating - it's coming - and unless these two major tech powerhouses take a whopping 1 week outta their lives to communicate - it's not gonna get fixed. Fast Forward to your macro problems we are ALL having.

 

Everything you read online will tell you that it's an authentication / platform compatibility issue and is probably related to 32 / 64 bit architecture software types. That is "mostly" a bunch of hooey. (FYI, always install 64 bit when you can, it does tend to function better with your processor). What's happening is that you DON'T have VBA OR the authorization to use VBA has been blocked and there is no "fix this" button (because, again, "reasons"...). So, when Excel reads the VBA script being passed down from QB, it goes, oh, let me check the VBA engine to see how this is supposed to be translated and... OH MY DEAR HEAVEN! There is NO VBA code to translate this! It MUST be bad! Compile error!!! Danger Will Robinson! Danger!

 

And your productivity as an accountant just stopped-  completely. Although, you can hand code those spreadsheets, or just enter the information online manually... one employee at a time. Bet you all love that solution, huh? (*knowing wink)

 

It's not a compile error. It's not bad script from QB. You don't have to rebuild your company files or reinstall the software (well, some might have to - between Intuit and Microsoft... they both have... "issues"). It's like if you accountants went to enter payroll and the company handed you a blank sheet of paper. Where's the payroll? I can't enter "nothing". I NEED numbers! Error!

 

You can roll back your computer updates to the last time you knew it to work ... for now ... and it will work (hopefully). That is, until your computer updates (and if you don't update, modern windows has a neat feature to utilize ALL of your disk and memory processing power to slow you down to a snail's pace until you do). What to do? For now... you need to download a full version of Microsoft Office. Not 365, not the monthly subscription, Microsoft Office. Save yourself time and energy and find some instructions on line to download a "trial" copy and go buy one of those cheap, "activation codes" (I'm not gonna post the link, even tho it's actually perfectly legit and financially awesome - I don't know how QB mods will feel about it - Google it). 4 outta 5 times, the folks selling it are honest... (*sigh), and outta those 4, if the code doesn't work, it's cause they're abusing it and mass reselling it and at least 80% of them will just give you a new code, and when you go for the install, make "sure", that in the options, VBA is selected. Voila! Reboot the machine to get the registry back in order and the day is saved. You don't even have to uninstall MS 365 (although that will cause you some heartache if you don't).

 

Now - this may not work 100% for everyone. We are talking Microsoft... and Intuit ... and two companies that apparently don't know how to be tech companies... so, who knows? But, this is an immediate, long-term solution to get y'all back up and running asap. I hope it helps. My son is doing the full desktop version of Office install tonight for me and getting VBA turned back on. Good luck!

January 20, 2023

Here is the fix that Microsoft had me do and it will roll back Office 365 and the client ready, SUI & W2 uploads now work.  I did help another person do this, they can get the SUI & W2 uploads to work, but not the client ready reports.

 

1.  Go to office.com and log into your Microsoft account. Go to admin, then down to "show all"

2.  Go to Org Settings, select Microsoft 365 installation options, then select "Every six months (Semi-Annual          Enterprise Channel), save and exit

3.  Uninstall Office 365, when done restart your computer

4.  Go back to office.com, go to Home, in the upper right hand corner, click on install apps and pick premium       Microsoft 365 apps and download and install Office 365.

 

This will install a rollback to 2008 version and then it will work.

 

Hope this helps

January 23, 2023

I had the same issue , when you run the client payroll report, no report is generated automatically any more,  I spent  over 4 hours with Intuit tech supprt and they did all the trouble shooting and come to last statement it is Microsoft issue and you have to contact Microsoft. 

 

I decided to find the solution my self and this s the solution: 

 

  • click on report. scroll down to employee and choose Client Ready report 
  • excel opens up and prompts you to enable connect, Do so. 
  • the excel is not blank since the connection to data is lost.  
  • choose Addins on tool bar
  • on first tool bar now, choose get data from quick books 
  • this shoud resolve the issue .