Payroll Reports Every HR Team Needs: The Eleven That Do Real Work

Most payroll teams in India produce a lot of reports and still cannot answer the one question that gets asked when something goes wrong: why is this month's payout ₹4.2 lakh higher than last month's?

That is the test for payroll reports. Not how many you can export, but whether the set you keep can explain a movement, prove a remittance, and tell finance what is coming. Payroll software will generate forty reports if you let it. Eleven of them do actual work and the rest are the same numbers cut a different way.

This piece sets out the eleven, what each one has to contain to be useful, and the three reconciliations that turn a stack of reports into a defensible payroll. It is written for the person who has to close the month and then answer questions about it, not for the person choosing a reporting module.

Positions are current at August 2026 and reflect the Labour Codes as brought into force on 21 November 2025, the Central Rules notified on 8 May 2026, and the Income-tax Act, 2025 which applies to salary paid from 1 April 2026. State rules under the codes are still being notified and form numbers vary by state. Verify anything state-specific before you rely on it. Nothing here is legal or tax advice.

The short version, before the detail.

A payroll report is any output that lets you pay the right amount, remit the right amount, prove both later, or tell finance what is coming. Eleven do real work in an Indian payroll: the payroll register, the variance report, the bank transfer file and its control total, the provident fund contribution report, the ESI contribution report, the TDS report and Form 24Q working, the professional tax and labour welfare fund report, the attendance and overtime reconciliation, the cost allocation report, the leave liability report, and the arrears and off-cycle report. The register is the record everything else is checked against, and Section 50 of the Code on Wages requires it to show days worked, overtime hours, gross wages and each deduction separately. The variance report is the one that finds errors, because a wrong salary looks like a right one and only the movement gives it away.

What a Payroll Report Is Actually For

Every payroll report you need serves one of four purposes. If it serves none of them, it is a view, not a report, and you can stop maintaining it.

• Pay the right amount. Reports that let you catch an error before the bank file goes out.
• Remit the right amount. Reports that feed a challan, a return or a state filing.
• Prove both. Registers and reconciliations that let you reconstruct a payment months later, for an auditor, an inspector or an employee.
• Tell finance what is coming. Provisions and liabilities that hit the books before they hit the bank.

The reason this framing matters is that most payroll teams are strong on the first two and weak on the third. They can pay correctly and remit on time, and then cannot explain, eight months later, why one employee's March salary was ₹11,400 lower than February's. The explanation existed at the time and was never written down anywhere durable.

Section 50 of the Code on Wages puts a floor under this. Every employer has to maintain a register of persons employed, a muster roll, and a wage register showing the wage period, days worked, overtime, each deduction separately and the net paid. Whatever your software calls its outputs, those three have to exist and have to agree with each other.

The Eleven Reports That Matter

Two reports that appear on most lists are missing from that table deliberately. A headcount report belongs to HR rather than payroll, and duplicating it in the payroll system creates two numbers that eventually disagree. A gratuity provision is an actuarial valuation done annually by a valuer, not a payroll report, and treating it as one produces a figure your auditor will not accept.

The Payroll Register, and Why It Is Not the Payslip File

The payroll register is the single record everything else is checked against. One row per employee, one column per component, for one wage period.

It is not a folder of payslips. A payslip is what one employee sees; the register is what the payroll totals to. Teams that treat the payslip export as their register discover the difference the first time they need to sum a component across the company, or explain a total that includes people who left mid-month.

A register that will survive scrutiny has all of the following, per employee, for the wage period:

• Employee code, name, location, department, and the state that governs their statutory deductions.
• Date of joining, and date of leaving where relevant, because proration is the most common source of a disputed figure.
• Paid days, LOP days and overtime hours, matching the muster roll for the same period.
• Every earning component separately. Basic and dearness allowance have to be separable from the rest, because that is the base almost every statutory calculation sits on.
• Every deduction separately. Not a single "deductions" figure. Section 50 requires deductions to be shown individually, and Section 18(3) caps total deductions at fifty per cent of wages in any wage period, which you cannot demonstrate from a lumped total.
• Gross, total deductions, net pay, and the payment date.

The column people leave out is the state. In a single-state company nobody misses it. The moment you have employees in Karnataka and Maharashtra, professional tax is a per-state calculation with per-state due dates, and a register that cannot be grouped by state cannot produce the filing. Our professional tax rates by state page sets out how far apart those slabs actually are.

Keep the register for the full statutory retention period and keep it in a form you can still read. Under the Code on Wages the limitation period for a wage claim is three years from the date the claim arises, and the authority hearing it can award compensation of up to ten times the amount claimed, so a register that cannot be produced is an expensive thing to be missing.

