Governance

Control and traceability—built into the platform

When multiple users work with budgets, forecasts, consolidation, and reporting, it must be clear who has access to which data, who can change it, and who is responsible for approval.

PLANNORS integrates roles, access control, approvals, history, and audit trails into the platform, enabling Finance to create structure around both data and processes—without making the work unnecessarily burdensome for users.

.infocard-block .card-preheader-icon{width:44px;height:44px;flex:0 0 44px}.infocard-block .card-preheader-row{margin-bottom:18px}@media (max-width:767px){.infocard-block .infocard-block__grid:has(.infocard-block__card:nth-child(4)):not(:has(.infocard-block__card:nth-child(5))){grid-template-columns:1fr!important}} /* kompakte kort: ikon og titel på samme linje, tekst rykket op (Sophie 9/9) */ .infocard-block__card:has(.card-preheader-icon){min-height:0} .infocard-block__card:has(.card-preheader-icon) .infocard-block__card-content{padding:22px 24px 24px} .infocard-block__card:has(.card-preheader-icon) .infocard-block__card-content>div:first-child{display:flex;flex-wrap:wrap;align-items:center;column-gap:14px;row-gap:12px} .infocard-block__card:has(.card-preheader-icon) .card-preheader-row{margin:0;flex:0 0 auto} .infocard-block__card:has(.card-preheader-icon) .card-preheader-row .card-preheader{display:none} .infocard-block__card:has(.card-preheader-icon) .card-title{font-size:18px;line-height:1.25;flex:1 1 0;margin:0} .infocard-block__card:has(.card-preheader-icon) .card-text{flex:0 0 100%;margin:0} .infocard-block__card:has(.card-preheader-icon) .card-text p{margin:0}

Who can view, change, and approve what?

Governance is not only about access to the system. In PLANNORS, roles and permissions can control access to relevant data and functions, while approval flows create structure around approvals, and history and audit trails support control of changes.

This gives Finance a clearer basis for managing accountability and access across the organisation.

Overview

Governance in PLANNORS—from access to history

Governance should not be an extra control task alongside Finance processes. It should be part of how users work.

In PLANNORS, governance can be embedded from each user’s access and responsibilities through approval and subsequent history. This creates structure around who works with which data, who is accountable, what has changed, and how the process has progressed.

@media (max-width:991px){.pl-figur picture{display:block;max-width:560px;margin:0 auto}}Governance in PLANNORS consists of four components around a shared core: Permissions and roles, Approval flows, Audit trails, and Versioning and history—security, control, and trust.

Roles & Policies

Control which data, functions, and processes each user can work with. Role-based access can be applied across, for example, companies, departments, cost centres, reports, and planning processes.

Users · Roles · Access levels

Two ways to manage access. Roles group permissions by job function, for example administrator, controller, and budget owner. Policies, or access rules, determine access based on specific conditions, for example that a user may only edit their own department when the budget is open. The examples are configured according to the company’s own structure.
#pl-gov-roller-m{display:none}#pl-gov-roller-m svg{display:block;height:auto;width:100%;max-width:420px;margin:0 auto}@media(max-width:991px){#pl-gov-roller-m{display:block}#pl-gov-roller img{display:none}#pl-gov-roller .text-media-block__column–center{display:none}}
Roller og policies i PLANNORSTo måder at styre adgang på. Roller samler rettigheder efter arbejdsfunktion, for eksempel administrator, controller og budgetansvarlig, og er enkle at administrere og gennemgå. Policies, eller adgangsregler, afgør adgang ud fra konkrete betingelser, for eksempel at en bruger kun må redigere egen afdeling, når budgettet er åbent, og giver en fleksibel og præcis afgrænsning. Eksemplerne sættes op efter virksomhedens egen struktur.TO MÅDER AT STYRE ADGANG PÅRollerSamler rettigheder efter arbejdsfunktionAdministratorControllerBudgetansvarligEnkelt at administrere og gennemgåPolicies (adgangsregler)Afgør adgang ud fra konkrete betingelserMå kun redigere egen afdeling, når budgettet er åbentFleksibel og præcis afgrænsningEksempler. Roller og policies sættes op efter jeres egen struktur.

Approval flows

Create structured approval processes around budgets, forecasts, and other planning activities. Accountability, status, and approvals can be tracked throughout the process.

Workflow · Status · Approvals

@media (max-width:991px){.pl-figur picture{display:block;max-width:560px;margin:0 auto}}Approval flow in four steps: 1. Creation, 2. Submission, 3. Review, 4. Approved and locked—status, accountability, and approvals are visible throughout.

