AccountantsWorld documents importing employee and prior-period payroll information in Excel format as part of Payroll Relief’s conversion capabilities. That supports asking about an import; it does not establish that every record in a previous platform will transfer automatically. A migration plan should define the records, balances, and responsibilities that must be accepted before the first live payroll. Source: official workflow documentation.
The framework below is a proposed acceptance process for an accounting firm. Obtain the current import specification and assistance scope directly from the provider before preparing production data.
Specify the boundary in dates and responsibilities
Choose the last payroll handled under the old arrangement and the first intended live payroll in the new one. Record the pay period and the pay date so everyone is describing the same transaction. Then identify who handles corrections discovered after that boundary.
For a conversion during a reporting period, ask the old provider, new provider, and responsible payroll professional to agree which records and period totals each needs. Importing history does not establish who is responsible for preparing, filing, or correcting a return.
Have the responsible parties document the arrangement for each relevant filing obligation. “We handle year-end” is less useful than an agreement identifying the employer, period, form, data source, and accountable party. The tax monitoring guide explains how to preserve ownership after conversion.
Separate operational data from historical access
Identify what the new process must use to calculate and report correctly, what staff must be able to consult, and what should remain in an authorized archive. Ask the provider which requirements its conversion service covers.
A prior pay statement and a current deduction setting serve different purposes. Keeping the former accessible does not establish that the latter was recreated correctly. Importing a current setting likewise does not prove that historical supporting documents will be available to staff or employees.
Create an inventory organized by purpose. Assign an owner to each category and state how it will be checked. Keep production files within the approved transfer route agreed with the relevant providers; the inventory can describe categories without exposing employee details.
Agree on the source of truth
Choose the source records against which the new setup will be reconciled. Resolve contradictions in those records first, or explicitly retain them as open issues. If two old-system reports disagree, importing one successfully cannot resolve the underlying difference.
The proposed checks below describe evidence to request. They do not claim that Payroll Relief supplies a particular conversion report for every item.
| Area | Proposed acceptance evidence | Question raised by a mismatch |
|---|---|---|
| Employee population | Agreed population compared with received data | Was a record excluded, duplicated, or intentionally archived? |
| Pay and deduction setup | Representative records checked against approved instructions | Does the new setting reflect the intended current instruction? |
| Prior-period totals | Reconciliation at the levels required by the payroll professional | Is the difference a mapping issue, source error, or omitted event? |
| Accounting allocation | Sample output compared with accounting requirements | Does the problem concern conversion or regular export mapping? |
| Historical documents | Demonstrated access through the agreed destination | Who can retrieve documents after old access ends? |
Do not clear a mismatch simply because it is small. Determine its cause and whether it affects another record, period, or calculation. Acceptance should belong to the person responsible for that part of the payroll, with the reason documented.
Review a representative cycle before live processing
Ask the provider how a comparison can be performed without initiating live funds movement or duplicate filing. Use its approved method and confirm the limits. Public feature descriptions are insufficient to invent a safe testing sequence.
Select representative conditions from the client, including an ordinary employee and any material exception affecting the first cycle. Determine whether the team can produce and explain the expected result. A totals-only comparison can conceal offsetting differences, so agree on appropriate record-level checks.
Keep operational readiness separate from data readiness. Staff need appropriate access, the client needs submission instructions, and the escalation route needs to work. Imported records are only one part of the first payroll’s preparation.
Set an explicit go-live decision
Prepare a short decision record identifying accepted areas, unresolved differences, and the person authorized to approve the transition. Unexplained material balances, unresolved payment instructions, or unclear filing ownership require resolution before the related live action.
Also agree what happens if the launch is postponed. Confirm whether the existing provider can continue another cycle and what notice it requires. Do not assume a fallback remains available after termination; the actual service terms determine the options.
A target date is useful for organizing work, but it should not silently become acceptance of unresolved problems. If the date moves, update the data boundary and recheck any information that changed in the meantime.
Close the conversion with evidence
After the first live cycle, reconcile the outputs and retain the acceptance record. Identify remaining historical-access work separately from anything that affects ongoing calculation or reporting.
Recurring exchange with accounting belongs in the integration workflow. Routine approval belongs in the payroll review process. A conversion is accepted when the agreed evidence has been reviewed and remaining work has an owner, rather than when an upload reports success.