What is VAT on an invoice calculated - New VAT rate

[guccij]

Thanks for the additional help, guys.

Unfortunately as my Access is the 2007 version, the KB article makes little sense to me. There is no "View" menu, for example. I think I found my way around but as I couldn't be sure, I backed out.

Instead I have resolved not to change any orders received before today and carry on just with the 15% change.

I do wish that the people who run Actinic would remember that having created an out of the box ecommerce solution, any KB articles and other explanatory stuff needs to be written in simple terms as well.

It's not fair that community users should have to fill in the gaps.

[brucet]

Re. Access 2007, I apologise for the oversight. This morning was the first time I've used it, I had no idea it was so different.

The steps are to click 'Query Design' in the 'Create' ribbon; click 'Close'; right-click in the blank 'Queryx' window and select 'SQL View'. Then paste in the SQL and follow the rest of the Knowledge Base instructions.

I will get the article updated.

[brucet]

For Enterprise users with the SQL database option ONLY, we've just finished testing a version of the code that's compatible with MS SQL (as you can see it's been a more complicated job).

Please use this instead of the code in the Knowledge Base:

UPDATE OrderDetail
SET OrderDetail.sTax1OpaqueData =
CAST([TaxBands_1].[nBandID] AS VARCHAR(4)) + '=' + CAST(CAST(100*([TaxBands_1].[dBandRate]) AS INTEGER) AS VARCHAR(4)) + '=0=' + [TaxBands_1].[sBandName] + '='
FROM OrderDetail, TaxBands
INNER JOIN TaxBands AS TaxBands_1
ON TaxBands.nTaxID = TaxBands_1.nTaxID
WHERE (
(
((CAST([TaxBands].[nBandID] AS VARCHAR(4)) + '=' + CAST(CAST(100*([TaxBands].[dBandRate]) AS INTEGER) AS VARCHAR(4)) + '=0=' + [TaxBands].[sBandName] + '=') = CAST([sTax1OpaqueData] AS VARCHAR(50)))
OR
((CAST([TaxBands].[nBandID] AS VARCHAR(4)) + '=' + CAST(CAST(100*([TaxBands].[dBandRate]) AS INTEGER) AS VARCHAR(4)) + '.00=0=' + [TaxBands].[sBandName] + '=') = CAST([sTax1OpaqueData] AS VARCHAR(50)))
)
AND ((TaxBands.dBandRate)=17.5) AND ((TaxBands_1.dBandRate)=17.5) AND (([TaxBands].[bDefault])=1) AND (([TaxBands_1].[bDefault])=0));

Enterprise users with the Access database option can use the code in the Knowledge Base.

[pinbrook]

Thanks for the additional help, guys.

Unfortunately as my Access is the 2007 version, the KB article makes little sense to me. There is no "View" menu, for example. I think I found my way around but as I couldn't be sure, I backed out.

Instead I have resolved not to change any orders received before today and carry on just with the 15% change.

I do wish that the people who run Actinic would remember that having created an out of the box ecommerce solution, any KB articles and other explanatory stuff needs to be written in simple terms as well.

It's not fair that community users should have to fill in the gaps.

I wholeheartedly agree, there should be a patch to cover this, you cant have an out of the box solution and then expect people to run SQL queries using Access which they probably don't have.

Failing a patch, then maybe a send your snapshot in service for a nominal fee - as i agree actinic shouldn't have to bear the brunt of the cost of this ridiculous 2% change that is going to cost more for businesses to implement than the extra trade it is meant to encourage.

[brucet]

I totally agree that a patch would have been the best thing. Unfortunately fixing the issue with existing orders is a bit complicated, and would involve a fairly fundamental change to the way order lines are edited. It's also not the most obvious possible side-effect of changing the tax, so it was a few days before we identified it. There simply was not time to develop and fully test a patch to correct it - the risk was just too great.

We did consider providing a snapshot fix as a service. But if more than about 1% of our user base had requested it, we would have had difficulty meeting demand within the time frame. Our response to other support issues would definitely have suffered as a result.

The method we've provided is at least safe, and scaleable. But we will definitely look to produce something better before they change the tax back again. At least we all have a bit more notice of that date...

[Mike Hughes]

Bruce, that's fine but this has always been a problem with the way actinic treats existing orders. The same thing happens if you ever change your shipping costs or countries you deliver to, etc. An order should be fixed at the time it is created. Changes to the tax, shipping, delivery methods, etc should only affect new orders not ones that were accepted under different terms and conditions.

Mike

[pinbrook]

We did consider providing a snapshot fix as a service. But if more than about 1% of our user base had requested it, we would have had difficulty meeting demand within the time frame. Our response to other support issues would definitely have suffered as a result.

So what is the solution for users without Access?

And people with or without Access who are not confident to run the required fixes?

[Jan]

So what is the solution for users without Access?

And people with or without Access who are not confident to run the required fixes?

The other way to change the VAT rate is to enter a new tax rate at 15% and then manually change all of your products to use this. The solution Actinic have provided is a quicker way of doing it.

Regards,