NetSuite stays your system of record. Rever connects to it read-only, maps its records into a canonical model of your books, and puts fifteen specialist agents, coordinated by Eve, to work on the transactions in scope. Rever never writes to NetSuite: your team approves each entry in the Inbox, it comes back as an import file your team loads, and NetSuite stays the place entries post.
NetSuite AI agents on a read-only connection
The connection is a direct, deterministic integration that reads and never writes, in place of an MCP server or an agent holding your NetSuite credentials, so the agents can read only what the connection provides and your source data stays unchanged. Your team sets up the connection with Rever during the Proof of Value, and Rever can also read from a common database you already maintain if NetSuite data already lands there.
NetSuite ships AI features of its own; Oracle NetSuite's documentation covers them. Rever's agents work across NetSuite and the other sources a finance check needs: your banks, Stripe and the documents behind each transaction.
What stays where
| Stays in NetSuite | Happens in Rever |
|---|---|
| The general ledger, subsidiaries, vendors, customers and transactions | A mapped copy of the records in scope, reconciled back to the NetSuite trial balance |
| Posting, period locks and your NetSuite roles | Findings, questions and approvals in the Inbox, with the evidence attached |
| Bank reconciliation as your team completes and signs it in NetSuite | Matcher's continuous bank-to-book matching and Investigator's work on the differences |
| Any approved entry or invoice, once posted | Journal's preparation of the entry and the check that it landed once |
Rever never writes to NetSuite. When your team approves an entry, such as an accrual, Journal hands it back as an import file your team loads, then confirms the posting exists once in NetSuite. Approval thresholds and dual approval for material amounts are yours to set.
Which agents work on NetSuite records
| Use case | Lead agent | What it does with the records |
|---|---|---|
| Accounts payable | Spend Guard, with Matcher and Entitlement | Ties each bill to its order, receipt and contract terms, screens the payment run for duplicates and price drift, and recalculates vendor rebates and credits |
| Accounts receivable | Revenue Assurance and Deduction | Checks that delivered work was billed at contract terms and tests each short payment against the evidence |
| Bank reconciliation | Matcher | Reconciles bank, card and processor activity to the books as it lands |
| Balance reconciliation | Matcher | Agrees vendor, customer and intercompany balances line by line |
| Period close | Close Orchestrator, with Journal and Flux Analyst | Keeps tasks and sign-offs moving, prepares accruals and reversals, and explains movements to the transaction |
| Cash forecasting | Cash Pilot | Builds a 13-week cash forecast from reconciled receivables, payables and bank activity |
| Continuous monitoring | Sentinel, with Steward and Auditor | Flags vendor bank-detail changes and unusual payment patterns, watches sync health and tests procedures |
The NetSuite bank reconciliation article walks through how Matcher works beside the reconciliation your team completes in NetSuite. Rever and your ERP answers the questions your ERP admin, IT lead and auditor will ask.
What the zero-day scan does first
Once read-only access is in place and the mappings are approved, the zero-day scan makes the first pass over your NetSuite records. It inventories the extracted populations, periods and source control totals, and records any module or period it could not reach. It compares source and landed journal counts and debit and credit totals by entity, period and account, then reconciles the NetSuite trial balance to Rever's canonical book.
The scan parks records that fail a check, with a reason and an owner. Mapping questions return to Mapping Studio with an Inbox task, connector failures go to Steward, and accounting differences go to the responsible agent as findings. The scan then launches the initial verification and control baseline across the in-scope population, and the initial findings arrive with their evidence. Missing sources and blocked checks stay visible.