Yes, you can build parts of an ERP with AI, and for a small company with one entity, one country and simple processes a home-built tool can run day-to-day operations. Where it fails is the part an auditor or tax authority checks: entries that can never be overwritten, a provable trail from every document to the tax return, retention for up to ten years, and structured e-invoices that change with the law. A bought ERP delivers those as standard. A home-built one has to prove each of them, and keep proving them after every rule change.

The question is no longer theoretical. On 5 November 2026 a user posted in r/ChatGPTPro that they had built an ERP with ChatGPT without being a programmer and would use it at work the next day; the thread drew 181 comments within days, and similar threads ran in r/AI_Agents and r/SAP in October. This guide does not judge any single project. It sets out what a home-built system has to pass, using the published rules themselves (read on 10 November 2026), the pricing data behind the ERP Pilot comparison, and 220 runs of our selection quiz from small companies.

💡 Key Takeaway

Treat an AI-built system like any other ERP candidate: it has to pass the same knockout criteria. If it cannot show an immutable journal, an audit trail and compliant e-invoicing, it is a useful tool next to your books, not your books.

Can you build your own ERP with AI?

You can build an application that does what most people picture when they hear ERP: customers, items, orders, stock movements, invoices and a dashboard. Modern coding assistants generate the database tables, forms and reports for that in hours, and a person who knows the business can steer them without writing code. For a team that has lived in spreadsheets, that is a real step forward.

What you get is an application, not yet an ERP in the sense your accountant, auditor or tax office means. The difference is not the number of screens. It is a set of guarantees about the data: that a posted entry stays as it was posted, that every number on the tax return can be traced back to source documents, that the system is documented, and that all of it still holds in eight or ten years. None of that is visible in a demo, which is why a home-built system usually looks finished long before it is.

So the useful question is narrower: which parts of the ERP should you build, and which should you buy? The rest of this guide answers that part by part.

What does an AI-built ERP get right?

The parts that are specific to your business. Standard ERPs are built around common processes and charge for every deviation, either in licences for an add-on or in consulting days for an extension. A home-built tool fits your process exactly, on day one, at the cost of a subscription to a coding assistant.

  • Operational screens. Job tickets, production boards, service checklists, delivery planning: tools that people use all day and where the fit of the screen matters more than accounting rules.
  • Reporting and dashboards. Reading data that already sits in your accounting system and showing it the way management wants to see it.
  • Glue between systems. Moving orders from a web shop into the ERP, or stock levels out of it, where no standard connector exists.
  • Prototypes. A working model of how you want a process to run is the best requirements document you can hand an ERP vendor or partner.

All four have something in common: they can be wrong for a day without the books being wrong. That is the line this guide keeps coming back to.

Where does a home-built ERP fail first?

At the general ledger. Tax authorities do not regulate software brands, but they do regulate the properties of electronic books, and those properties are exactly what a quickly generated application lacks.

In the United States, IRS Revenue Procedure 98-25 sets the rules for records kept in an automated system. It applies to every taxpayer with assets of $10 million or more, and to smaller ones whose required records exist only in electronic form, which covers many small companies that keep their books only in software (section 4.02). The records must be kept as long as they may be material to a tax assessment, they must reconcile to the books and the return through an audit trail, and they must hold transaction-level detail that identifies the source documents (section 5.01). The company must document the system, including "the internal controls used to prevent the unauthorized addition, alteration, or deletion of retained records," and that documentation must record every change to the system with its date (sections 6.02 and 6.04).

Germany is stricter and more explicit. Section 146(4) of the Fiscal Code (AO) forbids any change to an entry "in a way that the original content can no longer be determined." Section 147(3) AO requires books and annual statements to be kept for ten years, accounting vouchers for eight and other tax-relevant records for six. The tax administration's GoBD principles add a written procedural documentation of the system on top. A company with a German entity carries those obligations whether its software was bought or generated.

RequirementWhat the rule saysWhat a home-built ERP must show
Immutable entriesNo change that hides the original content (AO 146(4)); controls against unauthorized alteration or deletion (Rev. Proc. 98-25, 6.02)Corrections only as new entries or reversals; no UPDATE or DELETE on posted records, at database level, not just in the user interface
Audit trailRecords must reconcile to the books and the return (5.01)A chain from every tax return figure to account totals to single transactions to the source document
Retention10 years for books, 8 for vouchers, 6 for other records (AO 147(3)); as long as material for US assessmentsReadable, exportable data for a decade, through every rewrite of the application
System documentationData flows, controls, file layouts and every change with its date (6.01 to 6.04)A maintained description of the system, which AI-generated code rarely comes with
Data access for auditorsRecords must be available on request and capable of being processed (5.01(4))Standard exports an auditor can load, not a screenshot of a dashboard

