ERP Modernisation & AI P2P: 7 Steps for SAP Business One

ERP modernisation means moving finance off spreadsheets, disconnected tools and legacy accounting software onto one integrated ERP, then adding AI and automation on top. The order matters. AI needs clean, structured data, and the ERP is what gives it that. Get the foundation wrong and automation just makes the mess run faster.

That was the core message of our recent webinar with aclaros, an SAP Business One Platinum Partner in North America. James Kearns, Head of International Markets at Kefron AP, and Neal Johnie, Sales Director at aclaros, covered when to modernise, why AI projects fail, and what touchless purchase-to-pay (P2P) looks like for SAP Business One accounts payable teams in practice.

Here is what they said, and what finance leaders can take from it.

Key takeaways

• ERP is the foundation, AI is the accelerator. Without structured ERP data, AI only sees fragments.
• Standardise before you automate. Automation amplifies chaos if processes aren't clean.
• Bad data is the number one reason ERP projects underperform. Treat data cleansing as its own workstream.
• Start AI with your highest-friction process, not a brainstorm of AI ideas.
• A realistic SAP Business One implementation takes four to six months. AP automation on top of it goes live in weeks.
• The right touchless rate depends on your business. Smith Cameron Group runs at around 53% touch-free by design. TerraCycle runs at around 80%.

What is ERP modernisation?

ERP modernisation is the shift from disparate systems, manual processes and spreadsheet reporting to an integrated ERP platform that acts as the single system of record for the business. A modern ERP covers the core modules (finance, accounting, inventory, purchasing, sales and production) and connects natively to specialist applications for everything else.

Neal described this as a best-of-breed strategy. No single system can be everything to everyone, so the ERP sits at the centre and industry-specific tools plug into it. For AP and purchase-to-pay, that means an ERP like SAP Business One with an AP automation platform like Kefron AP integrated directly into it.

He was also clear that technology is the catalyst, not the starting point. Digital transformation starts with people, culture and standardised processes. If your organisation hasn't done that work, no system will make it ready.

Why legacy systems and spreadsheets are failing finance teams

Disconnected spreadsheets, manual procure-to-pay processes and homegrown systems that don't talk to each other don't scale. Neal called it the spaghetti-string problem. The obvious cost is lost productivity. The less obvious costs are:

• High maintenance costs on systems nobody wants to touch.
• Weak auditability, because data is copied between tools by hand.
• Tribal knowledge, where one person knows how to run a specific report. When they leave, that knowledge goes with them.
• Talent drain. Good finance people want modern tools. They won't stay long keying data from one system into another.

In Neal's experience, employees spend up to 20% of their time searching for or manually entering data, and for scaling businesses the cost of manual data management can overtake the cost of an ERP implementation within 18 months.

The high cost of doing nothing

Plenty of companies run a full ERP evaluation and then decide to do nothing. For leadership, the status quo feels safe. Neal's view is that it is currently the highest-risk strategy available, because competitors using AI-driven ERPs are pricing faster and responding to customers faster.

Some teams also hold off because they think AI will let them build their own system. James's response: a manufacturing and distribution business probably shouldn't be spending time building an AP system or an ERP, with all the security and data concerns that come with it.

Signs your business has outgrown its accounting system

Neal split the warning signs into two levels: what's happening across the business, and what your team feels day to day.

If you're on QuickBooks, Sage 50 or a similar entry-level package and recognise several of these, that's the tipping point for moving to an ERP like SAP Business One. Kefron's guide to the 10 warning signs your finance team needs AP automation covers the AP-specific signals.

7 steps to start an ERP modernisation project

Neal's framework for getting an ERP modernisation project off the ground:

