Skip to main content
Avalara Help Center

Avalara AvaTax for Microsoft Dynamics AX 2012 R3 CU8 Hotfix Release Notes

Read the release notes to learn about the latest changes, improvements, and fixes to AvaTax for Microsoft Dynamics AX 2012. For more detailed information, see the AvaTax for Microsoft Dynamics AX 2012 guide.

June 20, 2017

Updates and improvements in AvaTax for Microsoft Dynamics AX 2012 release 6.3.1000.309.02.10:

  • Code change document
  • Fixed the "Tax Document could not be found" error that occurred while posting project invoices  

June 20, 2017

Updates and improvements in AvaTax for Microsoft Dynamics AX 2012 release 6.3.1000.309.05.04:

  • Code change document
  • Fixed an issue where consumer use tax was calculating incorrectly  

April 6, 2017

  • Avalara release 6.3.1000.309.05.03
  • Code change document
  • Fixed an issue where the calculation of sales tax was incorrect for a project with item requirements 

March 2, 2017

  • Avalara release 6.3.1000.309.03.04
  • Code change document
  • Fixed an issue where the project transactions in AvaTax didn't match the transactions in Microsoft Dynamics AX 2012 after reconciling transactions

January 31, 2017

  • Avalara release 6.3.1000.309.02.09
  • Code change document
  • Fixed an issue where the number of transactions after posting a batch of sales orders didn't match in Microsoft Dynamics AX 2012 and AvaTax 
  • Fixed an error that occurred during the posting of a transaction in Microsoft Dynamics AX 2012 that set the Doc Status to Uncommitted to AvaTax

December 30, 2016

  • Avalara release 6.3.1000.309.05.02
  • Code change document
  • Fixed the issue where a posted project invoice without dimensions displayed the Doc Status as Uncommitted in AvaTax
  • Fixed an issue where the VAT number wasn't sent from Microsoft Dynamics AX 2012 to AvaTax for a project transaction 

December 26, 2016

  • Avalara release 6.3.1000.309.06.05
  • Code change document
  • Fixed an issue where the allocated miscellaneous charges for a purchase invoice had a negative amount

November 23, 2016

  • Avalara release 6.3.1000.309.06.04
  • Code change document
  • Fixed the "The tax document could not be found" error while posting project invoice proposals
  • Fixed the issue that occurred when posting AP invoices with purchase orders having allocated charges
  • Fixed the issue where the calculated sales tax was displayed as $0 in Microsoft Dynamics AX 2012. This issue occurred when a free-text invoice was created from a recurring invoice template.

October 25, 2016

  • Avalara release 6.3.1000.309.03.03
  • Code change document
  • Fixed the exception error that occurred while reconciling transactions
  • You can now map an Entity/Use code for a project

September 28, 2016

  • Avalara release 6.3.1000.309.06.03
  • Code change document
  • Fixed the issue where the invoice amount, listed in the Project Invoice Proposal, didn't include the tax amount.

September 16, 2016

  • Avalara release 6.3.1000.309.06.02
  • Code change document
  • Fixed the issue where in a previous integration release, when calculating consumer use tax for a purchase invoice, the use tax liability account was being debited and the inventory/use tax debit GL account was being credited. Now, the use tax liability account is credited and the inventory/use tax debit GL account is debited.
  • Fixed the issue where the delivery address, mentioned in the purchase order, wasn't used for calculating the consumer use tax for a vendor invoice created from the purchase order.

August 16, 2016

  • Avalara release 6.3.1000.309.06.01
  • Code change document
  • Fixed the "Unknown Country Name or Code GBR" error that occurred when a sales order was created and posted with GBR as the country code.

April 6, 2016

  • Avalara release 6.3.1000.309.02.07
  • Specific Code Change document
  • Fixed an issue with the process of posting invoices.

March 8, 2016

  • Avalara release 6.3.1000.309.03.02
  • Specific Code change document
  • Added a fall-back mechanism for assigning the warehouse or site address to a service order. The origin address passed from Microsoft Dynamics AX to AvaTax is selected in the following order based on availability:
    • Warehouse address
    • Site address
    • Company address

February 19, 2016

  • Avalara release 6.3.1000.309.03.01
  • Specific Code change document
  • Added fall-back mechanism for assigning the taxability code mapping in Projects Accounting. For an item, the tax codeHoverTT.png passed from Microsoft Dynamics AX to AvaTax is selected in the following chronological order based on availability:
    • Item
    • Item group
    • Project item

January 15, 2016

  • Avalara release 6.3.1000.309.02.06
  • Specific code change document
  • This hotfix is applicable only to Microsoft Dynamics AX 2012 6.3.1000.309.02.05.
  • Fixed the issue where a change in the customer address resulted in an inaccurate tax calculation for free text invoices.

November 5, 2015

July 28, 2015

  • Avalara release 6.3.1000.309.02.04
  • Code change document
  • Fixed an issue that occurred while posting multiple sales orders at a time.
  • Fixed an issue that occurred while posting return orders with negative quantity.

July 28, 2015

  • Avalara release 6.3.1000.309.02.03
  • Code change document
  • Fixed the following issues with validated addresses:
    • Update of validated address in customer records
    • Return of incorrect attention line
  • Fixed an issue where the addition of miscellaneous charges calculated the incorrect amount of sales tax.

May 22, 2015

  • Avalara release 6.3.1000.309.02.02
  • Code change document
  • Fixed the "Cannot edit a record in Header (AVA_Header)" error displayed while posting a sales order.

May 13, 2015

  • Avalara release 6.3.1000.309.02.01
  • Code change document
  • Fixed an issue where the Sales Total window failed to display the sales tax field.