Skip to main content
Avalara Help Center

AvaTax for Sage 300 Release Notes Archive

AvaTax for Sage 300 (2018 releases)

January 2, 2018

Release 6.20.116.00

Fixed

  • Fixed the issue where a "Duplicate address code" error prevented transactions from processing and posting 

AvaTax for Sage 300 (2017 releases)

August 16, 2017

Release 6.30.105.00

Fixed

  • Fixed the "Tax group AVATAX mismatches with the AvaTax Options " error that occurred while posting sales transactions without line items
  • Fixed the "This is a duplicate of an existing Document with unique index and cannot be saved" error that occurred while trying to post edited AR transactions
  • Fixed the issue that terminated the AR batch deletion operation without displaying a message
  • Fixed the issue where sales tax wasn't calculated for credit notes created from RMA module
  • Fixed the issue that occurred while deleting lines in sales order  

August 16, 2017

Release 6.20.115.00

Fixed

  • Fixed the "Tax group AVATAX mismatches with the AvaTax Options " error that occurred while posting sales transactions without line items
  • Fixed the "This is a duplicate of an existing Document with unique index and cannot be saved" error that occurred while trying to post edited AR transactions
  • Fixed the issue that terminated the AR batch deletion operation without displaying a message
  • Fixed the issue where sales tax wasn't calculated for credit notes created from RMA module
  • Fixed the issue that occurred while deleting lines in sales order  

May 23, 2017

Release 6.40.102.00

  • You can now map tax codes using the Tax Code Mapping utility for Type A/R item
  • Fixed the Data Dictionary error that occurred while creating OE transactions 
  • Fixed the issue where transactions failed to commit due to a Data Dictionary error
  • Fixed the issue where the Country for Mapping list took too long to populate data, which made the UI freeze 
  • Fixed the issue where PST exemptions weren't applied
  • Fixed the issue that occurred while processing transactions with a negative quantity
  • Fixed the database error that occurred while posting sales invoices ​​​​

May 23, 2017

Release 2016 6.30.104.00

  • Fixed the "CreateFile Failed" error that occurred while installing on workstations
  • Fixed the item price update issue that occurred while reposting the sales order

April 25, 2017

Release 6.30.103.00

  • You can now map tax codes using the Tax Code Mapping utility for Type A/R item
  • Fixed the Data Dictionary error that occurred while creating OE transactions 
  • Fixed the issue where transactions failed to commit due to a Data Dictionary error
  • Fixed the issue where the Country for Mapping list took too long to populate data, which made the UI freeze 
  • Fixed the issue where PST exemptions for Canada weren't applied
  • Fixed the issue that occurred while processing transactions with a negative quantity
  • Fixed the database error that occurred while posting sales invoices   

January 31, 2017

Release 6.20.114.00

  • You can now map tax codes using the Tax Code Mapping utility for Type A/R item
  • Fixed the Data Dictionary error that occurred while creating OE transactions 
  • Fixed the issue where transactions failed to commit due to a Data Dictionary error
  • Fixed the issue where the Country for Mapping list took too long to populate data, which made the UI freeze 
  • Fixed the issue where PST exemptions weren't applied
  • Fixed the issue that occurred while processing transactions with a negative quantity

AvaTax for Sage 300 (2016 releases)

October 15, 2016

Release 6.40.101.00

  • Compatible build for Sage 300 2017

September 30, 2016

