| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Attendances (hr_attendance)
• Employees (hr) • Discuss (mail) |
| Lines of code | 4237 |
| Technical Name |
ntt_biometric_attendance |
| License | OPL-1 |
| Versions | 18.0 19.0 |
Stop attendance chaos. Close payroll with confidence.
Employees scan at the device — Odoo receives attendance automatically. No more daily USB/Excel routines, fewer disputes, and a cleaner path from scans to HR Attendance.
Built for HR teams who want fewer disputes, and for Owners/IT who want stable operations and clear control.
Before vs After
This is the real reason you buy attendance integration: less manual work for HR, fewer payroll disputes, and better visibility for management.
- HR exports USB/Excel daily (or weekly) — easy to miss records.
- Duplicates & inconsistencies create "why is my attendance wrong?" disputes.
- Multiple sites run different processes — hard to standardize.
- When a device has issues, people notice only after data is missing.
- Attendance flows into Odoo automatically — HR spends time verifying, not importing.
- Cleaner records reduce disputes and "payroll panic" at month end.
- Company-wide standardized process across sites.
- Device status visibility: monitor Online/Offline to detect issues early and fix fast.
Why HR teams choose this
Built for HR: cleaner attendance & easier payroll — plus IT control with Online/Offline device monitoring.
Trustworthy attendance, easier disputes
Cleaner, consistent records make it easier for HR to explain attendance and resolve questions calmly.
No more USB/Excel routines
Remove repetitive importing tasks. HR can focus on approvals, policies, and payroll.
Automatic data cleanup
Reduce duplicates and confusion — fewer corrections before closing payroll.
Payroll-ready HR Attendance
Keep a reliable flow into Odoo HR Attendance so month-end closing becomes faster and safer.
Approved devices only
Owners/IT can control which devices are allowed to send attendance into Odoo.
Online/Offline device monitoring
Monitor device connection status (Online/Offline) to detect issues early and fix them quickly.
Setup & Configuration (10 minutes) — do it once, use it reliably for the long term
- Biometric device must support ADMS feature.
- Device must have Internet access.
- Have your Odoo URL address ready (example.ntt-tech.com).
- From Main Menu, select System Info.
- In System Info, select Device Info.
- Take a photo or note down the Serial Number (SN) to enter in Odoo.
- From Main Menu, select COMM.
- Select Cloud Server Setting.
- Enable Enable Domain Name to enter your Odoo URL address.
- Enter Server Address as your Odoo URL (example.ntt-tech.com).
- If you use HTTPS (URL starts with https://), enable HTTPS on the device.
- In Odoo, the device status will change to Online about 10 seconds after configuration is complete.
Practical outcomes you'll feel day 1 — less manual work for HR, cleaner data for payroll, and clearer visibility for managers.
Requirements
Not sure? Send the device model + screenshot of "Cloud Server / ADMS" page. We'll confirm compatibility before purchase.
FAQ
Device stays Offline in Odoo
- Confirm the device in Odoo (approved/whitelisted).
- On the device: verify Cloud Server / ADMS is enabled and Server Address is correct.
- Make sure the device can reach your Odoo address. Try a different network if needed.
- Enable HTTPS on the device.
Employees scan, but no attendance appears
- Please make sure your device is in Online status
- Re-check Server Address (domain spelling) and ensure Enable Domain Name is set (if required by your device).
- Restart the device once after configuration (quick recovery step).
Wrong time / late check-in in Odoo
- Set the correct Timezone on the device record in Odoo. Then click "Upload Setting".
Duplicates or missing records during payroll closing
- Avoid mixing manual USB/Excel imports with PUSH at the same time.
- Use the built-in sync flow (raw logs → HR Attendance) to keep records consistent.
- If you need to recover history, use Get attendance data.
Do I need middleware or a local PC?
No. The device pushes directly to Odoo via ADMS/iClock endpoints, and Odoo manages the queue + synchronization.
Do I need to open ports on the device?
The connection is device-initiated, so Odoo doesn't "connect into" the device. You still need an Odoo URL reachable by the device network (public domain, VPN, or tunnel).
What happens if the device goes offline?
When the device reconnects, it can continue pushing data. You can also download attendance by date range for recovery.
Can I sync only a specific date range for payroll closing?
Yes. Use the download wizard to request ATTLOG between StartTime/EndTime (command-based).
Does it support biometrics like face or vein?
The module can store biometric templates uploaded by the device (type depends on your device capabilities). Remote enrollment from Odoo is available for fingerprint (guided at device).
Support that reduces your risk
Pre-sales compatibility check + roll-out support. Attendance is mission-critical — we treat it that way.
Pre-Sales
- Odoo version (CE/EE/Odoo.sh)
- Device model name
- Screenshot of "Cloud Server / ADMS" page
- Provide screenshots or videos, if available.
Support
- A description of the issue you're experiencing
- Your expectations for resolving the situation
- Include images or videos that replicate the issue
- Your order number and attach a screenshot
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module