HR Tech & HRMS

HRMS, payroll, and workforce apps — built for Indian compliance.

eCorpIT builds custom HRMS and configures Zoho, Keka, greytHR and Darwinbox — payroll, PF, ESI, TDS, attendance and self-service, engineered against the four Labour Codes and designed aligned with DPDP Act, 2023 requirements. Multi-vendor by design. Priced per legal entity. CMMI Level 5 process discipline.

  • CMMI Level 5
  • Microsoft Partner — Dynamics 365 + Power Platform
  • Multi-vendor — Zoho, Keka, greytHR, Darwinbox, custom
  • Designed aligned with DPDP Act, 2023 requirements
  • Source code & configurations 100% yours
  • NDA before any technical discussion

What HR Tech & HRMS means at eCorpIT

Payroll that still calculates correctly after your third statutory rate change.

HR Tech & HRMS at eCorpIT is the design, build, configuration and integration of the software that runs your workforce — custom HRMS, payroll and statutory compliance for PF, ESI, TDS, Professional Tax and Labour Welfare Fund, attendance and field-ops apps, HRMS-to-ERP integration, and DPDP remediation — whether you build custom or configure Zoho, Keka, greytHR or Darwinbox.

Most engagements draw on three. Common patterns:

  • Config Payroll Zoho / Keka rollout re-engineered under the 50% wage rule
  • Custom HRMS Attendance Multi-entity build with biometric-to-payroll integration
  • Payroll DPDP Legacy schema remediation with erasure and consent paths

What we build

Four HR-tech sub-disciplines. Open one. See exactly what we ship.

Most engagements draw on three — a mid-market rollout needs configuration, payroll re-engineering and attendance; a group build anchors on custom HRMS with a DPDP-first schema from day one.

Sub-discipline 1 of 4

Custom HRMS Development

Custom HRMS Development at eCorpIT covers the design and build of workforce-management software when off-the-shelf HRMS does not fit — for organisations with contractor networks, blended gig-plus-payroll workforces, multi-entity structures, per-shift or per-piece pay, field workforces, or industry constraints that Zoho, Keka, greytHR and Darwinbox cannot represent without invasive customisation.

What we deliver

  • Custom HRMS architecture — modular design covering employee master, org structure, payroll, attendance, leave, benefits, performance, self-service and reporting, with effective-dated history from day one because retrofitting effective dating is close to a rewrite.
  • Industry-specific HRMS modules — manufacturing (shift-based pay, contractor management), retail and hospitality (rostering, tip pooling, cash reconciliation), logistics (driver apps, per-trip pay), healthcare (rostering, on-call, compliance), IT services (billable-hours to payroll, project cost attribution).
  • Multi-entity, multi-state architecture — one platform, many legal entities, distinct professional tax and Labour Welfare Fund matrices per state, consolidated reporting up.
  • HRMS-mobile companion apps — employee self-service, field-ops apps, shop-floor interfaces, executive dashboards on Flutter or React Native, shared backend.
  • HRMS integration layer — connecting HRMS to ERP (SAP, Tally, Dynamics, NetSuite), biometric hardware, banking, statutory portals and third-party payroll processors.
  • DPDP-first schema design — erasure paths, consent records, biometric-data handling and audit trails engineered into the data model from the start, not bolted on later.

Tech stack (16)

  • Node.js
  • NestJS
  • Django
  • FastAPI
  • Java Spring Boot
  • .NET Core
  • PostgreSQL
  • MongoDB
  • Redis
  • React
  • Next.js
  • Flutter
  • React Native
  • MuleSoft
  • Kafka
  • BullMQ

Use cases we've shipped

Custom HR and workforce work across manufacturing, education, healthcare and infrastructure clients, including multi-entity payroll consolidation, biometric-attendance to payroll integration, contractor-management systems, and executive HR dashboards for founder-led groups.

Sub-discipline 2 of 4

HRMS Configuration & Rollout

HRMS Configuration at eCorpIT covers Zoho Payroll, Zoho People, Keka, greytHR and Darwinbox rollouts plus the customisation, integration and ongoing administration that turns a deployed system into a used system.

