A custom AL extension built, installed and supported by ECOSIRE that connects Square POS and the Square API to Business Central — pay-by-link on invoices, card and tap-to-pay acceptance, automatic payout-to-invoice reconciliation, refund sync and customer card-on-file. Built to order by ECOSIRE for Dynamics 365 BC (build-to-order) — indicative price from $199.00 USD; request a quote for a scoped proposal.
应用清单
围绕您的工作流程构建
A custom AL extension built, installed and supported by ECOSIRE that connects Square POS and the Square API to Business Central — pay-by-link on invoices, card and tap-to-pay acceptance, automatic payout-to-invoice reconciliation, refund sync and customer card-on-file.
无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。
以一次性构建价格开始。我们在启动时与您共同确定范围。
ECOSIRE 在您的 Dynamics 365 Business Central 上构建、配置并安装。
约 2–4 周内上线,并提供上线后的支持期。
Square Payments Connector for Business Central is a build-to-order AL extension, not an instant AppSource download. ECOSIRE develops it against your Square account and your Business Central environment, then installs it as a per-tenant extension and supports it on an ongoing basis.
If you take card payments through Square POS and keep your books in Business Central, you live with a daily disconnect: Square holds the transactions, fees and payouts, while BC holds the customer ledger and unpaid invoices. This connector closes that gap.
On the AL side we ship a focused extension: page extensions on the Sales Invoice and Customer Card surface a "Send Square Pay Link" action, table extensions persist Square payment, payout and card-on-file references against your documents, and event subscribers on posting and on the Square webhook react in real time. A dedicated job queue entry polls the Square Payments and Payouts API to catch anything a webhook missed.
When a payout lands in your bank, the connector matches the constituent Square payments back to the originating BC invoices and prepares the cash receipt and the Square processing-fee line, so a Square deposit reconciles to the customer ledger instead of sitting as a lump sum. Refunds issued in Square flow back as credit memos or applied refunds. Customer card-on-file uses the Square Cards API so repeat customers can be charged without re-keying details.
Authentication uses your own Square OAuth credentials stored in Isolated Storage, scoped by a custom permission set. Because it is built to order, we map it to your number series, dimensions, payment methods and bank accounts — and can extend it toward Dataverse / Power Platform if you later want Square data in Power BI or a flow.
Runs day-to-day sales through Square POS and Square Online but keeps the books in Business Central. Wants card takings, fees and bank payouts to land in the customer ledger automatically instead of being re-keyed each week.
Spends hours every month matching a single Square bank deposit back to dozens of individual sales and chasing where the processing fees went. Needs the payout split and reconciled against open invoices with the fee posted correctly.
Owns the Business Central tenant and is wary of unsupported customizations. Wants a clean per-tenant extension that touches no base objects, uses a proper permission set, and comes with someone to call when Square changes its API.
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| Square pay-by-link generated directly on BC sales invoices | 包含 | 部分支持 | 部分支持 | |
| Automatic Square payout split and reconciliation to originating invoices | 包含 | 部分支持 | 部分支持 | |
| Square processing-fee posted to the correct G/L account | 包含 | 部分支持 | 部分支持 | |
| Refund sync and customer card-on-file via Square Cards API | 包含 | 部分支持 | 部分支持 | |
| Delivered as an upgrade-safe per-tenant AL extension (no base-object changes) | 包含 | 部分支持 | 包含 | |
| Mapped to your number series, dimensions, bank accounts and payment methods | 包含 | 包含 | 不包括在内 | |
| Ongoing support and updates for Square API and BC release changes | 包含 | 不包括在内 | 部分支持 | |
| Instant self-service install with no build lead time | 不包括在内 | 不包括在内 | 包含 |
No. This is a build-to-order extension. ECOSIRE develops it against your specific Square account and Business Central environment, then installs it as a per-tenant extension directly into your tenant. There is no instant AppSource listing to click and install — you get a connector configured for your number series, bank accounts and Square credentials.
Typical lead time is about 2 to 4 weeks from when we receive your Square API access and a sandbox login. The schedule depends on how custom your reconciliation and dimension mapping needs are. We build and test in your sandbox first, run UAT with sample payments, a payout and a refund, and only then install to production.
Every build includes a post-go-live support window with a named ECOSIRE contact. We monitor for Square API changes and Business Central platform upgrades (BC ships major releases twice a year) and update the extension so it keeps working. Longer-term support and enhancement plans are available; because it is a per-tenant extension, we can patch and redeploy without disrupting your base application.
No. It is delivered as a separate AL extension using table extensions, page extensions and event subscribers. Your base application is untouched, which keeps your tenant upgrade-safe and lets the connector be updated or removed cleanly.
Yes, as an option. Because the connector stores Square payment and payout references on your BC documents, we can surface that data through the BC API/OData or push it into Dataverse so Power BI dashboards and Power Automate flows can use it. This is scoped as an add-on during the build.
A custom AL extension built, installed and supported by ECOSIRE that connects Square POS and the Square API to Business Central — pay-by-link on invoices, card and tap-to-pay acceptance, automatic payout-to-invoice reconciliation, refund sync and customer card-on-file.