I agree with division/multiplication issue. Or maybe just simply an assumption that VAT is always there and sanity checks on the systems just won’t allow 0 (or negative number) as a tax percentage.
I meant that in general even ‘official’ systems have stupid bugs or practices just because things have been in a certain way for long time. Years ago I wrote a small invoicing program which had obviously manage VAT and it would’ve been a simple mistake to assume that VAT (or any tax percentage) is just a whole number since that’s what I’ve ever seen before. That particular piece of software is well obsolete now, but that would’ve managed the decimals since it handled all the numbers in the same way just to keep things simple and monetary values obviously need decimals. However, without any verification it wouldn’t been a crazy assumption to store tax percentages as a two digit integer everywhere.
I agree with division/multiplication issue. Or maybe just simply an assumption that VAT is always there and sanity checks on the systems just won’t allow 0 (or negative number) as a tax percentage.
I meant that in general even ‘official’ systems have stupid bugs or practices just because things have been in a certain way for long time. Years ago I wrote a small invoicing program which had obviously manage VAT and it would’ve been a simple mistake to assume that VAT (or any tax percentage) is just a whole number since that’s what I’ve ever seen before. That particular piece of software is well obsolete now, but that would’ve managed the decimals since it handled all the numbers in the same way just to keep things simple and monetary values obviously need decimals. However, without any verification it wouldn’t been a crazy assumption to store tax percentages as a two digit integer everywhere.