Mapping Studio is where Rever learns the shape of your books before any agent acts on them. It maps the source tables and data in your ERP, banks and documents into Rever's canonical record of the books. On top of that record, Eve builds a profile of your business and the policies the agents work within. With both in place, Rever judges each finding against your own terms.
One connected record, a canonical data model of the books
An ERP stores an invoice in one table, the purchase order in another, the receipt in a third, and the payment in a bank feed the ERP never sees. To assemble the file for one exception, you open all four. Mapping Studio maps those sources into one canonical data model, so each kind of record has one shape whichever system it came from. Rever keeps the result in Records, in canonical form: one place for every original record, calculation and source reference, connected to the work that used it.
Every agent reads this record. Matcher uses it to tie a Stripe payout to its bank line, and Investigator uses it to check whether a contract amendment explains a price difference. Eve answers your questions from the same workpapers and Records, so you and the fifteen agents work from one record of the books.
The mappings themselves need your approval before they go live. A mapping question that comes up later returns to Mapping Studio with its evidence and a linked task in your Inbox. If a mapping caused an issue, you approve the fix to the mapping and any accounting correction as two decisions.
The business profile
The second output is the profile, and Eve builds it from the mapped records. It holds the terms your business runs on: your business model, your parties and significant ledgers, your commercial terms and your accounting policies. If the records are silent, Eve asks your team targeted questions. For each process she drafts an SOP, and the process owner confirms it before any agent uses it. Materiality and approval paths sit in Settings, by entity and by user.
The profile is what makes a finding yours. A price-drift exception at a distributor with negotiated freight terms and the same exception at a clinic group with fixed contracts are two different findings. At the distributor it may be a fuel surcharge an amendment allows; at the clinic group it may be a leak. Rever judges each against the contracts in your profile and the tolerances you set, so the answer and the evidence are specific to the case.
The same profile sets the next step. Matcher commits a match within your tolerances and hands a dispute to Investigator. A correction goes to Journal and waits for approval in your Inbox, and a claim goes to a vendor only after your team approves it.
Mapping Studio and Agent Studio
Agent Studio, in early access on Growth Pro and Enterprise, is where a new agent comes from: you describe the need, Eve builds the workflow, and the agent starts as an observer. Mapping Studio establishes what the agents work on. The fifteen agents, and any you add, all read from it.
Once Eve has built your business context and your mappings are approved, the zero-day scan makes its first pass. It lands the source data through the mapping workflow, reconciles the source trial balance to the canonical book by entity, period and account, and parks anything it cannot decide, with a reason.