Capabilities · Continuous monitoring
Continuous monitoring of controls, systems and unusual changes
Sentinel detects unusual changes and potential control abuse, including suspicious vendor-bank changes and payment patterns. Steward monitors system health, stale data and stalled tasks. Auditor tests whether procedures were followed, and Matcher keeps the reconciliations current. Risks arrive with safeguards recommended, for your review.
Never writes to your systems · Zero-day scan · 100% coverage · Your team keeps the final say
01Where the work breaks
Where control gaps stay small and unseen
A control tested on a sample after the close can be broken for weeks before anyone notices.
- 01
Controls are tested on a sample after the close, so a broken one runs for weeks
- 02
Vendor-bank changes and payment patterns are reviewed when someone happens to look
- 03
Failed syncs and stale data quietly undermine every downstream check
- 04
Nobody can say how a control performed last period, because nobody counted
02How Rever works
How Rever runs continuous monitoring
Connect, build context and unlock value, then verify the outcome. The same shape as every Rever procedure.
- Step 01
Connect your systems
Link your ERP, banks, master data and the systems that feed them. Rever reads through their APIs and works on its own copy. Nothing in your systems changes.
- Step 02
Run the zero-day scan
Eve maps controls, owners and materiality, then the zero-day scan tests the period and reports what worked, what did not and what could not be tested.
- Step 03
Agents work continuously
Sentinel watches changes and patterns and Matcher keeps reconciliations current across 100% of in-scope activity; Steward monitors the connected systems; Auditor independently tests the approved procedures and reports what was tested and what was not.
- Step 04
Approve from one Inbox
Supported risks arrive with recommended safeguards and their financial impact. Your decision is recorded with what happened next. The outcome is verified against the source before it counts.
Illustrative data03What your team gets
Evidence you can follow. Decisions you keep.
Unusual changes caught early
Sentinel detects suspicious vendor-bank changes, unusual payment patterns and potential control abuse, and presents supported risks with recommended safeguards.
System health tied to financial impact
Steward identifies stale data, failed syncs and stalled tasks, explains what they mean for the numbers and verifies that affected work resumes after repair.
Controls tested, not assumed
Auditor independently tests whether procedures were followed and whether controls worked, and reports gaps, untested areas and corrective actions.
Safeguards recommended, decided by you
Every risk arrives in the Inbox with its evidence and a recommended safeguard. Your team decides, and the decision is recorded with what happened next.
04Before and after
Manual continuous monitoring versus Rever
| Dimension | Periodic testing | Rever |
|---|---|---|
| Cadence | A sample after the close | Continuous, across 100% of in-scope activity |
| Unusual changes | Found by whoever happens to look | Detected by Sentinel, with safeguards recommended |
| System health | Noticed when a report is wrong | Watched by Steward, tied to financial impact |
| Control testing | Asserted at audit time | Tested independently by Auditor |
| Evidence | Assembled on request | Kept with each finding |
| Decisions | Scattered across email | Recorded in the Inbox with what happened next |
05The agents on this job
5 of the fifteen, coordinated by Eve
Eve brings the business context and names one lead for each finding. On continuous monitoring, Sentinel leads. The lead owns the conclusion, supporting agents contribute the checks it rests on, and Eve adds specialists as your approved scope requires. Every decision goes to your team.
Sentinel
Detects approval splitting, authority breaches, unauthorised master-data changes, unsupported payments and unusual patterns, and requests a proportionate review or an Inbox-approved hold.
Full scope Agent 14 · SupportingSteward
Watches failed syncs, stale sources and stalled work, prioritised by the finance work they block.
Full scope Agent 15 · SupportingAuditor
Tests the controls and the agents' own procedures on a cycle, including duplicate detection, ungated hand-backs and self-approval.
Full scope Agent 05 · SupportingMatcher
Supplies the field-level comparisons behind unsupported-payment and duplicate findings.
Full scope Agent 03 · SupportingSpend Guard
Reports duplicate and split spending patterns that point to a control failure rather than an accounting error.
Full scopeThe evidence behind each check
Examples of the transaction checks behind this work. Matcher compares the evidence legs field by field, a leg can hold several linked records, Investigator adds a fourth or fifth document when the first three disagree, and the specialist owns the financial conclusion.
| Transaction family | Three evidence legs | What is compared | Financial lead |
|---|---|---|---|
| Purchasing authorisation | Approved budget or indent · Accepted quotation · Purchase order | Available allocation, selected scope, price and authorisation | Spend Guard, Sentinel |
| Expense reimbursement | Approved expense claim · Receipt or support · Reimbursement payment | Employee, business purpose, policy, date, amount and duplication | Deduction, Spend Guard |
| Payroll settlement | Approved payroll register · Payment instruction file · Bank settlement | Employees, deductions, approved totals and actual disbursement | Matcher, Sentinel |
| AP settlement | Approved supplier invoice · Payment allocation or remittance · Bank debit | Payee, bank reference, amount, currency, discounts and partial settlement | Spend Guard, Matcher |
06FAQ
Questions about continuous monitoring
What does continuous monitoring mean with Rever?
Controls, systems and master data are watched as activity happens rather than reviewed on a sample after the close. Sentinel, Steward and Matcher each own a part of that watch across the in-scope population; Auditor tests the procedures independently and states its coverage; and every risk reaches your Inbox with evidence and a recommended safeguard.
What does Sentinel watch?
Unusual changes and potential control abuse: vendor-bank detail changes, unusual payment patterns, master-data changes and other movements that deserve a second look before money moves.
Does Rever block transactions?
Only after your team approves the hold in the Inbox. The hold is recorded in Rever, your team is told on Slack and email and applies it in the payment run. No agent places a hold automatically. Sentinel presents supported risks and recommended safeguards for human review, and every financial action follows your approval process.
Will Rever change our source data?
No. Rever reads your ERP, bank and payment records through their APIs, keeps a working copy inside Rever (the shadow ledger) and does every check, reconciliation and calculation there, during the zero-day scan and after it. Your ERP stays the system of record.
What does a free Proof of Value show?
You connect your systems and Rever works on a limited period of your data, so you can see how it works on your own records before signing up. We walk through what was checked, the supported findings and their financial significance, and the actions required to pursue value.
What does 100% coverage mean?
Every in-scope transaction in the connected population is included in the relevant checks. Missing sources, documents and blocked procedures remain visible.
See your own controls watched
Get a free Proof of Value on a limited period of your records, with every risk supported by evidence.