NOVERA.Software

10 · Status

Where each module stands.

ModuleStateNote
Financial coreLive in productionPosting, banking, allocations, periods and multi-currency in daily use
Slovak VATLive, filings acceptedReturn, control statement and both XML exports; submission remains manual by design
Reporting18 reports liveCurrent work: matching the remaining reports to their originals
Document AILiveLearning store runs with a built-in rule set; its table is optional
Email & AI triageLiveMailbox, triage, translation and the supplier invoice queue
InvestmentsBuilt, schema pendingPhase one complete; general ledger posting and broker import scoped to phase two
MessagingBuilt, schema pendingCore and realtime delivered; reactions, search and templates follow
Notifications & pushBuilt, schema pendingPlatform complete; needs its tables and a key pair to go live
Planner & notesLive, extendingCalendar search and rich detail shipped this month

Platform description

Where the system stands

NOVERA v2.0 is live, carrying real users and real filings, and the parts of it that matter most have been verified against reality as well as against tests. The trial balance was checked against the previous system over seventy-two accounts and returned no differences. The VAT filings were specified from six accepted submissions. The document reading rules reproduce the company's own worked examples to the cent. The occupancy report now reconciles line for line with the report it replaces.

Waiting on schema scripts. These modules are complete in code and leave their not-yet-configured state once their scripts are run:

  • notifications and Web Push;
  • messaging;
  • parts of investments;
  • the AI lesson table.

Nothing is lost by the wait, and each screen says clearly that it is not switched on for that entity yet.

Four open items to keep in view:

  • A database index on the ledger table. It is the permanent fix for the settlement lookups behind the paid and settles indicators. Without it those queries scan, and on a growing ledger they will eventually exceed their time limit and fail without any visible error. It is a schema change and so waits on the owner's approval.
  • The SQL testing blind spot. The build container runs no database, so query changes are proved by inspection and by static assertion until they run on the live catalogs. This has caused real defects before. The method accounts for it, but it remains the weakest point in the chain.
  • Reproducing a filed VAT return. A filed return cannot currently be reproduced after an amendment, because the boxes are recomputed live and the submitted XML is not stored. Storing the filed figures would close it.
  • Source control. The project is not under source control. That was a considered decision, and the hash and baseline discipline exists to compensate, but it remains the one area where a mistake is hardest to undo. It should be revisited when there is a quiet week.

Next: the reporting shelf, which is where the next round of work resumes.