Integrations

Integrations in NeevHR today

NeevHR connects to biometric devices, banks, statutory portals, messaging channels and your own systems. Everything listed here is in the product now. Channels that use your own account are connected per company.

A map of NeevHR integrations. Punches, website applications, API calls and CSV files come in. Bank files, statutory files and accounting files go out as files your team uploads. Messages and webhooks go out once connected.

Files stay files: NeevHR does not move money or post to a portal or an accounting product by itself.

Biometric attendance devices

Punches arrive over the ADMS (iClock) push protocol used by many eSSL, ZKTeco and Matrix devices. Devices are registered by serial number and mapped to employees. Compatibility is confirmed for your models during implementation.

  • ADMS push ingestion
  • Send employees to devices
  • Compare who is on each device
  • Device last-seen status
  • Punch file import
  • API-key punch ingest

Banks and accounting

Salary payment files for upload to your bank, and accounting files for Tally Prime and Zoho Books from published payroll. You download a file and import it: NeevHR does not move money or post directly into accounting software.

  • Bank files: generic, HDFC, ICICI, SBI, Axis, Kotak (CSV)
  • NEFT or RTGS by amount
  • Tally Prime vouchers (XML)
  • Zoho Books journals (CSV)
  • Journal voucher CSV with GL mapping
  • Cost-centre split

Statutory portals

Files in the formats the government portals accept, generated from the published payroll run, for your team to upload.

  • EPFO ECR
  • ESIC contribution file
  • Form 24Q (FVU text format)
  • Challans

Messaging channels

Notifications reach employees on the channels they use, from one dispatcher. Each channel uses your own provider account.

  • Email
  • SMS (MSG91 or Twilio)
  • WhatsApp (Meta Cloud API)
  • Browser push
  • Editable templates and a delivery log
  • Email from your own domain, with DNS records from your IT team

Approval channels

Approvers can approve or reject from Slack, Microsoft Teams or WhatsApp. Each is connected per company, using your own app or business account, with a setup guide for each. It stays off until its test passes and a Company Admin switches it on.

  • Slack: your own Slack app
  • Microsoft Teams: your own bot, with your Microsoft 365 admin
  • WhatsApp: your own WhatsApp Business account, with Meta's charges
  • Money and pay requests only open in NeevHR

API and webhooks

Connect your own systems with scoped API keys that act as service principals, and receive HMAC-signed outbound webhooks with retries. API documentation is shared with customers during implementation.

  • Scoped API keys
  • HMAC-signed webhooks
  • Retries with backoff
  • Audited API activity

Data import and export

Bring data in with validation and take it out whenever you need it, without lock-in.

  • CSV import with dry-run
  • Opening balances import
  • Export from lists and reports
  • Scheduled email reports

Need a specific integration?

Tell us what you run today and we will show what connects now. See also security.

Talk to us

Integration questions

Does NeevHR have an API?

Yes. Scoped API keys let your systems call NeevHR as a service principal, and outbound webhooks notify your systems of events. API documentation is shared with customers during implementation.

Which biometric devices are supported?

Devices that support the ADMS (iClock) push protocol, used by many eSSL, ZKTeco and Matrix models, plus punch file import for others. We confirm your models during implementation.

Does NeevHR connect to Slack, Teams or WhatsApp for approvals?

Yes, per company. You connect your own Slack app, Teams bot or WhatsApp Business account by following its setup guide, test it, and a Company Admin switches it on.

Does NeevHR integrate with Tally?

By file, yes. NeevHR makes vouchers for Tally Prime (XML) and journals for Zoho Books (CSV) from published payroll, which your accounts team imports. It is a file, not a live connection.