Sold to ISK account (“Avyttrad till investeringssparkonto” (fält 573))
https://bricknode.atlassian.net/browse/TRAFM-164
When a sell has been made to an Investment savings account (ISK) it should be reported to SKV in the following reports KU21?? (ska den här verkligen vara med här), KU32 and KU40.
This is supported in the use of internal transfers in BFS and the tax application fetches these technical sells and add the Sold to ISK value to these reports both in Excel and XML.
First you need to add the transaction type for the technical sell used in BFS, normally Default_Trade_Sell_Technical, to the Transaction type section of the export to Excel popup.
Then you need to add which ISK acocunt types you have in your BFS instance. This is made in the Account types for ISK section of the export to Excel popup.
In the Excel file, the value is populated in column F, called “ReportSoldToISK”. TRUE is reported if this sell in question was made to an ISK account and FALSE if not.
In the XML the value is populated in field number 573, called “Avyttrad till investeringssparkonto”.
TIN number and country code TIN
https://bricknode.atlassian.net/browse/TRAFM-172
Since release 2.38 you can enter TINs for end customers in BFS. To do this you go to the details page of a customer and edit the TIN section.
If there are a TIN value for the customer in BFS, the tax application will fetch it and use it in the KU reports. These values (TIN number and country code TIN) is added to all KU reports except KU30.
In the excel file the values are populated in the two columns called “ReportTIN” and “ReportCountryCodeTIN”.
When you extract the XML file the values will end up in the fields with number 252 (TIN) and 076 (LandskodTIN).
Warn if negative standard income (schablonintäkt) in KU30
https://bricknode.atlassian.net/browse/TRAFM-170
If the standard income (Schablonintäkt) is negative when exporting the excel file for the KU30, you will get a warning and information about which account it is. At this point you can download the file and fix the issue in the excel file before you upload it again to create the XML file, or you can cancel and go to BFS and correct the situation on the account and then export a new Excel again.
Rounding of Loss in KU40 (profit/loss)
The rounding ot profits and loss should be made in different way so that it is benificial for the end customer (not pay to much tax). Before the tax application rounded profits and loss in the same way but this is now fixed according to SKV regulations (loss is rounded up and profits down).
https://bricknode.atlassian.net/browse/TRAFM-163
ISIN not a required field in KU31
Since the ISIN field is not required in the KU31 report, the tax application now removes that field if there are no ISIN on the instrument in question. Before the app required this and you had to make a lot of manual work to get it out in the excel and remove it from xml. If an ISIN doesnt exist on the instrument there will be no ISIN filed in the xml file that is uploaded to SKV.
https://bricknode.atlassian.net/browse/TRAFM-157
Field type for “schablonintäkt” of KU30 changed
The value of “schablonintäkt” has now the correct field type according to SKV regulations. Before it was incorrectly a 12 digit large field, this is now changed to a 10 digit field.
https://bricknode.atlassian.net/browse/TRAFM-169
New schema for 2021
The app now supports the XML schema for 2021 tax reporting.