From Fishbowl
Jump to navigation Jump to search

Icon.Avalara.png The Avalara module, located in the Integrations group, is an add-on module that can be installed from the Icon.Plugin.png Plugin module. After installing the plugin, a new module is added that integrates with Avalara AvaTax. Avalara takes the hassle out of managing the many complex taxing laws and automatically returns a total tax amount based on the product, price, and location.


The documentation on this page is for the most recent version of the Icon.Avalara.png Avalara plugin. To get the most recent version, Update Fishbowl.

  1. In any Fishbowl Client, open the Icon.Plugin.png Plugin module, located in the Integrations group.
  2. Select the Icon.Avalara.png Avalara plugin and click Install.
  3. Completely close all Fishbowl Clients.
  4. Exit the Fishbowl Server by right-clicking the Fishbowl Server tray icon and selecting Exit.
  5. After re-opening the Fishbowl Server, the admin user can access the Icon.Avalara.png Avalara module from any Fishbowl Client by opening the Integrations group.
  6. To grant access to additional users, assign the Avalara-View access right to the appropriate groups in the Icon.User Group.png User Group module


Avalara Connect.png
  1. In the Icon.Avalara.png Avalara module, enter the username and password used to log into Avalara.
  2. Alternatively, enter the Account Number and License Key which can be obtained by logging in at https://admin.avalara.com/. For more information, click here.
  3. The other fields are Avalara options, such as the ability to mark transactions as Pending or Committed.
  4. Click the Connect button in the Icon.Avalara.png Avalara module to verify that the connection is valid and then click Save.


  1. All products must be marked as taxable in Fishbowl or they will not be sent to Avalara. Non-taxable products should have a non-taxable code assigned and the taxable box checked in Fishbowl.
  2. The tax code for a product can be set on the Custom tab of the Icon.Product.png Product module.
  3. To get a tax estimate, click the Avalara Button.png Avalara button on the Sales Order module toolbar.
    Avalara Tax Estimate.png
    • If any changes are made to the order (modified quantity, partial shipment, address change, etc.), the estimated amount may vary from the actual amount calculated during shipping.
    • In some cases, local laws and other complexities may also result in the actual tax being different from the estimate.
    • The tax estimate is stored on the Details tab of the Icon.Sales Order.png Sales Order module.
    • The Order Estimated Tax column can also be enabled on the Sales Order report.
      Estimated Tax on report.png
    • The order total will not include tax until the order has been shipped.
  4. Once an order has shipped, a line item will be added to the order with the actual tax amount.
    Avalara Actual Amount.png
    • Below is an example of the data that is stored in Avalara when an order ships.
      AvaTax details.png

Avalara will validate the Ship To address when requesting a tax estimate and when the order is shipped. An address can also be validated manually by clicking the Validate Address Icon Button.png Validate Address button above the Ship To address.


When using Avalara, some orders need to be processed in a specific way to ensure that the correct calculations are made. Below are some notes that apply when using the Avalara integration.

  • USA - Avalara is not configured for countries outside of the United States.
  • Taxable vs tax codes - All products must be marked as taxable in Fishbowl or they will not be sent to Avalara. Non-taxable products should have a non-taxable code assigned and the taxable box checked in Fishbowl.
  • Shipping - If an order doesn't have anything to ship, a non-inventory item should be added to the order so that the order will be routed through the shipping process.
  • Dropship - Dropship items should be received before shipping the last item on the order. A warning will be displayed when trying to ship an order with unreceived dropship items.
  • Duplicate - Duplicating a fulfilled sales order will also copy the Avalara line item tax to the new order. This item should be removed from the new order so that the tax on the new order is recalculated correctly.
  • Returns - The Receive Button.png Receive button at the top of the Icon.Receiving.png Receiving module should be used to receive all credit return items. The Receive button on the component toolbar to the right should only be used if there will be an accounting export after receiving each line item.
  • Checkout - Orders with the Avatax tax item cannot be processed in Icon.Fishbowl Checkout.png Fishbowl Checkout and will display an error.
  • Miscellaneous items - A miscellaneous sale or credit should only be used if it has a $0 amount, because miscellaneous items do not have tax codes. Instead, new products should be created and associated with the correct tax codes. Alternatively, non-inventory items can be associated with the correct tax codes and the line item descriptions could be edited on each sales order as needed.
  • Service - Service items must be combined with an item that will go through the shipping process. If service items are also combined with credit return or dropship items, Quick Fulfill must be used to fulfill the rest of the order first, then fulfill the credit return or dropship items. An alternative would be to create these as non-inventory items instead.
  • Return and Dropship - Credit Return items and Dropship items should not be combined with Service items. If they are, Quick Fulfill must be used to fulfill the rest of the order and then fulfill the Return. Use the Receiving Ref # to enter a unique number to prevent tax calculation issues.

Release Notes

Released on 8/13/2020

  • There is no longer a warning displayed when fulfilling sale items before dropship as that is no longer required to process the dropship lines.
  • When doing dropship or credit return items, use the reference # field in receiving to set the invoice number displayed in Avalara. This should not be the exact sales order number but could be a variation. (Ex. 20005-1) This field must be utilized to prevent tax duplication issues.
  • Customers can choose to integrate with a sandbox avalara account for testing
  • Customers can choose whether to send the Customer Name or Customer Account Number to the CustomerCode in Avalara
  • Customers can choose to send the QB class on the sales order as the Avalara LocationCode
  • Customers can now choose to include or exclude the order number prefix

Released on 2/9/2017

  • Issue: Products with a number that is greater than 50 characters in length causes an error and doesn't display a clear error message.
  • Resolution: Error message from Avalara is now passed through to Fishbowl.
  • Issue: An error occurs when syncing with Avalara via the estimated tax button if the location group on the order does not have a default address in the company module.
  • Resolution: Estimated tax now displays a message informing the user that an address needs to be entered before estimated tax can be calculated.
  • Issue: Multiple shipments against a single sales order update Avalara with the latest transaction only when the "commit transactions" option is not enabled.
  • Resolution: Multi shipment orders now process each shipment correctly.

Released on 10/13/2016

  • Issue: Validating an address frequently fails when fields contain any additional data like an ATTENTION: listing.
  • Resolution: Rather than a direct fail, Fishbowl now attempts a secondary validate using City/State/Zip.

Released on 6/9/2016

  • Avalara AvaTax integration plugin allows for address validation and item based taxing