Payroll Accounting and Employee Administration

Introduction

Payroll is both an accounting process and an information-governance process. It converts employment terms, attendance records, pay-head rules and statutory requirements into authorised payments and accounting entries. In Tally.ERP 9, payroll is integrated with ledgers, cost centres, attendance records and reporting tools. Correct configuration is therefore more important than merely entering salary amounts.

Payroll errors can affect employee welfare, tax compliance, financial statements, labour-law compliance and organisational trust. A professional accountant must understand not only the menu path in Tally.ERP 9, but also the logic behind master creation, calculation, authorisation, posting, reconciliation and confidentiality.

This chapter uses generic statutory examples. Exact tax rates, contribution ceilings, exemption rules and filing formats depend on the applicable jurisdiction, assessment year and Tally release. They must be verified against current legislation and official product documentation before processing live payroll.

Learning Objectives

After studying this chapter, the learner should be able to:

1. Explain the architecture of payroll accounting in Tally.ERP 9.
2. Create and maintain employee, employee-group, attendance, pay-head and salary masters.
3. Distinguish earnings, deductions, reimbursements and employer contributions.
4. Process attendance, payroll vouchers, statutory deductions and reimbursements.
5. Prepare payslips, payroll statements, payment advice and management reports.
6. Apply controls for authorisation, confidentiality, auditability and data protection.
7. Analyse payroll exceptions and reconcile payroll with the general ledger.

1. Payroll as an Integrated Accounting System

A payroll system has five connected layers:

The basic accounting relationship is:

Here, gross earnings include salary components earned during the period; reimbursements are approved repayments of business expenses and may be treated differently for tax purposes; and employee deductions are amounts withheld from the employee. This equation applies after all attendance, leave, eligibility and statutory rules have been validated. Employer contributions are normally an additional employer cost and are not subtracted from employee net pay.

A broader employer-cost relationship is:

These relationships are accounting classifications, not substitutes for legal definitions of taxable income or wages.

2. Payroll Configuration in Tally.ERP 9

Payroll features are generally enabled from F11: Features, where the organisation activates payroll and, where required, attendance or related options. The precise screen labels vary by release and localisation. Configuration should be performed in a controlled company data environment, with a documented chart of accounts and a tested payroll period.

Before enabling payroll, management should decide:

• the payroll frequency, such as monthly or weekly;
• the financial year and salary period;
• employee numbering and department structure;
• attendance units, such as days, hours or pieces;
• the basis of salary calculation;
• required statutory schemes;
• approval responsibilities;
• accounting treatment for advances, loans, reimbursements and employer contributions; and
• retention, access and backup policies.

A payroll calendar should identify cut-off dates, attendance approval, payroll computation, review, payment and statutory remittance dates.

3. Employee and Employee-Group Masters

3.1 Employee master

An employee master normally records an employee’s name, code, joining date, designation, department, location, bank details, salary basis and statutory identification information. Sensitive fields should be collected only when necessary and should be protected from unauthorised access.

A good employee code is stable, unique and independent of personal characteristics. Reusing a code after an employee leaves can corrupt historical reports and statutory records. Changes in bank account, department or salary should be documented with an effective date rather than silently overwriting historical information.

3.2 Employee groups

Employee groups support common treatment for departments, grades, locations or employment categories. For example, “Production—Grade A” may share attendance and salary rules, while individual salary details remain employee-specific.

Groups improve maintainability, but they should not be used to conceal exceptions. An employee whose compensation differs from the group should have a documented individual salary structure and an approval trail.

3.3 Employee data governance

The payroll administrator should apply the following controls:

1. Completeness: required identity, employment and payment fields are present.
2. Uniqueness: no duplicate employee code or bank account is created without investigation.
3. Validity: joining date, leaving date and salary effective date are logically consistent.
4. Authorisation: master changes are approved by designated personnel.
5. Confidentiality: access is limited according to role.
6. Traceability: changes can be linked to a user, date and supporting document.

4. Attendance and Production Masters

Attendance types define the units recorded by the system. Common examples include Present, Absent, Paid Leave, Unpaid Leave, Overtime Hours and Work-from-Home Days. Production types are useful where pay is linked to output, such as units produced or tasks completed.