1. Anchor on business outcomes, not technology. Define why you're modernising: scalability, margin control, audit readiness, cash visibility or automation. Tie success to finance KPIs like close cycle time, PO compliance and cost leakage.
2. Map your current state end to end. Document procure-to-pay, order-to-cash, inventory and financial close as they really run today. Manual handoffs, spreadsheets and rework loops are where the hidden risk and cost sit.
3. Standardise before you automate. Remove unnecessary exceptions and tribal-knowledge workflows. Define future-state processes that are repeatable, auditable and scalable.
4. Treat data as a first-class workstream. Cleanse suppliers, items, chart of accounts and approval hierarchies early, and agree data ownership and governance upfront.
5. Design with AI and automation in mind from day one, then phase it in. Touchless AP, intelligent invoice capture, three-way matching and exception handling work best embedded, not bolted on later.
6. Align stakeholders early. Finance usually leads, but operations, IT and procurement need to agree priorities. You need clear executive sponsorship. ERP is a business transformation, not an IT project.
7. Build a realistic phased roadmap. Core financials first, then operational depth (inventory, production), then advanced automation. Success is measured in value realised, not go-live dates.

Where should an SAP Business One implementation start?

Every implementation starts with finance. SAP Business One is a financial accounting system at its core. Service businesses can often start with accounting and grow from there. For inventory and production businesses, Neal recommends phase one covers accounting and inventory with sales and purchasing, then production and MRP capabilities come later.

How long does an SAP Business One implementation take?

For a business moving from QuickBooks or similar, Neal puts a realistic timeline at four to six months from contract to go-live. It can be done in three, but training and data cleansing are the biggest tasks on the customer side and shouldn't be rushed.

The project team is usually three to five people: a sponsor who can make decisions (owner, president or CEO), an internal project manager (some customers bring in external support for extra capacity), and subject matter experts from finance, operations and sales.

Why AI projects fail, and how to avoid it

James pointed to Gartner research suggesting around one in three AI projects fail. From his experience across AP and P2P projects, failure usually comes down to four things.

1. No clear business problem

The board or management team says "we need to invest in AI", but nobody has defined what it's meant to solve:

• Start with a high-friction process, not AI ideas. Finance leaders already know where the friction is. A room full of people brainstorming AI use cases rarely finds it faster.
• Quantify the baseline. Map cost, time, errors and FTE involvement. How many minutes does each invoice take, multiplied by your weekly volume? Once it's quantified, the size of the problem is obvious. Kefron's invoice processing calculator does this maths for you.
• Assess data readiness. If you can't clearly describe how a process works today, it isn't ready for AI.
• Define success properly. "We want to automate AP" is a weak goal. "We want to automate AP invoice data entry and save about eight hours a week" is a good one. Then decide what the team will do with that time back.

2. Vendor hype and misaligned expectations

Almost overnight, most AP vendors added "AI" to their product names and messaging. Some of it is genuine. Some isn't. We have seen plenty of customers arrive after abandoning a project because the vendor promised more than it delivered.

The fix is good documentation:

• Run discovery workshops and have the vendor document your as-is process, then play it back to you.
• Have the vendor document the to-be process step by step, not just a proposal full of diagrams.
• Agree success criteria together: what success looks like and by when.
• Write down all known risks. Every software project carries risk. Pretending otherwise is how projects fail.

3. Integration

Integration is where a project goes from four or five weeks to four or five months. James's three areas to nail down before you commit:

• Integration method. APIs are secure and fast but can be less flexible if you need data manipulated before it reaches the ERP. File-based exchange can suit that better. Neither is better in every case. Kefron AP offers a standard API connection, Kefron Konnect (encrypted SFTP file exchange) and custom API integration. See how Kefron AP connects to your ERP.
• Integration frequency. Everyone wants real time. Work out what actually needs to be. If you don't add new suppliers every day, does the vendor feed need to be instant?
• Integration ownership. Agree who owns architecture and design, field-level data mapping, the API connection, and configuration. Kefron and aclaros do the heavy lifting on joint projects, but customers still need super users and some IT input. Assigning that early prevents the "we don't have capacity" delay halfway through.

