Tax Checkbox On POS

Sounds like you may have some customers that are marked as tax exempt.

Glenn Adams Tiber Creek C> I am experiencing an issue with the tax status of items during checkout. The

My client doesn't sell by customer or gather customer data at the register. These registers are being used as "tills" in a high traffic environment. There are a couple of customers in the database as a test but these are not, as far as I know, associated with any sales.

Dan

"Glenn Adams [MVP - Retail Mgmt]" wrote:

I have some more interesting information. The issue is related to the field Taxable that defined for item records. That field appears to determine whether or not the item is taxable (easy guess :) ) and that field is used by the POS to set the Tax checkbox on the transaction screen.

The big question for me is what affects this field? I cannot find any option or setting on the add/edit item dialog in SO Manager that directly affects this field. I have determined that if I edit an item in SOM that has this field set to 0, but there is a tax assigned to it (TaxID0), and I save the item, this field returns to 1. I do not need to make any changes to the item, just view it in the edit dialog.

So, there is some process my folks are performing that is changing the setting of this field. It could be the inventory management software on our portable scanners and I am asking my vendor about this.

Is there something else going on that I'm not seeing? For example, if a cashier clears the checkbox for a transaction item does the system persist this? I haven't experimented with this but I don't think that's happening.

What other features of the system touch this field? I'd like to know so I can be aware and maybe set up some monitoring code to track this.

As of this last evening I ran an update query in SOA to reset the TaxID and Taxable for all items in the DB. I'm thinking I'll put a trigger on the DB to watch this change and see if I can track what's going on. Unless someone has answers :).

Dan

"dwtalso" wrote:

There is an option you can set in SO Manger regarding how taxes are assigned. It's either by Item or by customer.

When it is set to "By Customer", the item properties screen will change such that where you currently see a combo box where you can select the Item Tax you would instead see a check box that sets the Taxable field.

Maybe you have changed the tax assignment field at some point, but it's more likely that you either imported items and the Taxable field was not accounted for or you assigned Item tax IDs using SQL code (that's why you see so many warnings about applying updates).

Honestly, I thought that the taxable field was ignored when the tax option was set to "By Item", but it looks like you have discovered that it is not. What version are you running?

Glenn Adams Tiber Creek C> I have some more interesting information. The issue is related to the field

I have verified that I have the configuration set to "By Item".

I have also created an update trigger in the database to audit those fields. If they change I should be able to determine the events that surround the change.

However, you bring up an excellent point with respect to importing. I built this database by writing code against wholeseller spreadsheets (the DB currently has 32k+ items and no one volunteered to enter all of 'em by hand...including me) and I'm looking at the code and I didn't originally set the Taxable field. I did go back and update that field later on.

I've had to do a couple of smaller imports along the way to finish out the database. I'm willing to admit that I cannot account for performing an update of Taxable for all of those runs. It's very possible that *I* created the issue and we just caught it now.

That means my audits will show that nothing is changing the field because no more imports are occurring to this system.

I h> There is an option you can set in SO Manger regarding how taxes are