Matching payments: reference, amount, balance

2026-09-09

Recognising a payment does not require keeping a copy of your bank history.

Recognising a payment does not require keeping a copy of your bank history. A statement shows a transfer with no name and no number — and you cannot tell which amount due just closed. The brand pays in euros while the claim is in another currency — and suddenly it is unclear whether the claim is closed.

We take only what the match needs, and we record the payer as a fingerprint, not as an account number. A payment made after or before the due date still matches, because the number outweighs the date — and we recognise it even when retyped on a phone. A payment RECORDED in full stops the demand letter before it goes out — even when you have already sealed it.

A partial payment closes only its part — and the collection notice asks for the remainder, not the whole. We attach a number to the amount due which you put in the transfer title — that is how we recognise the payment. You record the payment next to the claim, copied from the bank statement, and the strength of the match is computed by the server, not the browser.

We treat the transfer title as text from a stranger: we parse it, but we do not store it and never put it in logs. We close the amount due on our own only on a full match with a single candidate — in every other case we ask you. We do not subtract a payment in another currency from the claim and we do not convert it at a rate — a conversion would be a judgement, not a fact.

We are exploring splitting a single bulk transfer across several amounts due. We are working on recognising a reversed payment, so a receivable does not stay closed by mistake. We are exploring recording who is expected to pay, so a transfer from an unexpected account gets flagged.

Informational material, not legal advice. We state the parameter and where to verify it — we do not assess your situation.