A solar EPC business does not fit the shape Business Central ships with. A rooftop job starts as a site visit with a shading assessment and a roof measurement, becomes a design with a specific panel/inverter/mounting combination, turns into a purchase plan for long-lead inverters, then a crew schedule, then a subsidy claim and a net-metering application with a utility, and finally a five- or ten-year O&M contract with periodic cleaning visits and breakdown callouts. Native Business Central gives you Projects (Jobs), Job Planning Lines, Purchase Orders, Assembly and Service Management — solid financial bones, but nothing that knows what a string layout is, that a utility application has a status, that panel serial numbers must be captured at commissioning for warranty, or that an O&M ticket in year three belongs to the same asset the crew installed in year one. Teams end up running the real work in spreadsheets and WhatsApp while Job Ledger Entry only ever sees the money, which is exactly why margin per site is discovered months late.

We build an AL extension that puts the solar workflow inside Business Central rather than beside it. New tables carry the domain: Site Survey (roof type, tilt, azimuth, shading loss %, usable area, meter details, utility reference), System Design (DC/AC capacity, module and inverter selection, string configuration, expected annual generation), and Project Asset Register (serialised modules, inverters and optimisers linked back to the installing job). Those records are stitched to the standard Job table via table extensions, and an approved design converts into Job Planning Lines plus a project BOM through a codeunit, so consumption, WIP and job costing continue to post exactly the way your accountant already expects. Procurement runs on standard requisition and purchase documents, with lead-time flags on inverters and structure so a long-lead item raises its own alert rather than surfacing on the day the crew arrives.

Execution and compliance are handled the same pragmatic way. Installation tasks — civil, structure, module mounting, DC/AC wiring, earthing, inverter commissioning, meter change — are scheduled per job with crew and resource assignment, dependency ordering and a mobile-friendly list page a supervisor can update from site. Every subsidy, net-metering and inspection document is tracked as a checklist row with an owner, a submission date, a reference number and a status, so a stalled utility approval shows on a dashboard instead of in one person's inbox; files attach through the standard Business Central attachment/media stack. O&M contracts create scheduled preventive visits via job queue entries and open tickets against the asset register, with SLA response clocks and a link straight back to the original design and serial numbers.

The extension is built the way a supportable Business Central app should be: table and page extensions over base objects rather than modified base code, business logic in codeunits, integration through event subscribers rather than intrusive hooks, dedicated permission sets for surveyor, project manager, procurement and O&M roles, and API pages exposing surveys, projects, tasks and tickets over REST API v2.0 / OData v4 so a field app, Power BI report, Power Apps form or Dataverse-connected flow can read and write without anyone hand-keying. It targets current Business Central release waves and installs on SaaS as a per-tenant extension or AppSource-format app, and on-premises where you run your own container.

Because it is build-to-order, nothing here is a download you buy blind. We start with a scoping call, confirm exactly which flows you need — some EPCs live and die on subsidy paperwork, others on O&M ticket volume — and quote fixed scope. Typical delivery is 2-4 weeks from confirmed scope. You get the AL source compiled for your Business Central version, installation on your sandbox first, UAT against your own jobs, then production deployment with a rollback plan, followed by a support window while your team beds it in.