STANDALONE APP · BBR
How many statement lines are still unmatched — and why?
The engine matches the statement against payables, receivables and the general ledger across eight layers, each with a score. What does not match does not disappear: it stays listed, with the reason. Below, a preview with illustrative data.
Beavy|Bank Recon
ReconcileStatementLedgerRules
Lines in the period1.842
Matched automatically1.694 · 92%
Waiting for your review104
Orphans, no match44
HOW THE ENGINE DECIDED — LAYER BY LAYER
SCORE 100Statement FITID equal to the entry's document — same transaction, no doubt612
SCORE 96Exact amount and the counterparty name inside the statement description487
SCORE 95→60Exact amount, date within 7 days — the score drops 5 points per day of distance402
SCORE 88→85Only the name matches, by text similarity — goes to review104
SCORE 75 / 70Three entries add up to one line, or three lines add up to one entry89
AMBIGUOUSTwo different counterparties would match the same line — the engine does not guess44
Whatever matches in one layer leaves the pool: the earlier layer always wins. Ambiguity falls through to the next layer instead of becoming a guess.
WHAT WAS LEFT, AND WHY
BALANCEDeclared on the statement × calculated by the system: 0,04% differencegreen
INTERNAL PAIR12 lines are transfers between the company's own accountsok
ACCOUNT HOLDERThe statement's tax ID matches the company — another client's statement is blocked at importok
ORPHANR$ 4.200 credited on 14/09 with no matching documentsuggest
RULEYou wrote «FACEBK» → Marketing. 31 lines now match on their ownlearned
ASK BEAVY
Why didn't this Stripe line match?
It is a refund, not revenue. The counterparty memory keeps the sign: STRIPE on credit is revenue, on debit it is a refund. Since the amount would match two different entries, the engine chose to ask you rather than get it wrong.