Eve and the agents

15 specialist agents. One coordinated team.

Each agent owns a defined area of finance work, with a published scope: what starts its work, what it checks, who it hands off to, what it files and what stays with your team. Eve coordinates their context and responsibilities.

Read-only connections · Zero-day scan · 100% coverage · Your team keeps the final say

Eve answering which vendors still owe tier-3 rebates, citing the contract, purchase ledger and findingIllustrative data

01Eve

Meet Eve, your agentic finance manager

Eve brings business context to the work. She connects the records, processes, policies and people behind your numbers, then coordinates the right specialists for each finance task.

  • 01

    Understand your business

    Builds a shared view of your business model, systems, commercial terms and accounting policies.

  • 02

    Organise the work

    Maps processes and controls, prepares SOPs, and assigns lead and supporting agents.

  • 03

    Bring decisions together

    Routes questions, findings and approvals to your team with their evidence and financial significance.

  • 04

    Improve performance

    Reviews agent work, monitors unresolved issues and recommends improvements to procedures.

Start with Eve.
Try Rever Free

02The team

Five work groups, fifteen responsibilities

Select any agent to read what it owns. Eve sits at the centre because every agent works from the context she keeps.

Group 01 · Recover value and protect spend01 / 15

Entitlement

Finds contractual rebates, credits, discounts and commissions that are due. Recalculates eligibility, checks what has already been received and assembles supported claims for approval.

Full scope
Turning on its own · select any agent to pause

03The roster

Every agent, and what it is responsible for

Open any agent for its full scope: triggers, procedures, handoffs, workbooks, findings, Inbox boundaries and acceptance examples.

Once Eve has built your business context and your mappings are approved, the zero-day scan checks the connected records.Source to ledger by entity, period and account, anything undecided parked and visible, and the checks repeated after relevant syncs.
The zero-day scan

04How a duty runs

From a new record to a verified outcome, the same nine steps

Every duty follows one sequence, whichever agent leads it. Work lands in the files your team already keeps: Reconciliations, Inventory, Records, Findings, Inbox and Home.

  1. 01

    A trigger arrives

    A transaction, document, ledger change, schedule or question from your team. Eve consults the approved business profile and responsibility map, names a lead agent and supporting agents, and dispatches the approved duty.

  2. 02

    Readiness is checked

    The agent checks scope, access, source freshness, mappings, SOP and policy. Missing prerequisites are recorded with the financial work they affect. Ready portions continue with explicit coverage limits.

  3. 03

    The procedure runs

    Population, calculations, documents, judgments, exceptions and conclusion are stored in the right place: reconciliation workpapers in Reconciliations, inventory work in Inventory, source and accounting records in Records.

  4. 04

    Reports and workbooks are published

    Each agent publishes its reports in its own area. Downloadable workbooks reproduce the run's population, formulas, checks, exceptions and evidence references, and link back to the underlying work.

  5. 05

    Issues become findings

    Every issue or opportunity is registered in Findings with a lead owner, contributing agents, evidence, materiality, value category and next action. A successful check stays in the workpaper; it does not need an invented finding.

  6. 06

    Decisions happen in your Inbox

    Every human action is a linked Inbox task from a finding: approvals, questions, documents requested, assignment decisions, policy changes, disputes and acknowledgments. A Slack or email reply attaches to the same task.

  7. 07

    Only approved actions execute

    The responsible agent or the permitted service executes only what was approved or already delegated. Journal owns invoice creation and accounting postings. Payments and source-system actions use your permitted execution services.

  8. 08

    Execution is verified

    The agent verifies the result against the source, ledger, receipt, response or rerun, and updates the original finding and workpaper. A rejected or failed action stays open while the issue persists.

  9. 09

    Home reports what changed

    Home summarises findings, attention required, validated outcomes and recovered value from the same records. Every number drills down to the finding, the Inbox decision, the workpaper, the record and the proof of execution.

05One issue, end to end

An accepted milestone with no invoice

How one finding moves through the team: verified, approved from your Inbox, executed through your connector, reconciled when the cash lands, and counted once.

  1. 01Evesees an accepted milestone in the project system with no invoice and allocates Revenue Assurance and Matcher under the approved project SOP.
  2. 02Evidencelinks the contract, the amendment and the acceptance in Records.
  3. 03Matcherverifies contractual scope, amount, date and party.
  4. 04Revenue Assurancedetermines whether billing is due and assesses recognition separately, then raises one finding with a supported billing request.
  5. 05Investigatorsteps in only if additional evidence challenges the milestone, and resolves it before billing is approved or executed.
  6. 06Your teamapproves the billing from the Inbox.
  7. 07Journalcreates the invoice through a permitted execution workflow, records the source receipt and the accounting effect, and links the final invoice in Records. Revenue Assurance rechecks it independently.
  8. 08Cash Pilotincludes the invoice once in the 13-week forecast and tracks an approved collection action.
  9. 09Matcherreconciles the bank receipt to the receivable when the cash lands, and Cash Pilot verifies the timing.
  10. 10Homeshows the billing correction and the cash outcome in their separate categories, linked to the same issue. The invoice is never counted again as additional recovery.

Illustrative sequence from the agent operating model. A failed connector at any step produces a Steward health log, a linked system finding and an Inbox repair task, and financial completion waits for source verification.

06What complete means

A run is complete when all of this is true

A missing prerequisite cannot create a clean pass, and a local draft is not a completed posting. These are the conditions every agent run has to meet before its results reach Home.

  • The population, exclusions and missing sources are identified and reconciled to available control totals.
  • The business profile, mapping, accounting policy, SOP and threshold versions that governed the run are recorded.
  • Every applicable procedure has a performed result or an explicit reason it was not performed. A missing prerequisite cannot create a clean pass.
  • Workpapers, canonical records, agent reports and verified downloads are stored and cross-referenced in their destinations.
  • Every issue or opportunity has one authoritative finding with an accountable owner, and every human action has a linked Inbox record.
  • Any consequential action meets the approved authority boundary, including Inbox approval before every payment hold.
  • Execution is verified against actual source outcomes, posting receipts, cash or an independent rerun. Partial and failed outcomes stay visible.
  • Financial value is classified, supported and counted once, and Home reconciles to the same underlying records.
  • Auditor can trace each procedure to a test and disclose untested coverage or limitations.

07Accountability

How the agent team stays accountable

Agents follow established procedures and your approved SOPs. Their own work is reviewed, tested and reported, so the team improves.

01

Eve reviews the work

Eve reviews agent output, monitors unresolved issues and recommends improvements to procedures. She assigns approved duties to lead and supporting agents, and proposes changes for your team to approve.

02

Auditor tests independently

Auditor checks whether agents followed approved procedures and whether controls worked, and reports gaps, untested areas and corrective actions.

03

Steward keeps the ground solid

Steward watches system health, stale data, failed syncs and stalled tasks, explains their financial impact and verifies that affected work resumes after repair.

04

Your team keeps the final say

Every finding, question and approval reaches your Inbox with its evidence and financial significance. Financial actions follow your authority and approval process.

Meet them on your own books

Book a demo, or start with a free Proof of Value on a limited period of your data.