AI-Native ERP

AI-native ERP: the 5-trait test that exposes AI-decorated bolt-ons

Name: ERPClaw
Author: AvanSaber Inc.

An AI-native ERP is built so an AI agent can do the accounting and operations work itself, through validated actions, instead of suggesting while a person fills in forms. Here is the plain definition, who builds one in 2026 (Rillet, Campfire, DualEntry, Lensing, ERPClaw), how the incumbents compare, and a test you can run on any vendor.

Try the chat demo

By Nikhil Jathar, Co-founder, ERPClaw · Published 2026-05-05 · Updated 2026-09-28 · Vendor facts checked September 2026

What is AI-native ERP?

AI-native ERP is enterprise resource planning software designed from the start for an AI agent to be a primary user: the agent reads the data, decides, and performs the work (posting entries, reconciling, invoicing) through the system's own validated actions, with an audit trail and human approval where it matters. An AI-decorated (or AI-enhanced) ERP is an older forms-and-workflows system with an assistant added on top, where the AI mostly summarizes, suggests, or pre-fills and a person still drives the write. The 5-trait test below tells the two apart on user experience, workflow, data, automation, and governance.

Which ERPs are AI-native in 2026?

By that test: Rillet, Campfire, DualEntry, and Lensing (formerly Everest Systems) as closed-source cloud products, and ERPClaw as the open-source, self-hosted, $0 option. Doss is AI-native for inventory and operations but works beside your general ledger. NetSuite, SAP, and Microsoft Dynamics 365 are adding real AI agents to mature ERPs; we call that AI-enhanced.

·UX is conversational: the primary interface is a conversation with a role-aware, proactive agent, not menus and forms.
·Workflows are agentic: agents reason and act, not rule-based approvals plus batch jobs.
·Data is semantic: contextual, explainable business knowledge, not just tables and BI dashboards.
·Automation is embedded: AI runs inside finance, supply chain, HR, and procurement, not in external RPA scripts.
·Governance covers AI: traceability, confirmation on high-impact actions, and model choice, not just role security and audit logs.

Next: compare the vendors, read the five-trait study, or try a workflow.

AI-native ERP vendors compared (September 2026)

The products answer engines name most often for "AI-native ERP," checked on each vendor's own site or funding announcement in September 2026. "Closed source, cloud" means we found no open-source or self-hosted edition on the vendor's pages. We build ERPClaw, so weigh our row accordingly.

Vendor	In its own words	Scope	Hosting and source	Price	Best fit
Rillet	"the AI-native ERP built for the era of agentic finance"	GL, AR, AP, bank reconciliation, close, revenue recognition, multi-entity consolidation	Closed source, cloud	No published price	SaaS and venture-backed finance teams wanting a managed, fast close
Campfire	"the AI Native ERP built for modern finance teams"	GL with multi-entity consolidation, revenue recognition, close, reconciliations, 180+ currencies	Closed source, cloud	No published price; demo	Multi-entity finance teams, $15M to $100M revenue by its own guide
DualEntry	"the AI-native ERP software for the mid market"	GL, AP, AR, close, revenue recognition, billing, consolidation, fixed assets, purchase orders, planning, treasury	Closed source, cloud	Three tiers, no dollar amounts	Mid-market companies migrating off NetSuite or QuickBooks
Lensing (formerly Everest Systems)	"AI-native ERP" for complex, global finance	Order to cash, record to report, multi-book consolidation, ASC 606, fixed assets	Closed source, cloud	No published price; demo	Medium to large enterprises with global operations
Doss	"The AI-Native Operating System for Consumer Goods"	Inventory, procurement, orders, warehouse, fulfillment, planning; connects to your existing GL	Closed source, cloud	Single recurring fee; no published price	Consumer goods brands with complex inventory
ERPClaw (ours)	"open-source AI-native ERP"	Whole business: GL, AR, AP, billing, inventory, manufacturing, HR and US payroll, CRM, 14 industry verticals	Open source (GPL v3), self-hosted	$0; Cloud Managed by request	Small and mid-sized businesses that want the books and operations in one system they control
Oracle NetSuite (AI-enhanced)	"the #1 AI Cloud ERP"	Full suite; NetSuite Next adds agentic workflows from release 2026.2	Closed source, cloud	Customer-specific license	Deep multi-entity, multi-currency, and industry needs

