What should shared finance teams check beyond the number of logins?

Specify unified viewing, entity switching, employee-facing employer labels, reporting and administrator boundaries separately.

The situation

An existing operator wanted a single entry point for several employers and did not require every entity to be isolated.

Why this condition changes the workflow

Counting accounts does not define the desired operating model. Demonstrate the actual workflow with two employers and inspect the retrieved records before assuming a company column or shared login meets every requirement.

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. Identify the responsible account and owner. Locate the authorized administrator, correct company and source batch. Verify supported handover arrangements and employee-facing identity rather than sharing personal credentials or creating an extra account to bypass confusion.

3. Retrieve and inspect a real record. Download an available test record and check the people, period and relevant acknowledgment event against the approved figures. Keep that verified relationship in the monthly archive; do not rely only on a screenshot.

4. Refresh the period's actual recipient list. Include new starters, current workers and any final settlements, and distinguish repeated sending from adding people. Confirm the account's present allowances separately from the operational list.

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 should administrator identity and account handover be separated?

Distinguish who logs in, which company appears, where employee messages originate and who owns the records. Follow the current authorized handover process and verify any sender customization. Do not share login codes or create another account merely because a batch cannot be located. 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?

• How should companies distinguish and hand over administrator access?

• What should we verify in exported payslip records?

• Organize approved payslip batches across companies and projects

• Send final pay or commission details to a former employee

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.