Earnings and deduction components in a payroll template

A payroll template is the catalogue of earning and deduction lines a monthly run will use. It is not a second software product page. Name the list once so every employee on that structure is calculated the same way: recurring earnings, variable earnings, statutory lines as configured, and recoveries. If a line is missing, it will not appear unless you add an exception. If a line exists but nobody owns its input, it still appears — often as a zero, a stale amount, or a surprise.

Keep two documents distinct. The salary structure explains how CTC is broken into basic, HRA, and other allowances; that design belongs on salary structure: basic, HRA, and allowances. The template is the operational list those names become. Dayzen payroll includes templates, adjustments, dashboards, and reports as verified calculation capabilities. It calculates; it does not file government returns or disburse salary through a bank file. Run order stays on the payroll-run checklist. This page owns the anatomy of the lines.

What a template is for

A template answers four questions for every line: what it is called, whether it repeats, how its amount is sourced, and whether other lines depend on it. Call the line the same thing employees will see. If finance calls it “special allowance” and HR calls it “other,” the payslip becomes an argument. Recurring lines should have a default monthly amount or a formula from CTC. Variable lines should have an empty default and a named owner who posts the figure before freeze. Statutory lines should exist only where you have decided they apply, with the current method taken from official materials for that period — not from a remembered percentage in a chat. Recoveries should point at a balance, not at a round number someone typed from memory.

Do not invent a nationwide set of required component names. A short list that matches the contract is better than a long template nobody maintains. Map each template to a role family, location, or employment type. A plant and a registered office often need different statutory lines even when CTC looks similar. Two templates with the same earning names and different deduction sets is clearer than one template with optional lines that fire for the wrong people. On transfer, the template follows the assignment payroll should read — not last year’s spreadsheet tab.

Recurring earnings

Recurring earnings are lines that exist every month while the person is on that structure, unless you change the structure. Typical names in Indian private offices include basic, house rent allowance, and a residual special or other allowance. Conveyance, telephone, and similar heads are recurring only if you pay them every month as part of the structure. If they are reimbursed against bills, they are not this category — they are a claims process, and stuffing them into payroll as a fixed line will misstate both tax and net pay.

Write, for each recurring line:

• The display name on the payslip.
• Whether the amount is a fixed rupee figure, a percentage of another line, or a remainder after other heads.
• Whether it is payable in a partial month (joiners and leavers) using the same day-count method as the rest of salary, or held as a full month only — that choice must be written, not implied.
• Whether it is included in the bases other lines use (for example, a statutory calculation that takes a named wage, or a recovery that should not reduce a particular head). Do not treat a popular blog split as law.

Keep examples generic. “Basic plus HRA plus a residual allowance” is enough. Do not paste a sample CTC with invented statutory percentages. Unpaid-day rupees after the day count is known belong with LOP amount methods, not here.

Variable earnings

Variable earnings are lines that may be zero in a given month. Common Indian office examples: a one-time bonus, an incentive, overtime if you pay it in payroll, a joining or retention amount you chose to run through salary, or a reimbursement you have decided to pay as a payroll line rather than as expense. Variable does not mean informal. It means the amount is an input for that period, not a standing figure on the structure.

Name the owner of each variable line. Incentives often sit with sales operations, overtime with the site manager, bonuses with HR or finance after approval. If nobody owns the input, payroll will either skip people or invent a number under time pressure. Publish the cutoff: the date the variable file must be in, in the same calendar as attendance and leave freeze. Late incentive lists are a next-cycle item or a written exception, not a reason to keep the whole company in draft.

Do not use a variable earning as a hidden salary increase. Raise the recurring structure if the monthly amount should change; post a dated variable line if the money is once. Mixing the two makes year-to-date reports and tax estimates lie. If you pay overtime or extra-work cash through payroll, give it a named line, an owner, and a cutoff. This page does not decide whether an establishment must pay cash, rest, or something else. Comp-off as rest is a leave topic, not a template line.

Statutory lines as configured

Statutory lines are deductions or contributions you calculate because a rule you have reviewed applies to that employee in that period. In Indian payroll conversations the usual cluster is provident fund, ESI, professional tax, and tax deducted at source, plus employer-side counterparts where you calculate them. This article does not publish rates, slabs, wage ceilings, due dates, or form numbers. Those change. Verify them on the official portal or gazette that actually governs the period you are running, and put the current method into configuration after that check — not from a neighbour’s template.

Treat each statutory line as configured, not as folklore:

• Who is in scope (by location, wage, or employment type as your reviewed rule requires).
• Which earning heads form the base you will use. That mapping is a design decision until a binding instrument you have read says otherwise. Do not copy a 50 percent basic split as if it were a gazette fact.
• Whether the employee line and the employer line both appear in the run, even if only the employee line prints on the payslip.
• What happens in a partial month or a month with unpaid days: recalculate from prorated earnings, or another written method. Pick one and keep it.

Wrong-scope statutory lines deduct people who should not be in, or skip people who should. Assignment rules are cheaper than next-cycle patches. Dayzen can calculate these components when configured; it does not file EPF, ESI, professional tax, or TDS, and it does not remit to government. Do not retell calculation versus filing versus bank pay here.

Recoveries

Recoveries are deductions that return money already given or scheduled: a salary advance, a loan instalment, a notice-period shortfall you have decided to run in a normal month, or a similar company receivable. They are not statutory just because they appear next to PF on the slip. They need a principal, a remaining balance, and a recovery amount for the period. If you only type a deduction without a balance, you will recover too long or stop too early.

Give recoveries their own lines. Do not hide an advance inside “other deduction.” The advance article owns issue, schedule, balance, and exit recovery; this page only requires a named line the run can post to. Loss of pay is an outcome of unpaid days after attendance and leave close, shown as a deduction or a reduced earning. It is not a standing template rupee “because last month was messy.”

How lines show on the payslip and in reports

Payslip anatomy — identity, period, earnings, deductions, net — belongs on what belongs on an Indian payslip. The template is the engine behind those rows. Hidden lines that change net without explanation destroy trust. Reports need stable codes, not only display names: renaming “Special allowance” mid-year without a code breaks year-to-date. Dayzen dashboards and reports read the calculated run. They will not invent a component you never configured, and they will not replace a bank file or a government challan. Recurring monthly corrections are real components with owners. A one-off because last month locked wrong is an adjustment path, not a junk drawer on the template.

Building and changing a template without turning it into folklore

Start from the contract and the salary-structure decision, not from a competitor’s screenshot. Add recurring earnings until CTC is allocated, statutory lines only after scope and the official method for this year are decided, variable earnings you actually pay, and recoveries you actually issue. Stop. Write the effective month when you change a template. Do not silently remap heads in a locked month. Test a full-month employee, a mid-month joiner, and someone with a recovery plus a variable line. If net cannot be explained from the lines, the template is not finished. Walk the same cases through Dayzen payroll so the software reproduces the catalogue rather than inventing a second one.

---

A payroll template is a named list of recurring earnings, variable earnings, configured statutory lines, and recoveries. Keep examples generic, keep statutory methods on official sources, and keep Dayzen in its lane: templates, adjustments, dashboards, reports, and payslips as calculation — not filing, and not bank disbursement. Structure design stays on the salary-structure article; the monthly happy path stays on the run checklist; the printed document stays on the payslip anatomy page.