Your bank confirms your cash balance from outside the company. Rever reads your bank activity over read-only connections, ties each line to the books and to the payment or receipt behind it, and brings the differences to your team with the evidence attached. Your banks and your ledger stay as they are.
How Rever connects to your banks
Rever reads bank activity through your bank connections, and takes statements in as documents where a feed is not available. Each connection is a direct, deterministic integration that reads and never writes, in place of an MCP server or an agent holding your banking credentials, so the agents can read only what the connection provides. Rever can also read from a common database you already maintain if your bank data already lands there. Your team sets up the connections with Rever during the Proof of Value.
No agent moves money. Rever prepares and checks: a payment hold needs Inbox approval before it is recorded in Rever, your team is told on Slack and email and applies it in the payment run, and other actions on cash are prepared with their evidence for your team to action.
What stays where
| Stays with your banks and your ledger | Happens in Rever |
|---|---|
| Accounts, balances, payments and the authority to release them | Bank lines matched to book cash entries and to the payment or receipt behind each one |
| The reconciliation your team signs in the ERP | Matcher's continuous bank-to-book matching, with each open item cited |
| Vendor bank details in your vendor master | Sentinel's review of any change to those details before a payment goes out |
| Any approved correcting entry, once posted | Journal's preparation of the entry and the check that it posted once |
Approval thresholds and dual approval for material amounts are yours to set.
Which agents work on bank data
| Use case | Agent | What it does with the bank data |
|---|---|---|
| Bank reconciliation | Matcher (lead) | Reconciles bank, card, payroll and processor activity to the books, including many-to-one settlements, fees and timing differences |
| Bank reconciliation | Investigator | Traces an unexplained difference to the transaction, party or timing cause and recommends the correction |
| Bank reconciliation | Journal | Prepares the correcting entries and, after approval in your Inbox, hands them back as an import file your team loads |
| Bank reconciliation | Evidence | Links each reconciled item to its statement line, invoice and posting |
| Bank reconciliation | Steward | Watches bank-feed freshness and failed syncs, so a stale statement shows as a health item |
| Cash forecasting | Cash Pilot | Builds a 13-week cash forecast from reconciled bank activity, receivables and payables, and compares expected cash with what landed |
| Continuous monitoring | Sentinel | Flags suspicious vendor bank-detail changes and payment patterns; for a bank-detail change, it "prepares an independent human callback using a previously trusted contact and known-good details" |
The bank reconciliation template shows the reconciliation layout your team reviews, and bank reconciliation on rever.ai covers the use case in full. Rever and your ERP answers the questions your IT lead and auditor will ask.
What the zero-day scan does first
With read-only access in place, the zero-day scan inventories the bank populations and periods it extracted and records any account or period it could not reach. It lands the accepted records with their source identifiers, guarding against duplicate delivery, and hands the landed population to Matcher to tie out against the book cash entries.
The scan reveals initial findings with the evidence behind them: a bank line with no book entry, a payment recorded in the books that never cleared, a fee nobody booked. Connector failures go to Steward and accounting differences go to the responsible agent. Missing statements and blocked checks stay visible.