How to reconcile Stripe with NetSuite: the complete guide, and which connector you need

To reconcile Stripe with NetSuite, you match each Stripe payout to one NetSuite bank deposit, and you build that deposit from the individual payments, refunds, disputes, and fees the payout contains. The payout is a net batch, not a sale. Record the customer payments to Undeposited Funds (or a Stripe clearing account), group them into a deposit per payout, add fees and dispute costs as separate lines, and confirm the deposit total and date match your bank statement. Then reconcile the Stripe balance itself at month-end, so money still in transit is accounted for.

That's the whole method in one paragraph. The rest of this guide is the detail that makes it work every month: the Stripe reports to use, the NetSuite setup, a worked payout with journal entries, how timing, fees, refunds, chargebacks, and currencies break the tie-out, and the question most teams eventually ask — do you need Stripe's own connector, a dedicated reconciliation tool, or something else?

Key takeaways

• One Stripe payout should equal one NetSuite deposit. Stripe's Payout reconciliation report groups every transaction into the automatic payout that settled it, which is the backbone of the tie-out.

• Payouts are net. Each payout equals charges minus refunds, disputes, and fees. Book the gross sales and the fees separately, or your revenue and your fee expense are both wrong.

• Timing gaps are normal. Stripe's standard US settlement timing is two business days, so month-end always leaves some cash in transit that needs its own reconciliation.

• Stripe's own connector, the Stripe Connector for NetSuite, requires automatic payouts, creates a bank deposit per payout, and records fees as deposit lines. Without automatic payouts, its deposit automation doesn't work.

• Choose a connector on exception handling, not features. Every serious option creates deposits; they differ in what happens when a payout doesn't tie.

• Loopfour, the deterministic finance workflow automation platform, runs the payout-to-deposit match as governed workflow, holds any payout that doesn't tie, and routes it to an approver with the evidence attached.

Why Stripe and NetSuite don't tie out on their own

Stripe and NetSuite don't tie out on their own because they record different events at different times. NetSuite records invoices and customer payments. Stripe records balance transactions and then sends a payout that nets many of them together. Your bank only sees the payout.

Five things break the tie-out, and every guide in this cluster covers one of them in depth:

• Netting. One deposit represents many transactions and fees. See why Stripe payouts don't tie to the NetSuite bank deposit.

• Timing. Payments settle days after they're captured, so deposit dates never match transaction dates. See why Stripe deposit dates never match transaction dates.

• Fees, refunds, and chargebacks recorded wrongly or not at all. See how to record fees, refunds, and chargebacks so the amounts tie.

• Currency conversion between the charge currency and the settlement currency. See how to reconcile multi-currency Stripe payouts in NetSuite.

• Payments stranded in Undeposited Funds because the deposit step never happened. See why payments get stuck in Undeposited Funds after a Stripe payout.

The Stripe data you reconcile from

Reconcile from Stripe's balance transactions and payouts, not from the charges list. Every movement in your Stripe balance — charge, refund, dispute, fee, payout — is a balance transaction with a gross, fee, and net amount. Payouts settle batches of them.

The Payout reconciliation report

