Perimattic
hrms

TallyPrime Keka HRMS Integration - Auto Payroll & PF/ESI Sync

The TallyPrime-Keka connector syncs monthly payroll runs from Keka HRMS into TallyPrime as salary journals, splits PF and ESI liabilities into the correct statutory ledgers, and posts TDS deductions per employee per section. Attendance adjustments, reimbursements, and full-and-final settlements flow into the same monthly cycle. Rs 2,499/month.

Sync monthly Keka payroll runs into TallyPrime as salary journals — PF and ESI liabilities split into statutory ledgers, TDS posted per employee.

TallyPrime
Keka HRMS
5-minute setup30-day money backNo coding required
1-2 days → 15 min

Monthly Keka-to-Tally reconciliation collapses

4 TDS sections

192, 194J, 194C, 194D posted per employee per section

Real-time

Reimbursements from Keka expense-claim webhook

Multi-entity

Group companies on separate Keka tenants supported in parallel

Overview

What this connector does

Keka is India's fastest-growing modern HRMS. 8,000+ mid-market and enterprise Indian businesses use it for payroll, attendance, performance, and expense management. The single biggest pain for finance teams running Keka alongside TallyPrime is monthly reconciliation — payroll runs on Keka, but accounting has to happen in Tally, and Keka's built-in Tally export produces a static CSV that does not split PF/ESI/TDS into the correct statutory ledgers or handle cost-centre-wise posting.

The manual workflow — export Keka payroll to CSV, prepare salary journal entries, split PF (employer + employee share) and ESI (employer + employee share) into statutory ledgers, post TDS per section (192, 194J, 194C, 194D) for downstream Form 24Q filing, book employer contributions, allocate per cost centre for MIS, reconcile the bank credit against the Keka payroll register — consumes 1-2 full days every month. F&F settlements at exit add another day per exit employee, and reimbursements from Keka expense claims usually get tracked in a separate Excel because the CSV export cannot handle them.

This connector automates the entire cycle. Keka payroll runs are pulled via the Keka API v3 the moment they close for the month. Salary journal entries are posted into Tally per employee cost centre using the department + cost-centre mapping from Keka. PF and ESI liabilities are split into statutory ledgers (EPFO ECR-compatible, ESIC challan-compatible structures). TDS per section per employee is posted separately so Form 24Q filing has clean data. Attendance-based adjustments (LOP), reimbursements from Keka expense claims (real-time via webhook), and full-and-final settlements at exit (encashment, gratuity, full-year TDS reconciliation as one journal per exit) all flow through the same pipeline.

Multi-entity Keka groups running separate tenants per legal entity get parallel sync pipelines — each Keka tenant maps to a specific Tally company, and statutory boundaries per PAN / TAN stay clean. Multi-branch payroll with different ESI sub-codes is preserved through the sync so downstream Tally-ESIC filing runs correctly per sub-code. Bank credit for salary payments is reconciled through the existing Tally banking connector (HDFC or ICICI) against the Keka salary register — bounced payments, wrong beneficiary, and held salary surface in the reconciliation dashboard for finance to investigate.

Before vs After

What changes when you plug ERPPlugs in

See how automation transforms your TallyPrime-Keka HRMS workflow.

Without ERPPlugs

  • Keka payroll exported to CSV every month; Tally salary journal entered manually
  • PF, ESI, TDS split into statutory ledgers by hand — 1-2 days of accounting effort per month
  • Cost centre allocation per employee entered manually into the journal
  • Reimbursements from Keka expense claims tracked in a separate Excel
  • Full-and-final settlements posted as one-off journals per exit employee, often incomplete

With ERPPlugs

  • Keka payroll pulled via API on payroll close; Tally salary journal auto-posted
  • PF (employer + employee), ESI (employer + employee), TDS per section posted to statutory ledgers
  • Cost centre allocation per employee driven by Keka department + cost-centre mapping
  • Reimbursements posted in real-time from Keka expense-claim webhook
  • F&F settlements land as one settlement journal per exit with encashment, gratuity, and TDS reconciliation
Who It's For

Built for teams that need reliable automation

