I already asked this question in the past and yes there is a QA process, threats signatures are uploaded on a pre-release server which is:
ftp://dnl-test.kaspersky-labs.com/beta_updates/pre-release/After that they are checked for false alarms during some time and at the end they are finally pushed on public update servers.
Citation (aehrlich @ 20.04.2009 10:39)

OK, the statement about the strange behaviour ("update is not required") was my fault: there were two updates, 08:43 and 08:45 and the "update is not required" message concerned the second one, so no more mystics.
However, the stated fix time 20:30 GMT+3 (Moscow time) is 19:30 GMT+2, am I correct ;-)? And from the screenshots one could see that the false positive was still detected after update at 21:40 GMT+2, i.e. 2 hours later than the "stated fix time".
This QA process can explain why this false alarm has been fixed at 20:30 GMT+3 whereas the file was still detected later.
Citation (svsuser @ 20.04.2009 17:51)

Kaspersky smoked wmiprvse.exe off of 30 of my XP boxes. Now I too am wondering about this. In another month I am adding 200 new worsktations running new Point-Of-Sale software in our 53 offices. Since they will all be managed through Kaspersky, I am really concerned that this might happen again with much larger and far reaching results.
You can add your software in the exclusion list then you will be sure it can not be flagged as a threat by Kaspersky Anti-Virus.