The Variance Report Finds More Errors Than Anything Else

If you add one report to your close, add this one. It compares the current run to the previous run, employee by employee and component by component, and it catches things no rule-based validation will.

The reason it works is that payroll errors are almost never wrong in an obvious way. A wrong basic is still a plausible number. A missing LOP day produces a salary that looks entirely normal. What is not normal is the movement, and the movement is what a variance report shows.

Thresholds worth setting, and what a breach usually turns out to be:

The two "any difference at all" rows are absolute. A payroll where the bank file and the register disagree by ₹1 has an unexplained mechanism in it, and unexplained mechanisms do not stay small.

Run the variance report before you release payment, not after. A variance report produced after the bank file has gone out is a record of what you will be correcting next month.

The Statutory Remittance Set

These reports exist to feed a filing. Their content is dictated by the receiving system, which means the useful test is not whether they look right but whether they upload without error.

Three points that cost people money.

PF and ESI wages are not the same figure as each other and neither is gross salary. PF sits on basic, dearness allowance and retaining allowance, subject to the ceiling that applies to the member. ESI sits on a wider set of monthly wages and applies below the coverage threshold. A report that shows one "wages" column and drives both is wrong for at least one of them. The ESI side is worked through in detail in our guide to ESI calculation and contribution rates.

TDS is deducted against an annual estimate, not against the month. That means the monthly TDS report is only meaningful next to the estimate it came from, and a TDS report that shows the deduction without the projected annual income cannot be checked by anybody. Keep the working, per employee, for the year. The arithmetic behind it is set out in TDS on salary, old versus new regime.

Professional tax and LWF are the ones that get skipped in multi-state companies, because they are small per employee and the registrations sit with different offices. They are also the easiest for an inspector to check, since the liability is arithmetic from your own headcount.

Three Reconciliations, in Order

Reports tell you what the system thinks. Reconciliations tell you whether it is true. Run these three every month, in this sequence, because each one depends on the last being clean.

One: attendance to register. Paid days, LOP days and overtime hours in the payroll register have to match the muster roll for the same period. This is the reconciliation most often skipped and the one that most often finds money. In the migrations we run, the failure is almost never a missing register. It is a register that exists and does not reconcile with the payslip, in both directions: overtime worked and not paid, and overtime paid on shifts the muster roll cannot evidence. The first is a liability, the second is an audit finding.

Two: register to bank. The sum of net pay in the register equals the sum of the bank transfer file, and the count of payees matches. Any held salary, any payment made by a different instrument, and any returned transfer is listed separately with a reason. A returned transfer that quietly sits in the company account is one of the more awkward things to discover a year later.

Three: register to remittances and to the ledger. Employee PF deducted in the register equals employee PF in the ECR. Employee ESI equals the ESI file. TDS deducted equals the challan. Then the whole payroll posts to the general ledger as one entry set that ties to the register, with the statutory liabilities sitting in liability accounts until they are paid, rather than being netted against salary cost.

The third reconciliation is where the payroll team and the finance team usually find they have been working from different numbers all year. It is worth doing in month one of any new system rather than in month twelve.

The Liability Reports Finance Will Ask For

These do not affect this month's payment and are the first to be dropped when the close gets tight. They are also the ones the auditor asks for.

Leave liability. Encashable leave balance per employee, valued at the current applicable wage, totalled by department. Two things make this report wrong more often than not. The first is valuing at basic when your policy or the applicable law encashes on a wider base. The second is including leave types that are not encashable under your own policy, which inflates the provision and then reverses embarrassingly. The valuation itself is straightforward and our leave encashment calculator runs it.

Bonus provision. The statutory bonus chapter of the Code on Wages applies to establishments with twenty or more persons employed, or which employed twenty or more on any day during the accounting year. The provision has to be built through the year rather than discovered in the month it is paid.

Gratuity provision. An actuarial valuation, annually, by a valuer. What payroll owes the valuer is clean data: date of joining, current wages on the correct definition, and the leaver history. Most bad valuations are bad because the input file was. The individual computation, for when an employee actually exits, is in our gratuity calculator and the rules behind it in gratuity calculation in India.

Arrears and off-cycle payments. Everything paid outside the regular run, with the period it relates to. This report exists because retrospective payments do not just add money, they change the statutory position of the month they relate to. An increment backdated to April, paid in September, changes PF wages for five months and may change the TDS estimate for the year. If the arrears report only shows the amount and not the period, nobody can work out what else moved.

A Monthly, Quarterly and Annual Cadence

The quarterly TDS-to-estimate review is the one worth adding if you do not already run it. Under-deduction discovered in Q3 is spread over four months. The same shortfall discovered in March is taken out of one payslip, and that is where the queries come from.