Release 6.30.102.00

  • Fixed the issue where the client installer was missing from the installer package.
  • Fixed the issue where the AR batch execution was slower than expected.
  • Fixed the issue with the addition of an AR invoice to the AR batch. Add an AR invoice to the AR batch and then, save it successfully.
  • Fixed the issue where the subtotal amounts in Orders were either incorrect or missing.
  • Fixed the issue where line-level discounts in the OE Order/Shipments weren't displaying in the OE invoice.
  • Fixed the issue where the header-level discount in the OE invoice wasn't displayed in the AR batch after the day-end process was executed.
  • Fixed the errors that occurred when AvaTax was installed without the following modules activated:
    • Order Entry
    • Inventory Control
  • Fixed the issue where the item's commodity number wasn't sent as the tax code for an Order Entry even when the AvaTax Options > General > Tax Code Mapping field was selected as Commodity Number.
  • Fixed the issue where the header-level discount wasn't considered for shipments when the Shipment Entry was created from an Order Entry with a discount.
  • Fixed the issue where the invoice was showing an incorrect quantity for a partial shipment.
  • Fixed the issue where the credit note was showing incorrect subtotals when lines were deleted from the invoice while creating a credit note.
  • Fixed the issue where the PO Number wasn't showing in the transactions.
  • Fixed the errors that occurred during the posting of AR recurring batch.
  • Fixed the issue where during tax calculations for miscellaneous items, the tax code P0000000 was considered instead of tax codes mapped in AvaTax for Sage 300.
  • Fixed the issue where the search criteria for reconciliation of documents didn't show correct results.
  • Fixed the "Company not found Verify the CompanyCode" error generated while searching for a non-AvaTax company invoice from AvaTax History.
  • Fixed the "Record has been modified by another Program" error generated while manually trying to edit an entity/use code in the AvaTax Entity/Use Code Mapping utility.
  • Revised error messages for:
    • Incorrect or missing address on the transaction 
    • Incorrect or incomplete address in the company profile 
  • Fixed the issue with the item tax class while posting an order having items that were non-taxable, amount as 0, and entity use code at the line-level.
  • Fixed issues noticed while posting multiple shipment invoices.
  • Fixed issues where invoices processed from the Capture Payments with Invoices screen weren't posted to AvaTax.

September 30, 2016

Release 6.12.107.00

Changed

  • Revised error messages for:
    • Incorrect or missing address on the transaction 
    • Incorrect or incomplete address in the company profile 

Fixed

  • Fixed the issue where the AR batch execution was slower than expected.
  • Fixed the issue with the addition of an AR invoice to the AR batch. Add an AR invoice to the AR batch and then save it successfully.
  • Fixed the issue where the subtotal amounts in the Orders were either incorrect or missing.
  • Fixed the issue where line-level discounts in the OE Order/Shipments weren't displaying in the OE invoice.
  • Fixed the issue where the header-level discount in the OE invoice wasn't displayed in the AR batch after the day end process was executed.
  • Fixed the errors that occurred when AvaTax was installed without the following modules activated:
    • Order Entry
    • Inventory Control
  • Fixed the issue where the item's commodity number wasn't sent as the tax code for an Order Entry even when the AvaTax Options > General > Tax Code Mapping field was selected as Commodity Number.
  • Fixed the issue where the header-level discount wasn't considered for shipments when the Shipment Entry was created from a Order Entry with a discount.
  • Fixed the issue where the invoice was showing an incorrect quantity for a partial shipment.
  • Fixed the issue where the credit note was showing incorrect subtotals when lines were deleted from the invoice while creating a credit note.
  • Fixed the issue where the PO Number wasn't showing in the transactions.
  • Fixed the errors that occurred during the posting of AR recurring batch.
  • Fixed the issue where during tax calculations for miscellaneous items, the tax code P0000000 was considered instead of tax codes mapped in AvaTax for Sage 300. .
  • Fixed the issue where the search criteria for reconciliation of documents didn't show correct results.
  • Fixed the "Company not found Verify the CompanyCode" error generated while searching for a non-AvaTax company invoice from AvaTax History.
  • Fixed the "Record has been modified by another Program" error generated while manually trying to edit an entity/use code in the AvaTax Entity/Use Code Mapping utility.
  • Fixed the issue with the item tax class while posting an order having items that were non-taxable, amount as 0, and entity use code at the line-level.
  • Fixed issues noticed while posting multiple shipment invoices.
  • Fixed issues where invoices processed from the Capture Payments with Invoices screen weren't posted to AvaTax.

August 31, 2016

