Do you want to prevent matches with similar addresses from scoring too high, or being reported at all?
Most easily, if the addresses are the same apart from the street or flat/unit number, you can set the option "Must have building/house/apartment number match" on (in mSQL and mHub, this is the “mustMatchPremise” constraint). But, you might miss some good matches with simple typos this way.
If you want something more sophisticated, you can change the Matching Weights for Address, by changing the Possible and Likely Weights for Address. The Address Weights work quite differently from weights on other data items:
- Address scores are calculated as a proportion of the Sure Weight, with a maximum of 100% if the addresses are essentially a perfect match
- Address scores achieving below the Possible Weight are set to zero
- Addresses with differences in premise number (where the premise numbers don't even fuzzy match) will be restricted to a score that doesn’t exceed the Likely Address Weight.
By tinkering with these weights (and maybe the minimum score threshold), you can ensure that records where the name match isn't a sure match are not reported (or score lower).
There is additional flexibility in mSQL and mHub with regard to premise numbers that fuzzy match such as 23/23A, 23/32, 23/230, 23/53.