The Problem: The “Excel Export” Nightmare

Most companies have a biometric machine at the gate and a cloud HRMS like Keka for payroll. However, they are often completely disconnected. Every month, an HR admin has to physically take a USB drive, download a file from the biometric machine, format it in Excel, fix the errors, and upload it to Keka.

This manual process is slow, prone to human error, and leads to endless payroll disputes with employees.

The Solution: Real-Time Data Sync

We configure your existing biometric hardware to communicate directly with your HRMS software. When an employee punches in, the data travels securely over your office network or the internet and updates their attendance record in Keka instantly.

How We Connect Your Hardware to Keka

Keka is a cloud-based platform, while your biometric machine sits on-premise. There are three ways to bridge this gap, and we implement the best one based on your IT infrastructure:

1. Push-Based Integration (ADMS/WDMS): If your biometric device supports ADMS (Automatic Data Master Server), we configure it to push data directly to Keka’s cloud API over the internet. This is the cleanest and most hands-free method.

2. SDK / Middleware Integration: If your machine is older and does not support direct cloud push, we install a lightweight middleware software on a local office PC. This software reads the logs from the machine and pushes them to Keka.

3. API-Based Sync: For custom setups, we use Keka’s open API to create a secure, automated sync schedule (e.g., every 15 minutes).

What We Configure During the Setup

Integration is not just about a network cable. We ensure the data makes sense to your HR team:

• Employee Mapping: We map the biometric User ID of every employee to their unique Keka Employee ID.

• Shift & Roster Rules: Keka handles complex shifts. We ensure the raw punches from the machine are correctly interpreted by Keka based on your day, night, and rotational shift policies.

• Leave & Holiday Sync: We configure the system so employees on approved leave in Keka are not marked absent if they don’t punch in.

• Overtime (OT) Rules: We ensure pre-shift and post-shift overtime punches are captured accurately and passed to Keka for payroll calculation.

Why Choose Us? Local Presence + Technical Expertise

You could hire a remote freelancer to set up an API, but if your office network crashes, they can’t help you.

We are a physical systems integrator based in Delhi NCR. We understand the hardware (eSSL, ZKTeco), the networking (LAN, Wi-Fi, Firewalls), and the software (Keka, greytHR). If there is a physical wiring issue or a local network block, our technicians can visit your office in Gurugram, Delhi, or Noida to fix it on-site.

(For clients outside Delhi NCR, we provide complete remote integration and support).

HRMS & Software We Support

We provide integration services for all major Indian and global HRMS platforms:

• Primary Integrations: Keka, greytHR, RazorpayX, HROne.

• Enterprise ERPs: SAP, Oracle, Microsoft Dynamics.

• Other Software: Zoho People, Spine HR, and custom in-house ERPs.

• Biometric Brands: eSSL, ZKTeco, Matrix, Hikvision, Suprema.

Areas We Serve

On-Site Integration & Support: Delhi NCR (Gurugram, Delhi, Noida, Greater Noida, Ghaziabad, Faridabad).
Remote Integration: Pan-India.

Frequently Asked Questions

Can you integrate our existing (old) eSSL machine with Keka?

Yes. As long as the machine is functional and has network capabilities, we can usually integrate it with Keka using our SDK or middleware solutions. You do not necessarily need to buy new hardware.

Does this integration require a dedicated computer to be left on?

It depends on the method. If your machine supports direct cloud push (ADMS), no computer is needed. If we use a middleware sync method, a basic office PC needs to be left on during working hours to act as the bridge.

What happens if the internet goes down?

Your biometric machine will continue to store punches locally in its memory. Once the internet connection is restored, the machine or middleware will automatically push the backlog of punches to Keka. No data is lost.

Is the data secure?

Yes. We use secure API tokens and encrypted connections. We do not store your employee data on third-party servers; the data flows directly from your device to your Keka account.

Can we track contract labor in Keka through this?

Keka is primarily designed for permanent employees. If you have a large contract workforce, we can integrate the biometric machine with a Contractor Labour Management System (CLMS) and then sync the consolidated data to Keka.

How long does the integration take?

A standard setup for a single machine and basic shift rules usually takes 3 to 5 working days, including testing and HR training. Complex multi-location setups take longer.