First of the month, and the unmatched pile grows
Your product connects to a letting agency's client account through a bank feed and matches incoming rent to tenancies. On the first working day of the month, the payments arrive. Many match. The rest drop into an unmatched queue: a payment with reference RENT, one from a surname that does not appear on any tenancy, three payments of a third of the rent each for a student house, a payment slightly short because the tenant deducted something, and one that pays two months at once.
The agency's accounts person works through the queue by hand, searching tenancies, checking last month's statements and ringing tenants. Until each payment is matched, the landlord statement cannot be run, and the arrears list is wrong: tenants who have paid show as owing.
Why exact matching fails on rent
Rent is paid by people, from their own banking apps, in ways that make sense to them. Your matching was probably written around the clean case: one tenancy, one payment, the right reference, the right amount.
- Tenants type their own reference, or none, or copy last month's wrong one.
- Sharers in HMOs and student lets pay separate shares on different days.
- Parents, guarantors and employers pay on a tenant's behalf from accounts with other names.
- Housing benefit and Universal Credit payments arrive with their own references and amounts.
- Part payments, overpayments and payments covering more than one month are common.
- Your matching treats every miss as equally unknown, so an obvious match waits alongside a genuine mystery.
What an unmatched queue costs
The agency's accounts team loses days at the start of each month, when they are busiest. Landlord statements and payments are delayed, which is exactly the thing landlords notice. Tenants who have paid receive arrears reminders, and some ring the office upset. Every manual match is also a chance for an error in client money, which the agency then has to find and correct.
For you, a large unmatched queue is the most visible sign that your product is not saving the agency time, and it is often the subject of the first complaint an accounts manager makes.
How we build rent matching that learns
What we build scores each payment against likely tenancies using every clue available, and remembers what people confirm.
- Reference parsing that finds tenancy references, property addresses, flat numbers and tenant names inside messy references, allowing for typos.
- Payer memory: once a person confirms that payments from a given account belong to a tenancy, future payments from that account are suggested automatically.
- Amount logic that recognises shares of the rent, part payments, known deductions and multiple months, and checks against what is due.
- Date logic that expects payments near each tenancy's due date and understands benefit payment patterns.
- A confidence score for each suggested match, with your agency's rule for what can be matched automatically and what needs a person.
- An unmatched queue sorted by confidence, showing the top suggestions and the reason for each, so most items take a click rather than a search.
| Payment | Clues used | Likely outcome |
|---|---|---|
| Reference RENT, known payer account | Payer memory, amount, date | Matched with high confidence |
| A third of the rent from a sharer | Name on tenancy, share of rent | Matched as a part payment |
| Parent pays, surname differs | Payer memory once confirmed | Suggested, then automatic in future |
| Slightly short, tenant deducted repair | Amount and note in reference | Suggested, flagged for review |
| No clues at all | None | Queue, top suggestions shown |
Rules about how part payments and deductions are handled belong to the agency and its accountant. We make the product apply the agency's rules consistently and show every decision.
The first of the month, afterwards
The payments arrive. Most match automatically as before. Of the rest, many are now suggested with high confidence: the parent's account confirmed last month, the sharers' third payments, the benefit payment with its usual reference. The accounts person approves them in a few minutes, looks properly at the handful that are genuinely unclear, and runs landlord statements on time. The arrears list is right, so the reminders go only to tenants who have not paid.
Is your unmatched queue too long?
- Matching relies on an exact reference and amount.
- Agencies spend the first days of every month matching payments by hand.
- Tenants who paid receive arrears reminders.
- Payments from parents and guarantors never match automatically.
- Your product does not remember which accounts pay which tenancies.