A build-to-order AL extension that connects Tabby and Tamara BNPL to Microsoft Dynamics 365 Business Central — capturing installment plans on orders, reconciling settlements and gateway fees, and handling refunds and cancellations. Built, installed as a per-tenant extension, and supported by ECOSIRE on your BC environment. Built to order by ECOSIRE for Dynamics 365 BC (build-to-order) — indicative price from $499.00 USD; request a quote for a scoped proposal.
App manifest
Built around your workflow
A build-to-order AL extension that connects Tabby and Tamara BNPL to Microsoft Dynamics 365 Business Central — capturing installment plans on orders, reconciling settlements and gateway fees, and handling refunds and cancellations. Built, installed as a per-tenant extension, and supported by ECOSIRE on your BC environment.
No DIY setup — a working app, built, installed and supported by ECOSIRE.
Start with a one-time build price. We scope it with you at kickoff.
ECOSIRE builds, configures and installs it on your Dynamics 365 Business Central.
You go live in about 2–4 weeks, with a post-launch support window.
GCC shoppers increasingly expect to split a purchase across Tabby or Tamara at checkout — but Business Central has no native concept of a Buy-Now-Pay-Later provider, deferred settlement, or per-transaction gateway fees. The result is usually a spreadsheet and a monthly reconciliation headache: the customer paid in full at the till, but the cash lands days later, net of fees, in a separate payout.
The Tabby & Tamara BNPL Connector closes that gap. It is a custom AL extension that ECOSIRE builds for your specific Business Central setup and installs as a per-tenant extension on your environment — sandbox first, then production. It registers Tabby and Tamara as payment providers, captures the chosen installment plan against the BC sales order and posted invoice, and tracks each BNPL transaction through its lifecycle from authorization to settlement.
When provider payouts arrive, the connector matches settlement lines back to the originating invoices, books the gateway fee to a configurable G/L account, and posts the net receipt against the customer or a clearing account so your Bank and Customer Ledger Entries reconcile cleanly. Refunds and order cancellations flow back through the same provider APIs and post the corresponding correcting entries.
Because this is build-to-order, the extension is shaped around your chart of accounts, currencies (AED, SAR and other GCC currencies), number series, and posting conventions — not a one-size-fits-all AppSource listing. ECOSIRE handles the provider API credentials, table and page extensions, event subscribers, permission sets, and a Job Queue entry to poll settlements on a schedule. You get a working integration on your tenant, source-available AL, and a named team to support and extend it. This is honest custom delivery, not an instant download — typical lead time is a few weeks from kickoff to production go-live.
Owns the chart of accounts and monthly close. Needs BNPL settlements, gateway fees, and net receipts to reconcile automatically inside Business Central instead of being rebuilt from provider portals and spreadsheets.
Runs the online and in-store checkout where Tabby and Tamara are offered. Wants the installment plan and provider reference captured on every order so fulfilment, refunds, and cancellations stay in sync with the ERP.
Responsible for the BC tenant, extensions, and permissions. Prefers an upgrade-safe per-tenant extension using event subscribers and proper permission sets over ad-hoc code changes, and wants a supported partner rather than orphaned custom work.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Tabby & Tamara BNPL checkout integration with Business Central | Included | Partial support | Partial support | |
| Installment plan captured on the BC sales order and posted invoice | Included | Partial support | Partial support | |
| Automated settlement and gateway-fee reconciliation to G/L | Included | Partial support | Partial support | |
| Refund, partial-refund, and cancellation handling via provider APIs | Included | Partial support | Partial support | |
| Multi-currency GCC (AED, SAR) support aligned to your setup | Included | Partial support | Partial support | |
| Upgrade-safe per-tenant extension (table/page extensions + event subscribers) | Included | Partial support | Included | |
| Tailored to your chart of accounts, number series, and posting conventions | Included | Included | Not included | |
| Source-available AL with named ongoing support and no lock-in | Included | Partial support | Not included |
This is built to order, not an instant AppSource download. Typical lead time is a few weeks from kickoff to production go-live, depending on the complexity of your posting setup and how quickly Tabby/Tamara API credentials and a BC sandbox are available. ECOSIRE develops the AL extension, validates it in your sandbox, then installs it as a per-tenant extension on production. We confirm a firm timeline during scoping.
Merchant accounts and API credentials for Tabby and Tamara (sandbox and production), access to a Business Central sandbox environment, and your chart-of-accounts and posting details — the G/L accounts for BNPL clearing and gateway fees, currencies in use, and number series. We work from there; you don't need any AL development capability in-house.
It is installed as a per-tenant extension on your tenant — built specifically for your configuration rather than published as a generic AppSource listing. It uses table/page extensions and event subscribers rather than modifying core objects, so it is upgrade-safe across Business Central's monthly and major releases. You receive the AL source.
A Job Queue entry polls the provider settlement reports on your schedule. The connector matches each payout line to its originating invoice, posts the net receipt, and books the gateway fee to its own G/L account. Refunds and partial refunds call the provider refund API and post correcting Customer Ledger and Bank entries; cancellations void the authorization and reverse any provisional postings. Unmatched items surface on a reconciliation page for finance review.
Yes. Every build includes a defined post-go-live warranty period with a named ECOSIRE contact for fixes. Beyond that we offer ongoing support and maintenance — adapting to Tabby/Tamara API changes, Business Central platform upgrades, and new requirements such as additional currencies, providers, or reporting. Because you hold the AL source, you are never locked in.
Yes. The BNPL transaction and settlement data lives in standard Business Central tables, which can be exposed via the BC API/OData and surfaced to Dataverse. From there you can build Power BI dashboards on BNPL volume, fees, and settlement timing, or trigger Power Automate alerts on exceptions. We scope the specific fields and flows you need during the build.
A build-to-order AL extension that connects Tabby and Tamara BNPL to Microsoft Dynamics 365 Business Central — capturing installment plans on orders, reconciling settlements and gateway fees, and handling refunds and cancellations. Built, installed as a per-tenant extension, and supported by ECOSIRE on your BC environment.