Commercial cleaning is a recurring-service business, and Business Central was not designed around recurring service. A cleaning firm servicing 120 sites on nightly, three-times-weekly and monthly frequencies has to answer four questions every day: who is due where, what has to be done at each site, what supplies went out of the store, and what gets invoiced at month end. In standard Business Central you can approximate parts of that with Service Management contracts, Jobs, and Recurring Sales Lines, but the pieces do not join up. Service Contract lines have no notion of a per-site task list a supervisor signs off. Resource Ledger Entries capture hours but not which cleaner was rostered against which site visit. Item consumption on a cleaning round has no home other than a manual negative adjustment. And the moment a client adds a floor or drops a Saturday visit mid-contract, the recurring invoice and the schedule drift apart, because nothing links them.

We build a per-tenant AL extension (or an AppSource-targeted app if you prefer that packaging) that adds the missing service layer directly into your Business Central company. The core is a Site Contract table extending the Customer with sites, service frequencies and contract lines, plus a schedule engine that expands those frequencies into dated Cleaning Visit records through a Job Queue Entry running a scheduling codeunit — typically nightly, with a configurable horizon of one working week. Each generated visit carries a Checklist Template resolved from the site: task lines, required evidence, and pass/fail criteria. Supervisors complete inspections against the same records, and a weighted score writes back to the visit, so you can report site quality per customer, per supervisor, per month.

Technically it is a normal, upgrade-safe Business Central extension. New tables and pages carry your object range; existing surfaces get table extensions and page extensions rather than modified base objects — a Site FactBox on the Customer Card, contract fields on the Sales Invoice, a Cleaning Visits part on the Resource Card. Business logic lives in codeunits behind event subscribers on the standard publishers (sales posting, item journal posting, resource ledger posting), so a Business Central release-wave upgrade does not break the extension's behaviour. Supplies post through Item Journal lines against a site-specific dimension, so cost per site falls out of standard Business Central dimension analysis rather than a parallel report. Staff hours post as Resource Ledger Entries with the visit as source, keeping payroll export and job costing on the standard rails. Recurring contract invoicing runs as a second job queue codeunit that reads the period's completed visits plus the contract's fixed lines, builds Sales Invoices in a batch, and either leaves them for review or posts them per a setup flag — with a full audit trail from invoice line back to visit.

Everything is reachable from outside Business Central. We expose API pages on the API v2.0 endpoint (custom apiPublisher/apiGroup) for visits, checklists and site contracts, so a Power App or a mobile crew form can read the night's schedule and write completion and photo evidence back; OData v4 web services cover the reporting side for Power BI. Dataverse virtual tables are available where you already run Power Platform, and the same API is what a third-party workforce app would integrate against. Permission sets ship with the extension — an Operations set that can generate schedules and edit contracts, a Supervisor set that can complete visits and inspections, and a read-only set for account managers — so you are not handing SUPER to field staff. The extension targets current Business Central release waves and runs on SaaS online or on-premises.

This is build-to-order, and we are explicit about what that means. Nothing downloads today. You book a scoping call, we walk your site and contract structure, your existing Business Central setup and your invoicing rules, and we come back with a fixed scope and a quotation. From confirmed scope, typical delivery is one working week: we develop against your Business Central version, deploy to a sandbox for UAT with your real contract data, iterate on the checklist and invoicing rules with your operations lead, then install to production with a documented rollback. You receive the AL source code, the git repository, technical and user documentation, a training session, and a post-go-live support window. Because it is your extension rather than a shared marketplace app, the checklist model, frequency rules and invoice layout are shaped to how your firm actually operates.