CozyHR
Menu
Products
Docs
Resources
Compliance
Company
Support
Blog
PayrollStatutory ComplianceCompensationHRMS

Statutory Bonus Under the Payment of Bonus Act: Guide

A payroll team's guide to calculating statutory bonus correctly: eligibility, the two wage ceilings, the calculation formula, and common compliance mistakes.

CozyHR editorial team 19 September 2026 20 min read
CozyHR Blog
Statutory Bonus Under the Payment of Bonus Act: Guide

Statutory Bonus Under the Payment of Bonus Act: A Calculation Guide

Every festive season, payroll teams across India face the same question from employees, founders, and finance: "how is the bonus calculated, and why is it different from what I expected?" Statutory bonus is one of the most misunderstood parts of Indian payroll — often confused with a discretionary Diwali gift, a performance bonus, or an ex-gratia payment, when it is in fact a distinct, legally mandated payment governed by its own eligibility rules, calculation formula, and payment timeline.

This guide walks HR and payroll teams through what statutory bonus actually is, who is eligible, how to calculate it correctly, and how to avoid the most common compliance mistakes. As with all statutory guidance, the specific wage ceilings, minimum and maximum bonus percentages, and thresholds referenced by the law are subject to periodic revision — always verify the current figures against the latest government notification or your legal counsel before running your bonus calculation for the year.

Statutory Bonus vs. Everything Else Called "Bonus"

Before calculating anything, separate statutory bonus from the other payments commonly bundled under the same word:

Payment TypeWhat It IsGoverned By
Statutory bonusA legally mandated annual payment tied to the employer's "allocable surplus" and the employee's wages, within a minimum and maximum percentage bandThe Payment of Bonus Act framework
Diwali/festival bonusA discretionary, employer-chosen gift or payment, often given regardless of the statutory calculationCompany policy, not statute
Performance/incentive bonusVariable pay tied to individual, team, or company performance metricsEmployment contract / compensation policy
Ex-gratia paymentA goodwill payment made even where statutory eligibility isn't met, often to bring total payout to a round, communicated figureCompany policy
Sales commissionPayment tied directly to sales achievement, usually contractualEmployment contract / incentive plan

A frequent, costly mistake is treating a discretionary Diwali payment as if it satisfies the statutory bonus obligation, without actually running the statutory calculation. If your discretionary payment happens to equal or exceed the statutory minimum for every eligible employee, you may be fine in substance — but you still need the calculation on record to prove it, especially in group companies where wage levels vary widely across roles and locations.

The confusion is understandable: both types of payment often land in the same payroll cycle around the same festive season, both show up as a single lump sum in the employee's bank account, and few employees ever ask to see the underlying formula. But an inspector, auditor, or labour court reviewing a dispute will ask exactly that question — and "we paid a generous Diwali bonus" is not, on its own, evidence that the statutory obligation was met and documented correctly.

Who Is Eligible for Statutory Bonus

Eligibility for statutory bonus generally depends on two things:

  1. The employer's applicability — establishments employing at or above a defined minimum number of persons, once they cross a specified age from the date of first sale/manufacture (there is typically an initial exemption period for newly set-up establishments before the bonus obligation kicks in, subject to conditions), are covered.
  2. The employee's eligibility — an employee who has worked at least a minimum number of days in the accounting year is eligible, provided their wages fall at or below the applicable wage ceiling for bonus eligibility.

Two separate wage figures matter and are frequently confused:

  • The eligibility ceiling — the wage limit below which an employee qualifies for statutory bonus at all.
  • The calculation ceiling — a separate (often lower) wage figure used to actually compute the bonus amount, even for an employee whose real wages are higher than this ceiling but still under the eligibility limit.

Because both figures are subject to revision, payroll teams should maintain a single source of truth (ideally inside the HRMS) for the currently applicable ceilings, refreshed whenever a government notification changes them, rather than relying on institutional memory or an old spreadsheet formula.

The Bonus Calculation Formula, Conceptually

