Compound Tax

Yes, it is in my list of to-dos.

Any news on tax tables support for various countries?

As for us in Canada each province have it's own tax tables, which, like mentionned in the main issue above, is calculated with the total cost of a product taxed federally.

So STORM should track the shipping address region to be able to properly apply the proper tax rate.

I'm throwing in my support for this feature, definitely a must have for us Canadian users.

Yes - it is on the list of things to do, and i'm also willing to look at patches that cover this issue. I do realise this is needed for a fair few (mainly Canadian?) users.

However, i'll state that I wouldn't use this feature, so it won't be as high priority as some of the other bits that impact me directly.

Alongside compound tax, I think it will be best to define default tax percentages globally for Storm rather than in the specific modules. This affects Invoices and Expenses -> and hence changing component to Storm.module.

Please could any users looking for compound tax functionality have a look at http://storm.beta-web.co.uk/node/335. This is a short questionaire aiming to get appropriate defaults.

Thanks.

not that i'm interested in compound tax, nor i understand what that exactly is, but i'm getting Access denied, so outhers might have the same problem wit checking it out.

Thanks for pointing that out - it should work now.

Assigning to self - I'm in progress with this and it will be in the next stable release.

Any idea why I can't changed the tax options? From Administer -> storm -> storm under "taxation defaults" I have Tax1 and Tax2. I change changed the options and click save, and get "the configuration options have been saved". But they are not - they just go back to the previous values ??

I can't find where this is maintained. Is it in the database or a config file ?

Some parts of the compound tax system are not working at the moment - perhaps i've missed a good shortcut somewhere, but it has been a fairly major change across the whole of Storm - so please bear with me whilst this is sorted out. I'll post here when its in a state that can be tested effectively.

Re the problem you posted - do you mean the values on the admin settings form default back to your previous values, or the values on the node add forms? If the first, there is a problem, if the second, this is 'in progress'.

For those who do want to test this out - the expenses section is up and running using it, with the caveat that although 'Tax 1' and 'Tax 2' will eventually be replaced by the variables set in the admin settings, i'll do this bit last as it really only is a display issue, and makes debugging a lot easier to have the names set.

The node edit forms have become a little more crowded - for this i'm thinking of putting an additional setting in which can toggle the viewing of one or both of the tax settings fields - i.e. if you don't use tax ever, you would be able to set the defaults to 'do not apply tax', not view the fields on the node edit form, and every node would simply not use tax. If you only use one tax, you would be able to set the defaults then only view the first tax on the node edit form.

Invoices now support compound tax too, meaning that this is done apart from the following known issues:
- 'Display tax fields' settings
- View html invoice - table alignment error
- Pdf invoice - no support yet

Magnity,

Sorry I didn't reply for so long.

| " .. do you mean the values on the admin settings form default back to your previous values, or the values on the node add forms? "

I meant the first. I can't change the values under "taxation defaults" at all. That is, I can change them on the form, but when it reloads after an apparently successful it is back to original values (trying to change both to "Do not apply", but reverts back to "Apply").

Is it just me that has this behavior?

I have grepped through code and checked a few table in the database, but I haven't done drupal development, so not sure where to look for issue.

Thanks for the report - yes this is a bug. A patch has been submitted in #535336: Taxation defaults don't get saved which solves it.

I believe this is now fixed.

This change has touched a number of the areas of Storm though, so there may be some bugs or even inconsistencies that need to be ironed out - if you spot any, please either reopen this issue, or (preferably) open a new issue so that we can track each one.

Also, I appreciate that many people will not use double taxes. Feel free to suggest ways of ensuring that it doesn't get in the way for you.