Stripe and NetSuite: Paid-Invoice Reconciliation Template

A nightly workflow that matches recently paid Stripe invoices against open NetSuite invoices, marks the reconciled ones, and flags any mismatches for review.

What It Builds

A Schedule trigger fires every night and pulls the invoices Stripe paid that day. A Loop walks each one while NetSuite Connector nodes look up the matching open invoice by number and amount. When the totals agree, the workflow marks the NetSuite invoice as paid; when they do not, a Condition node routes the record into a flagged list so your finance team can investigate. Spojit posts a short summary at the end.

The Prompt

Paste this into Miraxa and it builds the workflow, connecting the tools for you:

Every night at 1am, get all Stripe invoices marked paid in the last 24 hours. For each one, find the matching open invoice in NetSuite by invoice number and total amount. If the amounts match, mark the NetSuite invoice as paid. If they do not match or no NetSuite invoice is found, add it to a mismatch list. At the end, send me an email summarizing how many were reconciled and listing the mismatches.

Connectors Used

  • Schedule trigger - runs the reconciliation nightly on a cron you set.
  • Stripe - reads recently paid invoices.
  • NetSuite - looks up open invoices and marks matches as paid.
  • Send Email - delivers the reconciliation summary.

Customize It

Change the lookback window or the run time in the prompt, match on a custom field instead of invoice number, or set an amount tolerance (for example, allow a few cents of rounding) before a record counts as a mismatch. You can also route the mismatch list to a Slack channel instead of email.

Tips

  • Give the NetSuite connection write scope so it can update invoice status, not just read.
  • Use a NetSuite Connector node in Direct mode for the lookup and update steps to keep them exact and AI-cost free.
  • Currency and partial payments are common mismatch causes: include the currency in the match and review flagged records before bulk-applying changes.

Related

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.