A dental practice runs on three clocks that Dynamics 365 Business Central has no native concept of: the chair, the treatment plan, and the lab bench. Business Central gives you a solid customer ledger, sales invoices, VAT/tax posting, inventory for consumables and a Service Management module that was designed for field service on serialised equipment — not for a hygienist's 30-minute recall slot or a five-visit crown sequence with an insurance pre-authorisation attached. Practices end up running the clinical side in a standalone dental app and the money side in Business Central, keying the same procedure twice, reconciling patient balances by hand, and discovering a lab case is late only when the patient is already in the chair.

What we build is an AL extension for Business Central that closes that gap without forking your finance setup. Patients extend Customer through a table extension plus a Patient Card page, so every clinical record still posts to the customer ledger you already reconcile. A chair and provider model reuses Business Central Resource records with capacity calendars, and the Appointment table carries chair, provider, duration, procedure codes and status, surfaced on a day/week board page with reassignment actions and conflict validation in a scheduling codeunit. Treatment plans are versioned header/line documents: each line references a procedure code (mapped to an Item or Resource and a posting group), carries an estimate, a patient share and an insurer share, and can be accepted line by line. On completion, a posting codeunit turns accepted, delivered plan lines into a Sales Invoice through the standard Sales Header / Sales Line posting path — never a custom ledger — so tax, dimensions and posting groups behave exactly as your accountant expects.

Lab work is a first-class document: lab vendor, send and due dates, case status, shade and material fields, and an optional Purchase Order raised to the lab so cost lands against the case and the treatment plan margin is real rather than assumed. Recalls are driven by a Job Queue Entry that scans due recall dates and queues reminders through email, an SMS gateway or a Power Automate flow. Technically it is built to stay upgrade-safe: table and page extensions rather than base-object modification, event subscribers instead of hooks into Microsoft code, a reserved object ID range and prefix registered to your tenant, and dedicated permission sets so reception can book, clinicians can plan and only finance can post. API pages published on the Business Central REST API v2.0 / OData v4 surface expose appointments, patients, treatment plans and lab cases so a patient portal, imaging software or a Power Apps front-end can read and write them; Dataverse virtual tables and Power BI reporting are wired on request. The extension targets current Business Central release waves and runs on SaaS (per-tenant extension or AppSource-packaged app) as well as on-premises.

This is build-to-order, not a download. After a scoping call we produce a written functional specification covering your procedure code set, insurance and claim handling, chair and provider layout, lab vendors and recall rules, and confirm the price against that scope. Typical delivery is one working week from confirmed scope. We build against your Business Central version, deploy to your sandbox for UAT with your own patient and procedure data, then install into production during an agreed window with a documented rollback. You receive the AL source, the git repository, technical and user documentation, a live training session, and a post-go-live support window for fixes and adjustments.