This article applies to:AvaTax for QuickBooks Desktop
Read the release notes to learn about the latest additions, changes, and fixes to AvaTax for QuickBooks Desktop.
AvaTax for QuickBooks Desktop (2020 releases)
November 13, 2020
- Fixed an issue that caused an error to display when attempting to calculate leasing tax in Chicago.
March 15, 2020
- Fixed an issue where a QuickBooks Desktop certificate listed as invalid prevented tax from calculating for some users.
AvaTax for QuickBooks Desktop (2019 releases)
March 15, 2019
- You can now create a test customer during initial setup
- AvaTax for QuickBooks Desktop is now compatible with QuickBooks Desktop 2020
- Improved error messaging
- Fixed an issue where items or services with a 0.00 price were listed as 0.00%
- Fixed an issue where entity/use codes lists weren't updated when the connector was upgraded
- Fixed an issue where the incorrect AvaTax company displayed after importing another company's data
- Fixed an issue that prevented changing the reconciliation date range after selecting an initial date range
- Fixed the issue that caused an "AvalaraEventCallback.exe has stopped working" error when attempting to export or print an AvaTax reconciliation report
AvaTax for QuickBooks Desktop (2018 releases)
December 21, 2018
- Added a tax item rollback utility. Use this utility to restore tax items to what they were before you installed AvaTax.
- Renamed the reconciliation window AvaTax Reconciliation
- Entity use code F is now "Religious Organization"
- Added entity use code M - "Educational Organization"
- Improved the AvaTax for QuickBooks Desktop setup wizard:
- Added a message to let you know when the setup wizard finishes
- Added buttons that make it easier to select/deselect tax items
- The window pops up on top of your desktop (now it won't get lost if you're using many apps at once)
- Fixed an issue that prevented tax calculation on the first transaction sent to AvaTax for some users
- Fixed an issue with the tax schedule that caused an error
- Fixed an issue with the Batch Address Validation utility that caused an error
- Fixed an issue with user permissions that resulted in a "StatusCode 3260" error
- Fixed an issue where tax was being calculated using different origin addresses for transactions with the same Site ID