Bank Reconciliation

Bank Reconciliation closes the last gap in the revenue lifecycle: a deposit has landed in your bank, and something in Suger says it should have. This page matches the two, automatically where it is confident enough and through a human review queue where it is not.

Overview

Open Revenue → Bank Reconciliation, under Operations in the sidebar. The page has four summary cards, a reconciliation summary panel, and two tabs — All Transactions and Review Queue.

It reads the bank accounts you connected on the Bank Accounts tab of Revenue Settings. Until at least one account is linked there, there is nothing here to reconcile.

How a bank transaction gets matched

Matching runs in three tiers. A transaction only reaches a person once the two automatic tiers have declined to settle it:

The thresholds are fixed, not configurable:

Summary cards

All Transactions

The All Transactions tab lists every imported bank transaction with its date, amount, currency, bank account, reference, description, match status, confidence, matched to, and variance.

Confidence is how sure the matcher is about the match it proposed, so a low-confidence match can be reviewed before it is accepted. Matched To names what it was matched against. When the matched record belongs to a payout, it shows that payout’s reference — or its disbursement ID — as a link that opens the same Disbursement detail as Cash & Disbursements, with the payout summary, linked invoices, refund activity, and source payload; a record paid out across several payouts links to the earliest. Otherwise it shows the matched record’s ID.

Narrow the list with the bank account, currency and status filters, or search by amount or description.

Unmatched

The Unmatched tab is scoped to transactions with no match at all, and its label carries the count. It is deliberately separate from the Review Queue: a transaction with nothing proposed for it is a different problem from one with a proposal awaiting your decision.

Review Queue

The Review Queue tab is scoped to the transactions still awaiting a decision, and its tab label carries that count. It is a table of each transaction’s Date, Description, Amount, Match Status, Confidence, Variance, and Why flagged, and each row offers Review Match, which opens the review dialog.

Why flagged says what sent the transaction to a person:

To work one transaction:

1. Open the Review Queue tab.
2. Select Review Match on the transaction you want to settle.
3. Review the suggested matches. Each suggestion was saved when the transaction was scored, and shows its confidence percentage and the reason it was suggested.
4. If none of them is right, choose a target type and search for the correct record yourself.
5. Add a comment explaining the decision.
6. Select Approve Match to bind the transaction to the selected candidate, or Reject Suggestion to decline the suggestions without binding anything.

Approve Match requires a selected candidate. Reject Suggestion does not — it records that the suggestions were wrong and returns the transaction to the queue.

What a transaction can be matched to

KPI calculation formulas

Counts are over the bank transactions in scope. Amounts are converted to USD at the rate for the reporting date; if a rate is unavailable for any currency present, the summary is not returned rather than being reported with a gap.

Freshness

Bank reconciliation runs on its own schedule — every 15 minutes, for every organization with an active bank account — and does not wait for a channel sync. Provider upserts and the overlap window make repeated runs idempotent, so a transaction is never double-imported. See Revenue Settings for the accounts that feed it.