A custom-built Business Central extension that turns BC into a complete institutional finance system — student enrollment, recurring fee billing, scholarships, installment plans, arrears tracking and department cost centers — installed and supported by ECOSIRE on your tenant. Built to order by ECOSIRE for Dynamics 365 BC (build-to-order) — indicative price from $499.00 USD; request a quote for a scoped proposal.
示意预览A custom-built Business Central extension that turns BC into a complete institutional finance system
— student enrollment, recurring fee billing, scholarships, installment plans, arrears tracking and department cost centers — installed and supported by
ECOSIRE on your tenant.
无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。
以一次性构建价格开始。我们在启动时与您共同确定范围。
ECOSIRE 在您的 Dynamics 365 Business Central 上构建、配置并安装。
约 2–4 周内上线,并提供上线后的支持期。
Schools, colleges and universities run on Business Central for general ledger, AP/AR and reporting — but BC has no concept of a student, a fee structure, a scholarship or a term-based installment plan. Bursars end up reconciling fees in spreadsheets and posting journals by hand. This extension closes that gap.
Education & School ERP for Business Central is a per-tenant AL extension that ECOSIRE designs, builds, installs and supports directly on your Business Central environment (cloud SaaS or on-prem). It is not an instant Microsoft AppSource download — it is built to order around your fee calendar, scholarship rules and chart of accounts, then deployed as a signed extension to your tenant.
We add Student and Enrollment tables with table/page extensions linking each student to a BC Customer record, so every fee posts through standard G/L, dimensions and AR aging with no shadow ledger. A Fee Structure setup drives recurring billing through the Job Queue, generating posted sales invoices per term. Scholarship and discount management applies percentage or fixed awards as invoice lines or credit memos with full audit trail. Installment plans schedule due dates and an arrears report surfaces overdue balances by student, program or faculty.
Departments and faculties map to BC Dimensions (cost centers) so the finance head sees contribution by program in standard analysis views. Event subscribers keep posting logic inside BC's own routines — no fragile customizations. We provision dedicated permission sets for bursars, registrars and read-only auditors, and expose student/fee data over the BC REST/OData API for your portal, Power BI or Power Automate flows. Optional Dataverse sync feeds a Power Apps admissions or parent app.
You get a working system on your tenant, source AL, and a support relationship — not a black box.
Owns fee collection and institutional finance. Wants every term's billing generated automatically, arrears visible in real time, and all of it posting through Business Central's standard G/L and AR instead of side spreadsheets.
Maintains student and enrollment records. Needs each student tied to a billable account so admissions, program changes and withdrawals flow straight into fee and scholarship handling without re-keying.
Responsible for the Business Central tenant. Prefers a clean per-tenant extension using event subscribers and permission sets that survive Microsoft's twice-yearly updates, rather than risky base-app modifications.
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | Dynamics 365 Business Central 原生 |
|---|---|---|---|---|
| Student, enrollment and fee-structure data model on top of BC | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Automated recurring term fee billing via Job Queue | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Scholarship / discount management with audit trail | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Installment plans and arrears/aging by program & faculty | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Posts through native BC G/L, AR and Dimensions (no shadow ledger) | 包含 | 部分支持 | 部分支持 | 包含 |
| Built, installed and supported on YOUR tenant by the vendor | 包含 | 不包括在内 | 不包括在内 | 不包括在内 |
| Source AL code handed over to you | 包含 | 包含 | 不包括在内 | 不包括在内 |
| Tailored to your fee calendar, scholarship rules and chart of accounts | 包含 | 包含 | 不包括在内 | 不包括在内 |
| Upgrade-safe via event subscribers / extension model | 包含 | 部分支持 | 包含 | 包含 |
No. This is a build-to-order extension. ECOSIRE designs it around your fee calendar, scholarship rules and chart of accounts, then builds, signs and installs it as a per-tenant AL extension directly on your Business Central environment. There is no AppSource listing or self-service download — you get a system tailored to your institution and deployed for you.
Typical lead time is about 2 to 4 weeks from requirements sign-off, depending on the complexity of your fee structures, scholarship logic and any portal or Dataverse integration. After our discovery call we give you a firm schedule. We deploy first to a sandbox tenant for your acceptance testing, then promote to production.
The included support window covers bug fixes, configuration help and a verified compatibility check against Microsoft's spring and fall BC releases. Because the extension uses event subscribers and table/page extensions rather than base-app modifications, updates are normally non-breaking. After the initial window you can continue on an annual support and maintenance agreement.
Yes. Each student is linked to a Business Central Customer, and all fees post as standard sales invoices and credit memos through BC's own posting routines. That means G/L, AR aging, dimensions, tax and statutory reporting all work natively — there is no separate ledger to reconcile.
Yes. Student, fee, installment and balance data is exposed over the Business Central REST/OData v4 API, and we can drive Power Automate flows or a Dataverse-backed Power App. Online payment reconciliation against the matching gateway can be wired in as part of the build or as a follow-on engagement; we scope that during discovery.
A custom-built Business Central extension that turns BC into a complete institutional finance system — student enrollment, recurring fee billing, scholarships, installment plans, arrears tracking and department cost centers — installed and supported by ECOSIRE on your tenant.