Audit trails

Track changes with information about who changed what and when. The audit trail provides documentation and makes it easier to understand the development from previous to current values.

Who · What · When · Before/After

Audit trail: every change is automatically logged with who, what, when, and old and new value—full traceability.
#pl-gov-audit-m{display:none}#pl-gov-audit-m svg{display:block;height:auto;width:100%;max-width:420px;margin:0 auto}@media(max-width:991px){#pl-gov-audit-m{display:block;padding-top:48px}main > .block:has(img[src*=”plannors-gov-audit”]){padding-bottom:0 !important}.text-media-block__column:has(> img[src*=”plannors-gov-audit”]){display:none}}
Audit trail: hver ændring logges automatisk med hvem, hvad, hvornår og gammel og ny værdiFuld sporbarhed: hver ændring logges med bruger, ændring, tidspunkt og værdien før og efter.HVEMHVADHVORNÅRFØR → EFTER

Versioning & history

Preserve previous versions of budgets, forecasts, and scenarios, and compare developments over time. This makes it possible both to retain an approved budget and continue working with new forecasts and assumptions.

Versions · Scenarios · Comparisons

#pl-gov-versioner-m{display:none}#pl-gov-versioner-m svg{display:block;height:auto;width:100%;max-width:420px;margin:0 auto}@media(max-width:991px){#pl-gov-versioner-m{display:block;padding-top:48px}main > .block:has(img[src*=”plannors-gov-versioner-v2″]){padding-bottom:0 !important}.text-media-block__column:has(> img[src*=”plannors-gov-versioner-v2″]){display:none}}
Versionsstyring: budgetter, forecasts og scenarier gemmes i versioner og kan sammenlignes over tidBudget: version 1, godkendt og låst. Forecast: version 2, justeret løbende. Scenarier: version 3, budgettet står urørt.SAMMENLIGN OVER TIDBudgetVersionGodkendt og låstForecastVersionJusteret løbendeScenarierVersionBudgettet står urørtTID

AI & GOVERNANCE

AI on Finance data requires governance

Financial data is among the company’s most sensitive information. When AI becomes part of Finance, access to data and functionality must therefore still be managed within the company’s governance.

In PLANNORS, AI is integrated into the platform and can support work such as identifying variances, understanding developments, and creating a better basis for analysis and forecasting.

This means AI does not have to be a standalone tool alongside Finance processes, but can be part of the platform where Finance already works with data, access, and governance.

AI Finance

THE RESULT

Governance should create control—not more administration

Governance is not an end in itself. It should enable Finance to work efficiently with the company’s financial data and processes, while access, accountability, approvals, and changes can be managed.

This creates a stronger foundation for budgeting, forecasting, consolidation, reporting, and analysis—and for introducing automation and AI into Finance in a controlled manner.

Icon: Governance

Control over access

Control who can view and work with relevant data and functions.

Icon: Log

Clear roles and responsibilities

Create clarity around responsibilities, permissions, and approvals.

Icon: User

Structured approvals

Use approval flows to create structure around Finance processes.

Icon: Data foundation

History and audit trails

Track changes and history so Finance gains better insight into what has been changed.

Icon: Process

More efficient workflows

Structure workflows and reduce the need for manual steps and coordination.

Icon: Chart

Governance around AI

Bring AI into Finance with access and governance as part of the foundation.

FAQ

Frequently asked questions

Four of the questions we are most often asked about governance. The rest are on the FAQ page.

Yes. PLANNORS has audit trails that make it possible to track changes and see, among other things, who made a change, what was changed, and when the change was made. This provides Finance with documentation and traceability throughout the process.

PLANNORS supports approval flows for, among other things, budgeting and forecasting. Roles, status, and responsibilities can be defined in the process, so it is clear who must provide input and who must approve.

Yes. PLANNORS preserves versions and history, so budgets, forecasts, and scenarios can be compared over time. An approved budget can thus be retained, while new forecasts and scenarios are developed based on changed assumptions.

Role-based security, audit trail, version control, Row Level Security, Single Sign-On, and Multi-Factor Authentication are included across PLANNORS editions. Approval functionality depends on the edition, where Professional supports simple approval flows, while Enterprise provides access to more advanced workflows.

Next steps

Gain control without making processes heavier

Book a demo and see how PLANNORS works with roles, permissions, approval flows, audit trails, and versioning as an integrated part of Finance processes.