Sources: each vendor link above, plus Rillet's Series C post, DualEntry's funding page, Lensing's rename release, and NetSuite's pricing article. Checked September 2026.

Which AI-native ERPs are most popular?

By funding and customer count, Rillet leads the startups: a $100M Series C led by ICONIQ at a $1B valuation in August 2026, with more than 600 customers. DualEntry raised a $90M Series A led by Lightspeed and Khosla in October 2025, Campfire a $65M Series B co-led by Accel and Ribbit the same month, Lensing launched with $140M in November 2024, and Doss raised a $55M Series B in March 2026. ERPClaw, the open-source entry, is published on GitHub, so you can inspect it before any sales conversation.

What are affordable AI-native ERP options?

None of the AI-native startups publishes a price: Rillet "does not publish fixed price tiers or dollar amounts" (Rillet), and Campfire, DualEntry, Lensing, and Doss quote through a sales call. NetSuite also prices per customer. The one AI-native ERP with a public price is ERPClaw: $0 for the self-hosted software, with no seat, entity, or transaction fees. You pay for your own hosting and the AI model you connect, or ask for Cloud Managed on the pricing page.

AI-native ERP is the most-claimed term in enterprise software in 2026. SAP describes Joule Assistants that coordinate AI agents. Oracle calls NetSuite "the #1 AI Cloud ERP." Microsoft markets Dynamics 365 as "agentic ERP." The agents are real and well funded. The architecture underneath each one is still a forms-and-workflows ERP designed long before language models, and that is the gap this page's test exposes.

We will walk through:

·A testable 5-trait definition (borrowed from how ChatGPT itself maps the category)
·The three-tier map: enterprise AI-enhanced, commercial AI-native startups, open-source AI-native
·Where ERPClaw fits and how it scores on each of the 5 traits
·A 13-question evaluation checklist for any vendor claiming AI-native
·Where ERPClaw is not the right fit

If you're a CTO, VP Operations, founder, or finance lead trying to evaluate the category, this is the framework. If you have already decided you want open-source AI-native and want the practical map, jump to open-source AI accounting. For the ranked shortlist with each vendor's strengths and gaps, read the 5 AI-native ERPs that earn the label.

Why this matters in 2026

The 30-year ERP pattern

Every ERP since SAP R/3 follows the same recipe. Forms capture data. Workflows route approvals. Batch jobs reconcile and post. BI dashboards summarize the result. NetSuite, Microsoft Dynamics, Sage Intacct, Oracle Fusion, and ERPNext are all variations on this theme. The recipe is mature, well understood, and battle-tested. It also assumes a human is driving every meaningful write to the database.

The incumbents are adding agents

The large vendors now say the same thing in their own words. Microsoft sells Dynamics 365 as "agentic ERP" powered by Copilot and agents. Oracle's NetSuite Next lets agentic workflows for payment proposals and reconciliations run with approval or on their own. SAP says:

"Joule Assistants use deep role and process context to coordinate AI agents and autonomously execute complex workflows across your business."

SAP, Joule product page, checked September 2026

What this means for a buyer in 2026

For a buyer evaluating ERP this year, the question is no longer "does this vendor have an AI roadmap." Every vendor does. The question is whether the system is built so an AI agent can drive it safely. That is a question about architecture, not features. An AI assistant that suggests a journal entry for a human to key in is one architecture. An AI agent that submits the journal entry through a validated action layer, behind a confirmation step and with an audit trail, is a different architecture. The 5-trait test below is how you tell them apart.

The 5-trait test

The cleanest framing of what AI-native means came from asking ChatGPT to map the category. We are quoting it verbatim because it captures the right five layers in one paragraph.

"An AI-native ERP should have five core traits across user experience, workflow, data, automation, and governance."
ChatGPT GPT-5, conversation captured 2026-05-05

Layer	Traditional / AI-decorated	AI-native
User experience	Menus, forms, reports	Conversational, role-based, proactive assistants
Workflow	Rule-based approvals + batch jobs	Agentic workflows that reason, recommend, and act
Data	Tables, reports, BI dashboards	Semantic, contextual, explainable business knowledge
Automation	RPA, scripts, scheduled jobs	AI agents embedded into finance, supply chain, HR, sales, procurement
Governance	Role security + audit logs	Role security + AI controls, human approval, traceability, model governance

