Payroll Journal Entries and Reconciliation Guide India

If you have ever stared at a payroll register that says one number and a trial balance that says another, you already know why payroll journal entries India teams book every month deserve more attention than they usually get. Payroll is the biggest recurring expense for most small and mid-sized businesses, and it touches six or seven statutory heads at once: provident fund, ESI, professional tax, TDS on salary, labour welfare fund, and sometimes gratuity and bonus. One wrong ledger mapping and the error repeats every month until the auditor finds it.

This guide walks through the full accounting flow, from the payroll register to the general ledger, with worked examples, tables and a month-end checklist you can adapt. It is written for payroll executives, accountants, finance heads and founders who want their books to tie out to the rupee.

A quick note before we start: all figures below are illustrative round numbers chosen to make the arithmetic easy to follow. Statutory rates, wage ceilings, due dates and thresholds change, and they differ by state. Always verify current rules with the relevant government portal or your chartered accountant before applying anything here.

Why payroll accounting trips up even careful teams

Payroll looks simple from the outside: employees work, the company pays them. Inside the books, one pay run creates a surprising number of moving parts.

• Expense is recognised in one month, but cash moves in the next.
• Some deductions are paid to the government (PF, ESI, PT, TDS), some are recovered from employees (loans, advances), and some stay inside the company (notice period recovery).
• Employer contributions are an extra cost that never appears in an employee's payslip take-home.
• Provisions such as bonus, gratuity and leave encashment build up silently across the year.
• Challans are paid against a return period, bank debits show up on a different date, and the GL posting date may be a third.

Each of these creates a timing gap. Reconciliation is simply the discipline of explaining every gap, every month, with a document behind it.

The big picture: from payroll register to general ledger

Think of payroll accounting as a pipeline with five stages. Problems almost always occur at the handoffs between stages, not inside a stage.

1. Attendance and inputs. Days worked, leave, overtime, new joiners, exits, one-time earnings and deductions are frozen for the month.
2. Payroll processing. The HRMS computes earnings, statutory deductions, employer contributions and net pay for every employee. The output is the payroll register.
3. Journal creation. The register totals are summarised into a payroll journal, grouped by ledger head and, where needed, by cost centre.
4. Posting to the GL. The journal is imported or keyed into the accounting software and approved.
5. Payment and reconciliation. Salaries are disbursed, statutory challans are paid, and balances in liability accounts are matched to the register, the bank and the challans.

A useful rule: the payroll register is the single source of truth for amounts, the GL is the source of truth for accounting, and the bank statement and challans are the external proof. Reconciliation is the process of making all three agree.

Core principle: accrual, not cash

Salary for March belongs to March, even if you pay it on 3 April. Under accrual accounting, which is what Indian companies following Ind AS or AS use, you recognise the expense in the period the service was rendered. That means the payroll journal for a month is dated the last day of that month, and the liability sits on the balance sheet until paid.

Smaller proprietors and some small firms follow a cash or hybrid method for tax purposes, but the books of a company, LLP or any entity that gets audited should be on an accrual basis. Check with your CA if you are unsure which basis applies to you.

The chart of accounts you need before posting a single entry

Good payroll accounting starts with a clean set of ledgers. Here is a practical structure for an SMB. Names will vary with your accounting software, but the logic holds.

Two design choices will save you grief later.

First, keep statutory liabilities in separate ledgers instead of one big "Payroll Liabilities" account. When PF is split from ESI and PT, reconciling each one against its challan is straightforward.

Second, decide whether employer and employee PF share one payable ledger or two. Many teams use one PF payable because the challan is a single payment, but keep a sub-ledger or report that shows the split. Whichever you choose, be consistent.

Step 1: Accruing salary expense

The first and most important journal is the accrual. It records what the company owes for the month once payroll is finalised.

Let us use one illustrative month for a company with a small team. All numbers are made up for demonstration.

Illustrative payroll summary for the month (in rupees):

