Last updated: 2026-04-25

Resolving unmatched rows

Anchorlet tries to match each per-property row in a statement to a property in your workspace. When the match isn't confident, the row appears as Unmatched and you'll see an orange "→" button next to the raw agency address.

How matching works

In order:

  1. Eircode — if the agency address contains a full Irish Eircode and one of your properties has the same Eircode, that's a high-confidence match.
  2. Address prefix + town — first three address tokens plus the town. Matches at medium confidence.
  3. Fuzzy — last-resort token similarity. Matches at low confidence (above 0.85 similarity).

If none of these clear, the row is unmatched.

Resolving manually

  1. Open the statement.
  2. Click the Unmatched → button on the row.
  3. The resolver modal opens. Pick the right property from the dropdown — search by name or address.
  4. Optional: tick "Remember this mapping" so future statements with the same raw address auto-link at high confidence.
  5. Click Assign.

The row now shows a high-confidence match labelled manual, distinct from the cascade-driven matches.

"Remember this mapping" — what it does

Saves the raw agency string → property mapping into a per-workspace address_aliases table. Future ingests check the alias table first, before the fuzzy cascade. So if the agency consistently writes "Apt 4, Burlington Rd" and your property is "4 Burlington Road, Dublin 4", you only have to resolve it once.

Aliases are scoped to (workspace, agency), so a different agency writing the same string doesn't accidentally inherit your decision.

When you can't find the right property

Sometimes a statement row genuinely doesn't correspond to a property in your workspace — maybe a mislabelled charge, or a property you've sold. In that case:

  1. Click the Unmatched → button.
  2. At the bottom of the modal, click Create new property. Anchorlet pre-fills the new-property form with the address from the statement.
  3. Or: leave it unmatched. The row stays visible on the statement; it just doesn't roll up into any property's ledger.

Reprocessing fixes a bad first pass

If you've manually resolved a few rows on a statement and then realise the source file had errors, reprocess the statement (… menu → Reprocess) to start fresh. The old statement is moved to Recently Deleted, the source file is re-extracted, and you start with a clean set of rows. You'll have to re-do the manual matches — but if you ticked "remember" earlier, those propagate via aliases.