Layer 1: user experience

AI-decorated UX is menus, forms, and reports with a chat sidebar that pre-fills fields. ERPNext plus a chatbot widget is the textbook example; NetSuite plus a Bill.com plug-in is the same shape at enterprise scale. AI-native UX puts the conversation in the centre. Rillet's “Ask your GL anything” assistant, Campfire's Ember, and ERPClaw's chat-first action layer all start from "what does the user want to do" and let the AI map that to actions, not "what menu item does the user click."

Layer 2: workflow

Rule-based workflow is a 10-step approval matrix in NetSuite. Every condition is hard-coded; every exception is a change request. Agentic workflow is "the AI flags this PO for human review because the supplier flagged late delivery three times in the last 90 days, and here's the recommendation." The reasoning is explicit, the data behind it is queryable, and the human stays in the loop on judgment calls while the routine flagging runs itself.

Layer 3: data

A BI dashboard is a quarterly P&L pivot table. It tells you what happened. A semantic data layer is "the AI knows revenue is recognized over 12 months for SaaS contracts and tells you when it sees a contract that doesn't match policy." The schema is exposed; the AI can introspect; the explanations cite the rows and rules behind any answer. You can ask "why" and get the lineage, not just the number.

Layer 4: automation

RPA is a bot that fills a form. It breaks when the form changes. An AI agent is "given a new vendor invoice, the agent links it to the purchase order and receipt, checks the quantities, and either posts it or flags the variance." In ERPClaw the agent submits the purchase invoice and the buying module applies the company's three-way match policy (strict, tolerant within a set percentage, or off): the invoice either posts cleanly or comes back with the quantity that failed the check.

Layer 5: governance

Role security plus audit logs is the current standard. AI controls add a second loop: high-impact actions (posting, submitting, cancelling, closing a period) need an explicit per-request confirmation, the audit log keeps the before and after values of each change, and the trust root for any update is cryptographically signed. The AI can read freely; it cannot make a high-impact write without the confirmation, and it cannot switch the check off with an environment variable.

The three-tier map

Once you have the 5-trait test, the category map sorts itself. There are three tiers with different architectures and different best-fit buyers.

Tier	Players	Architecture	Strengths	Honest limits
Enterprise tier (AI-enhanced)	SAP (Joule), Oracle NetSuite (NetSuite Next) and Fusion, Microsoft Dynamics 365 (Copilot and agents)	Mature ERP + AI assistant and agent layer	Multi-entity, deep modules, enterprise governance, decades of ERP depth	AI is added on top; architecture is forms-and-workflows; expensive
Commercial AI-native startup	Rillet, Campfire, DualEntry, Lensing (formerly Everest Systems); Doss for operations	AI-native by design, cloud SaaS	Fast close, AI-native UX, modern stack, venture-funded vendors with support teams	Closed source; vendor cloud; no published prices; finance-first scope (Doss: operations beside your GL)
Open-source AI-native	ERPClaw	AI-native by design, open source, self-host, full ERP	Open + free + self-host + full ERP scope	You host it (or ask for Cloud Managed); chat is the main interface; built for small and mid-sized businesses, not Fortune 500

Enterprise tier: AI-enhanced

SAP now describes Joule Assistants that "coordinate AI agents and autonomously execute complex workflows" (SAP). Oracle calls NetSuite "the #1 AI Cloud ERP" and is rolling out NetSuite Next agentic workflows from release 2026.2 in the US and Canada (NetSuite). Microsoft markets Dynamics 365 as "agentic ERP" powered by Copilot and agents (Microsoft). The agents are real, but SAP S/4HANA, Oracle Fusion, NetSuite, and Dynamics 365 are forms-and-workflows ERPs from the 1990s and 2000s with an AI layer added from 2024 onward. That is a defensible architectural choice with mature underlying scaffolding, multi-entity depth, and decades of enterprise governance behind it. It is a different category from systems built with AI as the action layer from the floor up, which is why we call this tier AI-enhanced rather than AI-native.