Attendance rules must distinguish between:

• calendar days and payable days;
• paid and unpaid absence;
• approved and unapproved overtime;
• holiday and weekly-off treatment; and
• attendance data and payroll approval.

If a monthly salary is based on payable days, a simplified pro-rata calculation is:

“Salary-basis days” may be calendar days, scheduled working days or another legally approved basis. The organisation must select one basis consistently and document how joining, separation, leave and holidays are handled. The formula must not be applied where a specific statute, contract or company policy prescribes another method.

Attendance vouchers should be entered or imported from an approved source and reviewed before payroll is computed. A common control is to compare attendance totals with the employee’s working calendar and investigate negative, excessive or missing values.

5. Pay Heads and Salary Structures

A pay head defines the identity, calculation method, accounting classification and reporting treatment of a payroll component. It should not be created merely because a label appears on a payslip. The accountant must first determine the economic nature of the item.

5.1 Main classes of pay heads

In Tally.ERP 9, pay heads can be configured as income, deduction, reimbursement or contribution types. Their calculation may be fixed, attendance-based, production-based, percentage-based or dependent on another pay head.

5.2 Percentage-based calculations

A percentage pay head is calculated as:

where Base is the specified salary component or aggregate, and Rate is the percentage. The base must be explicitly defined. For example, a contribution calculated on basic pay is not automatically calculated on gross pay.

If basic pay is ₹30,000 and an allowance is 20% of basic pay:

If an employee contribution is 12% of basic pay, the contribution is ₹3,600, subject to the applicable statutory base, rounding rule and ceiling. The arithmetic is simple; the legal classification is not.

5.3 Salary details and effective dates

Salary details assign pay heads to an employee or group and specify the rate, formula and effective date. A revision should normally create a new effective-dated line. Backdated revisions require special review because they may alter previous payroll periods, tax withholding and statutory returns.

A salary structure should be tested with:

• a full-attendance employee;
• an employee with unpaid leave;
• a new joiner;
• an employee leaving mid-period;
• an employee receiving overtime;
• an employee with a loan or advance; and
• an employee subject to statutory deductions.

6. Payroll Processing Cycle

The payroll cycle is a controlled sequence rather than a single voucher-entry event.

Step 1: Freeze and validate masters

Confirm employee status, salary revisions, bank details, statutory identifiers and approved changes. Lock or document the cut-off date so that late amendments are separately authorised.

Step 2: Record attendance and production

Enter attendance or import it from an approved system. Review exceptions, leave approvals, overtime authorisations and missing records.

Step 3: Compute payroll

Use the configured salary structure and attendance information. Review gross earnings, deductions, employer contributions and net pay by employee and department.

Step 4: Record adjustments

Enter approved bonuses, incentives, reimbursements, salary advances, loan recoveries, arrears and reversals. Each adjustment should have documentary support.

Step 5: Review and authorise

A reviewer should compare current payroll with the previous period and investigate unusual movements. Useful exception tests include new employees, terminated employees, zero net pay, unusually high overtime, duplicate bank accounts and large changes in deductions.

Step 6: Post payroll accounting

Payroll posting transfers the computed amounts to expense, liability and receivable ledgers. The posting should be checked against the payroll register and trial balance.

Step 7: Pay employees and remit liabilities

Prepare payment advice or bank transfer data after approval. Statutory liabilities should be remitted by the due date, with payment evidence retained.

Step 8: Close and archive

Generate payslips and reports, reconcile balances, preserve supporting documents and restrict retrospective alteration of the processed period.

7. Worked Application: Monthly Payroll

The following is an illustrative case, not a statement of any jurisdiction’s statutory rates.

An employee has the following monthly salary structure:

Gross earnings are:

Total deductions are:

Net pay, including the approved reimbursement, is:

The employer’s cost, assuming the reimbursement is an employer expense and the employer contribution is additional, is:

The example assumes full attendance, no statutory ceiling, no rounding difference and a reimbursement that is paid through payroll. Taxability and accounting classification must be determined under the applicable law and policy.

