{"id":3118,"date":"2026-04-30T10:14:31","date_gmt":"2026-04-30T10:14:31","guid":{"rendered":"https:\/\/onfinity.io\/blog\/uncategorized\/configure-hr-settings-erp-payroll-leave-recruitment\/"},"modified":"2026-04-30T10:14:31","modified_gmt":"2026-04-30T10:14:31","slug":"configure-hr-settings-erp-payroll-leave-recruitment","status":"publish","type":"post","link":"https:\/\/onfinity.io\/blog\/uncategorized\/configure-hr-settings-erp-payroll-leave-recruitment\/","title":{"rendered":"How to Configure HR Settings in ERP for Payroll, Leave, and Recruitment"},"content":{"rendered":"<p>Managing <a href=\"https:\/\/onfinity.io\/\">HR settings configuration<\/a> across disconnected payroll, leave, and recruitment modules creates inconsistencies. Different tax calendars, misaligned payroll periods, and conflicting leave policies force teams to configure the same data multiple times. Onfinity ERP consolidates this into a single configuration screen where income tax calendars, payroll balance periods, leave suffix logic, and recruitment criteria are defined once and applied across all HR modules.<\/p>\n<p>This centralized approach reduces setup time, minimizes errors, and ensures that payroll calculations, leave entitlements, and hiring workflows operate from the same foundation. Organizations managing multiple legal entities or complex leave policies benefit from reusable configurations that adapt to different business units without duplicating effort.<\/p>\n<h2>Mapping Payroll and Tax Calendars for Financial Accuracy<\/h2>\n<p>The income tax calendar defines the financial year used for statutory tax calculations, aligning with regional guidelines such as April to March for India or January to December for other jurisdictions. This calendar must be created in the period control screen before it can be selected in HR settings.<\/p>\n<p>The payroll balance calendar controls the accounting periods used for payroll accruals, reconciliation, and reporting. Both calendars are linked to pre-configured period controls, ensuring consistency between HR and finance modules. Using the same calendar for both income tax and payroll balance simplifies reconciliation and audit readiness.<\/p>\n<p>Onfinity allows organizations to maintain separate calendars per legal entity when managing multiple companies. This ensures that each business unit follows its own statutory requirements while sharing the same <a href=\"https:\/\/onfinity.io\/demo.php\">payroll calendar setup<\/a> framework.<\/p>\n<h2>Consolidating Expense Invoices and Payroll Posting<\/h2>\n<p>The consolidated expense invoice feature controls how employee expenses are grouped for posting to the general ledger. When enabled, all payroll expenses are combined into a single invoice, reducing the number of accounting entries and simplifying ledger reconciliation.<\/p>\n<p>A designated employee, typically from payroll or accounts, is assigned to generate these invoices. This employee must have a payroll term and payment method configured in their employee record under personal info and additional info tabs.<\/p>\n<p>If the checkbox is disabled, each expense entry is invoiced separately. This offers more granular control but increases administrative effort. The consolidated approach is especially useful for organizations that need to post payroll expenses efficiently while maintaining clear audit trails.<\/p>\n<h2>Configuring Leave Entitlements with Suffix-Based Logic<\/h2>\n<p>The leave suffix system separates leave logic from fixed values, allowing reusable configurations across leave types. In the leave group field, a generic suffix such as &#8216;max cap&#8217; is defined without specifying leave type names like annual or sick leave.<\/p>\n<p>Numeric values are configured separately in the global value window using this suffix. For example, annual leave max cap can be set to 24 days, while sick leave max cap is set to 10 days. Both reference the same suffix but apply different entitlements based on leave type.<\/p>\n<p>The accrual for resign checkbox controls whether leave continues to accumulate after an employee submits resignation. When enabled, a separate suffix such as &#8216;resignation max cap&#8217; becomes available. This allows organizations to define different entitlements for resigned employees during their notice period.<\/p>\n<p>For instance, annual leave resignation max cap might be set to two days, ensuring resigned employees receive reduced entitlements compared to active staff. This approach aligns leave policies with company resignation procedures without hardcoding values.<\/p>\n<h2>Enabling Payslip Approval Workflows and Recruitment Criteria<\/h2>\n<p>The payslip approval required checkbox enforces a review workflow before employees can view or download their payslips. When enabled, the system activates a job field where the process that generates payslips after HR approval is selected.<\/p>\n<p>If disabled, employees can directly access payslips once they are rolled out by payroll or HR. This setting gives organizations control over payslip distribution based on their internal approval policies.<\/p>\n<p>In the recruitment group field, the recruitment criteria setting defines whether hiring is position-based or grade-based. Selecting position ensures that job postings and applicant tracking follow position-specific requirements rather than generic grade structures.<\/p>\n<p>The employee group field specifies which group will be assigned when an applicant is converted into an employee after offer acceptance. This ensures that new hires are automatically placed into the correct organizational segment without manual intervention.<\/p>\n<h2>Reducing Setup Complexity with a Unified HR Configuration<\/h2>\n<p>A single <a href=\"https:\/\/onfinity.io\/\">ERP leave management<\/a> screen eliminates the need to configure payroll, leave, and recruitment separately. Predefined templates for document expiry alerts such as passport, visa, and contract are mapped here, along with employee milestone notifications like birthdays and work anniversaries.<\/p>\n<p>The reporting hierarchy is linked to tree configuration, ensuring that organizational structure is reflected across modules. This integration reduces training time and improves data accuracy by removing the need for duplicate setups.<\/p>\n<p>The week start day setting controls how attendance, shifts, and weekly leave accruals are calculated. Selecting Monday aligns with most regional standards, while Sunday is common in retail or Gulf countries. This field ensures that weekly reporting and leave calculations start on the correct day.<\/p>\n<p>Onfinity ERP&#8217;s unified approach speeds up implementation by allowing organizations to define core HR policies once and apply them across payroll, leave, workforce, and recruitment modules. Organizations managing multiple entities or complex leave policies benefit from this centralized, reusable configuration model.<\/p>\n<div style=\"max-width: 800px; margin: 20px auto;\">\n<p><strong>Watch how this works in Onfinity ERP:<\/strong><\/p>\n<div style=\"position: relative; padding-bottom: 56.25%; height: 0;\"><iframe src=\"https:\/\/www.youtube.com\/embed\/_lQMfXcJpvE\" style=\"position: absolute; top: 0; left: 0; width: 100%; height: 100%;\" frameborder=\"0\" allowfullscreen><\/iframe><\/div>\n<\/div>\n<h2>See the HR Settings Workflow in Action<\/h2>\n<p>If your organization is managing payroll calendars, leave policies, and recruitment workflows across disconnected systems, Onfinity ERP unifies these into a single configuration screen. <a href=\"https:\/\/onfinity.io\/demo.php\">Request a demo<\/a> to see the HR settings workflow in action and understand how it reduces setup complexity while ensuring consistency across modules.<\/p>\n<p>Follow us on <a href=\"https:\/\/www.linkedin.com\/company\/onfinityio\" target=\"_blank\" rel=\"noopener\">LinkedIn<\/a> for more insights on ERP best practices.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A unified HR settings screen in Onfinity ERP reduces setup complexity by centralizing payroll calendars, leave entitlements, and recruitment workflows\u2014ensuring consistency across modules and eliminating duplicate configuration effort.<\/p>\n","protected":false},"author":1,"featured_media":3119,"comment_status":"","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-3118","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/onfinity.io\/blog\/wp-json\/wp\/v2\/posts\/3118"}],"collection":[{"href":"https:\/\/onfinity.io\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/onfinity.io\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/onfinity.io\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/onfinity.io\/blog\/wp-json\/wp\/v2\/comments?post=3118"}],"version-history":[{"count":0,"href":"https:\/\/onfinity.io\/blog\/wp-json\/wp\/v2\/posts\/3118\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/onfinity.io\/blog\/wp-json\/wp\/v2\/media\/3119"}],"wp:attachment":[{"href":"https:\/\/onfinity.io\/blog\/wp-json\/wp\/v2\/media?parent=3118"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/onfinity.io\/blog\/wp-json\/wp\/v2\/categories?post=3118"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/onfinity.io\/blog\/wp-json\/wp\/v2\/tags?post=3118"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}