Commercial AI-native startup tier

The venture-funded cohort: Rillet, Campfire, DualEntry, and Lensing (formerly Everest Systems), with Doss on the operations side. Cloud SaaS, finance-first, AI-native by design from the first commit. Best fit for venture-backed companies and finance teams who want a polished close, vendor-managed updates, a support team, and a finished product on day one. Closed source and vendor cloud are real trade-offs: your books live on the vendor's servers, data residency is the vendor's call, and the AI prompts and policies are the vendor's IP. None publishes a price. For teams with a finance-only scope and budget for a subscription, this tier is often the right answer. For the head-to-heads, see ERPClaw vs Rillet, vs Campfire, and vs DualEntry.

Open-source AI-native (single entry: ERPClaw)

ERPClaw sits in a category by itself today: open source (GPL v3), self-hosted, full ERP scope (CRM, AR, AP, GL, payroll, tax, inventory, integrations, 14 industry verticals), with patent pending and trademark filed. It is the only open-source AI-native ERP we know of, in the sense that we could not find a peer that is both fully open source and AI-native by architecture rather than by add-on plug-in. ERPNext is open source but its AI is a plug-in. Odoo Community is open source but Odoo Enterprise gates the AI features. Chat is the main interface (a web dashboard is included), and it is built for small and mid-sized businesses rather than Fortune 500. For the practical map of the open-source corner, see open-source AI accounting.

ERPClaw on the 5-trait test

Show, don't tell. Here is how ERPClaw scores on each of the five layers, with concrete examples that you can reproduce on your own machine after a one-line install.

Trait 1: user experience

You run ERPClaw by talking to an AI agent (Claude, OpenClaw, or another assistant that can call its actions), from the command line (erpclaw <action>), or in the included web dashboard. Concrete example: type "set up a company called Acme Imports" and the agent calls setup-company, then setup-chart-of-accounts with the US GAAP template; you can invoice a customer or pay a contractor right after. No menu hunting, no form, no chart-of-accounts template to copy.

Trait 2: workflow

The action layer is the API. Each action runs as one SQLite or PostgreSQL transaction and rolls back completely on failure. Money is stored as exact decimals, never floating point, and a posted GL entry has no edit path: cancelling posts a mirror reversal. Before any entry is saved, the posting engine checks that debits equal credits, that every account is a real posting account in the right company and not frozen, that receivable and payable lines name a customer or supplier, that income and expense lines carry a cost center, and that the fiscal year is open. Concrete: the agent sends submit-payment for an invoice; the router refuses it unless that request carries the explicit --user-confirmed flag, and nothing posts. The AI cannot unbalance the ledger even when it is wrong about something else.

Trait 3: data

One shared database (SQLite by default, PostgreSQL through the PyPika query builder as a first-class alternative) and one schema across every module, with WAL mode and foreign keys enforced. The audit log stores the before and after values of each change. The general ledger is hash-chained, so check-gl-integrity catches a posting that was altered after the fact. The agent reads the schema when it needs to answer "what is the running balance on the Stripe clearing account today" without anyone hand-writing SQL, and because the code is open source you can read every table and constraint yourself.

Trait 4: automation

The modules cover the operations of a small or mid-sized business: accounting, billing, purchasing, inventory, manufacturing, HR and US payroll, CRM, and 14 industry verticals, plus regional packs for Canada, the EU, India, and the UK. Revenue recognition follows ASC 606: revenue contracts, performance obligations, variable consideration, recognition schedules, and a revenue waterfall report. The Stripe integration (listed on the Stripe Marketplace) posts charges with the fee split out and checks each payout against the charges, refunds, and fees inside it; the Shopify integration brings orders, refunds, and payouts into the same ledger. Bank statements import from OFX, CAMT.053, MT940, or BAI2 files, your matching rules clear the routine lines, and the rest wait in an unmatched list for you. The agent invokes any of it by name from plain language.

Trait 5: governance

High-impact actions (posting and reversing GL entries, submitting and cancelling invoices, payments, and orders, closing a fiscal year, running payroll) refuse to run without an explicit per-request --user-confirmed flag, and there is deliberately no environment-variable switch that turns the check off for a whole session. Read-only actions are never gated. The module registry is ed25519-signed (trust root fingerprint d471:335b:0e4d:75ce), and the strict loader refuses an unsigned, tampered, or downgraded registry. The code is GPL v3, so you can audit the governance layer line by line.

