Guarding companies live or die on two numbers: hours contracted at each post, and hours actually stood. Dynamics 365 Business Central handles the money side of that business well — customers, contracts as sales documents, recurring invoicing, resources, jobs and the general ledger — but it has no concept of a post. There is no table that says "Gate 2 at the Marina warehouse needs one licensed officer, 19:00–07:00, seven nights, and the relief must not push anyone past 48 hours in a rolling week." So operations runs the roster in Excel or a standalone guard-tour app, payroll re-keys the hours, and finance invoices from a spreadsheet that nobody reconciles back to the contract. The gaps show up as unbilled overtime, billed-but-unworked hours a client eventually disputes, and a licence expiry nobody caught until an audit.

ECOSIRE builds a Business Central AL extension that closes that loop inside the system where the invoice already lives. We add first-class Guard Site, Site Post and Post Requirement tables keyed to the Customer and to the contract line, so a post carries its own coverage pattern, required certifications, bill rate and pay rate. Guards are modelled as an extension of Resource (or of Employee where you run Business Central payroll), with licence and certification expiry dates that a job queue entry checks nightly. The Roster Line table holds planned versus actual start/end, a relief reason code, and a status flow — Planned, Confirmed, Worked, No-Show, Relieved — enforced in a codeunit rather than by page validation, so the same rules apply to a mobile check-in arriving through an API page as to a dispatcher editing the roster list page.

Technically it is a standard AL extension — per-tenant for a single company, or packaged as an AppSource app if you want to resell it — built with table and page extensions on Customer, Resource, Job and Sales Line, event subscribers rather than base-application modification, and its own permission sets separating Dispatcher, Payroll and Finance. Patrol and incident capture is exposed as API pages on REST API v2.0 (OData v4), so a guard-tour scanner, an NFC checkpoint app or a Power App on Dataverse posts checkpoint hits and incident records straight into Business Central with the site, post and roster line already resolved. Billing runs the other direction: a codeunit aggregates worked hours by post and contract period, applies the post's bill rate plus overtime and public-holiday multipliers, and generates sales invoice lines with drill-down back to the exact shifts — so a client query about one line on a 400-hour invoice is answered in two clicks. The same aggregation, on the pay-rate side, produces a payroll input export in whatever layout your provider accepts. Job queue entries handle nightly roster gap detection, licence-expiry alerts and unbilled-hours reporting.

This is a build-to-order product, not a download. There is no AppSource listing to install today; we build the extension against your Business Central version, your contract structures and your actual pay and overtime rules, because the difference between a 12-hour night post in the Gulf and a UK licensed site is entirely in those rules. Typical delivery is two to four weeks from confirmed scope, on current Business Central release waves, SaaS or on-premises. We start with a scoping call, write the specification, build and unit-test the extension, deploy to your sandbox for UAT with your own roster and contract data, then go live with a rollback plan and a documented handover.

You receive the AL source, a git repository, permission sets, technical documentation and a user guide, plus a post-go-live support window. Nothing is locked, obfuscated, or dependent on ECOSIRE remaining in the picture.