Payroll Reconciliation

It is the process of checking that four things agree with each other every month: what the payroll register says was paid and deducted, what the accounting books (General Ledger) show as booked, what was actually deposited with the government (TDS, PF, ESI, Professional Tax challans), and what was reported in the statutory returns filed. In a well-run business these four numbers match exactly. In practice, because payroll, accounting, and statutory deposit are often handled by different people or teams, small mismatches creep in — and payroll reconciliation is the control that catches them before they become a notice or an audit finding.

Not automatically. Payroll processing computes gross-to-net salary, deducts statutory amounts, and disburses pay. It does not, by itself, verify that the accounting entries booked in the GL match the payroll register, or that the amount deducted actually matches the amount deposited with the government. Many payroll software tools and even payroll vendors stop at generating reports — they do not cross-check those reports against your books or your bank-confirmed challan payments. Reconciliation is a distinct control layer that sits above payroll processing.

Monthly, as part of the regular month-end close, is the standard we recommend. TDS, PF, and ESI all have monthly deposit due dates, so a monthly reconciliation catches shortfalls before the corresponding due date rather than after. On top of the monthly cycle, we run a quarterly reconciliation tied to the Form 24Q TDS return, and an annual reconciliation tied to Form 16 issuance and statutory audit preparation.

If the amount deposited with the Income Tax Department is less than the amount actually deducted from employee salaries under Section 192, this is treated as short payment of TDS. It attracts interest under Section 201(1A) calculated from the date the deduction was due to be deposited, and the deductor can be treated as an assessee-in-default for the shortfall. A short-payment or short-deduction pattern flagged through the quarterly Form 24Q return commonly generates a TRACES intimation under Section 200A demanding payment of the shortfall plus interest.

If the Provident Fund contribution deducted from employees and the matching employer contribution do not match what is reported in the monthly ECR filed with EPFO, or what is actually deposited via challan, the shortfall can trigger an EPFO inquiry under Section 7A of the EPF & MP Act 1952. Where a shortfall is established, the employer becomes liable for damages under Section 14B calculated on the shortfall amount from the date it originally arose — not from the date it is detected — which means the longer a mismatch goes unnoticed, the larger the eventual liability.

The mechanics are similar — matching what was deducted, what was booked in the GL, what was deposited via challan, and what was reported in the ESIC monthly return — but ESI carries an additional complication: eligibility is wage-based, tied to a wage ceiling that is periodically revised by the government. An employee who crosses the applicable wage ceiling mid-year through an increment stops being ESI-eligible from the point of that change (subject to the applicable contribution period rules), and reconciliation must specifically test for this threshold-crossing scenario, which is easy to miss in a routine payroll run.

Professional Tax is levied and collected by individual state governments, not centrally, so each state has its own slab structure, due dates, and remittance authority. A business with employees in, for example, Tamil Nadu, Karnataka, and Telangana must maintain separate PT registrations, separate remittance schedules, and separate reconciliation for each state. It is common for a single state's remittance to be missed entirely when the reconciliation process was designed around a single-state business and never updated as the company expanded.

Statutory auditors specifically test employee benefit expense and the related statutory payable balances (TDS payable, PF payable, ESI payable) as part of their audit procedures under the applicable Standards on Auditing. An unreconciled payroll ledger — where the GL balance does not tie to the payroll register, the challans paid, or the returns filed — is one of the most frequent sources of audit queries, adjusting entries, and management letter points in mid-sized Indian companies. A well-reconciled payroll trail, handed to the auditor as a ready schedule, materially reduces audit query cycles.

Form 16 is the annual TDS certificate the employer issues to each employee, consisting of Part A (downloaded from TRACES, showing quarterly TDS deposited) and Part B (a detailed salary and deduction computation prepared by the employer). Form 26AS (and its successor, the Annual Information Statement or AIS) is the employee's own tax credit statement drawn from what the deductor has reported to the government. If the TDS shown in Form 16 does not match what appears in the employee's Form 26AS/AIS, the employee's own income tax return can face a mismatch notice or a delay in processing their refund.

It can surface certain red flags — a ghost employee in the payroll register with no corresponding GL cost centre allocation, a net pay figure in the bank disbursement that does not match the payroll register, or a statutory deduction shown as withheld from an employee but never actually deposited. Reconciliation is not, by itself, a forensic audit, but a disciplined monthly reconciliation process is one of the most effective early-warning controls against payroll-related irregularities, precisely because it forces every figure to be independently cross-verified rather than taken on trust from a single source.

Yes. An external payroll vendor is typically responsible for computing and processing payroll correctly, and may even confirm that statutory deposits were made — but the ultimate statutory liability for correct TDS deduction, PF/ESI contribution, and timely deposit remains with the employer, not the vendor. Independent reconciliation verifies the vendor's figures against the actual GL booking and the actual government challan, rather than relying solely on the vendor's own report.

