A funeral home does not sell products, it manages cases. From the first call at 2am to the final statement six weeks later, one case file has to hold the decedent record, the informant and next-of-kin contacts, the arrangement conference decisions, casket and urn selection, the visitation and service times, the crematory or cemetery booking, the death certificate and permit numbers, the cash advance items paid to third parties, and the itemized price list the family signed. Standard Dynamics 365 Business Central has no concept of any of it. You can force a case into a Sales Order and the arrangements into sales lines, but the moment you need to attach a service on a specific date at a specific chapel, track a merchandise item that is also part of a package, or print a price disclosure in the sequence a regulator requires, you are in spreadsheets and a filing cabinet — and the numbers in Business Central stop matching the numbers the family was quoted.

ECOSIRE builds a Business Central AL extension that makes the case the primary document. A new Funeral Case table carries decedent details, informant and responsible-party links to Customer and Contact, disposition type, and a status flow (First Call → Arrangement → Scheduled → Serviced → Billed → Closed) driven by a state codeunit rather than free text. Arrangement lines sit in a dedicated line table with line types for Professional Services, Facilities & Staff, Merchandise, Packages, and Cash Advances, so a cash advance passes through to the family statement at cost without inflating your revenue or your COGS. Merchandise lines are real Item records, so caskets, urns and register books draw on standard Business Central inventory, item tracking and costing — no shadow catalogue. Packages explode into their component lines with an allocated price, and the component detail stays visible for disclosure.

Scheduling is modelled with a Resource-backed booking table: chapels, hearses, limousines, preparation rooms, celebrants and licensed directors are all resources, and a booking codeunit enforces overlap validation across a case's visitation, service and committal appointments before it will post. Regulatory documentation is generated from the case with Word layout report objects — general price list, itemized statement of goods and services selected, authorization and cremation permission forms, transit and burial permits — with a Funeral Document Log recording which version was issued, to whom, and when, so an inspection has an audit trail instead of a folder. Family billing posts through native Sales Invoice and Cust. Ledger Entry, with support for split responsibility across multiple payers, insurance assignment, and installment terms, so aging, statements and collections behave exactly as your accountant already expects.

Technically it is a standard AL extension for current Business Central release waves on SaaS or on-premises: table and page extensions rather than base-app modification, event subscribers into Sales-Post and Item Jnl.-Post Line, dedicated permission sets separating arrangers, directors and finance, and API pages exposed over REST API v2.0 / OData v4 so an obituary website, a Power BI case-volume report, or a Power Automate flow in Dataverse can read case and schedule data without a middleman. Long-running work — preneed accrual, document expiry reminders, unbilled-case alerts — runs on Job Queue Entries, not on someone remembering.

This is build-to-order, not an AppSource download. We start with a scoping call, confirm your disposition types, price list structure, document set and jurisdiction, then write the extension against your Business Central version. Typical delivery is one working week from confirmed scope. You get the AL source, the compiled app deployed to a sandbox for UAT, a documented rollback, training for your arrangers and office staff, and a support window after go-live. If your state or country requires a form we have not seen, we build it — that is the point of building to order.