Currently, a single VAT period (/31/201001210131 → 01.10.2020 to 31.01.2021) can be specified, and it is associated with a single set of VAT rates (/32/7.7).
We must plan for a change in VAT rates (e.g. imagine a switch from 7.7% to 8.2% between 2020 and 2021).
This could be encoded by using multiple pairs of /31/ and /32/ tags:
/31/201001201231 → 01.10.2020 to 31.12.2020
/32/7.7 → VAT rate 7.7%
/31/210101210131 → 01.01.2021 to 31.01.2021
/32/8.2 → VAT rate 8.2%
How about software which does not expect multiple /31/ and /32/ elements? Should this require a major version change of the Swico-String specification?
Currently, a single VAT period (
/31/201001210131→ 01.10.2020 to 31.01.2021) can be specified, and it is associated with a single set of VAT rates (/32/7.7).We must plan for a change in VAT rates (e.g. imagine a switch from 7.7% to 8.2% between 2020 and 2021).
This could be encoded by using multiple pairs of
/31/and/32/tags:/31/201001201231→ 01.10.2020 to 31.12.2020/32/7.7→ VAT rate 7.7%/31/210101210131→ 01.01.2021 to 31.01.2021/32/8.2→ VAT rate 8.2%How about software which does not expect multiple
/31/and/32/elements? Should this require a major version change of the Swico-String specification?