Skip to content

ERPNova Cognitive

An ERP that serves many companies from the same codebase and adds optional intelligence on top.

Vertical: Business management and finance Solid base

What it is for

Run a company’s entire operation — finance, people, customers, processes — with a system that can serve many companies at once.

What it does

A common core that knows nothing about any specific industry, plus an ecosystem of add-ons that provide the specifics (finance, HR, CRM, verticals, connectors) and an optional AI layer on top.

Sector

Enterprise resource planning software, multi-sector.

What it improves

Traditional ERPs require long, expensive implementation projects per client. This model onboards a new company without duplicating the system, and adds intelligence only for those who pay for it.

Target client

SMEs through distributors, and specific verticals where the add-ons already cover the industry.

Status and maturity

The asset with the most recent development activity in the portfolio. Highly disciplined layered architecture with explicit dependency rules and a proprietary add-on development kit.

Differentiator

Real data isolation between companies at database level, and an add-on ecosystem with versioned contracts that lets third parties build on the platform.

Commercial fit

Subscription per company and per add-on plus channel commission. The realistic route is entering through a vertical where the group already has domain knowledge.

Architecture

Layered architecture

A core that knows nothing about any industry and an ecosystem of add-ons that supply the specifics, with versioned contracts between them. Dependency discipline is what lets a third party build on top without breaking the core.

  1. 01

    Platform core

    Multi-company with database-level isolation and global guards, identity and multi-factor, audit, event bus with retry and dead-letter queue, configuration engine, role-based access control and an administration console.

  2. 02

    Accounting and finance

    Double-entry ledger with a hash chain verified by the database itself, a fiscal engine and a multi-country withholding engine that computes in integers and distinguishes the base by regime.

  3. 03

    Fiscal localisation

    A broad family of per-country add-ons with rate catalogues, issuance and subscription to posted-invoice events delegating to shared logic.

  4. 04

    Operations

    Warehouse, production planning, point of sale, product, customer relationship and orders, all as add-ons on the same core.

  5. 05

    Optional cognitive layer

    Intelligence added above the functional layer and contracted separately: those who do not want it do not pay for it and the system works the same.

  6. 06

    Add-on development kit

    Proprietary contracts, types and utilities so the ecosystem can grow without touching the core.

Inventory

Status per component

A real inventory of the asset’s components with their declared status. We publish capability, never code or internal figures.

Built and testedFunctional with declared debtDesigned, not implementedWired; depends on a third party
  • Multi-company isolation and access control

    Built and tested

    Global guards over row-level isolation; the piece that makes many-companies-on-one-codebase viable.

  • Ledger with hash chain

    Built and tested

    Verified inside the database: editing an entry by hand breaks the chain.

  • Multi-country withholding engine

    Built and tested

    Real computation in integer cents with base by regime, minimum base and declared rounding.

  • Add-on loading in production

    Built and tested

    This was a real blocker: only a handful of add-ons loaded in production. Fixed at the root — shared build configuration and path-based resolution — and today the full catalogue loads.

  • Advanced accounting core

    Designed, not implemented

    Cost accounting, depreciation, bank persistence, warehouse locations and product variants: gaps identified by code audit and declared openly.

  • Per-country electronic signature

    Functional with declared debt

    The kit has real advanced signature, but localisation add-ons do not use it yet except in one country. Stated, not dressed up.

  • Group consolidation

    Designed, not implemented

    The data model exists, the functionality does not. An earlier claim treating it as closed was retracted.

  • Interface internationalisation

    Designed, not implemented

    Pending: the front end is not translated yet.

This profile describes capabilities and status, not implementation. Code, architecture documentation and internal figures are shared under a confidentiality agreement during due diligence.