Contract Labour Wage & Invoice Reconciliation

Frequently asked questions

How are contractor wage rates managed?+

Rates are configured per worker category, contractor, and state minimum-wage schedule, with revisions applying from their effective date and a full audit trail on every change. Iddion RegX applies the correct rate automatically per worker and site, so a rate revision in one state doesn't require manual updates across your contractor base.

What stops unauthorised overtime from being paid?+

OT beyond the configured threshold creates a digital approval request before it becomes payable — unapproved OT never enters the calculation. The gate knows what was worked, the rule knows what was approved, and the payable amount can only be the intersection. That structure closes unauthorised OT, ghost OT, and unclaimed legitimate OT together.

Why compute contractor payroll from gate data instead of contractor rosters?+

Contractor-submitted rosters are where leakage lives: inflated headcount, unworked OT credited, wrong rate codes applied. Iddion RegX computes wages only from verified attendance events, so every rupee traces to a biometric punch at a specific gate and time. Disputes get settled against records rather than arguments.

Are PF and ESI handled for contract workers?+

Yes — PF, ESI, and LWF are computed per worker each payroll cycle with challan-ready outputs, and mismatches surface in real time rather than at filing deadlines. The same records feed the registers in CLRA compliance software and the statutory-side matching in challan reconciliation.

Does it handle state-wise minimum wage differences?+

Yes. Minimum-wage schedules are maintained per state and worker category, and applied automatically by site — which matters for multi-state operations where the same trade carries different statutory rates across plants, and where a missed revision becomes an arrears liability.

Can contractors see their own payroll data?+

Contractor logins expose their own workers' verified hours, computed wages, and deduction summaries. Most billing disputes disappear at this step, because the contractor sees the same numbers before invoicing rather than arguing about them afterwards.

What happens when a worker's attendance is disputed after payroll runs?+

Every payroll line links back to its source attendance events, so a disputed entry is traced to the gate record, the shift rule applied, and any approval on file. Corrections are processed as adjustments with an audit trail, not by overwriting the original run.

How does this reduce the principal employer's statutory exposure?+

Under CLRA, contractor defaults on wages and statutory dues can fall back on the principal employer. Because Iddion RegX computes wages and deductions from your own verified attendance data, you hold independent evidence of what was owed and what was remitted — rather than relying entirely on the contractor's word.

Does it integrate with our ERP or finance system?+

Validated payroll and invoice data can flow to your finance system through the approval workflow, so verified amounts move to AP without re-keying.

Can we run payroll for multiple contractors and sites in one cycle?+

Yes — a single run covers every contractor, category, and site with their own rate structures and statutory rules applied, producing per-contractor outputs for billing and consolidated views for finance.

What audit trail does a payroll run leave?+

Each run records the attendance events used, rates applied, OT approvals referenced, deductions computed, and every subsequent adjustment with its approver and timestamp — the evidence set an inspector or internal audit actually asks for.