Release 6.20.113.00

  • Fixed the issue where the AR batch execution was slower than expected.
  • Fixed the issue with the addition of an AR invoice to the AR batch. Add an AR invoice to the AR batch and then, save it successfully.
  • Fixed the issue where the subtotal amounts in Orders were either incorrect or missing.
  • Fixed the issue where line-level discounts in the OE Order/Shipments weren't displaying in the OE invoice.
  • Fixed the issue where the header-level discount in the OE invoice wasn't displayed in the AR batch after the day-end process was executed.

August 16, 2016

Release 6.20.112.00

  • Fixed the errors that occurred when AvaTax was installed without the following modules activated:
    • Order Entry
    • Inventory Control
  • Fixed the issue where the item's commodity number wasn't sent as the tax code for an Order Entry even when the AvaTax Options > General > Tax Code Mapping field was selected as Commodity Number.
  • Fixed the issue where the header-level discount wasn't considered for shipments when the Shipment Entry was created from a Order Entry with a discount.
  • Fixed the issue where the invoice was showing an incorrect quantity for a partial shipment.
  • Fixed the issue where the credit note was showing incorrect subtotals when lines were deleted from the invoice while creating a credit note.
  • Fixed the issue where the PO Number wasn't showing in the transactions.
  • Fixed the errors that occurred during the posting of AR recurring batch.

June 30, 2016

Release 6.30.01.00

  • Compatible build for Sage 300 2016

June 30, 2016

Release 6.20.111.00

  • Fixed the issue where during tax calculations for miscellaneous items, the tax code P0000000 was considered instead of tax codes mapped in AvaTax for Sage 300.
  • Fixed the issue where the search criteria for reconciliation of documents didn't show correct results.
  • Fixed the "Company not found Verify the CompanyCode" error generated while searching for a non-AvaTax company invoice from AvaTax History.
  • Fixed the "Record has been modified by another Program" error generated while manually trying to edit an entity/use code in the AvaTax Entity/Use Code Mapping utility.
  • Revised error messages for:
    • Incorrect or missing address on the transaction 
    • Incorrect or incomplete address in the company profile 
  • Fixed the issue with the item tax class while posting an order having items that were non-taxable, amount as 0, and entity use code at the line level.
  • Fixed issues noticed while posting multiple shipment invoices.
  • Fixed issues where invoices processed from the Capture Payments with Invoices screen weren't posted to AvaTax.

June 1, 2016

Release 6.12.106.00

  • Enhanced batch utility for tax calculation. You can now recalculate tax for AR batches and update corrupted/deleted documents
  • Integration with Avalara's certificate management system. You can now request and retrieve exemption certificates
  • Added the Setup Assistant to aid setup and configuration for AvaTax. Option available in Sage Sales Tax Powered by Avalara > AvaTax Setup Assistant
  • A self-provisioning feature lets new users create an AvaTax account and company with trial plan of 30 days without any assistance. On the Avalara Setup Assistant page, click Sign up
  • Added the Tax Profile Assistant to aid with nexusHoverTT.png setup and other settings for AvaTax
  • Now you can choose to send the UPC instead of the item code to dictate product taxability. By default, the item code is sent to AvaTax
  • You can now calculate consumer use tax for an invoice created from the Receipt Entry and the Invoice Entry in Purchase Orders > P/O Transactions
  • Added AvaTax Transactions Report. This report displays posted or saved documents based on document type, range of document numbers, and range of dates
  • Added the option to select and assign a Currency Code while creating a new Tax Group Code. This option is only available if the Multicurrency option in the System Manager is selected and enabled during the Sage 300 installation. If the Multicurrency option is not selected and enabled, then the Functional Currency is assigned to the Tax Group Code
  • Invoices deleted in the AR module will now also be deleted from AvaTax
  • Removed the Tax Only Adjustment functionality
  • Added appropriate status messages during the posting process of AR batches
  • Fixed the errors generated during the posting of AR Batch
  • Fixed the issue with tax calculation for transactions having both taxable and non-taxable items
  • Fixed an issue with the tax calculation based on the item quantity for Orders
  • Fixed the issue where the currency code was appearing in non-related fields in an invoice
  • Fixed an issue where the discount at the header-level was added to the credit note amount during the tax calculation
  • Fixed an issue where the header level discounts were not considered while calculating tax in the OE module
  • Fixed "The total tax base/amount of the detailFs (amount) does not match the tax base/amount of the document (amount) for tax authority AVATAX" error that occurred after you click Generate CN in the R/A Return Authorization Entry window

