The Top 6 Accounting Software Implementation Mistakes Clients Make
Posted on Jun 8, 2021 9:00:00 AM by Rebecca Hurst
Congratulations! Your team has chosen a new accounting software to implement. You are looking forward to improved processes and a user-friendly interface. But how do you ensure that the implementation goes off without a hitch?
Wipfli’s technology consulting team assists clients with their software implementations by helping them identify opportunities for improvement, minimize and mitigate risk, configure data maps, and implement a fully operational system that simplifies processes by providing accurate financial information to investors, leadership, and other stakeholders. While we have helped our clients achieve these goals, we’ve noted these top six implementation mistakes that clients make and how to avoid them.
1. Spending too little time defining requirements
Many clients start an implementation thinking they know what they want out of a new accounting software system. But once discovery sessions start with their implementation consultants, they often find there are other ways to complete accounting activities. Though it may take some extra time at the beginning of the project, it is important to explore the different functionality offered to you by your new accounting software system to ensure you are implementing the most effective processes for your organization.
2. Excluding users and key stakeholders
Too often we finish an accounting software implementation and find out that there are users in the system that we didn’t know about. Unfortunately, these users could have provided key information that positively affected the software configuration and business process workflows, and they could have benefitted from formal training by an experienced professional.
3. Underestimating time to complete implementation
Wipfli’s technology consulting team completes accounting software implementations all day long. However, we understand that is not your full-time job and you are juggling a million other tasks from approving AP payments to finishing up the quarterly forecast. Though implementing an accounting software may not seem like a heavy lift over a long period of time, we often estimate that your time investment in the implementation will be just as much, if not more, than ours. Time spent defining requirements, extracting and translating data into import templates, participating in training, and testing out the accounting software before go-live can quickly add to your plate.
4. Recreating your old accounting software system
One of the most detrimental phrases to your organization’s growth and success is “We’ve always done it this way”, and it’s a phrase we hear often during accounting software implementations. There’s no point in investing in a new system if it provides the same processes and results, right?!
5. Spending too little time training and testing
It’s been proven time and again through Wipfli’s accounting software implementations that there is a
direct correlation between time spent training and testing in the software and the success of the accounting team after go-live.
6. No investment in buy-in/change management
Even before the software implementation begins, your employees know a change is coming. Managing expectations and generating buy-in from all users and key stakeholders involved in the accounting software implementation will minimize unnecessary delays throughout the project.
Do you want to dive deeper into each of these mistakes and learn how to avoid them? Attend the Wipfli/Urban Hub Coffee Chat on Tuesday, July 20; register for FREE at https://events.greatergbc.org/sbaweb/events/events.asp?details=true&cale_id=2454&month=7/1/2021
Blog submitted by: Rebecca Hurst, a licensed CPA and manager with Wipfli’s technology consulting practice. Her experience at Wipfli product implementations and project management for clients in a variety of industries including nonprofit, health care, and technology. She enjoys assisting her clients with industry best practices, process improvements, and reporting requirements.