What we deliver

  • Zoho Payroll implementation (India) — configuration of statutory components (PF, ESI, TDS, LWF, PT), salary templates rebuilt against the Code on Wages 50% rule, Form 16 with digital signature, Form 24Q, TDS challan generation. Zoho Payroll India pricing is free up to 10 employees and runs ₹1,000 / ₹3,000 / ₹4,000 per organisation per month on annual billing, plus ₹40 / ₹60 / ₹80 per additional employee, exclusive of GST. A 200-employee company on Premium annual billing pays approximately ₹1.92 lakh per year.
  • Zoho People implementation — HR core, attendance, leave, performance and shift-scheduling; India tiers reported between ₹50 and ₹230 per employee per month.
  • Keka implementation — HR + payroll + performance suite; India tiers reported at ₹9,999 to ₹15,999 per month base plus ₹90 to ₹150 per additional head.
  • greytHR implementation — payroll-first with statutory strength; reported from roughly ₹3,495 per month at 50 employees.
  • Darwinbox implementation — enterprise HRMS quoted on scope; we run the discovery and configuration but do not publish rate cards Darwinbox itself does not.
  • Dynamics 365 HR implementation (Microsoft Partner) — Sales, Customer Service, Finance, Supply Chain and HR modules configured, customised and integrated.
  • Per legal entity licencing — under Zoho Payroll's published terms, a separate licence is required for each legal entity while multiple branches of one entity can share a single licence. Group structures with three or four Indian entities should price the subscription accordingly before comparing against a build.
  • Migration from legacy HRMS — Tally payroll, in-house Excel-based payroll and older cloud HRMS platforms migrated with data integrity, parallel-run and reconciliation to the rupee.

Tech stack (12)

  • Zoho Payroll
  • Zoho People
  • Keka
  • greytHR
  • Darwinbox
  • Microsoft Dynamics 365 HR
  • SAP SuccessFactors
  • Workday
  • HubSpot
  • Zapier
  • Workato
  • MuleSoft

Use cases we've shipped

Zoho Payroll rollouts for mid-market Indian clients standardising on the Zoho One suite. Keka and greytHR implementations for services and IT clients. Multi-entity Zoho deployments for group structures with three to five Indian entities.

Sub-discipline 3 of 4

Payroll & Statutory Compliance

Payroll & Statutory Compliance Engineering at eCorpIT covers the specific engineering work required to bring a payroll system — bought or built — into compliance with the four Labour Codes (effective 21 November 2025) and the underlying statutory rate structure.

What we deliver

  • Salary structure re-engineering under the 50% rule. Section 2(y) of the Code on Wages defines wages as basic pay, dearness allowance and retaining allowance, and caps excluded allowances at 50% of total remuneration. Every salary template, CTC calculator, offer-letter generator, arrears computation and historic payslip regeneration path rebuilt against the new definition. Legal commentary places the aggregate statutory cost increase at 5% to 15% for most employers, concentrated in IT services, BPO, retail and hospitality.
  • Statutory rate coverage — EPF (employee 12% of wages, wage ceiling ₹15,000/month), EPF employer (12%, split 3.67% EPF and 8.33% EPS, plus 0.50% EDLI and 0.50% admin), ESI (employee 0.75% / employer 3.25% of gross, gross up to ₹21,000/month), TDS (slab-based, Form 24Q quarterly, Form 16 annually), Professional Tax (state-specific matrix), Labour Welfare Fund (state-specific). The rates did not move under the Codes; the base they apply to did.
  • Filing and document generation — Form 16 with digital signature, Form 24Q, TDS challan recording, PF ECR, ESI monthly return, Professional Tax filings, LWF filings, compliance calendar with escalation rules.
  • Labour Codes obligations — appointment letters generated and versioned per worker, gratuity accrual from year one for fixed-term employees, aggregator contributions for gig and platform workers (1% to 2% of turnover capped at 5% of amounts paid), single-registration / single-licence / single-return workflows, salary release by the 7th for IT and ITES workers as a hard cut-off.
  • Parallel-run engineering — two to three payroll cycles running the old and new systems side by side, reconciled to the rupee before cutover. The step teams skip and the step that catches wage-definition errors before an employee’s take-home pay is wrong.
  • In-hand pay communication tooling — when basic rises to meet the definition, employee EPF at 12% of basic rises with it and monthly in-hand pay falls for anyone previously on a 30% basic structure. Total compensation is unchanged and retirement corpus grows faster, but employees notice the smaller number first. We build the before-and-after payslip breakdown and PF-gain projection views that convert a compliance change into a communicated change.

