March 22, 2026
Bank Matching Upgrade
Section titled “Bank Matching Upgrade”Changed
Section titled “Changed”- Added exact-sum expense bundle matching in Banking, so one imported bank charge can now link to multiple existing expense records when the bookkeeping detail is finer than the statement line.
- Added automatic exact-match suggestions in the banking match dialog to surface likely single-expense or multi-expense combinations before a reviewer has to build the bundle manually.
- Expanded transaction detail views so linked expense records, linked totals, and any remaining unmatched amount are visible from the banking workspace.
- Tightened bank-review resolution so categorizing a transaction is no longer enough on its own: transactions now stay in review until they link to a concrete expense, invoice, order, or other accounting record.
- Fixed the old one-to-one matching limitation that forced teams to collapse detailed expenses just to reconcile a bundled bank transaction.
- Fixed unmatch and ignore actions so they now clear every linked expense record from the bank transaction instead of only clearing the first linked expense pointer.
- Fixed deposit and AI categorization paths that could previously mark a bank transaction as done without linking it to a real accounting record.
Why It Matters
Section titled “Why It Matters”Card processors and marketplaces often settle several real expenses into one posted bank line, and deposits often need to clear against invoices or other receivables activity. Eclipse now keeps the bank feed aligned with the real accounting records behind both sides of that flow instead of letting “categorized” stand in for a true match.