A build-to-order AL extension that turns Business Central into a recurring-revenue engine: subscription plans, automated cycle invoicing via job queue, and auto-charge of stored cards, SEPA, or ACH with dunning and proration. Built, installed per-tenant, and supported by ECOSIRE. One-time license from $399.00 USD for Dynamics 365 BC (build-to-order) — includes 12 months of updates and support.

A build-to-order AL extension that turns Business Central into a recurring-revenue engine: subscription plans, automated cycle invoicing via job queue, and auto-charge of stored cards, SEPA, or ACH with dunning and proration. Built, installed per-tenant, and supported by ECOSIRE.
Keine Zahlung jetzt. Dies sendet eine Angebotsanfrage an unser Team – wir melden uns per E-Mail mit Preisen und nächsten Schritten.
Recurring-revenue businesses outgrow manual sales invoices fast. Business Central's core Recurring Sales Lines and standard sales documents can repeat line items, but they do not model true subscriptions: plan lifecycles, proration on mid-cycle changes, usage metering, automated card capture, or dunning on failed payments. This is a custom AL extension that ECOSIRE builds, installs, and supports on your Business Central environment to close that gap.
Dedicated Subscription Plan, Subscription, and Billing Schedule tables built in AL, linked to standard Customer and Item records via table relations
Job Queue entry that runs each billing cycle automatically and generates posted sales invoices on the dates you define
Auto-charge of stored card tokens, SEPA Direct Debit, or ACH against your chosen gateway (Stripe Billing, GoCardless, Adyen, or acquirer tokenization API) over AL HttpClient
Proration engine that calculates correct invoice amounts for mid-cycle upgrades, downgrades, and cancellations against the plan calendar
Configurable dunning sequences with retry cadence, escalation, and customer email notifications on failed payments
Usage-based and tiered billing with metered counters that can be posted via the BC REST/OData API or Power Platform flows
We deliver it as a per-tenant extension (or AppSource-style managed app where you prefer), built with table and page extensions over the Customer, Sales Header, and Payment data, plus dedicated Subscription Plan, Subscription, and Billing Schedule tables. Event subscribers hook the invoice-posting and payment flows; a Job Queue entry runs the billing cycle on your schedule and generates posted sales invoices automatically. Proration, upgrades, downgrades, and cancellations are calculated against the plan calendar so mid-term changes invoice correctly.
For collection, we integrate the gateway you already use — Stripe Billing, GoCardless, Adyen, or your acquirer's tokenization API — over HTTPS from AL HttpClient, charging stored card tokens, SEPA Direct Debit, or ACH on each cycle. Failed payments enter a configurable dunning sequence with retry cadence and customer notifications. Usage-based and tiered pricing are supported via metered counters posted through the BC REST/OData API or Power Platform.
Because it is build-to-order, scope is honest and finite: we confirm your plans, gateway, and tax handling, build against your sandbox, and hand over permission sets, documentation, and source. Nothing here is an instant download — it is a delivered, supported engineering project.
Runs billing for a software subscription business on Business Central and needs invoices and card charges to fire automatically each cycle, with dunning handling the failures so AR stops chasing them by hand.
Sells retainers and tiered service plans, needs proration when clients upgrade mid-month and a clean record of who is active, paused, or past-due without exporting to spreadsheets.
Implements BC for a subscription client and needs a supported, source-delivered extension rather than hand-rolling recurring billing in AL or stitching together a generic AppSource app that does not match the gateway or tax rules.
Kaufen Sie die Lizenz auf ecosire.com und laden Sie die ZIP-Datei des Recurring Billing & Subscriptions Payments for Business Central-Moduls von Ihrem Konto-Dashboard herunter.
Extrahieren Sie die ZIP-Datei in Ihren Odoo-Ordner für benutzerdefinierte Add-ons auf dem Server (oder laden Sie sie über „Apps“ > „Aus Datei installieren“ auf Odoo.sh/Runbot hoch).
Aktivieren Sie den Entwicklermodus, öffnen Sie „Apps“, klicken Sie auf „Apps-Liste aktualisieren“, suchen Sie nach „Recurring Billing & Subscriptions Payments for Business Central“ und klicken Sie auf „Installieren“.
Öffnen Sie das neue Menü, fügen Sie Ihren ECOSIRE-Lizenzschlüssel ein, verbinden Sie alle externen Anmeldeinformationen (Shopify, Amazon, Stripe usw.) und speichern Sie.
Führen Sie den integrierten Verbindungstest aus, synchronisieren Sie Ihre ersten 10 Datensätze und planen Sie den wiederkehrenden Cron. Wenden Sie sich an den Support, wenn etwas fehlschlägt.
| Kriterium | ECOSIRE | Benutzerdefinierter Build | Konkurrent | Odoo Native |
|---|---|---|---|---|
| True subscription plan and lifecycle model (trial, active, paused, cancelled) | ||||
| Automated cycle invoicing via Job Queue | ||||
| Auto-charge stored cards / SEPA / ACH through your gateway | ||||
| Proration on mid-cycle upgrades and downgrades | ||||
| Dunning and failed-payment retry sequences | ||||
| Usage-based and tiered billing | ||||
| Built, installed, and supported on your environment with source handover | ||||
| Matched to your exact gateway, tax, and plan rules |
Typical delivery is 3 to 5 weeks after we confirm scope: your plan structures, the payment gateway, tax handling, and dunning rules. We build against your Business Central sandbox first, run a billing cycle end-to-end with you, then install on production. This is an engineering project, not an instant AppSource download, so the timeline reflects real configuration and testing against your environment.
We hand over the full AL source and provide a support window after go-live for fixes and adjustments. Because it is built as an extension using event subscribers (not modifications to base objects), it survives Microsoft's monthly and major BC releases cleanly. We offer an optional maintenance retainer to re-test and re-publish against each major BC upgrade and to handle gateway API version changes.
We integrate the gateway you already use. We have built against Stripe Billing, GoCardless, and Adyen, and can work with most acquirers that expose a tokenization and charge API. Methods include stored card tokens, SEPA Direct Debit, and ACH. We never store raw card numbers in Business Central; only gateway tokens and references are held, and secrets live in BC isolated storage.
By default we deliver it as a per-tenant extension installed directly on your environment, which is the fastest path and gives you the source. If you would rather have it packaged as a managed AppSource-style app for stricter change control, we can build it that way too. Both run as proper AL extensions and do not alter base application objects.
Yes. The extension exposes subscription and billing data through the Business Central REST/OData API, and we can optionally synchronize status to Dataverse so it surfaces in Dynamics 365 CRM, customer portals, and Power BI. Usage metering can be pushed in through the same API or via Power Platform flows for usage-based plans.
A build-to-order AL extension that turns Business Central into a recurring-revenue engine: subscription plans, automated cycle invoicing via job queue, and auto-charge of stored cards, SEPA, or ACH with dunning and proration. Built, installed per-tenant, and supported by ECOSIRE.