Neal added that you don't need every scenario on day one. Start with the baseline integration points and grow into the rest. Phasing also builds buy-in: a champion inside the business can show the time saved in phase one before phase two starts.

4. ROI forgotten after sign-off

Business cases get signed off, go to the board, then sit in a drawer. James recommends bringing the KPIs back up at every customer success check-in, every four to six weeks:

• How many FTE hours have we saved?
• We agreed 60%, 70% or 80% of the process could be automated. How much is fully automated three or six months in?
• Where are we against the original business case?

That keeps you accountable to the business, and keeps the vendor accountable too. For a full method, see how to measure AP automation ROI.

How AI is changing accounts payable and purchase-to-pay

Most AP teams James and Neal speak to describe the same six problems:

1. Manual invoice data entry. Two to three minutes per invoice doesn't sound like much until you multiply it by 500, 1,000 or 2,000 invoices a month. Our guide to cost per invoice shows what that adds up to.
2. Line-by-line matching of invoices against purchase orders and goods receipts, then chasing people across the business when they don't match.
3. Verifying invoices are accurate and legitimate. Swivel-chair work: keying data from the invoice into the ERP, then checking it again.
4. Coding non-PO invoices to the right GL code and department.
5. Chasing approvers and handling internal and supplier queries.
6. Finding and reporting on information spread across siloed systems.

James sees AI changing finance operations in three ways.

Efficiency and automation

AI removes the repetitive work: data entry, GL coding and order matching. In an automated AP process, an invoice flows like this:

1. The invoice arrives and AI extracts the invoice data.
2. The system verifies it: fraud detection rules, no-PO-no-pay policies, discrepancy checks and duplicate detection.
3. The invoice is matched line by line against the PO and goods receipt using automated 2-way and 3-way matching.
4. Matched invoices route for approval or post straight into the ERP.

Conversational intelligence

This is the part James is most excited about. Finance teams have put up with subpar reporting for years because the data sits in too many places. Conversational intelligence means asking your AP system a question in plain language and getting the answer in seconds, the same way you'd use ChatGPT, Copilot, Gemini or Claude.

For example: "Show me the top 10 suppliers who sent an invoice with a price increase in the last 30 days." No custom dashboard request, no CSV export. Kefron AP's AI Report Centre is built for exactly this, alongside the existing AP analytics dashboards.

The skill-set shift

Scaling businesses usually don't want a smaller finance team. They want the same team doing more valuable work. James's question for finance leaders: what would your team do with an extra day a week?

• Some customers want to get on top of supplier price discrepancies and negotiate early payment discounts.
• Smith Cameron Group's business case was simple: keep the good people they have and stop new hires spending time on repetitive work.
• Big Brand Tire & Service, one of the largest tire dealerships in North America, wants finance to act as a business partner, with the headspace to vet acquisitions and funding decisions.

James covers more of what finance leaders are telling us in AI in finance: what finance leaders are telling us.

What touchless rate should SAP Business One teams expect?

There is no single right touchless rate. It depends on how your business receives goods and services, and which invoices you want a person to check. Kefron AP customers typically see 70–90% touchless processing for recurring suppliers, but the number that matters is the one that fits your controls.

Two mutual Kefron and aclaros customers on SAP Business One show the range:

• Smith Cameron Group: 70% of invoices pass automatic verification with no discrepancies, confirmed accurate and not duplicates. 53% are processed fully touch-free through matching. That's deliberate. Smith Cameron wants a person to review a subset of inventory and stock invoices before they go into SAP. Read the Smith Cameron SAP Business One case study.
• TerraCycle: around eight in every 10 invoices processed touch-free.

James's point: you'll see claims of 80–90% touch-free automation everywhere online. That doesn't mean it's achievable or even desirable for your business case. For benchmarks and how to calculate your own rate, see touchless invoice processing rates in 2026.

