No — and we are deliberate about that. This is a build-to-order extension. ECOSIRE builds it for your specific Business Central setup and installs it as a per-tenant AL extension on your environment (cloud or on-prem). There is no instant AppSource download; you get an app tailored to your sites, roles and approval rules.

Typical lead time is about 2 to 4 weeks depending on scope — number of site types, whether you need the Dataverse/Power Platform surface, and how your approval and payroll posting should work. After a short scoping call we confirm a firm date, build in a sandbox, validate, then install on your production tenant with a working handover.

It is deployed as a per-tenant extension directly onto your Business Central tenant, with its own permission sets and a Job Queue entry. Attendance records, selfies and geofence data stay inside your BC tenant and Dataverse if used. Nothing is held in a separate ECOSIRE-controlled SaaS, and there are no per-worker attendance subscription fees.

After go-live ECOSIRE provides support for the extension and keeps it compatible with Business Central updates as agreed — Microsoft ships major BC releases twice a year, and we test and adjust the extension against those. Support, change requests (new sites, new rules) and version-compatibility maintenance are arranged in a support agreement separate from the one-time build price.

Yes. Because we deliver real table and page extensions plus event subscribers, each punch can be linked to an Employee, a Resource or a Job/Project. Approved hours can be posted toward job costing or handed to your payroll process. We configure the linkage and rounding rules to match how your business already books time in BC.

Yes. The mobile app captures the punch, GPS coordinates and selfie offline and queues them on the device. When the phone regains connectivity the queued punches sync to Business Central through the REST/OData API, with the original timestamp preserved and flagged so supervisors can see it was an offline capture.