April 29, 2016

Release 6.20.110.00

  • Calculate consumer use tax for an invoice created from the Receipt Entry and the Invoice Entry in Purchase Orders > P/O Transactions.
  • Added the option to select and assign a Currency Code while creating a new Tax Group Code. This option is only available if the Multicurrency option in the System Manager is selected and enabled during the Sage 300 installation. If the Multicurrency option is not selected and enabled, then the Functional Currency is assigned to the Tax Group Code
  • Fixed "The total tax base/amount of the details (amount) does not match the tax base/amount of the document (amount) for tax authority AVATAX" error that occurred after you click Generate CN in the R/A Return Authorization Entry window.
  • Added appropriate status messages during the posting process of AR batches.
  • Added AvaTax Transactions Report. This report displays posted or saved documents based on document type, range of document numbers, and range of dates.
  • Fixed the issue with tax calculation for transactions having both taxable and non-taxable items.

AvaTax for Sage 300 (2015 releases)

December 31, 2015

Release 6.20.108.00

  • Choose to send the UPC instead of the item code to dictate product taxability. By default, the item code is sent to AvaTax.
  • Integration with Avalara's certificate management system. Request and retrieve exemption certificates.
  • Added the Setup Assistant to aid setup and configuration for AvaTax. Option available in Sage Sales Tax Powered by Avalara > AvaTax Setup Assistant.
  • A self-provisioning feature lets new users create an AvaTax account and company with trial plan of 30 days without any assistance. On the Avalara Setup Assistant page, click Sign up.
  • Added the Tax Profile Assistant to aid with nexusHoverTT.png setup and other settings for AvaTax.
  • Fixed an issue where the batch tax calculation utility failed to calculate tax for a batch with individually printed invoices.
  • Fixed an issue where the discount at the header-level was added to the credit note amount during the tax calculation.
  • Applicable for Sage 300 2014 Product update 3 only: The Business Registration Number, also known as the Business Identification Number (BIN), is available in this Product Update only. AvaTax for Sage 300 now sends the BIN along with the currency code in the transaction details.

November 30, 2015

Release 6.20.107.00

  • Enhanced batch utility for tax calculation. You can now recalculate tax for AR batches and update corrupted/deleted documents.
  • Fixed an issue with tax only credits where the tax amount was updated but the order amount remained unchanged after the tax calculation. This issue was noted when the miscellaneous charge STADJ was used in a credit memo.
  • Fixed the errors generated during the posting of AR Batch
  • Fixed the foreign key error generated while posting credit memos in the Sales module
  • Fixed the issue where the currency code was appearing in non-related fields in an invoice

October 28, 2015

Release 6.20.106.00

  • Fixed an issue where the header level discounts were not considered while calculating tax in the OE module
  • Fixed an issue with the tax calculation based on the item quantity for Orders
  • Invoices deleted in the AR module will now also be deleted from AvaTax

October 8, 2015

Release 6.12.105.00

  • Fixed the issue that occurred while posting transactions when the tax calculation option was disabled
  • Fixed the "User can not be authenticated", "Doc status invalid", and "HTTP" errors that occurred during posting of transactions  
  • Fixed the connectivity issue that created duplicate documents resulting in an error during posting

September 15, 2015

Release 6.20.105.00

  • Fixed the issue that occurred while posting transactions when the tax calculation option was disabled
  • Fixed the "User can not be authenticated", "Doc status invalid", and "HTTP" errors that occurred during posting of transactions
  • Fixed the connectivity issue that created duplicate documents resulting in an error during posting

July 7, 2015

