Sage 100

Sales Tax Based Upon Zip Code Although we know it is not optimal, we have an e-commerce based customer who uses Zip Codes in their Magento site for calculation of sales tax (Avalara $$$ to high for now). So importing orders options are bring tax in as something other than tax or use zip codes and still risk rounding errors but preserve Sage Sales Tax reporting functionality. We can pull rates used in Magento and load into Sage as Tax Codes and Schedules. I see a ZIP Cross Reference table that can be used to assign sales tax schedules by zip code, but in that case someone would have to setup all the schedules and then maintain the cross reference.. This would be much better for reporting purposes but nearly impossible to keep synchronized with the eCommerce site. Currently we are planning on the zip code = schedule route, but thought better to ""ask the experts"" to see how others have dealt with this...

Have they set up zip code cross references in their Sales Tax Schedule Maintenance? If they have I don't see what the problem would be other than the maintaining the information.

They have not. They are a wasteland in sales tax setup with a single county per state and editing orders as they come in in the detail..... You gotta love orphans

Sounds like an excellent opportunity to be adopted by someone like you.

So we got Georgia all counties electronically and a cross reference of the Georgia city/zip code/ county listing and will be slamming those together to load the tables and test. I assume the Zip XRef will assign tax schedules to customers in some auto magical way? AM I A FOOL for expecting magic from Sage?

Gary, have you tried pulling down a state table from www.taxrate.com. It is managed by Avalara and you can download tables quarterly. The table contains the state, county, and city rates as well as the state tax region identifier. It also contains a 5 digit zip code reference. It isn't perfect but it is a good start. You can use the data in spreadsheet to load multiple tables in 100. I have attached the table for Oklahoma as an example.