Payroll integrations in India: Tally and accounting journals, bank salary files and biometric attendance

Payroll software needs three integrations to save real time: an accounting journal that posts salaries, deductions and liabilities to Tally or your accounting system by cost centre; a bank file or API that pays net salaries from the approved payroll without manual edits; and an attendance feed from biometric or app-based devices locked before the payroll run. Without them, staff retype data, errors creep in and the savings you counted disappear. This guide explains what each integration should do, how to test it and illustrative costs.

It belongs to the guide on why payroll software projects fail.

Accounting integration (Tally and others)

Many Indian MSMEs keep books in TallyPrime or another accounting tool. TallyPrime supports integration through methods such as XML over HTTP, JSON and ODBC, and many payroll products offer a Tally connector or an import file. Other accounting systems usually accept a journal import or an API.

What the journal should contain

Debit	Credit
Salaries and wages expense (by cost centre or department)	Salaries payable (net pay)
Employer PF, EDLI and admin charges	PF payable
Employer ESI	ESI payable
Bonus and gratuity provisions	Provisions
	TDS payable
	Professional tax payable (by state)
	LWF payable (by state)
	Loans and advances recovered

Tests

Post a month's payroll and check the trial balance moves exactly by the payroll totals.
Check cost centre and branch splits.
Post the payment entries for PF, ESI, TDS and PT when challans are paid.
Re-post a corrected payroll and confirm the old entry is reversed, not duplicated.

If you also run an ERP, decide which system owns payroll. Two systems computing the same salary is a common error source.

Bank salary payments

Payroll software can usually produce a salary upload file in your bank's format, or connect through a bank API or a payments platform.

Method	How it works	Controls
Bank upload file	Software generates a file; finance uploads to net banking; approver releases	Lock the file; checksum or total match; maker-checker in the bank
Direct API	Software sends payments after approval	Approval rules inside the software; daily limits
Payments platform	A payments provider pays salaries from a funded account	Check the provider's terms and reconciliation reports

Tests

Generate the file for 10 test employees and upload in the bank's test or small-value mode.
Check failed payments (closed accounts) return and are flagged in payroll.
Reconcile bank debits to the payroll register.
Ensure bank detail changes need approval and are logged.

Biometric and app attendance

Attendance is the most common source of payroll errors. Options:

Option	Fits	Watch out for
Biometric or face-recognition terminals	Factories, warehouses, offices with fixed entrances	Device compatibility, offline sync, data protection for biometric data
Mobile app with geo-fencing	Field sales, multiple small sites	Battery, network, consent for location data
Web punch or self-declaration with approval	Office staff, hybrid work	Weak evidence for overtime
Manual muster imported	Very small units	Delays, disputes

Integration requirements

Device data flows automatically or daily into the attendance module.
Shift rules (night, rotational, split) compute hours and overtime.
Missed punches are regularised by employees and approved before cut-off.
Attendance for the month is locked before the payroll run, and late changes become arrears next month.

Biometric data is personal data, and may be regarded as sensitive in practice; collect only what you need, protect it and delete it on exit. See employee data under DPDP.

How integrations usually break

Symptom	Typical cause	Fix
Trial balance does not match payroll totals	Ledger mapping changed in accounts but not in payroll	Freeze the mapping; review it after any chart-of-accounts change
Duplicate salary entries	Payroll re-run posted again without reversal	Post only after final approval; reverse before re-posting
Salary credited to an old account	Bank detail changed in HR but not synced	Single source for bank details with approval
Overtime missing for night shift	Shift crossing midnight split into two days	Configure overnight shifts and test them
Attendance gaps after a power cut	Device stored punches offline and never synced	Daily sync check and device health alerts

Assign an owner for each integration and check it monthly, not only at go-live.

Other integrations worth checking

EPFO and ESIC portals: most software generates upload files; direct submission varies.
Income-tax: Form 138 file generation and validation, Form 130 generation.
HR systems: if you use a separate recruitment or performance tool, employee master sync.
Expense and travel: reimbursements flowing to payroll.
Single sign-on: for larger teams.

Illustrative integration costs

Integration	Illustrative one-time cost
Tally or accounting connector	₹0–₹30,000 (often included; custom mapping extra)
Bank file format setup	₹0–₹15,000
Biometric device integration	₹10,000–₹50,000 plus devices
Custom API work	By estimate

Add these to the one-time line of the 3-year TCO example and the payback calculator.

Frequently asked questions

Do we need an API, or is a file enough?

For most MSMEs a well-controlled file is enough. APIs help at higher volumes but need careful approval rules.

Can biometric devices from one vendor work with any payroll software?

Not always. Check compatibility before buying devices, or buy them through the software vendor's supported list.

Should payroll post every employee to accounts?

Usually summary entries by cost centre are enough; employee-level detail stays in payroll.

Are the integration costs real prices?

They are illustrative ranges, not vendor quotes.

Sources

Tally Solutions — TallyPrime integration capabilities
Reserve Bank of India — payment system rules
EPFO — ECR upload
ESIC — contribution filing
MeitY — DPDP Act and Rules