イメージプレビューLayered attendance security for Odoo HR:
geolocation, geofence, face recognition, IP-lock, selfie capture and reason logging.
Attendance Validation & Controls Suiteとは？
Layered attendance security for Odoo HR: geolocation, geofence, face recognition, IP-lock, selfie capture and reason logging. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $999.00 USD; request a quote for a scoped proposal.
主な機能
受注生産、すべておまかせ
自分での設定は不要 — ECOSIRE が構築・インストール・サポートする実働アプリです。
- 1
ご注文
一回限りの構築料金から始めます。キックオフで一緒に範囲を決めます。
- 2
構築とインストール
ECOSIRE がお客様の Odoo 上で構築・設定・インストールします。
- 3
本番稼働 + サポート
約1週間（営業日ベース）で稼働し、本番稼働後2週間のサポートが付きます。納品したコードの不具合は無償で修正します。
技術仕様
- Odoo互換性
- Odoo 17, Odoo 18, Odoo 19
- エディション
- Enterprise＆Community
- ライセンス
- ライセンスの確認が必要です
- Python要件
- Python 3.10+
- データベース
- PostgreSQL 12+
この製品について
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.
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 one working week 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.
得られるもの
- 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.
これは誰のためのものですか
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.
Attendance Validation & Controls Suite の比較方法
| 基準 | エコシエール | カスタムビルド | 競合他社 | Odoo 標準機能 |
|---|---|---|---|---|
| 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 (one working 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 | 付属 | 付属 | 含まれていない | 付属 |
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 one working week 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.
関連モジュール
Attachment Preview In-Browser for Odoo
A made-to-order Odoo capability that renders PDF, Word, Excel, and PowerPoint attachments directly inside the chatter and document views — no downloads, no context-switching. ECOSIRE builds, installs, and supports it against your exact Odoo version and workflows.
Audit Trail & SoX Compliance Log
An immutable, field-level audit trail for Odoo accounting — capturing who changed what, when, from which IP, with full before/after value diffs and tamper-evident locking your auditors can trust. Built to order, installed and supported by ECOSIRE.
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.