NetSuite bank reconciliation stays in NetSuite when you add Rever. Your team keeps matching and reconciling there, and Rever reads NetSuite through a read-only connection that leaves your records as they are. NetSuite stays the system of record and the place entries post. Rever's agents work beside it: Matcher reconciles bank and NetSuite activity to its documents as it lands, and Journal prepares the entries a person approves.
What Rever reads, and what it leaves alone
Your NetSuite administrator will ask what Rever touches and what breaks at the next upgrade. The connection is a direct, deterministic integration that reads and never writes, in Rever's words "rather than an MCP server or an agent holding credentials", so the agents can read only what the connection provides. The source data stays unchanged, and the roles and saved searches your team built stay as your administrator set them.
Rever reads the records it needs from NetSuite, from your banks and, if you bill through it, from Stripe. Mapping Studio maps those records into Rever's canonical record of the books, and each number in Records links back to the NetSuite document it came from.
Rever never posts to NetSuite. Journal prepares the entry with its support, a person with the authority approves it in the Inbox, and the approved entry comes back as an import file your team loads; Journal then checks the resulting record. Journal cannot approve its own entry. Rever and the ERP you already run takes your IT lead's questions on certifications, hosting and the security pack.
How bank reconciliation works in NetSuite
A NetSuite bank reconciliation starts with the bank's data. Your team brings it in through a bank feed, which pulls transactions from the bank on a schedule, or by importing the statement file the bank sends. The bank lines then sit in NetSuite beside the transactions your team recorded against that account.
NetSuite applies matching rules to pair each bank line with a NetSuite transaction on amount, date and reference, and someone on your team matches the lines the rules leave. For a line with nothing behind it in the ledger, such as a bank fee or interest earned, your team records the transaction and matches it.
For each statement period, your team reconciles the account to the bank statement. The matched transactions should bring the NetSuite balance to the statement's ending balance, and the person reconciling explains any difference before marking the statement reconciled. In current NetSuite releases, your team does the matching on the Match Bank Data page and the reconciliation on the Reconcile Account Statement page.
NetSuite keeps each reconciled statement, and its reconciliation reports show what cleared in the period and what stayed outstanding. Your auditor tests the reconciliation from those records.
NetSuite bank reconciliation and continuous matching
Matcher reads the same bank activity, together with the NetSuite records behind each line and, where you use it, Stripe. It checks amounts, dates, references and identities across bank, processor and ledger records as they land, including many-to-one settlements, fees and timing differences. If a line does not agree, Investigator traces it to the exact transaction, party or timing cause and recommends the correction. Steward watches bank-feed freshness and failed syncs, so a stale statement shows up as a health item instead of a clean reconciliation that is wrong.
The two cover different ground. NetSuite's reconciliation pairs bank lines with ledger transactions and ties the ledger to the statement balance for a period. Matcher works through the month and follows a line past the ledger to its source documents. Your team keeps reconciling in NetSuite, and at period end the person doing it has Matcher's matches and Investigator's findings open beside the reconciliation, so a line the rules left unmatched arrives with its explanation.
A processor payout shows the difference. The bank receives one deposit, net of fees and refunds, and your team matches it in NetSuite to the ledger entry that records it. Matcher ties the same deposit to each charge and refund inside it, and each charge to the invoice it paid, so a fee or a refund with no entry behind it surfaces as an item someone can work before it ages in a suspense account. If a bank fee or a missed deposit needs an entry, Journal prepares it and a person approves it before it reaches NetSuite. Rever's bank reconciliation page sets out the agents on this job.
The close, the trail and the auditor
At month-end Close Orchestrator keeps the month-end close checklist moving and routes sign-off to your Inbox with any blockers in view. Journal prepares the accruals with their support, and each one waits for approval before your team loads it into NetSuite. Rever's period close page covers the rest of the close.
NetSuite keeps its own audit trail of changes to its records. Rever records the agents' side: every approval, question and send-back is a decision in the Inbox, with what happened next, and every number drills down to the finding, the workpaper, the record and the verified outcome. Evidence keeps the statement lines, invoices and postings linked to the reconciliation, and the workpaper downloads in Excel for review and audit.
Start with one entity: NetSuite, the main operating bank accounts and Stripe if you bill through it. Set up the read-only connections with Rever, and the zero-day scan reconciles the period and lists every unexplained difference.