Check the arithmetic: 10,00,000 minus 80,000, 3,000, 5,000, 70,000 and 20,000 equals 8,22,000. The register should always prove itself this way before you create any journal.

Journal 1: Gross salary, employee deductions and net pay

On the last day of the month:

Total debits equal total credits at 10,00,000. This single entry captures the expense, the amounts withheld on behalf of the government and the net amount owed to staff.

Journal 2: Employer contributions

Employer contributions are an additional cost to the company on top of gross salary.

Many HRMS tools post Journals 1 and 2 as a single voucher. Either approach works as long as the totals match the register.

A small but important point: some PF components, such as administration charges and EDLI contributions, are also employer costs. Confirm how your PF challan is built and make sure each component has a home in the GL. If your challan has five components and your ledger has one, you will struggle to reconcile later.

Step 2: Paying salaries through the bank

When you transfer net pay, the entry is simple.

In practice, payroll teams run into three real-world wrinkles.

• Partial failures. If two employees' transfers are rejected because of wrong account numbers, the bank debit will be lower than the register net pay. Do not adjust the journal. Leave the unpaid balance in Salary Payable, and clear it when the re-payment goes through.
• Bulk file versus actual debit. Banks sometimes debit one lump sum and apply charges separately. Book bank charges to a bank charges ledger, not to payroll.
• Payments made in cash or by cheque. Treat them the same way, but make sure the paid amount appears in the payroll payment report.

Many finance teams add a Payroll Clearing account. The bank debit goes to the clearing account first, and individual employee credits are matched against it. This is optional, but it is useful when you want a quick way to see which payments are still pending at month-end.

Step 3: Recording statutory payments

Each statutory payment clears the corresponding liability. The amounts below reuse the illustrative figures above.

PF payment

Employee share 80,000 plus employer share 80,000 gives 1,60,000 payable to EPFO, ignoring other components for simplicity.

ESI payment

Professional tax payment

TDS on salary deposit

Once you have posted the payments, every statutory payable account should be at zero or equal to the amount genuinely not yet due. A non-zero balance with no explanation is a red flag.

Statutory payment tracking table

Because due dates, return formats and portals differ, many teams keep a simple tracker. Treat the "typical timing" column as a prompt to verify, not as legal advice.

Add columns for "Due date", "Paid date", "Amount per register", "Amount per challan" and "Difference". That one sheet will carry most of your reconciliation work.

Reimbursements: keep them out of gross pay

Reimbursements such as fuel, phone bills, travel and business expenses are not salary in the usual sense. Your treatment depends on how the company has structured them, and the tax treatment can differ, so check with your tax advisor. From a bookkeeping view, the cleanest approach is:

• Book claims to the actual expense head (Travel, Communication, etc.), not to Salaries and Wages.
• Credit Salary Payable or a separate Reimbursements Payable ledger if paid with salary.
• Keep supporting bills linked to the claim.

Illustrative entry: employees submit approved claims of 40,000 in total, paid with salary.

When paid, debit Reimbursements Payable and credit Bank. If you instead pay reimbursements as part of the net salary transfer, make sure the bank file amount ties to net pay plus reimbursements, otherwise the reconciliation will always show a difference equal to the claims.

Loans and advances to employees

Salary advances and staff loans are assets, not expenses. The mistake teams make is netting them straight against salary expense, which understates both the expense and the receivable.

Illustrative example: an employee receives a salary advance of 30,000, to be recovered in three equal instalments.

At the time of the advance:

Each month, 10,000 is recovered through payroll. This was already reflected in Journal 1 as a credit to Employee Loans and Advances. After three months, the ledger for that employee should be zero.

Two controls matter here:

1. Keep an employee-wise sub-ledger so that you can see balances person by person.
2. Review the aging of advances every quarter. Balances that sit for months, or belong to employees who have left, need action. Where a loan is interest-free or below-market, there may be tax implications for the employee, so ask your tax advisor.

Provisions: bonus, gratuity and leave encashment