Stripe's Payout reconciliation report matches each payout in your bank account with the batch of transactions it settles. Stripe's documentation is specific about the prerequisite: the report is available only if you use automatic payouts (or you're a platform whose connected accounts do). If you use manual payouts, Stripe points you to the Balance report instead, because Stripe can't tell which transactions a manual payout contains.

The report has four sections that map directly to your reconciliation:

Download the itemized version. The itemized payout reconciliation export includes one row per balance transaction with automatic_payout_id, gross, fee, net, reporting_category, charge_id, customer_id, and optional metadata columns. That payout ID is the key that ties Stripe to NetSuite.

Data timing

Stripe computes reporting data daily, and a day's activity is normally available in reports by 12:00 pm the next day. Stripe also notes that reports for a first automatic payout after manual payouts, or for payouts more than 180 days after the previous one, can take longer. Build your reconciliation schedule around that: reconcile yesterday's payouts, not today's.

Instant payouts

Stripe states that it can't identify which transactions are included in an instant payout, because you control its timing and amount. If you use instant payouts, you reconcile them against your transaction history yourself. If clean reconciliation matters more than speed, reserve instant payouts for genuine exceptions.

How to set up NetSuite for Stripe reconciliation

Set up NetSuite before you reconcile anything: decide where Stripe payments land, which accounts receive fees and dispute costs, and which bank account receives each payout currency. Four decisions cover most of it.

Undeposited Funds or a clearing account? Both work. Undeposited Funds is NetSuite's native holding account and is what Stripe's own connector uses. A dedicated Stripe clearing account is easier to reconcile against the Stripe balance at month-end, because nothing else posts to it. Whichever you choose, the balance in that account should equal payments recorded but not yet paid out — which is the Stripe-side number you'll check at month-end.

If you run NetSuite OneWorld, subsidiaries must line up. Stripe's connector documentation notes that the fee account's subsidiary must match the bank account's subsidiary, and the subsidiary on customer payments must match the bank account's subsidiary, unless you use a parent subsidiary with Include Children enabled. The same rule applies to a manual process.

How to reconcile Stripe with NetSuite, step by step

The manual process has eight steps, from exporting the payout detail to reconciling the Stripe balance at month-end. Automation changes who does each step, not the steps themselves.

1. Export the itemized payout reconciliation

Download the itemized Payout reconciliation report for the period, including metadata that links charges to NetSuite invoices. If your integration stores the NetSuite invoice number or internal ID in payment metadata, add that column. It turns matching from a search into a lookup.

2. Confirm every charge has a NetSuite customer payment

For each charge row, find the NetSuite customer payment it created, or create one. The payment should be for the gross charge amount, applied to the right invoice, and posted to Undeposited Funds or your clearing account. If a Stripe charge has no NetSuite payment, the deposit you build in step four won't include it, and the payout won't tie.

3. Record refunds and disputes

Record each refund as a credit memo and customer refund, and each dispute as the reversal of the original payment plus a dispute fee. Stripe's documentation explains what happens when a dispute opens: Stripe debits your balance for the disputed amount plus a dispute fee. If you later win, the disputed amount comes back; for businesses outside Mexico, Stripe states the dispute-received fee is non-refundable. Each of those movements appears in a payout, and each needs a NetSuite record.

4. Create one bank deposit per payout

Create a NetSuite bank deposit dated the payout's arrival date, select the customer payments and refunds in that payout, and add fees as negative lines. In NetSuite's deposit form, that means selecting the payments from Undeposited Funds and entering fees and dispute costs in the Cash Back section against your fee accounts. Stripe's connector does the same thing: it records Stripe fees and fee refunds as Cash Back and Other Deposit lines, and dispute fees as Cash Back lines.

5. Check the deposit total against the payout

The deposit total must equal the payout's net amount to the cent. If it doesn't, something in the payout is missing from NetSuite, or something in NetSuite doesn't belong in this payout. Don't save a deposit that doesn't tie; find the difference first.

6. Match the deposit to the bank statement

Match the NetSuite deposit to the bank line for that payout. Stripe's payout reconciliation data includes a trace_id field where supported, which banks use to locate specific transfers. When the amount and date agree and the trace ID matches, the bank-side reconciliation is done.

7. Handle failed payouts

If a payout fails, reverse or delete the deposit you created for it and wait for the retry. Stripe's failed payouts export includes a retried_payout_id, which tells you which later payout picked up the same transactions.

8. Reconcile the Stripe balance at month-end

At month-end, reconcile the Stripe balance to your NetSuite clearing or Undeposited Funds balance. Use Stripe's Balance summary and Ending balance reconciliation sections: the ending balance is money Stripe holds for you that hasn't paid out yet. Your NetSuite holding account should show the same net position, allowing for fees you've recorded. If it doesn't, the difference is a real reconciling item, not a timing one.

The flow in one line: charges and refunds → NetSuite payments to Undeposited Funds → payout arrives → one deposit per payout with fee lines → deposit matched to bank → month-end Stripe balance matched to holding account.

Book a workflow review to see this flow running on your own Stripe account and NetSuite subsidiaries.

Worked example: one payout, start to finish

Here is a single Stripe payout reconciled to NetSuite with real numbers. The amounts are illustrative; your fees depend on your Stripe pricing.

Payout po_1Qx… arrives in your US operating account on March 5 for $9,365.00. The itemized payout reconciliation shows:

The entries behind it

Customer payments (12 charges, recorded as they occur):

Refund (credit memo applied, then customer refund issued through Stripe):

Dispute opened ($50 disputed amount):

Bank deposit for the payout (net effect of clearing the payout's payments, refund, and dispute from Undeposited Funds; fees in Cash Back):

Check the tie-out: across these entries, Undeposited Funds nets to zero for this payout: $10,000.00 in, $250.00 and $50.00 out for the refund and dispute, and the remaining $9,700.00 cleared by the deposit. The deposit's bank debit of $9,365.00 equals the payout and the bank line. Revenue stays gross at $10,000.00 less the $250.00 refund; fees sit in expense at $335.00.

If the dispute is later won, Stripe returns the $50.00 in a future payout: debit Undeposited Funds, credit disputes receivable. The $15.00 dispute-received fee stays an expense, consistent with Stripe's statement that it's non-refundable outside Mexico. If it's lost, move the $50.00 from disputes receivable to chargeback losses.

Timing differences: why deposit dates never match transaction dates

Stripe deposit dates never match transaction dates because of settlement timing: funds from a charge become available days after capture, then pay out on your schedule. Stripe's documentation lists standard settlement timing by country; for the United States it's two business days. Stripe also notes that the payout schedule doesn't change settlement timing — with daily automatic payouts and T+2 timing, today's payout contains transactions captured two business days ago.

At month-end, the gap becomes a balance. Charges captured on the last two business days of March pay out in April. Those amounts sit in Undeposited Funds or your clearing account at March 31, and Stripe's Ending balance reconciliation shows them as unsettled. That's a reconciling item you explain, not an error you fix. The trap is treating it as an error and forcing the March deposit to include April's payout.

Fees, refunds, and chargebacks: recording them so the amounts tie

Record every fee, refund, and dispute as its own line or transaction, at gross, so the payout ties and revenue stays correct. Netting fees against revenue is the most common cause of a Stripe-to-NetSuite variance that no one can explain.

Stripe's connector documentation lists fee types worth separating: payment processing fees, Stripe fees for software and services, application fees charged by third-party apps, and, on Interchange Plus pricing, network fees and Stripe fees recorded separately. Map each to an account deliberately; the default of "all fees in one account" hides changes in your cost of payments.

Multi-currency Stripe payouts in NetSuite

When a customer pays in one currency and Stripe settles in another, the NetSuite payment is in the charge currency and the deposit is in the settlement currency. Stripe's connector documentation gives an example: a customer payment of 75 EUR that Stripe deposits as 100 USD appears in NetSuite as a EUR customer payment of 75 and a deposit showing the converted 100.

Three details decide whether multi-currency payouts tie:

• Which exchange rate you use. Stripe's connector uses Stripe's exchange rate on payments and refunds instead of NetSuite's, which Stripe says helps eliminate the FX gain or loss that would otherwise post when transactions reconcile to the deposit. A manual process using NetSuite's daily rate will create small FX differences on every payout.

• Where currency conversion fees go. Stripe bundles conversion fees with processing fees by default; the connector can split them onto their own deposit line if you enable the relevant setting.

• Which bank account receives each currency. If you settle in more than one currency, each needs its own NetSuite bank account, and each payout deposits to the account in its currency.

Customer currencies matter too. Stripe's documentation notes that NetSuite requires a currency to be added to a customer before that customer can pay in it; otherwise the sync fails. That's a master-data check to add before a new currency goes live.

Why payments get stuck in Undeposited Funds

Payments get stuck in Undeposited Funds when the deposit step never runs for their payout. The payment was recorded; the money arrived; nobody grouped them.

The usual causes:

• Manual payouts. Stripe's connector documentation is direct: with manual payouts, deposit automation doesn't work, payments aren't mapped to specific charges, and everything stays in Undeposited Funds for you to manage.

• A payout that failed validation because one transaction in it didn't match NetSuite, so no deposit was created.

• Payments recorded before the connector's sync start date, which the connector can't include.

• Duplicates, where a payment was recorded twice and only one was deposited.

Age your Undeposited Funds balance weekly. Anything older than your settlement timing plus a few days is a problem to investigate, not a timing item.

Running a three-way match: Stripe, the general ledger, and the bank

A three-way match proves the same money agrees in three places: Stripe's payout records, NetSuite's deposit, and the bank statement. It's the control auditors understand immediately.

Store the Stripe payout ID on every NetSuite deposit. It's the one field that makes the three-way match a lookup instead of a hunt. For the full procedure, see how to run a three-way match between Stripe, the general ledger, and the bank.

Which connector do you need: Stripe's own, or a dedicated reconciliation tool?

Most teams reconciling Stripe with NetSuite at volume use a connector; the question is which one. Every serious option creates NetSuite deposits from Stripe payouts. They differ in who builds and supports it, how it treats exceptions, and how much control finance has over the rules.

Stripe Connector for NetSuite

Stripe's own connector is the most complete out-of-the-box option. Stripe's documentation describes deposit automation that runs daily: the connector creates payments and refunds for each Stripe transaction in Undeposited Funds, creates a bank deposit when Stripe notifies it that a payout has arrived, adds fees for processing, currency conversion, disputes, and refunds as separate lines to expense accounts you specify, and checks that the deposit total and date match your bank statement. It validates every transaction in a payout — not already deposited, posted to Undeposited Funds, and matching amounts — before creating the deposit.

Its requirements are specific. The connector requires automatic payouts, and Stripe recommends a daily schedule: its documentation notes NetSuite can create and send up to 10,000 transactions, and daily payouts keep the volume per payout lower. Implementation starts by contacting Stripe; a free, self-serve version exists, but Stripe notes it accepts payments through a payment link without syncing payments or other data to NetSuite.

Best for: Companies whose Stripe activity is the main source of NetSuite payments and who want Stripe to support the integration.

iPaaS integration apps

Celigo's Stripe–NetSuite app creates a custom payout record and a NetSuite deposit per payout, and posts variances to a designated account. Celigo's documentation states the net amount of the payout will always match the NetSuite deposited amount, with variance records created when transaction amounts don't match or a NetSuite transaction is missing.

That variance account is worth a hard look. It guarantees the deposit ties, but it moves the unexplained difference somewhere else. Someone still needs to review and clear that account every month.

Best for: Teams already running Celigo for other NetSuite integrations.

Summary-sync tools

Summary-sync tools post aggregated entries instead of one record per transaction. Synder, for example, documents a per-payout summary mode for Stripe that's supported for Oracle NetSuite and designed to match payout deposits exactly.

The trade-off is detail. A summary entry ties to the bank, but it doesn't apply payments to individual NetSuite invoices, so AR and cash application need a separate process.

Best for: High-volume, low-ticket businesses that don't invoice customers individually in NetSuite.

Custom builds

A custom build reads Stripe balance transactions and payouts through Stripe's API and writes NetSuite records through SuiteTalk or REST. It fits unusual models, such as platforms with complex Connect flows, and it makes your engineers the permanent owners of validation, retries, and every NetSuite release.

Best for: Companies with a dedicated integration engineer and requirements no product meets.

Governed finance workflows

Loopfour runs Stripe-to-NetSuite reconciliation as a deterministic workflow on the Loopfour Studio canvas: payout received → pull itemized transactions → validate each against NetSuite → build the deposit with mapped fee lines → confirm against the bank → hold and route anything that doesn't tie. The difference is what happens at the exception. A connector emails an admin or posts to a variance account. Loopfour holds the run, sends the specific failing transaction to a named approver in Slack with the Stripe and NetSuite records side by side, and records the decision in the execution tree.

We build and maintain the workflow on your existing Stripe account and NetSuite subsidiaries, alongside Cash Application, AR & Dunning, and month-end close workflows that use the same data.

Best for: Finance teams, fractional CFO firms, and AI or SaaS companies whose Stripe volume has outgrown manual review, and whose auditors want to see who approved each exception.

How to choose a Stripe–NetSuite reconciliation approach

Choose on three questions: how you're paid, how many exceptions you see, and who you want owning the fix when a payout doesn't tie.

Connectors win on speed to value, and that's a real advantage. If your payouts tie most days and a variance email is enough, a connector is the right answer.

The case for governed workflows starts where exceptions do. A connector knows how to build a deposit. It doesn't know your policy on a late refund, a disputed charge from a parent account, or a payout that spans a closed period. A variance account ties the numbers but hides the reason. Loopfour ties the numbers and keeps the reason, because every exception is resolved by a person you named, under a rule you approved, with the record kept. Loopfour is SOC 2 Type II certified, encrypts data with AES-256 at rest and TLS 1.3 in transit, and never uses your data to train models.

Frequently asked questions

How do I reconcile Stripe payouts in NetSuite? Record each Stripe charge as a NetSuite customer payment to Undeposited Funds, then create one bank deposit per Stripe payout that selects those payments and any refunds, with processing and dispute fees entered as Cash Back lines. The deposit total must equal the payout net amount, and the deposit should match the bank statement line for that payout.

Why doesn't my Stripe payout match the NetSuite deposit? Usually because the payout is net of fees, refunds, and disputes that weren't recorded in NetSuite, or because a charge in the payout has no NetSuite payment. Timing and currency conversion also cause mismatches. Stripe's itemized Payout reconciliation report shows exactly which transactions each automatic payout contains.

Do I need automatic payouts to reconcile Stripe with NetSuite? For report-based and connector-based reconciliation, yes. Stripe's Payout reconciliation report requires automatic payouts, and the Stripe Connector for NetSuite's deposit automation doesn't work with manual payouts. With manual payouts, you reconcile against the Balance report and your own transaction records.

Should Stripe fees be recorded as an expense or netted against revenue? Record them as an expense. Record customer payments at the gross charge amount and enter fees as separate lines on the deposit to a payment processing fee account. Netting fees against revenue understates revenue and makes the payout impossible to tie.

What is the Stripe Connector for NetSuite? It's Stripe's own integration that automates recording Stripe charges, refunds, disputes, fees, and payouts in NetSuite, including one bank deposit per payout. It requires automatic payouts, and implementation begins by contacting Stripe. A free self-serve version only supports accepting payments through a payment link without syncing data to NetSuite.

How do I handle Stripe chargebacks in NetSuite? When a dispute opens, record the reversal of the disputed amount and the dispute fee, both of which Stripe debits from your balance. If you win, record the returned amount when it arrives in a later payout; Stripe states the dispute-received fee is non-refundable for businesses outside Mexico.

Can Loopfour reconcile Stripe with NetSuite? Yes. Loopfour runs payout-to-deposit reconciliation as a deterministic workflow on your existing Stripe and NetSuite accounts, validates every transaction before the deposit is created, and routes any payout that doesn't tie to a named approver in Slack. Every run is recorded in an execution tree.

Conclusion

Reconciling Stripe with NetSuite comes down to one rule and a handful of disciplines. The rule: one Stripe payout equals one NetSuite deposit, built from the gross transactions and fees it contains. The disciplines: use Stripe's itemized payout data, keep revenue gross and fees in expense, record refunds and disputes as they happen, treat month-end timing as a reconciling item, and store the payout ID on every deposit.

Pick the tool that matches your volume and your exceptions. When the exceptions are what keep your controller up at close, pick the approach that shows who resolved each one and why.

Tell us the one workflow your team dreads. We will show it running — deterministic, permissioned, and auditable.

Book a demo.

Sources

• Stripe Docs: Payout reconciliation report

• Stripe Docs: Stripe payouts in NetSuite

• Stripe Docs: Deposit automation (Stripe Connector for NetSuite)

• Stripe Docs: Multiple currencies with Stripe and NetSuite

• Stripe Docs: How disputes work

• Stripe Docs: Receive payouts

• Celigo Help Center: Reconcile your Stripe payouts

Related reading

• Why your Stripe payouts don't tie to the NetSuite bank deposit

• Why Stripe deposit dates never match transaction dates, and how to reconcile across the gap

• Stripe-to-NetSuite variances: how to record fees, refunds, and chargebacks so the amounts tie

• How to reconcile multi-currency Stripe payouts in NetSuite

• Why payments get stuck in Undeposited Funds after a Stripe payout

• How to run a three-way match between Stripe, the general ledger, and the bank