Tech stack (10)

  • Custom payroll engines
  • Zoho Payroll
  • Keka Payroll
  • greytHR
  • Rain
  • RazorpayX Payroll
  • TDS challan APIs
  • EPFO ECR portal
  • ESIC portal
  • digital signature integrations

Use cases we've shipped

Payroll re-engineering under the 50% wage rule for services, IT and manufacturing clients. Statutory compliance overhaul programmes across multi-entity Indian group structures. Parallel-run and cutover for legacy-to-cloud payroll migrations.

Sub-discipline 4 of 4

Attendance, Leave & Field-Ops Apps

Attendance, Leave & Field-Ops Apps at eCorpIT covers the mobile and mixed-hardware workforce systems that sit upstream of payroll — the source-of-truth layer where accuracy determines everything downstream, and where DPDP obligations bite hardest because biometric data is involved.

What we deliver

  • Biometric attendance integration — fingerprint, face and retina hardware wired into a central platform, with explicit consent flows, encryption at rest, deletion when the purpose ends (typically at employee exit), and no third-party sharing without fresh consent. A biometric attendance system with no deletion path is a DPDP liability, and a surprising number of deployed systems have none.
  • Mobile self-service apps — payslip download, tax declarations, reimbursements, approvals, leave application, comp-off, WFH marking, shift-swap, on-call rostering, expense claims — on Flutter or React Native with offline-first design where field connectivity is unreliable.
  • Geo-fenced field attendance — driver, sales, service and installation workforces marked in and out against defined geo-fences, with photo-verification and manager exception workflows.
  • Rostering and shift-scheduling engines — for retail, hospitality, healthcare and logistics operations where the shift is the atomic pay unit and the roster is the operational plan.
  • Leave engines — statutory leave, earned leave, sick leave, casual leave, maternity, paternity, sabbatical, LOP, gratuity-relevant service tracking, with state-specific and industry-specific rule overlays.
  • HR-as-a-product surfaces — where the employee app is customer-facing or field-facing (a hospital's rostering app, a logistics driver app, a retail chain's shift-swap app), HR data becomes part of your product and lives where your product lives.

Tech stack (14)

  • Flutter
  • React Native
  • Node.js
  • NestJS
  • FastAPI
  • PostgreSQL
  • MongoDB
  • Redis
  • Firebase Cloud Messaging
  • APNs
  • MapmyIndia
  • Google Maps Platform
  • ZKTeco / Matrix / eSSL
  • custom hardware bridges

Use cases we've shipped

Field-ops mobile apps for service and installation businesses. Biometric-attendance integration for manufacturing and hospitality clients. Geo-fenced attendance for distributed field sales teams. Mobile self-service across services, education and healthcare clients.

Full tech stack

The vendors, platforms, and tools we deploy in production.

HRMS & payroll platforms

  • Zoho Payroll
  • Zoho People
  • Keka
  • greytHR
  • Darwinbox
  • Microsoft Dynamics 365 HR
  • SAP SuccessFactors
  • Workday
  • Rain
  • RazorpayX Payroll
  • Tally payroll (migration)
  • Custom HRMS builds

Integration & middleware

  • MuleSoft Anypoint
  • Workato
  • Tray.io
  • Zapier
  • Make
  • n8n
  • Apache Kafka
  • RabbitMQ
  • AWS EventBridge
  • Azure Service Bus
  • Apigee
  • Kong
  • AWS API Gateway

Statutory & filing integrations

  • EPFO ECR portal
  • ESIC portal
  • TRACES
  • TDS challan APIs (NSDL)
  • Professional Tax portals
  • Labour Welfare Fund portals
  • digital signature (DSC)
  • GST integrations
  • Aadhaar-based verification

Attendance hardware & mobile

  • ZKTeco
  • Matrix
  • eSSL
  • Realtime
  • Suprema
  • Firebase Cloud Messaging
  • APNs
  • MapmyIndia
  • Google Maps Platform
  • Flutter
  • React Native
  • offline-first sync

Backend frameworks

  • Node.js
  • NestJS
  • Django
  • FastAPI
  • Java Spring Boot
  • .NET Core
  • Go
  • PostgreSQL
  • MongoDB
  • Redis

