One system that runs the company, from document to decision
NG One connects sales, procurement, inventory, production, finance and people into a single graph of business data. The Serbian chart of accounts, tax rates and filing deadlines sit in the core — not in a localization package bolted on top. The intelligence layer works over that same data, and every draft decision carries an explanation and a path back to the source record.
- Nine business spaces
- SEF, VAT and fiscalization
- Serbian payroll in the core
- Real warehouse management
- AI with evidence and drafts
- Multitenant and API-first
Built for serious business.
Scope, stated as a number
Every figure here can be counted on this site: space by space, capability by capability, each one with a name and a description of what it does. These numbers describe the scope of the system — how much work it covers, not how much faster somebody's month got.
9
business spaces
The first level of navigation in the product. The number is fixed by the system's information architecture, not rounded for the website — a tenth space would mean a different product.
~60
technical domains
Domain modules in the platform registry. The user never sees them as a list — that is what the nine spaces are for.
270
named capabilities
Thirty per space, each with a name and a description of what it does. They are countable on the space pages — not one of them is a line on a wish list.
8
end-to-end processes in the Atlas
Lead-to-Cash, Procure-to-Pay, Plan-to-Fulfill, Record-to-Report, Hire-to-Retire, Case-to-Resolution, Project-to-Cash and Acquire-to-Retire.
2 × 2
languages and themes, as equals
Serbian and English, light and dark — from day one. Neither is an afterthought translation or a night mode added later.
Existing systems solve half the problem
This is not about bad software. It is about a market that moved: no existing family of systems covers both halves that a Serbian company now has to cover at the same time.
The regulation moved under the system
By 2026 the state had merged invoicing, VAT records, delivery notes and public-sector receivables into one connected ecosystem around the national e-invoicing platform. The outbound invoice, the EEO and EPP records, the electronic delivery note, the public-sector registry and the fiscal receipt are no longer separate errands — they are one flow with deadlines and mutual dependencies. A system that treats them as five unrelated exports does not solve that work. It hands it to people.
Foreign systems do not know the local half
Odoo, Business Central and SAP bring a mature core and serious operational depth. But Serbian statutory payroll, PPP-PD filings, the cash desk, travel orders, the KEP book, agricultural purchase with VAT compensation and offsetting are a gap each of them fills through a partner localization — an add-on on top of an add-on, with its own upgrade cycle. That is where the budget goes: into teaching the system the country it operates in.
Local systems have no modern layer
Pantheon, Calculus and BizniSoft understand the regulation and have kept Serbian companies running for decades. But a real WMS with bin locations, directed picking and wave picking, along with QMS and CMMS, subscriptions, helpdesk with SLAs, full CRM and a self-service portal, is not in their core. Once a company grows past that line, those modules get bought elsewhere and joined by export — and the system boundary quietly moves into a spreadsheet.
The work gets finished between the systems
Wherever two systems do not talk, a person covers the difference: double entry, monthly reconciliation, a spreadsheet sent by email and the version of that spreadsheet that never gets sent. The most expensive module in most companies is on no vendor's price list — it is a sheet somebody maintains by hand, with no owner, no audit trail and no control. When that person leaves, part of the business truth leaves with them.
NG One covers both halves on one platform: local regulation in the core, modern operational modules in the core, and one graph of business data underneath both. That is also why it is built from the foundations rather than layered onto an existing product — the decisions that make this possible cannot be added later.
Nine areas, not fifty-seven menu entries
NG One technically has around sixty domains. The user never sees them as a list. Work is organised into nine business areas; each has its own workspace, its own processes and its own place in the value chain, and the navigation rail never goes deeper than two levels. Each page below lists the thirty named capabilities of its area — with a name and a description, so the scope is read rather than assumed.
My work
The personalized home screen: decisions and exceptions, tasks and approvals, an AI daily brief, and what NG One finished on its own.
30 capabilitiesSales and customers
From opportunity to cash, in one chain with nothing retyped.
30 capabilitiesProcurement and suppliers
From need to payment: purchase orders, receipts, invoices, and a landed cost that stays correct after customs arrives late.
30 capabilitiesInventory and logistics
Stock on hand, goods in motion and value on the ledger — one record, reconciled at all times.
30 capabilitiesProduction and operations
Engineering data, planning, shop floor, quality and projects in one flow — with a product cost that is not assembled after the fact.
30 capabilitiesFinance and compliance
Serbian statutory accounting, dimensions and VAT — in the core, not bolted on.
30 capabilitiesPeople and organization
Employees, working time, absences and Serbian payroll — in the core of the system, not in a separate program next to it.
30 capabilitiesDocuments and processes
One document kernel, one approval path and one decision trail — underneath every document in the system.
30 capabilitiesInsights, automation and AI
The command center for decisions — evidence behind every insight, a trail behind every automation.
30 capabilities
AI that brings evidence, a draft and context
AI in NG One is not a separate module or a chat window off to the side. It works over the screen you are on, the document you are looking at and the data you are entitled to see. Every conclusion carries an explanation and a path to the source record, and every suggestion is a draft a person confirms, edits or rejects.
An AI daily brief instead of an empty chart
The working day does not open with a generic dashboard but with a sentence about what is waiting: how many decisions, which collections are at risk, which documents do not reconcile, and what the system has completed since your last sign-in. Every line links to the record it came from — a briefing that does not lead to work is just a prettier report.
A copilot that answers with evidence
On an invoice the panel offers what people actually do on an invoice: explain the posting, check the VAT treatment, find the matching goods receipt, check for a duplicate, draft a message to the supplier. The answer always carries the figure, the explanation, the source documents and a drill-down into them. An answer without evidence is not shown — that is a constraint, not a feature you switch on.
OCR that refuses to guess
Confidence is measured per field type, not per document: amount, tax number, account number and date each have their own threshold. A field the model is unsure about stays empty and asks for a person, rather than being filled with a likely value that surfaces only during an audit. Duplicates are caught before posting, and the proposal carries the link to the receipt or purchase order it belongs to.
Suggestions arrive as drafts
A dunning letter for a late customer, a purchase order from a replenishment proposal, a task, a reply to a supplier — the system prepares them fully and a person confirms them. Confirming, editing and rejecting are equal outcomes, and all three stay in the trail. Autonomy without confirmation exists only where the rule is deterministic and explicitly enabled — and then it is automation by rule, not a model's judgement.
AI respects permissions and leaves a trail
The model sees exactly what the user sees: same authorization, same data scope, same tenant isolation. Every prompt, suggestion and confirmation enters the AI audit, consumption is metered, and limits are configured per tenant. An evaluation harness with golden sets, isolation tests and prompt-injection tests runs in CI — before a change reaches a user, not after a ticket about it.
Predictions computed from your own history
Cash-in projection from open items and payment patterns, collection risk per partner, detection of postings that deviate from the usual pattern. The model computes from your data, not from somebody else's average — your customers pay late in their own particular way, not in the industry's. So every forecast states how many periods and which items it rests on, and it is sharper in December than in January. A forecast that will not say what it stands on is not a forecast — it is an assumption with a confidence interval.
A map of the company, not a diagram in a deck
The Atlas is a full-screen view of how the company actually runs: parallel value chains, the points where they cross, and live state on every node. It opens with a shortcut from any screen, adapts to the role, and every node is an entry into the real screen — not a picture of one.
Revenue
Lead-to-Cash
Opportunity
7 opportunities in negotiation
Quote
12 quotes awaiting a reply
Order
9 orders ready to ship
Delivery1
3 picking tasks are late
Invoice2
18 invoices raised from delivery notes with no entry
automatedCollection
average collection 37 days
automated
Procurement
Procure-to-Pay
Requisition
14 purchase proposals from stock minimums
automatedApproval
6 approvals awaiting a decision
Purchase order
23 purchase orders open
Goods receipt1
4 shipments arrive today
Invoice2
93% of invoices matched automatically
automatedPayment
31 payment orders prepared by due date
automated
Operations
Plan-to-Fulfill
Plan
demand plan confirmed for 6 weeks
Material sourcing
MRP proposed 17 purchase orders
automatedProduction
8 work orders on the floor
Quality
2 lots in quarantine
Stock1
41 items below minimum
Delivery1
3 picking tasks are late
Finance
Record-to-Report
Document2
47 inbound documents read and proposed for posting
automatedPosting
47 documents posted with no manual entry
automatedControls
83% of the bank statement matched
automatedClose
2 checks open before period close
Reporting
VAT return ready 4 days before the deadline
Employees, working time, absences and Serbian payroll — in the core of the system, not in a separate program next to it.
One document kernel, one approval path and one decision trail — underneath every document in the system.
The command center for decisions — evidence behind every insight, a trail behind every automation.
StockProcurement · Operations · Revenue
A supplier receipt, finished goods from the floor and a delivery to a customer all move the same balance. Three chains, one availability figure — which is why a customer reservation can see material still in transit.
- ProcurementGoods receipt
- OperationsStock
- RevenueDelivery
InvoiceRevenue · Procurement · Finance
The outgoing invoice from sales and the incoming invoice from procurement are different documents, yet they enter the same journal and the same tax records. Record-to-Report picks both up as a single stream.
- RevenueInvoice
- ProcurementInvoice
- FinanceDocument
Parallel chains, not one line
A company is not a linear process: procurement does not always follow a sale, production does not always follow stock, service is an independent flow. So the Atlas lays Lead-to-Cash, Procure-to-Pay, Plan-to-Fulfill and Record-to-Report side by side, and reveals the crossings on shared nodes — stock, invoice — progressively instead of tangling them into one picture.
Live state on the node
Every node shows how many documents are active, what is waiting for a decision, what is late, how the integration stands and how much was processed automatically. Semantic colour is used only for status, risk, delay and success — there is no decorative colour per module, because it would also colour everything that is fine.
The intelligent layer runs through everything
Insights, automation and AI are not one of the chains but a layer that runs through all of them. The thread appears where something was handled automatically or where a conclusion has a provenance — and nowhere else. That is also why you can see what the system did on its own without opening a separate report.
A perspective per role
A director, finance, sales, procurement, logistics, production, HR and an administrator do not get the same map with a different filter — the Atlas narrows the chains to the ones the user actually takes part in, and shows their responsibilities, decisions and blockages. Users with broader rights switch perspective; personalisation never bypasses authorization.
What NG One did on its own
Every ERP can produce a document. The real question is how many documents were produced without a person, how much of the bank statement matched itself, and how many hours that returned. NG One measures that and shows it as a KPI, in the same place where the work happens — automation that is not measured is a promise, not a result.
Rules instead of routine
Event → condition → action, configured in the console without a developer: a delivery notice to the customer, a replenishment proposal, a dunning letter on due date, escalation of a task that breached its SLA, a recurring invoice under a contract. A rule has an effective date and a version, so it is always known which rule produced what.
Approvals with limits and a trail
Multi-step approvals with amount limits, branching and substitutes, maker-checker on sensitive actions, delegation for absences, bulk approval for what repeats. Nothing passes outside the rules, and who approved what, when and under which limit stays in an immutable log.
Matching you can see
Automatic bank statement matching by reference model, amount and partner; three-way matching of purchase order, goods receipt and invoice; duplicate invoice checks before posting. What the system cannot match, it hands to a person with an explanation of why it could not — a quiet guess is worse than an unmatched line.
An automation centre that reports on itself
One screen with the active rules, execution history, successes and failures, and time saved. Automation nobody can see does not earn trust, and a rule nobody watches becomes a silent error — so every execution is recorded, the ones that worked and the ones that did not.
What it looks like in the morning
Carried by AI or automation- Good morning. Today you have 6 decisions, 3 collections at risk and 2 documents that do not reconcile.
- Since your last sign-in NG One has posted 47 documents automatically and matched 83% of the bank statement.
The message is an illustration from the demo tenant. It shows the shape of the briefing and the path behind each number — not a measured outcome in your company.
NG One orchestrates the family rather than replacing it
Konis Software already has products that work in their own areas: NG Commerce as an eCommerce operating system, NG Sara as an autonomous sales AI agent, NG Nora as an AI voice and chat agent, NG eFiscal on the fiscal channel, and NG Operations in manufacturing planning and execution. NG One is the core beneath them — it takes in their events, posts them, reconciles them, and returns the data they do not hold themselves.
- eCommerce operating system
NG Commerce
Enterprise eCommerce Operating System
Every sales channel, checkout, fiscalization and fulfilment — the customer-facing side of the business.
Exchange with NG One
- An order placed in the storefront becomes a sales order in NG One — nothing is retyped.
- Stock, price lists and discount policy from NG One are the source of truth for the catalogue and checkout.
- The delivery note and the invoice are issued and posted in NG One; the storefront shows the customer their status.
- A return from the storefront opens a stock return and a credit note in NG One.
- Manufacturing planning and execution
NG Operations
Manufacturing Planning & Execution (ERP / MRP / MES)
The planning layer between the ERP and the warehouse: demand into a plan, plan into work orders, work orders into execution.
Exchange with NG One
- Items, bills of materials, customers and suppliers come from NG One and remain governed there.
- Confirmed sales orders from NG One enter the sales plan as firm demand, not an estimate.
- Purchase order proposals from MRP return to procurement in NG One and pass approval before reaching the supplier.
- Material consumption and reported output are posted to stock and to the general ledger in NG One.
- Autonomous AI sales agent
NG Sara
Autonomous AI Sales Agent
Spots the opening in existing and new accounts and carries it through to an offer — on the channel the customer actually uses.
Exchange with NG One
- Purchase history and Partner 360 from NG One decide who Sara approaches, and with what.
- Credit limits and open items from NG One stop an offer to a customer who is late paying.
- Opportunities and activities Sara opens sit in the NG One sales pipeline, on the partner and on the document.
- An accepted offer becomes a sales order in NG One, together with the decision trail that produced it.
- AI voice and chat agent
NG Nora
AI Voice & Chat Agent
Answers inbound calls and messages and resolves the request while the customer is still on the line.
Exchange with NG One
- Nora reads stock, price and order status from NG One while the customer is on the line.
- Orders and reservations from a conversation are created as documents in NG One, under the same rules as if a salesperson had entered them.
- A complaint logged during a call opens a case in NG One, with the transcript attached.
- A handover to a live agent leaves a task in NG One carrying the call context — the person does not start from zero.
- Electronic fiscalization (ESIR class 3)
NG eFiscal
Electronic Fiscalization (ESIR class 3)
Software fiscalization of every settled sale through the tax authority's V-PFR — no register, no printer, no extra device.
Exchange with NG One
- Settled retail turnover from NG One goes through V-PFR and returns with a fiscal number and QR code.
- The fiscal receipt is linked to its outgoing invoice in NG One and enters the tax records.
- Advances, refunds and reversals from NG One travel the same path and get their own fiscal record.
- The immutable record of issued receipts is the basis for the KEP book and tax records in NG One.
Every card answers two questions: what the product does and what exactly it exchanges with NG One. A company already running one of them does not start over and does not switch off what works.
Regulation is not a module on the side
A statutory obligation in Serbia does not sit at the end of a process — it is part of the document from the moment the document exists. So the chart of accounts, tax rates, deadlines and mappings are effective-dated parameters in the core: the past is computed under the rules of the past, and a change made in July does not rewrite a correction from March. Below are the six obligations that most often decide which system a company buys — each named explicitly, because a regulation has a name, a form and a deadline.
SEF — outbound and inbound e-invoices
Sending outbound and receiving inbound invoices through the national e-invoicing system, with statuses and document lifecycle inside the system rather than in a separate portal.
Exchange uses the UBL 2.1 format the platform requires. An inbound invoice is accepted or rejected within the statutory window, and the deadline sits on the document itself — not in somebody's reminder. Public-sector receivables go through the central invoice registry, from that same document.
VAT records (EEO, EPP), POPDV and PP PDV
An internal VAT engine with the record structure, POPDV and PP PDV XML output, and period-versioned mapping — correcting an old document follows the rules that applied then.
The EEO and EPP records are records, not a report assembled at the end: a document enters them when it comes into existence, so POPDV and PP PDV are read out of the ledger rather than retyped into a spreadsheet against the deadline.
E-fiscalization — ESIR, LPFR and VPFR
The retail fiscal channel: a receipt is fiscalized through the local (LPFR) or virtual (VPFR) processor, and the fiscal slip stays tied to the invoice, the stock movement and the posting inside one system — with no till that has to be reconciled against inventory at closing time.
Retail costing and the KEP book work over the same item and the same stock as wholesale, so the retail price, the KEP entry and the fiscal receipt cannot drift apart.
Payroll and PPP-PD filing
Serbian statutory payroll, PPP-PD XML, the sick-leave record structure, contracts and positions, travel orders and employee self-service — part of the core, not a localization package.
The sick-leave and social-insurance registries are named channels, not a generic “HR integration”. Payslips are retained permanently — that is a statutory obligation to the employee, not a retention setting somebody can shorten.
Electronic delivery notes
The electronic delivery note as part of the fulfilment flow, linked to the sales order, the stock movement and the invoice — one document, one trail, no re-entry in a separate application.
The delivery note is created at the moment of dispatch, out of the same shipment that moves the stock — not reconstructed from the invoice at month end, when nobody remembers how the goods actually moved.
APR — statutory financial statements
Annual financial statements with the submission file, produced from the same ledger that produces the trial balance — not assembled in a spreadsheet outside the system.
The trial balance, the financial statements and the corporate income tax return all come out of the same ledger, with fixed assets and depreciation inside it. The close happens once, not three times in three tools that then disagree.
The decisions made before the first line of code
Some things in an ERP cannot be retrofitted — they are in the foundation or they are absent. These six decisions are in the foundation of NG One, settled before the first report was written, because none of them can be added later without reposting history. That is precisely why systems that grew over twenty years do not have them in the core: what they lacked was not intelligence but the opportunity.
Multitenant with isolation in the database
Data isolation at the database level (RLS), several legal entities inside one tenant, multi-currency, and the accounting-firm mode anticipated from the start. The control plane is separated from the data: platform staff see tenant health, not business records, and support access requires the client's approval and stays audited.
Dimensional accounting from the first entry
Cost centre, project, plant, sales channel and bearer are part of the ledger line, not a field added afterwards. The report by project comes out of the same ledger as the trial balance and always agrees with it. Entries posted without a dimension cannot acquire one without reposting — which is why the decision belongs in the foundation.
Effective-dated statutory parameters
Every rate, threshold and mapping carries an effective date and a version. A correction to a March document is computed under March rules even after the regulation changed in July, and the posting references the rule version that produced it. In a country where tax rules change mid-year, that is a condition of accuracy, not a convenience.
API-first, with integrations kept apart
REST and OpenAPI over every function, a job queue, notifications by email, SMS, Viber and push, MCP-ready from the start. Domain flows are connected into one graph, but every external channel — e-invoicing, bank, fiscal service — stays a separate adapter with its own lifecycle: one service failing does not take the flow down with it.
Clean core and versioned configuration
Adaptation goes through effective-dated configuration and through extensions that do not touch the core, so an upgrade stays an upgrade rather than becoming a migration. Configuration sets, provisioning without developers, and an audit of every settings change — plus import and export with a dry-run diff and per-row errors instead of the message “import failed”.
Dense tables, two themes, three screen modes
Desktop-first dense screens for transactional work, a responsive view for the road, and handheld terminal operation for the warehouse. Every list has column toggles, an advanced filter with operators, saved views per user, Excel export and footer totals. Light and dark from day one, density per user — because people spend eight hours in this.
What is NG One?
NG One is Konis Software's business system for the Serbian market — an ERP in which the intelligence layer is part of the core rather than an add-on. It covers work across nine business areas: my work, sales and customers, procurement and suppliers, inventory and logistics, production and operations, finance and compliance, people and organisation, documents and processes, and insights with automation and AI. Underneath sit around sixty technical domains, 270 named capabilities and one graph of data, so goods, money, regulation and labour are not tracked as three separate truths. The goal is narrow and measurable: cover both the Serbian statutory half that foreign systems lack and the modern modules that local systems lack — on one platform.
What does the early-access programme offer?
The programme runs until 1 September 2026 and carries a 40% discount on the solution price, against a 10% reservation advance. The discount is the smaller part of the value. The larger part is influence: your chart of accounts, the dimensions you report on, your documents and your tax mappings enter the configuration early, while the room for those decisions is still being set. That is not a formality — a dimension that has entered the ledger does not change without reposting history, so how you will report for the next ten years is a technical decision rather than a contract line. Early access is where it gets made with you in the room.
What does NG One cost?
Pricing is determined on request, after a review of scope — and that is a consequence of the model rather than an evasion. Licensing follows the type of user, not headcount without distinction: someone posting all day, a warehouse operator on a handheld terminal, and an employee who files one travel order a month cannot reasonably cost the same. On top of that, what not every company needs is licensed granularly — shop-floor and warehouse terminals, the self-service portal, AI credits. So a conversation about price is a conversation about your scope: how many people, in which roles, which modules and which integrations.
Cloud or on-premise?
Cloud is the default and where the system works best: data isolation sits at the database level, every tenant has its own environment, and upgrades arrive without a project. An on-premise licence exists in the licensing framework, together with usage metering and entitlements — a licence model is not something you rework afterwards without consequences for every client, so it was settled in the foundation. One consequence of the cloud model matters more than the rest: the line platform staff do not cross. The control plane sees tenant health and consumption, not business data, and support access requires your approval and stays in the audit log.
Does NG One replace everything we run today?
Not necessarily, and that is deliberate. NG One is a core that orchestrates: it takes events from systems that work well, posts them, reconciles them and returns data those systems do not hold. If your storefront, fiscal channel or shop-floor operation already works, there is no reason to switch them off for the core to function. What NG One does claim for itself is one place of business truth — the ledger, stock, partners and regulation have to live together, because that is exactly where the difference that a spreadsheet otherwise absorbs gets made.
How does NG One fit with NG Commerce, NG Sara, NG Nora, NG eFiscal and NG Operations?
As the core of the family, not as their replacement. NG Commerce runs online sales and sends orders, shipments and payments into NG One; NG Sara, an autonomous sales AI agent, works over the customers and opportunities NG One maintains; NG Nora takes inbound conversations and needs the same context about the customer, stock and price; NG eFiscal holds the fiscal channel; NG Operations plans and executes manufacturing. Each exchanges a specific, named set of data with the core, and the ecosystem page states for every product both what it does and what it exchanges — rather than offering “it is integrated” as an answer.
Does NG One cover Serbian regulations?
That is the product's primary measure of success, not a line item on a feature list. The Serbian chart of accounts, the posting engine and effective-dated statutory parameters sit in the foundation. The VAT engine keeps the EEO and EPP records and produces the POPDV and PP PDV XML; the ledger works with dimensions, with receivables and payments alongside it. Payroll runs with PPP-PD, sick-leave and social-insurance filings. APR financial statements, fixed assets and corporate income tax come out of the same ledger that produces the trial balance. SEF sends and receives invoices, the electronic delivery note follows the shipment, the central registry carries public-sector receivables, and the fiscal channel runs through LPFR and VPFR. Every one of those obligations is named explicitly on the compliance page: “compliant with local legislation” is not an answer, it is a way of avoiding one.
What does migrating from Pantheon or Business Central look like?
A project of its own with its own artefacts, not an import at the end of the rollout. There are templates for partners, items, opening balances, stock by lot and open documents, plus mapping of old codes onto new ones. A trial migration runs first, then reconciliation with control totals: the trial balance, open items and stock from the old system must agree with the new one before the cutover is confirmed. Rollback is part of the plan, not an improvisation on a Saturday night. The chart of accounts and the choice of dimensions demand the most attention — that is where you decide how you will report for the next ten years.
See NG One against your own processes
Book a working session. We go through your flows, your documents and your statutory obligations, and show where NG One fits alongside what you already run and what it replaces. The conversation is technical: screens, postings, regulations and your questions — no slides full of logos.