A Stripe payout is a net figure. Behind it sit the gross charges, the fees, the refunds, the chargebacks and the timing of each settlement, and your ledger has to agree with all of them. Rever reads Stripe for processor activity over a read-only connection, beside your ERP and your bank feeds, and its agents tie the three together.
How Rever connects to Stripe
The Stripe connection is a direct, deterministic integration that reads and never writes, like every Rever connection. No agent holds your Stripe credentials, and the agents can read only what the connection provides, so your Stripe data stays unchanged. Rever reads the ERP or QuickBooks books and your banks through their own connectors, or a common database you already maintain.
No agent moves money. A refund, credit or correction your team approves is prepared with its evidence for your team to action.
What stays where
| Stays in Stripe and your ledger | Happens in Rever |
|---|---|
| Charges, refunds, disputes and payouts in Stripe | The processor settlement checked from gross sales to the bank receipt |
| Revenue and fee entries in your ERP or QuickBooks | Each payout tied to the receivables it settles, with differences surfaced |
| Your Stripe account settings and payout schedule | Findings, questions and approvals in the Inbox, each with its evidence |
| Any approved correction, once posted | Journal's preparation of the entry and the check that it posted once |
Which agents work on Stripe activity
| Check | Lead agent | Evidence compared |
|---|---|---|
| Processor settlement | Revenue Assurance and Matcher | The gross sales population, the Stripe settlement and the bank receipt: gross to net, fees, refunds, chargebacks and settlement timing |
| Cash application | Matcher | Receipts, processor payouts and partial payments tied to the invoices they settle |
| Bank reconciliation | Matcher, with Investigator | Bank and processor activity reconciled to the books, including many-to-one settlements, fees and timing differences |
| Billing completeness | Revenue Assurance | Invoices checked against the agreement and delivery or usage evidence, where those sources are connected |
| Cash forecasting | Cash Pilot | Expected receipts in the 13-week cash forecast compared with what landed |
| Data health | Steward | Payout feed freshness and failed syncs, so a stale feed shows as a health item |
What the zero-day scan does first
With read-only access in place, the zero-day scan inventories the Stripe populations and periods it extracted, records anything it could not reach, and lands the accepted records with their source identifiers, guarding against duplicate delivery. Matcher then receives the landed population for transaction reconciliation against the bank and the ledger.
Differences arrive as findings with the evidence behind them: a payout that does not agree with the charges less fees and refunds, a refund recorded twice, a fee booked to the wrong account. Missing periods and blocked checks stay visible.
For the ledger side, see NetSuite, QuickBooks and Dynamics 365, Rever and your ERP and NetSuite bank reconciliation.