How Kefron AP works with SAP Business One

Kefron AP integrates directly with SAP Business One, as well as SAP S/4HANA and SAP ECC6. It captures, codes, matches and routes invoices for approval, then posts them into SAP Business One, with suppliers, POs, goods receipts and GL codes synced back from the ERP. AI extraction combined with human validation delivers 99%+ data accuracy.

For mutual customers, Kefron and aclaros agree ownership of each part of the integration upfront, so the SAP Business One side and the AP side move together. If you're scoping a project, start with these key questions on AP automation for SAP.

Pricing is straightforward. Kefron AP charges a fixed monthly subscription based on your invoice volume band, so you can budget and see exactly what you'll pay as volume grows. Implementation is a one-off fee. There are no per-user fees. See how Kefron AP pricing works.

Comparing options? See our breakdown of the best AP automation for SAP Business One.

ERP is the foundation, AI is the accelerator

Neal closed the session with the line that sums it up: without ERP, AI sees fragments. With ERP, AI sees patterns.

If you're still on a legacy system and planning to automate AP first, James's advice is to be honest about whether you're just kicking the harder decision down the road. Get the ERP right, standardise the process, clean the data, then let automation do its job.

Already on SAP Business One and want to see what touchless AP looks like on your own invoices? Book a Kefron AP demo.

Frequently asked questions

What is ERP modernisation?

ERP modernisation is moving a business from disconnected systems, spreadsheets and legacy accounting software to an integrated ERP that acts as the single source of truth for finance, inventory, purchasing, sales and operations. Specialist tools, such as AP automation, then integrate directly into the ERP.

Should you automate accounts payable before replacing your ERP?

If your ERP is legacy and due to be replaced, automating AP first often delays the harder decision. AI and automation work best when the ERP is the central system of record. If you already run a modern ERP like SAP Business One, adding AP automation is the logical next step.

How long does it take to implement SAP Business One?

For a business moving from QuickBooks or a similar package, a realistic SAP Business One implementation takes four to six months from contract to go-live. It can be done in about three months, but training and data cleansing need enough time to be done properly.

How long does AP automation take to implement with SAP Business One?

AP automation is usually live in weeks, not months, when the integration method, data mapping and ownership are agreed upfront. Kefron AP implementations typically take three to six weeks, depending on invoice volume, entities and approval complexity.

Why do ERP projects fail?

Bad data is the number one reason ERP projects underperform. Other common causes are automating processes before standardising them, unclear business outcomes, poor stakeholder alignment, and treating ERP as an IT project rather than a business transformation.

Why do AI projects fail in finance?

Four reasons come up most often: no clearly defined business problem, vendor hype that sets the wrong expectations, integration that is underestimated, and ROI that nobody tracks after the business case is signed off.

What is touchless invoice processing?

Touchless invoice processing is when an invoice is captured, verified, matched to its purchase order and approved for payment without anyone in the finance team handling it. The touchless processing rate is the percentage of invoices processed this way.

What is a good touchless processing rate?

It depends on your receiving process and controls. Kefron AP customers typically see 70–90% touchless processing for recurring suppliers. Some businesses choose a lower rate on purpose, for example to keep a manual check on inventory invoices.

Does Kefron AP integrate with QuickBooks?

No. Kefron AP is built for mid-market and enterprise finance teams on ERPs such as SAP Business One, NetSuite, Microsoft Dynamics 365, Sage, Oracle, Infor and Unit4. It does not integrate with QuickBooks or Xero.

How is AP automation priced?

Kefron AP uses a fixed monthly subscription based on invoice volume bands, plus a one-off implementation fee. There are no per-user or per-approver charges, so cost tracks the work you process rather than headcount.

Who needs to be on an ERP or AP automation project team?

Usually three to five people: a project sponsor with decision-making authority, an internal project manager, and subject matter experts from finance, operations and sales. IT input is needed for access and sign-off on the integration.