Provisions are where payroll accounting meets judgement. They are expenses the company has incurred but not yet paid, and they should accumulate month by month, not appear as a shock in March.

Statutory bonus provision

If your company is covered by the bonus law, you will need to accrue a monthly amount against the expected annual payout. A common approach is a fixed percentage of eligible wages, adjusted at year-end.

Illustrative monthly entry: eligible wages 6,00,000; assumed accrual of 8.33 percent, which is 50,000 (rounded).

Check the current eligibility and ceiling rules before choosing your percentage. The rate you accrue each month is an estimate. The actual payout is determined after year-end.

Gratuity provision

Gratuity is a defined-benefit obligation, and for most companies the number comes from an actuarial valuation. Smaller employers sometimes use a simple formula for monthly accrual and true up at year-end with an actuary's report. Whichever method you follow, your auditor will expect a documented basis.

Illustrative monthly entry: estimated monthly accrual of 20,000.

If you fund gratuity through a group scheme with an insurer, the premium or contribution paid reduces the liability or becomes a plan asset, depending on structure. This is where your actuary and CA should guide you.

Leave encashment provision

Where accumulated leave can be encashed, an obligation builds up. A typical approach is to compute, for each employee, the unused encashable leave multiplied by the daily salary rate, at month-end or quarter-end.

Illustrative entry: the leave liability increases by 15,000 this month.

When an employee actually encashes leave, debit the provision, not the expense, up to the amount provided.

Provision summary

Cost-centre and department allocation

Founders often want to know what each department or project really costs. That needs payroll expense split by cost centre, not just a single salary total.

Practical ways to do it:

• Tag each employee with a department, location, project or legal entity in the HRMS.
• Export the journal with a cost-centre dimension so that every debit line carries its tag.
• For shared employees, define an allocation percentage (for example, 60 percent sales, 40 percent support) and apply it at the register level, not in a spreadsheet afterwards.

Illustrative allocation of 10,00,000 gross salary:

The totals tie back to the earlier example (employer PF 80,000 plus employer ESI 10,000 equals 90,000). Always check that your cost-centre totals add up to the register total. If they do not, someone is missing a tag.

Statutory liabilities usually stay at the entity level. You allocate the expense by cost centre, but the PF payable is one number for the entity or establishment.

Full-and-final settlement entries

When an employee leaves, the full-and-final (F&F) settlement pulls together many items. The accounting should reflect each one separately so that the numbers are auditable.

Illustrative F&F for one employee:

Check: 40,000 + 18,000 + 60,000 = 1,18,000 of earnings. Less 25,000, 10,000, 6,000 and 8,000 which is 49,000, leaving 69,000.

F&F journal

Debits: 1,18,000. Credits: 10,000 + 25,000 + 6,000 + 8,000 + 69,000 = 1,18,000. Balanced.

Notes for practitioners:

• Whether notice recovery is shown as other income or as a reduction of salary expense is a policy decision. Pick one and apply it consistently.
• Gratuity eligibility, taxability and limits are governed by law. Verify current rules before computing.
• Release the F&F payment only after the clearance checklist is complete: assets returned, loans settled, approvals recorded.
• Pay F&F through the same bank approval workflow as regular salary, with the same maker-checker controls.

Reversals, corrections and arrears

Mistakes happen. What matters is how you correct them and whether the trail is visible.

Rule of thumb

Never edit a posted journal. Reverse it or post an adjusting entry that references the original voucher number. This keeps the audit trail intact.

Example 1: Overpaid salary recovered next month

An employee was overpaid 5,000 in the previous month because of an attendance error.

In the month of discovery, recover through payroll:

Here the net effect is that the recovery reduces the payout. Some teams first record the overpayment as a receivable and then clear it on recovery, which is cleaner if the recovery spans several months.

Example 2: Arrears for a salary revision

A revision effective from an earlier date results in arrears of 1,20,000 paid with this month's salary, covering the prior three months.