Release 6.12.104.00

  • Fixed an issue with the quantity of partially shipped orders. You are now able to zero the remaining quantity of partially shipped orders and continue with order processing
  • Fixed an issue with the printing of invoices after posting multiple transactions
  • Fixed an issue with the activation of AvaTax for new installations
  • Fixed an issue where uncommitted documents were posted to AvaTax
  • Fixed the "Invalid input. This user is not authorized to approve credit." error generated during overriding a credit limit. Only single authorization required for posting an invoice

June 16, 2015

Release 6.20.104.00

  • Fixed the latency issue experienced when processing multiple recurring charge invoices in accounts receivable
  • Fixed an issue with the quantity of partially shipped orders. You are now able to zero the remaining quantity of partially shipped orders and continue with order processing.
  • Fixed an issue where a blank location code for non-stock items generated an address error during tax calculation
  • Fixed an issue with the AR Batch Processing utility. An AR batch with errors in invoices with recurring charges, slowed down the entire process.
  • Fixed an issue with the printing of invoices after posting multiple transactions
  • Fixed an issue with the activation of AvaTax for new installations
  • Fixed an issue where uncommitted documents were posted to AvaTax

April 17, 2015

Release 6.12.103.00

  • Fixed an issue where the invoice data failed to export details in the selected file format after the installation of AvaTax for Sage 300.
  • Fixed an issue with blank ship-to address codes. Now, for transactions with a blank ship-to address code, the bill-to address code and the corresponding entity/use code is used.
  • You can now upgrade from any previous version to this version
  • Added tax class 2 for better exemption handling capability. Only customers with a Registration number and Tax class 2 will be exempted.
  • Fixed an issue with the AR Batch Processing utility. An AR batch with error in invoices with recurring charges, slowed down the entire batch process.

April 6, 2015

Release 6.20.103.00

  • Fixed an issue where the invoice data failed to export details in the selected file format. This issue was noted after the installation of AvaTax for Sage 300.
  • Fixed an issue with blank ship-to address codes. Now, for transactions with a blank ship-to address code, the bill-to address code and the corresponding entity/use code is used.
  • Upgrade from any previous version to this version
  • Added tax class 2 for better exemption handling capability. Only customers with a Registration number and Tax class 2 are exempted
  • Fixed an issue with the AR Batch Processing utility. An AR batch with error in invoices with recurring charges, slowed down the entire batch process

AvaTax for Sage 300 (2014 releases)

November 28, 2014

Release 6.20.102.00

  • Send the item's General Ledger account number along with the item's other information to AvaTax
  • Apply entity/use codesHoverTT.png at the line level in transactions
  • Use the built-in Sage 300 Job Costing utility to calculate taxes on O/E and A/R transactions
  • Validate a transaction's address before you calculate tax on it
  • Choose your own AvaTax company code in Sage 300. By default, the name of the company that is logged into Sage 300 is displayed.
  • Tax-only adjustments in the Sage 300 O/E Credit/Debit Note Entry utility
  • Disable warning messages in AvaTax
  • Use the built-in Sage 300 AR Invoice Batch List utility to post AR transactions to AvaTax
  • Use the built-in Sage 300 R/A Return Authorization Entry utility to calculate tax on return authorizations
  • Use the built-in Sage 300 O/E Order Entry utility to calculate tax on partial shipments
  • Use the tax calculation date instead of the document date to calculate taxes in the Sage 300 O/E Credit/Debit Note utility and Sage 300 AR Credit/Debit Note Entry utility

October 21, 2014

