An accounting software update checklist helps a CPA firm prepare for changes to QuickBooks, Sage, Windows, or a server before those changes interrupt accounting work. The important steps are broader than installing a patch: confirm compatibility, protect the right data, choose a workable time, and test the workflows staff rely on.
Start by identifying what is changing. A routine security patch, an accounting application update, and a major operating system or server upgrade may carry different compatibility and recovery considerations. Avoid treating them as interchangeable, and follow the relevant vendor guidance for the exact product and environment.
Before the update: define the change
Write down the software and systems involved, including the product edition and release, Windows version, server role, and whether the application uses a shared company file or multi-user configuration. Note connected services and devices too, such as integrations, printers, remote access, or other tools used for bookkeeping and reporting.
Check the vendor's system requirements and update instructions for the exact version you plan to install. For example, Sage publishes requirements for its U.S. edition; compare the applicable details with your own environment rather than relying on general assumptions. Review Sage 50 system requirements before proceeding.
For Windows or server changes, review deployment guidance and confirm that the planned update fits the server's role and the firm's setup. Microsoft provides preparation guidance for deploying Windows. If a vendor requirement or dependency is unclear, resolve it before scheduling the update.
Protect data and confirm recovery options
Identify all data and settings that may need protection before the change. Depending on the system, that can include the accounting company file, related attachments or exports, application settings, and other files or services needed to resume normal work. Confirm where each backup is stored and who can access it.
- Confirm that the backup completed successfully and covers the data involved in the update.
- Check that the backup is stored separately from the system being changed, where the firm's backup approach supports that.
- Verify that authorized staff can access the backup and understand the recovery process.
- Test a restore to a separate location or suitable test environment when possible, and check that the restored data can be opened and used.
- Document who will coordinate recovery if the update fails or the application behaves unexpectedly.
A completed backup is not the same as a confirmed recovery plan. The firm should know what will be restored, who can perform the work, and how staff will access the system while recovery is underway. For more detail on planning and verifying recovery, see financial data backup considerations.
Plan the window and communicate it
Choose a time when the affected system can be taken out of use without colliding with critical work. Consider payroll processing, month-end close, filing deadlines, client deliverables, and other busy periods. A technically convenient maintenance window is not a good choice if staff need the accounting system during it.
Before work begins, tell affected users what will change, when access may be unavailable, and when they should sign out or stop entering data. For shared accounting software, confirm that users are signed out when required by the vendor's instructions. Assign an update owner and a separate person, when practical, to verify the accounting tasks afterward.
Use a written change plan that records the intended update, the systems affected, the planned sequence, the backup and recovery steps, and the people responsible for approval and testing. CISA's patch management recommendations can help inform a repeatable approach to planning and managing patches.
Decide the order for shared systems
There is no single installation order that fits every QuickBooks, Sage, Windows, or server configuration. The appropriate sequence depends on the product's instructions, the firm's setup, and the dependencies between its server and workstations. Check vendor guidance before changing a shared environment, and do not assume that updating one workstation completes the update for everyone.
Record which systems or workstations are included and confirm that any required client components, services, or access settings are addressed. If staff use QuickBooks Desktop in multi-user mode, test the shared workflow after the change, not just whether the program opens on one computer. If users are already experiencing slow shared access, review common QuickBooks multi-user performance checks as a separate troubleshooting step.
Test the work staff actually do
After the update, validate the system in a planned way before considering the change complete. Use an appropriate test company file or other safe test method when available, and avoid making unnecessary changes to live accounting records during acceptance checks.
- Confirm that the application opens and the intended company file is accessible.
- Test access from more than one workstation if staff share the application or data.
- Verify that expected user permissions and multi-user access work.
- Check routine tasks such as opening records, entering a test transaction where appropriate, and viewing or producing a report.
- Confirm that relevant integrations, printing, remote access, and related services still work.
- Ask the designated reviewer to confirm that key workflows behave as expected before normal work resumes.
For firms that depend on connected applications, include those connections in the acceptance test. A successful update to one program does not by itself confirm that related data flows are working. See what to check when QuickBooks and Sage integrations stop syncing.
Keep a record and define a stop point
Document what was updated, when the work took place, who approved it, and what was tested. Record any issues and how they were resolved. This gives the firm a useful operational record and makes it easier to review what happened if a later problem appears.
Agree in advance on conditions that mean the change should pause or be rolled back, such as failed access, unexpected data behavior, or a broken critical workflow. The recovery decision should follow the product's instructions and the firm's documented plan. If the issue cannot be resolved within the planned window, communicate the status and next steps to affected staff rather than allowing uncertainty about whether the system is ready.
Frequently asked questions
What should a CPA firm check before updating QuickBooks Desktop?
Confirm the product edition and release, the Windows environment, and any shared-file or multi-user dependencies. Review the update instructions, protect and verify the company file backup, plan for users to sign out if required, and test access and routine tasks after the change.
Should accounting software updates be installed on the server or workstations first?
Follow the instructions for the specific product and configuration. The right order can depend on how the server and workstations are set up, so do not assume a universal sequence. Record the plan and test shared access after all required components are updated.
How can we test whether a backup is usable?
Where possible, restore it to a separate location or suitable test environment, then confirm that the restored data opens and can support the tasks the firm needs. Also verify that staff with recovery responsibilities can access the backup and know the restoration process.
When is the safest time to update shared accounting software?
Choose a period when the system can be unavailable without interfering with payroll, close activities, filing deadlines, or other essential work. Tell affected users about the window and allow time for testing and recovery if the change does not go as planned.
Make updates a planned maintenance task
A careful update process combines compatibility checks, verified recovery options, sensible scheduling, and workflow testing. Zevonix supports financial firms with financial software support, 24/7 monitoring, and remote and onsite support. If you want help preparing an update plan for your firm, contact Zevonix at (904) 658-0777.