Why AP Can’t Be an Afterthought in An SAP Cloud ERP Migration

The clock is ticking. SAP’s 2027 mainstream maintenance deadline for legacy ERP systems is an imminent forcing function, and finance organizations face a critical challenge around maintaining uninterrupted, automated accounts payable operations while protecting the integrity of their new ERP core. Recent industry data and vendor advancements underscore that a Clean Core strategy anchored in certified, non-invasive integrations is essential for success.

SAPinsider’s 2026 Benchmark Research on ERP Migration and Transformation reveals that urgency. The report notes that while 55% of organizations report having deployed SAP S/4HANA or SAP S/4HANA Cloud, only 34% have completed a full transition. Another 36% remain in implementation, evaluation, or business-case stages, with many moving to cloud deployments to navigate licensing constraints and unlock generative AI capabilities.

The Clean Core Imperative

One of the most consequential shifts in modern SAP strategy is the move toward a Clean Core architecture — the discipline of keeping the SAP system free of custom code and point-to-point integrations that accumulate technical debt and turn every upgrade into an expensive, risky project. As organizations race to migrate, the temptation to build quick, bespoke integrations for AP automation is real. However, those shortcuts become anchors the moment SAP issues its next update.

This is exactly why Basware’s recent announcement that it is one of the first AP solution providers worldwide to earn SAP Clean Core certification for its Connector for SAP Cloud ERP Private carries weight. The certification is a technical proof that the integration operates entirely outside SAP’s core system, using SAP’s approved extension and integration frameworks. For SAP customers, that means no custom code to maintain, no broken integrations after upgrades, and no AP blackout windows during migration.

Why AP Cannot Go Dark During Migration

SAPinsider’s research underscores the complexity lurking beneath reported migration numbers. Many large enterprises run multiple ERP instances in parallel, meaning a single SAP S/4HANA deployment may represent only a fraction of a company’s landscape. However, finance teams navigating this complexity cannot afford for AP operations to stall as invoices don’t pause for IT projects.

Basware’s Connector is purpose-built to keep invoice processing and AP automation running continuously before, during, and after go-live by directly integrating Basware’s Invoice Lifecycle Management (ILM) platform into the SAP Cloud ERP ecosystem. The practical impact is significant: AI-powered invoice processing, automated three-way matching, and compliance with 60+ country e-invoicing mandates continue without interruption, giving finance teams clean, reliable AP data from day one rather than months after cutover.

Reshaping the Migration Business Case

Global enterprises require a specialized layer like Basware’s platform to handle complex invoice variability, manage 60+ country-specific e-invoicing mandates, and deliver touchless processing at scale. Real-world results confirm the value. KION Group leveraged Basware during its SAP S/4HANA transition and achieved a 50% reduction in AP cycle times while enabling reliable cash-flow forecasting. The company used the solution to tidy up its accounts and prevent inaccurate data from migrating into the new system. This ensured a smoother cutover and immediate post-migration visibility.

Heineken offers a vivid example of this playbook in action. As part of its Digital Backbone Transformation Program — which includes a worldwide SAP S/4HANA rollout — Heineken France standardized invoice management on Basware ahead of its 2027 SAP migration. By cleaning up AP before invoices ever reached the ERP, the brewer cut its invoice backlog by 50%, achieved 100% reconciliation automation, and raised on-time supplier payment compliance from roughly 75% to 95%. Crucially, the France deployment now serves as a repeatable blueprint for rolling out the same model across the company’s other markets — exactly the kind of pre-migration discipline that prevents bad data and broken automation from carrying into a new SAP core.

What This Means for SAPinsiders

Prioritize clean core-certified AP integrations before an ERP migration project. Custom AP integrations built during migration create hidden liabilities that surface at upgrade time. Choosing a connector that has earned SAP Clean Core certification means AP automation is architected to remain upgrade-safe indefinitely. With only 34% of organizations having fully completed their SAP S/4HANA transition per SAPinsider’s 2026 research, the organizations still mid-migration have a decisive window to get this right. SAPinsiders should evaluate their current AP integration strategy against Clean Core principles now, and replace any customizations with certified, pre-built connectors before go-live.

Treat AP continuity as a migration success criterion. Finance leaders often focus migration planning on ERP data accuracy and system stability, while AP continuity is treated as an operational detail. This is a costly mistake as invoice-processing disruptions during migration directly impact supplier relationships, payment terms, and working capital. Finance leaders should demand that their AP solution provider demonstrates uninterrupted processing through the cutover period and validate that capability with customer references.

SAP migration should accelerate an organization’s AP AI strategy. SAPinsider’s 2026 data highlights that generative AI and SAP’s AI roadmap are now material drivers of migration timelines. Finance teams should use the migration moment as a catalyst to upgrade their AP automation capabilities in parallel. This is because a specialist AP platform trained on billions of real-world invoice transactions will extract far more value from the SAP Cloud ERP ecosystem than a generic integration ever could. Touchless invoice processing, dynamic discounting, global e-invoicing compliance, and predictive cash-flow visibility are all achievable at go-live, but only if the AP layer is selected and deployed with the same strategic intent as the ERP itself.