Comparison
Rules, Machine Learning or LLMs: AI Options in ERP
Compare rule-based automation, machine learning and LLM assistants inside an ERP: what each does well and where it needs a person.
Short answer: use rules where the answer must be exactly the same every time, machine learning where you have lots of history and a clear number to predict, and an LLM assistant where people need to ask questions or draft text. In an ERP the safest design mixes all three and keeps a person approving changes.
The finance director's three questions
A finance director hears the same pitch from three vendors in one week: AI that scores your leads, AI that forecasts your cash, and AI that answers questions about your accounts in plain English. All three are called AI. Only one will help with Monday's real problem.
She asks each vendor the same questions: how does it decide, what happens when it is wrong, and can it change my data on its own? The answers reveal three quite different technologies, and the right use for each.
The problem
AI in ERP is a label covering very different techniques. Rules follow logic you write. Machine learning finds patterns in past data. Large language models read and write text. Each is good at one job and poor at others, and mixing them up leads to disappointment or risk.
The risk is not only that AI is wrong, but that it is wrong confidently, in a system where numbers feed decisions, payments and tax. A good design decides in advance where AI may speak and where only a person may act.
- Vendors call everything AI, so comparisons are impossible.
- A model gives a score nobody can explain.
- An assistant sounds sure about something the records do not say.
- Staff fear that AI will change data without anyone noticing.
The options side by side
| Rules | Machine learning | LLM assistants | |
|---|---|---|---|
| Good at | Fixed logic such as scoring or validation. | Forecasts and anomalies from past data. | Language: answering questions, summarising, drafting. |
| Explainable | Completely. | Partly. | Hard to prove why a sentence was written. |
| Needs | Someone to write the rules. | Clean history and monitoring. | Good context and guardrails. |
| Can be wrong | Only if the rule is. | Yes, on new patterns. | Yes, and sounds confident. |
| Typical use in ERP | Lead scoring, approvals, checks. | Demand and cash forecasts, odd transactions. | Asking your records questions, first drafts. |
Rules: exact and explainable
Rules are plain logic: if the order exceeds the credit limit, hold it; if a lead has a website and a phone number, give it these points. They are predictable, auditable and cheap to run, and anyone can read why a result happened.
They do not learn. When the business changes, someone must change the rules, which is usually what you want for anything that must be exactly the same every time.
Machine learning: patterns in history
Machine learning learns from past data to predict a number or flag something unusual, such as next month's demand or a payment that looks out of pattern. It shines when you have a lot of clean history and a clear thing to predict.
It is harder to explain and it can fail quietly when conditions change, so it needs monitoring and a person who understands its limits.
LLM assistants: language and questions
A large language model reads and writes text. In an ERP it can answer a question about your records, summarise a customer's history or draft a reply. It saves time on work that is mostly reading and writing.
It can also state something untrue in a confident voice, so it should read only what the user may see, cite where facts came from and never change data without approval.
How to decide
Match the technique to the job, not the job to the technique.
- Must the answer be identical every time? Use rules.
- Do you have a year or more of clean history and a number to predict? Consider machine learning.
- Is the job reading or writing text? Use an LLM assistant with guardrails.
- Would a wrong answer cost money? Add a preview and a person's approval.
- Do you need to explain the result to an auditor? Prefer rules.
The solution: a practical path
A safe rollout adds capability in the order of risk.
- Start with rules for checks and scores you can read and explain.
- Add an assistant for questions and first drafts, limited to what each user may see.
- Require a preview and a person's approval before anything changes data, and log every action.
- Collect clean history, then add forecasting where a clear number is worth predicting.
- Review results monthly and retire anything that is not earning its place.
Where ReckonERP fits
The Reckon AI assistant works inside the permissions of the person asking, and changes are applied only after you review and approve them.
The Sales AI Agent scores leads with fixed rules you can read, uses AI for research and drafts, and waits for a person to approve any message. AI and integration usage is billed separately. See AI-assisted selling.
Conclusion
Rules, machine learning and language models are three tools, not three versions of the same tool. A sound ERP uses rules for what must be exact, learning for what can be predicted and language models for what is read and written, with a person approving changes.
Ask every AI vendor how it decides, what happens when it is wrong and whether it may change your data alone. The answers tell you more than the demo.
Frequently asked questions
Should an AI change my data on its own?
Not without approval. Show a preview, let a person approve, and keep a log.
Do I need machine learning to start?
No. Start with rules and an assistant for questions and drafts. Add forecasting when you have enough clean history.
Why score leads with rules?
Because you can read and explain the result, and it does not change unexpectedly.
Can an assistant see all my records?
It should only see what the signed-in user may see. In ReckonERP it works inside that person's permissions.
Who pays for AI usage?
AI and integration usage is billed separately from the module subscription.
