The ERP innovations worth paying attention to right now

Ask a finance director what their ERP system does and most will describe what it used to do: hold the ledger, run payroll, generate the month-end report nobody reads until something in it is wrong. That description is going stale fast. The systems running underneath most mid-sized and large businesses are changing shape, and the change matters well beyond the finance department. It touches headcount planning, office layout, training pipelines, and how quickly a business can respond when the market shifts under it.

Four shifts stand out this year. The first is systems that execute, not just report. The oldest complaint about enterprise software is that it tells you what already happened. You get a dashboard showing last month’s numbers, and the decision that needed making happened three weeks before the dashboard caught up.

That’s changing as vendors build AI agents directly into core workflows rather than bolting on a chatbot for asking questions. SAP has pushed hard here with its Business AI portfolio, which now spans several hundred embedded use cases across forecasting, inventory, and customer service. Priority Software has taken a similar path with its aiERP platform, embedding agents into finance, sales, and supply chain modules that can post receipts, match invoices, and generate purchase orders without a person keying each step. Gartner expects generative AI and predictive analytics to be standard in roughly four out of five ERP systems by 2028, which tells you this stopped being a novelty and became a baseline expectation.

The distinction worth holding onto: reporting software tells someone what happened. Executing software does something about it, and asks a human to sign off on the calls that matter. That’s a different relationship between a person and their system, and most job descriptions in finance and operations haven’t caught up to it yet.

Composable systems replacing the one giant platform

For years the promise of ERP was a single system doing everything, from procurement to HR to shop-floor scheduling. In practice, that single system usually meant one department’s needs winning out over everyone else’s, with the rest of the business working around a tool that fit them badly.

Composable ERP breaks that bargain apart. Instead of one monolithic platform, businesses assemble a core system for financials and identity, then plug in specialized tools for the functions that need more depth: a dedicated warehouse management system here, a purpose-built scheduling tool there, all talking to each other through open APIs rather than living inside one vendor’s walls. Two-tier ERP strategies, where a corporate parent runs one system and fast-growing subsidiaries run lighter cloud platforms underneath it, follow the same logic at a larger scale. Gartner has been advising exactly this kind of assessment for large organizations weighing whether a single-tier approach still serves them.

For a business that’s grown by acquisition or expanded into new markets quickly, this matters more than almost any other item on this list. It’s the difference between forcing every new office into last decade’s software and letting each one run what actually fits.

Industry-specific builds instead of generic ones

A food manufacturer tracking batch recipes and a pharmaceutical company managing regulatory traceability have almost nothing in common operationally, yet for years both were sold nearly identical generic ERP packages and told to customize their way to fit. That’s reversing. Vendors are increasingly building for the specific compliance and workflow demands of a sector rather than expecting every customer to bend a generic tool into shape, cutting implementation time and reducing the layer of custom code a business has to maintain and eventually replace.

The knock-on effect for workplace planning is real: a shorter implementation cycle means the disruption to how teams actually work, the retraining, the temporary dip in productivity while everyone learns a new system, shrinks too.

Real operations data, not a snapshot from last week

The fourth shift is about where the data comes from in the first place. IoT sensors on warehouse floors, shop-floor equipment, and delivery fleets are increasingly feeding straight into ERP platforms, so a stock count or a maintenance flag reflects what’s happening right now rather than what a batch upload said this morning. Paired with mobile-first design, that means a plant manager or a field engineer can see and act on live data standing on the floor, not back at a desk waiting for a report to refresh.

What this adds up to for the people running operations, not just IT

None of these four shifts sits neatly inside a technology budget line. A composable system changes how quickly a new office location can go live. An industry-specific build changes how long onboarding takes for someone joining that team. Agentic automation changes what the entry-level finance role actually consists of, and therefore what a graduate scheme should be training people to do. Real-time data flowing in from the floor changes who needs to be near that floor at all.

The businesses treating ERP selection purely as a procurement decision are missing most of the story. The systems underneath finance, supply chain, and operations are quietly rewriting what those departments look like day to day, and the workplace planning conversation is better off starting from that reality rather than discovering it after the rollout.