If the arrears relate to a previous financial year and amounts are material, discuss with your auditor whether they should be treated as a prior-period item. For most SMBs the arrears are booked in the period paid, but do not assume. Statutory contributions on arrears should be computed as per prevailing rules, so verify with your compliance advisor.

Example 3: Wrong ledger mapping found after close

If the earlier period is closed, post a reclassification entry in the current period:

Add a narration describing the original voucher, the reason and who approved it.

Month-end close checklist for payroll accounting

Use this as a working list. Most teams finish it in a few hours once the habit is set.

Before posting

• Attendance and leave inputs locked; no pending changes.
• Joiners, leavers and transfers verified against HR records.
• One-time earnings, deductions and reimbursements approved.
• Payroll register generated and arithmetic check passed (gross minus deductions equals net).
• Variance review: compare headcount, gross and net pay against the previous month and explain large movements.

Posting

• Payroll journal created from the register, grouped by ledger and cost centre.
• Debits equal credits; the journal total ties to register gross.
• Employer contributions and provisions posted.
• Journal reviewed and approved by someone other than the preparer.

Payments

• Bank disbursement file approved and released, with total tied to the register net pay.
• Failed or returned payments identified and listed.
• Statutory challans prepared with amounts per register.
• Statutory payments made and recorded before due dates.

After posting: reconciliation

• Salary Payable matches the unpaid net pay list.
• Each statutory payable matches the challan amount due or paid.
• Loans and advances sub-ledger matches the GL.
• Provision balances reviewed and rolled forward.
• Cost-centre totals match the register.
• Any open differences documented with owner and expected clearing date.

The four-way reconciliation: register, GL, bank and challans

This is the heart of payroll accounting. A good reconciliation ties four sources together.

Step-by-step reconciliation

Step 1: Register to GL (expense). Compare total gross earnings, employer contributions and other earnings in the register with the debit totals posted to expense ledgers. Any difference means a missing component or a mapping error.

Step 2: Register to GL (liabilities). For each deduction head, compare the register total with the credit posted to the corresponding payable ledger. Do this head by head: PF, ESI, PT, TDS, loan recovery, net pay.

Step 3: GL to bank (net salary). Compare the Salary Payable debits with the bank debits for salary payments. Differences should be explained by returned payments, timing, or payments that straddle month-end.

Step 4: GL to challans (statutory). Compare the movement in each statutory payable with challan amounts. Where the challan includes interest, late fees or penalties, those must be booked to an expense head, not left in the payable.

Step 5: Closing balances. After all payments, the closing balance in each payable should equal the amount due but not yet paid. Prove it with a list.

Illustrative reconciliation summary

The 5,000 difference in net pay is not an error. It is a documented timing difference, and Salary Payable should show exactly that balance at month-end.

Common reconciling items

• Rounding differences between the HRMS and the challan, usually a few rupees.
• Interest or damages on late payment included in a challan.
• Employee exits mid-month where the contribution is computed on a different wage base.
• Retrospective changes after the register was finalised.
• Bank holidays pushing a payment into the following month.
• Employees whose salary is on hold.

Common errors and how to prevent them

Almost every item on that list disappears when payroll data flows to the accounting system automatically and the mapping is set up once, carefully.

Audit trail: what auditors want to see

An auditor does not need your payroll to be perfect. They need it to be explainable. A solid audit trail has these elements.

• Traceability. Every GL entry should reference the payroll month, batch or register ID.
• Supporting documents. Payroll register, bank advice, challans, returns, provision workings, loan sanction letters and F&F sheets.
• Approval evidence. Who prepared, who reviewed, who approved, and when.
• Change history. Who changed an employee's salary, bank details or deductions, and who approved it.
• Version control. Frozen registers for each closed month, with any later changes shown as separate adjustments.
• Narrations. A line that says what the entry is, for which month, and why. "Payroll entry" is not enough. "Salary accrual for the month of the period, as per register ID" is better.

Keep these in an organised folder structure by month so that you can respond to queries quickly. Retention periods for payroll records vary by law, so confirm them with your advisor.

