A Spreadsheet Can Be a Workflow, Not a Workaround
Some employers assume that if payroll software exists, every person involved must type directly into it.
Payroll Relief explicitly supports another model.
Current IRIS documentation describes an Upload mode for payroll data stored in Excel. It identifies the option as useful for employers with large payrolls or employers that do not have direct access to Payroll Relief.
The broader Payroll Processing documentation describes a workflow in which Payroll Relief generates a file containing default payroll data, the employer edits it and the completed worksheet is returned for upload and continued processing.
That can work extremely well.
It can also create spectacular confusion if nobody knows which spreadsheet is final.
Establish one source file
The payroll file should have one clear owner.
Avoid:
Payroll_Final.xlsx
Payroll_Final2.xlsx
Payroll_Final_JaneEdits.xlsx
Payroll_REAL_FINAL.xlsx
That naming convention is a symptom that several people are editing different versions.
A better internal process assigns:
- one payroll-period identifier;
- one working file;
- one responsible coordinator;
- one submission status.
Lock the business facts before sending
Before the payroll worksheet leaves the employer, confirm:
- employee population;
- regular hours;
- overtime;
- PTO;
- bonuses;
- commissions;
- reimbursements;
- one-time deductions;
- employees who should receive no check.
If managers are still changing hours while the file is being sent to the accountant, the problem is not Excel.
It is the absence of an internal cutoff.
Separate employee setup from payroll input
A payroll spreadsheet can communicate current-period amounts.
It should not become the only record of an employee change that also requires underlying setup to change.
For example:
“John gets a $500 bonus this payroll.”
is a payroll-period input.
“John’s regular annual salary changed permanently.”
may also require employee setup to be updated.
Payroll Relief’s processing documentation says changes to employee salary, deductions and tax setup can be made before payroll is recalculated.
The employer-accountant handoff should therefore distinguish:
this-payroll-only changes
from:
permanent setup changes.
Use a change log
A small notes section can prevent a large amount of confusion.
Record items such as:
- new hire;
- terminated worker;
- one-time bonus;
- salary change;
- deduction change;
- direct-deposit change submitted separately;
- employee intentionally skipped;
- department/location change.
This helps the reviewer understand why the payroll differs from the previous period.
Review the imported result, not just the spreadsheet
The spreadsheet is input.
The calculated payroll is output.
Payroll Relief’s review process provides summary, employee details and comparison reporting after payroll calculation.
The employer should therefore verify the calculated payroll even if the spreadsheet was meticulously prepared.
A perfect spreadsheet can still expose a setup issue after the application processes it.
Treat import errors as data problems first
Payroll systems tend to be strict about file structure.
IRIS publishes detailed employee import specifications including expected headers and accepted values for certain fields.
If an import behaves unexpectedly:
- confirm the correct template;
- check columns and headers;
- verify expected data formats;
- check whether formulas or formatting altered values;
- compare the imported result with the source file.
Do not repeatedly upload altered files without knowing which difference you are testing.
Spreadsheets work best when they reduce access complexity
The Excel workflow can be especially attractive when the employer wants managers to supply payroll data without giving those managers direct payroll-system access.
Managers can contribute business facts.
One coordinator can consolidate the information.
The payroll professional can work inside Payroll Relief.
That creates a simple division:
many people produce payroll inputs; very few people operate payroll software.
For many small employers, that is a feature rather than a limitation.