Recurring Billing & Subscriptions Payments for Business Central

Recursos Principais

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

Event subscribers on invoice-posting and payment-application events so the engine extends, never patches, core BC behavior

Subscription lifecycle management: trial, active, paused, past-due, and cancelled states with audit history

Customer and subscription pages (page extensions) showing next bill date, lifetime value, payment method on file, and dunning status

Dedicated permission sets for billing administrators and read-only finance roles, plus telemetry to Application Insights

Optional Dataverse / Power Platform synchronization so subscription status surfaces in CRM, portals, and Power BI

Webhook handling for asynchronous gateway events (payment succeeded, failed, refunded, mandate cancelled) with idempotent processing

Feito sob encomenda, pronto para você

Sem configuração por conta própria — um app funcional criado, instalado e com suporte da ECOSIRE.

Você faz o pedido

Comece com um preço único de desenvolvimento. Definimos o escopo com você no início.

Nós criamos e instalamos

A ECOSIRE cria, configura e instala no seu Dynamics 365 Business Central.

No ar + suporte

Você entra no ar em cerca de 2–4 semanas, com um período de suporte pós-lançamento.

Sobre este Produto

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.

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.

O que você ganha

A per-tenant Business Central extension (.app) built in AL, installed on your sandbox then production environment

Gateway integration configured against your live Stripe Billing, GoCardless, Adyen, or acquirer account with secrets stored in BC isolated storage

Job Queue setup for automated billing cycles, with cadence and posting behavior tuned to your finance process

Permission sets, configuration pages, and a setup wizard for plans, schedules, and dunning rules

Full AL source code in a Git repository handed over to you, with build and deployment instructions

Admin and end-user documentation plus a recorded walkthrough of the billing, proration, and dunning flows

Para quem é isso

SaaS Finance Lead

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.

Managed Services Operations Manager

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.

Business Central Functional Consultant

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.

Como Recurring Billing & Subscriptions Payments for Business Central se compara

Critério	ECOSIRE	Construção personalizada	Concorrente
True subscription plan and lifecycle model (trial, active, paused, cancelled)	Incluído	Suporte parcial	Incluído
Automated cycle invoicing via Job Queue	Incluído	Suporte parcial	Incluído
Auto-charge stored cards / SEPA / ACH through your gateway	Incluído	Suporte parcial	Suporte parcial
Proration on mid-cycle upgrades and downgrades	Incluído	Suporte parcial	Suporte parcial
Dunning and failed-payment retry sequences	Incluído	Suporte parcial	Incluído
Usage-based and tiered billing	Incluído	Suporte parcial	Suporte parcial
Built, installed, and supported on your environment with source handover	Incluído	Incluído	Não incluído
Matched to your exact gateway, tax, and plan rules	Incluído	Incluído	Suporte parcial

Perguntas frequentes sobre Recurring Billing & Subscriptions Payments for Business Central

How long does delivery take, since this is build-to-order?

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.

What happens with ongoing support and Business Central updates?

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.

Which payment gateways and methods do you support?

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.

Is this a per-tenant extension or an AppSource app?

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.

Can subscription data flow into Power BI, Dataverse, or our CRM?

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.