Controls and segregation of duties

Payroll is high-value, repetitive and sensitive, which makes it an attractive target for both error and fraud. Even a team of three can separate duties sensibly.

Practical controls for small teams

1. Maker-checker on every step. Even if one person prepares and one reviews, it makes a difference.
2. Bank detail changes need a second approval, with verification outside the system.
3. Headcount reconciliation. Match employees on payroll to the active employee list from HR every month. Look for ghost employees and unreleased leavers.
4. Variance thresholds. Any employee whose pay moves beyond a set threshold gets a note.
5. Role-based access so that people only see what they need.
6. Period locks in both HRMS and accounting software after close.
7. Exception reports. Zero net pay, negative net pay, duplicate bank accounts, duplicate PAN or UAN, and employees with no attendance but with pay.

If your team is very small and complete separation is impossible, add a periodic review by the founder or an external accountant. Independent oversight is better than none.

Integrating your HRMS with accounting software

Manual journal entry from payroll is one of the most error-prone steps in the whole cycle. Integration takes the human re-keying out and makes the mapping a one-time, reviewable decision.

What typically gets integrated

• Payroll journal (earnings, deductions, employer contributions, net pay)
• Cost-centre or department tags
• Provision entries
• Payment vouchers for salary and statutory remittances
• Employee master (sometimes) for employee-wise ledgers

Common export formats

Always do a trial import into a test company or a test period before importing into live books.

Mapping ledger heads: a sample table

This is the single most important setup task. Write it down and get finance to sign it off.

Integration best practices

• Name ledgers exactly the same in both systems, or use a mapping layer that translates names.
• Version your mapping. When you add a new pay component, add the ledger mapping the same day, before the next payroll run.
• Validate before posting. The integration should refuse to post unbalanced journals.
• Log every sync. You should be able to see what was sent, when, by whom and the result.
• Handle reruns carefully. A re-exported journal should reverse the earlier one or update it, not duplicate it.
• Reconcile after every import. A quick check that the posted debit total equals the register gross is a ten-second control that catches most mapping errors.

A good HRMS like CozyHR is built to produce a ledger-wise payroll journal from the same register that generates payslips and statutory files, so the numbers cannot drift between systems. Whichever tool you use, insist on that property: one source, many outputs.

Year-end and audit readiness

The year-end close should not be a scramble. If you have followed the monthly routine, most of the year-end work is confirmation.

Year-end checklist

1. Twelve-month tie-out. Total gross salary per the registers should equal the Salaries and Wages ledger for the year, plus or minus documented adjustments.
2. Statutory liability clearance. List each payable's closing balance with the challan or due-date support. Outstanding amounts at year-end should be genuinely due after year-end.
3. TDS reconciliation. Match TDS deducted per payroll, deposited per challans and reported in quarterly returns, then compare with Form 16 totals. Verify the current form and return requirements.
4. PF and ESI annual reconciliation. Match contributions per payroll with portal records.
5. Provisions true-up. Update bonus, gratuity and leave encashment to the final computed liability, with actuarial inputs where applicable.
6. Loans and advances review. Confirm balances, recoveries and any write-offs with approvals.
7. Employee-wise annual summary. Gross, deductions and net per employee, to be used for Form 16 and for audit sampling.
8. Cut-off testing. Make sure salary for the last month is in the right year and that any arrears or reversals relate to the correct period.
9. Related-party and director remuneration. Verify approvals and disclosure requirements with your CA.
10. Document pack. Registers, reconciliations, challans, returns, provision workings, approvals and policies, organised by month.

Questions auditors commonly ask

• How do you ensure that only active employees are paid?
• Who approves changes to salary and bank details?
• How are provisions estimated?
• How do you reconcile statutory liabilities?
• Can you show the trail for a sample employee from attendance to bank credit?

If you can answer each of these with a document or a report, you are in good shape.

A compact worked month, start to finish

