Skip to main content
Avalara Help Center

Dec 27 2012 Release Guide: Sage Sales Tax for Sage 300 ERP 6.0A Powered by Avalara AvaTax


Product Release Information



Sage 300 ERP 2012 Sales Tax, Powered by AvaTax

Release Number:

Release Date:

27-12-2012 (DD-MM-YYYY)

Customer Support:

For more information or support, please visit or email at












This document contains the release notes for Sage 300 ERP Sales Tax, Powered by AvaTax  for Sage 300 ERP 2012 version 6.0A. The following sections describe the release in detail and provide late-breaking or other information that supplements the main documentation.


Installation and Upgrade Notes




All users must Log off from Sage 300 ERP before deploying this release.

There is two level of installation.


  1. During the installation user can specify two paths using ‘Browse’ directory capability provided in installer package
  • Avatax connector path (Relative path where Avatax connector need to be installed). Default location is “C:\Program Files\Avalara\AvaTax Connect Adapter\”
  • Application directory path (Relative path where Sage 300 ERP application is installed).
  1. After the install-Shield’s installation a new folder is created “%avatax_connect_path%\”
  2. Following files are created at the specific locations
    • 11 files in the % avatax_connect_path%\bin
    • TV60A folder is copied to the Sage 300 ERP application directory (on the path as per user’s selection during installation)
  • TV60AENG.chm file is copied to the help folder of Sage 300 ERP folder (on the path as per user’s selection during installation)



 Before installation of this release, if any previous version of Sage 300 ERP Connector already installed needs to be uninstall.




This release consists of the following items:


  • Release notes (this file)
  • Executable setup file – ‘Sage 300 ERP Sales Tax Powered by AvaTax’


Version Compatibility


This version is compatible with


  • All Sage 300 ERP 6.0A Editions (Required Modules: SM, GL, AR, IC, and OE with PU1)


  • Database: MS SQL 2005– supported and tested, MS SQL 2008 - supported, Pervasive PSQL version 10.3 – supported



Minimum System Requirements


System Processor:

Server: Intel duo-core/quad-core processor or higher, Client: Intel Core 2 Duo

System Memory:

Server : 4 GB RAM , Client: 2 GB                                                

Free Disk Space:

Server: 5 GB, Client: 100 MB

Operating System:

Server: Windows 2008 Server, Windows 2003 Server, Client: Windows XP(SP3),


x86/x64 Windows Vista (Supported)


Internet access

Existing Software:

Microsoft’s .NET framework 2.0 (If not present the Installer will install the .NET framework 2.0 from web)












Issues Fixed In -

  • Ticket #32 - Pass Location Code
  • Ticket #37 - Company Address Validation Functionality in AvaTax Option UI
  • Ticket #36 - Sage 300 ERP Connector: Address Validation in all transaction Screen Ship-to Window
  • Ticket #38 - AR Invoice Entry - Save Confirmation message on Window close button click
  • Ticket #511 - TVHIS03 and TVWRK03 tables: Putting "TaxName" field values into "JurisName" table field of Canada Sales Tax Transactions
  • Ticket #525 - Errors with AK customers
  • Ticket #33 -  Credit Memo - Tax Calculation Date
  • Ticket #523 - Customized AvaTax screens log users out of 300 ERP
  • Ticket #34 -  Job Costing in 300 ERP – AvaTax for Sage 300 ERP 6.0
  • Ticket #522 -Tax Only Adjustment – Sage 300 ERP ERP
  • Ticket #524 - Screen resizing issue AvaTax Order Entry UI
  • Ticket #526 - Error when importing shipments
  • Ticket #35 - Wrongly passed Item Code as a Revenue Account in Credit Note


Known Issues and Workarounds (If any)

  • Ticket #15229 - Invalid DocCode passes to request in case of AR Invoice after firing GetTax
  • Ticket #16677 - DLL hell issue in case previous version of  DLL is already registered.
  • Ticket #15270 - Reconciliation - Instead of TaxBase amount it requires to do Reconciliation on the basis of Total amount of Dash Board.
  • Ticket:  3341- Log file Generation fails when two different UI's are active at a time.
  • Ticket:  4580 - Partial Shipments Issue on Order Entry UI.
  • Ticket:  5948 - SP1 - Tab Indexing On Avatax Options UI.
  • Ticket:  5587 -  Document gets posted at ERP even if any errors thrown from AvaTax during commit call (for Already existing Transactions at AvaTax Server)
  • Ticket:  6399 -  Multi User access to be restricted for Reconciliation UI


Others -                                                         

  • Currently, help file linking with all UIs is done, but “UI/Content based help” needs to handle on each UI.
  • On AvaTax Options screen, if changes are made, while other connector UIs are open; then it is not throwing any error message or restricting saving event.
  • In AR Integration, AR Retainage/PJC/OE/Misc. Receipt related Tax calculations – Currently out of scope.
  • Was this article helpful?