Modernizing Accounts Payable in SAP: Start With What Your Team Absorbs
Modernize SAP accounts payable by reducing exceptions, improving supplier collaboration, and using automation and AI to drive efficiency.
Accounts payable is the last place an error surfaces. The purchase order nobody raised, the contract nobody loaded, the goods receipt nobody posted, the supplier invoicing the wrong entity: none of it starts in AP and all of it ends there.
The team absorbs it. Over time the absorbing becomes the job, and nobody outside AP notices, because the invoices still get paid.
That is why AP modernization keeps coming back onto the agenda. Cost per invoice is the number on the slide. What restarts the conversation is the volume of work the team carries that nobody designed for them to carry.
SAP finance organizations come at this from different places. Some automated invoice processing years ago and have watched the gains flatten. Others still key invoices by hand. The prompt is usually external: an ERP move, an e-invoicing mandate, a question from the CFO about AI. Either way the question is the same. What would actually be different?
01
Where the Day Actually Goes
Before deciding what to change, be specific about where AP time goes. In most organizations it concentrates in four places.
→Supplier inquiries. Calls and emails asking where an invoice is, nearly all of which a visible status would have answered.
→Chasing approvers. Invoices that are not in dispute, sitting with someone who is travelling, has changed roles, or was never the right approver.
→Exception rework. The same categories of break every month, handled by the people who know the workaround rather than fixed at the source.
→Period end. Working out what arrived, what did not, and what the accrual should be, under time pressure.
An automation rate measures none of this well. Two organizations reporting the same number can have entirely different problems behind it. Ask an AP team where the week went, though, and you will get these four in roughly this order, without prompting.
They are also the test of a modernization program. If the four look the same afterwards, the program did not land, whatever the dashboard says.
02
What Changes When It Works
A modernized AP process looks unremarkable from the outside.
Every invoice, from every channel and every entity, lands in one worklist with a status anyone can see, which removes inquiry volume instead of answering it faster. Approvals reach people where they already work and escalate on a rule rather than a phone call. Exceptions route by category, and every category has an owner accountable for making it smaller. At cutoff, what has arrived is known, so the accrual rests on better information and fewer assumptions
Most of the distance between those two states is design work rather than software: which exception categories you intend to retire, which master data you intend to correct, and what you are prepared to require of suppliers. Write that down and you have the specification the platform gets built to.
03
The Supplier Side of the Problem
Two of the four costs start outside the building. Supplier inquiries, and much of the exception rework, trace back to how invoices arrive and what they contain when they do.
E-invoicing is forcing the issue. Mandates land country by country on fixed dates, each with its own format and clearance rules, so a multinational is managing a rolling schedule rather than a deadline. Handled as compliance, it leaves a set of point integrations to maintain. Handled as part of AP modernization, it fixes the input, because a structured invoice that arrives carrying the purchase order reference, the tax treatment and the line detail is less likely to become an exception.
Supplier collaboration is the other half. Connecting suppliers through SAP Business Network turns the exchange from documents in a mailbox into transactions against a shared record. Suppliers check order, receipt and payment status themselves, and invoices can be validated against the purchase order before submission, so a mismatch is the supplier's to correct at creation. Coverage is what makes this pay, so sequence it by spend and by inquiry volume.
04
The Platform Comes Second
It still matters. It sets the ceiling on what the process can become, and SAP customers have two well-supported routes to it.
SAP Ariba Invoicing, which many teams still know as Central Invoice Management, is SAP's cloud invoice solution. It runs as a service on SAP Business Technology Platform, brings invoices from every channel (supplier email, PDF, Peppol, SAP Business Network) onto a single worklist with a shared status view, and has AI-based capture built in. It connects to SAP S/4HANA Cloud public and private editions, to SAP S/4HANA 2022 and later, and to ECC, so for most estates it does not have to wait behind an ERP program.
OpenText Vendor Invoice Management, sold through SAP as a solution extension, runs inside the SAP system itself. It is built for complexity, and it holds up in the environments that have the most of it: many company codes, heavy three-way matching, layered approval hierarchies, country-specific tax and compliance handling. Current releases carry strong embedded AI for capture, data enrichment and exception handling, with Content Aviator answering natural-language questions on a document. Extension runs on-stack or through SAP BTP. Where an estate has spent a decade encoding real operating detail into VIM, that detail is an asset, and the question is usually whether the environment is current enough to use what is now in the product.
Which route fits follows from the estate, the roadmap, and where your four costs sit. It is a real decision, and a smaller one than it is usually made to be, because neither route improves an exception that was designed badly upstream.
05
What AI Changes, and What It Does Not
AI in invoice processing has moved past extraction. SAP's invoicing assistant orchestrates Joule agents that read PDFs and images, propose tax, G/L and supplier codes from historical non-PO patterns, flag price and contract anomalies as possible fraud, and clear some exceptions without a person. OpenText runs its own layer in Content Aviator, now integrated with Joule, so VIM invoices can be selected and approved through Joule or another agentic platform.
Some of this reaches upstream, which is the new part. An agent that spots a missing goods receipt and prompts the receiver before the invoice falls due is working on the cause.
The limits have not moved. No model raises a purchase order nobody raised, or finds a price in a contract nobody loaded. Agents learn from history, so an inconsistent history teaches inconsistency, and an agent acting on it spreads that faster than a person would.
Cut the exception categories, clean the master data feeding them and tell suppliers what to send, and the agents work on a smaller, better-behaved remainder.
An agent makes a well-designed process faster. It makes a poorly designed one faster too.
06
How the Work Gets Done
Whatever the starting point, this work takes one of three shapes. Optima operates in all three.
Advise
Know what to changeFits when AP performance is hard to explain, or invoice management has landed on the roadmap and no one has built the case from process facts.
What it looks like: a structured read of exception categories, master data root causes, supplier input quality, integration and roadmap dependencies. The output is the specification and the sequence, including which platform supports it.
Transform
Make the changeFits when the direction is set and material change is required: a new invoice capability, an ERP transition the invoice environment has to be rebuilt around rather than lifted through, or an e-invoicing mandate with a hard date and a country list behind it.
What it looks like: implementation, migration, integration, and controlled extension where standard configuration will not meet the requirement. Success is defined at the start: fewer exception categories, not faster handling of the same ones.
Optimize
Keep it movingFits when the platform is sound but the curve has flattened. Exceptions are handled and never retired. The team has quietly grown around the workarounds.
What it looks like: exception design, master data discipline, supplier onboarding and network coverage, and the configuration debt any long-lived invoice environment carries, including switching on capability the business is already paying for.
AP modernization is a decision about what the team should no longer be absorbing, followed by the platform, configuration and discipline to make that stick.
If your automation curve has flattened, or invoice management is on your roadmap for next year, it is a good conversation to have in person.
Visit us at SAP Connect from October 5-7. We'll be in booth 6206. Book a time to chat with the team or stop by the booth with your questions anytime.