Traceable events, separated customer data and clear permissions. Built into how Kapit works.
Role-based access, two-factor authentication and BankID for administrator sign-in. Sensitive actions, such as manual adjustments and payment runs, require approval by a second person.
Prepares the documentation
Reviews and approves
The action is logged with the user and a reference.
Financial events are stored without overwriting previous entries. Balances and reports are calculated from the same events.
Amounts are handled as whole öre, the Swedish currency's minor unit. Event keys protect against duplicate posting. Rebuilds have run IDs and source references. Missing documentation is shown as missing.
Customer data is separated across the system's layers. Disabled modules remain blocked even when someone uses a direct link.
Separation covers queries, snapshots, logs, queues and cache keys. Modules can be used independently.
AI can analyse and suggest. It must never create a financial event, change a snapshot or hide missing data.
Every run is logged. Write access is disabled by default and requires the relevant module, permission and confirmation for each action. Forecasts are labelled as forecasts.