40% off the solution priceReserve early access
No announcements, no marketing, and nothing written to fill a calendar. This is how NG One works and why it works that way: why dimensional posting has to exist before the first posted line, how an OCR that refuses to guess gets measured, what Serbian regulation demands of a system, and where the international ERP stops. Where a number appears, so does where it came from.
The three that say the most about how the system decides: what the regulation demands of it, what the scope actually costs, and where the limit of what software may claim sits.
Invoicing, VAT records, electronic delivery notes and the invoice registry now share one portal and one certificate — yet they remain four services on four clocks, which is why an ERP that merges them into one module breaks on the first rule change.
Sixty domains is a fact about the architecture; fifty-seven equal menu items is a decision — and a poor one.
Payroll and local documents are not features missing from foreign ERPs; they are a boundary data crosses by hand every month, which is precisely why an add-on does not close them.
Ordered by theme, and by date within a theme. There is no archive by year: a piece on effective-dated parameters does not expire because May has passed — it expires when the rule changes, and then it gets rewritten.
A VAT rate changes once a decade — which is exactly why most systems store it somewhere that makes it impossible, after a change, to prove what was applied to a document from a closed period.
Analysis by project, cost centre and channel is not a report you add when someone asks for it — it is the shape of the journal line, chosen before the first entry is posted.
Isolation between customers is a solved problem; isolation between platform staff and customer data almost never is — and it is built with the same tool and one test.
A matrix of roles and checkboxes answers one of the six questions ERP authorisation has to settle — the other five usually end up in a spreadsheet, a policy nobody reads, and the head of the chief accountant.
Automation is invisible while it works and visible only when it fails — which is why the only honest proof of its value is a counted event no human had to touch.
Inventory accounting answers how much you have; a WMS answers where it sits and who touches it next — and those two questions demand different data models.
A goods receipt dated in the past changes the cost of stock that has already been shipped, invoiced and posted — the hardest problem in inventory accounting.
A single accuracy percentage hides the only thing that costs money: which field was missed, and whether the system stayed silent or filled in its best guess.
Autonomy levels, evidence behind every conclusion and golden-set evals in CI — why the line between a proposal and a posted entry belongs in the architecture, not the prompt.
If something here made you go and check how that stands at your company, the next step is an hour about your documents rather than ours.