Matching and alerting policy
Pre-authorisation matching
How far the booked amount may differ from the authorisation and still count as the same purchase. Set to 0 to require an exact amount.
Upper limit in cents, whichever is smaller. Without it, 25% of a large payment would be a very wide window. 5000 = 50.00.
Comma-separated. Ignored when comparing payees, because many banks prefix the booked name but not the pending one. Only affects comparison — what the bank sends is still what gets written.
Decision thresholds
How confident the matcher must be that a booking is the settlement of an existing row before it merges the two without asking. Raising it means more cases land in the review queue; lowering it means more are decided for you.
Below this the booking is treated as a new transaction and imported. Between the two it is held back and listed under Review — nothing is written to the budget until you decide. Must not be above the value above it; setting the two equal leaves only genuine ties to be asked about.
How often a transaction that reaches the matcher turns out to be the settlement of a row you already have, rather than something new. Most bookings never reach the matcher at all — the bank’s own reference settles them first — so this is about the ones left over. It is a claim about your bank, not a measurement: raising it makes the matcher readier to pair, lowering it makes it readier to import as new. Fifty is what the program assumed before it could be set.
Most transactions are decided without you, and nobody ever finds out whether those decisions were right — which is where the expensive mistakes are. With this on, each sync picks the single decision whose answer would tell the matcher the most and asks about it under Review. Your budget is not affected either way and nothing waits on the answer. There is always an “I cannot say”; use it rather than guessing, because a guessed answer teaches the matcher something false.
Balance drift
Email when the budget and the bank disagree by more than this, and only when it persists across two consecutive syncs. 0 disables the email; the difference is still logged and exposed on /health.