A simplified posting may include:

• Debit salary and allowance expense ₹38,000;
• Debit approved travel expense ₹1,500;
• Debit employer contribution expense ₹3,600;
• Credit employee contribution payable ₹3,600;
• Credit tax payable ₹2,400;
• Credit loan receivable or loan-recovery ledger ₹1,000;
• Credit bank or payroll payable ₹32,500; and
• Credit employer contribution payable ₹3,600.

The exact journal structure depends on whether payroll is posted directly to bank, first to a payroll payable ledger, or through a payment voucher. The total debits and credits must agree.

8. Statutory Contributions, Tax and Reimbursements

Statutory payroll processing requires classification, calculation, deduction, remittance and reporting. The accountant should maintain a statutory matrix containing the scheme, applicable employees, calculation base, employee rate, employer rate, ceiling, due date, return and responsible officer.

A statutory deduction should not be treated as an expense of the employer merely because it appears in payroll. Employee deductions are generally amounts withheld and payable to a third party. Employer contributions are generally employer costs and statutory liabilities. Tax treatment, however, depends on the relevant law.

Reimbursements require special care. A reimbursement supported by an approved business expense claim may differ from a taxable allowance. Payroll configuration should therefore distinguish:

• fixed allowances;
• expense reimbursements;
• advances and their settlement;
• non-cash benefits; and
• recoveries from employees.

An advance is not automatically an expense. It is normally recorded as an employee receivable until supported expenses are approved or the amount is recovered. Duplicate reimbursement is prevented by matching the claim, receipt, approval and payment reference.

9. Payslips and Payroll Reports

A payslip should communicate the pay period, employee identity, attendance or payable days, earnings, deductions, reimbursements, employer contributions where disclosure is required, net pay and relevant statutory information. It should be issued securely rather than distributed through an uncontrolled public channel.

Important Tally payroll reports include, depending on configuration and release:

• employee pay sheet;
• payroll register;
• attendance register;
• pay-head summary;
• department or cost-centre analysis;
• statutory deduction statements;
• employee-wise ledger or pay details;
• salary payable and payment reports; and
• payslips.

Management may use payroll reports to analyse headcount, overtime, department cost, absenteeism, salary movement and statutory exposure. Reports must be reconciled to the general ledger. A payroll register that does not agree with salary expense or payroll liabilities indicates an error in configuration, posting, adjustment or period selection.

10. Internal Control and Confidentiality

Payroll is a high-risk area because one person may otherwise create an employee, alter salary, process payroll and authorise payment. Segregation of duties should separate:

1. employee master maintenance;
2. attendance approval;
3. payroll computation;
4. payroll review;
5. payment authorisation; and
6. statutory remittance and reconciliation.

Tally.ERP 9 security controls should be configured using appropriate users, passwords, security levels and restricted access to payroll reports. Controls should also include regular backups, access reviews, audit trails where available, data restoration tests and secure transmission of payslips.

Confidentiality is not limited to hiding net pay. Salary structures, bank details, tax identifiers, medical information and disciplinary deductions may all be sensitive. The principle of least privilege means that a user receives only the access needed for assigned work.

A payroll change log should record the old value, new value, effective date, reason, supporting document, preparer and approver. Where the software edition or configuration does not provide a complete audit trail, compensating controls such as approved change forms, period locking and independent review are necessary.

11. Reconciliation and Analytical Review

Payroll reconciliation links operational records to accounting records and cash payments. At minimum, the accountant should reconcile:

• employee-level net pay to the bank payment file;
• payroll liabilities to statutory remittances;
• salary expense to the general ledger;
• employee advances and loan recoveries to subsidiary records;
• opening and closing payable balances; and
• current-period headcount to the approved employee list.

Useful analytical indicators include average payroll cost per employee, overtime as a percentage of gross earnings, variance in headcount, unexplained changes in net pay and ageing of statutory liabilities. These indicators do not prove fraud or error; they identify items for investigation.

A payroll variance may be expressed as:

A percentage variance, when the prior-period amount is not zero, is:

The absolute-value sign ensures that the denominator is positive. Percentage variance should be interpreted cautiously when the prior-period amount is very small or changes sign.

12. Illustrative Case: Meridian Components

Background. Meridian Components employs 86 people across production, sales and administration. It previously maintained attendance in spreadsheets and entered one consolidated salary journal monthly. Employees received inconsistent payslips, and statutory liabilities were reconciled only at year-end.

Problem. A salary revision for six production employees was applied one month late. Overtime was approved by supervisors but not independently reviewed. Two employees shared a bank account because an old employee code had been reused. Management could not determine payroll cost by department.

Analysis. The root causes were weak master governance, absence of effective dates, inadequate segregation of duties and lack of reconciliation between attendance, payroll and bank data. The problem was not solved merely by changing the salary journal.

Approach. Meridian enabled payroll and attendance features in a test company, created employee groups by department and grade, assigned unique employee codes, defined pay heads, and entered salary details with effective dates. Attendance approval was assigned to supervisors, while payroll review was assigned to finance. The company created separate ledgers for salary expense, employee deductions, statutory liabilities, loans and reimbursements. Before payment, finance compared the payroll register with bank details and performed a prior-period variance review.

Outcome. The revised process identified the six arrears correctly, prevented duplicate bank details from passing unnoticed, produced department-wise payroll reports and allowed statutory balances to be reconciled monthly. The company also introduced restricted payslip distribution and quarterly access reviews.

Learning points. Integrated payroll improves control only when master data, authorisation and reconciliation are integrated as well. Automation accelerates both correct processing and incorrect processing; therefore, configuration testing and review remain essential.

13. Limitations, Risks and Contemporary Developments

Tally.ERP 9 is a business accounting platform, not a substitute for legal interpretation or human review. Risks include incorrect pay-head bases, outdated statutory rates, duplicate employee records, unauthorised changes, incomplete attendance, rounding differences, insecure exports and inaccurate migration from spreadsheets.

Contemporary payroll environments increasingly use biometric or cloud attendance systems, bank interfaces, employee self-service, electronic statutory filing and analytics. Integration can reduce manual entry but creates additional risks: interface failures, excessive data collection, vendor dependence, cyberattack and unclear responsibility for corrections.

Artificial intelligence may assist with anomaly detection, such as identifying unusual overtime or duplicate bank accounts. It should not autonomously alter salary masters or make employment decisions without human approval, explainability, access controls and a documented review process. Personal data should not be sent to an external AI service unless lawful, necessary, contractually protected and approved under organisational policy.

Best practice is to maintain a test environment, document configuration, use controlled change management, reconcile every payroll period, preserve evidence and review statutory requirements regularly.

Chapter Summary

Payroll accounting in Tally.ERP 9 combines employee administration, attendance, compensation design, accounting and statutory reporting. Employee and employee-group masters provide the organisational structure; attendance and production types provide the basis for payable time; and pay heads define earnings, deductions, reimbursements and employer contributions. Salary details must be effective-dated and tested against ordinary and exceptional cases.

A sound payroll cycle validates masters, records approved attendance, computes payroll, processes adjustments, performs independent review, posts accounting entries, pays employees, remits liabilities and archives evidence. The key accounting distinction is between employee deductions, employer costs, reimbursements and employee receivables. Reconciliation, segregation of duties, least-privilege access, secure payslips and documented change control protect both the organisation and its employees. Technology improves speed and reporting, but it does not remove the need for legal verification, professional judgement and ethical governance.

Key Terms

Attendance type: A category used to record payable or non-payable time.

Employee master: The record containing an employee’s identity, employment and payment information.

Employee group: A classification used to apply common payroll or organisational properties.

Employer contribution: A contribution funded by the employer in addition to employee pay.

Earnings: Amounts earned by an employee, such as salary, allowance or bonus.

Effective date: The date from which a master or salary rule applies.

Gross earnings: Total earnings before employee deductions.

Net pay: Amount transferred or payable to the employee after permitted additions and deductions.

Pay head: A configured payroll component with a calculation and accounting treatment.

Payroll register: A period-wise summary of employee earnings, deductions and net pay.

