We are building an ERP that understands both the law and the work
NG One is a product of Konis Software. It grew out of one remark we have heard for years, in every company, in almost identical words: the system knows what happened, but not why, and it is no help in deciding what to do next. NG One is an attempt to change that — one core that connects data, people and processes, does what it can on its own, and explains everything it does.
- A Konis Software product
- Nine business spaces in one core
- Part of the NG product family
Who we are
Konis Software builds business software that runs in Serbian companies every day — and everything in NG One grew out of that work.
Konis Software develops products for retail, hospitality, logistics and field operations: NG Commerce, NG Sara, NG Nora, NG eFiscal and NG Operations. Each solves its part of the work, and each runs at real clients, with real documents and real deadlines. That experience is the reason we dare start an ERP at all: we know what it looks like when a fiscal printer dies on a Friday afternoon, how a warehouse behaves when a truck arrives half wrong, and why an accountant in December trusts no report they did not assemble themselves.
NG One is not the sixth product in a row. It is the core the others stand around — a system that runs finance, purchasing, sales, inventory, manufacturing, people and documents, and orchestrates the neighbouring products rather than replacing them. A company already taking payments on NG eFiscal should not have to abandon it to get an ERP; it should get a core that talks to it.
This is also the place to say what the system stands on, because none of it is visible from a screen. Beneath nine business spaces and around sixty technical domains sits one platform: a multitenant core with database-level isolation, six-layer authorization, a document framework with state machines, the workflow kernel, versioned configuration, the licensing framework, and an API over everything that exists in the system. These decisions are rarely written about because they do not demo — and they are the whole difference between a system that absorbs a new legal entity, a new dimension and a new tax rate in its third year, and a system that gets rewritten in its third year.
The Intelligent Core
The idea behind the name and behind the mark. Three elements, each of which means something the system actually does.
The core
The point where data, people and processes meet. A company has one truth not because someone declared it, but because every document is born in the same model and posted into the same ledger. The core is the reason a report does not need reconciling before it can be read.
The open ring
There is one ring — that is the 'One'. It is open on purpose: the system is controlled, but not closed. Every object exists in the API, every integration is a separate adapter with its own lifecycle, and neighbouring products connect rather than get swallowed.
The intelligence thread
A thin line connecting document to document, action to reason, conclusion to source. It appears only when something means something — when AI proposed it, when automation completed it, when a conclusion opens down to the document it came from. A thread that glows for no reason is decoration, and decoration in an ERP is noise.
Character
This is not a slogan but a test. When we argue about a screen, a message or an animation, the question is whether the answer passes these three sentences.
Calm in the work. Strong in the decision. Intelligent in every process.
Calm in the work
Eight hours a day inside a system means nothing may blink, glow or ask for attention without a reason. Light is the default theme, motion is functional and can be switched off without losing meaning, and at most one pulse exists per screen. The working surface is quiet — drama is reserved for the places where decisions are made.
Strong in the decision
When the system asserts something, it brings the evidence with it. The executive view does not show five charts; it shows the change, the cause of the change, the consequence, and three possible decisions with a what-if beside them. A number without a source is an opinion, and opinions are not the job of an ERP.
Intelligent in every process
AI is not a screen in the menu but a layer in every flow: a proposed dunning letter where collections are tracked, a proposed entry where posting happens, a recognized exception where it arises. Always as a draft a person confirms — a system that decides for you is not clever, it is unverifiable.
Why an ERP in 2026
Writing a new ERP is, statistically, a bad idea. Here is why we started anyway.
Because the line splitting the market is artificial. Domestic systems know the regulation but lack the modern modules: a real warehouse, QMS, maintenance, subscriptions, service with SLAs, a full CRM, a portal. International systems have all of that but fall over on Serbian payroll and local documents — the cash desk, travel orders, the retail ledger, agricultural purchase, offsets. A company gets to choose which half of the problem to keep. That line is not a law of nature; it exists because both camps started twenty years ago with one side in focus, and today neither can cross to the other without rewriting its core.
Because some decisions cannot be added later. Dimensional posting, effective-dated statutory parameters, a tenant model ready for agency mode, separate integration adapters over a single domain graph, clean-core extensions with versioned configuration — every one of those must exist before the first posted line. A system without them cannot acquire them by upgrade, only by migration. In NG One they sit beneath the first posted line rather than above it — that is the only moment at which they can be made.
Because AI has finally stopped being a demo. Not an assistant that paraphrases a document, but a layer that reads an inbound invoice and refuses to guess when it is unsure, that proposes a dunning letter with the days overdue calculated and the document attached, and that can say at the end of the day what it did on its own. A layer like that needs one place with the data and a clear record of every action. Existing systems struggle to acquire that after the fact, because one place with the data is not something you bolt on as a module; NG One is built around it.
And because we have clients who tell us when we are wrong. Konis Software does not build an ERP from a slide deck but from five products that are already out there, hitting the same statute, the same deadlines and the same people every day — NG eFiscal fiscalises through the V-PFR as an approved ESIR, with a decision number behind it rather than an intention. The companies running those products know their business better than we do, and they say so without softening it. The early access program exists precisely for that: so the people who do that work sit at the table while the system goes into their company, and so what they say changes the product rather than only the minutes.
How we work
Four rules that show up in the product, not only in this text.
Scope is counted, not described
Nine business spaces, around sixty technical domains beneath them, eight end-to-end processes and 270 named capabilities — thirty per space, each with a sentence saying what it does. All of it is on this site and all of it can be counted. A claim with no cover in the system does not appear here: scope is not inflated for effect, because inflated scope shows up at the first meeting after the signature.
Depth, not a module list
The flows run all the way: order to cash, purchase to payment, posting to the APR filing. The warehouse is a real WMS in the core — bin locations, directed picking, waves — not a quantity field on an item. A system is measured by what it finishes, not by the length of its menu.
Configuration before code
If a rule can be an effective-dated setting, it will not be code. Clean core means your customization does not block the upgrade, and versioned configuration means old entries still carry the rule they were made under.
Security is not a module for large accounts
Tenant isolation, six-layer authorization, segregation of duties, maker-checker, an immutable log, and support access only on your approval exist in every edition. Platform staff do not see business data — the boundary between control plane and data plane is hard, not a matter of trust.
The product family
NG One is a core, not a replacement. Each neighbouring product does its job better than a module inside an ERP would.
A company taking payments on NG eFiscal, receiving orders through NG Commerce and running field work in NG Operations has no reason to switch any of it off to get an ERP. NG One connects those flows: a receipt from the till becomes a posting and a tax record, an order from the shop becomes a sales order and a stock reservation, a work order from the field becomes a cost and an invoice. Every link is a separate adapter with its own lifecycle, so a failure in one channel does not take the rest down.
That is also why NG One is called what it is called. One system does not mean one program containing everything — it means one place where everything adds up to the same truth.
Konis Software
The company site: the team, the story and the whole product family.
NG Commerce
The commerce and ordering platform — the way sales enters the core.
NG Sara
Hospitality: orders, floor management and payment.
NG Nora
Ordering and communication with guests and customers.
NG eFiscal
Fiscalization and the fiscal channel — the receipt that becomes a posting in NG One.
NG Operations
Operations and field work: orders, people and time on site.
Write to us about what you do
The best conversations so far started with the sentence 'that is not how it works here'. If you have a sentence like that, it is the one we need.