A per-tenant Business Central extension that imports PSP and acquirer settlement files, auto-matches payouts to invoices and orders, splits gross versus fees versus refunds to the correct G/L accounts, and surfaces an exception worklist for everything that does not tie out. Built, installed and supported by ECOSIRE. Built to order by ECOSIRE for Dynamics 365 BC (build-to-order) — indicative price from $349.00 USD; request a quote for a scoped proposal.
Manifesto do app
Feito em torno do seu fluxo de trabalho
A per-tenant Business Central extension that imports PSP and acquirer settlement files, auto-matches payouts to invoices and orders, splits gross versus fees versus refunds to the correct G/L accounts, and surfaces an exception worklist for everything that does not tie out. Built, installed and supported by ECOSIRE.
Sem configuração por conta própria — um app funcional criado, instalado e com suporte da ECOSIRE.
Comece com um preço único de desenvolvimento. Definimos o escopo com você no início.
A ECOSIRE cria, configura e instala no seu Dynamics 365 Business Central.
Você entra no ar em cerca de 2–4 semanas, com um período de suporte pós-lançamento.
If your finance team manually reconciles card and PSP settlements against Business Central sales, this extension removes the spreadsheet. ECOSIRE builds it to order as a per-tenant AL extension installed directly on your Business Central environment (cloud SaaS or on-prem) — not a generic AppSource download.
Settlement and payout files (Stripe, Adyen, PayPal, Checkout.com, Worldpay, or your acquirer's bank-deposit report) are imported through a configurable parser. We model each PSP as a record in a new Settlement Provider setup table, with field mappings stored so CSV/JSON/PSP-API column layouts are decoded without code changes per upload. Imports run on demand or on a schedule via the Job Queue.
The matching engine reconciles each payout line to its originating Sales Invoice, Sales Order, or posted Cust. Ledger Entry using order reference, payment intent ID, amount and date tolerances. When a deposit nets gross sales against processor fees and refunds, the engine splits the lines and posts fees to your designated expense account and refunds to the correct contra account through a General Journal, so the bank deposit reconciles cleanly to the penny.
Anything that does not auto-match lands on an Exception Worklist page — a filterable list page (built as an AL page object) where finance can match manually, reassign, or write off. Multi-PSP and multi-currency are first-class: each provider keeps its own currency and exchange handling tied to BC's currency tables.
Delivered with dedicated permission sets, event-subscriber-based posting hooks (no core object modification), and a short admin guide. Because it ships as an extension, it survives Microsoft's monthly and major BC updates. ECOSIRE scopes your exact PSPs and G/L mapping before build, then installs and supports it.
Owns month-end and needs every PSP deposit to tie out to invoices and the G/L. Lives in the exception worklist, approves write-offs, and wants fees and refunds posted correctly without rebuilding spreadsheets each cycle.
Responsible for a clean, upgrade-safe tenant. Cares that this is an event-subscriber-based extension (no base-object changes), scoped by permission sets, scheduled through the Job Queue, and that it survives Microsoft's monthly BC releases.
Wants accurate, auditable revenue and processor-cost figures. Values the drill-down from G/L back to the settlement file row and the Power BI/OData feed for monitoring reconciliation health across multiple PSPs and currencies.
| Critério | ECOSIRE | Construção personalizada | Concorrente | Odoo nativo |
|---|---|---|---|---|
| Auto-import of PSP/acquirer settlement files (CSV/JSON/API) | Incluído | Suporte parcial | Suporte parcial | |
| Auto-match payouts to invoices, orders and ledger entries with tolerances | Incluído | Suporte parcial | Suporte parcial | |
| Automatic gross / fee / refund split posted to the correct G/L accounts | Incluído | Suporte parcial | Suporte parcial | |
| Exception worklist for unmatched and disputed items | Incluído | Não incluído | Suporte parcial | |
| Configured to your exact PSPs and chart of accounts at delivery | Incluído | Incluído | Não incluído | |
| Upgrade-safe (event subscribers, no base-object changes) | Incluído | Suporte parcial | Incluído | |
| Installed and supported on your tenant by the builder | Incluído | Suporte parcial | Não incluído | |
| Multi-PSP and multi-currency handling out of the box | Incluído | Suporte parcial | Suporte parcial |
No. This is a build-to-order extension. ECOSIRE scopes your specific PSPs, settlement file formats and G/L mapping, builds the AL extension to match, and installs it as a per-tenant extension on your Business Central environment. There is no instant AppSource download — it is configured to your tenant and supported by us.
Typical lead time is 2 to 4 weeks from the scoping call, depending on how many PSPs you reconcile, the complexity of your settlement file formats and your chart-of-accounts mapping. A single-PSP build is on the shorter end; multi-PSP, multi-currency scopes take longer. We confirm a firm date once requirements are agreed.
Because it ships as an extension using event subscribers rather than modifying Microsoft base objects, it is designed to survive BC monthly and major updates. ECOSIRE provides post-install support, fixes any issue caused by a Microsoft platform change, and can add new PSPs or adjust G/L mappings on request. Ongoing support terms are agreed at purchase.
Any provider whose settlement or payout data you can export as CSV/JSON or pull via API — for example Stripe, Adyen, PayPal, Checkout.com, Worldpay, or a bank/acquirer deposit report. Each provider is configured as its own Settlement Provider record with its own parser mapping, so adding a new one later does not require rebuilding the extension.
No core objects are altered. The extension adds its own tables, pages, parser codeunits and event subscribers, and posts through standard General Journals. Posting is gated behind dedicated permission sets, and every matched line drills back to its source invoice, ledger entry and settlement file row for audit.
Yes. We can expose the reconciliation results as an OData/REST API page so Power BI, Power Automate or a Dataverse integration can read matched, unmatched and exception data for dashboards and alerts. This is included as an optional deliverable when you need cross-system reporting.
A build-to-order Odoo localization that loads Algeria's full wilaya and commune hierarchy with bilingual French and Arabic names, wired into partner addresses and reporting. ECOSIRE builds, installs, and supports it after your quotation.
A build-to-order 2Checkout (Verifone) payment integration for ERPNext, giving global digital-goods sellers card acceptance, 45+ local payment methods, multi-currency checkout, and reconciled invoices. ECOSIRE scopes, builds, installs, and supports it on your ERPNext v15/v16 instance.
A build-to-order 2Checkout / Verifone payment gateway for Magento 2 and Adobe Commerce: localized checkout in 12 languages, iDEAL, Giropay and regional methods, multi-currency global selling, subscription billing and tax/invoicing automation — engineered, installed and supported by ECOSIRE.
A per-tenant Business Central extension that imports PSP and acquirer settlement files, auto-matches payouts to invoices and orders, splits gross versus fees versus refunds to the correct G/L accounts, and surfaces an exception worklist for everything that does not tie out. Built, installed and supported by ECOSIRE.