Core HR and payroll
What this domain tests
Core HR and payroll covers the employee record that payroll consumes: person, employment, job, position, pay, and the date-effective changes that alter them. The exam tests how Infor CloudSuite HCM stores history, how Action and Reason codes classify changes, and how pay groups, earnings, deductions, balances, and the payroll cycle turn that data into a confirmed, reconciled pay run.
Effective dating and Action Reason
Infor Global HR records are date-effective: a change does not overwrite the past; it inserts a new effective-dated row. The Action (Hire, Transfer, Promotion, Termination, Pay Change) and Reason pair explains why. Payroll and benefits read the row valid on the relevant date, so a back-dated transfer can create retroactive pay or benefit eligibility. Always check the effective date before saving; correcting a historical row without the right date can silently change prior payroll.
Payroll building blocks
A pay group links employees to a pay cycle, payroll calendar, currency, and GL mapping. Earnings and deductions carry calculation rules, taxable status, priority/sequence, and accumulators. Payroll runs typically move from time import and calculation to a pre-confirmation register, confirmation, payment, and GL output. Balances (YTD, QTD) are updated in the run; deduction arrears must be handled explicitly.
Worked example
An employee earns 52,000 annually, paid semi-monthly over 24 periods: 52,000 / 24 = 2,166.67 per period. The pay period is the 16th–30th. The employee is hired on the 20th, so 11 calendar days remain in a 15-day period. With calendar-day proration: 2,166.67 × 11/15 = 1,588.89 gross. The Hire action is effective on the 20th, the pay group is assigned, and the prorated earning is calculated. If the hire is entered after the run, a retro adjustment is needed rather than editing the confirmed register.
Traps
Do not confuse pay group with pay cycle. Do not forget deduction priority and arrears. Do not reconcile only gross pay; compare register, payment, and GL. Avoid changing a confirmed run instead of processing retro pay.