Rever for private equity: portfolio company finance

For PE sponsors, operating partners and portfolio CFOs.

Rever is agentic AI finance automation, built by finance, for finance. It connects read-only to the ERP, banks and documents a portfolio company already runs. Eve, Rever's agentic finance manager, coordinates fifteen specialist agents across reconciliation, the close and value recovery. Rever never writes to their systems, and people approve every financial action.

For a sponsor the motion is two zero-day scans on two portfolio companies in parallel: the one with the newest CFO and the one with the most recent add-on. Each gets a free Proof of Value on an agreed scope, then two findings reports to compare.

Fifteen agents for each portfolio company

Every portfolio finance team does the same work by hand: match transactions to documents, explain exceptions, prepare the close, chase the rebates the business is owed. Rever puts a team of agents on that work, on the ledger the company already runs. Agents prepare, and the company's own people approve.

Fifteen agents in five work groups

Eve coordinates the fifteen and is not one of them. She builds each company's business profile, drafts the SOPs its process owners confirm, and gives every ledger one lead agent and named support. Each agent has a published scope on rever.ai/agents: what starts its work, what it checks, who it hands off to and what stays with the company's team.

The number that survives diligence

Rever tracks five outcomes, each in its own column: value identified, value recovered, leakage prevented, cash released and errors corrected. Identified is a supported opportunity that still needs validation or action. Recovered means verified cash received or a credit applied. Rever reports the ratio between them, value recovered divided by value found, and calls it the honesty ratio. A QoE provider can test it, because every recovered dollar drills down to the finding, the Inbox decision, the workpaper, the record and the verified outcome.

Rever checks 100% of in-scope transactions, not a sample, and the scan leaves missing sources and blocked procedures in view. The sponsor's numbers come from each company's own records, never from a forecast.

Every add-on on its own system

An add-on closes on a Friday. On Monday it still runs its own QuickBooks, its own bank accounts and its own AP clerk, and it stays that way for months while the platform decides when to consolidate. The same vendor sits in two vendor masters, one per entity. The distributor rebate the founder negotiated sits in a PDF nobody at the platform has read. That PDF holds basis points.

Rever connects read-only to NetSuite, Dynamics 365, QuickBooks, Stripe, the company's banks and its documents, or to a common database the company already maintains. Each connection is a direct, deterministic integration, so the agents read what the connection provides and the source data stays unchanged. The sponsor can scan the add-on on its own QuickBooks before consolidation, and the platform on its NetSuite alongside it. The add-on article walks through what that scan finds.

An add-on that carries stock

A distributor or manufacturer add-on brings inventory the platform has never counted. The Inventory agent reconciles opening stock plus additions less consumption to closing stock with no balancing plug, recomputes valuation under the company's cost method and ties the subledger to the general ledger. Stale goods received not invoiced surface as findings, receipts attached.

For the ERP admin

Each connection is a direct, deterministic integration that reads and never writes. Approved entries come back as an import file the add-on's team loads, and the add-on's clerk keeps the pen.

Mapping Studio, per company

Mapping Studio maps each company's data: the source tables and data in its ERP go into Rever's canonical record, so a vendor bill, a bank line and a receiving record link to each other. Open an entry in Records and walk to its purchase order, amendment and payment.

Eve then builds context. She assembles the business profile from cited evidence: revenue models, parties, significant ledgers, commercial terms and accounting policies. She drafts a process-specific SOP for each ledger and asks the process owner to confirm it before any agent uses it. She asks targeted questions wherever the records are silent.

Kept per company

Two companies differ here, and Rever keeps them apart. In Settings, each entity defines its own materiality and approval paths. The platform's tolerances are not the add-on's. The platform routes approvals to its controller; the add-on routes them to its own finance lead. A price-drift exception at a distributor and the same exception at a clinic group get judged against different terms.

On Enterprise, multi-entity, multi-ERP and consolidation run through the Console on top of each company's own profile. The Mapping Studio article in the CFO pack covers the mapping step in detail.

New agents come from Agent Studio, in early access, on page 9.

Two scans, in parallel

The zero-day scan is the first pass over a company's connected records once read-only access is in place. It applies the relevant reconciliations, verifications and controls to the in-scope population and reveals initial findings with the evidence behind them. Missing sources and blocked procedures stay visible. Run it at two companies side by side and the sponsor holds two evidenced starting points before the next board cycle. Start with two scans makes the case for running them in parallel.

Checks in each scan

Duplicate invoices and payments. Price drift against the order or contract. Unclaimed rebates and credits. Short payments and deductions tested against invoices, agreements and delivery evidence. Delivered work and contract price changes that never reached an invoice. Unmatched bank and processor items.

The Proof of Value at each company

Each company gets a free Proof of Value on an agreed scope, in four steps. The CFO agrees the scope: which entity, which systems, which period, with read-only connections set up alongside the company's team. Eve builds context. The zero-day scan runs on a limited period of the company's data. Rever's team then walks the CFO through the supported findings, their financial significance, what needs more evidence and the actions required to pursue value.

Picking the two companies

Each portfolio company CFO approves their own engagement. The sponsor recommends the two companies and reads the two reports. The scan promises no dollar amount, no percentage of spend and no assurance that a finding is recoverable.

A two-company readout, by category

This readout is hypothetical. It shows the shape of two findings reports, not a result at any company. Counts are illustrative; dollar totals belong in each company's own report, with evidence.

Company A is the platform, on NetSuite OneWorld, four entities, a controller and an AP team of three. Company B is an add-on closed 90 days ago, on QuickBooks, one entity, one AP clerk, with a warehouse.

Reading the two columns

