How Frappe HR income tax slabs work for payroll teams
Frappe HR uses income tax slabs to calculate the tax withheld from each employee's salary slip, and it lets payroll teams adjust that figure for each person through employee tax exemption declarations and the proofs that support them. Payroll leads need this when every cycle has to withhold the right amount across employees who have made different declarations. The configuration sits inside Frappe HR, which runs on ERPNext, so it applies to teams that self-host ERPNext with the HR module and whose payroll country calculates tax by slabs. Teams whose country uses a different method, or whose tax is handled by a separate statutory app, should confirm the scope with their implementer before they build anything.
The rules themselves are not something DeployOpen supplies. The slab bands, rates, rebates, exemption categories, proof requirements and filing obligations must come from the employer's tax advisor or the tax authority, and the written rule set should be signed off before anyone enters it into the system. DeployOpen's role is to translate that approved rule set into Frappe HR settings, test the calculations against worked examples provided by the client, and document how the configuration behaves when the rules change. Ask the advisor to state each rule with its effective date, because Frappe HR applies slabs by effective date and an error in the date will affect every slip calculated after it.
Before go-live, confirm three things with your advisor and your team: which slab tables apply to which employees, how declarations and proofs will be collected and approved, and who owns updates when the authority changes the rates. Then run a parallel payroll for at least one cycle, comparing the tax computed by Frappe HR with the figures your current process produces for the same employees. Differences usually trace back to a missing structure assignment, a declaration entered after the cycle closed or a slab with the wrong effective date, so review those links first. Keep the income tax computation report as evidence for auditors, but remember that it documents your configuration and does not certify that the tax was correct.
Which tax setup fits your payroll country and team
When every employee is paid under one tax jurisdiction and that jurisdiction's income tax can be expressed as dated slabs, most of the work stays inside core Frappe HR. You create the Income Tax Slab records with their effective dates, attach them to the relevant salary structure assignments, and let the payroll run compute tax on each salary slip. Your tax advisor still supplies the rates, thresholds, rebates and rules for which allowances are taxable, and those figures must be entered exactly as the law states them.
- Slab records: Enter each slab band, rate and effective date from the rules your adviser confirms, and keep older slabs so past payrolls can be recalculated.
- Structure assignments: Link the correct slab to each salary structure assignment so the tax follows the employee, not a spreadsheet.
- Exemption declarations: Decide which declarations and proofs your jurisdiction accepts and configure them in Frappe HR only where your adviser confirms the treatment.
- Filing outputs: Confirm with your adviser whether the income tax computation report meets your filing needs or whether a separate return format is required.
Confirm with your local tax adviser that a single slab table truly represents your rules before you rely on it for live payroll.
Where a country has its own statutory payroll rules, such as the India Payroll app for Indian statutory payroll, the country app supplies much of the tax logic and filing structure. Frappe HR still runs the employee records, salary structures, payroll entries and accounting postings, but the country app adds the statutory components, regime selection and returns that the generic slab setup does not cover. Your team configures both layers and must check that they do not double-count the same deduction.
- App coverage: Confirm which app and version covers your jurisdiction and whether it is actively maintained for your ERPNext and Frappe HR version.
- Core configuration: Keep employee master data, salary components and payroll frequency in core Frappe HR, following the country app's setup guidance.
- Statutory layer: Let the country app handle the statutory deductions, regime choices and filing formats it documents, instead of rebuilding them with custom slabs.
- Overlap checks: Test a sample payroll to confirm no tax component is calculated twice across core slabs and the country app.
- Local supply: Ask your local adviser to validate the app's rule tables and filing outputs before go-live.
Check the app's documentation for the exact version pairing and the statutory rules it does not cover in your situation.
When staff are paid in more than one country, a single slab table is rarely enough, because each employee's tax follows the jurisdiction of their work or residence. The practical approach is to segment the setup by country: separate salary structures, slab sets and, where needed, companies or payroll entries per jurisdiction. Frappe HR can hold these side by side, but cross-border rules such as tax treaties, dual residency and expatriate treatment usually need input from advisers in each country.
- Segmentation: Group employees by payroll jurisdiction and assign each group its own structures and slab records.
- Local advisers: Obtain written tax rules for each country, including effective dates, and record who approved each rule set.
- Country apps: Use a country-specific app only for the jurisdictions it covers and keep the others on core configuration.
- Reporting: Confirm which accounting entries and tax reports must be separated by company or currency.
- Change control: Set up a process to add a new country before the first employee is paid there.
Identify every jurisdiction in your workforce now, because each one adds rules, advisers and testing effort.
Configuration options for tax slabs and exemptions
This table compares the four building blocks that drive income tax in Frappe HR: the Income Tax Slab, the salary structure assignment, the exemption declaration and its proofs, and the computation report. Read each row as a question to answer before configuration starts. The main takeaway is that a slab only affects an employee once it is linked through an assignment, and exemptions only reduce tax after proofs are reviewed.
| Building block | Purpose | When it fits | What to confirm before relying on it |
|---|---|---|---|
| Income Tax Slab | Holds the slab rows, rates and the effective date that tax tables are based on | Each regime or tax year that applies to your employees, including separate slabs for old and new regimes where your country offers both | Effective dates match your statutory calendar, slab limits and rates are entered from the current official source, and cess or surcharge rules are included if they apply |
| Salary structure assignment | Links a slab to an employee from a given date so payroll computes tax for that person | Every employee who should be taxed under a given slab, including mid-year joiners and anyone changing regime | Assignments carry the correct slab and start date, and existing assignments are reviewed after any change to the structure or slab |
| Employee tax exemption declaration | Records the exemptions and deductions an employee claims for the financial year | Employees who claim allowances, deductions or investment-based relief that reduce taxable income | The declaration period, the exemption categories your payroll policy accepts, and the cutoff date for late declarations |
| Exemption proofs | Stores the documents that back each declared amount so payroll can accept or reject it | Any declared exemption that needs evidence, such as rent receipts or investment certificates | Which proof types HR accepts, who approves them, and whether accepted amounts are capped to the declared figure |
| Income tax computation report | Shows taxable income, slabs applied and tax computed per employee for review | Checking tax before a payroll run, reconciling declarations against proofs and answering employee queries | Report filters match the financial year, figures agree with sample salary slips, and the report is reviewed by payroll or tax staff before filing |
| Payroll and statutory review | Confirms that the configured rules match the tax law and company policy in force | Before the first payroll run of a financial year and after any regulatory change | Who owns the rule set, what evidence is kept, and whether a tax adviser has reviewed the configuration |
Configure tax slabs, structure links and exemptions in order
This sequence takes payroll income tax from agreed rules to a verified result: slabs carry the right effective dates, each employee picks up the correct slab through their structure assignment, exemption declarations are collected with proofs, and the computation report matches an independent check before any salary slip goes out.
Confirm tax year and effective dates with the adviser
Before anything is built in Frappe HR, agree in writing with your tax adviser or payroll authority which financial year the slabs cover, which regime applies to each employee group, and the exact date from which each slab rate takes effect. Record the rate table, surcharge or cess rules, and any standard deduction the adviser confirms. Ask them to provide a worked annual example for one salary level so you can use it as the reference in later checks. This step is done when the adviser has signed off a single rule sheet that the configuration will follow. Frappe HR does not provide tax advice, so the rule sheet is the contract between your team and the adviser.
Create income tax slabs with effective dates
In Frappe HR, create one Income Tax Slab per regime or rule set, entering each band with its minimum and maximum amount and rate, and set the effective from date that matches the adviser's sheet. Where rules change in a later year, create a new slab with a new effective date rather than editing the old one, so historic salary slips still recalculate correctly. Enter any additional charges that apply above a threshold. Your check is to open the saved slab and compare every band against the rule sheet line by line, including the boundary amounts where one band ends and the next begins.
Attach slabs through salary structure assignments
Link each employee or group to the correct income tax slab by creating or updating Salary Structure Assignments with the slab set in the assignment, effective from the date the rule applies. Confirm that the salary structure used for payroll includes the component that drives taxable earnings, since the slab is applied to the taxable amount the structure produces. Assign a small pilot group first, then extend the assignment to the rest of the population in batches. The output is a list of employees with their slab, assignment date and structure, which you can export and compare with your HR records before the first payroll run.
Set the exemption declaration period and proof categories
Configure the employee tax exemption declaration period in Frappe HR for the financial year, and define the exemption categories your adviser has approved, along with the proof expected for each one. Open the declaration window only after the category list is final, because employees will submit against those categories. Confirm with your adviser which declarations and proofs must be reviewed before they reduce taxable income, and whether any proof must be retained for a period set by your local rules. The check is a test declaration submitted by a pilot employee and reviewed by the payroll user, confirming that the category, amount and proof fields behave as the adviser's rule sheet describes.
Test one employee with a draft salary slip
Choose a pilot employee whose salary, structure assignment and approved exemptions represent a typical case, and generate a draft salary slip for a single payroll period. Read the tax component on the slip and trace how it was derived: the taxable earnings, the slab applied, the exemptions deducted and the monthly deduction. Do not submit the slip. If the figures do not match the reference, return to the slab, assignment or declaration step to find the source of the difference before going further. This step is complete when the draft slip shows the expected monthly tax for that employee and the trace makes sense to someone who did not build the setup.
Reconcile the annual tax with a manual calculation
Take the same pilot employee's annual taxable income, apply the exemptions as declared, and calculate the annual tax by hand using the adviser's worked example method. Compare that figure with the total tax Frappe HR projects across the year for that employee, allowing for how the period deductions are spread across months. Record any difference and its cause, whether a rounding rule, a mid-year salary change or a slab date mismatch. Repeat with one employee at a different salary level and one with a mid-year change. This check is the most important one in the sequence, because a configuration that looks correct on a single slip can still spread tax unevenly across the year.
Run the income tax computation report
Once the pilot cases reconcile, run the income tax computation report for the full employee population for the financial year. Use it to check that every employee has a slab assignment, that declared exemptions appear with approved proofs only, and that the totals for taxable income and tax deducted by month agree with the payroll register. Investigate any employee with no assignment, a zero tax result where a positive one is expected, or exemptions without a reviewed proof. Save the report and the reconciliation notes as the evidence package for the adviser and, where your rules require it, for your auditors, who will form their own conclusions on that evidence.
Why effective dates decide which tax slab applies
A tax slab in Frappe HR only applies to pay periods on or after its effective date, so the date you set on each slab decides which bracket a salary slip uses. When a slab set is revised partway through the financial year, the new slabs take over from their effective date and the earlier months keep the rules that were in force at the time. Before you add a new slab set, confirm with your payroll owner which date the statutory change takes effect and whether any employee's pay period straddles it, because a mismatch between the slab date and the pay period is the most common reason a year-end tax total looks wrong.
A mid-year salary revision or a change of salary structure can also change which slab is picked, even when the slabs themselves are correct. Structure assignments carry their own effective dates, and the tax slab is linked to the structure, so an employee moved to a different structure or a new assignment can start being taxed under a different slab set from a date you may not have intended. Before any structure change goes live, run a tested check on a sample of employees across each affected structure, comparing the slip produced before and after the change for the same pay period, and confirm the year-to-date tax on the slip still matches the expected total. Designing the structures themselves, including components and formulas, is covered in the sibling topic on salary structures and salary components.
Protecting tax declarations and proof documents
Tax declarations and proof attachments contain salary, identity and family details, and they drive every withholding figure. The controls below cover who can see them, how long personal data stays in the system, how changes are traced, and how slab changes are rehearsed before they touch live payroll.
Restrict role access to declarations
Employee Tax Exemption Declarations and their proof attachments should be visible only to the roles that process payroll and to the employee who submitted them. Review which roles hold read and write permission on the declaration, the proof document and the Income Tax Slab doctype, and remove broad HR or accounts access that is not needed for the task. Test each role with a sample user before go-live, because permissions set on a parent document do not always reach the attachments you expect.
Minimize personal data in proofs
Proof documents such as rent receipts, investment certificates and loan statements often carry more personal data than the tax calculation needs. Agree a written list of the fields the payroll team actually uses, ask employees to redact account numbers and unrelated identifiers, and define who may download the original file. Check how attachments are stored, backed up and removed when an employee leaves, and confirm that your retention rule covers both the file and the declaration record.
Trace changes to slabs and declarations
Slab edits and declaration amendments change net pay for every affected employee, so you need to know who changed what and when. Confirm that Frappe's version history is enabled on the doctypes you rely on, and decide who approves a slab change before it is saved. Export the change log at each payroll cycle and keep it with the payroll run so an auditor or a manager can reconstruct the figures without asking the people who made them.
Back up before changing slabs
A slab change applied to an open payroll period can alter salary slips that are already reviewed. Take a verified database and file backup of the production site immediately before you add a new effective-dated slab or edit an existing one, and record the backup identifier in the change ticket. Confirm that you can restore to that point on a separate environment, since a backup that has never been restored tells you little about recovery.
Rehearse changes on a non-production site
Build the new slabs, structure assignments and exemption rules on a copy of the production site with recent employee data, then run a draft payroll and compare the income tax computation report with the figures from the previous cycle. Differences should be explained line by line before the change reaches production. Keep the non-production site out of reach of live employee email and payment integrations, and remove production-only scripts before the copy runs.
What teams ask before configuring payroll tax in Frappe HR
What does configuring income tax in Frappe HR cost, and what drives the effort?
The cost follows the written scope, and no price list applies. The main drivers are the number of tax slabs and regimes, how many countries or payroll jurisdictions the setup covers, how many exemption types the policy allows, how many employees fall into each rule group, and how many proof types must be reviewed. Each added regime or jurisdiction multiplies the test cases, because every slab set needs its own worked examples against sample salary slips. Ask for the quote to split the work into design of tax rules, build of slabs and structure assignments, exemption and proof setup, the computation report, and test payroll runs. Confirm whether any of these recur, such as annual slab updates when a tax authority changes its rates, and who performs them.
How long does income tax configuration and testing usually take?
Duration depends on how many rules have to be verified and how many parallel payroll cycles must be tested before go-live. A single country with one slab set and a simple exemption list is far shorter than a multi-jurisdiction setup with several regimes, declaration windows and proof workflows. Testing usually takes longer than building, because each slab change must be checked against salary slips for employees at the edges of each band, including mid-year joiners and employees whose structure changed. Plan for at least one full parallel payroll run before the first live cycle. Ask for the timeline to show the testing window separately, and confirm which tax calendar dates the project must hit.
What must our team provide before the work starts?
The engagement needs three inputs from your side. First, the tax rules as your tax adviser or payroll authority confirms them: slab limits, rates, effective dates, standard deductions, exemption categories and any rebate or surcharge rules. Second, employee data for the payroll population: employee IDs, joining and leaving dates, designations, current salary structures and any tax regime selections employees have made. Third, a sample payroll: a few months of historical salary slips or a representative test set, including edge cases such as arrears, unpaid leave and mid-year revisions. Without these, the build can encode an assumption that is wrong and only surface in a live cycle.
Can an internal payroll or HR team configure income tax alone?
Yes, for a simple setup, an internal team that knows Frappe HR and its payroll concepts can create tax slabs, link them through salary structure assignments and test a few salary slips. The risk grows when the rules span several effective dates, regimes or jurisdictions, or when exemption proofs must be verified and linked to declarations. Internal teams usually need a named owner for the tax rule source, a documented test set and a second reviewer for the first live cycle. A partner can take on the build and testing while your team keeps the rule ownership and approval. Decide this split in writing before the work starts so responsibility for each tax rate is clear.
Does DeployOpen issue tax compliance attestations or certifications for our payroll?
No. DeployOpen configures the Frappe HR system, its tax slabs, exemption workflows and computation report, and documents how each is set up and tested. It does not issue tax compliance attestations, audit reports or certifications. Your tax adviser decides whether the rules match the law, and an independent auditor or the relevant authority assesses compliance where that applies. DeployOpen can prepare the evidence those reviewers need, such as configuration records, test results and a change log for slab updates, but the conclusion on compliance rests with them.
How do we check that the income tax computation is correct after go-live?
Run the income tax computation report against a known test set before each payroll cycle, and compare the results with figures your tax adviser has calculated by hand for a sample of employees. Check employees near each slab boundary, those with exemptions applied, and those who changed structure or regime during the year. Keep a record of each slab change with its effective date so past runs can be reproduced. Ask the implementer which tests will be delivered as part of the handover and which will be your team's ongoing responsibility.
What should we ask for in a written quote for this work?
Ask for a scope that lists each country or payroll jurisdiction, the number of slab sets and effective dates, the exemption categories and proof types, the report deliverable, the test cases and the number of parallel payroll runs. Ask who maintains the tax rules after handover, how slab updates are applied, and whether any retainer covers changes when the law changes. Confirm what the quote excludes, such as the tax adviser's review, data cleansing, or integration with a separate payroll bank file. Fixed-scope agreements should state these items in writing before work starts.
What DeployOpen delivers on tax configuration
DeployOpen starts tax configuration with a written scope, because the slabs, exemption rules and proof requirements in Frappe HR are only as good as the requirements they encode. We work with your payroll lead and tax adviser to record which income tax slabs apply, how each one is keyed to an effective date, which salary structures and structure assignments will carry them, and which exemption declaration categories and proof types your employees must submit. The agreed requirements are documented in the engagement scope before any configuration begins, so the client, not DeployOpen, owns the decisions about what the tax rules say.
Once the requirements are agreed, we configure the Income Tax Slab records, link them through the relevant salary structure assignments, and set up the employee tax exemption declaration and proof workflow. We then build test cases from sample employees covering mid-year joiners, mid-year slab changes, declarations submitted late and proofs rejected after payroll has run. Each test records the expected tax deducted and the value the income tax computation report produces, so your team can rerun the same cases after any later change. Test data is anonymized or synthetic, and the test environment stays in infrastructure you control.
We then document the setup for payroll staff: how to add a new slab period, how to assign it to structures, how declarations and proofs move through approval, and what to check before each payroll run. We also prepare the evidence pack for your external auditors, including the configuration record, test results, change history and the report outputs for sampled periods. DeployOpen does not set tax law, interpret how a slab applies to a specific employee, or certify that the payroll results are correct. Your tax adviser confirms the rules, and independent auditors decide whether your controls are adequate.
How DeployOpen scopes and supports Frappe HR tax setup
DeployOpen plans and configures Frappe HR income tax slabs and employee tax exemptions inside your own ERPNext environment, starting from written rules your finance and HR teams have approved. Engagements are fixed-scope, so the slabs, exemption categories, proof requirements and reports are agreed in writing before any build work starts.
How we scope
- Inventory the tax regimes, financial years and employee categories the payroll must handle
- Document which slab tables, effective dates and salary structures are in scope
- Agree in writing which exemption declarations, proof types and approval steps are covered
How we build
- Configure income tax slabs by effective date and link them through structure assignments
- Set up exemption declarations and proof workflows that match your agreed HR policy
- Test the income tax computation report against sample salary slips before sign-off
How we hand over
- Deliver a written configuration record covering slabs, assignments, exemption rules and approvals
- Document the steps HR and payroll staff follow each financial year to update slabs
- Walk through the computation report with the people who will review it each cycle
How we support
- Support changes to slabs or exemption rules when tax rules are revised for a new year
- Available as a retainer for ongoing configuration reviews and upgrade testing
- Ask your tax adviser to confirm the final rates and rules before they go live
