Produktdetails werden auf Englisch angezeigt. Übersetzungen folgen in Kürze.
Kurze Fakten
- Preis
- $349.00 USD
- dynamics_365_business_central-Versionen
- —
- Rüstzeit
- 20 Min
- Lizenz
- Einmalig und unbefristet
- Sprachen
- 11 Sprachen
Einmalkauf
Payment Reconciliation & Settlement Matching for Business Central
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.
$349.00USD
Keine Zahlung jetzt. Dies sendet eine Angebotsanfrage an unser Team – wir melden uns per E-Mail mit Preisen und nächsten Schritten.
Hauptfunktionen
Auto-import of settlement and payout files from PSPs and acquirers (CSV, JSON, or direct PSP-API pull), parsed through a configurable field-mapping table so new file layouts need no code change
Per-PSP Settlement Provider setup table that stores parser mappings, default G/L accounts, fee/refund contra accounts and currency per provider
Matching engine that ties payout lines to Sales Invoices, Sales Orders and posted Cust. Ledger Entries using order reference, payment-intent ID, amount and configurable date/amount tolerances
Automatic split of net deposits into gross sales, processor fees and refunds, each posted to its designated G/L account via a General Journal
Exception Worklist page (AL list page) for unmatched, partially matched and disputed items, with manual match, reassign and write-off actions
Multi-PSP and multi-currency handling tied to Business Central currency and exchange-rate tables, with per-provider rounding tolerance
Scheduled imports and matching runs via the Business Central Job Queue, with run logs and a per-batch reconciliation summary
Event-subscriber posting hooks (no modification of Microsoft base objects) so the extension stays upgrade-safe across BC updates
Dedicated permission sets separating import, matching, posting and setup so finance roles get least-privilege access
Drill-down from any matched line back to the source invoice, ledger entry and the originating settlement file row for full audit traceability
Reconciliation status dashboard cue group showing matched / unmatched / exception counts and value per import batch
Optional OData/REST API page exposure of reconciliation results for Power BI or Power Platform reporting
Über dieses Produkt
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.
Warum Payment Reconciliation & Settlement Matching for Business Central wählen
Auto-import of settlement and payout files from PSPs and acquirers (CSV, JSON, or direct PSP-API pull), parsed through a configurable field-mapping table so new file layouts need no code change
Per-PSP Settlement Provider setup table that stores parser mappings, default G/L accounts, fee/refund contra accounts and currency per provider
Matching engine that ties payout lines to Sales Invoices, Sales Orders and posted Cust. Ledger Entries using order reference, payment-intent ID, amount and configurable date/amount tolerances
Automatic split of net deposits into gross sales, processor fees and refunds, each posted to its designated G/L account via a General Journal
Exception Worklist page (AL list page) for unmatched, partially matched and disputed items, with manual match, reassign and write-off actions
Multi-PSP and multi-currency handling tied to Business Central currency and exchange-rate tables, with per-provider rounding tolerance
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.
Was Sie bekommen
- A per-tenant Business Central AL extension (.app) built to your exact PSPs and chart-of-accounts mapping, installed on your environment by ECOSIRE
- Settlement Provider setup configured for each of your live PSPs/acquirers with field mappings, default and contra G/L accounts, and currency
- Job Queue entries configured for scheduled import and matching, plus the Exception Worklist and reconciliation dashboard pages
- Dedicated permission sets assigned to your finance and admin roles
- Source AL project (table/page extensions, event subscribers, parser codeunits) delivered to your team or kept under ECOSIRE maintenance, per your choice
- Admin and finance-user guide covering import, exception handling, posting and adding a new PSP, plus a post-install handover session
Für wen das ist
Finance / Accounts Receivable Manager
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.
Business Central Administrator / IT Lead
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.
Controller / Finance Director
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.
Installationsübersicht
Von ECOSIRE herunterladen
Kaufen Sie die Lizenz auf ecosire.com und laden Sie die ZIP-Datei des Payment Reconciliation & Settlement Matching for Business Central-Moduls von Ihrem Konto-Dashboard herunter.
Auf Odoo hochladen
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).
Installieren Sie das Modul
Aktivieren Sie den Entwicklermodus, öffnen Sie „Apps“, klicken Sie auf „Apps-Liste aktualisieren“, suchen Sie nach „Payment Reconciliation & Settlement Matching for Business Central“ und klicken Sie auf „Installieren“.
Einstellungen konfigurieren
Ö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.
Verifizieren und live gehen
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.
Wie Payment Reconciliation & Settlement Matching for Business Central im Vergleich abschneidet
| Kriterium | ECOSIRE | Benutzerdefinierter Build | Konkurrent | Odoo Native |
|---|---|---|---|---|
| Auto-import of PSP/acquirer settlement files (CSV/JSON/API) | ||||
| Auto-match payouts to invoices, orders and ledger entries with tolerances | ||||
| Automatic gross / fee / refund split posted to the correct G/L accounts | ||||
| Exception worklist for unmatched and disputed items | ||||
| Configured to your exact PSPs and chart of accounts at delivery | ||||
| Upgrade-safe (event subscribers, no base-object changes) | ||||
| Installed and supported on your tenant by the builder | ||||
| Multi-PSP and multi-currency handling out of the box |
Häufig gestellte Fragen zu Payment Reconciliation & Settlement Matching for Business Central
+Is this a Microsoft AppSource app I can install instantly?
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.
+How long does delivery take after purchase?
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.
+How do ongoing support and updates work?
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.
+Which PSPs and acquirers can you support?
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.
+Will it modify our existing Business Central objects or data?
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.
+Can the reconciliation results feed Power BI or the Power Platform?
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.
Warum Kunden ECOSIRE vertrauen
SOC 2 ausgerichtet
DSGVO-konform
Sichere Stripe-Zahlung
30 Tage Geld-zurück-Garantie
Lebenslange Updates
LGPL-3.0-Lizenz
Angebot anfordern
Payment Reconciliation & Settlement Matching for Business Central
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.
- Auto-import of settlement and payout files from PSPs and acquirers (CSV, JSON, or direct PSP-API pull), parsed through a configurable field-mapping table so new file layouts need no code change
- Per-PSP Settlement Provider setup table that stores parser mappings, default G/L accounts, fee/refund contra accounts and currency per provider
- Matching engine that ties payout lines to Sales Invoices, Sales Orders and posted Cust. Ledger Entries using order reference, payment-intent ID, amount and configurable date/amount tolerances
- Automatic split of net deposits into gross sales, processor fees and refunds, each posted to its designated G/L account via a General Journal