Questions People Ask

What is the difference between a payroll register and a salary register?

In Indian practice the two terms are used for the same document, and the Code on Wages calls it a wage register. It is the record showing, for one wage period, each employee's wage period details, days worked, overtime hours, gross wages, every deduction separately, and the net amount paid. Some software splits it into an earnings register and a deductions register, which is a display choice rather than a different record.

How long do payroll records have to be kept in India?

Longer than most retention policies assume. The practical driver is the three-year limitation period for a wage claim under the Code on Wages, which runs from the date the claim arises rather than from the date of payment, and can be extended for sufficient cause. Income tax and provident fund records have their own longer horizons. Eight years is the common working standard, and the more useful question is whether the records are still readable and still reconcile, not whether they exist somewhere.

Which payroll report should I run before releasing salaries?

The variance report, compared against the previous month, with a threshold on individual net pay movement. It catches missed leavers, duplicated components and proration errors, all of which produce numbers that look perfectly plausible in isolation. Set the thresholds at 2 per cent on total gross, 15 per cent on any individual's net pay and 20 per cent on any individual's TDS, and treat two things as absolute: the headcount paid must match the HR master exactly, and the bank file total must equal the register's net pay total exactly. Anything other than 12.00 per cent for employer provident fund as a share of PF wages means a member is configured wrongly. Run it before you release payment rather than after, because a variance report produced once the bank file has gone out is a record of what you will be correcting next month.

Do I need separate payroll reports for each state?

For professional tax and labour welfare fund, yes, because both are state levies with their own rates, returns and due dates, and they are filed per registration. For PF, ESI and TDS the filing is at the establishment or TAN level rather than per state. The practical answer is that your payroll register needs a state column so any of these can be produced by grouping rather than by rebuilding.

What should a payroll variance report compare?

Current month against previous month at three levels: the company total, each component, and each employee. Employee-level comparison is the part usually left out and the part that finds errors, because a company total can be flat while two individuals are wrong in opposite directions.

Is a payslip a payroll report?

No, and treating it as one is a common structural mistake. A payslip is the employee's copy of one row, and issuing it is a separate statutory duty under Section 50 of the Code on Wages. A report is an aggregation across employees. If your only record of what was paid is a folder of payslips, you cannot produce a total, cannot group by state, and cannot run a variance. Our payslip format guide covers what the slip itself has to carry.

Who should have access to payroll reports?

Fewer people than usually do. Individual pay data should sit with payroll, the finance approver and the employee. Managers need cost by department, which is the cost allocation report, and it does not need individual salaries in it. The distinction is easy to build in at setup and difficult to retrofit after a report with everybody's salary in it has been emailed once.

Where This Leaves You

If you run three things from this article, run the variance report before release, the attendance reconciliation against the muster roll, and the control-total check between the register and the bank file. Those three catch most of what actually goes wrong, and none of them requires a reporting project.

If you are building the full set, the order that works is: get the register right first, because everything else is derived from it; then the reconciliations, because they tell you whether the register is true; then the liability reports, because finance will ask for them and the data has to have been clean all year for them to mean anything.

Most reporting problems are not reporting problems. They are the consequence of attendance living in one system, the payroll register in another, and the statutory filings being assembled by hand from both. Our payroll management system produces the register, the statutory files and the reconciliations off one record, and our attendance management software is the source the muster roll reconciliation runs against. Book a free demo and bring last month's register and last month's bank file, because the gap between those two is the fastest way to see whether you have a reporting problem or a payroll one.

Related reading: common payroll errors and how to prevent them, the payroll compliance checklist, attendance compliance after the Labour Codes, CTC breakup, component by component, and Excel payroll versus payroll software, if producing this set by hand is the actual problem.

Sources

• Code on Wages, 2019, enacted text on India Code. Section 50 on the register of persons employed, the muster roll, the wage register and wage slips; section 18(3) on the fifty per cent deduction cap; section 41(2) on the twenty-employee threshold for statutory bonus; and section 45 on the three-year limitation for a wage claim.
• Employees' Provident Fund Organisation, epfindia.gov.in. Contribution rates and the electronic challan cum return, including its filing deadline.
• ESIC contribution rates, esic.gov.in. Employee and employer shares, the wage threshold and the monthly contribution file.
• Income Tax Department, incometax.gov.in. Salary TDS deposit dates, the quarterly return and the annual certificate issued to employees.

Form numbers and filing dates under the Income-tax Act, 2025 and the Income-tax Rules, 2026 should be confirmed on the department's portal before use; the 2026 Rules renumbered extensively. State rules under the Labour Codes are still being notified and register formats vary by state. Verify the current position before configuring a payroll run.