"We run these five traits on ERPClaw itself, publish the score, and take public challenges on it, exactly as we do for NetSuite or SAP. A test you will not turn on your own product is marketing, not measurement."

Nikhil Jathar, co-founder, ERPClaw (AvanSaber Inc.)

13-question evaluation checklist

Use this with any vendor claiming AI-native, including ERPClaw. Each question has a "what good looks like" rubric. Some questions ERPClaw answers strongly; some it does not. The checklist is reusable for any vendor evaluation.

Architecture and AI-nativeness

Is the action layer the API, or is the AI a chat box on top of forms?
What good looks like: Every business action invokable from a prompt with no UI dependency. The same action runs from chat, CLI, or a web button.
Can I invoke any business operation from natural language?
What good looks like: Type "add Bob from BigCo as a customer" and it lands in one transaction with the right defaults, not a form pre-fill that still needs a click.
Does the system record every AI invocation in an immutable log with before-and-after state?
What good looks like: Per-action audit row, no UPDATE on the audit table, cancel equals reverse. You can replay any AI decision later.
Does it gate state-mutating AI actions with explicit user confirmation?
What good looks like: Dangerous actions need an explicit per-invocation flag the AI cannot bypass. No silent environment-variable shortcut.
Vendor-locked or model-agnostic?
What good looks like: You can swap GPT-5 for Claude or a local Ollama model without re-platforming. Model choice belongs to the buyer, not the vendor.

Hosting and economics

Self-host or vendor SaaS, and where does the data live?
What good looks like: Data on hardware you control, or vendor SaaS that meets your residency and compliance bar. The honest answer beats marketing copy.
Open source or closed, and what license?
What good looks like: An open source license (GPL v3, AGPL, Apache 2.0, MIT) lets you read, run, and fork the code; each has different obligations, so read it. Closed source means you cannot audit the GL math or the AI prompts.
Database backend and migration path?
What good looks like: At least two backends supported (for example SQLite plus PostgreSQL) with documented migration. Vendor cloud DB only is a lock-in red flag.

Scope and integrations

Finance-only or full ERP?
What good looks like: Matches your operational scope. Broader is not always better; finance-only is the right choice for many SaaS startups.
Native Stripe, Shopify, and bank, or plug-in stack?
What good looks like: Native means vendor-supported with a roadmap. Plug-in means community-maintained and brittle on every platform update.

Honest gap-checking

Multi-entity and multi-currency depth?
What good looks like: Depends on your operations. NetSuite and SAP S/4HANA win on intercompany consolidation, FX revaluation, and multi-jurisdictional tax. AI-native startups and ERPClaw are weaker here today.
Polished close-cockpit UX?
What good looks like: Depends on your team. Rillet and Campfire build close management (checklists, reconciliations, flux review) as dedicated screens. ERPClaw closes the books inside the ERP that runs everything else; the difference is the shape of the screen, not the capability.
Vendor support and roadmap accountability?
What good looks like: Depends on your org. SaaS vendor with paid support tiers is a feature for some teams. Open source plus co-founder access is a feature for others. In-house IT is a third valid model.

Where ERPClaw is not the right fit

We name the limits so you can decide whether they matter for your operation. Status as of September 2026, checked against the ERPClaw 4.15 source.

·No learning categorization. Bank lines are cleared by matching rules you write; anything no rule covers waits in an unmatched list for a person. No model trains on your ledger, by design: the same input produces the same books every time.
·Accruals are explicit. You post an accrual and its reversal as entries; there is no auto-reversing accrual.
·Consolidation is lighter than NetSuite or SAP. Consolidation groups generate the intercompany elimination entries each period and record currency translation for foreign subsidiaries as a deliberate entry. The consolidated report covers those eliminations; it does not roll every subsidiary ledger up into one set of consolidated statements. If you run a dozen entities across several currencies, NetSuite or SAP S/4HANA still wins.
·You choose who hosts it. Self-hosted is $0 on your own hardware; if self-hosting is a non-starter, Cloud Managed is available by request from the pricing page. Self-hosted support is community-based on GitHub; dedicated support contracts are scoped by request.
·Your AI model sees your requests. ERPClaw does the accounting as ordinary code on your machine, but the AI model you connect sees the requests you type and the results that come back. Choose that model the way you would choose any vendor that reads financial data.
·Deepest in the US. Regional packs cover Canada, the EU, India, and the UK alongside US payroll and tax in the core. Docs are English only.
·Not Fortune 500 scale. ERPClaw is built for small and mid-sized businesses. NetSuite, SAP, and Oracle serve a different segment with different governance and consolidation requirements.