The TallyPrime <-> Keka HRMSconnector fits into finance, ops, and revenue teams that have outgrown copy-paste — the ones whose month-end close should not depend on a spreadsheet, whose ledger accuracy should not depend on human vigilance, and whose sales velocity should not stall behind an accountant's inbox.

Below are the roles that get the fastest return the moment this connector goes live. If yours is on the list, the payback is typically visible in the first billing cycle.

HR Head

Owns Keka payroll for a 200-500 employee group and needs monthly Tally sync without manual CSV rework.

Finance Manager

Books monthly salary journals in Tally and wants PF, ESI, and TDS split into statutory ledgers automatically per cost centre.

Group Controller

Runs a multi-entity group with separate Keka tenants per legal entity and needs statutory boundaries per PAN / TAN kept clean.

Architecture & Sync

How data flows and what gets synced

The bridge between TallyPrime and Keka HRMS, and the exact records that move across it.

Data flow
TallyPrime

TallyPrime

ERPPlugs

ERPPlugs Engine

Keka HRMS

Keka HRMS

What flows across
Monthly payroll journalPF / ESI liabilityTDS per sectionReimbursements
Sync details
Data TypeDirectionFrequency
Monthly payroll journalKeka → TallyPrimeMonthly (on payroll close)
PF / ESI liabilityKeka → TallyPrimeMonthly (on payroll close)
TDS per sectionKeka → TallyPrimeMonthly (on payroll close)
ReimbursementsKeka → TallyPrimeReal-time (webhook)
How this connector compares

Alternative TallyPrime <-> Keka HRMS integrations available to Indian businesses, and where each fits.

ConnectorTypeKeka HRMS SupportTypical Capabilities
TallyPrime <-> Keka HRMSThis pageNative ERP connector✓ NativeAuto-sync of Keka monthly payroll runs into Tally, Salary journal posting per employee cost centre, PF liability split (employer + employee) into statutory ledgers
Tally Developer / TDL customizationIn-house Tally scriptingFull (developer required)
Zapier + Tally + [target app]iPaaS bridge (no Tally-side native support)Partial
Custom REST/CSV middlewareBespoke developmentFull (weeks to build)
Manual CSV export/importSpreadsheet workflowManual only
Automation

Common automation scenarios

Real workflows this connector automates for you.

When

Keka payroll closed for the month

Then

Salary journal auto-posted into Tally with cost-centre allocation per employee, PF and ESI split, TDS per section per employee

When

Employee submits an expense claim in Keka and it gets approved

Then

Reimbursement voucher posted in real-time to Tally against the employee expense ledger

When

Employee exits and F&F is calculated in Keka

Then

F&F journal posted with encashment (leave / notice), gratuity, and full-year TDS reconciliation as one settlement voucher

When

Group entity opens a new Keka tenant

Then

Onboarding creates a fresh sync pipeline mapped to the corresponding Tally company with statutory boundaries per new PAN / TAN

Capabilities

What's included

Auto-sync of Keka monthly payroll runs into Tally
Salary journal posting per employee cost centre
PF liability split (employer + employee) into statutory ledgers
ESI liability split (employer + employee) into statutory ledgers
TDS deduction per section (192, 194J, 194C, 194D)
Attendance-based adjustments per employee
Reimbursement posting from Keka expense claims
Full-and-final settlement handling for exits
Multi-entity support for group companies on Keka
Reconciliation against monthly salary bank credit
Why It Matters

Key Benefits

1-2 Days → 15 Minutes

Monthly Keka-to-Tally reconciliation collapses.

Statutory Split Correct

PF, ESI, TDS booked to statutory ledgers automatically.

Cost Centre Accurate

Salary journals per employee cost centre.

F&F Handled

Full-and-final settlements flow through the same pipeline.

Free to Try

Try the TallyPrime <-> Keka HRMS Connector Free

Start with 1 connector and 100 transactions/month — no credit card required. See real data flowing between TallyPrime and Keka HRMS inside 5 minutes.

Compliance & Setup

Compliance-ready. Live in minutes.

What you get out of the box for statutory compliance — and the exact steps to go live.

Compliance & Compatibility

