Stripe and NetSuite: Refund Reconciliation Template
When a refund is issued in Stripe, this Spojit template writes a matching credit memo or refund record into NetSuite against the original invoice, so your ledger stays accurate without manual re-entry.
What It Builds
A Webhook Trigger listens for Stripe refund events. A Connector node in Direct mode looks up the original charge and invoice, then a second Connector node creates a credit memo or refund record in NetSuite tied to that invoice. A Condition node skips anything already reconciled so refunds are never double-posted.
The Prompt
Paste this into Miraxa and it builds the workflow, connecting the tools for you:
Build a workflow that triggers on a Stripe refund webhook. Look up the original charge and the matching NetSuite invoice for that customer and order, then create a NetSuite credit memo (or refund record) against that invoice for the refunded amount. Skip the refund if a credit memo already exists, and post a note to Slack with the customer name, invoice number, and refunded amount.Connectors Used
- Stripe - the refund webhook that starts the run (Webhook Trigger with HMAC verification).
- NetSuite - creates the credit memo or refund record against the original invoice.
- Slack - optional confirmation note for the finance channel.
Customize It
Swap the Slack note for a Send Email step, change which NetSuite record type you create (credit memo versus refund), or add the currency and reason fields to the posted summary. You can also adjust the matching keys (customer, order, or charge ID) that link the refund to the right invoice.
Tips
- Give the NetSuite connection write access to credit memos and refund records, plus read access to invoices for the lookup.
- Keep both NetSuite steps in Direct mode for exact, repeatable records with no AI cost.
- The Condition idempotency check matters when Stripe retries a webhook: it prevents a second credit memo for the same refund.