Migrating to a new ERP doesn’t have to mean starting over in accounts payable. Here’s how that conversation usually goes.
One of the questions I hear most often from customers isn’t about how Basware is performing, it’s about timing. They’re going through an ERP migration, and someone senior is asking heads of department to reconsider connected systems. AP is always near the top of the list.
It’s a fair question. ERP programs touch everything, especially financials. But when you work through the detail, the case for keeping AP automation in place is almost always stronger than the case for changing it, and in many cases, Basware can actively improve what your new ERP delivers.
ERP transformations are significant investments. Basware helps protect and extend the return on that investment in two ways that don’t always make it onto the initial business case: feeding better-quality data into your ERP’s AI and analytics engines earlier in the process, and maintaining full AP coverage for legacy ERPs that fall outside the transformation scope. The risk argument for keeping Basware is strong. The ROI argument is just as compelling.
ERP migrations are multi-year programs, two years, sometimes four. During that entire period, the business still needs to run: invoices processed, suppliers paid, cash flow visible. Finance doesn’t get to pause.
Basware operates independently of your ERP. It connects via standard integrations but doesn’t live inside it, so when you cut over to a new system, Basware reconnects, and AP operations continue without disruption. That’s why customers like KION Group ran their Basware implementation in parallel with their ERP transition rather than stopping one to do the other.
The clean core principle is central to most modern ERP strategies, including SAP ERP Cloud: minimize customization of the base system to reduce long-term cost and upgrade complexity. The problem is that AP is inherently complex, with exceptions, approval workflows, compliance logic, and multi-country mandates. Building that natively inside your ERP creates exactly the kind of customization clean core is designed to avoid.
Basware handles that complexity in a dedicated layer alongside the ERP, not inside it. For SAP customers specifically, Basware’s integration is built on the SAP Business Technology Platform (BTP) - which means it connects natively within the SAP ecosystem, is visible to your IT team as a certified SAP integration, and doesn’t introduce any third-party connectivity risk into the architecture. That’s a meaningful distinction when IT is evaluating what stays and what goes during a migration. Mauser Packaging’s IT Director puts it plainly:
“While we could configure SAP to do what some of Basware does, we’d never get it to be as good as Basware. That’s why Basware was selected to feed the ERP system instead of us building our own solution.”- Bill Martin, IT Director, Mauser Packaging Solutions
AP automation represents real accumulated investment: touchless processing built to scale, supplier relationships configured, and team workflows embedded. That doesn’t always show up in cost comparison, but it should.
What also tends to be underestimated are the implementation costs of a replacement platform, supplier re-onboarding, team retraining, and the productivity loss while a new system beds in - often spread over many months and quietly absorbed rather than properly scrutinized.
Imerys arrived at Basware running more than ten ERPs across a structure built through acquisition. They needed AP automation that could consolidate across ERP transitions rather than be disrupted by them. They deployed across 14 countries in six months, with their broader ERP program still running in parallel.
E-invoicing mandates are rolling out across Europe, LATAM, and APAC. Archiving requirements, tax authority validations, and clearance models - the obligations vary by country and keep changing. A specialist solution handles that continuously and embeds compliance into workflows. An ERP-native approach typically requires a customization project every time a regulation changes, running directly against the clean core goal.
For a team mid-migration with IT resources already stretched, a compliance gap in a key market is an invisible risk, until it isn’t.
ERP changes stretch teams to their limits. IT is at capacity. Finance is managing business-critical processes that can’t be disrupted. Running an AP platform migration at the same time adds a new workstream and new risk to a program already carrying plenty of both.
Basware is a known quantity in that environment, with pre-built integrations, an established implementation approach, and support teams who take time to understand your setup. Keeping it in place holds one thing stable while everything else moves. In my experience, that’s worth quite a lot.
Every ERP program should involve a proper review of connected systems that scrutiny is right and healthy. But for AP automation, the argument for continuity consistently wins when you weigh the real costs: financial, operational, and in terms of the progress you’ve already made, as well as the opportunity to get more from your ERP investment, not less.
If you’re heading into a migration and want to think through what it means for your Basware setup, your customer success manager is a good place to start. We’ve helped a lot of customers work through this, and we’re happy to help you make the case internally too.
ERP change doesn’t have to mean starting over. See how to protect what’s already working and unlock more value from your SAP Cloud ERP investment.
Read the checklist: Optimizing AP Before, During, and After Your SAP Cloud ERP Migration
Get practical guidance to maintain continuity, reduce risk, and accelerate value - before, during, and after go-live.