Release 6.12.102.00

  • Now you can send the item's GL account number along with the item's other information to AvaTax.
  • Now you can apply entity/use codesHoverTT.png even at the line level in transactions.
  • Now you can use the built-in Sage 300 Job Costing utility to calculate taxes on O/E and A/R transactions.
  • Now you can validate a transaction's address before you calculate tax on it.
  • Now you choose your own AvaTax company code in Sage 300. By default, the name of the company that is logged into Sage 300 is displayed.
  • Now you can do tax-only adjustments in the Sage 300 O/E Credit/Debit Note Entry utility.
  • Now you can disable warning messages in AvaTax.
  • Now you can use the built-in Sage 300 AR Invoice Batch List utility to post AR transactions to AvaTax.
  • Now you can use the built-in Sage 300 R/A Return Authorization Entry utility to calculate tax on return authorizations.
  • Now you can use the built-in Sage 300 O/E Order Entry utility to calculate tax on partial shipments.
  • Now you can use the tax calculation date instead of the document date to calculate taxes in the Sage 300 O/E Credit/Debit Note utility and Sage 300 AR Credit/Debit Note Entry utility.

July 10, 2014

Release 6.20.101.00

  • Validate addresses in Sage 300 utilities
  • Calculate sales tax in Sage 300 modules

June 30, 2014

Release 6.12.101.0

  • The new Address ValidationHoverTT.png tab on the AvaTax Options dialog box is simpler and more intuitive than before.
  • Now you can send tax-calculation requests to AvaTax directly from Sage 300 dialog boxes instead of through AvaTax dialog boxes.
  • Now you can map tax codes in all Sage 300 transaction dialog boxes.
  • Now you can map entity/use codes in all Sage 300 transaction dialog boxes.
  • Now you can map freight and miscellaneous tax codes in all Sage 300 transaction dialog boxes.
  • Now you can use the transaction posting date instead of the transaction date when you post transactions to AvaTax.

May 20, 2014

Release 5.63.002.01

Avalara release number: 5.63.002.01
Compatible with:

Sage 300 ERP 5.6

Release date: May 20, 2014
Files included: Sage Sales Tax Powered by Avalara for Sage 300 ERP Version 5.63.002.01.exe

What's new

  • AvaTax AR Invoice Entry module tax calculation date. Now you can use a menu item in the AvaTax AR Invoice Entry module to enter a tax calculation date.

The menu on the screen above open the following dialog box to let you change the tax calculation date.

What's improved

  • Access rights for non-admin users. Now non-admin users can use AvaTax AR invoice entry to add and save transactions.

AvaTax for Sage 300 (2013 releases)

March 21, 2013

Release 6.1.0.1.0.03

Product:

Sage 300 ERP 2012 Sales Tax, Powered by AvaTax

Release Number:

6.1.0.1.0.03

Release Date:

21-03-2013 (DD-MM-YYYY)

Customer Support:

For more information or support, please visit www.avalara.com or email at support@avalara.com


Introduction

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

This is General Hot-fix Release.

Installation

All users must Log off from Sage 300 ERP 2012 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 2012 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
    • TV61A folder is copied to the Sage 300 ERP 2012 application directory (on the path as per user’s selection during installation)
  • TV61AENG.chm file is copied to the help folder of Sage 300 ERP 2012 folder (on the path as per user’s selection during installation)
  1. For integration of AvaTax Portal on Sage 300 ERP 2012, refer guide located at following path

“%Sage 300 ERP 2012 application directory%\TV61A\AvaTax_Portal_Integration_61A\Read Me.txt”

Note:   

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

Manifest

This release consists of the following items:

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

Version Compatibility

This version is compatible with

  • Sage 300 ERP 2012  6.1A Editions (Required Modules: SM, GL, AR, IC, and OE)
  • Database: MS SQL 2005– supported and tested, MS SQL 2008 - supported, Pervasive PSQL version 10.3 – supported
  • This Hot-fix 6.1.0.1.0.03 is compatible with 6.1.0.1.0.01

Minimum System Requirements

Issues Fixed in 6.1.0.1.0.03

  • Trac Ticket #1252- Sage 300 ERP 6.1.0.1.0.02 - Non-AvaTax Document not posting in AR Invoice Batch
  • Ticket #36040- Non-avatax document exists in a batch being processed via the avatax screens the batch will not post

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.

January 23, 2013

Release 5.6.3.1.0.02

Product Release Information

Product:

Sage 300 ERP 2012 Sales Tax, Powered by AvaTax

