A salary file can balance and still contain compliance gaps. An employee may have received the correct net pay while their PF record uses an outdated wage base, an ESIC entry is missing, or an unpaid-leave adjustment has not reached the statutory return. Month-end payroll reconciliation connects these records before the period is closed.
Payroll reconciliation is the employee-wise comparison of approved inputs, salary calculations, bank payments, statutory returns, contribution payments and accounting entries. The objective is to explain every difference, correct exceptions and retain evidence of review.
Why a successful salary transfer is only one checkpoint
Payroll involves HR, attendance owners, finance, banks and statutory portals. Each system may reflect a different version of the same month if inputs arrive late or corrections are made without a shared approval process. A new joiner can appear in the bank file but be omitted from the contribution return. An exit can be recorded by HR after payroll has already been finalised.
A monthly close gives these teams one agreed record. It also makes employee queries easier to resolve: the team can trace a payslip figure to the approved input, the deduction, the payment and the relevant statutory record.
1. Freeze and reconcile the employee master
Begin with the population, before reviewing amounts. Compare the opening employee list with joining, exit, transfer and employment-status changes during the month. Confirm which employees should receive salary and which should appear in each statutory return.
- Check employee IDs, joining dates, last working dates and work locations.
- Validate bank details and statutory identifiers through the appropriate process.
- Review PF and ESIC coverage decisions individually, including supporting declarations.
- Keep an approved list of changes received after the input cut-off.
Do not force identical headcounts across every report. Payroll and statutory coverage can legitimately differ. Record why each employee is included or excluded rather than assuming a difference is automatically an error.
2. Match attendance and variable inputs to approvals
Reconcile paid days, unpaid leave, overtime, incentives, arrears, reimbursements and recoveries with the authorised input files. Pay particular attention to retroactive changes: they should show the original period, the reason for adjustment and the approving owner.
Use exception reports for unexpected changes in payable days, duplicate incentives, unusually large overtime and recovery amounts. A payroll processor should not have to infer whether an adjustment is valid from an informal message.
3. Review gross pay, deduction bases and net pay
Compare current-month results with the previous month, then explain material differences. Separate changes caused by headcount, salary revisions, variable pay and attendance. Review unusual zero-pay, negative-pay or high-deduction cases before the bank file is released.
Check each statutory calculation against its own applicable wage definition, eligibility conditions, contribution period and current notified rules. Gross salary, statutory wages and CTC should not be treated as interchangeable figures. Where payroll configuration changes, retain a calculation note and test representative employee cases.
4. Reconcile PF payroll workings with the ECR
For each covered employee, compare the payroll PF workings with the Electronic Challan-cum-Return (ECR). Review the identifier, relevant wage fields, employee and employer contributions, pension eligibility, non-contributory-period information and applicable arrears. Resolve differences before approving the return.
EPFO's revamped ECR separates return submission from payment generation, with system validations and conditional revision facilities. An approved return should therefore be tracked through challan generation and payment confirmation as separate close activities. Use the official EPFO ECR FAQs for the filing workflow and conditions.
A useful control is to compare three records together: employee-level payroll workings, the approved ECR and the payment acknowledgement. A matching grand total alone will not identify amounts allocated to the wrong employee.
5. Reconcile ESIC and State-specific deductions
Match ESIC contribution workings to the covered employee population, wage data and contribution records. Review new entrants, exits, unpaid days and changes that may affect coverage or the contribution basis. Assess these under the applicable rules rather than switching coverage solely because one month's gross salary changes.
For Professional Tax and Labour Welfare Fund, maintain a location-wise matrix of applicability, employee categories and contribution or filing schedules. These requirements vary by State. An annual calendar helps distinguish the checks needed every month from obligations due at a different interval.
6. Match salary payments and accounting entries
Compare the approved net-pay register with the bank upload, then check the bank's final payment result. A submitted file does not prove that every employee received the money. Track rejected transfers, duplicate payments, holds and reprocessing separately.
Finance should reconcile salary expense and payable balances with the payroll register, and statutory payable balances with the related workings and payment evidence. Explain outstanding items by employee, contribution type or transaction reference, with an owner and expected closure date.
A practical month-end control sheet
| Control | Compare these records | Suggested owner |
|---|---|---|
| Employee population | HR master, joining/exits and payroll register | HR + Payroll |
| Payable inputs | Attendance and approved variable-pay files | HR + Department owners |
| Salary calculations | Approved structure, calculation rules and variance report | Payroll reviewer |
| PF reconciliation | Payroll workings, ECR and payment acknowledgement | Compliance + Finance |
| ESIC / PT / LWF | Applicable employee workings, returns and payment evidence | Compliance |
| Salary payment | Net-pay register, bank file and final payment status | Finance |
| Accounting close | Payroll journals, ledgers and open-item register | Finance controller |
Example: a balanced total can hide a missing employee
Consider an illustrative payroll with 85 salary recipients. Its PF population may be smaller for valid reasons, but one eligible new joiner is accidentally excluded. At the same time, a correction for another employee increases that employee's contribution. Comparing only the overall PF total could conceal the omission.
An employee-wise reconciliation reveals both exceptions. The team can confirm the new joiner's eligibility, review the other adjustment and use the correction process available for the return's status. The lesson is to reconcile identity, coverage and amounts together.
7. Close exceptions with evidence
Maintain a single exception log with the issue, affected employee or transaction, financial effect, owner, corrective action and closure evidence. Separate a delayed bank transfer from a coverage question or an incorrect statutory wage field; each needs a different resolution.
Retain approved payroll inputs, variance reports, review sign-offs, statutory return acknowledgements, payment references and relevant employee communications in a controlled monthly folder. Restrict access because these records contain personal and financial information.
Five checks before payroll is marked closed
- Every material payroll movement has an approved explanation.
- Covered employees and contribution workings have been reconciled employee-wise.
- Return submission, challan generation and payment status have been verified.
- Rejected salary transfers and accounting differences have named owners.
- Review evidence and unresolved exceptions are recorded for follow-up.
Frequently asked questions
What is the difference between payroll processing and reconciliation?
Processing calculates salaries and deductions. Reconciliation checks those results against approved inputs, employee coverage, bank outcomes, statutory records and accounting entries.
Is filing the PF ECR enough to close the month's PF work?
No. Review the approved return, the generated challan and confirmed payment together, and resolve employee-wise differences. Filing and payment are separate workflow checkpoints.
Should payroll and PF or ESIC headcounts always match?
Not necessarily. Coverage can differ according to the applicable requirements and employee facts. Each exclusion or difference should have a documented reason.
Who should own payroll reconciliation?
Payroll can coordinate the close, with HR validating employee inputs, compliance reviewing statutory workings and finance confirming payments and accounting. A reviewer should approve exceptions and completion.
How Wren & Pecker can help
Wren & Pecker supports payroll outsourcing, PF, ESIC and statutory compliance and labour-law compliance reviews. The scope can include input checks, monthly payroll workings, statutory reconciliation, exception tracking and organised compliance evidence.
For an initial view of your organisation's controls, take the Free Compliance Audit. A document-based review can then investigate the areas requiring attention.
Official reference: EPFO's revamped ECR launch circular. This article describes recommended process controls; check current official instructions for your filing period. General information only, not a legal opinion or a finding of compliance.
Need a clearer monthly payroll close?
Discuss your payroll, statutory reconciliation and compliance requirements with the Wren & Pecker team.
Book a Payroll & Compliance Consultation