Most companies do not have an automation problem.
They have a prioritization problem.
Once a team starts looking at ERP automation, the list of possibilities gets long very quickly. Accounts payable. Accounts receivable. Approval routing. Reporting. Data entry. Notifications. Reconciliation. Status updates.
All of them may be manual. All of them may be frustrating.
But that does not mean all of them should be automated first.
The best ERP process automation projects usually start with a much simpler question:
Where is manual work creating the most repeatable, measurable friction right now?
That distinction matters. Automating the wrong workflow can simply make a bad process move faster. Automating the right one can remove hours of repetitive work, reduce unnecessary handoffs, improve visibility, and create a foundation for broader automation later.
So before deciding what your ERP can automate, decide what your business should automate.
A common mistake is beginning with ERP features. A team sees that the system can automatically route invoices, send reminders, generate reports, or update records, so the conversation becomes: "Which features should we turn on?"
That is backwards.
The better starting point is the current workflow. Look for processes where employees repeatedly enter the same information in multiple places, send the same follow-up emails, wait for routine approvals, export and clean the same reports, check statuses manually, move information between disconnected systems, or correct predictable errors.
Those are clues. But repetition alone is not enough.
Before automating anything, evaluate each workflow against five questions. How often does this process happen? How much employee time does it consume? How costly are errors or delays? How predictable are the rules? And what actually improves if the process becomes faster?
A task that happens twice a year is probably not your first automation priority. A task performed hundreds of times each month, with clear rules and constant follow-up, is a very different story.
Accounts payable is one of the first places many businesses should examine because it often contains exactly the kind of repetitive, rules-based work automation handles well.
Think about a typical invoice. Someone receives it. Someone enters the information. Someone checks it against another record. Someone determines who needs to approve it. Someone follows up when the approval sits unanswered. Someone updates the payment status.
Individually, none of those steps seems enormous. At scale, they add up.
If your team wants to automate accounts payable, do not start by trying to eliminate human involvement entirely. Start by removing the steps that require humans to behave like software. That may include capturing invoice information, matching invoices to purchase orders or records, routing invoices based on amount, department, or vendor, sending approval reminders, escalating overdue approvals, updating ERP statuses, and preparing approved invoices for the next payment step.
People should still handle exceptions, unusual invoices, disputes, and judgment calls. The goal is not "no humans." The goal is fewer humans spending time on predictable administrative work.
Accounts payable becomes a strong first candidate when invoice volume is growing, approvals regularly stall, duplicate entry is common, or finance employees spend a noticeable part of their week chasing routine transactions. If your AP process is already clean, fast, and low effort, another workflow may deserve priority. That is the point of prioritization.
Key Code Media shows what happens when repetitive administrative work starts consuming time that could be spent on higher-value analysis. Before moving to Acumatica, the company relied on separate systems for accounting, CRM, and project tracking, with manual data exports and imports slowing reporting and decision-making. Timecards and expenses also required manual entry. After consolidating those processes in Acumatica, employees could work from one connected system, timecards and expenses flowed directly into the ERP, and paperless workflows and digital invoicing reduced administrative overhead. The result was not removing people from the process. It was giving them less data entry to manage and more useful work to focus on. Read the full Key Code Media (Burbank, CA) story
Accounts receivable creates a different kind of friction. Instead of invoices entering the company, money needs to move in the other direction.
Manual AR processes can involve invoice generation, reminder emails, payment status checks, collection follow-up, cash application, and exception handling. Again, the question is not whether these activities can be automated. It is which parts should be.
Routine reminders are a good example. If the same reminder is sent under the same conditions every month, there is little value in requiring an employee to remember and send it manually. The same principle can apply to invoice creation, scheduled notifications, status changes, and payment matching when the rules are clear.
But AR also contains moments where context matters. A strategic customer with an unusual payment issue probably should not receive the exact same treatment as a routine overdue account.
Good automation removes repetitive follow-up while leaving room for human judgment where the relationship matters. That balance is important across all ERP workflow automation.
Some manual processes are not difficult. They are just slow because they depend on people noticing things.
An employee submits a request. It lands in someone's inbox. The approver is busy. Three days later, somebody asks for an update. Then another person realizes a second approval was required.
Nothing about the work itself was complicated. The workflow was simply unclear.
Approval automation can solve this remarkably well when the organization has defined rules. Requests below a certain threshold go to one manager. Larger requests require additional approval. Certain categories route to specific departments. Unanswered approvals trigger reminders after a defined period. High-priority requests escalate automatically. And approved transactions move to the next stage without anyone needing to manually push them forward.
This is where automation becomes more than a time saver. It creates consistency.
But there is a warning here: do not automate an approval process nobody fully understands. If employees cannot agree on who should approve what, automation will not solve the confusion. It will encode it.
Standardize first. Automate second.
Reporting often feels like the obvious automation target. Every week or month, someone exports data, merges spreadsheets, fixes formatting, reconciles numbers, and rebuilds essentially the same report. That is painful. And yes, much of it may be automated.
But reporting has a trap.
Sometimes the reporting process is manual because the underlying data is inconsistent. If information is being entered differently across teams, stored in multiple systems, or updated late, automatically generating the report does not solve the real problem. You simply get a bad report faster.
Before automating reporting, ask where the information originates, whether the data is consistently structured, whether employees are maintaining separate versions, whether the ERP contains everything the report requires, and which reconciliation steps are necessary and why.
Sometimes the correct automation project is not the dashboard. It is the workflow feeding the dashboard.
Fabuwood Cabinetry is a strong example of why reporting problems often have to be solved upstream. As the company grew, its legacy systems left manufacturing, inventory, and finance data siloed. Reporting required complex coding and manual reconciliation, while data mismatches delayed both forecasting and decision-making. Moving to Acumatica unified those workflows and connected more than 15 third-party applications, creating a single source of truth with clean, real-time data. Once the underlying information became reliable, employees could access KPIs and build reports without depending on developers. The reporting improvement started by fixing the data feeding the reports, not simply automating the final dashboard. Read the full Fabuwood Cabinetry Corp story
If AP, AR, approvals, and reporting all need work, score each process across four areas.
Volume. How frequently does the process occur? Higher volume generally increases the value of removing repetitive work.
Friction. How many manual touches, follow-ups, exports, corrections, or handoffs are involved? More friction usually means more opportunity.
Risk. What happens when the process goes wrong? Consider payment mistakes, missed approvals, collection delays, reporting inaccuracies, or weak internal controls.
Automation readiness. Can the process be explained with reasonably consistent rules? This is critical. A messy but highly repetitive process may look like an ideal target until you discover that every employee handles it differently. That workflow needs stabilization before automation.
The best first project is usually a process with high volume, high friction, meaningful business impact, and clear rules.
A practical ERP automation roadmap can be broken into three stages.
Phase 1: Stabilize. Document the process. Remove unnecessary steps. Define ownership. Identify exceptions. Clean up the rules. This phase may feel less exciting than automation, but it prevents you from building technology around broken workflows.
Phase 2: Catalyze. Now automate the predictable pieces. Routing. Matching. Notifications. Reminders. Scheduled reports. Status updates. Repetitive data movement. Keep humans focused on exceptions and decisions.
Phase 3: Maximize. Once the first workflows are stable and producing value, look for broader opportunities. You may connect processes across departments, build custom integrations, introduce more sophisticated exception handling, or automate workflows your ERP cannot support out of the box. At this point, automation becomes less about isolated tasks and more about how information moves through the business.
Do not judge success by how many workflows you automate. Measure what changed.
Depending on the process, that might include processing time, approval turnaround, manual touches per transaction, error or exception rates, reporting preparation time, employee hours spent on repetitive work, or collection and payment cycle time.
If the automation does not improve something the business actually cares about, adding more automation will not fix the problem.
ERP automation does not need to begin with an enormous transformation project.
Often, the strongest starting point is much less dramatic. One approval process that no longer needs chasing. One AP workflow with fewer manual touches. One AR process that follows up automatically. One report that no longer takes half a day to rebuild.
Find the repeated friction. Make the process clear. Automate the predictable work. Measure the result. Then move to the next bottleneck.
That is how ERP process automation becomes more than another technology initiative. It becomes a practical way to give your team back time, improve operational consistency, and build better systems as the business grows.
If you are not sure which workflow should come first, a Catalyst360 Discovery Session helps you map your AP, AR, approval, and reporting processes exactly as they operate today. The places with the most repeated handoffs, delays, manual entry, and predictable rules will tell you where the opportunity is.
No pressure to automate everything at once. Just clarity on where to start.
Schedule Your Discovery Session →
See how Acumatica supports workflow automation →