We have an intermittent issue where the BN100 ends a dependent life insurance plan incorrectly. The BN100 report looks correct, but when you access BN32.3, there is a Stop Date that should not be there. The issue has proven impossible to duplicate in our test environments. Our working theory is that the BN100 is "holding" a legitimate Stop Date from a previous record and applying it to subsequent records--in code-speak, that the Stop Date field is being used as a temp filed and is not being initialized. Does this sound familiar to anyone?
