The payroll run should use approved attendance loss-of-pay and overtime rather than a manually edited export.
Connected monthly operations
Move approved attendance outcomes into payroll without another reconciliation layer.
Connect resolved attendance, unpaid leave, overtime and allowances to payroll through one employee, policy and effective-date foundation.
Representative operating scenario Current boundaries stated clearly
Payroll control roomIllustrative interaction
1Initiate2Compute3Review4Approve5Finalise
Readiness check
Owner and history remain visible482Employees
31Inputs pending
DraftRun status
Calculation in progress
Owner and history remain visible468Computed
14Exceptions
6m 18sIllustrative run
Variance and output review
Run remains reversible before finalisation94%Ready
11Variance flags
AvailableRollback
Authorised review
Owner and history remain visible471Approved
11Held
2Approvers
Payslips and outputs
Owner and history remain visible471Payslips
5Bank files
4Statutory outputs
Who this page is for
For organisations replacing separate attendance and payroll systems or repeated spreadsheet handoffs.
The operating problem
What usually breaks before the software conversation begins.
Use these symptoms to determine whether the issue is data, policy, ownership, monthly closure or an unsupported product requirement.
01
Employee IDs and organisational dimensions differ across systems.
02
Attendance is exported before approval closure.
03
Corrections must be copied into payroll manually.
04
The reason for a payroll deduction is difficult to trace.
A practical operating approach
Resolve the policy first, then automate the cycle.
The exact product setup is validated during discovery and demonstration. The sequence below keeps the rule, owner and downstream result connected.
Use one employee foundation
Keep the employee, location, grade, employment type and effective date consistent across modules.
Resolve attendance first
Apply policy, corrections, leave and overtime approvals in the operating system.
Feed only approved outcomes
Move accepted loss-of-pay, overtime and allowance values to payroll.
Review payroll variance
Trace material movement back to the originating attendance or employee event.
Connected product scope
View the full product The outcome depends on more than one isolated feature.
Review the upstream source, policy resolver, approval path and downstream output together.
Core HR
Centralise employee records, organisation structures, dated lifecycle changes and policy scope so downstream attendance, leave, payroll, performance and access decisions use the same governed foundation.
ExploreTime & Attendance
Apply configurable rules to punches, shifts and work patterns, explain why each day resolved as it did, and close exceptions before they become payroll corrections.
ExploreLeave Management
Configure eligibility, accrual, balance-year, sandwich, clubbing, carry-forward, comp-off and encashment rules for different employee populations through one policy resolver.
ExplorePayroll
Connect effective-dated salary structures, attendance and leave inputs, earnings, deductions, reimbursements, recoveries and statutory calculations in a payroll run that can be reviewed and rolled back before finalisation.
Explore
Evaluation questions
Bring this use case into a demo Confirm the exact policy, evidence and product boundary.
The answers below reflect the supplied product source. Customer-specific commitments still require live-product and commercial validation.
Can attendance corrections update payroll inputs?
The connected product positioning supports approved attendance outcomes flowing to payroll; cut-offs and reprocessing rules should be configured and demonstrated.
Can unpaid leave and attendance loss-of-pay overlap?
The payroll material says the two are merged to avoid double deduction.
Does integration require a separate connector?
Within duoHR the modules share a product foundation; external devices or systems may require a validated import, SFTP or API path.
Connected monthly operations
Validate this use case with one real policy or transaction.
Bring a representative employee, location, shift, payroll month or output. We will shape the walkthrough around the exact operating case.