At a high level, statutory bonus computation for an eligible employee works like this:

  1. Determine "salary or wages" for bonus purposes for the accounting year — this generally means basic pay and dearness allowance (where applicable), not the full CTC, and specifically excludes components like HRA, overtime, and most allowances, though the exact inclusions can vary and should be confirmed for your specific payroll structure.
  2. Apply the calculation ceiling, if the employee's actual wages exceed it — the bonus is then computed as if the employee earned wages at the ceiling level, not their actual (higher) wages.
  3. Apply the applicable percentage, which falls within a statutorily defined minimum and maximum band. The employer must pay at least the statutory minimum percentage regardless of whether the company made a profit in that accounting year, and the amount payable above the minimum, up to the maximum, depends on the employer's computed "allocable surplus" for that accounting year under the Act's own formula.
  4. Pro-rate for partial-year employees — an employee who joined or worked only part of the accounting year receives a bonus computed proportionately to actual days/months worked, provided they meet the minimum working-days eligibility.
  5. Adjust for any interim payments — if the company has already paid an interim bonus, ex-gratia, or festival advance during the year, this can typically be set off against the final statutory bonus liability, but only if this intent and mechanism is clearly documented in company policy or communicated to employees at the time of payment.

Worked Example (Illustrative Figures Only)

To make the mechanics concrete, here is a fully illustrative example using round, hypothetical numbers — do not use the specific figures below as current statutory values; substitute the actual current ceiling and percentage figures applicable in your accounting year.

