Customer Scenarios

What should we check when uploaded employee details do not match?

An anonymized customer question, adapted to SugarHR’s published workflow. This is practical guidance, not a verified implementation result.

Use a one-person sample to check the header, employee identity, recipient address and active account. Recheck the preview after correcting the source information.

The situation

A business wanted to retain its own payroll columns, but a trial was blocked by conflicting employee details.

Why this condition changes the workflow

Rebuilding the whole workbook is not the first diagnostic step. Preserve its real structure while isolating the failing row, and distinguish a parsing problem from a previous employee-to-address association.

A practical sequence for this situation

1. Isolate a recognizable data structure. Keep the employee header and data separate from summary and approval regions. Test one or two rows that preserve the genuine columns, then compare the recognized fields and important amounts with the source.

2. Validate identity and recipient mapping. Inspect employee identifiers and personal addresses, including same-name people, changed contacts and unsettled leavers. Compare the preview with the approved source before the file becomes a live delivery batch.

3. Correct the identified record. Find the affected employee and original batch, check its acknowledgment state and use the supported correction process. Preview the approved replacement and preserve the link between old and revised information.

4. Check what employees should see. List essential pay explanations and internal-only fields. Preview different roles, names and zero-value items against that list, and verify any needed presentation setting in the current account.

What a useful test should demonstrate

Keep the approved sample version, the recipient comparison and the checked personal previews together. A useful result shows which real columns were recognized, what employees saw and which anomalies were corrected. A clean upload alone is insufficient if identity, zero items or internal fields still fail the stated requirement.

Questions to resolve in this context

How should an existing Excel file be prepared?

Use approved figures and a recognizable header and employee-data region. Check identifiers, periods and recipient addresses, keeping totals and sign-off areas distinguishable. A small structural sample helps diagnose parsing without unnecessarily rebuilding a workbook that supports the existing calculation process. Read the general explanation.

How can we reduce mismatches between people and addresses?

Check a reliable employee identifier alongside the person's reachable address. Include same-name workers, changed contacts, new starters and former staff awaiting settlement. Successful upload is not evidence that every source association is correct; compare representative personal previews before release. Read the general explanation.

How should an incorrect amount, recipient or version be corrected?

Identify the affected employee and original batch, then check its current state. Use the supported void, recall or correction process, preview the approved replacement and retain its relationship to the original. Verify restrictions for acknowledged records instead of promising an invisible rollback. Read the general explanation.

Related guidance

Test the conditions that matter to your team

Use a sample or anonymized approved file to check the specific conditions described here. Confirm any unverified account, channel or record requirement before a live send. Start Your Free 1-Month Trial.

Published by SugarHR Help Center. How we review guidance.

Start Your Free 1-Month Trial