A per-tenant Business Central AL extension that automatically populates and transmits Level 2 (tax, PO) and Level 3 (line-item) data on B2B card transactions so qualifying payments earn lower interchange rates. Built, installed and supported by ECOSIRE on your environment. Built to order by ECOSIRE for Dynamics 365 BC (build-to-order) — indicative price from $299.00 USD; request a quote for a scoped proposal.
应用清单
围绕您的工作流程构建
A per-tenant Business Central AL extension that automatically populates and transmits Level 2 (tax, PO) and Level 3 (line-item) data on B2B card transactions so qualifying payments earn lower interchange rates. Built, installed and supported by ECOSIRE on your environment.
无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。
以一次性构建价格开始。我们在启动时与您共同确定范围。
ECOSIRE 在您的 Dynamics 365 Business Central 上构建、配置并安装。
约 2–4 周内上线,并提供上线后的支持期。
Commercial and corporate cards in Business Central often settle at the most expensive interchange tier simply because the transaction is submitted without the supplementary data card networks reward. Level 2 data (sales tax amount, tax-exempt status, customer PO/order number) and Level 3 data (per-line item descriptions, quantities, unit-of-measure, unit price, commodity codes, freight) signal a low-risk B2B purchase — and qualifying transactions can settle at meaningfully lower interchange rates.
This is a build-to-order AL extension, not an instant AppSource download. ECOSIRE builds it against your specific gateway and chart of accounts, installs it as a per-tenant extension on your Business Central environment (cloud or on-prem), and supports it after go-live.
What we build. A table-extension and page-extension layer captures the Level 2/3 fields on Sales Orders, Posted Sales Invoices and the payment record. An event subscriber (typically on OnAfterPostSalesDoc or the payment-capture flow of your connector) assembles the L2/L3 payload from the posted document lines — descriptions, quantities, UoM, line amounts, the document tax breakdown and the customer PO. A per-gateway field-mapping module translates that payload into the exact API schema your processor expects (Authorize.Net, Stripe, Worldpay, Cybersource or your acquirer's API), because every gateway names and validates these fields differently. B2B card detection inspects the card BIN / product code returned at authorization and routes only commercial/corporate/purchasing cards through the enhanced-data path, so consumer cards are left untouched. An Interchange Savings report and Power BI-ready dataset show qualified vs. unqualified volume.
Permission sets, a Job Queue entry for retrying enhanced-data submission, and AL test codeunits are included. Optional Dataverse / Power Platform sync surfaces the savings data outside BC. We do not control your card network's qualification rules — we make sure Business Central submits clean, complete L2/L3 data so your transactions are eligible for the better rate.
Runs high commercial-card volume and is frustrated that corporate and purchasing-card payments settle at the most expensive interchange tier. Wants Business Central to submit the L2/L3 data that qualifies those transactions for lower rates without changing how the team posts invoices.
Owns the BC environment and the payment-connector integration. Needs the optimizer delivered as a clean per-tenant extension using event subscribers — no base-app modification, scoped permission sets, and a tested install path through sandbox before production.
Cares about measurable processing-cost reduction and audit trail. Wants the interchange-savings report and a Power BI dataset showing qualified vs. unqualified card volume so the savings from enhanced data are visible and defensible.
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| Auto-populates L2/L3 data from posted BC documents | 包含 | 部分支持 | 部分支持 | |
| Per-gateway field mapping configured for your processor | 包含 | 部分支持 | 部分支持 | |
| B2B card detection via BIN/card-product routing | 包含 | 部分支持 | 部分支持 | |
| Delivered as upgrade-safe per-tenant extension (no base-app changes) | 包含 | 部分支持 | 包含 | |
| Interchange-savings reporting with Power BI / OData dataset | 包含 | 部分支持 | 部分支持 | |
| Built, installed and supported on your environment by the vendor | 包含 | 不包括在内 | 不包括在内 | |
| Tailored to your tax, UoM and commodity-code mapping | 包含 | 包含 | 不包括在内 | |
| AL test codeunits validated against your real data | 包含 | 部分支持 | 不包括在内 |
This is built to order, so lead time depends on your gateway and catalog complexity. A typical engagement is roughly 2 to 4 weeks: a short discovery on your processor and document flow, build of the AL extension and per-gateway mapping, a tested install in your sandbox where we validate L2/L3 payloads against real documents, then a scheduled production install on your tenant. You'll have a confirmed timeline before we begin.
Every build includes a post-go-live support and warranty period for defects and gateway field-mapping fixes. Because it ships as a per-tenant extension, ECOSIRE updates it on your schedule — we test the .app against new Business Central release waves and adjust mappings if your processor changes its L2/L3 API. Optional ongoing maintenance covers proactive compatibility testing across BC updates and gateway changes.
We make your transactions eligible for lower rates by submitting clean, complete, validated Level 2/3 data — that is the part Business Central controls. Final qualification is decided by the card networks and your acquirer against their rules. We do not control those rules and won't promise a specific basis-point figure, but the savings report shows exactly which transactions qualified so you can verify the impact with your processor.
No. It's delivered as a per-tenant AL extension using table extensions, page extensions and event subscribers (for example on the post and payment-capture flows). Base application objects are not touched, which keeps you upgrade-safe across BC release waves and avoids conflicts with your existing payment connector.
We build the field mapping for your specific processor — common targets include Authorize.Net, Stripe, Worldpay and Cybersource, or your acquirer's direct API. It works on Business Central cloud (SaaS) and supported on-prem versions. If your gateway exposes an L2/L3 enhanced-data API, we can map to it; tell us your processor during discovery and we'll confirm fit before any commitment.
A per-tenant Business Central AL extension that automatically populates and transmits Level 2 (tax, PO) and Level 3 (line-item) data on B2B card transactions so qualifying payments earn lower interchange rates. Built, installed and supported by ECOSIRE on your environment.