Sources: IRS Rev. Proc. 98-25; German Fiscal Code sections 146 and 147, gesetze-im-internet.de. All read on 10 November 2026. Summaries, not legal advice; ask your tax adviser for your case.

The test that decides it

Ask the system to change an invoice that was posted last month. If it lets you edit the amount in place, without a reversal and a new entry that both stay visible, it fails the first requirement above, however good the rest of it looks.

How many small companies need the hard parts?

About half. From 19 February to 8 November 2026, 220 companies with 1 to 100 employees completed at least the first stage of the ERP Pilot selection quiz, in English or German. 110 of them (50%) reported at least one of three requirements that are the hardest to build yourself: operations in more than one country, more than one legal entity, or two accounting standards at the same time.

Small companies that need the hard parts of an ERP
At least one of the three110 of 220 (50%)Operations in more than one country84 of 220 (38%)More than one legal entity32 of 103 (31%)Two or more accounting standards49 of 220 (22%)
Small companies that need the hard parts of an ERP
Share of quiz runs
At least one of the three110 of 220 (50%)
Operations in more than one country84 of 220 (38%)
More than one legal entity32 of 103 (31%)
Two or more accounting standards49 of 220 (22%)

Source: ERP Pilot quiz, both language versions, 220 runs from companies with 1 to 100 employees, 19 February to 8 November 2026, minus test and internal runs. Legal entities are asked in the second stage only, so that row uses the 103 runs that answered it, and the top row is a lower bound. Measured on 10 November 2026.

Each of the three multiplies the work. More than one country means several currencies, several tax regimes and several sets of statutory reports, each of which changes on its own schedule. More than one legal entity means intercompany invoices that must match on both sides and a consolidation that eliminates them. Two accounting standards, for example local GAAP plus IFRS, mean parallel ledgers on the same transactions. Standard ERPs solve these once for thousands of customers. A home-built system has to solve them for one, and test them without a second customer to find the bugs.

The group that most often considers building is the one without an ERP today. 32 of the 130 runs that answered the question about their current system had none, and 15 of those 32 already reported at least one of the three requirements. The other half is the profile where a home-built tool has its best chance.

Which rule changes would you have to keep up with?

More than most small companies expect, and on fixed dates. The clearest example is e-invoicing in the European Union, which applies to any company with an EU entity or EU business customers.

E-invoicing dates a home-built ERP would have to meet
1 Jan 2025Germany: receive e-invoicesDomestic B2B buyers must accept them11 Mar 2025EU adopts VAT in the Digital AgeIn force since 14 April 20251 Jan 2027Germany: issue e-invoicesTurnover above 800,000 EUR1 Jan 2028Germany: all B2B issuersTransition rules for paper and PDF end1 Jul 2030EU cross-border digital reportingIntra-EU B2B supplies1 Jan 2035EU: national systems alignedDomestic real-time reporting
E-invoicing dates a home-built ERP would have to meet
DateChange
1 Jan 2025Germany: receive e-invoices. Domestic B2B buyers must accept them
11 Mar 2025EU adopts VAT in the Digital Age. In force since 14 April 2025
1 Jan 2027Germany: issue e-invoices. Turnover above 800,000 EUR
1 Jan 2028Germany: all B2B issuers. Transition rules for paper and PDF end
1 Jul 2030EU cross-border digital reporting. Intra-EU B2B supplies
1 Jan 2035EU: national systems aligned. Domestic real-time reporting

Sources: German VAT Act section 14 and section 27(38), gesetze-im-internet.de; European Commission, VAT in the Digital Age. Read on 10 November 2026.

In Germany, an e-invoice is no longer a PDF. Section 14(1) of the VAT Act defines it as an invoice "issued, transmitted and received in a structured electronic format" that follows the European standard EN 16931 (or an agreed format that can be extracted into it), and section 14(2) makes it mandatory between domestic businesses. The transition rules in section 27(38) allow paper and other formats until the end of 2026, and until the end of 2027 only for issuers whose turnover in the prior year was 800,000 EUR or less. Our guide to German e-invoicing covers which standard ERPs create and read these formats today.

For a home-built ERP, each of these dates is a development project with a deadline set by law: generate a valid XRechnung or ZUGFeRD file, validate it, receive and process incoming ones, archive both in the original format. Then the EU cross-border reporting from 2030 adds the next one. A vendor ships these as an update to all customers at once; with your own system, you are the vendor.

Is AI-generated code safe enough for your books?

Not without review. In a benchmark published on 30 July 2025, Veracode tested more than 100 large language models on 80 coding tasks and found that the models introduced vulnerabilities in 45% of test cases, classified in the OWASP Top 10. On two specific weaknesses the models failed in most cases: cross-site scripting in 86% and log injection in 88%.

