QuickBooks 2016 R5 Released

Intuit released the QuickBooks 2016 R5 update for the U.S. version of QuickBooks. This is available as a manual update from the Intuit support website. I’m not sure when it will go out as an automatic update.

I haven’t had a chance to test this yet. You may want to wait a week to see if there is any great outpouring of grief from early adopters (which I don’t expect, but I’m cautious).

The biggest issue is a change that relates to PCI (Payment Card Industry) compliance – if you need this, then you have to do some extra work to remove a component from your system. If you remove that component, several features in QuickBooks will stop working (and possibly other programs).

These changes should affect Pro, Premier and Enterprise:

This release changes one of the Microsoft programming tools that is used in QuickBooks, converting from MSXML 4 to MSXML 6. This is needed to address PCI Compliance standards. I talked about this in more detail in my article on the QuickBooks 2015 R9 release. To be compliant you need to remove MSXML 4 from your system after converting – that is something that might create problems with other programs on your computer that might require it. So be careful. Note that if you remove this component then several utilities provided by Intuit will stop working, including Contacts Sync, Scan Manager, and Shipping Manager.

  • The Rebuild utility has been updated to delete stray item sites.
  • An issue is resolved that would cause Verify to fail after deleting the class selected on a record.
  • An issue is fixed that prevented users with Internet Explorer 11 from accessing their banks website using the QuickBooks internal browser.
  • Transactions can now be saved successfully even if they contain a detail line that uses an item that has a manufacturer’s part number for an assembly item that was not purchased through a vendor.

These changes only affect Enterprise users:

  • If you disallow negative inventory quantities, when creating an invoice from a sales order you will only receive a “Negative On Hand Detected” alert after you have completed editing all items.
  • Barcodes can be manipulated without causing the screen to freeze (alignment changed, printed, previewed before printing)
  • An issue was resolved that caused the following error to show up in the QBWIN.LOG file when running a Verify: Sum of item xxxxxx on item site table not match quantity on hand stored at item history table.

Leave a Reply