A custom-built AL extension that adds a recurring contract engine, usage/metered billing, mid-cycle proration, dunning, and two-way Stripe Billing synchronization to Microsoft Dynamics 365 Business Central — built, installed per-tenant, and supported by ECOSIRE. One-time license from $499.00 USD for Dynamics 365 BC (build-to-order) — includes 12 months of updates and support.

A custom-built AL extension that adds a recurring contract engine, usage/metered billing, mid-cycle proration, dunning, and two-way Stripe Billing synchronization to Microsoft Dynamics 365 Business Central — built, installed per-tenant, and supported by ECOSIRE.
Sin pago ahora. Esto envía una solicitud de presupuesto a nuestro equipo; te responderemos por correo con precios y próximos pasos.
Business Central handles invoices well but has no native concept of a subscription lifecycle: it cannot model a recurring contract, meter usage, prorate a mid-cycle plan change, or keep a payment processor in sync. This extension closes that gap.
Subscription Contract engine: a custom AL table with table/page extensions on Customer and Sales Invoice modeling plan, billing interval, term, and lifecycle status
Recurring invoice run driven by the Business Central Job Queue — generates and posts cyclical sales invoices with the correct posting groups, dimensions, and currency
Usage / metered billing: ingest consumption records via an API page (OData v4) and bill plans on actual usage per cycle
Two-way Stripe Billing sync of Subscriptions, Prices, Customers, and Invoices using AL HttpClient calls and signed webhook ingestion
Mid-cycle proration for upgrades, downgrades, and cancellations, with credits and charges reflected in both BC and Stripe
Dunning sequences on failed Stripe charges — configurable retry cadence, customer notifications, and contract suspension rules
ECOSIRE builds, installs, and supports a per-tenant AL extension that adds a full subscription engine to your existing Business Central environment. A new Subscription Contract table (with table/page extensions on Customer and Sales Invoice) drives a recurring billing run through the Job Queue: each cycle generates posted sales invoices, applies proration for upgrades, downgrades, and cancellations, and ingests metered usage so consumption-based plans bill on actuals.
The Stripe integration is genuinely two-way. Using AL HTTP clients against the Stripe Billing API plus signed webhook ingestion through a Business Central API page (OData v4), the extension keeps Stripe Subscriptions, Prices, and Customers aligned with BC contracts. A successful Stripe charge marks the BC invoice paid and applies the customer ledger entry; a BC plan change pushes a prorated update back to Stripe. Failed payments trigger a configurable dunning sequence with revenue-recognition schedules so deferred revenue is released correctly.
Because this is build-to-order, the engine is scoped to your plans, currencies, tax setup, and posting groups — not a generic AppSource template you bend to fit. ECOSIRE delivers permission sets, the deployed extension on sandbox then production, a Stripe webhook endpoint, and handover documentation. This is not an instant marketplace download: it is a scoped engagement with an honest lead time, deployed as a per-tenant extension you fully own, with optional ongoing support.
Owns recurring revenue accuracy and needs proration, dunning, and revenue schedules to reconcile cleanly between Business Central and Stripe without month-end spreadsheet patchwork.
Runs a usage-based or tiered subscription model and wants metered billing and plan changes to flow automatically from Stripe into BC invoices and the customer ledger.
Responsible for the BC tenant and wants a clean per-tenant extension with proper permission sets, Job Queue control, and idempotent webhooks rather than fragile point-to-point scripts.
Compre la licencia en ecosire.com y descargue el módulo ZIP Subscription & Recurring Billing with Stripe Sync for Business Central desde el panel de su cuenta.
Extraiga el ZIP en su carpeta de complementos personalizados de Odoo en el servidor (o cárguelo a través de Aplicaciones > Instalar desde archivo en Odoo.sh/runbot).
Active el modo de desarrollador, abra Aplicaciones, haga clic en Actualizar lista de aplicaciones, busque Subscription & Recurring Billing with Stripe Sync for Business Central y presione Instalar.
Abra el nuevo menú, pegue su clave de licencia de ECOSIRE, conecte cualquier credencial externa (Shopify, Amazon, Stripe, etc.) y guarde.
Ejecute la prueba de conexión integrada, sincronice sus primeros 10 registros y programe el cron recurrente. Póngase en contacto con el soporte si algo falla.
| Criterio | ECOSIRE | Construcción personalizada | Competidor | Odoo Nativo |
|---|---|---|---|---|
| Native subscription contract lifecycle (plan, term, status) in BC | ||||
| Two-way Stripe Billing sync with signed, idempotent webhooks | ||||
| Usage / metered billing ingested via BC API page (OData v4) | ||||
| Mid-cycle proration synced across BC and Stripe | ||||
| Tailored to your exact posting groups, currencies, and tax setup | ||||
| Built, deployed per-tenant, and supported for you (no in-house AL team needed) | ||||
| Dunning sequences and revenue recognition schedules |
This is a build-to-order engagement, not an instant AppSource download. After a short scoping call we confirm your plans, currencies, tax setup, and Stripe configuration, then build the AL extension. Typical delivery is a few weeks depending on the number of plans and proration rules. We deploy first to your Business Central sandbox for validation, then promote the same per-tenant extension to production and configure the live Stripe webhook. You receive the .app file, permission sets, and handover documentation.
You own the deployed per-tenant extension. We offer an optional support and maintenance arrangement covering bug fixes, compatibility with Business Central major-version upgrades (the AL runtime and API surface change across releases), Stripe API version changes, and small enhancements such as new plans or dunning rules. Without a support plan, the extension keeps running as delivered; you can re-engage us for any changes later.
It is delivered as a per-tenant (PTE) extension installed directly on your environment, so it can be tailored to your exact posting groups, dimensions, and Stripe setup. It is not published to the public AppSource marketplace. This gives you customization freedom; the trade-off versus an AppSource app is that updates come from ECOSIRE rather than an automatic marketplace channel.
Webhook handling is idempotent and signature-verified. Each Stripe event carries an identifier we record before posting, so a retried or duplicate webhook delivery is recognized and skipped. AL event subscribers on the posting routines ensure customer ledger entries and payment application happen exactly once, and reconciliation logic flags any mismatch between a Stripe Subscription/Invoice and its BC contract for review.
Yes. Usage records are ingested through a Business Central API page (OData v4) and aggregated per billing cycle, so metered plans bill on actual consumption. Mid-cycle upgrades, downgrades, and cancellations are prorated, with the resulting credit or charge reflected in both the BC invoice and the corresponding Stripe Subscription update, keeping the two systems aligned for that cycle.
A custom-built AL extension that adds a recurring contract engine, usage/metered billing, mid-cycle proration, dunning, and two-way Stripe Billing synchronization to Microsoft Dynamics 365 Business Central — built, installed per-tenant, and supported by ECOSIRE.