Connect Stripe to NetSuite

Payments land in Stripe. The books live in NetSuite. Reconciling the two is usually a spreadsheet of exported charges, a manual match against open invoices, and a fee adjustment someone calculates at month-end. It is slow, and it is where the bank balance and the GL drift apart.

• Each paid invoice is matched to its open AR invoice in NetSuite and recorded as a customer payment, keyed on IDs carried in Stripe metadata
• Each payout is reconciled to a bank deposit, with gross, fees, and refunds each on the correct account, so the NetSuite bank balance matches the real one
• Anything the mapping cannot resolve, a missing invoice ID or an unexpected balance-transaction type, lands in a review queue rather than a wrong entry
• Every entry is an ordered run log, so a disputed reconciliation has a record of the Stripe object and the GL posting it produced

The reconciliation flow finance turns on first.

Every paid Stripe invoice booked against the right open NetSuite invoice

Triggered on invoice.paid, with a branch to the review queue for anything that will not match.

1. 1Trigger: Stripe Event received for invoice.paid, carrying the invoice, its customer, and amount_paid in cents.
2. 2Identify: read customer.metadata.netsuite_customer_id and invoice.metadata.netsuite_invoice_id, set when the invoice was created.
3. 3Branch: if either ID is missing, post the invoice to #billing-review with the Stripe link and stop.
4. 4Fees: read the related balance transaction for fee and net.
5. 5Write: NetSuite Create record on CustomerPayment, applying it to the named invoice, mapping the fields below. The processing fee posts as a separate expense line to the Merchant Fees account.
6. 6Idempotency: the write uses the Stripe event ID as the payment's external ID, so a redelivered event does not post a second payment.
7. 7Payout reconcile: a second flow on payout.paid reads the payout's balance transactions and creates a NetSuite deposit to the Stripe clearing account, with a line per charge and a negative line for total fees.

The starting map for the invoice.paid to NetSuite Customer Payment step.

• Payments on invoices. Paid invoices become customer payments applied to the matching AR invoice, with fees posted separately. (Stripe to NetSuite)
• Payout reconciliation. Each payout becomes a bank deposit to the Stripe clearing account, with gross, fees, and refunds on the correct accounts. (Stripe to NetSuite)
• Refunds and disputes. A refund creates a customer refund or credit memo. A dispute creates a journal entry to the disputes account, reversed on resolution. (Stripe to NetSuite)
• Invoice creation (optional). Where NetSuite is the billing system, a new NetSuite invoice creates the matching Stripe invoice and stores the cross-IDs in metadata. (NetSuite to Stripe)

The same controls apply to this sync as to every other Neblex workload.

• Ordered run log. Every entry is an event log with the Stripe object, the match logic, and the GL posting. Replay a run without re-creating the payment.
• Review queue. Unmatched invoices, unexpected balance-transaction types, and currency mismatches queue for a person rather than posting a wrong entry.
• Scoped access. Stripe uses a restricted API key with read on invoices, charges, and balance transactions. NetSuite uses a role limited to payments, deposits, and journals.
• Environments. Build against Stripe test mode and a NetSuite sandbox, then promote the same flow to live and production.