Production type: A unit used where compensation depends on output.

Reimbursement: Repayment of an approved expense incurred for the organisation.

Salary structure: The set of pay heads and rates applicable to an employee.

Statutory deduction: An amount withheld under a legal requirement.

Statutory liability: An amount payable to a government or authorised statutory body.

Segregation of duties: Separation of incompatible responsibilities among different persons.

Payroll payable: A liability representing amounts due to employees or other parties.

Variance analysis: Comparison of current results with a prior, budgeted or expected amount.

Review Questions

Short Answer Questions

1. What is the function of a pay head in Tally.ERP 9?
2. Distinguish gross earnings from net pay.
3. Why are effective dates important in salary details?
4. State two controls over employee masters.
5. What is the purpose of payroll reconciliation?

Long Answer Questions

1. Explain the complete payroll processing cycle from master validation to period closure.
2. Discuss the classification and accounting treatment of earnings, deductions, reimbursements and employer contributions.
3. Explain how attendance and production types influence payroll computation.
4. Analyse the role of segregation of duties and confidentiality in payroll administration.
5. Describe the reports required for operational, accounting and statutory payroll review.

Analytical / Application Questions

1. An employee has gross earnings of ₹52,000, deductions of ₹8,500 and an approved reimbursement of ₹2,000. Calculate net pay and explain which items should be reviewed before payment.
2. A company’s payroll expense agrees with the general ledger, but statutory liabilities do not agree with remittance records. Identify possible causes and design a reconciliation procedure.
3. A salary revision is entered without an effective date and changes the prior month’s payroll. Evaluate the control failure and recommend a correction and prevention plan.

Multiple Choice Questions with Answers

Question 1

Which Tally object primarily defines the calculation and accounting treatment of a payroll component?

A. Employee group

B. Pay head

C. Attendance voucher

D. Cost centre

Correct Answer: B. Pay head

Question 2

Which item is normally added to earnings rather than deducted from employee pay?

A. Tax withheld

B. Loan recovery

C. Approved reimbursement

D. Employee statutory contribution

Correct Answer: C. Approved reimbursement

Question 3

If basic salary is ₹30,000 and an allowance is 20% of basic salary, what is the allowance?

A. ₹3,000

B. ₹6,000

C. ₹20,000

D. ₹36,000

Correct Answer: B. ₹6,000

Question 4

What is the main purpose of an effective date in salary details?

A. To identify the employee’s bank

B. To determine when a salary rule applies

C. To replace attendance records

D. To calculate department headcount

Correct Answer: B. To determine when a salary rule applies

Question 5

Which control best reduces the risk that one person can create an employee and authorise payment?

A. Using one shared password

B. Removing all payroll reports

C. Segregation of duties

D. Reusing employee codes

Correct Answer: C. Segregation of duties

Question 6

Which formula represents net pay in the chapter’s general model?

A. Gross earnings − employer contributions

B. Gross earnings + reimbursements − employee deductions

C. Gross earnings + employee deductions − reimbursements

D. Employer cost − gross earnings

Correct Answer: B. Gross earnings + reimbursements − employee deductions

Question 7

An employer contribution of 12% on basic pay of ₹30,000 equals:

A. ₹2,500

B. ₹3,000

C. ₹3,600

D. ₹4,200

Correct Answer: C. ₹3,600

Question 8

Which report is most directly useful for comparing payroll cost by department?

A. Department or cost-centre analysis

B. Bank reconciliation only

C. Employee leave application

D. Stock summary

Correct Answer: A. Department or cost-centre analysis

Question 9

Why should an employee loan recovery usually be linked to a receivable ledger?

A. It is always an employer expense

B. It represents recovery of an amount due from the employee

C. It is never recorded in accounting

D. It replaces the salary expense ledger

Correct Answer: B. It represents recovery of an amount due from the employee

Question 10

What is the most appropriate first response to an unusually large payroll variance?

A. Automatically delete the payroll period

B. Ignore it if net pay is positive

C. Investigate the underlying employee, attendance and master changes

D. Change all pay-head rates

Correct Answer: C. Investigate the underlying employee, attendance and master changes