When HR teams manually define measurement units for leave balances, attendance records, or time-off requests across different departments, inconsistencies quickly emerge. One team tracks leave in hours while another uses days, creating reporting conflicts and policy enforcement challenges. Proper HR ERP configuration eliminates these issues by establishing standardized input values at the system level, ensuring every transaction uses the same measurement framework.
This foundational setup determines how your system calculates accruals, applies policies, and generates reports across all organizational units. Without it, automated workflows cannot function reliably.
Why Input Value Configuration Matters for HR Operations
Input values function as the measurement standards that your ERP system references whenever it processes HR transactions. When an employee submits a leave request, the system needs to know whether to calculate the request in days, hours, or another unit. This definition must exist before any leave policy can be configured or applied.
Organizations operating multiple locations face additional complexity. A corporate headquarters might measure leave in days while regional offices use different standards based on local labor laws. The input value definition layer allows administrators to establish either universal standards or location-specific variations, depending on business requirements.
This configuration also prevents downstream errors in transaction processing. Once a leave management system references an input value, every related calculation inherits that standard automatically. Accrual formulas, balance calculations, and approval workflows all operate using the same measurement framework, eliminating manual reconciliation.
The Input Value Setup Workflow in Onfinity ERP
Input value configuration begins in the general setup area under HR Management. Administrators access general definitions to create new values that will be referenced throughout the system. This placement ensures that foundational data definitions are established before transactional modules are configured.
Two mandatory fields control each input value: organization scope and name. The organization field determines whether the definition applies across all entities or only to specific locations. The name field establishes the label that users will see when the value appears in transactions or reports.
The system auto-fills the organization field based on the administrator’s login credentials, reducing manual entry and ensuring proper access control. If an administrator has permissions for multiple organizations, they can choose to apply the input value universally or limit it to specific entities.
Once saved, the input value becomes immediately available throughout the HR module. Leave configurations, attendance tracking, and other processes can now reference this standardized definition, ensuring consistency across all future transactions.
How Multi-Organization Input Value Management Works
Onfinity’s organization field offers two configuration approaches. The universal selector, marked with a star icon, applies an input value across all organizational units. This option suits businesses with standardized corporate policies that apply uniformly regardless of location.
The alternative approach configures input values at the individual organization level. Companies operating in multiple countries often need this flexibility because labor regulations vary by jurisdiction. One region might require leave tracking in days while another uses hours to comply with local employment law.
The multi-view display consolidates all configured input values into a single interface. Administrators can toggle between records to review definitions across the enterprise, making it straightforward to identify inconsistencies or audit configuration changes over time.
This organizational flexibility supports both centralized and decentralized HR management models. Corporate teams can establish baseline standards while regional administrators maintain the ability to configure location-specific variations when needed.
Setting Up Input Values for Leave Management Use Cases
Leave tracking requires input values defined as measurement units that match how your organization administers time-off policies. Most businesses use “days” as the standard unit because leave policies typically grant annual entitlements measured in full or half days.
Once the “days” input value definition exists in the system, every leave-related transaction references this standard automatically. When an employee submits a request, the system calculates the impact on their balance using days as the unit. Accrual formulas apply the same standard when adding leave entitlements at the start of each period.
This standardization enables automated balance calculations that update in real time. When a manager approves a leave request, the system deducts the correct number of days from the employee’s available balance without manual intervention. Reports showing leave utilization across departments all use the same measurement framework, making the data directly comparable.
The same configuration approach extends to other HR metrics beyond leave. Organizations tracking training time might create an input value for “training days” while those managing flexible work arrangements could define “remote work days” as a separate category.
Watch how this works in Onfinity ERP:
Best Practices for Managing Input Values in Your ERP
Complete your organization structure configuration before creating input values. The system uses organizational hierarchy to control access and determine where definitions apply, so this foundation must exist first.
Use clear naming conventions that business users will understand immediately. Technical labels like “LV_DAYS_01” create confusion, while straightforward names like “Days” or “Hours” make the purpose obvious to anyone configuring leave policies or reviewing reports.
Review your configured input values regularly using the multi-view display. Over time, organizations sometimes create duplicate definitions or inconsistent naming that reduces data quality. A quarterly audit of your general definitions helps maintain clean configuration.
When implementing across multiple organizations, establish your governance model early. Decide whether HR policies will be centrally managed or locally controlled, then configure input values to match that structure. Changing from organization-specific to universal definitions later requires reconfiguring dependent processes.
Document your input value definitions as part of your ERP configuration guide. When new administrators join your team or you need to troubleshoot issues, having clear documentation of why specific input values exist and where they are used saves significant time.
See How Onfinity Simplifies HR Configuration
If your team manually defines measurement units across different systems or struggles with inconsistent HR data, Onfinity’s unified approach to input value management provides a single configuration point that applies across all organizational units. Schedule a demo to see how multi-organization management works in practice and how standardized definitions enable automated leave tracking workflows.
Follow us on our LinkedIn page for more practical insights on ERP configuration and HR process optimization.