First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.
Continue in the practice tool above to load more questions, 50 at a time.
Question 1Core HR and payroll
In Infor CloudSuite HCM, which element of the employee record uniquely identifies a worker across the entire tenant and is never reused after termination?
- The legal employer tax identifier
- The position code attached to the primary assignment
- The employee number assigned by the global sequence Correct answer.
- The department cost center code
Explanation
The employee number is the tenant-wide unique identifier generated by the configured numbering sequence, and it remains tied to the person record even after termination so historical data stays intact. Position codes, tax identifiers, and cost centers describe organizational or legal attributes and are not person-level unique keys.
Question 2Core HR and payroll
A new hire must be able to view payslips but must not see salary amounts of colleagues. Which Infor CloudSuite HCM mechanism enforces this?
- Global HR parameter defaults
- Role-based security with data access restrictions Correct answer.
- Payroll calendar assignment
- Position hierarchy inheritance
Explanation
Access to sensitive pay data is controlled by security roles combined with data access levels, so a role can allow self-service payslip viewing while restricting visibility to other employees' compensation. Parameters, calendars, and hierarchies organize processing and structure but do not authorize data visibility.
Question 3Core HR and payroll
Which payroll element represents a recurring earnings amount that is defined once and then automatically included in every payroll run until an end date is reached?
- A recurring earning or deduction assignment Correct answer.
- A one-time payment
- A retroactive adjustment
- A manual off-cycle check
Explanation
Recurring earnings and deductions are attached to the employee with effective and end dates, so the payroll engine picks them up each period automatically. One-time payments, retro adjustments, and off-cycle checks are event-driven and do not repeat on their own.
Question 4Core HR and payroll
What is the primary purpose of a pay group in Infor CloudSuite HCM payroll?
- To group employees who share the same payroll calendar and processing rules Correct answer.
- To group employees by their manager for approvals
- To group employees by their job family for reporting
- To group employees by their benefit plan enrollment
Explanation
A pay group ties employees to a specific payroll calendar and set of processing rules, so runs can be executed for a defined population on shared dates. Job families, managers, and benefit enrollments are separate organizational concepts and do not drive payroll run selection.
Question 5Core HR and payroll
Which action creates a new effective-dated row on an employee's job record while preserving the prior row for history?
- Inserting a new effective-dated record Correct answer.
- Archiving the employee record
- Overwriting the current row in place
- Deleting the existing record
Explanation
Infor CloudSuite HCM uses effective dating, so changes are captured by inserting a new dated row while the previous row remains intact for audit and retroactive processing. Deleting, overwriting, or archiving removes or hides history rather than preserving it.
Question 6Core HR and payroll
An employee's pay rate changes mid-period. How does the payroll engine typically handle the change when the pay element is configured for proration?
- It applies the new rate to the entire period
- It splits the period and applies each rate to the days it was effective Correct answer.
- It defers the change to the next period
- It applies the old rate until the next calendar year
Explanation
Proration logic divides the pay period according to the effective dates of each rate, so earnings reflect the days worked at each rate. Applying one rate to the whole period, deferring the change, or waiting for a new year would misstate the employee's earnings.
Question 7Core HR and payroll
Which element determines the date range for which a payroll run calculates earnings and deductions?
- The benefit plan year
- The payroll calendar period Correct answer.
- The position effective date
- The employee hire date
Explanation
The payroll calendar defines period start and end dates, and each run calculates earnings and deductions for that defined window. Hire dates, plan years, and position dates influence eligibility but do not set the calculation window.
Question 8Core HR and payroll
A retroactive pay adjustment is required after a late-approved salary increase. What is the standard approach in Infor CloudSuite HCM payroll?
- Reopen and rerun every historical payroll period
- Process a retro calculation that compares prior results with recalculated results and pays the difference Correct answer.
- Ignore the change until the next annual review
- Manually add a one-time payment equal to the estimated difference
Explanation
The payroll engine recalculates prior periods using the corrected data and pays the net difference as a retro adjustment, preserving the audit trail. Manual estimates, full reruns of closed periods, or deferral all create control or accuracy problems.
Question 9Core HR and payroll
Which configuration controls how many hours an employee must work before overtime is calculated at a premium rate?
- The shift differential code
- The pay group calendar
- The overtime rule with its threshold and rate multiplier Correct answer.
- The absence plan accrual rule
Explanation
Overtime rules define the threshold, eligibility, and multiplier that the payroll engine applies to qualifying hours. Calendars, differential codes, and absence plans affect timing, premiums for shifts, and leave balances respectively, not the overtime threshold.
Question 10Core HR and payroll
Which object links an employee to a specific job, location, and manager for a defined period?
- The person record
- The assignment record Correct answer.
- The benefit group record
- The legal entity record
Explanation
The assignment record captures the working relationship details such as job, location, and manager for an effective period, and an employee may have multiple assignments. The person record holds identity data, while legal entity and benefit group records serve different purposes.
Question 11Core HR and payroll
An employee transfers to a new legal entity but stays in the same position. What must typically be created to reflect the transfer correctly for payroll?
- A new position code with the same attributes
- A new person record replacing the old one
- A new pay group only, with no assignment change
- A new assignment with the new legal entity and appropriate effective date Correct answer.
Explanation
Because payroll liability follows the legal entity, the transfer is modeled with a new assignment effective on the transfer date while the person record persists. Replacing the person record, changing only the pay group, or duplicating the position does not correctly capture the employing entity.
Question 12Core HR and payroll
Which absence configuration defines how much leave an employee earns per pay period and the maximum balance that can be carried?
- The time entry approval workflow
- The shift schedule pattern
- The absence reason code
- The accrual plan with accrual rate and carryover rules Correct answer.
Explanation
Accrual plans specify the earning rate, eligibility, and carryover or maximum balance limits applied each period. Reason codes categorize absence, schedules define working patterns, and workflows route approvals, but none of these set accrual amounts.
Question 13Core HR and payroll
A payroll administrator needs to verify gross-to-net results before finalizing a run. Which capability supports this review?
- Payroll simulation or a trial calculation of the run Correct answer.
- Employee self-service updates
- Automatic check printing
- Direct posting to the general ledger
Explanation
Simulation or trial calculation lets the administrator review calculated earnings, deductions, and net pay before committing the run. Posting to the ledger, printing checks, and self-service updates occur after or outside the review step and do not validate results.
Question 14Core HR and payroll
Which deduction configuration ensures that an employee's net pay never falls below zero when multiple deductions apply?
- A flat deduction amount
- A deduction end date
- Deduction priority with arrears handling Correct answer.
- A pre-tax deduction flag
Explanation
Deduction priority sequences which deductions are taken first, and arrears handling carries any shortfall forward when net pay would otherwise go negative. Flat amounts, tax flags, and end dates affect calculation or timing but not the ordering that prevents negative net pay.
Question 15Core HR and payroll
What is the effect of setting a pay element's calculation basis to a percentage of another earning?
- The element is excluded from taxation
- The element requires manual entry each run
- The element is derived from the referenced earning each time payroll runs Correct answer.
- The element becomes a fixed amount per period
Explanation
A percentage-of-earnings basis makes the element recalculate from the referenced earning during each run, so changes in the base flow through automatically. Fixed amounts, tax treatment, and manual entry are governed by other settings.
Question 16Core HR and payroll
Which record stores an employee's bank account details used for net pay disbursement?
- The emergency contact record
- The tax withholding record
- The benefit enrollment record
- The payment method or direct deposit record Correct answer.
Explanation
Payment method records hold bank routing and account information used to disburse net pay electronically. Benefit enrollment, tax withholding, and emergency contacts serve unrelated purposes and are not used for disbursement.
Question 17Core HR and payroll
A company runs payroll for two legal entities with different pay cycles. How should the configuration be structured?
- One pay group per department
- A single off-cycle run for both entities
- One shared pay group with a single calendar
- Separate pay groups per entity aligned to their respective calendars Correct answer.
Explanation
Because pay groups bind employees to a calendar and processing rules, entities with different cycles need distinct pay groups matched to their calendars. A shared group, department grouping, or combined off-cycle run cannot accommodate divergent cycles cleanly.
Question 18Core HR and payroll
Which statement best describes the relationship between a person record and an employee record in Infor CloudSuite HCM?
- A person record holds identity data and can be linked to one or more employee records Correct answer.
- An employee record must exist before a person record can be created
- Person and employee records are the same object with different labels
- A person record is created only after the first payroll run
Explanation
The person record centralizes identity and personal information, and employment data is held on linked employee records, which supports scenarios such as rehires or multiple jobs. The other statements invert or misstate this relationship.
Question 19Core HR and payroll
What does a payroll reconciliation report typically compare to validate a completed run?
- Employee headcount against position budget
- Benefit elections against plan documents
- Current period results against prior period or expected totals Correct answer.
- Time entries against shift schedules
Explanation
Reconciliation compares the current run's totals with prior periods or expected amounts to detect anomalies before posting. Headcount, benefit elections, and schedule comparisons support other audits but do not validate payroll totals.
Question 20Core HR and payroll
A terminated employee must receive final wages including accrued but unused vacation. Which configuration supports paying out the balance automatically?
- A manual one-time payment entered by the administrator
- An extension of the employee's pay group end date
- An accrual plan payout rule tied to the termination action Correct answer.
- A retro adjustment to the last regular run
Explanation
Payout rules on the accrual plan trigger calculation of unused balances when the termination event is processed, ensuring consistent final pay. Manual payments, retro adjustments, and extending pay group dates do not systematically handle accrued balances.
Question 21Core HR and payroll
Which combination correctly describes how a mid-period hire's salary is calculated when proration uses a workday basis?
- Salary prorated only if the hire date falls on the first workday
- Salary divided by workdays in the period, multiplied by workdays from the hire date Correct answer.
- Salary divided by calendar days, multiplied by calendar days worked
- Full salary paid because the hire occurred within the period
Explanation
Workday-basis proration divides the period salary by the number of workdays and multiplies by the workdays the employee was active, which excludes non-working days from the calculation. Paying full salary, using calendar days, or conditioning on the first workday misapplies the basis.
Question 22Core HR and payroll
An employee has two assignments in different pay groups. What is a key payroll consideration?
- Both assignments are combined into a single pay group run
- Each assignment is processed under its own pay group and calendar Correct answer.
- Only the primary assignment is ever paid
- The secondary assignment is paid only through off-cycle runs
Explanation
When assignments belong to different pay groups, each is processed according to its own calendar and rules, which can produce separate payments. Ignoring the secondary assignment, merging groups, or restricting to off-cycle runs misrepresents the configuration.
Question 23Core HR and payroll
Which control best prevents an employee from being paid after termination in a subsequent payroll run?
- Removing the employee's bank account details
- Termination effective dating combined with pay group end-date validation Correct answer.
- Restricting the employee's self-service access
- A manual review of the payroll register after payment
Explanation
Effective-dated termination combined with validation that the assignment end date precedes the run period stops payment at the source. After-the-fact review, access restriction, or removing bank details does not prevent the erroneous payment from being calculated.
Question 24Core HR and payroll
Which statement about retroactive deduction recalculations is accurate?
- They apply only to statutory deductions
- They are prohibited once a period is closed
- They always increase the employee's net pay
- They adjust prior deduction amounts and can produce arrears when the original deduction was too low Correct answer.
Explanation
Retro processing recalculates prior deductions and reconciles the difference, which may create arrears if too little was withheld originally. Closed periods can still be adjusted through retro, net pay may rise or fall, and the logic applies to voluntary as well as statutory deductions.
Question 25Core HR and payroll
Which practice best supports auditability of manual pay adjustments in Infor CloudSuite HCM?
- Batching adjustments into a single generic earning code
- Applying adjustments through a spreadsheet outside the system
- Entering adjustments directly into the final net pay amount
- Recording adjustments as documented pay elements with reason codes and approval Correct answer.
Explanation
Documented pay elements with reason codes and approvals create a traceable record linking each adjustment to its justification. Editing net pay directly, using external spreadsheets, or collapsing adjustments into one generic code destroys the audit trail.
Question 26Core HR and payroll
In Infor CloudSuite HCM, which structure groups employees who share the same payroll rules, pay cycle, and calendar so they are processed together?
- Job code
- Position control group
- Pay group Correct answer.
- Benefit plan
Explanation
A pay group is the payroll processing unit that binds employees to a common pay cycle, run calendar, and set of payroll rules. Employees in different pay groups are calculated in separate runs even when they belong to the same legal entity.
Question 27Core HR and payroll
Which component of a pay element defines the arithmetic applied to its input values, such as multiplying hours by a rate?
- Calculation rule Correct answer.
- Ledger account mapping
- Eligibility profile
- Payroll calendar
Explanation
The calculation rule attached to a pay element determines how inputs are transformed into an amount, for example rate times hours or a flat amount. Eligibility profiles and calendars affect who and when, not the arithmetic itself.
Question 28Core HR and payroll
An HR administrator needs to record a job history change effective on a future date without altering the employee's current assignment today. Which capability supports this?
- Entering a dated, future-effective row in the employment or assignment history Correct answer.
- Creating a duplicate employee record for the future state
- Deleting the current assignment and recreating it on the effective date
- Overwriting the current row and relying on audit logs to recover the prior value
Explanation
Infor CloudSuite HCM stores history as dated, effective-dated rows, so a future-dated change sits alongside the current row and becomes active on its effective date. This preserves the current state until the change takes effect.
Question 29Core HR and payroll
Which object holds the employment relationship that payroll and benefits processing reference for an individual?
- Organization unit
- Person record
- User account
- Employee record Correct answer.
Explanation
The person record captures the individual, while the employee record represents the employment relationship that payroll, benefits, and assignment data attach to. Payroll processing references the employee record rather than the person or login account.
Question 30Core HR and payroll
Which configuration element determines the cut-off and pay date for a payroll run?
- Pay element
- Deduction rule
- Benefit eligibility profile
- Payroll calendar Correct answer.
Explanation
The payroll calendar defines period start and end dates, cut-offs, and pay dates that a run uses. Pay elements and deduction rules describe amounts, not the timing of the run.
Question 31Core HR and payroll
What is the primary purpose of a pay element in Infor CloudSuite HCM payroll?
- To schedule the payroll run for a legal entity
- To define a discrete earning or deduction that the payroll engine can calculate and report Correct answer.
- To store the employee's tax filing status for the year
- To assign a manager to an employee for the assignment period
Explanation
A pay element represents a specific earning or deduction, such as base salary or a union due, with its own calculation and reporting behavior. Other objects handle management relationships, tax data, and run scheduling.
Question 32Core HR and payroll
Which record type links an employee to a position for a defined period and is used by payroll to determine the applicable salary?
- Person
- Benefit enrollment
- Payroll run
- Assignment Correct answer.
Explanation
The assignment ties an employee to a position, organization, and period, and carries the salary and pay group used in payroll. Person and enrollment records do not by themselves define the position-based salary period.
Question 33Core HR and payroll
Which control ensures an employee's net pay is not reduced below zero when several deductions are scheduled in the same run?
- A pay element calculation basis of percentage of gross
- A benefit eligibility profile
- A payroll calendar cut-off date
- A deduction priority and arrears handling rule Correct answer.
Explanation
Deduction priority sequencing combined with arrears handling determines the order deductions are taken and what happens when funds are insufficient, preventing negative net pay. Calculation basis and calendar settings do not address insufficient funds.
Question 34Core HR and payroll
An employee's assignment changes from one pay group to another mid-period. What is the typical payroll consideration?
- The employee is automatically excluded from payroll until the next full period
- Only the new pay group's calendar applies to the entire period
- The pay group change is ignored until year-end reconciliation
- The employee may need to be processed in both pay groups for the portion of the period in each Correct answer.
Explanation
When an assignment moves between pay groups mid-period, each pay group's calendar and rules apply to the portion of the period the employee was in it, so the employee can appear in more than one run. Ignoring the split would misstate earnings and deductions.
Question 35Core HR and payroll
A pay element is configured with a calculation basis of a percentage of another earning. What is the practical effect?
- Its amount is derived from the referenced earning rather than entered independently Correct answer.
- Its amount is fixed at the value stored on the pay element definition
- Its amount is calculated only when the referenced earning is zero
- Its amount is taken directly from the employee's bank record
Explanation
A percentage-of-earning basis makes the element dependent on another earning, so the referenced amount drives the result. This is commonly used for contributions or premiums tied to base pay.
Question 36Core HR and payroll
Which approach best supports auditability when an administrator must enter a manual pay adjustment?
- Adjust the employee's base salary temporarily and reverse it in the next period
- Record the adjustment as a distinct pay element input with a reason code and supporting documentation Correct answer.
- Post the adjustment directly to the general ledger outside payroll
- Ask the employee to confirm the amount by email and rely on that as the record
Explanation
A distinct input with a reason code keeps the adjustment traceable through calculation, reporting, and audit without distorting base pay. Temporary salary changes and off-system postings break the audit trail.
Question 37Core HR and payroll
A terminated employee has accrued but unused vacation that must be paid in the final run. Which configuration supports this?
- A recurring deduction with arrears enabled
- A benefit eligibility profile with a termination event
- A pay group calendar with an early cut-off
- A termination payout rule that references the absence balance and generates a final earning Correct answer.
Explanation
Final pay for unused leave requires a payout rule that reads the absence balance at termination and produces a corresponding earning in the final run. Deductions, eligibility profiles, and calendar cut-offs do not generate the payout.
Question 38Core HR and payroll
Which practice best verifies gross-to-net results before a payroll run is finalized?
- Relying on the prior period's totals as a baseline
- Reviewing only the total gross amount for the legal entity
- Approving the run and checking the bank file after disbursement
- Reviewing a payroll register or simulation report showing earnings, deductions, and net by employee Correct answer.
Explanation
A register or simulation report exposes each employee's earnings, deductions, and net before finalization, allowing errors to be corrected. Post-disbursement checks or aggregate-only reviews cannot prevent incorrect payments.
Question 39Core HR and payroll
An employee has two concurrent assignments in different pay groups. What is a key payroll consideration?
- Each assignment is processed under its own pay group's rules and calendar Correct answer.
- Both assignments must use the same pay group by design
- The secondary assignment is paid only at year-end
- Only the primary assignment is ever paid
Explanation
Concurrent assignments can belong to different pay groups, so each is processed under its own rules and calendar, and totals are consolidated for the person. Assuming only one assignment is paid would understate earnings.
Question 40Core HR and payroll
Which mechanism best prevents payment of an employee after termination in a later payroll run?
- A pay element with a percentage calculation basis
- A manual note in the employee's file
- A deduction with arrears enabled
- An effective-dated termination that ends the assignment before the run's period start Correct answer.
Explanation
An effective-dated termination that closes the assignment before the run period means the employee is not eligible for that run. Manual notes and unrelated pay element settings do not affect eligibility.
Question 41Core HR and payroll
What does a payroll reconciliation typically compare to validate a completed run?
- The current run against the prior year's audited financial statements
- Run totals against the detailed employee-level results and expected control totals Correct answer.
- The payroll calendar against the organization hierarchy
- The bank file against the benefit enrollment records
Explanation
Reconciliation checks that aggregate run totals equal the sum of employee-level details and expected control totals, catching discrepancies before posting. Comparing unrelated records does not validate the run.
Question 42Core HR and payroll
A mid-period hire's salary is prorated using a workday basis. Which approach reflects that method?
- Pay the full period salary and recover the excess in the next period
- Divide the annual salary by twelve regardless of the hire date
- Divide the period salary by the number of working days in the period and multiply by days worked Correct answer.
- Multiply the hourly rate by the number of calendar days in the period
Explanation
Workday proration divides the period salary by the working days in the period and multiplies by the working days the employee was active. Using calendar days or ignoring the hire date produces a different, incorrect amount.
Question 43Core HR and payroll
Which configuration links an employee's bank account to net pay disbursement?
- A payment method or payee record with bank details and distribution percentages Correct answer.
- A payroll calendar entry
- A benefit eligibility profile
- A pay element input value
Explanation
Payment method or payee records hold bank details and the split percentages used to disburse net pay. Pay element inputs and calendars do not carry bank account information.
Question 44Core HR and payroll
Why should a pay element's calculation rule be tested with a simulation before it is used in a live run?
- Simulation reveals calculation and eligibility errors without affecting real payments Correct answer.
- Simulation automatically updates the general ledger balances
- Simulation permanently locks the pay element from further changes
- Simulation replaces the need for payroll reconciliation
Explanation
Simulation exercises the calculation rule against employee data so errors surface before real disbursement, protecting employees and the ledger. It does not lock configuration or substitute for reconciliation.
Question 45Core HR and payroll
An employee receives a late-approved salary increase covering prior periods. What is the standard way to pay the shortfall?
- Post the difference as a one-time deduction
- Change the current salary only and ignore prior periods
- Create a new employee record for the retroactive period
- Generate a retroactive adjustment that recalculates prior periods and pays the difference Correct answer.
Explanation
Retroactive processing recalculates the affected prior periods under the new rate and pays the resulting difference. Ignoring prior periods or misclassifying the amount as a deduction produces incorrect pay.
Question 46Core HR and payroll
Which statement about retroactive deduction recalculation is accurate?
- Deductions are never affected by retroactive earning changes
- Retroactive deductions are always posted as earnings
- Retroactive deduction changes require a new legal entity
- Deductions tied to a recalculated earning may themselves be recalculated for the affected periods Correct answer.
Explanation
When an earning is recalculated retroactively, deductions whose basis depends on that earning can also be recalculated for the affected periods. Treating deductions as unaffected or as earnings is incorrect.
Question 47Core HR and payroll
A company runs payroll for two legal entities with different pay cycles. How should configuration be structured?
- Separate pay groups per legal entity and cycle, each with its own payroll calendar Correct answer.
- One pay group per employee regardless of entity
- A single calendar shared by all entities with no pay groups
- A single pay group with one calendar for both entities
Explanation
Pay groups bound to each legal entity and cycle, each with its own calendar, keep processing and reporting aligned with legal requirements. A single shared group or calendar cannot represent different cycles.
Question 48Core HR and payroll
Which analysis best explains why an employee appears in two payroll runs in one month?
- The payroll calendar was duplicated by mistake
- The employee's pay element was configured with a percentage basis
- The employee's assignment moved between pay groups mid-period, so each group processed its portion Correct answer.
- The employee was double-hired into two person records
Explanation
A mid-period pay group change causes each pay group to process the portion of the period the employee was in it, producing two run appearances. Duplicate person records or calendar errors are separate issues, and a percentage basis does not cause dual runs.
Question 49Core HR and payroll
An auditor asks how a manual adjustment can be traced from entry to the general ledger. Which chain best answers this?
- Adjustment input, calculation result, payroll register line, and ledger posting reference Correct answer.
- Employee email, manager approval, and bank statement
- Person record, user account, and organization unit
- Pay group calendar, benefit enrollment, and position hierarchy
Explanation
Traceability runs from the input through the calculation result, the register line, and the ledger posting reference, forming an auditable chain. Records unrelated to the adjustment do not establish that chain.
Question 50Core HR and payroll
Which scenario most likely indicates an incorrect deduction priority configuration?
- A deduction amount equals a percentage of a referenced earning
- An employee's net pay equals gross pay minus all deductions
- A pay element appears on the payroll register with a reason code
- A statutory deduction is reduced while a voluntary deduction is paid in full when funds are insufficient Correct answer.
Explanation
Statutory deductions normally take precedence over voluntary ones, so paying a voluntary deduction in full while reducing a statutory one signals a priority error. The other scenarios describe normal payroll behavior.