Vendor Payment Management & Bank Integration for Business Central

Recursos Principais

SEPA and ISO 20022 pain.001 (.001.09 / .001.03) payment file generation, mapped to your specific bank's schema and validated against its XSD

Direct bank connectivity via the gateway your bank exposes — host-to-host SFTP, EBICS, or bank/aggregator API — implemented with AL HttpClient codeunits

Inbound camt.053 / camt.054 statement import with automatic matching into Bank Account Reconciliation

Unified vendor, employee and customer (refund) payment handling from a single payment workspace

Payment approval workflow built on native BC Approval Entries and workflow events, with multi-step and amount-threshold routing

Table and page extensions on Payment Journal, Vendor, Employee and Bank Account Card — no modification of base objects, fully upgrade-safe

Job Queue automation for scheduled exchange-rate download, file export and statement polling

Remittance advice PDF generation and automated email to vendors per payment run

Secure bank credential storage in Isolated Storage (no secrets in tables or code)

Dedicated permission sets for AP clerks, approvers and administrators following least-privilege design

Payment status tracking — draft, pending approval, exported, acknowledged, settled — with full audit trail

Optional exposure of payment and status data through the BC REST/OData API and Dataverse for Power BI / Power Automate

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

Business Central's core AP gives you the Payment Journal, suggested vendor payments and a generic positive-pay/SEPA export — but most finance teams still hit a wall when their bank wants a specific ISO 20022 pain.001 layout, when payments need a real approval chain, or when statement reconciliation has to round-trip automatically. This extension closes those gaps as a tailored AL solution built for your tenant and your bank.

ECOSIRE engineers it as a per-tenant extension (not a one-size AppSource listing): table and page extensions on the Payment Journal, Vendor, Employee and Bank Account Card; a configurable pain.001.001.09 / .03 export engine mapped to your bank's exact schema; and an approval workflow built on Business Central's native Approval Entries and workflow events so payment batches route to the right approvers before release.

Bank connectivity is implemented against the gateway your bank actually exposes — a host-to-host SFTP drop, an EBICS/API endpoint, or an aggregator — using AL HttpClient calls and codeunits, with secure credentials held in Isolated Storage. Outbound files are signed/exported on a Job Queue entry; inbound camt.053 statements are imported and matched to the Bank Account Reconciliation. Exchange rates download on a schedule, and remittance advice PDFs generate and email per payment run.

Because it is AL, it is upgrade-safe across BC monthly releases, ships with its own permission sets, and can surface payment data through the BC REST/OData API or into Dataverse for Power BI and Power Automate. You buy a one-time build; ECOSIRE scopes your bank format, develops, installs to sandbox then production, and supports it.

O que você ganha

A per-tenant Business Central AL extension (.app) installed to your sandbox and production environments

Bank-format mapping configured and tested against your bank's actual pain.001 schema and XSD

Configured connectivity to your bank gateway (SFTP / EBICS / API) with credentials secured in Isolated Storage

Approval workflow configuration with your approver hierarchy and amount thresholds

Permission sets assigned to your AP, approver and admin user roles

Job Queue entries set up for exchange-rate download, export and statement import

Source code, AL project and deployment package handed over to you

Admin and end-user documentation plus a handover walkthrough session

Para quem é isso

AP Manager

Owns the outbound payment run and wants vendor, employee and customer refunds paid from one place, with a clean approval trail and files the bank accepts on the first try.

Finance Controller / CFO

Needs enforced segregation of duties on payment release, amount-threshold approvals and a complete audit trail for compliance, without bolting on a separate treasury tool.

BC Administrator / IT

Wants an upgrade-safe AL extension with proper permission sets and Isolated Storage for bank credentials — not unsupported base-object modifications or a fragile spreadsheet export.

Como Vendor Payment Management & Bank Integration for Business Central se compara

Critério	ECOSIRE	Construção personalizada	Concorrente
Bank-specific pain.001 mapped to your exact XSD (not a generic template)	Incluído	Suporte parcial	Suporte parcial
Direct bank connectivity (SFTP / EBICS / API) sending payments and importing statements	Incluído	Suporte parcial	Incluído
Unified vendor, employee and customer-refund payment handling	Incluído	Suporte parcial	Suporte parcial
Payment approval workflow on native BC Approval Entries with amount thresholds	Incluído	Suporte parcial	Suporte parcial
Upgrade-safe AL extension with dedicated permission sets and Isolated Storage credentials	Incluído	Suporte parcial	Incluído
Built, installed and supported on your environment by the vendor	Incluído	Suporte parcial	Não incluído
Source code handed over to you (no lock-in)	Incluído	Incluído	Não incluído
Remittance advice PDF generation and automated emailing per run	Incluído	Suporte parcial	Suporte parcial

Perguntas frequentes sobre Vendor Payment Management & Bank Integration for Business Central

How long does it take to build and deliver?

Typical lead time is 3 to 5 weeks from a confirmed scope. Week 1 is requirements and obtaining your bank's exact pain.001 schema, XSD and connectivity details; the middle weeks are AL development and unit testing in a sandbox; the final phase is your UAT against test files, then production install. The biggest variable is your bank — how quickly they provide their format spec and test-environment credentials directly affects the timeline.

Is this a download from Microsoft AppSource?

No. This is a build-to-order extension. There is no instant AppSource download — ECOSIRE scopes it to your bank and processes, develops the AL extension, and installs it as a per-tenant extension directly on your Business Central environment (sandbox first, then production). You receive the .app package and source code at handover.

What do ongoing support and updates cover?

The one-time build includes a warranty period for defect fixes after go-live. Because it is a clean AL extension on table/page extensions and workflow events, it is upgrade-safe across Business Central's monthly releases, but we offer an optional support retainer to verify each major BC update, adapt to any bank-format change (banks periodically revise pain.001 versions), and handle enhancements. You always hold the source code, so you are never locked in.

Which banks and payment formats are supported?

Any bank that accepts ISO 20022 pain.001 (.001.09 or .001.03) or a SEPA Credit Transfer file, and any connectivity method your bank publishes — host-to-host SFTP, EBICS, or a bank/aggregator REST API. We map to your bank's specific schema during the build rather than shipping a generic template, which is why first-pass acceptance is high. If your bank uses a proprietary format we will confirm feasibility in scoping.

Will it survive Business Central upgrades and is our data safe?

Yes. It is built entirely with AL extension objects (table extensions, page extensions, event subscribers and codeunits) and never modifies base application objects, so Microsoft's monthly platform updates do not break it. Bank credentials live in Isolated Storage, not in tables or code, and the extension ships with its own least-privilege permission sets so only authorized roles can release payments.