Customer Scenarios
How can one finance person send payslips for several small companies?
An anonymized customer question, adapted to SugarHR’s published workflow. This is practical guidance, not a verified implementation result.
Keep each company's approved payroll identifiable, preview individual statements and verify the resulting records. A company name on a sheet does not itself create a separate workspace.
The situation
One finance person supported several small businesses and wanted to replace individual screenshots and manually collected replies.
Why this condition changes the workflow
Define whether the requirement is merely displaying the correct employer or isolating data between employers. Those are different acceptance tests. Do not combine sheets in a way that loses the payer's identity.
A practical sequence for this situation
1. Test employer identity and management scope separately. Use two representative employers to inspect statement labels, batches and administrator visibility. Record whether the requirement is identification, isolation or unified access; a spreadsheet label does not prove all three.
2. Complete calculation and approval first. Resolve hours, rates, tax and deductions in the existing authorized process. Use only the approved results for statement preparation; importing a number does not mean the delivery product calculated it.
3. Let employees review before the requested action. Explain what the statement covers and which acknowledgment is required. Keep unread, unconfirmed and queried statements distinguishable so the administrator can respond to the actual issue rather than assume every delay has one cause.
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 employer, project where relevant, period, recipient and approved version identifiable throughout the record. Test the actual account arrangement or final-settlement route, not merely a label on a sheet. Separate organizational approval, employee acknowledgment and bank payment so one successful event is not treated as proof of all three.
Questions to resolve in this context
Does a company column create separate company spaces?
No. A company label can identify the employer shown on a statement. Separate workspaces, entity switching, scoped administrators and consolidated reports are different requirements. Demonstrate the intended arrangement with representative employers rather than inferring organization features from a column in Excel. Read the general explanation.
How can finance know that an export is usable?
Download an actual test file and inspect people, periods, relevant statuses and the connection to approved figures. Ask separately about handwriting images, timestamps and required formats. Published record export does not establish that every desired field or layout is available. Read the general explanation.
Related guidance
-
Does a company name in Excel create a separate company workspace?
-
Organize approved payslip batches across companies and projects
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