示意预览A per-tenant AL extension that adds standards-compliant ASC 606 / IFRS 15 deferred and recognized revenue
scheduling to Business Central — built, installed and supported by
ECOSIRE on your environment.
什么是 Revenue Recognition (ASC 606 / IFRS 15) for Business Central？
A per-tenant AL extension that adds standards-compliant ASC 606 / IFRS 15 deferred and recognized revenue scheduling to Business Central — built, installed and supported by ECOSIRE on your environment. Built to order by ECOSIRE for Dynamics 365 BC (build-to-order) — indicative price from $999.00 USD; request a quote for a scoped proposal.
核心功能
按需定制，全程代劳
无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。
- 1
您下单
以一次性构建价格开始。我们在启动时与您共同确定范围。
- 2
我们构建与安装
ECOSIRE 在您的 Dynamics 365 Business Central 上构建、配置并安装。
- 3
上线 + 支持
约一个工作周内上线，并包含两周上线支持。我们交付的代码中的缺陷免费修复。
关于此产品
Business Central's core engine posts revenue when you invoice. ASC 606 and IFRS 15 require you to recognize revenue as performance obligations are satisfied — which is rarely the invoice date. This extension closes that gap directly inside Business Central, with no bolt-on subledger to reconcile.
ECOSIRE builds this as a per-tenant AL extension installed on your own Business Central environment (cloud SaaS or on-prem). It is not an instant AppSource download — it is engineered to your contract structures, then deployed and supported by us. We add table and page extensions to Sales Orders, Sales Invoices and Items so an order line can be split into one or more performance obligations, each with its own recognition method: straight-line over a service period, milestone/percentage-of-completion, or usage-based metering.
A dedicated Revenue Recognition Schedule table generates the period-by-period recognition entries. Posting routines (wired through event subscribers on the standard sales posting codeunits) move amounts from a deferred revenue balance to recognized revenue via your designated G/L accounts. A deferred revenue waterfall page and Power BI-ready OData/API endpoint show exactly what remains to be recognized, by period and obligation.
Contract modifications — added scope, price changes, partial cancellations — are handled per the standards as either prospective reallocation or catch-up adjustment, with a full audit trail. Multi-currency contracts recognize at the correct rate with FX handled against your currency setup.
Recognition runs are batchable through the Job Queue for month-end. Access is gated by a dedicated permission set. Everything stays queryable in BC and exportable for your auditors. We scope to your real contracts first, demo on a sandbox, then deploy to production.
你得到什么
- A per-tenant AL extension (.app) built to your contract structures, installed on your Business Central sandbox then production environment
- Table and page extensions on Sales Orders, Sales Invoices and Items plus the new Revenue Recognition Schedule and Deferred Revenue setup pages
- Configured recognition methods, deferred/recognized G/L account mappings and recognition templates for your products and service lines
- A dedicated permission set and Job Queue entries for automated month-end recognition
- Published OData/API endpoints with a sample Power BI deferred-revenue waterfall report
- Sandbox UAT, data-migration of in-flight contracts, go-live deployment and a recorded handover session plus admin documentation
这是给谁的
Revenue Accountant
Owns IFRS 15 / ASC 606 compliance and wants recognition schedules generated and posted inside Business Central instead of maintained in spreadsheets reconciled by hand each month.
Financial Controller
Needs a defensible deferred revenue balance, a clean waterfall for the audit, and month-end recognition that runs automatically through the Job Queue with locked closed periods.
SaaS / Services CFO
Runs subscription, milestone and usage contracts and needs deferred revenue and recognized revenue to be auditor-ready and reportable in Power BI without a separate revenue subledger.
Revenue Recognition (ASC 606 / IFRS 15) for Business Central 如何比较
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | Dynamics 365 Business Central 原生 |
|---|---|---|---|---|
| ASC 606 / IFRS 15 performance-obligation recognition built in | 包含 | 部分支持 | 包含 | 不包括在内 |
| Tailored to your specific contract structures and G/L mapping | 包含 | 包含 | 部分支持 | 不包括在内 |
| Deferred revenue waterfall reporting | 包含 | 部分支持 | 包含 | 不包括在内 |
| Contract modification handling (reallocation / catch-up) | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Upgrade-safe via event subscribers, no base-app modification | 包含 | 部分支持 | 包含 | 包含 |
| Built, installed and supported on your tenant by the vendor | 包含 | 不包括在内 | 不包括在内 | 不包括在内 |
| Multi-currency recognition | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| OData/API access for Power BI and Power Platform | 包含 | 部分支持 | 部分支持 | 部分支持 |
关于Revenue Recognition (ASC 606 / IFRS 15) for Business Central的常见问题
How long does delivery take, and is this an AppSource app I download?
It is not an AppSource download. ECOSIRE builds this as a per-tenant AL extension tailored to your contract structures, then installs it on your Business Central environment. Typical delivery is about one working week: a scoping workshop on your real contracts, a build and sandbox demo, UAT, then production go-live. Timelines depend on how many recognition methods and contract-modification scenarios you need.
How does ongoing support and Business Central updates work after go-live?
Because it is installed as a per-tenant extension, it lives in your environment and we support it directly. Our support covers bug fixes, configuration changes and compatibility with Microsoft's monthly and major Business Central releases — Microsoft publishes upgrade compatibility events that we test against on your sandbox before each wave so your recognition logic keeps working. Support and update terms are agreed in a maintenance plan; we can also transfer source and documentation if you prefer to maintain it in-house.
Will this modify or break my base Business Central application?
No. The extension integrates through event subscribers on the standard sales posting codeunits and uses table/page extensions — it never modifies base application objects. That keeps your environment upgrade-safe and means the recognition logic is cleanly isolated and removable.
Does it work with Business Central cloud (SaaS) and on-premises?
Yes. The same AL extension targets both Business Central online (SaaS) and on-premises. On SaaS it is installed as a per-tenant extension; on-prem we deploy it to your server. The recognition engine, deferred ledger and API pages behave identically on both.
Can the deferred revenue and recognition data feed Power BI and other systems?
Yes. The extension exposes its schedules and the deferred revenue waterfall through Business Central's REST/OData v4 API pages, so the data is consumable by Power BI, Excel and the Power Platform (including Dataverse). We deliver a sample Power BI waterfall report you can extend.
相关模块
Retail Analytics & Store Dashboard
A retail-specific analytics layer for Microsoft Dynamics 365 Business Central, delivering store, basket, margin and staff KPIs in ready-made dashboards. Built, installed as a per-tenant AL extension, and supported by ECOSIRE on your own environment.
SAF-T Audit File Export for Business Central
A build-to-order AL extension that exports OECD-standard SAF-T audit files from Business Central — country-specific schemas, XSD validation, and an audit-ready submission helper, installed per-tenant and supported by ECOSIRE.
Sales Commission & Incentive Compensation for Dynamics 365 CRM
A build-to-order Dynamics 365 extension that models tiered commission plans, accrues incentive compensation when opportunities close as won, and produces rep-level statements and forecasts — built, installed as a per-tenant extension, and supported by ECOSIRE.
Revenue Recognition (ASC 606 / IFRS 15) for Business Central
A per-tenant AL extension that adds standards-compliant ASC 606 / IFRS 15 deferred and recognized revenue scheduling to Business Central — built, installed and supported by ECOSIRE on your environment.
- Performance-obligation model: split a single sales order/invoice line into multiple obligations, each with its own recognition method, term and G/L mapping
- Straight-line recognition over a defined service period with configurable period basis (daily-prorated or whole-period)
- Milestone / percentage-of-completion recognition driven by manual or project-linked completion events
- Usage-based recognition that consumes metered quantities and recognizes against actual consumption