Suppose an employee's basic + DA for bonus purposes for the year works out to a monthly average below the applicable calculation ceiling, and the company's minimum statutory bonus percentage for the year is a defined minimum percentage of eligible wages. The payroll calculation would be: eligible monthly wage (capped at the calculation ceiling, if actual wages exceed it) × number of months worked in the accounting year × applicable bonus percentage ÷ 12 (or computed on an annual eligible-wage basis directly, depending on your payroll system's formula convention). If the employee joined mid-year, the number of eligible months is pro-rated accordingly, provided the employee met the minimum working-days threshold for the year.

Build this formula once into your payroll or HRMS bonus module with the ceiling and percentage as configurable parameters (not hard-coded), so that when the government revises either figure, your team updates a single setting rather than reworking the underlying calculation logic every year.

A Second Worked Scenario: Employee Above the Calculation Ceiling

It helps to see the calculation-ceiling mechanic applied to an employee whose actual eligible wages sit above it but still under the separate eligibility ceiling. Again, treat the figures below as illustrative placeholders only, not current statutory values.

Suppose an employee's basic + DA works out to a monthly figure comfortably above the applicable calculation ceiling, but still below the separate, higher eligibility ceiling — meaning the employee is eligible for statutory bonus at all. Because actual wages exceed the calculation ceiling, payroll does not use the employee's real basic + DA in the formula. Instead, the system substitutes the calculation ceiling figure as the "deemed" monthly wage for bonus purposes, and applies the same months-worked and percentage logic used in the first example. The result is that two employees with meaningfully different basic + DA — one just above, one well above the calculation ceiling — can end up with an identical statutory bonus amount, because both are capped at the same deemed wage figure. This is a frequent source of "why did my colleague get the same bonus as me despite earning less" questions, and it's worth pre-empting in your annual bonus communication.

Building both scenarios into your test cases whenever you configure or upgrade your payroll bonus module is a good practice — it's easy to get the below-ceiling case right and still have a bug in the above-ceiling capping logic that only surfaces once a senior employee's payslip looks wrong.

The Annual Bonus Calculation Workflow for Payroll Teams

  1. Confirm accounting year and applicability. Establish whether the company is currently covered under the Act (headcount and age-of-establishment tests) and define your accounting year for bonus purposes (often, but not always, the same as your financial year).
  2. Pull eligible-wage data for every employee who worked any part of the accounting year, including those who exited during the year — exited employees who met the minimum working-days threshold remain eligible for a pro-rated bonus and are a commonly missed category.
  3. Apply the eligibility ceiling to exclude employees whose wages exceed the current threshold (unless your company policy extends an equivalent, clearly labeled discretionary payment to them instead).
  4. Apply the calculation ceiling for remaining eligible employees whose actual wages exceed it.
  5. Determine the applicable percentage for the year — the statutory minimum by default, or a higher percentage if the company's allocable surplus calculation supports (and management approves) a higher payout, up to the statutory maximum.
  6. Compute and cross-check the bonus amount for a sample of employees manually against the system-generated figure before running the full payroll batch — this single control step catches most configuration errors before they reach every payslip.
  7. Net off any interim/ex-gratia payments already made during the year, per your documented policy.
  8. Process payment within the statutory timeline — bonus is generally required to be paid within a defined number of months after the close of the accounting year, and payroll teams should build this into the annual compliance calendar alongside other year-end filings.
  9. Issue a bonus statement or clear payslip line item so employees can see the basis of the calculation, reducing help-desk queries during bonus season.
  10. Maintain statutory registers recording the bonus paid to each employee, as required under the Act's recordkeeping provisions, ready for inspection.

Common Payroll Mistakes on Statutory Bonus

  • Calculating on gross salary instead of basic + DA. This is the single most common error and can lead to either significant overpayment or, more commonly, underpayment relative to what the correct wage base would have produced, once caught in an audit.
  • Ignoring the calculation ceiling. Paying bonus on an employee's actual (higher) wages instead of capping the base at the calculation ceiling leads to inconsistent, non-compliant, and often needlessly expensive payouts.
  • Missing pro-ration for mid-year joiners and exits. Payroll systems that only calculate bonus for employees active on a specific "bonus eligibility date" quietly exclude people who left mid-year but still met the minimum working-days threshold.
  • Not distinguishing eligibility ceiling from calculation ceiling. These are two different figures serving two different purposes — conflating them produces systematically wrong results.
  • Treating a discretionary Diwali bonus as automatically satisfying the statutory obligation without running and documenting the actual calculation.
  • No documented allocable surplus calculation when paying above the statutory minimum — if the company pays a higher percentage some years and reverts to the minimum in a leaner year, having the surplus calculation on file protects against a perception of arbitrary reduction.
  • Missing the payment deadline, which is a distinct compliance failure independent of whether the calculation itself was correct.
  • Poor documentation for exempted new establishments. Newly set-up companies sometimes assume an indefinite exemption from bonus applicability; confirm the exact duration and conditions of any such exemption rather than assuming it continues indefinitely.

Statutory Bonus in a Multi-Entity or Multi-State Group

For groups with multiple registered entities or establishments across states, a few additional considerations apply:

  • Applicability is assessed per establishment, not automatically at the group level — a newly incorporated subsidiary may have a different applicability timeline than the parent company, even under common ownership.
  • Allocable surplus is generally computed per establishment's own accounts, so a loss-making subsidiary within an otherwise profitable group cannot simply "borrow" the parent's surplus to justify a higher bonus percentage without a properly documented basis.
  • Employees transferred between group entities mid-year need careful handling to ensure continuity of eligible service is tracked correctly and the bonus isn't double-counted or dropped entirely between the two entities' payroll systems.

Communicating Bonus Calculations to Employees

Bonus season generates a disproportionate volume of payroll queries, almost always because employees don't understand why their payout differs from a colleague's or from their own expectation. Reduce this by:

  • Publishing a short, plain-language explainer (distinct from the legal policy document) each year describing the wage base, ceiling, and percentage used for that year's calculation.
  • Including a clear line-item breakdown on the payslip or a dedicated bonus statement, showing eligible wage base, percentage applied, and any interim payment adjustment.
  • Training your HR helpdesk or ESS support team on the two-ceiling structure specifically, since "why is my bonus lower than my friend's who earns less than me" is one of the most common and most explainable queries once the calculation ceiling concept is understood.
  • Avoiding the word "bonus" loosely in internal communication when you mean a discretionary payment — use "statutory bonus," "Diwali gift," and "performance bonus" as distinct, consistently used terms across all employee communication.

Building an Audit-Ready Bonus Process

Whether facing a labour department inspection or an internal audit, be ready to produce:

  • The accounting-year applicability determination and, if claiming exemption, the documented basis for it.
  • The eligible-wage calculation for a sample (or full set) of employees, showing the ceiling application clearly.
  • The allocable surplus computation, if paying above the statutory minimum.
  • Proof of timely payment (bank transfer records or payslip records) within the statutory deadline.
  • The statutory bonus register required under the Act.
  • Documentation of how any interim or ex-gratia payments were set off against the final statutory liability.

Maintaining these as a standard annual compliance pack — the same discipline most payroll teams already apply to PF, ESI, and TDS filings — turns bonus season from an annual scramble into a routine, well-documented process.

How the Labour Code Consolidation Affects Bonus Calculations

As with other statutory payroll obligations, the ongoing consolidation of India's labour laws into broader codes has implications for how "wages" is defined for bonus purposes:

  • A common wage definition across codes means the same definition that affects PF, gratuity, and other statutory calculations may also reshape what counts as "salary or wages" for bonus purposes — a change in one place can ripple into your bonus base without a dedicated announcement specific to bonus.
  • Restructuring basic pay and allowances to comply with the new wage definition (many companies had to increase the basic pay component as a percentage of CTC to meet the "50% rule" commonly discussed in this context) can mechanically increase the bonus wage base even without any change to the bonus percentage itself — model this impact before your next bonus cycle, not after employees notice a change.
  • State notification timing continues to matter, since central codes generally take effect only once individual states issue their own implementing rules — a group with operations across multiple states may need to apply different effective dates for the revised wage definition in different locations during the transition period.

Payroll and finance teams should run a scenario model each year comparing the prior year's bonus wage base to the current year's, flagging any material shift caused by wage-structure or wage-definition changes rather than assuming the calculation logic is unchanged.

Setting Bonus Above the Statutory Minimum: A Governance Process

Many established companies choose to pay bonus above the statutory floor, either up to the statutory maximum or via a separate, clearly labeled discretionary component layered on top. If your company does this, build a simple annual governance process:

  1. Finance computes allocable surplus (or profitability more broadly, if paying a discretionary top-up rather than relying strictly on the Act's surplus formula) for the accounting year.
  2. Leadership approves the applicable percentage for that year, documented in board or management meeting minutes where appropriate for larger companies.
  3. HR and payroll translate the approved percentage into the calculation parameters (ceiling application, pro-ration rules) inside the payroll system.
  4. Communication is drafted clearly distinguishing the statutory bonus percentage from any additional discretionary component, so employees understand exactly what they are receiving and why it might differ from a friend at another company or a previous year at the same company.
  5. The decision and its basis are archived for the year, so that if the percentage needs to revert to a lower level in a leaner year, HR can show a consistent, principled basis rather than an arbitrary-seeming cut.

This governance discipline matters most in the year a company needs to reduce the percentage from a previous high — having a documented, surplus-linked rationale from prior years makes that conversation far easier with both employees and, if relevant, works councils or employee representative bodies.

Sector and Structure Notes

  • Seasonal establishments (certain agro-processing or seasonal manufacturing units) often have modified bonus computation rules recognizing the shorter operating period — confirm the specific treatment rather than applying a standard full-year formula.
  • IT/ITES and services-sector companies are generally covered under the standard framework like any other establishment above the headcount threshold; sector-specific exemptions discussed informally in some states have historically been narrow and conditional — never assume an exemption applies without a specific, current confirmation for your state and establishment type.
  • Group companies with a shared services or holding entity should confirm bonus applicability separately for each registered establishment, since a shared-services entity with a small headcount might fall below the applicability threshold even though the wider group is large.
  • Startups scaling rapidly should track headcount against the applicability threshold proactively — crossing the threshold mid-year triggers a bonus obligation for that full accounting year in many interpretations, not just prospectively from the date the threshold was crossed, so waiting until year-end to check applicability can create an unbudgeted liability.

HRMS Automation Checklist for Bonus Season

  • [ ] Eligibility ceiling and calculation ceiling stored as configurable, dated parameters (not hard-coded into formulas)
  • [ ] Applicable bonus percentage for the current accounting year approved and entered before the calculation run
  • [ ] Wage base definition (basic + DA, or as currently applicable) confirmed and mapped correctly to your salary structure components
  • [ ] Mid-year joiners and leavers included in the eligible population with correct pro-ration
  • [ ] Interim/ex-gratia payments during the year flagged and set off automatically against the final statutory bonus
  • [ ] Sample manual cross-check performed against system output before the full payroll run
  • [ ] Statutory bonus register generated automatically and stored for audit
  • [ ] Payment scheduled well within the statutory deadline, with a calendar reminder set for next year's cycle
  • [ ] Employee-facing bonus statement generated with a clear, plain-language breakdown

FAQs

1. Is statutory bonus payable even if the company made a loss in the accounting year? Yes — the law requires payment of at least the statutory minimum percentage regardless of profitability, subject to the establishment meeting the applicability conditions (headcount and, for new establishments, the initial exemption period). Only the amount above the minimum, up to the statutory maximum, depends on the company's computed allocable surplus.

2. Can we pay a fixed, higher bonus to everyone instead of running the ceiling-based calculation? You can pay more than the statutory minimum as a matter of policy, but you should still perform and retain the statutory calculation to demonstrate that every eligible employee received at least what the law requires — simply paying a flat, generous amount without documenting the underlying calculation leaves a compliance gap if amounts are later questioned.

3. Do employees who resigned during the year still get a statutory bonus? Yes, provided they worked the statutorily required minimum number of days in that accounting year — this is a frequently missed category, since many payroll systems only calculate bonus for employees active at the time of the bonus run.

4. What wage components are included when calculating statutory bonus? Generally basic pay and dearness allowance where applicable — not the full CTC, and typically excluding HRA, conveyance, overtime, and most other allowances. Confirm the precise inclusions against the current definition of "salary or wages" under the applicable rules, since payroll structures vary widely and mislabeling a component can shift an employee across the eligibility ceiling incorrectly.

5. Is statutory bonus taxable in the employee's hands? Statutory bonus is generally treated as taxable salary income in the year it is received, like most other cash components of compensation. This is a general position; employees with specific tax questions should be directed to consult their own tax advisor, and payroll should ensure bonus payments are correctly reflected in the relevant TDS and Form 16 computations for the year.

6. What happens if we miss the statutory payment deadline? Late payment is treated as a distinct compliance failure, separate from getting the calculation itself right, and can attract its own penalties and employee grievances. Build the payment deadline into your annual compliance calendar with the same rigor as your PF and ESI due dates, rather than treating it as a flexible, "whenever payroll gets to it" task.

7. Are apprentices and trainees eligible for statutory bonus? Apprentices engaged under a recognized apprenticeship scheme are generally excluded from statutory bonus eligibility, while trainees who are otherwise regular employees performing employee-like functions may be eligible depending on how their engagement is structured. Document the classification of every non-standard employment category (apprentice, trainee, intern) clearly, since this classification affects bonus, PF, and several other statutory obligations simultaneously.

8. How should a newly set-up company handle statutory bonus in its first few years? Confirm whether your establishment currently falls within the initial exemption period for newly set-up establishments, and under what specific conditions that exemption continues or ends (some frameworks tie the exemption to whether the establishment has yet earned a profit). Track this date carefully — many startups miss the transition point and only realize a bonus obligation has begun after the fact, which then requires a retroactive calculation and payment.

9. How does statutory bonus interact with an employee's full and final settlement? For employees who exit before the annual bonus run but met the minimum working-days threshold during the accounting year, the pro-rated statutory bonus owed for the period they worked should generally be included in or promptly settled alongside their full and final settlement, rather than deferred to the company's standard annual bonus cycle. Build a check into your offboarding workflow that flags exited employees for a bonus eligibility review, since this is a common gap between the payroll and offboarding processes.

10. Can an employer adjust or reduce the bonus percentage from one year to the next? Yes, provided the amount paid is never below the statutory minimum and any reduction above the minimum is genuinely linked to a documented change in the company's allocable surplus or a clearly communicated policy change — not an arbitrary, undocumented cut. Employees (and, where applicable, employee representative bodies) generally respond far better to a reduction accompanied by a clear, consistent rationale than to a silent year-over-year drop with no explanation.

Benchmarking Your Bonus Approach Against the Market

Because the statutory framework only sets a floor and a ceiling, companies have real discretion in where they land within that band, and in whether they layer a separate, clearly labeled discretionary component on top. A few practical benchmarking questions worth revisiting annually:

  • Where do comparable employers in your sector and city typically land on the statutory percentage, and do they supplement it with a separate performance or festival bonus?
  • How does your total festive-season payout (statutory bonus plus any discretionary component) compare to what a candidate would realistically expect when comparing offers, particularly for roles where competitors are known to pay generously around this time of year?
  • Is your bonus communication as clear as your competitors'? A company that pays a slightly lower statutory percentage but explains the calculation clearly often generates less employee frustration than one that pays more but leaves the formula a mystery.

Treat this benchmarking exercise as part of your annual compensation review cycle, not a separate, one-off project — it naturally belongs alongside your salary increment and merit matrix planning, since both draw on the same underlying wage data and the same broader conversation about total rewards competitiveness.

Conclusion

Statutory bonus sits at an unusual intersection of payroll mechanics, employee expectation management, and compliance documentation — get any one of the three wrong and bonus season turns into a support-ticket surge instead of a moment of genuine employee goodwill. The fix is the same one that works for every recurring statutory obligation: configure the ceiling and percentage as parameters your team can update in one place each year, run the calculation consistently for every eligible employee including mid-year joiners and leavers, and keep the documentation an inspector or auditor could review without a scramble.

If your current payroll process still relies on a manual spreadsheet for bonus calculation each year, that's usually the first place errors creep in. CozyHR's payroll engine handles the ceiling logic, pro-ration, and statutory register generation automatically, so your team can focus on communicating the result well instead of re-deriving the formula from scratch every festive season.