A timing difference occurs when, for example, a TDS challan for March salary is paid on the 7th of April — which is within the statutory due date — but the GL still shows the TDS payable balance as outstanding at 31 March simply because the payment fell just after month-end. This is not an error; it is a normal timing difference that should be documented and cleared, not treated as a variance requiring investigation. A genuine variance is when the amount deposited does not match the amount deducted at all, regardless of timing — that requires root-cause investigation and correction.

FnF settlements bundle several one-time components — notice pay recovery or payment, gratuity (subject to its own exemption limit under the Income Tax Act), leave encashment (with its own exemption treatment), and any bonus or incentive due — each of which has distinct TDS treatment. We reconcile the FnF computation against the correct exemption limits, verify the TDS withheld matches the taxable portion correctly, and confirm the GL booking and eventual challan deposit reflect the FnF amount accurately, since these one-off transactions are the most error-prone component of payroll.

The correct response depends on which record was wrong. If the shortfall is in the amount deposited (a genuine underpayment of TDS, PF, or ESI), a differential payment must be made along with the applicable interest or damages, and, where relevant, a correction filing submitted (a correction statement for Form 24Q, or a supplementary ECR/challan for PF). If the shortfall is a booking error in the GL rather than an actual deposit shortfall, a correcting journal entry is passed and no differential payment is needed. Reconciliation identifies which scenario applies before any correction is made.

Yes, as part of the broader reconciliation review, though the regime election itself is validated primarily during payroll computation. Reconciliation checks that the TDS actually deducted and deposited is consistent with the regime the employee elected (or the default new tax regime applied where no election was made), and flags cases where an employee's declared investments or deductions do not appear to have been correctly reflected in the monthly TDS run, since this would show up as an inconsistency between projected and actual TDS deposited over the year.

The Income Tax Act 2025 took effect from 1 April 2026 and replaced the Income Tax Act 1961. Salary TDS deducted and deposited up to 31 March 2026 continues to be governed by Section 192 of the 1961 Act, with the familiar Section 201(1A) interest and Section 200A intimation framework applying to that period. For salary paid or credited on or after 1 April 2026, the withholding obligation is carried forward under the corresponding table item of Section 392 of the Income Tax Act 2025, and any late-deposit interest or TRACES-equivalent processing for that period is computed under the 2025 Act's renumbered provisions. The reconciliation mechanics — matching what was deducted, deposited, and returned — do not change; what changes is the section citation quoted on the return and in correspondence, depending on which period the transaction falls in.

At minimum: the monthly payroll register for the period(s) under review, the GL trial balance extract for the relevant salary and statutory payable accounts, copies of the TDS/PF/ESI/PT challans paid, and the corresponding statutory returns filed (Form 24Q, PF ECR, ESIC return). For a first-time engagement, we typically also request the prior year's reconciliation working papers if any exist, and basic employee master data (UAN, ESIC number, state of employment) to correctly attribute figures across all four records.

Yes. Retrospective reconciliation is common when a business is preparing for a statutory audit that has fallen behind, responding to an EPFO or ESIC notice covering a past period, or undergoing due diligence ahead of a funding round or acquisition. The process is the same in principle — matching payroll register, GL, challans, and returns — but takes materially longer because source records for older periods often need to be retrieved from archived systems or a previous vendor, and any identified shortfall will carry accumulated interest or damages calculated from the original due date.

Payroll reconciliation is a control-level exercise performed through the year; the statutory audit is an independent, year-end assurance exercise performed by the appointed auditor. A well-reconciled payroll trail does not replace the audit, but it substantially reduces the volume of queries the auditor raises on employee benefit expense and statutory payable balances, because the supporting reconciliation schedule is already prepared and internally consistent when audit fieldwork begins.

It becomes relevant as soon as any statutory deduction applies — even a single employee whose salary crosses the basic exemption threshold triggers TDS under Section 192, and PF or ESI can apply well before headcount reaches double digits depending on your establishment's registration status. The reconciliation effort scales with complexity, not headcount alone: a 5-employee company with a straightforward single-state payroll needs a lighter reconciliation process than a 5-employee company with staff across three states and a mix of old and new tax regime elections.

Payroll reconciliation is an ongoing control process — matching figures across the payroll register, GL, challans, and returns as a routine part of the close cycle. A payroll audit is typically a more comprehensive, point-in-time review that can include testing the underlying salary structure design, verifying statutory applicability determinations (has every eligible employee actually been covered under PF/ESI), reviewing internal controls and segregation of duties, and assessing compliance with labour law beyond just the tax and social security withholdings. Reconciliation is usually a component within a broader payroll audit, not a substitute for one.