To bring it together, here is the illustrative month in one table. Use it as a template for your own summary.

Total cost to the company for the month in this example: gross 10,00,000, plus employer PF 80,000, plus employer ESI 10,000, plus provisions of 70,000, which is 11,60,000. That is the number the founder should have in mind when planning headcount, not just the gross salary.

Practical tips from the payroll desk

A few habits separate smooth closes from painful ones.

• Close payroll early in the cycle. The later you freeze inputs, the more reversals you will make.
• Reconcile weekly during the statutory payment window, not only at month-end.
• Keep a running "open items" list for payroll differences, with an owner for each.
• Document policy decisions such as how notice recovery is booked or how arrears are treated. Policies in people's heads do not survive attrition.
• Test changes in a sandbox. Before changing a pay component or ledger mapping, run a dummy payroll and compare the journal.
• Review the previous month's journal against the current one as a standing agenda item. Unexplained changes in a ledger line are your best early warning.
• Train a backup. Payroll knowledge should not sit with one person.

Frequently asked questions

1. On which date should the payroll journal be booked?

Book it on the last day of the payroll month, because the expense belongs to the month in which the service was rendered. Payment, even if it happens in the next month, clears the liability and does not change the expense period. Confirm with your auditor if your entity follows a different accounting basis.

2. Should employer PF and ESI be shown separately from salary expense?

It is good practice to book employer contributions to separate expense ledgers, because they are a distinct cost with distinct reporting. This also makes it easy to reconcile the expense to the challan components and to analyse total cost to company.

3. How do we handle a salary payment that fails for one employee?

Leave the amount in Salary Payable. Do not reverse the original journal. When the corrected payment goes through, debit Salary Payable and credit the bank. Keep a list of unpaid items with reasons so the closing balance is explainable.

4. Do we need a separate ledger for each statutory payable?

Yes, it is strongly recommended. Separate ledgers for PF, ESI, professional tax, TDS and labour welfare fund make reconciliation to individual challans simple and help you spot overdue items quickly.

5. How should we account for interest or penalty paid on a late statutory payment?

Book it to a dedicated expense ledger, such as Interest and Penalty on Statutory Dues, instead of leaving it in the payable. Whether the amount is allowable for tax purposes is a question for your tax advisor.

6. Can we post payroll to the accounting system once a year for simplicity?

That is not advisable. Monthly posting gives you accurate monthly profit and loss, timely statutory tracking and easier reconciliation. Annual posting hides errors until they are expensive to fix and may not satisfy audit or compliance expectations.

7. What is the minimum documentation we should keep for each payroll month?

At minimum: the approved payroll register, the posted journal with its reference, the bank payment advice, statutory challans and return acknowledgements, the reconciliation sheet, and approvals. Check applicable retention requirements with your advisor.

8. How do we know our HRMS to accounting mapping is correct?

Run a test import and compare. The debit total should equal register gross plus employer contributions, the credit totals should match each deduction head, and net pay should match Salary Payable. If every line ties out for two or three consecutive months, your mapping is sound. Re-test whenever you add a pay component.

Conclusion

Getting payroll journal entries India teams can rely on is not about clever accounting. It is about a repeatable routine: accrue on the last day of the month, keep statutory liabilities in separate ledgers, provide for bonus, gratuity and leave encashment as they build up, reconcile four ways every month, and keep a trail that anyone can follow. Most payroll errors come from broken handoffs between systems, so the fewer manual steps between the register and the ledger, the cleaner your books.

If you are tired of rebuilding journals in spreadsheets or chasing differences between your payroll register and your trial balance, it may be time to look at your tooling. CozyHR is HRMS and payroll software built for Indian SMBs, with payroll registers, statutory reports and accounting-ready journal exports in one place. You can try CozyHR on your next payroll cycle and see how much of this checklist runs on its own.

One last reminder: the examples in this article are illustrative, and statutory rates, limits, due dates and forms change over time. Please verify current rules with official sources or your chartered accountant before you finalise your own accounting policy.