Frontend

  • React
  • Next.js
  • Vue
  • Angular
  • Microsoft Power Apps
  • Salesforce Lightning

How we deliver HR-tech engagements

A 5-step framework with statutory modelling and a parallel run before every go-live.

  1. Weeks 0–3

    Statutory Model & Discovery

    Free 30-minute call, then a structured 1–3 week discovery: process documentation, entity and state inventory, statutory rate matrix, integration map, DPDP obligation register, target-state architecture. We define wages under Section 2(y), the contribution rules, and the state-wise Professional Tax and Labour Welfare Fund matrix before any interface work — getting this wrong late is the most expensive failure mode in HR tech. NDA before any technical conversation.

    • 30-min call
    • Statutory model first
    • Phased delivery plan
  2. Weeks 3–N

    Configuration or Custom Build

    Off-the-shelf platforms (Zoho, Keka, greytHR, Darwinbox, Dynamics 365 HR) configured. Custom HRMS modules and customisations developed in two-week sprints. Custom payroll engines follow the same sprint cadence with weekly demos.

    • Platform config
    • Two-week sprints
    • Weekly demos
  3. Pre-go-live

    Integration & Data Migration

    Biometric hardware, ERP and banking connectors built. Master data — employee master, org structure, historic payslips, leave balances, statutory balances — migrated, validated, reconciled. Cutover plan rehearsed. Rollback procedures documented before go-live.

    • Master data migration
    • Cutover rehearsal
    • Documented rollback
  4. Pre / at go-live

    UAT, Parallel Run, Training & Go-Live

    User acceptance testing with documented test scripts. Parallel run of two to three payroll cycles with old and new systems side by side, reconciled to the rupee. Role-based training for HR ops, payroll ops, managers and employees. Job aids and quick-reference guides. White-glove go-live support. In-hand pay communication built and sent to employees before their first live payslip.

    • Documented UAT
    • Parallel run
    • White-glove go-live
  5. Post-launch → ongoing

    Hypercare & Managed Services

    Hypercare period (typically 4–8 weeks post-go-live) with elevated support. Transition into managed services or hand-off to your in-house team. Quarterly system reviews tracking adoption, statutory-rule updates, and the next phase of work.

    • 4–8 week hypercare
    • Managed handover
    • Quarterly reviews

Engagement models

Six ways to work with us — every one an outcome we own.

There is no staff-augmentation line here on purpose. We take responsibility for the result, not for filling a seat. Pick the shape that fits the decision in front of you.

  1. Discovery & Prototype Sprint

    First engagement / HR platform validation. Fixed-fee sprint that de-risks a bigger decision.

    2–4 weeks · 2–3 senior · Flat fixed fee

  2. Fixed-Scope Project

    Clearly defined initiatives — Zoho / Keka rollout, payroll re-engineering, single-app builds.

    4–16 weeks · 2–6 engineers · Fixed + milestones

  3. Dedicated HR-Tech Pod

    Ongoing HR-platform product work. A senior pod operates as your engagement team.

    Ongoing · 3–8 senior · Monthly retainer

  4. Long-Term HR-Tech Partnership

    Group HR platforms across multiple entities and phases.

    6+ months · Scoped per phase · Retainer + outcome

  5. Managed HR-Tech Services

    Post-go-live operations. Predictable monthly retainer, SLA-backed.

    Always-on · Ops + support · Monthly + SLA

  6. Fractional CHRO-Tech + Pod

    Founder-led companies without a technical HR head.

    3+ months · 1 HR-tech lead + 2–4 engineers · Monthly retainer

Real HR-tech work

Workforce systems across our client base. Described by sector.