PF (EPFO ECR-compatible ledger structure)ESI (ESIC challan-compatible ledger structure)TDS per section for Form 24Q filingF&F settlement statutory calculation preserved from KekaIndia-region data residency for employee master and payroll data

TallyPrime

TallyPrime 4.x, 5.x with base install and cost-centre master enabled

Keka HRMS

Keka HRMS API v3, all Keka editions (Starter / Growth / Enterprise)

Setup in Minutes

1

Enable Keka API access

Enable the Keka API from your Keka admin console and provision credentials for the Perimattic bridge.

2

Map Keka pay heads to Tally ledgers

Map each Keka pay component (basic, HRA, special allowance, bonus) to the corresponding Tally salary ledger.

3

Configure PF/ESI/TDS ledgers

Set up the statutory ledgers in Tally and map them to Keka's statutory heads.

4

Baseline last 3 months

Run a dry-run sync of the last 3 payroll cycles to validate mappings against the historical Keka data.

Pricing

Simple, Transparent Pricing

Start free, upgrade as you grow.

Free Forever

Free

Free
  • 1 connector (read-only sync)
  • Daily sync (manual trigger)
  • Basic GST compliance (CGST, SGST, IGST)
  • HSN code auto-mapping
  • Community support
  • Standard sync-status dashboard
  • ERPPlugs branding on reports
  • Data retention (30 days)

Starter

2,499/mo
  • 1 connector (read-write sync)
  • 15-minute sync intervals
  • Full GST compliance (CGST, SGST, IGST, RCM)
  • HSN and SAC auto-classification
  • Email support (48-hour response)
  • Bank reconciliation with UTR matching
  • Multi-user access (up to 3 users)
  • Standard reporting dashboard
  • No ERPPlugs branding on reports
  • Data retention (12 months)
Most Popular

Growth

4,999/mo
  • 3 connectors (read-write sync)
  • Real-time sync (under 30 seconds)
  • Full GST compliance + e-invoice + e-way bill
  • HSN, SAC, and TDS auto-classification
  • Priority support (4-hour response)
  • Bank reconciliation across multiple accounts
  • Multi-user access (up to 10 users)
  • Custom field mapping and transformations
  • Advanced analytics dashboard
  • Webhook notifications for every event
  • Scheduled reports (daily / weekly / monthly)
  • Data retention (36 months)
Best Value

Enterprise

14,999/mo
  • Unlimited connectors
  • Real-time sync with sub-second latency
  • Dedicated account manager (1-hour SLA)
  • Full GST + e-invoice + e-way bill + IRN
  • White-label option (your brand on reports)
  • Custom field mapping and business logic
  • Advanced analytics + custom BI exports
  • Webhook notifications with retry and DLQ
  • SSO and role-based access control
  • Custom SLA with uptime guarantees
  • Onboarding workshop and dedicated CS team
  • Data retention (7 years) and audit export
  • India-region data residency (DPDP-aligned)
Answers

Frequently Asked Questions

Keka's built-in Tally export produces a CSV that has to be imported manually every month, and it does not split PF/ESI/TDS into the correct statutory ledgers or handle cost-centre-wise posting. This connector uses the Keka API directly, posts entries to the correct Tally structure, and handles the statutory splits and cost-centre allocation automatically.

Yes. When an employee exits, Keka triggers the F&F settlement calculation and passes it through the same monthly pipeline. Encashment (leave / notice), gratuity, and full-year TDS reconciliation land in Tally as one settlement journal per exit employee.

Groups running multiple Keka tenants (one per legal entity) get parallel sync pipelines. Each Keka tenant maps to a specific Tally company. Statutory boundaries per PAN / TAN stay clean.

When the Keka-generated bank file executes (whether via ICICI, HDFC, or bulk NEFT), the resulting bank credit is matched against the Keka salary register through the existing Tally banking connector. Any mismatches (bounced payments, wrong beneficiary, held salary) surface for finance to investigate.

Ready to connect TallyPrime with Keka HRMS?

Join thousands of Indian businesses automating their ERP workflows with ERPPlugs. Setup takes under 5 minutes.