When setting a go-live date for a
The next best go-live date is the beginning of a tax quarter. This allows for the current year-to-date data to be migrated at the quarterly summary level and quarterly tax reporting (941 reports) for the just ended quarter can be handled in the legacy system. The volume of migration data which requires cleansing and validation is significantly smaller than if you go-live mid quarter, again reducing the cost to implement.
Sometimes, however, it is impossible to avoid a go-live date which does not fall on the beginning of a tax year or quarter end date. Perhaps the legacy system is malfunctioning and support is not available. In this case, you must be prepared for the extra work and cost associated with migrating and validating period by period employee data. We recommend a mid-year, mid-quarter go-live be avoided if possible.
The bottom line: set a conservative go-live date and manage aggressively to meet that date. Remember payroll mistakes are costly in terms of employee confidence and moral, and possibly even in financial liability. Do not go-live before you are sure you have it right. If you have multiple facilities, consider a phased implementation schedule. Work with your
RSM McGladrey is a
By: David Funk, RSM McGladrey – Microsoft Dynamics ERP Certified Partner in New York