An aggressive auto-merge collapses two different residents who share a common name into one golden person, mixing their benefit histories. What risk does this illustrate, and what control helps?
Select an answer to reveal the explanation.
Short Explanation
Merging two different people is like gluing the wrong two files into one folder—damage spreads fast. That is a false-positive merge. When confidence is fuzzy, park the pair for a steward instead of auto-smashing them.
Full Explanation
False-positive merges incorrectly declare distinct entities to be the same, corrupting history and operations. Over-aggressive auto-merge settings elevate that risk. Practitioner controls include confidence thresholds, clerical review queues, and steward approval for uncertain pairs—balancing automation with human judgment where harm is high.