Surcharge & Convenience Fee Engine for Business Central

Recursos Principais

Card-brand and region-aware surcharge rules in a configurable Surcharge Rule table (Visa, Mastercard, Amex, Discover; per state/region)

Clear engine-level distinction between a card surcharge (credit-only, capped) and a flat convenience fee (alternative channel)

Automatic, separately-labelled fee line injected onto the posted invoice or receipt at the correct G/L account via posting event subscribers

Configurable caps (e.g. surcharge ceiling) and automatic exemptions for debit cards and regulated regions where surcharging is prohibited

Disclosure text rendered on payment pages and printed on documents so the fee is visible before the customer commits

AL table extensions on Sales Header / Service Header carrying fee basis, fee type, and disclosure state

Page extension surfacing the calculated fee and disclosure preview directly on payment and document pages

Dedicated permission set so only authorized roles can edit surcharge rules, caps, and exemptions

Fee data exposed over the BC REST/OData API for storefront checkout or Power Platform / Dataverse integration

Optional job queue entry to reconcile fee postings and flag mis-applied or exempted transactions

Telemetry events written to Application Insights for surcharge calculation auditing

Sandbox-first deployment: built and validated on your sandbox, then published to production as a per-tenant extension

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

Card processing fees quietly erode margin on every electronic payment your Business Central tenant takes. The Surcharge & Convenience Fee Engine lets US and MENA merchants offset that cost the compliant way — distinguishing a true card surcharge (assessed only on credit, capped, never on debit) from a flat convenience fee (charged for an alternative payment channel), and enforcing the rules automatically so your finance team never has to remember which states or regions are off-limits.

This is not an instant AppSource download. ECOSIRE builds the engine as a per-tenant AL extension, scoped to your Business Central environment, your card-brand mix, and the jurisdictions you actually trade in. We install it on your sandbox first, validate against your real payment and posting flows, then publish to production.

Under the hood it ships as a clean AL app: table extensions on Sales Header / Service Header to carry fee basis and disclosure state, a page extension that surfaces the calculated fee and disclosure text on payment and document pages, and event subscribers on posting routines that inject a separate, clearly-labelled fee line onto the invoice or receipt at the correct G/L account. Rules live in a configurable Surcharge Rule table — card brand, region/state, fee type, percentage or flat amount, cap, and exemption flags (debit cards, regulated regions) — all governed by a dedicated permission set.

Disclosure text renders on pay pages and prints on documents so the surcharge is visible before the customer commits, satisfying the core card-network disclosure requirement. Everything stays inside Business Central — no third-party middleware, no data leaving your tenant. Where you need it, we expose fee data over the BC REST/OData API for your storefront or Power Platform flows. ECOSIRE owns the build, the BC version upgrades, and ongoing support.

O que você ganha

A per-tenant AL extension (.app) built for your Business Central version, installed on your sandbox then published to production

Configured Surcharge Rule set matching your card-brand mix and the US states / MENA regions you trade in

Dedicated permission set and role assignment for surcharge administration

Disclosure text templates wired into payment pages and document print layouts

G/L account mapping and posting setup for the fee line, validated against your chart of accounts

Optional BC REST/OData endpoint or Power Platform connector exposing fee data for external checkout

Configuration and admin handover documentation plus a walkthrough session for your finance team

Source AL app package and a defined support and BC-upgrade window covered by ECOSIRE

Para quem é isso

Finance / Controller at a US BC merchant

Wants to recover card processing cost on credit-card sales without falling foul of state-level surcharge bans or card-network caps, and needs the fee posted cleanly to its own G/L account for reconciliation.

MENA e-commerce or services operator on Business Central

Charges a convenience fee on certain online payment channels and needs region-aware rules plus customer-facing disclosure that holds up across the jurisdictions they sell into.

BC administrator / IT lead

Needs the capability delivered as a governed per-tenant AL extension with a proper permission set and OData access — not a fragile manual customization — and wants ECOSIRE to own version upgrades.

Como Surcharge & Convenience Fee Engine for Business Central se compara

Critério	ECOSIRE	Construção personalizada	Concorrente
Card-brand and region/state-aware surcharge rules	Incluído	Suporte parcial	Suporte parcial
Enforced surcharge vs convenience-fee distinction with caps and exemptions	Incluído	Suporte parcial	Suporte parcial
Customer-facing disclosure text on pay pages and printed documents	Incluído	Suporte parcial	Suporte parcial
Automatic separate fee line at a dedicated G/L account via posting subscribers	Incluído	Incluído	Suporte parcial
Built, installed, and supported on your tenant with BC-upgrade maintenance	Incluído	Não incluído	Suporte parcial
Tailored to your exact jurisdictions and card mix (no generic preset)	Incluído	Incluído	Não incluído
BC REST/OData and Power Platform / Dataverse exposure for checkout	Incluído	Suporte parcial	Suporte parcial

Perguntas frequentes sobre Surcharge & Convenience Fee Engine for Business Central

How long until the engine is live, and is this an AppSource app I just download?

It is build-to-order, not an instant AppSource download. After we confirm your card-brand mix, jurisdictions, and posting setup, a typical build is delivered in about 2 to 3 weeks: we develop the AL extension, install and validate it on your Business Central sandbox, then publish to production as a per-tenant extension once you sign off. Complex multi-region rule sets or storefront/Power Platform integration can extend the timeline, and we'll tell you upfront.

Who handles ongoing support and Business Central version upgrades?

ECOSIRE does. Because this ships as a per-tenant AL extension we maintain, your defined support window covers configuration changes (new rules, caps, exemptions), bug fixes, and re-validation against Microsoft's BC major releases so the extension keeps installing cleanly after platform updates. We monitor your environment's update ring and adjust the app ahead of forced upgrades.

Does the engine keep me compliant with surcharging laws and card-network rules?

The engine enforces the controls compliance depends on — credit-only surcharging, debit exemption, configurable caps, region/state exemptions, and pre-commitment disclosure text. We configure those rules to the jurisdictions you specify, but ECOSIRE is not a law firm: you remain responsible for confirming the legality of surcharging in each region with your own counsel, and we update the rule table when you instruct us to.

What is the difference between a surcharge and a convenience fee in this engine, and why does it matter?

A surcharge is assessed specifically on credit-card payments, is capped, and is prohibited on debit and in certain regions — the engine enforces all of that. A convenience fee is a flat charge for using an alternative payment channel and follows different rules. Conflating the two is a common compliance trap, so the engine treats them as distinct fee types with their own rule logic, caps, and disclosure.

Will the fee post correctly and stay inside our Business Central tenant?

Yes. Posting event subscribers inject the fee as a separate, clearly-labelled line at the G/L account you nominate, so it reconciles independently from product revenue. Everything runs inside your BC tenant — no third-party middleware and no payment data leaving Microsoft's environment. Fee data is only exposed externally if you ask us to publish the optional OData endpoint.