Automatic bidirectional sync between Stripe and ERPNext. When a Stripe payment succeeds, an ERPNext Sales Invoice is created automatically. Customer records stay in sync across both systems.
Customers pay via Stripe but your books are in ERPNext. Someone has to manually create Sales Invoices every time a subscription payment comes in. Mistakes, delays, and reconciliation headaches.
Automatic bidirectional sync between Stripe and ERPNext. When a Stripe payment succeeds, an ERPNext Sales Invoice is created automatically. Customer records stay in sync across both systems.
Stripe webhook fires on subscription events (payment, cancellation, etc.)
Plugin matches Stripe customer to ERPNext customer record
Sales Invoice is auto-created in ERPNext with correct items and amounts
Subscription lifecycle events update ERPNext records in real-time
Here's what it looks like in action:
Every successful Stripe payment automatically creates a Sales Invoice in ERPNext. No manual entry.
Bidirectional — create a customer in either system and it appears in both.
Track trial, active, past due, cancelled, and expired states in ERPNext.
Stripe events processed instantly. No batch jobs or overnight syncs.
Python Frappe app, webhook handlers, README, email support
⚠️ Requirements: ERPNext v14+ / Frappe v14+, Stripe account with API keys
Yes — Stripe refund events create credit notes in ERPNext.
Maps Stripe products to ERPNext items. Configure the mapping once.
No. One-time purchase.
Questions? Email [email protected] · 14-day money-back guarantee