Pricing depends on headcount, number of states of operation, payroll complexity (presence of arrears, bonuses, FnF settlements, multiple pay cycles), whether the engagement is ongoing monthly reconciliation or a one-time retrospective catch-up, and whether it is bundled with PNPC's own payroll processing or accounting services versus standalone. We provide a written scope and fee quote after an initial review of your payroll volume and current process, rather than a generic flat rate that does not reflect actual complexity.

As soon as the first statutory deduction becomes applicable — that is, the first month TDS, PF, or ESI is withheld from any employee's salary. Starting reconciliation from month one, even with a very small headcount, is significantly easier than retrofitting a reconciliation process onto years of unreconciled payroll history once the business has scaled and a notice, audit finding, or due diligence request forces the issue.

Significantly. A reconciliation review immediately before a payroll system or vendor transition establishes clean opening balances — confirmed TDS payable, PF payable, ESI payable, and each employee's year-to-date salary and deduction figures — that can be accurately carried into the new system. Without this step, a common failure mode is that year-to-date figures reset incorrectly at transition, which then distorts the full financial year's Form 16 computation and creates a Form 24Q mismatch that is difficult to trace back to its origin months later.

None of the underlying steps change — we still match your payroll register, GL, challans, and returns, regardless of who runs the payroll itself. The main practical difference is coordination: we work with your existing payroll team or vendor to obtain the source data each month, rather than generating it ourselves internally, which can add a short coordination lag to the reconciliation timeline compared to when PNPC also handles payroll processing directly.

Yes. Investor and acquirer due diligence routinely tests HR and statutory compliance, including whether payroll figures tie to the books and statutory filings. An unreconciled payroll history is typically treated by diligence teams as an unquantified contingent liability — since the eventual TDS, PF, or ESI shortfall (plus interest or damages) cannot be precisely estimated until reconciled — which can affect valuation discussions, extend the diligence timeline, or result in specific indemnity clauses being added to the transaction documents.

Under the EPF & MP Act, damages under Section 14B are levied on delayed or short remittance, calculated on the outstanding amount from the date it originally fell due, at rates that vary depending on the period of default (the applicable rate structure has been revised over time by EPFO notification, so the current schedule should be confirmed for the specific default period). ESIC similarly levies interest and can initiate damages proceedings on delayed contributions. Because both are calculated from the original due date rather than the date of discovery, the exposure grows the longer a shortfall remains unaddressed — which is the core reason early reconciliation matters financially, not just procedurally.

We typically work alongside your existing team rather than replacing it — your accounting team continues to book entries and your payroll team (in-house or vendor) continues to process salary, while PNPC performs the independent cross-check across all four records each month and reports variances for resolution. This preserves segregation of duties, which is itself good internal control practice, since the team that reconciles should ideally not be the same team solely responsible for both processing and booking.

We start by establishing whether the four core records — payroll register, GL, challans, and returns — even exist in a retrievable, complete form for the period in question. Surprisingly often, the biggest initial finding in a first engagement is not a numeric mismatch but a documentation gap: a missing challan copy, an incomplete GL extract, or a payroll register that was overwritten by a subsequent month's run without version history. We resolve the data-availability gap first, because reconciliation cannot proceed meaningfully without complete source records.

Yes, where the client engages us for the correction as well. This can include a correction statement for Form 24Q (to fix a PAN error, challan mismatch, or deduction figure), a supplementary or corrected ECR filing for PF, or coordinating a response to an EPFO/ESIC query arising from the discrepancy. We treat correction filing as a natural extension of reconciliation, since identifying the variance without also correcting the underlying filing leaves the statutory exposure unresolved.

For ongoing engagements, reconciliation is built into the monthly close calendar with a fixed cut-off — typically within 5-7 working days of month-end — so it happens as a routine step rather than an ad hoc catch-up. We track outstanding items explicitly in a rolling reconciliation log, carried forward until resolved, rather than allowing an unresolved item to simply disappear into the next month's figures.

Yes, and this is the most common and efficient arrangement for clients who also use PNPC for day-to-day accounting, AP/AR, or full payroll processing. Because the GL, the payroll register, and often the challan payments are already being handled within the same engagement, reconciliation becomes a natural monthly checkpoint rather than a separate data-gathering exercise, and variances are typically identified and resolved faster.

The most frequent pattern is a mismatch between what payroll shows as deducted and what the GL shows as the statutory payable balance — typically because a mid-year salary revision, a one-time bonus, or an employee exit was updated in the payroll system but the corresponding GL entry was never adjusted to match, or was adjusted in a later, unrelated period as a lump-sum correction that obscures the original discrepancy.

Payroll software reports what the payroll system itself computed and processed — they do not independently verify that the GL was booked correctly, that the government challan actually matches the deduction, or that the return filed reconciles with both. A software report tells you what the payroll system believes happened; reconciliation tells you whether that belief matches reality across every other independent record. PNPC brings the CA-level cross-verification, root-cause investigation, and regulatory context — interest provisions, damages calculations, correction filing procedures — that a report alone cannot provide.