How to Configure Provident Fund Calculator in uKnowva HRMS?

Introduction

Provident Fund (PF) is one of the most essential statutory deductions in any organisation's payroll structure.

Ensuring accurate configuration of PF rules helps maintain compliance with government regulations and automates employee and employer contributions effectively.

uKnowva HRMS offers a built-in Provident Fund Calculator Plugin, which enables admins to set up the exact salary components to be considered, define threshold limits, and implement the latest PF calculation logic.

This article will guide you step-by-step on how to access, configure, and activate this plugin to align with your organisation’s PF policy.

Step 1: Accessing the Provident Fund Calculator Plugin

Begin by logging into your uKnowva HRMS instance. From the top-right corner of your screen, click on your profile icon to reveal a drop-down list of options.

Select uKnowva Configuration.

A new configuration panel will appear with a side menu.

From the menu on the left, choose Plugin Manager. This section displays a complete list of available plugins.

Scroll through or use the search bar to locate the Provident Fund Calculator plugin.

 

Ensure the plugin is already installed and published. Once located, click on it to open the configuration pop-up where all PF-related settings can be defined.

Step 2: Configuring the Plugin Fields and Calculation Rules

Within the configuration pop-up, start by selecting the field where employees’ PF Account Numbers are stored.

From the drop-down list in the Provident Fund Account Number section, choose the correct profile field that captures this data for each employee.

Next, proceed to the “Calculate PF on total of” field. Here, you must select the specific salary components on which the PF amount should be calculated.

These components should exactly match the titles defined in your salary structure.

To add more components, you can click the plus (+) icon, and if any component needs to be removed, click the bin icon next to it.

After defining the salary components, enter the Basic Max Limit Amount.

This value is typically ₹15,000 as per EPFO guidelines, but you may adjust it based on your organisation’s policy.

This threshold determines whether the PF calculation will be limited to the basic salary or include additional allowances.

In the Provident Fund % section, enter the employee’s and employer’s contribution percentages.

Commonly, both employee and employer contribute 12% each. Fill in these values under the Employer’s Contribution field as applicable.

Another key configuration is the PF Threshold Amount – Max Amount to Be Deducted as PF.

If this field is set to ₹15,000, PF will only be deducted on the first ₹15,000 of the salary, regardless of the actual salary. This ensures compliance with EPFO’s wage ceiling.

The next set of configurations aligns with the 2016 clarification by the Supreme Court. If an employee's basic salary is greater than or equal to the threshold amount, then PF will be calculated strictly on the basic salary component alone.

However, if the basic salary falls below the threshold, then uKnowva HRMS’s plugin logic automatically considers additional allowances such as special or other regular components as part of the PF base.

This dynamic logic helps ensure that ordinary wages are appropriately factored into the contribution base, as required by law.

Once all the necessary fields are configured correctly, click the Save button to activate your changes. If needed, you may click Cancel to discard unsaved edits.

Conclusion

That’s it!

You’ve now successfully configured the Provident Fund Calculator plugin in uKnowva HRMS.

By following this process, you ensure that PF contributions are calculated accurately while staying compliant with the 2016 Supreme Court ruling and standard PF practices.

This configuration allows the payroll engine to handle both threshold logic and additional wage components with precision.

If you have any questions or need additional support, feel free to contact us at This email address is being protected from spambots. You need JavaScript enabled to view it..

Was this Article helpful?