HR and payroll work stays inside NDAs. Here's where it shows up across our client portfolio, by sector and scope.

  • Manufacturing

    Multi Solar · Multi Infrastructure · MTBPL

    Operational and workforce systems for solar and infrastructure business. Shift-based pay, contractor management, safety compliance, field-team mobile apps and consolidated payroll across engineering group entities.

    • Custom HRMS
    • Contractor management
    • Shift-based pay
    • Safety compliance
  • Education

    HSBF · Candila Education · Dhaumya Academy

    Institutional HR and workforce systems for banking/finance training and academy clients. Faculty payroll, adjunct contracts, leave and academic-year rostering.

    • Faculty payroll
    • Adjunct contracts
    • Academic rostering
    • Leave engines
  • Healthcare & wellness

    Care2Solution · TrustingMinds · Furrvana

    HR and rostering for healthcare and wellness clients. Clinical rostering, on-call, DPDP-aligned employee data, patient-privacy separation from HR data.

    • Clinical rostering
    • On-call
    • DPDP-aligned
    • HIPAA-aware
  • Finance

    Exora Wealth · Candila Capital

    HR and workforce systems for wealth-management and capital-advisory clients. Advisor and RM compensation structures, incentive engines, KYC-aligned employee onboarding.

    • Advisor compensation
    • Incentive engines
    • KYC onboarding
    • Multi-state PT

Reference HR-tech patterns across industries

  • Multi-entity payroll consolidation for Indian group structures

  • Zoho Payroll and Zoho People rollouts across group entities

  • Keka and greytHR implementations for services and IT businesses

  • Custom rostering for hospitality and healthcare clients

  • Geo-fenced attendance for distributed field workforces

  • Biometric-attendance to payroll integration for manufacturing

  • Salary structure re-engineering under the 50% wage rule

  • DPDP remediation on legacy payroll schemas

Industries we serve

Eight workforce models, each with its own compliance edge cases.

Payroll and attendance rules differ by sector — shift pay, gig-worker contributions, clinical rostering, salary-release cut-offs. We build to the model, not to a template.

  • Manufacturing

    Shift-based pay, contractor management, IIoT-integrated attendance, safety compliance.

  • Retail & hospitality

    Rostering, tip pooling, cash reconciliation, high-turnover onboarding, mobile-first self-service.

  • Healthcare

    Clinical rostering, on-call, HIPAA-aware separation of patient and employee data, DPDP-aligned biometric handling.

  • IT services & BPO

    Billable-hours to payroll, project cost attribution, salary release by the 7th (Labour Codes hard cut-off), high-volume statutory compliance.

  • Logistics & mobility

    Driver apps, per-trip pay, geo-fenced attendance, contractor and platform-worker handling under the gig-worker provisions of the Social Security Code.

  • Education

    Faculty payroll, adjunct contracts, academic-year rostering, leave engines.

  • Finance & fintech

    Advisor and RM compensation, incentive engines, KYC-aligned employee onboarding, multi-state PT.

  • Startups & enterprises

    MVP HR platforms for founders, modernisation and DPDP remediation for enterprise teams.

Why eCorpIT for HR tech

Seven commitments. Including telling you to buy, when buying is the right answer.

  1. Multi-vendor by design.

    We work across Zoho, Keka, greytHR, Darwinbox, Microsoft Dynamics 365 HR and custom builds. Most HR-tech shops are committed to one platform and bend every problem to fit it. We pick the platform that fits your workforce model — including telling you when no off-the-shelf product fits and a custom build is the right answer, and telling you the opposite when it is not.

  2. We will tell you to buy, when buying is the right answer.

    Most companies under 500 employees should buy Zoho, Keka, greytHR or Darwinbox and spend the engineering budget on the layer above it. We turn away build engagements that should be configuration engagements. That is the same answer we give in the discovery call.

  3. Applications designed aligned with DPDP Act, 2023 requirements from the schema up.

    Erasure paths, consent records, biometric-data handling and audit trails engineered into the data model from day one — not bolted on after go-live. Retrofitting erasure into a payroll schema with a decade of denormalised history is the expensive version of DPDP compliance, and we have done it enough times to know which parts hurt.

  4. Statutory model first.

    We define wages under Section 2(y) of the Code on Wages, the contribution rules, and the state-wise Professional Tax and LWF matrix before any interface work. Getting this wrong late is the most expensive failure mode in HR tech, and it is the failure mode we have seen most often on projects we inherited from other vendors.

  5. CMMI Level 5 process discipline applied to payroll.

    Payroll systems run for a decade or more. CMMI Level 5 process controls — documented configurations, peer-reviewed customisations, versioned releases, drift detection — are why the customisations we ship still calculate correctly after your third round of statutory rate changes.

  6. Real cross-system integration depth.

    Most HR-tech vendors do configuration but rely on partners for integration. We run System Integration & Middleware as a full sub-discipline in-house — MuleSoft, Workato, Kafka, custom event-driven architectures. HRMS-to-ERP, HRMS-to-biometric, HRMS-to-banking — under one engagement.

  7. Source code, configurations and IP are 100% yours.

    Custom modules, Zoho / Keka / Darwinbox configurations, Apex, Power Platform configurations, integration code, IaC — committed to your repositories. We never operate HR systems in our environments on your behalf. You can switch vendors any time. NDA before any technical conversation.

