A guide for controllers, accounting managers and staff accountants.
Rever is agentic AI finance automation, built by finance, for finance. It connects read-only to the ERP and banks you already run, checks 100% of in-scope transactions, and puts fifteen specialist agents, coordinated by Eve, on your reconciliations, your close and the value your business is owed. Agents prepare and your team approves: Rever never writes to your systems, and nothing leaves Rever until a person with the authority signs off.
This edition follows the month as a controller lives it: the AP run, the bank and balance reconciliations, the close and the auditor's list, and the decisions that stay yours.
The controller's month, today and with Rever
Today the month has a shape you know. Your one AP person keys invoices and matches what the system will match; the rest lands in email. The bank reconciliation waits for the statement. The close checklist lives in a spreadsheet, you write the flux from memory, and your team builds the auditor's PBC list from folders after the fact. A material item surfaces after sign-off, and the period reopens.
With Rever the same work runs on the ledger you already keep, and nothing leaves Rever without your approval. Eve, your agentic finance manager, builds the business profile and gives each ledger a lead agent. Fifteen specialists work in five groups: recover value and protect profit (Entitlement, Deduction, Spend Guard, Revenue Assurance); verify the transaction and understand the difference (Matcher, Investigator); keep the books and close moving (Journal, Close Orchestrator, Flux Analyst); improve cash visibility and evidence (Cash Pilot, Inventory, Evidence); and keep the agent team accountable (Sentinel, Steward, Auditor).
Matcher ties activity to its documents as it lands, Spend Guard asks your approval to hold duplicates before the payment run, and Journal prepares entries for your team to post, only after your approval. The controller's case for keeping the pen sets out what leaves your desk and what stays.
Where the month changes
| Task | Today | With Rever |
|---|---|---|
| Matching | Keyed by hand; exceptions in email | Matcher as activity lands; Investigator on the differences |
| AP run | Duplicates found after payment | Spend Guard requests a hold before the run |
| Close | Spreadsheet checklist; reopens happen | Close Orchestrator keeps blockers visible all month |
| Audit | PBC list built from folders | Evidence keeps support attached to each entry |
Rever checks 100% of in-scope transactions. Your own measures are close days and reopens: record both before the scan and compare them after the Proof of Value.
Connect read-only: what your ERP admin and IT will ask
Rever reads NetSuite, Dynamics 365, QuickBooks, Stripe, your banks and your documents through read-only connections, or a common database you already maintain. Your source data stays unchanged.
The ERP admin
Each connection is a direct, deterministic integration rather than an MCP server or an agent holding credentials, so the agents read only what the connection provides. Rever never writes to your systems: an approved journal entry comes back as an import file your team loads, and your ERP stays the system of record. The CFO pack covers how Rever connects to your ERP.
IT
SOC 2 Type II, audited annually. ISO/IEC 27001:2022, certified. Data encrypted at rest and in transit, and no training on customer data. SSO, SAML and SCIM come with Enterprise. Rever runs in its managed cloud (tenant-isolated, region-pinned) or, on Enterprise, self-hosted or in a private cloud (dedicated, region-pinned). The security pack, with the SOC 2 report, ISO certificate, architecture and data-processing terms, comes on request; Rever's trust page lists the controls.
The auditor
Every approval, question and send-back is a recorded decision in the Inbox, with what happened next. Packages are priced on scope rather than seats, and everyone who reviews, approves or audits the work can be in Rever.
Where to start
One entity, the ERP, the operating bank accounts, and Stripe if you bill through it. The Proof of Value runs on a limited period of your data that you agree up front.
Mapping Studio and Eve: one connected record and your business profile
Mapping Studio is where Rever learns the layout of your books. It maps the source tables and data in your ERP into Rever's canonical record, and the zero-day scan checks the connected records once your mappings are approved. Mapping questions return to Mapping Studio with their evidence and a linked Inbox task. The CFO pack goes inside Mapping Studio.
One connected record
A vendor bill in the ERP, a line in the bank feed and a Stripe payout land as linked records. Open an entry in Records and walk to its documents: Evidence links each reconciled item to its statement line, invoice and posting. Investigator reads that file before it writes up a finding, and your reviewer opens it instead of asking the preparer to rebuild it.
The business profile
Eve builds the profile from cited evidence: your business model, systems, commercial terms and accounting policies, with targeted questions where the records are silent. She drafts a process-specific SOP and asks the process owner to confirm it before any agent uses it. Your team sets materiality and approval paths in Settings, entity by entity. Matching tolerances are thresholds you set: value, quantity, rate, date and rounding for Matcher.
Where agents come from
Eve builds new agents in Agent Studio, in early access; page 9 covers it. Mapping Studio sets the records the agents work on, and Settings holds the rules they work under.
The zero-day scan, read as a controller
The zero-day scan is the first pass over your connected records once read-only access is in place. It ties source and landed journal counts and totals by entity, period and account, then launches the approved verification and control baseline across the in-scope population. It reveals initial findings with the evidence behind them. Missing sources and blocked procedures stay visible, and a missing source cannot produce a clean pass.
What it checks in your reconciliations
| Area | What the scan looks for |
|---|---|
| AP | Duplicate bills and payments, price drift against PO or contract, three-way match exceptions |
| Bank and processor | Unmatched bank, card and processor items, many-to-one settlements and fees |
| Vendor and customer balances | Short payments and deductions tested against invoices and agreements, unclaimed credits |
| Contracts and rebates | Contractual price changes never billed, unclaimed rebates |
What comes back
Rever tracks five outcomes apart: value identified, value recovered, leakage prevented, cash released and errors corrected. Recovered means verified cash received or a credit applied. The honesty ratio, value recovered divided by value found, keeps identified and recovered apart.
Some findings are corrections rather than cash: an aged bank item, an accrual that never reversed, a missing receiving record. For a controller those matter as much as the recoveries, because they are the items that reopen a period.
In a free Proof of Value, you agree the scope, Eve builds context, the scan runs on a limited period of your data, and the team walks you through the supported findings and what needs more evidence. The CFO pack explains how the zero-day scan works.
What the scan promises
The scan carries no guaranteed amount and no percentage of spend. A finding is a supported opportunity; collecting it still takes validation and your approval.
The freight case, as preparer and as reviewer
This is an illustrative case, not a customer result. Read it once as the staff accountant who prepares it and once as the controller who approves it. Three-way match exceptions, line by line works the same case as a workpaper.
The signal. An invoice from FreightCo lands at $4,812 against purchase order PO-1884 for $4,502. Matcher compares the invoice with the purchase order and the receipt field by field. The price does not agree, so Matcher hands the $310 difference to Investigator.
The preparer's work. Investigator reads the documents behind the disputed amount. It finds amendment A2, signed 28 June, adding $240 of fuel surcharge, and a receiving record showing a short shipment worth $180. Journal drafts the entry: match $4,562, accrue $250. The accrual reverses on settlement, Close Orchestrator verifies the reversal, and every figure links to its document.
| Line | Amount | Source |
|---|---|---|
| Purchase order | $4,502.00 | PO-1884 |
| Fuel surcharge | +$240.00 | Amendment A2, signed 28 June |
| Short shipment | −$180.00 | Receiving record |
| Match | $4,562.00 | Invoice, re-added and traced |
| Accrue | $250.00 | Balances the invoice; reverses on settlement |
The reviewer's work. The finding arrives in your Inbox with its evidence and its financial significance. The approval path you set in Settings decides who signs, and a material amount takes two approvers. Journal cannot approve its own entry. After your approval, Journal hands the entry back as an import file your team loads, and checks the result once it is loaded. Your decision stays on the record.
What the case teaches. If FreightCo's fuel surcharges recur, Eve proposes a change to the AP procedure for your approval. She publishes it only after you approve and keeps the previous version, so next month's reviewer can see which SOP governed which match.
The Inbox and the Reconciliations room
The Inbox
Every human action lands in the Inbox: approvals, questions, document requests, disputes. Each task links to its finding, with the evidence and the financial significance attached. The staff accountant sees the questions that need a person; the controller sees the approvals on their path. Eve sequences attention by materiality, risk and pendency, so the items that matter before sign-off sit at the top. A Slack or email reply attaches to the same task.
The Reconciliations room
Reconciliations hold standing workpapers, each with its population, open items and evidence, ready to download in Excel. Matcher reconciles bank, card, payroll and processor activity to the books, including many-to-one settlements, fees and timing differences, and cites every open item. Investigator traces an unexplained difference to the exact transaction, party or timing cause and recommends the correction. Journal prepares it, and after approval hands it back as an import file your team loads. Steward watches bank-feed freshness, so a stale statement becomes a health item instead of a false clean reconciliation. Bank reconciliation and the AP run follows one day of it.
Before the AP run
Spend Guard screens every bill for duplicates, price drift against the order or contract and missed discounts, and requests a hold before the payment run. A hold needs your approval in the Inbox before it is recorded in Rever, and your team applies it in the payment run. Sentinel flags suspicious vendor-bank changes and payment patterns. For a bank-detail change it prepares an independent callback to a previously trusted contact, using known-good details instead of the ones that came with the change.
Who tests the agents
Auditor runs independent tests on the agents' work. It reperforms selected calculations and matches, reviews false positives and false negatives, and publishes an untested coverage statement, so a procedure nobody tested cannot pass as clean. You set the approval thresholds and the dual approval for material amounts. The floors hold in every plan, Free included: nothing leaves Rever without a recorded approval from an authorised approver, and the identity that prepares an action cannot approve it.
The close, without the reopen
A reopen is the controller's worst hour: a material item surfaces after sign-off and the period comes back. Rever moves the close work off the deadline, so your team finds the item while the period is still open.
Close Orchestrator
Close Orchestrator keeps tasks, reconciliations, schedules and sign-offs moving all month. It keeps a researched checklist tied to your business and policy, reviews the previous six months of close entries and adjustments, adds missing recurring tasks and verifies opening reversals. It routes decisions to your Inbox and will not certify an incomplete close. Sign-off waits for you, with completed work, remaining exceptions and blockers in view. The close and the PBC list carries it through to the auditor.
Journal
Journal recomputes accruals, provisions, depreciation and prepayments from the specialists' schedules; the $250 freight accrual above is one of them. Each entry carries its support. After approval in your Inbox, Journal hands each entry back as an import file your team loads, and material amounts take the dual approval you set. If you carry stock, Inventory checks cut-off and goods received not invoiced before sign-off.
Flux Analyst
Flux Analyst explains movements against the prior period, the three-month average and plan, down to party and unit level, and separates explanation from residual. Ask Eve about a movement and she answers from the current workpapers and Records, naming any uncertainty or coverage gap.
Evidence and Auditor
Evidence attaches the support to every close entry and keeps the two-way link between each entry and its documents. Auditor tests whether each agent performed its approved procedures and states what stayed untested. Fieldwork starts with the evidence already attached.
Start with the zero-day scan
The right first step is a zero-day scan on a limited period of your own data, inside a free Proof of Value.
Or start free
The Free plan runs the zero-day scan self-serve on the data you connect: read-only connections to your ERP, banks and documents, initial findings with their evidence, and Eve answering questions about the scanned data. Unlimited users, on managed cloud. The specialist agents come with Growth, priced after your Proof of Value.
The chases nobody owns
Unclaimed credits, open confirmations, missing documents: Eve turns that routine into a governed agent in Agent Studio, in early access on Growth Pro and Enterprise. You describe the need; Eve builds the workflow from automations already in Rever and records the SOP. The agent works under the same read-only connections and Inbox approvals as the fifteen, starts as an observer, and earns its role.
What happens next
1. A practitioner replies, someone on the finance side of the team.
2. A short call about your systems, your close and where you suspect value is leaking.
3. You agree the scope: which entity, which systems, which period. Rever's team sets up the read-only connections with yours.
4. Eve builds context, and the zero-day scan runs on that period.
5. A walkthrough of the supported findings and the actions to pursue value.
Bring three things
- Your systems. Which ERP, which banks, and whether you bill through Stripe.
- Your close. Days to sign-off today and the number of reopens last quarter.
- One worry. The vendor whose invoices never match, the bank items that age, the accrual nobody reverses.
A short guide to the terms
Zero-day scan: the first pass over your connected records once read-only access is in place. It runs the relevant checks across the in-scope population and reveals initial findings with their evidence.
Proof of Value: free. You agree the scope, Eve builds context, the zero-day scan runs on a limited period of your data, and the team walks you through the supported findings.
Mapping Studio: the component that maps ERP tables and data into Rever's record. Mapping questions return to it with their evidence.
Eve: your agentic finance manager. She builds the business profile, drafts SOPs for your confirmation, assigns lead and supporting agents, and answers from workpapers and Records. She cannot approve her own proposals, post journals or move money.
Inbox: where every human action lands, linked to its finding with the evidence attached.
Reconciliations: standing workpapers with their population, open items and evidence, downloadable in Excel.
Import file: how an approved journal entry leaves Rever: a file your team loads into your ERP, a .qbo file for QuickBooks today. Rever never writes to your systems. Materiality, approval paths and dual approval for material amounts are set in Settings.
Agent Studio: early access on Growth Pro and Enterprise. Eve builds a new agent from a need you describe; it starts as an observer.
Identified and recovered: two of the five outcomes Rever tracks apart. Identified is a supported opportunity that still needs validation or action; recovered is verified cash received or a credit applied.
Honesty ratio: value recovered divided by value found.
About this edition
Agent roles, controls, security, hosting and package descriptions follow rever.ai: product, agents, Agent Studio, pricing, trust, Proof of Value. The freight case is an illustrative case, not a customer result. Diagrams are editorial, not screenshots. The CFO edition of this series starts at rever.ai/explore.
© 2026 Rever Finance Inc. Explore Rever series.