What an ERP system is, and what it actually gives a company
An ERP is not an invoicing program with more options. It is one record of the business from which goods, money, regulation and labour all live at once — and that is how you recognise a real one.
- Published
- Author
- Konis Software
ERP (Enterprise Resource Planning) is a system in which a company's entire operation is kept as one connected record rather than as a set of separate programs that occasionally exchange files. The definition stays abstract until it is translated into a single concrete day: when a salesperson issues a quote, a warehouse worker ships the goods and an accountant posts the invoice, in an ERP those are three steps of the same document — not three entries of the same fact into three programs.
That yields the shortest test of whether a company has an ERP or merely a collection of tools: does anyone, even once, have to retype a value from one system into another. If they do, that is not an integrated system but an agreement between programs — and every such boundary is where the data begins to diverge.
What an ERP covers
The scope differs between systems, but the core is the same everywhere: a document created in one part of the company must automatically produce its consequence in all the others. The classic division looks like this.
| Area | What it covers | What would otherwise be separate |
|---|---|---|
| Sales and customers | Quote, order, delivery note, invoice, price lists and discounts, receivables | CRM + an invoicing program + a discount spreadsheet |
| Procurement | Purchase order, receipt, supplier invoice, three-way matching, advances | Email + spreadsheets + the accounting program |
| Inventory and logistics | Stock by location, reservations, lot and serial numbers, expiry, cost calculation | A warehouse program separate from finance |
| Production | Bills of material, work orders, consumption, cost of production | A spreadsheet of standards |
| Finance | General ledger, VAT records, bank statements, payments, fixed assets | An accounting firm with its own program |
| People | Payroll, working time, absences, travel orders | A separate payroll program |
An ERP is not an accounting program
This is the most common conflation in the market and it is worth resolving precisely, because the whole budget depends on it. An accounting program keeps what has **already happened**, in the shape the tax return requires. An ERP keeps the business **while it happens**, in the shape decisions need.
The difference shows most clearly in a question an accounting program cannot answer by nature: “how much stock is reserved against orders not yet shipped, and what is the margin on them per salesperson?” That figure does not exist in the general ledger, because it has not yet become a posting — it exists only in a system that keeps the operation, not only its consequence.
What an ERP gives — and what it does not
It is fair to separate the two, because an inflated promise is the most common cause of disappointment after go-live.
- **One source of truth.** Stock, customer debt and margin have no second version, because they are not kept in two places.
- **Visibility while reacting is still possible.** A missed deadline, a broken discount or a stalled order is visible as it happens, not in next month's report.
- **Control without slowing down.** Approval limits, separation of duties, and a record of who approved what, instead of trust taken on someone's word.
- **Compliance without retyping.** VAT records and e-invoices arise out of documents that already exist, rather than from a second data entry.
What an ERP does not give: no system repairs a process the company has not agreed on. If two people understand differently when an order counts as “confirmed”, an ERP will only multiply that disagreement faster and more consistently. Implementation therefore always begins with agreeing the process, not with choosing a vendor.
The Serbian context: what is mandatory here
A company operating in Serbia does not choose whether to cover these duties — only whether a system or a person covers them. This is the largest difference between local and foreign solutions, and the most frequent source of hidden cost.
- **SEF and e-invoicing** — sending, receiving and status tracking of invoices through the state e-invoicing system.
- **VAT records** — electronic recording of VAT calculations and individual records, alongside the PP PDV return.
- **E-fiscalization** — ESIR/LPFR for retail turnover, with a security element.
- **Payroll** — the PPP-PD filing, seniority premium, allowances and contracts outside employment; using the parameters that applied on the payroll date, not today's.
- **Electronic archiving** — retention periods and the archive book transcript.
The clause at the end of the fourth point deserves emphasis, because it is most often missed at selection time: payroll for a prior year must use the rules that applied then. A system that stores only the current value of a parameter cannot reproduce an old calculation — and that demand arrives every time an inspection or a correction request does.
When it is time for an ERP
There is no headcount or turnover above which a company “needs” an ERP. There are symptoms, and they are fairly unambiguous.
- 1
The same fact is entered twice
The delivery note is retyped into the invoice, the invoice into the accounting program, and stock into a spreadsheet. Every retype is a place for error and time nobody measures.
- 2
Reports disagree
Sales claims one turnover, finance another, and the warehouse holds a third figure. None is wrong — each measures a different thing from a different source.
- 3
Decisions wait for the monthly cut
A question about margin, collection or stock is answered only when someone sits down to assemble a report. By then the decision has been made without the figure.
- 4
Growth is paid for with people, not with the system
Double the turnover demands double the administration. That is the most expensive signal, because the cost only becomes visible once it is permanent.
What a modern ERP looks like
What is expected of a system implemented in 2026 differs from the previous generation on a few concrete points — and they are worth asking for explicitly, because all four are hard to add later.
- **Dimensions on the line from the first posting** — cost centre, project, channel and carrier sit on the line itself, so analytics do not arise from an after-the-fact allocation.
- **An API over everything the screen can do** — integration depends neither on file exports nor on screen scraping.
- **Automation that is measured** — rules that run on their own, with a record of what they actually did; automation without measurement is an assumption, not a feature.
- **AI that proposes rather than decides** — a draft with its source and trail, and a person who confirms; a proposal without evidence is a claim that cannot be checked.
NG One is built around exactly those four decisions, and that is the only reason it appears here: all four are architectural, must be chosen at the start, and cannot be added later without rebuilding the core. Whether that is the right architecture for a particular company is shown by its inventory of processes — not by this article.