Final Go Live Audit

This process applies to all client implementations requiring a final pre-go-live audit.

The audit is conducted after implementation setup and configuration activities have been completed and before the client is approved to proceed with go-live.

This process does not replace initial discovery, implementation setup, or ongoing project management responsibilities.

3. ROLES & RESPONSIBILITIES

Project Manager (PM) – Audit Owner

The Project Manager is responsible for:

• Scheduling and conducting the final go-live audit.
• Reviewing all applicable implementation configurations and client information.
• Validating accuracy, completeness, and consistency across applicable modules.
• Identifying and documenting discrepancies, missing information, and required corrections.
• Providing clear instructions to the Implementation Specialist for necessary updates.
• Reviewing and validating completed corrections.
• Confirming all audit requirements have been satisfied.
• Completing the final audit sign-off.

Implementation Specialist (IS) – Correction Owner

The Implementation Specialist is responsible for:

• Reviewing the findings documented by the Project Manager.
• Completing assigned corrections and system updates.
• Communicating completed updates and any outstanding concerns to the PM.
• Documenting corrections made.
• Completing the Implementation Specialist sign-off once assigned corrections are finished.

Both the PM and IS are required to sign off on the final audit.

4. FINAL AUDIT PROCESS

Step 1: Prepare for the Final Audit

The Project Manager must confirm that implementation setup and configuration activities are sufficiently complete to begin the final audit.

The PM should have access to applicable client documentation, configuration details, employee information, and supporting implementation records.

The final audit checklist must be used to guide the review.

Step 2: Conduct the Final Audit

The Project Manager will independently review all applicable implementation areas to confirm that information is accurate, complete, and configured as intended.

The audit should include, but is not limited to:

• Company and organization setup
• Employee demographics and employee data
• Time and attendance
• Payroll configuration
• Tax setup and tax information
• Benefits and deductions
• General ledger and accounting configurations
• Jobs and department setup
• Certified payroll, when applicable
• Reporting and required configurations
• Other client-specific configurations

The PM must validate the information against available client documentation and approved implementation requirements.

Simply confirming that a configuration exists is not sufficient. The PM must review the accuracy of the configuration.

Step 3: Document Audit Findings

Any discrepancies, missing information, incorrect configurations, or required updates must be documented on the Final Go-Live Audit Checklist.

Each finding must include:

• The specific area or module where the issue was identified.
• A clear description of the issue.
• The required correction or update.

Findings must be specific enough that the Implementation Specialist can understand and complete the required correction without having to interpret or guess what needs to be changed.

The PM is responsible for maintaining the audit checklist and tracking all findings through resolution.

Step 4: Assign Corrections to the Implementation Specialist

Once the audit is completed, the PM will communicate the documented findings to the IS.

The PM must provide clear direction regarding the required corrections and expectations for completion.

The IS will review the findings and complete the applicable system updates.

If additional information, clarification, or client confirmation is needed, the IS must communicate this to the PM before proceeding with an update that could impact the accuracy of the configuration.

Step 5: Complete and Document Corrections

The Implementation Specialist will:

• Complete the assigned system updates.
• Review the changes made to ensure they address the identified issue.
• Document the correction in the audit checklist.
• Communicate completion to the PM.
• Identify any items that remain outstanding or require escalation.

An item cannot be considered fully resolved simply because an update was made. It must be reviewed and verified by the Project Manager.

Step 6: PM Verification

The Project Manager is responsible for reviewing each correction completed by the IS.

The PM must verify that:

• The requested correction was completed.
• The configuration or information is now accurate.
• The correction did not introduce another discrepancy.
• The original audit finding has been fully resolved.

The PM must update the checklist to reflect the verification status of each finding.

If a correction is incomplete or inaccurate, the PM will return the item to the IS for additional updates.

Step 7: Final Audit Approval and Sign-Off

Once all findings have been addressed and verified, the PM and IS must complete their respective sign-offs.

The final audit must confirm that:

• All applicable audit areas have been reviewed.
• All identified issues have been corrected.
• All corrections have been verified by the PM.
• No unresolved issues remain that would prevent go-live.
• Any approved exceptions have been appropriately documented.

Both the Project Manager and Implementation Specialist must sign the checklist.

The client must not be considered approved for go-live until the final audit has been completed and the required approvals obtained.

5. ISSUE PRIORITIZATION & ESCALATION

Issues identified during the final audit should be prioritized based on their potential impact on the client's ability to successfully go live.

High Priority

Issues that could result in inaccurate payroll, incorrect employee pay, tax liabilities, compliance concerns, incorrect deductions, or significant system functionality issues.

These items must be resolved before go-live.

Medium Priority

Issues that impact functionality, reporting, configurations, or the client experience but do not immediately prevent payroll processing or core system functionality.

These items should be corrected before go-live whenever possible. Any exception must be documented and approved through the appropriate process.

Low Priority

Minor issues that do not impact payroll accuracy, compliance, required functionality, or the client's ability to successfully go live.

These items should be corrected before go-live when practical or documented with an assigned resolution plan and appropriate approval.

Any issue that presents a compliance, payroll accuracy, or significant operational risk must be escalated and cannot be treated as a routine exception.

6. REQUIRED DOCUMENTATION

The completed Final Go-Live Audit Checklist must be retained with the client's implementation documentation.

The checklist must include:

• Client information and scheduled go-live date.
• Completed audit categories.
• All identified findings and required corrections.
• Implementation Specialist correction notes.
• PM verification of each correction.
• Outstanding exceptions, if applicable.
• Final PM and IS sign-offs.

7. PROCESS COMPLETION

The final go-live audit process is considered complete when the audit has been conducted, all required corrections have been addressed and verified, and both the PM and IS have completed their sign-offs.

The completed checklist serves as the official record that the final implementation audit was performed and the client was reviewed for go-live readiness.

Process Standard: No final go-live audit is considered complete without documented findings, correction tracking, PM verification, and both required sign-offs.

Issues List