Los detalles del producto se muestran en inglés. Próximamente traducciones.
Datos rápidos
- Precio
- $499.00 USD
- Versiones de dynamics_365_business_central
- —
- tiempo de configuración
- 30 minutos
- Licencia
- Perpetuo único
- Idiomas
- 11 idiomas
Compra única
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.
$499.00USD
Sin pago ahora. Esto envía una solicitud de presupuesto a nuestro equipo; te responderemos por correo con precios y próximos pasos.
Características clave
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
Revenue Recognition Schedule table that generates dated recognition entries and posts deferred-to-recognized movements
Deferred revenue ledger with a period-by-period waterfall page showing remaining obligation by contract and obligation
Contract modification handling — prospective reallocation or cumulative catch-up adjustment per ASC 606 / IFRS 15, with audit trail
Multi-currency recognition with correct rate application and FX handling against BC currency setup
Event-subscriber integration with standard sales posting codeunits — no modification of base application objects
Job Queue entries for automated month-end recognition runs with posting-date and document filters
Dedicated permission set and posting-date-locked entries to protect closed periods
BC REST/OData v4 API pages exposing schedules and the deferred waterfall for Power BI, Excel and Dataverse / Power Platform
Sobre este producto
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.
Por qué elegir Revenue Recognition (ASC 606 / IFRS 15) for Business Central
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
Revenue Recognition Schedule table that generates dated recognition entries and posts deferred-to-recognized movements
Deferred revenue ledger with a period-by-period waterfall page showing remaining obligation by contract and obligation
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.
lo que obtienes
- 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
¿Para quién es esto?
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.
Descripción general de la instalación
Descargar desde ECOSIRE
Compre la licencia en ecosire.com y descargue el módulo ZIP Revenue Recognition (ASC 606 / IFRS 15) for Business Central desde el panel de su cuenta.
Subir a Odoo
Extraiga el ZIP en su carpeta de complementos personalizados de Odoo en el servidor (o cárguelo a través de Aplicaciones > Instalar desde archivo en Odoo.sh/runbot).
Instalar el módulo
Active el modo de desarrollador, abra Aplicaciones, haga clic en Actualizar lista de aplicaciones, busque Revenue Recognition (ASC 606 / IFRS 15) for Business Central y presione Instalar.
Configurar ajustes
Abra el nuevo menú, pegue su clave de licencia de ECOSIRE, conecte cualquier credencial externa (Shopify, Amazon, Stripe, etc.) y guarde.
Verificar y publicar
Ejecute la prueba de conexión integrada, sincronice sus primeros 10 registros y programe el cron recurrente. Póngase en contacto con el soporte si algo falla.
Cómo se compara Revenue Recognition (ASC 606 / IFRS 15) for Business Central
| Criterio | ECOSIRE | Construcción personalizada | Competidor | Odoo Nativo |
|---|---|---|---|---|
| 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 |
Preguntas frecuentes sobre 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 3 to 5 weeks: 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.
Por qué los clientes confían en ECOSIRE
SOC 2 alineado
Cumple con el RGPD
Pago seguro con franjas
Devolución de dinero en 30 días
Actualizaciones de por vida
Licencia LGPL-3.0
Módulos relacionados
Solicitar presupuesto
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