DPDP Act, 2023

Applications designed aligned with DPDP Act, 2023 requirements — from the schema up.

The DPDP Rules were notified in November 2025 with an 18-month implementation phase. Full compliance is required by mid-May 2027, and penalties under the Act reach ₹250 crore. The useful part for an HRMS decision is what the Act does NOT require: processing employee data to fulfil employment obligations and statutory compliance (PF, ESI, TDS) falls under legitimate uses and does not need separate consent. Processing outside that — using employee data for marketing or sharing it with third parties — does.

  • Biometric attendance needs explicit handling.

    Fingerprint, face and retina data used for attendance is sensitive personal data. It needs informed consent before collection, encryption at rest, deletion when the purpose ends (typically at exit), and no third-party sharing without fresh consent. A biometric attendance system with no deletion path is a liability.

  • Notice and withdrawal have to be real.

    Notices must be itemised and separate from general terms, in clear language, available in English or a Schedule VIII language, with a working mechanism to withdraw consent, exercise rights and raise grievances. Withdrawal must be as easy as consent was.

  • Erasure and breach paths must exist in the schema.

    Personal data has to be erasable on consent withdrawal or when the retention purpose ends, and breaches must be notified to the Data Protection Board and to each affected person. Retrofitting erasure into a payroll schema with a decade of denormalised history is the expensive version.

"Designed aligned with DPDP Act, 2023 requirements" describes how we engineer the data model. It is not a legal certification or a substitute for your own compliance sign-off.

Transparent HR-tech pricing

Typical engagement ranges. Real numbers, not "contact us" gates.

HR-tech pricing depends on entity count, employee volume, whether you build or configure, and integration scope. These are indicative ranges based on our typical engagements. All prices are exclusive of GST.

Engagement India (INR) Global (USD) Timeline Structure
Custom HRMS Development ₹35L – ₹85L $42K – $100K 20–36 weeks Fixed-scope + milestones
Payroll & Statutory Compliance Engineering ₹6L – ₹24L $7K – $29K 6–14 weeks Fixed-scope
Attendance, Leave & Field-Ops Mobile App ₹5L – ₹18L $6K – $22K 8–14 weeks Fixed-scope
Legacy HRMS Migration (Tally / Excel / cloud) ₹15L – ₹55L $18K – $66K Multi-quarter Phase-gated
HRMS ↔ ERP / CRM Integration ₹3L – ₹14L $4K – $17K Scope-dependent Fixed-scope
DPDP Remediation on Existing HR Data ₹4L – ₹20L $5K – $24K 6–14 weeks Fixed-scope
Managed HR-Tech Services from ₹1.5L / month from $1.8K / month Ongoing Monthly retainer
Dedicated HR-Tech Pod Monthly retainer Monthly retainer Ongoing Monthly retainer

INR and USD pricing with GST invoicing available. Milestone-based payments standard. Managed HR-tech services and dedicated pods bill on a monthly retainer.

Frequently asked questions

HR Tech, answered.

