Why AP processes become inconsistent across business units
Founder of The Write Creative, contributing author for Medius
Hear what's covered in this article:
AP processes become inconsistent across business units because organizations grow faster than their processes evolve. New business units, acquisitions, ERP systems, and local requirements often lead teams to develop their own ways of handling invoices, approvals, suppliers, and exceptions.
While these decisions may solve short-term operational needs, they gradually create process variation across the organization. As a result, shared services leaders often struggle with limited visibility, inconsistent controls, and difficulty measuring AP performance across entities.
Understanding how this variation develops is the first step toward building a more standardized and scalable AP operating model.
Growth creates process variation
Most organizations do not intentionally create fragmented AP processes.
In the early stages of growth, local teams often have the flexibility to develop procedures that work best for their business unit. A regional office may create a unique approval workflow. A department may establish its own supplier onboarding process. Another team may develop spreadsheets to manage invoice exceptions.
Individually, these decisions seem reasonable. Collectively, they create a patchwork of processes that becomes increasingly difficult to manage.
As invoice volumes increase and organizations add new entities, these small differences can lead to significant inefficiencies.
What was once a manageable local process becomes a barrier to visibility and consistency across the enterprise.
Acquisitions introduce new ways of working
Acquisitions are one of the most common sources of AP process variation.
Every acquired company brings its own systems, approval structures, supplier relationships, and operational habits. While finance leaders often focus on integrating financial data, operational processes may remain largely unchanged for months or even years.
As a result, organizations frequently inherit multiple versions of the same AP process.
One business unit may require three approvals for a non-PO invoice. Another may require only one. Supplier onboarding requirements may differ significantly between entities. Reporting structures often vary as well.
Over time, these inherited differences make it more difficult to establish consistent governance and reporting across the organization.
Multiple ERPs reduce visibility
ERP fragmentation creates another challenge for shared services teams.
Organizations often operate multiple ERP systems because of acquisitions, regional requirements, or historical technology decisions. While each system may support AP operations effectively on its own, managing accounts payable across several ERP environments can make standardization more difficult.
Different systems may support different approval workflows, reporting structures, supplier records, and coding practices.
As a result, shared services leaders may struggle to answer basic operational questions:
Which business unit has the highest exception rate?
Where are invoice approvals getting delayed?
Which entities process invoices most efficiently?
Without a consistent view of AP activity across systems, identifying opportunities for improvement becomes much more difficult.
Exceptions create process drift
One of the biggest contributors to AP inconsistency is exception handling.
Many organizations successfully document standard invoice workflows but manage exceptions through entirely different processes.
Supplier inquiries, coding questions, disputed invoices, missing purchase orders, and approval issues often move into email, spreadsheets, and informal conversations.
When this happens, the organization effectively operates two AP processes: the documented process and the process used to resolve exceptions.
Over time, exception handling becomes a source of process drift, reducing visibility and creating challenges for governance and reporting.
Why inconsistency becomes a shared services challenge
Process variation may seem manageable when viewed at the level of individual business units.
The challenge emerges when shared services teams attempt to manage AP performance across the entire organization.
Inconsistent workflows make reporting more difficult. Different approval structures create uneven cycle times. Supplier management practices vary between entities. Exceptions are handled differently depending on the team involved.
These differences make it harder to compare performance, enforce controls, and identify opportunities for improvement.
As organizations continue to grow, the cost of inconsistency increases.
How Medius helps shared services teams drive AP standardization
Organizations cannot standardize AP without visibility into where process variation exists.
Medius helps shared services teams bring invoice processing, approvals, exception management, and reporting into a centralized environment across business units and ERP systems. This creates greater consistency, governance, and visibility while supporting the flexibility needed for local requirements.
Learn more about how shared services teams can standardize AP processes across multiple business units.
Frequently asked questions
Business units often develop their own workflows, approval structures, supplier management practices, and exception handling procedures as organizations grow.
Acquisitions introduce new systems, workflows, approval processes, and supplier data that can increase process variation across the organization.
Exceptions frequently move outside standard workflows into email and spreadsheets, making them harder to track and govern.
Different ERP systems often support different workflows and reporting structures, making it more difficult to maintain consistent AP processes.
Visibility becomes difficult when business units operate different processes, systems, and reporting methods across the organization.