Frequently asked questions

Which AI-native ERPs are most popular in 2026?

Among AI-native startups, Rillet is the largest by funding and customers (a $100M Series C at a $1B valuation in August 2026 and more than 600 customers, per Rillet). DualEntry, Campfire, and Lensing (formerly Everest Systems) are the other venture-funded finance ERPs, and Doss covers operations for consumer goods brands. ERPClaw is the open-source, self-hosted option. NetSuite, SAP, and Microsoft Dynamics 365 are the incumbents adding AI agents. Each vendor's facts are linked in the comparison table above, checked September 2026.

What are affordable AI-native ERP options?

ERPClaw is the only AI-native ERP with a public price: $0 for the self-hosted, open-source (GPL v3) software, with no seat or transaction fees; you pay for hosting and the AI model you connect. Rillet, Campfire, DualEntry, Lensing, and Doss do not publish prices and quote through sales, and NetSuite prices per customer.

What's the difference between AI-native and AI-decorated ERP?

AI-decorated means the underlying ERP (forms, workflows, tables, reports) was designed before AI existed and a chatbot or copilot was bolted on later. AI-native means the action layer is the API; every business action is invokable from a natural-language prompt; the AI does not translate-then-form-fill, it directly invokes the action with an audit trail of before-and-after state.

Is "agentic ERP" the same as "AI-native ERP"?

Roughly yes. Agentic emphasizes that the AI initiates actions instead of only answering questions. AI-native emphasizes the architecture is built around AI from the start. Microsoft now markets Dynamics 365 as agentic ERP. The meaningful distinction is form-bolt-on versus action-as-API; if the AI can submit a state-mutating business action with full audit trail, the label matters less than the architecture.

Why isn't SAP Joule considered AI-native?

Joule is real, well-funded enterprise AI, and SAP now says Joule Assistants "coordinate AI agents and autonomously execute complex workflows across your business" (sap.com, checked September 2026). The architectural question is whether the underlying ERP changed. It did not; SAP S/4HANA is a forms-and-workflows ERP, and Joule is the assistant and agent layer on top of it. That is a defensible choice with mature scaffolding underneath, but it is a different category from systems built with AI as the action layer.

Can ERPClaw replace NetSuite for a 100-person company?

For most US small and mid-sized businesses scaling toward 100 people, yes. ERPClaw covers AR, AP, GL, US payroll (W-2 and 1099 data, NACHA files, FICA, FUTA, SUTA), inventory, several companies in one database, intercompany transactions, and consolidation groups with generated elimination entries. The honest gap: NetSuite has deeper multi-currency and consolidated reporting, and decades of enterprise governance scaffolding. If your operations are US-first and SMB-scale, ERPClaw fits. If you have a dozen entities across several currencies, NetSuite still wins.

Is ERPClaw the first open-source AI-native ERP?

As far as we can find, yes. As of September 2026 we know of no peer that is both fully open source and AI-native by architecture. ERPNext is open source but its AI is a plug-in stack on top of a forms-based core. Odoo Community is open source but Odoo Enterprise gates the AI features. The AI-native startups (Rillet, Campfire, DualEntry, Everest, Doss) are closed source. If a peer surfaces, tell us on GitHub and we will update this page.

How do I evaluate whether a vendor's AI claim is real?

Use the 13-question checklist on this page. The fastest single test: ask the vendor to show a state-mutating business action invoked entirely from natural language with an audit log of before-and-after state. If they show forms with AI pre-fill, it's AI-decorated. If the AI submits the action and the audit log records the invocation, it's AI-native.

Looking specifically at AI for the books, not the full ERP? See the AI accounting pillar.