What HR-tech services does eCorpIT offer?
eCorpIT delivers custom HRMS development, HRMS configuration and rollout across Zoho Payroll, Zoho People, Keka, greytHR and Darwinbox, payroll and statutory compliance engineering for PF, ESI, TDS, Professional Tax and Labour Welfare Fund, attendance and leave systems, biometric integration, field-ops mobile apps, HRMS-to-ERP integration and DPDP remediation on existing employee data schemas.
Should we build our own HRMS or buy Zoho, Keka, greytHR or Darwinbox?
Most companies under 500 employees should buy. Building is justified when your workforce model cannot be represented in packaged tools, when HR data is part of a customer-facing product, when data residency rules prevent multi-tenant hosting, or when integration cost with an existing ERP approaches the cost of building natively. We will tell you which case applies in discovery.
How much does an HRMS project cost in India in 2026?
Custom HRMS development runs ₹35–85 lakh over 20–36 weeks. Configuration on Zoho, Keka, greytHR or Darwinbox runs ₹4–18 lakh over 4–12 weeks. Payroll and statutory compliance engineering runs ₹6–24 lakh. Managed HR-tech services start from ₹1.5 lakh per month. Reference SaaS: Zoho Payroll Premium at 200 employees is approximately ₹1.92 lakh per year.
What changed for Indian payroll on 21 November 2025?
The Government made all four Labour Codes effective that day, rationalising 29 central labour laws. The Code on Wages redefined wages as basic pay plus dearness allowance and retaining allowance, and capped excluded allowances at 50% of remuneration. Legal commentary places the aggregate statutory cost increase at 5–15%, concentrated in IT, BPO, retail and hospitality.
Does the 50% wage rule change what our HRMS has to compute?
Yes. Every salary template, CTC calculator, offer-letter generator, arrears computation and historic payslip regeneration path has to be rebuilt against a new definition of wages. This is not a configuration change — it is a change to the primitive that the rest of payroll is derived from. Statutory rates did not move; the base they apply to did.
Do we need one payroll licence per legal entity?
Under Zoho Payroll's published terms, yes. A separate licence is required for each legal entity, while multiple branches of a single entity can run on one licence. Group structures with three or four Indian entities should price the subscription accordingly before comparing against a build. Keka, greytHR and Darwinbox have their own entity-scoping rules that we confirm during discovery.
What does DPDP require for employee data?
Processing for employment obligations and statutory compliance such as PF, ESI and TDS falls under legitimate uses and needs no separate consent. Anything beyond that does. Biometric attendance data needs explicit consent, encryption at rest, and deletion once its purpose ends, typically at employee exit. Full compliance is required by mid-May 2027 and penalties under the Act reach ₹250 crore.
Does eCorpIT integrate HRMS with our ERP and biometric hardware?
Yes. HRMS-to-ERP integration (Zoho-to-Tally, Keka-to-Dynamics, Darwinbox-to-SAP, custom-to-NetSuite) and biometric integration (ZKTeco, Matrix, eSSL, Suprema) run as a full sub-discipline in-house. Typical HRMS-to-ERP integration runs ₹3 lakh to ₹14 lakh depending on entity count and event volume, with two-way sync of employee master, cost centre, payroll journals and reimbursements.
Will our source code and configurations belong to us?
Yes. Custom modules, Zoho / Keka / Darwinbox configurations, Apex code, Power Platform configurations, integration code, IaC and infrastructure — all committed to your repositories and owned by you. You can switch vendors at any time. We never operate HRMS or payroll systems in our environments on your behalf; deployment is always to your cloud accounts under your control.
How does the parallel run work and why does it matter?
Two to three payroll cycles run the old and new systems side by side, reconciled to the rupee before cutover. This is the step teams skip when a programme runs late, and it is the step that catches wage-definition and arrears errors before they reach an employee's bank account. We build the parallel-run engine into every engagement.
Is eCorpIT CMMI-certified for HR-tech delivery?
Yes. eCorpIT is CMMI Level 5, the highest level in the CMMI for Development model. HR-tech engagements run under CMMI Level 5 process controls — documented configurations, peer-reviewed customisations, versioned releases, drift detection. Payroll runs for a decade, so the process controls matter more here than in many other software categories.
How do I start an HR-tech project with eCorpIT?
Fill the project estimate form or book a 30-minute discovery call. NDA signed before any technical conversation. Within 24 working hours, a senior solution architect responds with recommended approach — build, buy or configure — indicative pricing range, and delivery timeline. If configuration is the right answer, we will say so, and we will scope the configuration honestly.

New HRMS? Payroll re-engineering? Build vs buy? DPDP remediation? Let's scope it.

Free 24-hour HR-tech estimate from a senior eCorpIT solution architect. Custom HRMS, Zoho / Keka / greytHR / Darwinbox configuration, payroll and statutory compliance, attendance and field-ops apps, or DPDP remediation. NDA before any technical conversation. You walk away with a build-buy-or- configure recommendation, indicative cost, and a realistic timeline.