Stripe and NetSuite do not talk to each other out of the box. The result for most businesses is a finance team manually exporting Stripe reports, importing them into NetSuite, and spending two days each month reconciling payouts to bank deposits. Celigo solves this with a native Stripe connector that syncs automatically — but the integration requires careful accounting configuration to handle posting periods, multi-currency, payout batching, and ASC 606 deferral correctly. This guide covers how it works, what it costs, and the configuration decisions that determine whether month-end takes two days or two minutes.
NetSuite Stripe Integration — At a Glance
- 3 core flows: Charge (Stripe PaymentIntent → NetSuite paid invoice or Cash Sale); Refund (→ Credit Memo); Payout (→ Bank Deposit with charge/fee line detail that matches your bank statement exactly)
- Real-time: Celigo listens to Stripe webhooks — triggers on payment, refund, and payout events; no polling delay
- Critical setup step: Store the Stripe PaymentIntent ID on the NetSuite invoice at invoice creation (not at payment) — this is what enables charge-to-invoice matching; missing this causes Cash Sales to be created instead
- Cost: $8,000–$12,000 (standard single currency/subsidiary); $12,000–$18,000 (multi-currency/multi-subsidiary); $18,000–$25,000 (Stripe Subscriptions + ASC 606/ARM)
- Timeline: 4–6 weeks standard; 7–10 weeks with Stripe Subscription sync and NetSuite Advanced Revenue Management (ARM)
- ASC 606: Requires NetSuite ARM module — Celigo creates Revenue Arrangements from Stripe charge/subscription events; ARM handles deferral and recognition schedules automatically
How a NetSuite Stripe Integration Works
Celigo listens to Stripe webhook events in real time. When a payment succeeds, a refund is issued, or a payout is sent, Celigo receives the event and triggers the corresponding NetSuite action. The integration runs three primary flows:
- Charge flow: When a Stripe PaymentIntent is confirmed, Celigo looks for a matching open NetSuite invoice using the PaymentIntent ID stored as a custom field. If found, the invoice is marked Paid and a Customer Payment record is created. If no invoice exists, a Cash Sale is created with the charge metadata.
- Refund flow: When Stripe issues a refund, Celigo creates a Credit Memo in NetSuite linked to the original invoice. Partial refunds create a Credit Memo for the refunded amount only. Full refunds void the Customer Payment.
- Payout flow: When a Stripe payout is sent to your bank account, Celigo fetches the full list of balance transactions (charges, refunds, and fees) included in that payout and creates a NetSuite Bank Deposit with each charge as a line item and the Stripe fee as a separate bank charge. The net amount matches your bank statement.
Setting Up the Integration: Step by Step
A Celigo Stripe-NetSuite integration requires configuration in both Celigo and NetSuite before any data can flow. Here are the setup steps at a high level:
- NetSuite custom fields: Create a custom field on Invoice, Cash Sale, and Customer Payment records to store the Stripe PaymentIntent ID. This is the key used to match Stripe events to existing NetSuite records and prevent duplicates.
- Celigo Stripe connector: Authenticate Celigo to your Stripe account using the Stripe restricted API key (not the publishable key). Set up a Stripe webhook endpoint pointing to Celigo's webhook URL for payment_intent.succeeded, charge.refunded, and payout.paid events.
- Celigo NetSuite connector: Authenticate Celigo to NetSuite using Token-Based Auth (TBA) or OAuth 2.0 M2M. Configure the connection to your correct NetSuite account ID and sandbox account for testing.
- Flow configuration: Set up three Celigo flows — charge, refund, and payout — with field mapping from Stripe event properties to NetSuite record fields. Configure the item lookup (what NetSuite revenue account or item each Stripe charge maps to), the subsidiary, and the GL posting account.
- Idempotency: Configure each flow to check for an existing NetSuite record with the matching PaymentIntent ID before creating a new one. Without this, Stripe's webhook retry behavior will create duplicate records when your webhook endpoint is slow to respond.
- Sandbox testing: Run Stripe test events (payment_intent.succeeded, charge.refunded, payout.paid) against your NetSuite sandbox. Validate that records are created correctly, amounts match, and the payout bank deposit reconciles to the expected total.
Stripe Payout Reconciliation: How It Actually Works
This is the part most DIY integrations get wrong. Stripe sends a single bank transfer — the payout — that represents many individual charges minus processing fees. Your bank statement shows one deposit. NetSuite needs to show that one deposit broken down by its component charges so your finance team can reconcile it without manual work.
When the Stripe payout.paid webhook fires, Celigo calls Stripe's Balance Transactions API to fetch the list of all transactions included in that payout. This list includes each charge (with its gross amount), each refund (as a negative amount), and the Stripe fee for the payout period. Celigo creates a NetSuite Bank Deposit where:
- Each charge appears as a positive line item linked to the matching Customer Payment
- Each refund appears as a negative line item linked to the matching Credit Memo
- The total Stripe fee appears as a separate Bank Charge line
- The net total of all lines equals the actual bank deposit amount
With this structure, your NetSuite bank account reconciliation takes minutes: the deposit lines match the bank statement deposit, and every line traces back to a specific Stripe transaction.
Cost and Timeline
A Celigo Stripe-NetSuite integration costs $8,000–$25,000 to implement, depending on scope. Below is a breakdown by integration type.
| Integration type | Implementation cost | Timeline |
|---|---|---|
| Basic charge → invoice + payout reconciliation (single currency, single subsidiary) | $8,000–$12,000 | 4–5 weeks |
| Multi-currency + multi-subsidiary NetSuite | $12,000–$18,000 | 5–7 weeks |
| Stripe Subscriptions + NetSuite ARM revenue recognition (ASC 606) | $18,000–$25,000 | 7–10 weeks |
Celigo platform licensing adds $6,000–$18,000/year depending on the number of active Integration Apps and flow volume. For a single Stripe-NetSuite integration with moderate volume (under 10,000 charges/month), expect $6,000–$9,000/year in platform costs.
Common Errors and How to Fix Them
Duplicate Customer Payments in NetSuite
Cause: Stripe retried a webhook because your Celigo webhook endpoint was slow to respond, and the idempotency check was not in place. Fix: Add a lookup step at the start of the charge flow that searches NetSuite for an existing Customer Payment with the Stripe PaymentIntent ID. If found, skip the creation step and log a note.
Invoice not found — Cash Sale created instead
Cause: The NetSuite invoice does not have the Stripe PaymentIntent ID stored in the custom field, so Celigo cannot match the charge to an existing invoice. This happens when invoices are created in NetSuite without being linked to a Stripe payment session. Fix: Store the Stripe PaymentIntent ID on the invoice at the time of invoice creation (not at payment), either via your Stripe Checkout integration or by passing the PaymentIntent ID as a metadata field when creating the NetSuite invoice.
Payout bank deposit total does not match bank statement
Cause: The payout flow is not including all balance transactions, typically because Stripe's Balance Transactions API is being called with an incorrect payout ID or the fee transactions are being excluded. Fix: Verify that the Celigo payout flow is fetching balance transactions with the correct payout parameter set to the exact payout ID from the webhook payload, and that the fee transaction type (stripe_fee) is included in the deposit as a bank charge line.
Wrong posting period on NetSuite records
Cause: The charge occurred in a closed accounting period, and Celigo is trying to post to the charge date rather than the current open period. Fix: Add explicit period detection logic to the Celigo flow — check whether the target period is open before posting, and fall back to the most recent open period with a memo recording the original charge date.
Frequently Asked Questions
- Does Celigo have a pre-built Stripe connector for NetSuite?
- Yes. Celigo includes a native Stripe connector alongside its certified NetSuite SuiteApp. Entech configures the integration flows — charge-to-invoice matching, refund credit memos, payout reconciliation, and customer sync — and adds the NetSuite-specific accounting logic for your setup.
- How does Stripe payout reconciliation work in NetSuite?
- Celigo listens for the Stripe 'payout.paid' webhook, fetches the complete balance transaction list for that payout, and creates a NetSuite Bank Deposit with each contributing charge as a separate line item and the Stripe processing fee as a Bank Charge. The net amount matches your bank statement exactly.
- How much does a NetSuite Stripe integration cost?
- Implementation runs $8,000–$25,000. A basic charge-invoice-payout sync for single currency and subsidiary runs $8,000–$12,000. Adding multi-currency or ASC 606 Subscription sync increases the cost to $18,000–$25,000. Ongoing Celigo platform licensing adds $6,000–$18,000/year.
- How long does implementation take?
- 4–6 weeks for a standard charge-invoice-payout sync. 7–10 weeks for SaaS implementations with Stripe Subscription sync and NetSuite ARM revenue recognition.
- Can Celigo support ASC 606 revenue recognition from Stripe?
- Yes — with NetSuite's Advanced Revenue Management (ARM) module. Celigo creates NetSuite Revenue Arrangements from Stripe charge or subscription events, with recognition rules per product. ARM handles deferral and recognition schedules automatically once the Revenue Arrangement is correctly structured.
Need this built? Entech Solutions is a certified Celigo partner — we handle discovery, build, testing, and go-live for Stripe-NetSuite integrations and provide ongoing managed support afterward. Get in touch to scope your integration.