Company A's exceptions concentrate in price drift and deductions, the pattern four entities and a full AP team produce. Company B's concentrate in bank items, stock and a rebate programme nobody has touched, the pattern one clerk and a founder's PDF produce. The same method found both, and the fixes differ.

Each finding stays in the identified column until cash is received or a credit is applied. The honesty ratio at each company starts at zero and moves only when that happens. After the two walkthroughs the sponsor compares two ratios, each from its own ledger. Identified versus recovered explains why Rever keeps the columns apart.

One exception, end to end

This is an illustrative case, not a customer result: a freight exception at one company, followed from signal to hand-back.

Signal. An invoice from FreightCo lands at $4,812 against purchase order PO-1884 for $4,502. Matcher ties the bill to its order and receipt field by field, and the amounts disagree.

Evidence. Investigator reads the amendment behind the mismatch. Amendment A2, signed 28 June, added $240 of fuel surcharge. A receiving record shows a short shipment worth $180. Evidence links each figure to its page.

Draft and approval. Journal drafts the entry: match $4,562, accrue $250. Journal cannot approve its own entry, so the packet goes to the Inbox of the person whose approval threshold covers it.

Hand back. After that approval, Journal hands the entry back as an import file the company's team loads, and checks the result in the ledger once it is loaded.

Recurrence. If the carrier's surcharge recurs, Eve proposes an SOP change to the process owner. She publishes it only after approval and keeps the previous version.

The QoE provider's view

At diligence, the buyer's QoE provider can open the entry and see the invoice, the amendment, the receiving record and the Inbox decision that approved it. The freight case in the Controllers edition shows the same entry from the preparer's side and the approver's.

The control story

A sponsor sells a company twice, once to the buyer and once to the buyer's QoE provider, and the second sale turns on controls. Rever runs the same controls at both companies, and each company sets its own thresholds.

Agents prepare, people approve

Rever reads each company's systems and never writes to them. Only approved work leaves Rever, with thresholds and dual approval for material amounts set by each company. A payment hold needs Inbox approval before it is recorded in Rever, and the company's 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. A Sentinel pass never stands in for a person authorising a payment, and Eve cannot approve her own proposals, post journals or move money.

Agents answer for their own work

Auditor tests whether each agent followed its approved procedures, reperforms selected calculations and matches, and issues an untested coverage statement, so a material untested procedure cannot pass. Steward watches stale data, failed syncs and stalled tasks. Every new agent starts as an observer, and Eve promotes what performs and demotes what does not.

For a rebate claim, Evidence hands over a traceable pack: Entitlement's working, the contract terms and the purchases. Each approval, question and send-back sits in the Inbox as a recorded decision. Identified versus recovered shows how that trail backs the ratio.

For the security review

The security pack (SOC 2 report, ISO certificate, architecture, data-processing terms) is on request through rever.ai/trust.

The portfolio month

The two Proofs of Value show what a limited period held. A Growth package then puts the agents on each company's new transactions, closes and claims.

Every day. Matcher reconciles new bank, processor and ERP activity to its documents. Spend Guard screens bills for duplicates and price drift and requests an Inbox-approved hold before the payment run. Sentinel flags unusual vendor-bank changes and payment patterns for review.

Through the month. Entitlement recalculates rebates and credits as purchases land and assembles supported claims. Deduction tests short payments against invoices, agreements and delivery evidence. Revenue Assurance checks that delivered work and contract price changes reach an invoice. Claims go out only after an authorised approver at the company signs off. Cash Pilot keeps the 13-week cash forecast current; its recommendations carry no payment authority.

At month-end. Close Orchestrator keeps tasks, reconciliations and sign-offs moving, and routes decisions to the Inbox without certifying an incomplete close. Journal prepares accruals from specialist schedules. Flux Analyst explains movements against the prior period, the three-month average and plan. Sign-off waits for the CFO, with remaining exceptions and blockers visible. A day-15 lender package needs a close that stays ready all month. The portfolio month-end article follows one company through it.

Agent Studio, company by company

Each company carries work no product ships: the lender-package chase, the covenant check, a due-diligence request. Agent Studio, in early access on Growth Pro and Enterprise, turns that work into an agent. A finance user describes the need. Eve builds the workflow from automations already in Rever and records the SOP. She deploys the agent under the same read-only connections and Inbox approvals as the fifteen, and it starts as an observer. Each company keeps its own SOPs and approvals.

Start with the zero-day scan

The first step is two companies, each scanned on an agreed scope.

What happens next

1. A practitioner replies from the finance side of Rever's team.

2. A short call per company: its systems, its close and where the CFO suspects value is leaking.

3. Agree the scope at each: which entity, which systems, which period; each team sets up read-only connections with Rever.

4. Eve builds context, then the zero-day scan runs on a limited period of each company's data.

5. A walkthrough at each company of the supported findings, then two reports to compare.

Bring three things

• Two companies. The one with the newest CFO and the one with the most recent add-on.
• Their systems. ERP, banks, Stripe billing and any stock.
• Their CFOs. Each approves their own engagement. The sponsor recommends.

Sponsors can also write to founders@rever.ai with the subject "partnership".

Terms

Zero-day scan: the first pass over connected records once read-only access is in place, with initial findings and their evidence. Proof of Value: free, on an agreed scope and a limited period of data, ending in a walkthrough. Identified and recovered: two columns, kept apart; recovered means cash received or a credit applied. Honesty ratio: value recovered divided by value found. Agent Studio: where Eve builds a new agent; early access on Growth Pro and Enterprise.

About this edition

Agents, controls and packages follow rever.ai: product, agents, Agent Studio, pricing, trust, Proof of Value. The freight case is an illustrative case, not a customer result, and the two-company readout is hypothetical. The CFO pack lives at rever.ai/explore.

© 2026 Rever Finance Inc. Explore Rever series.