202
INTERMEDIATE PRACTICEUnderstand the operating control before running it

H2R 202 ยท TIME, PAYROLL, AND FINANCE

How do time, payroll, and Finance stay connected?

The employee lifecycle has financial consequences. Master data, compensation, time, absence, organisational assignment, and effective date must reach payroll correctly; the approved payroll result must then post to the right Finance accounts and controlling objects.

CONTROL CHAIN

Read the whole decision, not just its final screen

The result is trustworthy only when its business event, rule, identity, execution, and evidence agree.

  1. 01
    Employee and job dataInput
  2. 02
    Time and absenceEligibility
  3. 03
    Payroll inputsIdentity
  4. 04
    Payroll resultDecision
  5. 05
    Finance postingTarget
  6. 06
    Reconciliation evidenceEvidence

FIRST DECISION

Separate payroll input, calculation, and accounting consequence

A payroll result can be wrong because the employee input is wrong; payroll can be correct while its Finance posting is wrong. Diagnose the first stage that diverged rather than correcting the final amount alone.

Effective-date and pay-period boundary

A job change is valid from its EC effective date, but payroll processes it in a payroll period with a cut-off. Administrators must understand both dates to explain timing and retroactivity.

Time and absence input

Approved time, absence, valuation, eligibility, and pay types determine which facts become payroll inputs. A missing approval or late interface can be a process control, not a calculation error.

Payroll result

Payroll applies employee master data, compensation, time, absence, statutory rules, deductions, and retroactive logic to calculate the result for the relevant period.

ADMINISTRATOR AND SYSTEM-MANAGER LENS

What to understand before changing a setting

These are design and control questions. Detailed queues and incidents belong in 303 and 606.

Effective-date and pay-period boundary

A job change is valid from its EC effective date, but payroll processes it in a payroll period with a cut-off. Administrators must understand both dates to explain timing and retroactivity.

Time and absence input

Approved time, absence, valuation, eligibility, and pay types determine which facts become payroll inputs. A missing approval or late interface can be a process control, not a calculation error.

Payroll result

Payroll applies employee master data, compensation, time, absence, statutory rules, deductions, and retroactive logic to calculate the result for the relevant period.

Cost assignment

Company, cost center, organisational assignment, and payroll-posting rules influence where labour cost and liabilities land. Keep the HR assignment and Finance determination distinct.

Finance posting

A correct payroll result still needs correct posting mapping, account assignment, period, and document creation in Finance. Reconcile the payroll result to the accounting document.

Close and correction

Corrected employee data may require retroactive payroll, reversal, reposting, or a controlled accounting correction. Choose the correction path that preserves the audit trail.

INTERMEDIATE SCENARIO

A July transfer appears in EC, but August payroll uses the old cost center

First confirm the EC successor record and its effective date. Then establish the payroll cut-off, payroll-period input, cost-assignment derivation, and whether retroactive processing is expected. Correct the first unreliable input or determination and prove the payroll and Finance result.

  • Compare EC effective date with the payroll period and cut-off.
  • Trace the cost assignment from employee data through the payroll result.
  • Reconcile the corrected payroll result to its Finance posting.
CONTINUE THE PATHApply the model in the H2R practitioner map

Use 303 for operating hand-offs and 606 when a live case needs diagnosis and controlled recovery.

Open practitioner map