Three editions, one system — priced to scope
There is no figure on this page, and that is deliberate. The NG One licensing model measures the package, the type of every user, the features switched on, AI credits and actual consumption — so the same edition produces two different figures for two companies. A number written here would be correct for neither. What is here instead: what each edition carries, what sits on top of it as a granule, and the four factors that settle the figure in conversation.
- Pricing on request
- Licensed by user type
- Cloud, on-premise or hybrid
- Granules are paid for only when used
Why this page has no numbers
An ERP price that fits on a web page is the price of a system that does not know who uses it.
A per-user monthly figure assumes every user is the same. In an ERP that is never true. An accountant lives in the general ledger all day; a warehouse operator touches a handheld ten times a shift; a salesperson opens quotes; and an employee who files one travel order a month has no business carrying a full license at all. NG One therefore licenses by user type — full, operational, terminal and self-service. That is built into the licensing framework itself, not invented at the sales table. A company with fifty employees and eight full users pays materially differently from a company with fifty full users.
The second reason is scope. NG One has nine business spaces and roughly sixty domains, and no company uses all of them. A distributor does not want QMS; a manufacturer does not want rental; an accounting firm wants agency mode that nobody else needs. Feature entitlements are switched on per tenant, so the price follows what is switched on. When manufacturing goes live a year later, you pay for manufacturing — not for a new installation and not for a second migration.
The third reason is the honest one: the price of a solution is not only the license. It also holds the process review, configuration, data migration, the integrations your legal entity actually uses, and training. None of that can be estimated from a website. It is estimated by sitting down with your documents, your chart of accounts and your approval chain. After that conversation you get one figure and a written scope beside it — not a range.
Three editions
The editions are not sales thresholds but three scopes of one core: Core holds a single ledger and a single document flow, Business adds manufacturing, projects, payroll and live integrations, Enterprise carries warehouse depth, consolidation, agency mode and a delivery model of its own. Moving between them is switching on an entitlement over the same core — no migration and no second installation.
NG One Core
The core of the business: purchasing, sales, inventory, finance and documents in one system.
For companies running goods and finance in separate programs today, who want one ledger and one document flow.
Included in the edition
- A dimensional general ledger, the Serbian chart of accounts, and a posting engine that shows the full entry before it is booked
- Receivables and payables, statements of account, dunning, interest and offsets; file-based bank statements with automatic matching, and a cash desk
- Purchasing: purchase orders with approval, three-way matching, advances, landed costs and customs entries
- Sales and invoicing: quote, order, delivery note, invoice, advances, credit notes and version-dated price lists
- Inventory: every goods document, lot, serial and expiry with FEFO, available and reserved stock, stocktakes and handheld screens
- A VAT engine with the statutory ledgers and POPDV and PP PDV export, mapped by the rules in force for the period
- My work: task inbox, approvals, exceptions and the AI daily brief
- Core AI: a copilot that shows its evidence, OCR on inbound documents, and proposed actions that arrive as drafts
Granules on top, paid only if used
- License granules for warehouse terminals and handheld devices
- AI credits beyond the quota included in the edition
- An additional legal entity in the same tenant
NG One Business
Most common choiceThe whole business inside the system: manufacturing, projects, payroll, BI and live integrations.
For companies that manufacture, run projects, or calculate payroll themselves, and need the report to arrive without a spreadsheet on the way.
Included in the edition
- Everything in Core
- Manufacturing: bills of materials and routings, work orders, costing, and MRP with a planner view and what-if analysis
- Projects: budget, timesheets, controlling and project profitability in the same ledger the trial balance comes from
- People and organization: Serbian payroll, PPP-PD filings, travel orders, absences and employee self-service
- The full statutory scope: APR financial statements, fixed assets with dual depreciation and PPI-1, corporate income tax, POS and the retail ledger
- Live integrations: SEF e-invoicing and VAT ledgers, e-delivery notes, CRF, the National Bank rate list, banks, the tax portal, sick leave, CROSO and fiscalization
- A reporting center: OLAP, a report and print designer, a spreadsheet over live data, and a compliance dashboard
- Advanced AI: cash flow, demand and collection-risk prediction, anomaly detection, and a Serbian-language copilot across the full scope
Granules on top, paid only if used
- License granules for shop-floor terminals, warehouse terminals and handheld devices
- A self-service portal for customers and suppliers
- AI credits beyond the quota included in the edition
- On-premise or hybrid delivery
NG One Enterprise
For groups, large warehouses and regulated plants — with a delivery model of their own.
For groups of legal entities, distribution warehouses, regulated plants, and accounting firms running many clients from one installation.
Included in the edition
- Everything in Business
- Advanced WMS: bin locations and zones, directed put-away and picking, wave and batch picking, cross-docking, cycle counting and SSCC packing
- QMS, laboratory and CMMS: quality control, analyses, maintenance plans, and downtime tied back to the work order
- Consolidation and intercompany: eliminations, internal transactions and group-level reporting, with separate books per legal entity
- Agency mode: many client legal entities from one installation, with data isolation and separate rights per client
- AI agents with autonomy levels over payables, sales orders and collections, with a log of every action an agent takes
- On-premise or hybrid delivery with an on-premise license
- NG One Platform Control Center: environments, subscriptions, entitlement overrides, quotas and tenant health, behind a hard boundary to business data
Granules on top, paid only if used
- License granules for shop-floor and warehouse terminals and handheld devices
- A self-service portal for customers, suppliers and employees
- AI credits and dedicated quotas per legal entity
- Additional environments: test, training and staging
How the price is formed
Four factors. Every one of them has answers that already exist inside your company — nobody has simply put them side by side yet.
Scope of the solution
How many modules are switched on, across how many legal entities. This is the base factor: NG One does not charge for what is off, but every legal entity carries its own ledger, its own periods and its own tax records.
- Which business spaces are in use, and which stay off
- The number of legal entities, and whether they consolidate
- The number of warehouses, plants and points of sale
- Whether there is foreign-currency trade, import or export
Who works in the system
Licenses follow user type, not headcount. A full user works in documents and ledgers; an operational user works inside one flow; a terminal user is a plant or a warehouse on a handheld; a self-service user files a request and sees their own.
- How many people genuinely open documents, and how many only approve
- How many terminals run on the shop floor and in the warehouse
- Whether employees file their own absences and travel orders
- Whether customers or suppliers get a portal
Process and integration complexity
How much has to be configured before the system matches your business. Configuration needs no developer, but it does need time — and every integration is a separate adapter with its own credentials, certificates and testing.
- How many approval steps there are, and what the limits look like
- How many distinct price lists, discounts and contracts exist
- Which integrations go live: e-invoicing, banks, fiscalization, social insurance, the tax portal
- How much data is migrated, and out of which system
Delivery model and consumption
Cloud, on-premise or hybrid — and how much the system does on its own. AI credits and usage metering measure what is consumed: document processing, predictions and agent work. What you do not use, you do not pay for.
- Cloud, your own server, or a combination
- How many documents a month pass through OCR and AI processing
- Whether AI agents are used, and at which autonomy level
- How many environments are needed beside production: test, training, staging
The factors explain what we measure, not what it costs. There is no public multiplier table behind them: the figure comes out of your specific scope and is stated in the offer, in writing.
What every edition includes
None of this is sold separately, not even in the smallest edition. These are the foundations of the platform — without them the rest would not work at all.
Data isolation and six-layer authorization
Tenant isolation at the database level, then RBAC, data scope, approval limits, segregation of duties, maker-checker and delegation. Not an add-on for large accounts — it is how the system works.
Document framework and state machines
A registry of document types, named transitions with guards and effects, five dates on every document, and an immutable change log.
Configurability without a developer
Effective-dated settings, config sets, a console with its own audit trail, and a clean-core approach — changing a rule does not require a new build.
A REST API with an OpenAPI spec over everything
Every object that exists on a screen also exists in the API. There is no module reachable only through its own window.
Import, export, and Excel export from every list
A template builder, column-to-attribute mapping, a dry run that shows the diff, and errors reported per row — not one message at the end.
AI daily brief and a copilot that shows its evidence
The core AI layer runs in every edition: a brief of the day, answers with their source documents attached, and proposals that arrive as drafts a person confirms.
Automation rules and a record of what the system did on its own
A rule is an event, a condition and an action. Everything the system completes without a person is visible in one place, with the time and the reason.
Both themes, tabular figures and accessibility
Light is the default because that is where eight hours of work happen, dark exists from day one, and contrast and focus meet WCAG AA on every screen.
Granules on top of an edition
Each one switches on separately and is paid for only while it is used. None of them requires a different edition or a reinstall.
Terminal license granules
A shop-floor terminal, a warehouse terminal and a handheld are each their own license type. An operator reporting consumption does not need a full license, and should not carry the price of one.
Self-service portal
Employees file absences, travel orders and expenses; customers and suppliers see their own documents, balances and delivery status. Without full access to the system, and without a phone call for every question.
AI credits
Every edition includes a quota. Credits beyond it are bought separately and spent on document processing, predictions and agent work — consumption is metered and visible per legal entity.
On-premise license
The same system on your server or in a hybrid, when regulation, group policy or a decision about data requires it. The on-premise license is a separate granule, not a different product.
NG One Platform Control Center
Managing environments, subscriptions, entitlements and quotas, with tenant health and support access only on your approval. Control plane and data plane are hard-separated — platform staff do not see business data.
Pricing is determined on request, after a review of scope and process. Editions describe the scope of the solution, not a promised outcome; what each module does, and how far it goes, is written on its own page.
Why is there no price anywhere?
Because any number written here would be wrong. The price depends on module scope, the number of legal entities, the mix of user types, process complexity, which integrations go live, and the delivery model. Two companies of the same size in the same industry get different figures, because those items differ. Instead of a range that means nothing, you get one figure after a review — with a written scope beside it.
What does the path to an offer look like?
The first conversation is a survey: how you work today, what hurts, and what has to work from day one. Then comes the process review, where we walk your documents, your chart of accounts, your approval chain and the systems you connect to. Out of that comes a written scope — the list of modules, user types, integrations and the data to migrate. The offer is written against that scope. If the scope changes later, the offer changes too, but you can see exactly what moved.
Do you charge per user?
Per user type. A full user works in documents and ledgers, an operational user inside one flow, a terminal user is a handheld or a shop-floor terminal, and a self-service user files requests and sees their own. A company where forty people submit one travel order a month does not pay for forty full licenses. Types are changed in the console, without a conversation with us.
What are AI credits, and can I simply not use them?
AI credits meter AI processing: OCR on inbound documents, predictions, copilot answers and agent work. Every edition includes a quota that covers ordinary use. If you do not use AI, the quota is not consumed and nothing is added. If you use more, credits are topped up, and consumption is visible per legal entity and per kind of processing — not as one line at the end of the month.
Can we move from one edition to another?
Yes, and without a migration. An edition is a set of entitlements switched on over the same core — when manufacturing or consolidation is switched on, the system stays the same, the data stays where it is, and the new capability appears in the navigation. The whole module catalogue lives in one database under one permission model; the edition decides what is switched on for your tenant.
What goes into implementation, and what into the license?
The license is the right to use: the edition, user types, granules and the AI quota. Implementation is the work done once: review, configuration, data migration, integration setup, training and go-live. Those two figures stand apart in the offer and are never mixed. If someone shows a single number for both, that number is hiding one of them.
Is on-premise more expensive than cloud?
Not by definition — it is different. On-premise carries its own license and assumes you hold the server, the backups and the restore procedure; cloud puts infrastructure and operations on us. Which is cheaper for you depends on what you already run and what regulation or group policy requires. We do that comparison openly, with both figures on the table.
How do I know the system covers our particular business?
By seeing it against your own data. The process review runs on your documents, your chart of accounts and your approval chain, and what comes out of it is a written scope — module by module, user type by user type, integration by integration. Nine business spaces and roughly sixty domains carry eight end-to-end processes, from Lead-to-Cash to Acquire-to-Retire, and the Serbian statutory load by name: SEF e-invoices, the EEO and EPP VAT ledgers, POPDV, PP PDV, fiscalization, payroll with PPP-PD, CROSO, e-delivery notes, CRF, APR statements and the retail ledger. We still do not turn that into a claim that we fit every company: if something in your business falls outside the scope, the scope says so — before signature, not in the third month of the project.
Tell us the scope, and you get the figure
One conversation is enough to see whether we are right for you. If we are not, you will hear it in that conversation — not in the third revision of an offer.