Aperçu illustratifA build-to-order Dynamics 365 Business Central extension that connects fingerprint,
facial-recognition and RFID/NFC clocks to your tenant, auto-posts punches into timesheets, applies your overtime and absence rules, and exports clean payroll hours. Built, installed and supported by ECOSIRE.
Qu'est-ce que Biometric Time & Attendance for Business Central ?
A build-to-order Dynamics 365 Business Central extension that connects fingerprint, facial-recognition and RFID/NFC clocks to your tenant, auto-posts punches into timesheets, applies your overtime and absence rules, and exports clean payroll hours. Built, installed and supported by ECOSIRE. Built to order by ECOSIRE for Dynamics 365 BC (build-to-order) — indicative price from $999.00 USD; request a quote for a scoped proposal.
Fonctionnalités clés
Fait sur commande, clé en main
Aucune configuration à faire vous-même — une app fonctionnelle conçue, installée et prise en charge par ECOSIRE.
- 1
Vous commandez
Commencez par un prix de développement unique. Nous cadrons le projet avec vous au lancement.
- 2
Nous développons et installons
ECOSIRE la développe, la configure et l'installe sur votre Dynamics 365 Business Central.
- 3
Mise en ligne + assistance
Vous êtes en ligne en une semaine ouvrée environ, avec deux semaines d’assistance après la mise en production. Les défauts du code que nous livrons sont corrigés gratuitement.
À propos de ce produit
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 one working week depending on device count and rule complexity. The $999 price is the starting build fee; multi-device or multi-entity scopes are quoted after a short discovery call.
Ce que vous obtenez
- 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
Pour qui c'est
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.
Comment Biometric Time & Attendance for Business Central se compare
| Critère | ÉCOSIRE | Construction personnalisée | Concurrent | Natif Dynamics 365 Business Central |
|---|---|---|---|---|
| Native biometric clock-to-BC attendance out of the box | Inclus | Non inclus | Prise en charge partielle | Non inclus |
| Device-agnostic connector (ZKTeco, Suprema, RFID/NFC, PIN) | Inclus | Prise en charge partielle | Prise en charge partielle | Non inclus |
| Built as update-safe per-tenant AL extension (event subscribers, no base-code edits) | Inclus | Prise en charge partielle | Inclus | Non inclus |
| Tailored to your exact overtime, grace-period and absence rules | Inclus | Inclus | Prise en charge partielle | Non inclus |
| Installed and promoted to production for you (sandbox UAT first) | Inclus | Prise en charge partielle | Non inclus | Non inclus |
| Source code handed over to you | Inclus | Inclus | Non inclus | Non inclus |
| Ongoing support with BC release-wave compatibility checks | Inclus | Prise en charge partielle | Prise en charge partielle | Non inclus |
| Optional Dataverse / Power BI attendance dashboards | Inclus | Prise en charge partielle | Prise en charge partielle | Non inclus |
Foire aux questions sur 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 one working week 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 $999 cover and what is quoted separately?
The $999 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.
Modules associés
Bank Statement Import & E-Reconciliation
A per-tenant Business Central AL extension that imports CSV, XML, MT940 and CAMT.053 bank statements, applies a configurable matching-rules engine, and auto-reconciles transactions against your bank account ledger entries and open customer/vendor invoices — with a clean exception queue for the rest.
Belgium Peppol E-Invoicing
A build-to-order Dynamics 365 Business Central AL extension that posts, validates and transmits Peppol BIS Billing invoices for Belgium's structured B2B e-invoicing mandate through your chosen access point. ECOSIRE builds, installs and supports it after you request a quotation.
Brazil NFe / Fiscal Compliance for Business Central
Brazilian NF-e/NFC-e/NFS-e issuance, complex Brazilian tax calculation, DANFE generation, and SPED-aligned export — built as a per-tenant AL extension on your Business Central environment.
Bulk WhatsApp & SMS Campaigns for Dynamics 365
A build-to-order Business Central AL extension that sends segmented bulk WhatsApp and SMS broadcasts straight from CRM marketing lists, with approved template campaigns, scheduled drips, consent management, and full delivery, read, and reply analytics.
Biometric Time & Attendance for Business Central
A build-to-order Dynamics 365 Business Central extension that connects fingerprint, facial-recognition and RFID/NFC clocks to your tenant, auto-posts punches into timesheets, applies your overtime and absence rules, and exports clean payroll hours. Built, installed and supported by ECOSIRE.
- 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