Quick facts
- Price
- $299.00 USD
- Odoo versions
- 17, 18, 19
- Setup time
- 21 min
- License
- One-time perpetual
- Languages
- 11 languages
One-time Purchase
Attendance Validation & Controls Suite
Layered attendance security for Odoo HR: geolocation, geofence, face recognition, IP-lock, selfie capture and reason logging.
$299.00USD
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
Key Features
IP-address restriction: check-in/check-out allowed only from a configurable corporate IP allowlist per company or work location, with clear rejection messaging and an audit trail of blocked attempts.
Geolocation capture: latitude/longitude recorded on every punch via the browser/kiosk Geolocation API and stored on new fields on the hr.attendance record for later review.
Geofence enforcement: define allowed zones as a radius around a point or a polygon per work location; a compute method (@api.depends on the captured coordinates) sets validation_status to inside, outside or unknown.
Optional face-recognition validation: compare the live capture against an enrolled reference photo on hr.employee, storing a match score and pass/fail so impersonated punches are caught.
Mandatory selfie photo capture: a required binary image field on the attendance record at check-in and/or check-out, viewable by HR in the backend and attached to audit reports.
Reason/notes logging: a required text field enforced on manual entries, overrides, or out-of-geofence punches so every exception carries a documented justification.
Configurable enforcement mode per control: warn-only (log and allow) or hard-block (reject the punch), set independently for IP, geofence, face-match and selfie so you can phase in strictness.
Per-company / per-department / per-location policy: all thresholds, allowlists, zones and tolerances managed from Settings, honoring Odoo multi-company rules — no code changes to adjust policy.
Record-level security: ir.model.access.csv plus record rules so employees see only their own captures and coordinates, while HR managers and auditors get full visibility with least-privilege groups.
Automated flagging actions: base.automation / server actions raise activities, send notifications or tag records when a punch fails a control, so HR reviews only the exceptions.
QWeb audit reports: PDF and list/pivot views summarizing validated vs flagged attendances, geofence violations, IP rejections and face-match failures by employee, department and date range.
Kiosk and Employee self-service integration: OWL/JS widgets extend the standard Attendances kiosk and portal check-in so validation runs at the point of punch, with graceful fallback when a sensor is unavailable.
XML-RPC / JSON-RPC exposure: validation status and capture metadata are readable via Odoo's external API so external time clocks, turnstiles or BI tools can push and pull attendance data.
Privacy-aware retention: configurable purge/anonymization of stored selfies and coordinates after a retention window to keep the module aligned with your data-protection policy.
About this Product
Attendance fraud — buddy-punching, off-site check-ins, spoofed kiosks and "I was here, the system was down" disputes — quietly drains payroll and erodes trust in your HR data. The Attendance Validation & Controls Suite is a build-to-order Odoo module that ECOSIRE designs, builds, installs and supports for your specific policy, wrapping Odoo's native hr.attendance check-in/check-out flow in a layered validation gate: geolocation with polygon/radius geofences, corporate IP-address allowlists, optional face-recognition matching, mandatory selfie capture and a required reason/notes field on manual or out-of-policy actions.
Why Choose Attendance Validation & Controls Suite
IP-address restriction: check-in/check-out allowed only from a configurable corporate IP allowlist per company or work location, with clear rejection messaging and an audit trail of blocked attempts.
Geolocation capture: latitude/longitude recorded on every punch via the browser/kiosk Geolocation API and stored on new fields on the hr.attendance record for later review.
Geofence enforcement: define allowed zones as a radius around a point or a polygon per work location; a compute method (@api.depends on the captured coordinates) sets validation_status to inside, outside or unknown.
Optional face-recognition validation: compare the live capture against an enrolled reference photo on hr.employee, storing a match score and pass/fail so impersonated punches are caught.
Mandatory selfie photo capture: a required binary image field on the attendance record at check-in and/or check-out, viewable by HR in the backend and attached to audit reports.
Reason/notes logging: a required text field enforced on manual entries, overrides, or out-of-geofence punches so every exception carries a documented justification.
This is not an off-the-shelf apps.odoo.com download. We extend the core hr.attendance and hr.employee models with new fields (geo_latitude, geo_longitude, validation_status, capture_image, matched_score, override_reason) and compute logic using @api.depends, add validation on the check_in/check_out write path, enforce access with ir.model.access.csv plus record rules so employees only ever see their own captures, and ship OWL/JS front-end widgets for the kiosk and the Employee self-service portal. HR gets clean dashboards, QWeb PDF audit reports, and automated actions (ir.actions.server / base.automation) that flag or block suspicious punches. Every control is configurable per company, per department or per work location through Settings — no hard-coded rules.
We support Odoo 17, 18 and 19, on Community or Enterprise, and integrate cleanly with Payroll, Time Off and the standard Attendances kiosk. Typical delivery is 2–4 weeks depending on which controls you enable and how much policy customization you need. You get the full source module (no obfuscation, no per-seat licensing lock-in), a staging deployment, admin and end-user training, documentation, and a support window for post-go-live fixes. Because we build it to your rules, edge cases that generic modules ignore — night-shift geofences, multi-site tolerances, VPN allowlists, offline fallback, privacy-compliant retention — are handled the way your policy actually requires.
What you get
- Complete Odoo module source (__manifest__.py, models, views, security, QWeb reports, OWL/JS assets) targeting your Odoo 17, 18 or 19 version — full code you own, no per-seat lock-in.
- Configured validation policy: IP allowlists, geofence zones, face-match thresholds, selfie and reason rules set up per company/department/work location to match your written attendance policy.
- Staging deployment and UAT: the module installed on a staging or test database with sample data so your team validates behavior before it touches production.
- Production installation and go-live support: deployment to your server or Odoo.sh, module upgrade, and post-deploy verification that check-in/check-out flows and reports work end to end.
- Documentation set: admin configuration guide, end-user check-in guide, security/roles reference, and a data-retention/privacy note for your DPO.
- Admin and end-user training sessions (live or recorded) covering configuration, exception review, reporting and troubleshooting.
- Support window after go-live for bug fixes and adjustments, plus a written scope of what's covered and how to reach us.
- Security and access-control setup: ir.model.access.csv, record rules and user groups reviewed with your team so visibility of location and photo data is least-privilege.
Who this is for
HR Operations Manager
Owns attendance accuracy and payroll integrity. Needs to stop buddy-punching and off-site check-ins without turning every punch into a support ticket, and wants clean, defensible reports when a timesheet is disputed.
IT / Odoo Administrator
Responsible for the Odoo deployment across 17/18/19 and multi-company setup. Wants a maintainable module with proper security rules, IP allowlists and API access — not a black-box app that breaks on the next upgrade.
Compliance & Internal Audit Lead
Must prove attendance controls are enforced and that location/biometric data is handled with least-privilege access and a defined retention policy. Relies on the audit reports and reason-logging trail to satisfy reviewers.
Field & Multi-Site Operations Lead
Manages staff across warehouses, clinics, retail outlets or job sites. Needs per-location geofences, night-shift tolerances and offline fallback so genuine on-site workers are never wrongly blocked.
Installation overview
Download from ECOSIRE
Buy the license on ecosire.com and download the Attendance Validation & Controls Suite module ZIP from your account dashboard.
Upload to Odoo
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Install the module
Activate Developer Mode, open Apps, click Update Apps List, search for Attendance Validation & Controls Suite, and press Install.
Configure settings
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Verify & go live
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
How Attendance Validation & Controls Suite Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Layered controls (IP + geofence + face + selfie + reason) in one flow | ||||
| Geofence with polygon and per-location radius enforcement | ||||
| Tailored to your exact attendance policy and edge cases | ||||
| Record-level security so employees see only their own captures | ||||
| Built, installed and supported for you (2–4 week delivery) | ||||
| Supported across Odoo 17, 18 and 19 with upgrade path | ||||
| QWeb audit reports for flagged vs validated attendance | ||||
| Configurable privacy retention for biometric/location data | ||||
| You own full source, no per-seat lock-in |
Frequently Asked Questions about Attendance Validation & Controls Suite
+How long until the module is delivered and installed?
This is a build-to-order module, not an instant apps.odoo.com download. Typical delivery is 2–4 weeks from a confirmed scope, depending on how many controls you enable (IP, geofence, face-recognition, selfie, reason logging) and how much policy customization you need. The flow is: requirements confirmation, build, staging deployment and UAT, then production install and go-live support. Simpler configurations land closer to two weeks; multi-site, multi-company or face-recognition setups closer to four.
+What support and updates do I get after go-live?
Every engagement includes a post-go-live support window for bug fixes and adjustments, with a written scope of what's covered. Because you receive the full source, the module is yours to keep. We also handle version compatibility: if you upgrade Odoo (for example 18 to 19), we can migrate the module. Extended support, enhancement retainers and new-control add-ons are available separately, and we document how to reach us and how issues are triaged.
+Does it work on Odoo Community or only Enterprise, and which versions?
It works on both Community and Enterprise, and we build for Odoo 17, 18 and 19 — you tell us your version and edition and we target it exactly. The suite extends the standard hr.attendance / hr.employee models and the Attendances app, so it sits on top of core HR whether or not you have Enterprise features enabled.
+How does the face-recognition and selfie data stay private and compliant?
Selfie images and location coordinates are stored on the attendance record and protected with ir.model.access.csv plus record rules, so employees see only their own captures and only HR/audit roles get broader visibility. We add a configurable retention policy to purge or anonymize captures after a defined window, and we document the data flow for your DPO. Face recognition is optional — if your policy doesn't allow biometric matching, we ship the suite with geofence, IP and selfie controls instead.
+What happens if GPS, camera or network fails at check-in — do workers get locked out?
Each control has a configurable enforcement mode: warn-only (log the punch and flag it) or hard-block (reject it). You decide per control. For sensor or network failures we implement a graceful fallback — for example, allow the punch but mark validation_status as unknown and require a reason, or queue an offline check-in for later validation. Genuine on-site workers are never silently stranded; exceptions are routed to HR for review via automated actions.
+Can it integrate with our existing time clocks or external systems?
Yes. Validation status and capture metadata are exposed through Odoo's standard XML-RPC / JSON-RPC external API, so external turnstiles, biometric terminals or BI tools can read and write attendance data. We also integrate with native Payroll and Time Off so validated attendance flows into the rest of your HR processes, and we can wire in automated actions to notify managers or raise activities on flagged punches.
Why Customers Trust ECOSIRE
SOC 2 Aligned
GDPR Compliant
Secure Stripe Payment
30-Day Money Back
Lifetime Updates
LGPL-3.0 License
Related Modules
Request a quote
Attendance Validation & Controls Suite
Layered attendance security for Odoo HR: geolocation, geofence, face recognition, IP-lock, selfie capture and reason logging.
- IP-address restriction: check-in/check-out allowed only from a configurable corporate IP allowlist per company or work location, with clear rejection messaging and an audit trail of blocked attempts.
- Geolocation capture: latitude/longitude recorded on every punch via the browser/kiosk Geolocation API and stored on new fields on the hr.attendance record for later review.
- Geofence enforcement: define allowed zones as a radius around a point or a polygon per work location; a compute method (@api.depends on the captured coordinates) sets validation_status to inside, outside or unknown.
- Optional face-recognition validation: compare the live capture against an enrolled reference photo on hr.employee, storing a match score and pass/fail so impersonated punches are caught.