The questions we actually get, with the answers we actually give
This page collects them. Questions about a specific business space, about pricing or about the early access program live on their own pages; here are the ones that come up regardless of topic — including the handful whose answers are not pleasant.
- Product
- Implementation and pricing
- Technology and security
- Regulation and integrations
Product
What NG One is, what it covers, and how it relates to the other products.
What is NG One, in one sentence?
An ERP that runs a company's finance, purchasing, sales, inventory, manufacturing, people and documents, with an AI layer that works inside every flow rather than sitting as a separate screen. The difference from what is on the market is not the module count: it is that Serbian regulation and modern modules live in the same core, instead of one being in the system and the other in an add-on.
Who is NG One for, and who is it not for?
For companies that have outgrown separate programs and the spreadsheet holding them together: distribution, manufacturing, services, projects, several legal entities, a warehouse whose contents genuinely have to be known. Not for a three-person company with one warehouse — there a spreadsheet is the rational choice, and we will say so at the first meeting. Nor for a company that wants a system switched on without a migration and without a look at its processes: an ERP introduced that way is being run from a spreadsheet beside it within a year.
How big is NG One?
Nine business spaces, around sixty technical domains beneath them, and 270 named capabilities — thirty per space, each with a description of what it does. Eight end-to-end processes run through them: 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. The user never sees a list of sixty items: the navigation rail never goes deeper than two levels, and work is divided the way the work actually divides rather than the way the code was written. Every one of these numbers can be counted on this site — which is why they are here instead of adjectives.
Does NG One replace NG Commerce, NG eFiscal and the rest?
No. It orchestrates them. A receipt from an NG eFiscal till becomes a posting and a tax record, an order from NG Commerce becomes a sales order and a stock reservation, a work order from NG Operations becomes a cost and an invoice. Every link is a separate adapter with its own lifecycle. A company already using those products switches nothing off to get an ERP.
When can we start?
The first step is a survey: an hour about your processes. It produces a written scope, and the offer goes against that scope. After signature come configuration and the trial migration — with a per-row diff and control totals reconciled before the cutover. The go-live date is set against the scope, not against a wish: most of the time goes into your data and your integrations, and that part does not get faster by being skipped.
Implementation and pricing
What happens between the first conversation and the day people work in the system.
What do you need from us to produce an offer?
An hour of conversation and access to your typical documents. Specifically: what you do, how many legal entities you have, how many people genuinely open documents versus only approve them, which systems you run today, which documents pass through the company, and what your approval chain looks like. From that we write a scope, and the figure goes against the scope. There is no forty-question survey before the first conversation.
How long does implementation take?
It depends on scope, and anyone giving you a number before seeing your processes is guessing. What we can say is where the time goes: the largest part is not configuration but data — mapping legacy codes, opening balances, open items, lot-level stock — and reconciling control totals after the trial migration. That is why migration is planned first, not last. The second large part is integrations: each is a separate adapter with its own credentials and certificates, and each needs testing against your legal entity.
What happens to the data in our current system?
It migrates through templates: partners, items with units of measure and barcodes, opening balances, open customer and supplier items, lot and serial stock, open documents. Legacy codes are mapped and kept, so a document from the old system can still be found after the switch. Migration runs as a trial first, with a per-row diff and control totals that get reconciled before anything goes live. If they do not reconcile, the cutover does not happen — there is a way back.
Can we try it first?
Yes. A demo tenant with twelve months of turnover exists, and we walk scenarios through it against your processes — dimensional posting, picking, the VAT ledgers, AI suggestions, automation and signing. A trial tenant loaded with your own data comes once there is an agreed scope to test: before that we would be testing someone else's numbers, which proves nothing to anyone.
Technology and security
Where the data lives, who can reach it, and what happens if you leave.
Where is the data — in the cloud or with us?
Wherever you decide: cloud, your server, or a hybrid. The on-premise license is a granule, not a different product — same code, same model, same updates. The difference is who holds the server, the backups and the restore procedure. In the cloud we hold them, with point-in-time recovery and a restore drill that is actually run rather than merely documented.
Who at Konis Software can see our data?
Nobody, until you approve access. Support enters your tenant only with your approval, and every such entry is audited — who, when, for how long, and what they looked at. Platform staff, who manage tenants and licenses through the Control Center, do not see business data at all: the boundary between control plane and data plane is hard and part of the architecture, not an internal rule honoured out of goodwill.
Is there an API, and can we integrate ourselves?
Yes. REST with an OpenAPI spec over everything in the system — no module is reachable only through its own screen. Alongside it there is a job queue for long-running work, notifications, and an MCP-ready layer. If you have your own developer or partner, you need nobody from us to connect. The API is not an addition on top of the screens but the layer the screens themselves run on — which is why there is no list of exceptions.
What if we decide to leave?
You export everything and leave. A full tenant export exists as a capability, alongside tenant shutdown and legal hold for cases where data must be retained by order. Excel export is on every list, and the API is open over all of it. A system that keeps you by making the exit hard is not dependable but capturing, and that difference only becomes visible when it is too late.
Regulation and integrations
Serbian regulation, government services, and the boundaries worth knowing up front.
Does NG One support the e-invoicing system?
Yes, in both directions. Outbound invoices go to SEF as UBL 2.1, inbound invoices arrive through the same channel, and the VAT ledgers are filed in the EEO and EPP structures. POPDV, PP PDV, e-delivery notes and CRF sit alongside them. Each of those services is a separate adapter with its own credentials and certificates, even though they are connected in the same domain graph — an outage at one government service does not take the others down and does not stop posting. That split is deliberate: government services go down, and that gets designed for in advance rather than after the first outage.
Does NG One run payroll?
Yes. Payroll, PPP-PD filings, travel orders, absences and employee self-service run in the People and organisation space, and the links to CROSO and e-sick-leave run as separate adapters. The statutory parameters — rates, tax-free amounts, thresholds — are not constants in code but data carrying validity dates. So a mid-year change of law is handled by an entry rather than an upgrade, and a March payroll stays a payroll under March's rules.
What about fiscalization and the link between the fiscal receipt and e-invoicing?
Fiscalization runs through both channels, LPFR and VPFR, and the POS and the retail ledger sit in the core. The fiscal receipt and e-invoicing are connected in the same graph: a receipt from the till becomes a posting and a line in the tax ledger, not a second entry in a second program — and that is exactly the kind of link that is expensive to add afterwards. Companies already running NG eFiscal do not change the till; the core connects to its ESIR channel through an adapter.
Is the electronic signing in NG One a qualified signature?
These are two different things, and this is the most important distinction on the whole site, because the two get confused constantly. Internal approval and decision signing run on the workflow kernel: the signature is audited, it is known who signed, when, and against which version of the document, and the document cannot be silently altered after approval. That is control inside the company and it is sufficient for that — but on its own it is NOT a qualified electronic signature in the regulatory sense. A qualified signature, a legal entity's seal and a qualified timestamp are issued by no ERP but by a registered trust service provider — Pošta, PKS, Halcom and others. NG One binds to your issuer's certificate and to a timestamping account, for e-signing, the e-archive and filings. The certificate is yours, not ours, and that is the only correct division — the difference between evidence and a file.
How do you handle rule changes that take effect mid-year?
Through effective-dated statutory parameters. Rates, limits, mappings and forms are not constants in code but data with a validity date, and every transaction carries a reference to the rule version it was created under. When something changes in November, a correction to a March document follows March's rules, not November's. That decision cannot be added later without reposting history — which is why in NG One it sits beneath the first posted line rather than above it.
The answers describe the system and change with it. If an answer reads as too general for your case, ask — a specific question is answered by whoever designed that part of the system.
Your question is not here?
Send it. If the answer is useful to others, it will end up on this page.