yet there is problem if you install them. the Kingdee must be installed before the f-secure.

if you install F-secure antivirus before the Kingdee k3, the K3 won't work, it may tells you there isn't enough privilege, or the intermediate layer couldn't be connected. this was caused by F-secure blocking the K3 excutable file: kdmain.exe while it tries connect to the server.

i had experienced in domain enviroment there is a f-secure server manage all client policy, and the finacial manager told me she had experienced same problem in stand alone install f-secure enviroment in her former company.

in order to solve this, if you had them already installed, remove the f-secure and reinstall it again, then there will be a pop up windows ask if you want to allow the kdmain.exe connect to network, select 'always allow'.
in domain enviroment where is a f-secure server exist, you may unable to remove f-secure even you login as administrator, it was caused by the server policy. reboot computer in safe mode should be able to remove the f-secure antivirus.
in stand-along install of f-secure, it is possible by configure f-secure firewall for them to work, simply add the kdmain.exe to trusted allow list.

the correct way to install them is the f-secure should always be installed at last.