No. AI is not going to replace SAP Business One, and after 350+ implementations I think the question has the shape of the problem wrong. Writing an ERP’s code was never the expensive part. The expensive parts are books your auditor accepts, a period close that holds, and years of edge cases. AI belongs on top of that, not underneath it.
The 71-second version is in the video above. The reasoning is below.
Three things landed at once.
In February 2026, an Anthropic researcher gave 16 Claude agents the job of writing a C compiler from scratch. Over about 2,000 sessions and two weeks, at roughly $20,000 in API costs, they produced one that compiles the Linux kernel. You can read the write-up of that experiment yourself. It is a real result, and it changed how a lot of people think about what AI can build.
Then came the AI-first ERP startups, pitching finance software written mostly by models.
And on r/SAP in early 2026 someone asked directly whether SAP would be dethroned by custom-built AI ERPs. That thread is worth reading. Most replies said no. The most upvoted one asked two questions that have stayed with me: who audits the ledger of an AI-built ERP, and who supports it after go-live. A former Workday employee made the sharper commercial point, that AI will cut expensive customisations. Someone else said the hard part is writing specifications that capture decades of tribal knowledge.
One detail about the compiler experiment matters, and it usually gets lost. People repeat it as “AI built a CRM in two weeks.” It was a compiler. A compiler has a specification you can read, and the team had GCC sitting there as a known-good reference to check every answer against. Most of the effort went into tests. New features kept breaking features that already worked.
Your ledger has no GCC.
Ask anyone who has run a period close under time pressure.
What costs money in an ERP is not the screens. It is the books your auditor and your tax department accept without argument. It is stock valuation that still reconciles when you change costing method mid-year. It is an audit trail that shows who changed what and when, months later, to someone who does not work for you.
Then there are the edge cases. The credit note raised against an invoice from a closed period. The partial delivery against an advance payment in another currency. The item that is a raw material in one plant and a finished good in another. Nobody writes those into a specification at the start of a project. They surface in year three, from a user who says “this has always worked like that.”
That accumulated behaviour is the product. SAP Business One has had decades of businesses pushing on it in every direction, and the awkward cases are already handled.
And then there is the part nobody budgets for: support after go-live. When something is wrong in the close and the statutory filing is due on Friday, you need someone who has seen it before.
This is where the arithmetic turns, and it is the part I would want any owner to sit with.
We have built e-invoicing on SAP Business One for eight countries: India, Angola, Saudi Arabia, UAE, Oman, Malaysia, Mauritius and Romania. Eight countries, eight sets of rules, eight sets of formats, eight tax authorities with their own opinions about what a valid document looks like.
None of it holds still. The rules change every year. A format version is withdrawn, a field becomes mandatory, a threshold moves, and every business over that threshold has to comply by a date that was not negotiable.
Some of it also has to be certified. In 2026 our billing and e-invoicing software received production certification from AGT, Angola’s tax authority. That is not a sprint you plan around. It is a process with an external body that decides when you have passed.
Build your own ERP and all of that becomes yours. Not once, but every year, for every country you sell in. The code was the cheap part.
That upvoted reply on r/SAP asked the right question, so let me answer it as a partner.
An auditor is not reviewing your software. They are deciding whether they can sign off on your numbers. For that they need to see where a figure came from, what it was before, who changed it and under what authorisation. The audit trail has to stand up without you in the room explaining it.
In validated sectors the bar is higher again. In pharma, a system touching batch records or quality data carries validation obligations that assume a documented, controlled system with a vendor behind it.
So the question is not whether AI can write accounting logic. It is whether, two years from now, you can defend that logic to someone outside your company who has the power to qualify your accounts.
As an intelligent layer on top of the system of record.
That is what we built TEKAI for. It connects ChatGPT, Claude and other AI models to SAP Business One through the Model Context Protocol, and customers use their own AI subscription. TEKAI is read-only by default. Posting can be enabled after testing, and when it is, it goes through SAP Business One’s own services with a human in the loop, rather than writing into SAP Business One’s data directly, so SAP Business One records it like any other transaction. TEKAI does not store SAP Business One data.
The architectural payoff shows up when the models move, and they move fast. On 5 September 2026 we ran the same prompt on Claude Fable 5.1, which had been released on 1 September, and on GPT-6, against an SAP Business One demo system. Nothing was installed. Nothing was upgraded.
That is the whole argument in one sentence. When a better model ships, a layer lets you use it in days. If the model had been welded into your ledger, you would be rebuilding your ERP to get the benefit.
Keeping the two separate also keeps responsibility clear. The system of record stays auditable and supported. The AI layer is where you can afford to move quickly, because getting it wrong does not put your books at risk.
Plenty, and this is where I would push back on anyone saying AI is all noise.
Codr is our AI tool that builds SAP Business One Web Client extensions, including from old add-ons or from screen recordings of how people actually use them. Implementations with heavy custom development used to take us around 12 weeks. With Codr we go live in about 2 weeks. In 2026 we moved five customers to the SAP Business One Web Client with Codr.
Reports are changing too. A report used to be a project: someone specified it, someone built it, someone tested it, and by then the question had moved on. Now it is a question you type.
So AI is taking real cost out of ERP projects. It is taking it out of the parts where cost was always avoidable, which is customisation and reporting, while the system of record underneath stays exactly where it should be.
Two things, and they pull in different directions only if you confuse them.
Keep your books on a system your auditor already trusts, that handles your country’s compliance, and that someone supports when the close goes wrong at month-end.
Then build what makes your business different with AI, on top. Your pricing logic, your planning, the questions only your operation asks. That is where AI earns its money, and it is yours to move as fast as you like, because nothing in it has to survive an audit.
My SAP Business One experience goes back 20+ years, to 2005. TEKROI is an official SAP Business One partner (SAP PartnerEdge — Sell & Service), founded in 2020 in Hyderabad, with 350+ SAP Business One implementations behind us. Through all of it the system of record has been the thing you do not gamble with. AI has not changed that. It has given us a much better layer to put on top.
If you want to see what that layer looks like on your own numbers, bring your hardest questions.
No. AI writes code well, and writing code was never the expensive part of an ERP. The expensive parts are books your auditor and tax department accept, a period close that holds, stock valuation, an audit trail and years of edge cases. AI belongs as a layer on top of that system of record.
You can build software with AI. What you would then own is every compliance rule, every country’s e-invoicing format, every yearly change and every support call after go-live. We have built e-invoicing on SAP Business One for eight countries, and the rules move every year.
The question an auditor asks is who signs off on the books and whether the audit trail holds. In validated sectors such as pharma that bar is higher again. A system of record has to be defensible to someone outside your company, not only correct on the day it is built.
No. TEKAI does not store SAP Business One data. It connects ChatGPT, Claude and other AI models to SAP Business One through the Model Context Protocol, and customers use their own AI subscription.
TEKAI is read-only by default. Posting can be enabled after testing, and it goes through SAP Business One’s own services with a human in the loop, so SAP Business One records it like any other transaction.
Comment DEMO on the video and we will send you the free blueprint.