I once sat in on a call with a group of accountants spread across multiple business units of the same company. They had been live on their ERP for nearly two years. The system was running, the books were closing, and the team trusted the data. That’s a real positive, especially for a lean organization
But as the conversation went on, patterns started to emerge. Every person on the call was manually journaling prepaid expenses each month and tracking amortization schedules in Excel. Recurring vendor invoices were being re-entered from scratch every month because nobody had been introduced to recurring purchase lines. The system had the functionality. The team just never got to it.
That moment captured something that surfaces again and again in post-go-live environments. The system is working. The team trusts the numbers. But a very lean staff is spending time on manual work that the system could handle for them.
This isn’t a failure. It’s a natural consequence of implementation prioritization. Go-live is overwhelming, and the capabilities that didn’t make the initial cut simply never get revisited. The risk is manual entry errors and spreadsheets that fall out of sync with the system. And the longer it goes unchecked, the more likely leadership starts asking “are we paying for more than we’re using?” while users wonder “how did this new system make my job any easier?”
What Emerges Over Time
That call wasn’t unusual. When a support partner steps into a post-go-live environment, the same themes surface repeatedly. The specifics vary, but the categories are remarkably consistent.
Configuration that hasn’t kept up with the business.
At go-live, every setting is intentional. Then the business evolves: new product lines, new channels, maybe an acquisition. But the configuration stays frozen. Posting groups don’t get updated. Subledgers fall out of step with the general ledger. Often, the people who made the original design decisions are no longer around, and nobody documented what was left to revisit after go-live. The fix is usually a focused review, not a reimplementation. But nobody thinks to ask.
Features already in the platform but never adopted.
Built-in bank reconciliation, dimensional reporting, assembly management, cash flow forecasting: capabilities that exist, sitting dormant while teams default to manual processes and Excel exports. The features didn’t fail. They just never made it past go-live.
Workarounds that have become invisible.
Every ERP environment has workarounds. The problem is when they’re so embedded that nobody recognizes them anymore. Duplicate data entry across the ERP and a parallel spreadsheet. “That one person” who knows the secret sequence of steps to make month-end close actually work. The job isn’t to judge the workarounds. It’s to trace them back to root causes and find out whether the system can handle the task they were built to cover.
Training gaps that compound silently.
Go-live training is designed for the team that exists on day one. But teams turn over, and new hires almost always learn from coworkers rather than structured materials. Over time, the process in practice quietly diverges from the process as designed. The symptoms are predictable: posting errors, reports nobody trusts, and a growing reliance on institutional knowledge.
Integrations nobody is monitoring.
Integrations are easy to forget about because when they work, they’re invisible. But sync jobs fail silently, API endpoints get deprecated, and data drifts out of alignment between systems without anyone noticing. They’re the most fragile layer of any ERP environment, and the least monitored.
Where to Start
If any of this sounds familiar, it starts with a gut check:
- Talk to your users. Ask one question: does this work the way you need it to, or are you working around it?
- Revisit what was deprioritized. What didn’t make the cut at go-live? Is it still sitting on a list somewhere?
- Find out what you already own. Reporting tools, automation features, workflow capabilities: they may already be in your platform.
That will surface the symptoms. A support partner can help you get to the root causes: trace a workaround back to a misconfiguration, separate quick wins from deeper investments, and build the recurring review rhythm that keeps the system aligned with how the business actually operates today.
Implementation is chapter one. The companies that get the most from their ERP investment are the ones that treat what comes after as its own phase. If it’s been more than a year since your go-live and nobody has looked under the hood, it might be time.