Release Number:

5.6.3.1.0.02

Release Date:

23-1-2013 (DD-MM-YYYY)

Customer Support:

For more information or support, please visit www.avalara.com or email at support@avalara.com

 

 

 

 

 

 

 

 

 

 

Introduction

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

Installation

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)

Note:   

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

Manifest

This release consists of the following items:

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

Version Compatibility

This version is compatible with

  • All Sage 300 ERP 5.6A 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)

Networking:

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 - 5.6.3.1.0.02

  • 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 5.6
  • 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.

AvaTax for Sage 300 (2011 releases)

April 11, 2011

Release 5.6.2.1.0.03

Product:

Sage Accpac Sales Tax, Powered by AvaTax

Release Number:

5.6.2.1.0.03

Release Date:

11-04-2011 (DD-MM-YYYY)

Customer Support:

For more information or support, please visit www.avalara.com or email at support@avalara.com

Introduction

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

What's New?                  

  • Ticket #20340:- Accpac Connector - Win7 Compatability
  • InstallShield program enhancement, assigning necessary folder security to “Install Directory:\Program Files\Avalara\ Avalara Accpac Connector\”
  • InstallShield program enhancement: user defined path
  • ROTO.dat file update
  • AvaTax Option program update for reading path of Avalara.AvaTax.Adapter.dll file during enable logging feature
  • Ticket #18452:- AvaCert Phase 3: Create Accpac "stand-alone" connector for AvaCert Service
  • Ticket #20014: - Add Item Group Tax Code mapping functionality                                                                                   
  • This Build is supporting Sage Accpac ERP 5.6 with Product Update 2
  • This Build is using AvaTax Adapter 5.8.1.1

Installation        

All users must Log off from Sage Accpac 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 Accpac 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 Accpac ERP application directory (on the path as per user’s selection during installation)
  • TV60AENG.chm file is copied to the help folder of Sage Accpac folder (on the path as per user’s selection during installation)        

Note:   

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

Manifest

This release consists of the following items:

·        Release notes (this file)

·        Executable setup file – ‘Sage Accpac Sales Tax Powered by AvaTax Version 5.6.2.1.0.03.exe’

Version Compatibility

This version is compatible with

·        All Sage Accpac 5.6A Editions with Product Update 2 (Required Modules: SM, GL, AR, IC, and OE)

·        Database: MS SQL 2005 – supported and tested, Pervasive.sql (9.6 and 10.2) – supported

Minimum System Requirements –

System Processor:

Server: Intel Dual CPU Core 2/ Quad Core; 2 GB RAM, Client: Intel Core 2 Duo;

System Memory:

Server: 2 GB RAM, Client: 1 GB RAM (if XP) 2 GB RAM (if Vista)

Free Disk Space:

1 GB

Operating System:

x86 Windows 2003 Server, x86/x64 Windows Vista, Windows XP

Networking:

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 5.6.2.1.0.03 (This Release)

  • Ticket #5596   - Incorrect Document type passed during Get Tax Call for Credit note
  • Ticket #19928 - Accpac - General Housekeeping
  • Ticket #20043 - Multiple company access issues in Accpac
  • Ticket #20343 - Unprivileged Network Users Unable to Access Avatax
  • Ticket #22452 - Popup with "The User or account could not be authenticated” Run-time error in case of address validation.
  • Ticket #21782 -TESTING ONLY - AvaCert Phase 3: Create Accpac connector for AvaTax Certs "stand-alone"
  • Ticket #17850 – Required Sage ACCPAC 5.6 Connector which supports Product update one for opening AvaTax Transaction UIs.

Known Issues and Workarounds ( If any)

·        Ticket #15229 - Invalid DocCode passes to request in case of ARInvoice after firing GetTax only.

  • Ticket  #16677 - DLL issue in case previous version of  DLL is already registered.

·         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 error thrown from AvaTax during commits call (for already existing Transactions at AvaTax Server)

