Complete operational scope
Housing community management software — records, finances, documents, resolutions and cases
A feature list is useful only when the parts form a coherent process. WM Administrator is designed so that a user can move from source data to a result, decision and later evidence.
Units, owners and ownership shares
The register underpins most later operations. It should retain not only the current state but also the history required to explain older settlements.
The scope includes units, owners, ownership shares, relationships and controlled data import. A change of owner or share should not erase information needed to reconstruct an earlier period.
Charges, balances and funds
A charge should show the period, basis, rule and result. Preview before publication helps detect an incorrect total, missing input or unexpected change.
A balance should lead to the operations that changed it. A correction should not silently overwrite the historical state.
Documents, resolutions and cases
A contract, invoice, resolution or report should not be detached from the process it concerns. A document can be linked to a case, deadline, decision and responsible person.
For resolutions, the relevant elements include the wording version, eligible owners, votes, result and subsequent execution.
Controlled import before publication
Import should not mean “upload everything”. A safe flow shows mapping, errors and control totals before the imported data becomes the operative state.
If a record cannot be assigned unambiguously, the process should stop for that case rather than guess.
Roles, MFA and control of significant operations
A user should see only the scope required by their role. Shared accounts weaken accountability.
Selected higher-risk actions can require fresh identity confirmation or independent approval where the organisation’s process calls for it.
Audit trail and export
The audit trail should answer who, when, in what context and what changed. It does not replace the source document, but it helps reconstruct the operation.
Complete export is part of the normal data lifecycle, not an emergency feature at the end of a contract.
Optional modules
Depending on the current plan and production configuration, separate modules may provide accounting/OCR, online voting and procurement functions. Before publishing any specific claim about KSeF or JPK, Codex must verify the current production state and public contract because the repository contains both historical MVP documents with those integrations disabled and later full-feature implementation evidence.