Both matter for an ERP. Cross-site scripting lets an attacker run code in a user's browser, which in an ERP means in a session that can approve payments. Log injection lets someone write false entries into a log, which in an ERP is the audit trail. The benchmark measured the models' choices on test tasks, not every line of AI code in production. But it shows that the security of a generated system depends on whoever reviews it, and in the scenario where a non-programmer builds the ERP, that reviewer is often missing.

Who maintains it in year three?

The person who prompted the system is also its only developer, its only tester and its only documentation. If that person leaves, the company owns an ERP nobody can change, holding records it must keep for up to ten years.

What does buying cost by comparison?

Less in subscription than many expect, more in implementation. For ten users, the ERP Pilot pricing data puts the yearly subscription of Odoo Enterprise at $3,000 to $5,400 and of Dynamics 365 Business Central at $9,600 to $13,200, at list price. The one-off implementation is the larger line: $15,000 to $80,000 for Odoo and $25,000 to $150,000 for Business Central.

What buying an ERP costs at 10 users
Odoo Enterprise, subscription per year$3,000 to $5,400Business Central, subscription per year$9,600 to $13,200Odoo Enterprise, implementation (one-off)$15,000 to $80,000Business Central, implementation (one-off)$25,000 to $150,000
What buying an ERP costs at 10 users
Amount
Odoo Enterprise, subscription per year$3,000 to $5,400
Business Central, subscription per year$9,600 to $13,200
Odoo Enterprise, implementation (one-off)$15,000 to $80,000
Business Central, implementation (one-off)$25,000 to $150,000

Source: ERP Pilot pricing data and TCO model, list prices, 10 users. Subscription is 12 months; implementation is the range for a project of that size. Bars start at the low end of each range. Details on the Odoo and Business Central pricing pages.

A home-built system looks cheaper because its costs are hidden in salaries: the hours of the person who builds it, the hours of whoever fixes it, and the hours your tax adviser or auditor spends reconciling it. The honest comparison is three years of the bought system, including implementation, against three years of those hours plus hosting, backups, security review and the e-invoicing work in the timeline above. Our breakdown of ERP implementation costs shows where the money in a standard project goes, and the ERP price overview lists the subscription ranges of all 20 systems we compare.

For the smallest budgets there is a third path. The open-source Odoo Community edition has no licence fee and covers customers, sales, purchasing, stock and invoicing, and a coding assistant is well suited to extending it. Its full Accounting app with the financial reports is Enterprise only, so the books then stay in a standard accounting system, often your accountant's. You still build on a data model that many companies already run, instead of writing one from scratch.

When is building the right call?

When the thing you build is not the system of record for your finances. The pattern that holds up is a standard ERP or accounting system in the middle, with AI-built tools around it that read from it and write to it through its interfaces.

Build with AIBuy (or keep) as standard
Shop-floor and service screens tailored to your processGeneral ledger, receivables, payables
Dashboards and management reportsTax calculation and VAT returns
Connectors where no standard one existsE-invoicing in legally required formats
Prototypes and requirement modelsIntercompany, consolidation, parallel ledgers
Internal tools for one teamPayroll and anything with statutory reporting

Building the whole ERP can still be defensible in a narrow case: one entity, one country, one accounting standard, no e-invoicing obligation yet, an owner who reviews the code or pays someone to, and a plan to export everything into a standard system when the company grows. Our quiz data says that is roughly half of small companies today, and the timeline above says the e-invoicing condition expires for many of them in 2027 or 2028.

What should you check before go-live?

Run the same knockout list you would apply to any ERP vendor. If your home-built system cannot pass one of these, keep the accounting in a standard system and connect the two.

  1. Posted entries are immutable. Try to edit and delete a posted invoice, both in the interface and directly in the database. Only reversals should be possible.
  2. The audit trail is complete. Pick a figure from last quarter's tax return and trace it to single source documents.
  3. Every change is logged. Who changed what and when, for data and for the application itself, including changes made by the AI assistant.
  4. Exports work without the application. Your accountant can load the journal and master data into their own tools.
  5. E-invoices validate. Outgoing XRechnung or ZUGFeRD files pass an official validator, and incoming ones are processed and archived in the original format.
  6. Someone other than the builder can maintain it. There is documentation, a test suite and a second person who understands both.
  7. Security has been reviewed. Access rights, authentication and the OWASP Top 10 have been checked by someone qualified.

If the list rules out building, the next step is a shortlist. Our independent ranking of ERP software and the ERP selection guide show which standard systems fit a small company; Odoo, Business Central and SAP Business One are the usual starting points at that size. If the reason you considered building was AI itself, our overview of AI features in standard ERPs shows what you can get without writing the system yourself.

💡 Key Takeaway

Build the edges, buy the core. AI makes custom tools around an ERP cheap and fast. It does not make an immutable ledger, a ten-year archive or compliant e-invoicing appear by itself, and 50% of the small companies in our data already need more: several countries, entities or accounting standards.