·         Ticket #6399 - Multi User access to be restricted for Reconciliation UI

  • Issue #15229 - Invalid DocCode passes to request in case of ARInvoice after firing GetTax only.

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.

·        Connector is not supporting Web-deployment

AvaTax for Sage 300 (2010 releases) 

October 1, 2010

Release 5.6.1.1.0.02 

Product Release Information

Product:

Sage Accpac Sales Tax, Powered by AvaTax

Release Number:

5.6.1.1.0.02

Release Date:

01-10-2010 (DD-MM-YYYY)

Customer Support:

For more information or support, please visit www.avalara.com or email at support@avalara.com

Introduction

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

What's New?                  

  •  AvaCert Phase I : This functionality include following features
    1. AvaCert : Create Customer record into AvaCert
    2. AvaCert : Initiate Exception Certificate request workflow
    3. AvaCert : Provide web link for AvaCert portal.
  • This Build is supporting Sage Accpac ERP 5.6 with Product Update 1
  • This Build is using AvaTax Adapter 5.8.1.1
  • Batch Address Validation UI; export data to CSV file.

Installation   

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

There is two level of installation.

1.   After the install-Shield’s installation a new folder is created ‘C:\Program Files\Avalara\ Avalara Accpac Connector\’

2.   Following files are created at the specific locations

a.   11 files in the path C:\Program Files\Avalara\AvaTax Connect Adapter\Bin\

b.   TV56A folder is copied to the Sage Accpac folder (as mentioned in the system registry)

c.   TV56AENG.chm file is copied to the help folder of Sage Accpac folder (as mentioned in the system registry)       

Note:   

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

Manifest

This release consists of the following items:

·        Release notes (this file)

·        Executable setup file – ‘Sage Accpac Sales Tax Powered by AvaTax Version 5.6.1.1.0.02.exe’

Version Compatibility

This version is compatible with

·        All Sage Accpac 5.6A Editions with Product Update 1 (Required Modules: SM, GL, AR, IC, and OE)

·        Database: MS SQL 2005 – supported and tested, Pervasive.sql (9.6 and 10.2) – supported

Minimum System Requirements –

System Processor:

Server: Intel Dual CPU Core 2/ Quad Core; 2 GB RAM, Client: Intel Core 2 Duo;

System Memory:

Server: 2 GB RAM, Client: 1 GB RAM (if XP) 2 GB RAM (if Vista)

Free Disk Space:

1 GB

Operating System:

x86 Windows 2003 Server, x86/x64 Windows Vista, Windows XP

Networking:

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 5.6.1.1.0.02  (This Release)

  • Ticket  #18257  - ACCPAC 5.6 Product Update One blocking issue when AVATAX Group Code is not used
  • Ticket  #17540 ACCPAC 5.6 - Avatax Invoicing Screens pulling up native ACCPAC windows
  • Ticket  #17710 AvaCert Phase I integration - Placeholder issue for Phase I integration of vCert
  • Ticket #18000 Invoices that contain lines that are under 0.10 create a Tax Base imbalance error and does not allow full processing

Issues Fixed In 5.6.1.1.0.01

  • Ticket #17850 – Required Sage ACCPAC 5.6 Connector which supports Product update one for opening AvaTax Transaction UIs.

Issues Fixed In 5.6.0.1.0.02

·        Ticket #17154: ACCPAC- Country code not being passed on AR Batch invoice

·        Ticket #17037: Client/Server scenario - Unsuccessful test connection at client site and popup with error code.

·        Ticket #17083: ACCPAC 5.6 - Error message displayed in Batch Tax calc UI

Known Issues and Workarounds ( If any)

·        Ticket #15229 - Invalid DocCode passes to request in case of ARInvoice after firing GetTax only.

·         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 error thrown from AvaTax during commits call (for already existing Transactions at AvaTax Server)

·         Ticket #6399 - Multi User access to be restricted for Reconciliation UI

  • Issue #15229 - Invalid DocCode passes to request in case of ARInvoice after firing GetTax only.

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.

·        Connector is not supporting Web-deployment

  • Was this article helpful?