Washington State Sales Tax for Ubercart

jhodgdon - April 21, 2009 - 16:09

This module calculates Washington State Sales Tax in Ubercart.

Tax is calculated based on the purchaser's shipping address (or billing address, for non-shippable purchases), and the tax rate is found via address lookup on the Washington State Department of Revenue's web site, so that it always uses the most recent tax rate information.

After installing this module in the normal way, you'll need to visit the config page, which you can find inside the Ubercart configuration menu (path: admin/store/settings/uc_tax_wa). You'll need to choose which product types and line items are taxable, at a minimum, in order to generate any taxes.

If you are using Ubercart 6.x-2.0-beta5 or a later version, and you enable the tax reporting module that is distributed with Ubercart, you will also be able to prepare a report that lists all the sales tax you collected, by tax jurisdiction, with the official jurisdiction codes and rates (which can change quarterly). You will need this information in order to file your Excise Tax reports.

More details on module configuration and the tax calculation can be found in the README.txt file in the module zip.

An older version of this module for Drupal 5.x / Ubercart 1.x is available for download at http://www.ubercart.org/contrib/8311. Although it calculates the tax correctly for shippable items, it does not generate the tax report by jurisdiction, because Ubercart 1.x does not currently have the infrastructure to save the jurisdiction and rate information (see http://drupal.org/node/359544). Using the Drupal 5.x version is not recommended if you need to collect sales tax in Washington State, because you will not have the information you need to file your state taxes.

This module was developed by Jennifer Hodgdon (jhodgdon) of Poplar ProductivityWare.

Please check the issue information in the sidebar to see if your question has already been addressed before contacting the module developer with questions. Thanks!

Also please ensure you are running the latest version of this module, as your issue may have already been fixed.