Question

Exporting payroll reports - expired certificates

Forum|Forum|2 years ago
September 20, 2023
3 replies
0 views

When exporting reports from QB Enterprise 23.0 to Excel you typically have to click "Enable Content" to get macros enabled then the report loads. The issue we identified today is that certain reports are tied to certificates that expired in April of 2023 and as such the macros cannot be enabled. Intuit is aware and are currently researching.

We've seen this on multiple reports, not all, but one of them specifically is exported by going to REPORTS > EMPLOYEES AND PAYROLL > MORE PAYROLL REPORTS IN EXCEL > DEFERRED COMPENSATION REPORT (FOR 401(K) & MORE).

Instead of seeing an option for "Enable Content" it only says "Options" and when you click on that you see that the Intuit certificate in question expired on 4/16/23.

R

rvrfrf

Thanks for getting in touch with the Community, test7777777. I appreciate your detailed information.

Would it be possible for you to include a screenshot or two showing what's occurring in Excel when your Enable Content option isn't present and the Options option informs you that Intuit's certificate for your file has expired?

If you could, these screenshots would help me to better understand the situation and conduct further research on my end.

For the time being, I'd recommend confirming your books are up-to-date with their latest release.

Here's how:

In the top menu bar, go to Help, then Update QuickBooks Desktop.
Click Update Now.
Hit Get Updates.
When your update's finished, close and reopen QuickBooks.
Select Yes when you're asked to install the update.
Once it's complete, follow your on-screen instructions.

I'd also recommend you confirm you're working with the latest tax table update:

In your top menu bar, go to Employees, then Get Payroll Updates.
Click Download Entire Update.
Select Update.

I've also included a couple detailed resources about updating QuickBooks which may come in handy moving forward:

I'll be looking forward to your reply. Have a wonderful Wednesday!

T

test7777777Author

We're fully up to date.

Attached is a screenshot of the expired cert.

C

ChristineJoieR

I can see your struggle while managing on exporting report in Microsoft Excel, @test7777777. Let's find a way to resolve this issue of why you're unable to export the data from QuickBooks desktop to Excel.

In this situation, you may receive one or more messages indicating that the digital signature applied to the database is no longer valid. The file's active content is blocked. We suggest checking your Trust Center settings or contacting your IT administrator for assistance.

Furthermore, I also encourage you to contact our QuickBooks Desktop support team, so they can further check if there's current update with this issue with expired certificate concern.

Follow the steps below:

On your QuickBooks account, go to the Help section.
Choose Contact Us.
State your concern, then select Continue.
We'll email you a single-use code. Enter your code and select Continue.
Select to chat with us or Have us call you.

Additionally, if you wish to personalize your data report before exporting it, refer to this page for guidance: Customize payroll and employee reports.

Alternatively, you might want to create a backup of your financial files; we can utilize this article for the steps by step process: Back up your QuickBooks Desktop company file.

We are still here to support you on achieving your exporting task in QBDT. Please tag my name if you need one.

DHeraV

I understand how this situation has affected your business tasks, @test7777777. I have some information and fixes I can share to resolve the expired certificate you encountered.

The cause of this issue was the revocation of a Symantec Root certificate, which was used in the development of applications. As a result, many certificates were deemed invalid. QuickBooks, in order to maintain the highest level of security, only allows applications with valid certificates to access company file data.

Although the warning appears in QuickBooks, it is actually Intuit that is detecting and blocking access to company file data when invalid certificates are detected. This issue affects not only QuickBooks but also other developers who have been impacted by this recent event. The complete resolution of this issue will occur once developers using expired or invalid certificates update their apps with new valid certificates.

The temporary suspension of these expired certificates has been put on hold. Intuit and Microsoft have collaborated to find a solution within Windows that allows the resumption of third-party integration. To enable this, your system will automatically receive a Windows update during its scheduled update check.

I have here a temporary solution you can perform to help you past this situation. Let me walk you through the steps:

Download zip file - https://http-download.intuit.com/http.intuit/CMO/certSync/certSync.zip
Open the downloads folder or location the zip file was saved.
Open the zip file and extract the batch file.
Right-click on the certSync.bat file and choose Run as Administrator.
It may take a few minutes to run, you should not close the Command Prompt window until you see "CertUtil: -verifyCTL command completed successfully."
Once completed, close the window and start using your 3rd party app with QuickBooks.

Additionally, you might consider visiting this website where you can find a collection of articles that provide guidance on managing your QuickBooks file: QuickBooks Desktop Help Articles.

In case you require any further clarification or have additional queries about this matter, please notify me. I'm at your disposal to provide you with the relevant information.

BigRedConsulting

@DHeraV RE: Although the warning appears in QuickBooks, it is actually Intuit that is detecting and blocking access to company file data when invalid certificates are detected.

The warning doesn't appear in QuickBooks and it is not QuickBooks that is blocking anything. It is Excel. That should be clear enough from the OP's post and would be even cleared to you had you actually tried it.

You can tell it is Excel by lowering the security settings in Excel and then running the reports, which then connect to QuickBooks with no issue. Sheesh, this isn't really that complicated.

T

test7777777Author

Replying here with the conclusion. Tier II will not refer this issue to engineering and have closed the ticket with no resolution. I also spoke to a supervisor who said the same thing.

It's an absolute disgrace the way this has been handled by Intuit. After hours of troubleshooting tier II would not even attempt to reproduce the issue on their side because if they did, they would then have to take ownership of it and actually do something. The support rep I was working with didn't even have Enterprise 23 installed. Tier II did everything in their power to point to something in my environment as the cause. First they balked because the issue was occurring on a Remote Desktop server even though Remote Desktop services is fully supported by Intuit for QB Enterprise. OK fine, so we reproduced it for them on a Windows 10 system logged in locally. They still would not refer the issue to engineering to get resolved because "lowering Excel security is the resolution."

Intuit does not care about security and have basically abandoned the desktop product. Tier II is a disgrace and are not interested in providing actual support. So is management as the support supervisor I was working with basically just shrugged their shoulders and closed the ticket.

Keep this in mind when considering giving Intuit your money in the future.

BigRedConsulting

RE: "Tier II is a disgrace and are not interested in providing actual support."

Harsh, but rather accurate.

I suppose I could re-sign and publish all of the payroll report templates with current digital signatures. I wonder if that'd be helpful?

T

test7777777Author

You have the ability to do this?

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded