Attendance loss-of-pay, unpaid leave and approved overtime must reach payroll without double deduction or missing inputs.
Attendance-to-payroll operations
Close attendance with the exceptions resolved and the payroll impact understood.
Bring punches, shifts, leave, regularisation, loss-of-pay and overtime into one controlled closure before payroll computation begins.
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 HR and payroll teams that want to reduce late corrections, duplicate deductions and month-end reconciliation.
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
Attendance is exported before all corrections are approved.
02
Unpaid leave and attendance loss-of-pay overlap.
03
Overtime arrives as a separate spreadsheet.
04
Payroll variance is discovered after computation.
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.
Resolve the daily status
Use the configured attendance and leave policy for each employee and date.
Complete exception approvals
Close corrections, loss-of-pay and overtime with owner and status visible.
Validate the payroll feed
Merge attendance and unpaid-leave impact to avoid duplicate deduction.
Confirm closure by group or location
Begin payroll only when the approved populations are ready.
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.
Time & 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.
ExploreTimesheets & Overtime
Collect timesheets, overtime and compensatory-off requests, route them through policy-led approvals and pass approved values into payroll, project or reporting workflows.
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 duoHR avoid double deduction from attendance and unpaid leave?
The payroll material states that attendance loss-of-pay and unpaid leave are merged to avoid double deduction.
Can attendance be reprocessed after a policy correction?
Yes. The documented attendance scope includes reprocessing after policy correction.
Should payroll begin before every exception is resolved?
The recommended operating model is to make readiness and exceptions visible and close representative inputs before compute.
Attendance-to-payroll 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.