Biometric Time & Attendance for Business Central

Key Features

Clock-in via fingerprint, facial recognition, RFID/NFC card and PIN, captured from your existing terminals

Device-agnostic edge connector supporting ZKTeco, Suprema and compatible SDK/push families

Punches land in a dedicated AL staging table, then a Job Queue entry reconciles and posts them to BC timesheets

Built as a per-tenant AL extension using event subscribers and table/page extensions — no base-code customisation, update-safe

Configurable rule engine: overtime thresholds, grace periods, rounding, late/early-leave flags and automatic absence detection

Attendance-to-payroll hours export mapped to your payroll resource (BC payroll, partner payroll app, or CSV/OData hand-off)

Employee-to-device mapping with multi-shift, night-shift and split-shift handling

Reconciliation page surfacing missed punches, duplicates and out-of-pattern entries for HR review before posting

Respects existing BC permission sets and security groups; new permission set scoped to attendance roles

Optional Dataverse virtual tables and Power BI dashboard for live attendance and headcount analytics

Secure ingestion via the BC REST/OData v4 API with token-based authentication; no open base-app endpoints

Deployed to sandbox first for UAT, then promoted to the production environment by ECOSIRE

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Dynamics 365 Business Central.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

Stop re-keying clock data into Business Central by hand. This is a custom AL extension that ECOSIRE builds for your specific Dynamics 365 Business Central tenant, installs as a per-tenant (non-AppSource) extension, and supports going forward. It turns your physical clocking hardware into a live attendance and payroll feed inside BC.

Your fingerprint, facial-recognition, RFID/NFC and PIN terminals — ZKTeco, Suprema and similar device families — push punches into a staging table through a lightweight on-premise/edge connector. A Job Queue entry polls and reconciles those punches against employee records, then posts completed shifts to BC timesheets via table and page extensions. A configurable rule engine applies overtime thresholds, grace periods, late/early-leave flags and absence detection, so the hours that reach payroll are already clean and policy-correct.

Because it is built as an AL extension using event subscribers (not customised base code), it survives Microsoft's monthly and major BC updates and respects your existing permission sets. Data flows through supported surfaces — the BC REST/OData v4 API and, where you run Power Platform, optional Dataverse virtual tables for Power BI attendance dashboards.

Honest delivery: this is not an instant download. After purchase ECOSIRE scopes your devices, pay rules and payroll target, develops the extension, deploys it to your sandbox for UAT, then promotes it to production. You get the source, the deployment, and ongoing support. Typical first delivery is two to four weeks depending on device count and rule complexity. The $249 price is the starting build fee; multi-device or multi-entity scopes are quoted after a short discovery call.

What you get

A per-tenant Business Central AL extension (.app) built for your environment, with source code handed over

Edge/on-premise connector configured for your specific clock device models and network

Deployment to your BC sandbox for user-acceptance testing, then promotion to production

Configured rule engine reflecting your overtime, grace-period, rounding and absence policies

Mapped payroll hours export to your chosen payroll target (BC, partner app, or OData/CSV)

Dedicated permission set plus employee-to-device mapping configured for go-live

Admin and HR runbook covering reconciliation, Job Queue monitoring and adding new devices

Post-go-live support window with update-compatibility checks against BC release waves

Who this is for

HR / Payroll Manager

Owns the monthly pay run and is tired of manually transcribing clock exports into Business Central. Wants policy-correct hours, overtime and absences to arrive in BC automatically and auditable.

Operations / Plant Manager

Runs a shop-floor or shift workforce across multiple entry points. Needs reliable multi-shift, night-shift attendance tied to the same ERP the rest of the business already runs on.

Business Central IT / Partner Admin

Responsible for the BC tenant's health and updates. Wants a clean per-tenant AL extension using event subscribers and supported APIs that won't break on Microsoft's release waves or bypass permission sets.

How Biometric Time & Attendance for Business Central Compares

Criterion	ECOSIRE	Custom Build	Competitor
Native biometric clock-to-BC attendance out of the box	Included	Not included	Partial support
Device-agnostic connector (ZKTeco, Suprema, RFID/NFC, PIN)	Included	Partial support	Partial support
Built as update-safe per-tenant AL extension (event subscribers, no base-code edits)	Included	Partial support	Included
Tailored to your exact overtime, grace-period and absence rules	Included	Included	Partial support
Installed and promoted to production for you (sandbox UAT first)	Included	Partial support	Not included
Source code handed over to you	Included	Included	Not included
Ongoing support with BC release-wave compatibility checks	Included	Partial support	Partial support
Optional Dataverse / Power BI attendance dashboards	Included	Partial support	Partial support

Frequently Asked Questions about Biometric Time & Attendance for Business Central

How long until it's live, and is this an AppSource download?

No — this is build-to-order, not an instant AppSource install. After purchase ECOSIRE runs a short discovery on your devices, pay rules and payroll target, develops the AL extension, deploys it to your sandbox for UAT, then promotes it to production. Typical first delivery is two to four weeks depending on the number of device models and the complexity of your overtime and absence rules.

What happens with ongoing support and Business Central updates?

Because it's a per-tenant AL extension built with event subscribers and the supported REST/OData API rather than base-code changes, it is designed to survive Microsoft's monthly and major release waves. Your purchase includes a post-go-live support window; we run compatibility checks against upcoming BC release waves and fix any breakages. Ongoing maintenance, new devices, or new pay rules can be handled under a support retainer quoted after go-live.

Which clock devices and biometric methods are supported?

Fingerprint, facial recognition, RFID/NFC card and PIN entry are all supported. The edge connector is device-agnostic and built around common families such as ZKTeco and Suprema (push/SDK-based terminals). During discovery we confirm your exact models; if a device exposes a documented push or SDK protocol, we can integrate it.

Will it bypass our permission sets or modify the base application?

No. It ships a dedicated permission set scoped to attendance roles and respects your existing BC security groups. All logic lives in table/page extensions and event subscribers — the base application is never modified — so installs and uninstalls are clean and update-safe.

Can it feed our payroll and Power BI?

Yes. Reconciled, policy-applied hours export to your chosen payroll target — BC payroll, a partner payroll app, or an OData/CSV hand-off. Where you run Power Platform, we can expose attendance data through Dataverse virtual tables for a live Power BI attendance and headcount dashboard.

What does the $249 cover and what is quoted separately?

The $249 is the starting build fee for a standard single-entity scope with a common device family and typical pay rules. Larger scopes — many device models, multiple legal entities, complex shift patterns, or bespoke payroll integrations — are quoted after the discovery call. You always see the full price before any build work begins.