Business rules
Business rules describe the requirements and rules that apply to information. Each rule is defined once and referenced from building blocks, patterns and processes.
Appropriate number of employees per manager
VR-ORG-001 · Conditional rule
“A manager shall have an appropriate number of employees.”
Data quality indicator
Managers outside the appropriate span of controlTarget: 0
Affects
One employment in the organization
VR-ORG-002 · Cardinality rule
“An employee has only one employment in an organization.”
Data quality indicator
Persons with several concurrent employmentsTarget: 0
Affects
The manager's business responsibility
VR-ORG-003 · Responsibility rule
“A manager is responsible for the business goals of their part of the business, for their employees, and for costs and revenues according to the budget that applies to the manager's part of the business.”
Data quality indicator
Active employees without a unitTarget: 0
Affects
One manager per unit
VR-ORG-004 · Cardinality rule
“A unit has only one manager.”
Data quality indicator
Units with no manager or several managersTarget: 0
Affects
Units have staff
VR-ORG-005 · Mandatory rule
“A unit always has staff.”
Data quality indicator
Units without staffTarget: 0
Affects
The employee is employed by their manager
VR-ORG-006 · Mandatory rule
“An employee is employed by their manager.”
Data quality indicator
Employees whose manager is not employed in the same organisationTarget: 0
Affects
The manager's organizational employment
VR-ORG-007 · Conditional rule
“An employee who is a manager is, in terms of employment, linked to their own manager's unit. That unit sits directly above the manager's own unit in the unit hierarchy.”
Data quality indicator
Managers not employed in the parent unitTarget: 0
Affects
A manager must have a manager code
VR-ORG-008 · Value rule
“In the digital environment, titles and job names are irrelevant when determining management – people without a manager title can also be managers. An employee is a manager only through a formal manager assignment for a unit and must then have a manager code (A, B or C according to SKR AID). A manager code requires combined responsibility for operations, finance and staff (VEP). People without management responsibility must not have a manager code.”
Data quality indicator
Incorrect manager code assignmentTarget: 0
Affects
Occupation, position and occupation grouping are kept apart
VR-ORG-009 · Value rule
“An employment is linked to the organization's internal position. The internal position belongs to an internal occupation group and is mapped to external occupation code lists and external occupation groupings. External grouping codes never replace the internal position.”
Data quality indicator
Mixed up occupations and positionsTarget: 0
Affects
A process role is not a position
VR-ORG-010 · Value rule
“A process role describes specific tasks in certain activities in a business process and is classified with the Process role code list. A process role is linked to an employee. Some process roles can also be associated with a position, but far from all – an employee with one position works in several processes and therefore holds several process roles.”
Data quality indicator
Process roles registered as positionsTarget: 0
Affects
Not a consultant and an employee at the same time
VR-ORG-011 · Uniqueness rule
“A person cannot be a consultant and an employee in the same organization at the same time. The engagement types employee and consultant are mutually exclusive for the same person at the same point in time.”
Data quality indicator
Concurrent employment and consultancyTarget: 0
Affects
All staff have a position – an engagement type is not a position
VR-ORG-012 · Value rule
“Every employee, both employed and external staff, must have an internal position stating the occupation. An engagement type must never be used as a position or occupation grouping.”
Data quality indicator
Engagement type registered as positionTarget: 0
Affects
A manager must be an employee
VR-ORG-013 · Value rule
“A person with a manager code must have the engagement type employee in the organization. Managerial responsibility cannot be assigned to consultants, agency staff or other engagement types.”
Data quality indicator
Managers without employmentTarget: 0
Affects
A unit can be classified according to several code lists
VR-ORG-014 · Cardinality rule
“A unit can be classified according to several external code lists at the same time, and a code list can be used to classify many units. A unit may have one or more code values within the same code list when that code list's rules allow it. Each code value belongs to exactly one code list.”
Data quality indicator
Units with a primary activity classificationTarget: 100 %
Affects
Classification has its own validity and does not change the unit's identity
VR-ORG-015 · Conditional rule
“Each classification has its own validity period. When a classification changes, the old classification is ended and a new one is started — the unit's identity, name and position in the unit tree remain unchanged.”
Data quality indicator
Classifications without validity or against expired codesTarget: 0
Affects
The code list owner defines external code values
VR-ORG-016 · Responsibility rule
“The owner of an external code list is responsible for its definitions. The information pattern library refers to the code list and never creates its own alternative definitions of external code values.”
Data quality indicator
Locally created values in external code listsTarget: 0
Affects
Every unit has exactly one base cost center for operations, plus additional ones when needed
VR-ECO-002 · Cardinality rule
“Every unit in the unit tree — including grouping nodes such as administrations, divisions and management units — has exactly one primary cost center for ongoing operating costs (base cost center). Additional cost centers may be linked to the unit when separate financial reporting is required, for example government grants or commissioned activities. All cost centers under the unit are governed by the unit's manager.”
Data quality indicator
Units without exactly one base cost centreTarget: 0
Affects
A cost center belongs to exactly one unit and has a stable identity
VR-ECO-003 · Cardinality rule
“Every active cost center belongs to exactly one active unit. The cost center has its own stable identity and validity and can exist across several budget years.”
Data quality indicator
Cost centres with more than one unitTarget: 0
Affects
The financial system is the source of the cost center's existence
VR-ECO-004 · Responsibility rule
“The financial system is the authoritative source for which cost centers exist. The organisation description is authoritative for which unit a cost center belongs to. No active cost center may lack a relationship to a unit.”
Data quality indicator
Cost centres without unit or outside the financial systemTarget: 0
Affects
A budget is time-bound per cost center and budget year
VR-ECO-005 · Uniqueness rule
“A budget belongs to exactly one cost center and concerns exactly one budget year. The combination of cost center, budget year and budget version is unique. The budget separates revenues and costs; net budget is derived.”
Data quality indicator
Cost centres without a budget for the current yearTarget: 0
Affects
Management is shown only by the manager code on the employment
VR-ORG-023 · Value rule
“Who is a manager is shown exclusively by the manager code (SKR AID A, B or C) on the employee's employment, and the manager code implies combined responsibility for operations, finance and staff (VEP). Roles such as assistant, vice or deputy manager are not used in the model.”
Affects
No synonymous positions
VR-ORG-024 · Uniqueness rule
“The internal position code list must not contain synonyms. Each position must represent a unique occupation with its own title.”
Affects
Positions follow titles in external occupation code lists
VR-ORG-025 · Value rule
“The title of an internal position must follow the title of the occupation in the external occupation code list the position refers to. Local titles are not created when an external title exists.”
Affects
The person's formal competence is validated against operational requirements
VR-ORG-026 · Value rule
“Individuals hold licences, degrees and certificates, which are validated against competence requirements in operations, process roles and positions. Formal competence is never modelled as an internal position of its own.”
Affects
The unit's manager holds the primary budget responsibility
VR-ECO-001 · Responsibility rule
“Financial responsibility is one of the three VEP parts of management according to SKR AID. The employee with the manager code for a unit is also the manager of the unit's cost centers and holds the primary budget responsibility for their budgets. A cost center has exactly one manager. Budget responsibility follows the managerial assignment, not the budget or the cost center.”
Affects
Physical delivery of business services
VR-SRV-001 · Cardinality rule
“A business service can be delivered at zero, one or several physical places. A place is linked to the service only when delivery or consumption requires or offers physical presence at a place the organization has.”
Data quality indicator
Business services without a realising processTarget: 0
Affects
External and internal business services
VR-SRV-002 · Conditional rule
“A business service is either external or internal. External services target customers, citizens or other external recipients and are realised by core processes. Internal services target managers, employees, units or projects and are realised by supporting or governing processes.”
Data quality indicator
Services with the wrong service typeTarget: 0
Affects
A product's identity is independent of the supplier agreement
VR-PRD-001 · Uniqueness rule
“A product is identified by the barcode the producer assigns (e.g. GTIN). Changing supplier or framework agreement must never create a new product.”
Affects
A product in the item catalog is owned by a unit
VR-PRD-002 · Responsibility rule
“Every product in the item catalog must be directly linked to exactly one unit that introduced it.”
Affects
Delivery point, receiving party and workplace are kept apart
VR-GEO-001 · Uniqueness rule
“A physical delivery point is identified with a GLN on the Place building block. The electronic receiving address for invoices and orders (Peppol ID) belongs to the Organisation or Unit, and the statistical workplace (CFAR) belongs to the Statistics Sweden register. The three must never replace each other.”
Affects
Location address and postal address are kept apart
VR-GEO-002 · Uniqueness rule
“A location address according to SS 637006 identifies a physical building or entrance and is linked to Place. PO boxes, freepost and other postal addresses are distribution services and must never be used as the physical location of a place, unit or supplier.”
Affects
A position always states its reference system
VR-GEO-003 · Mandatory rule
“A position consists of coordinates and a stated coordinate reference system from the EPSG register. Coordinates without a reference system are invalid.”
Affects
Geography is external and neutral
VR-GEO-004 · Value rule
“Countries, counties, municipalities and urban areas are defined by ISO and Statistics Sweden and retrieved from there. The organisation links its places and units to geography but never builds its own organisation into it.”
Affects
A customer is always an external party
VR-CUS-001 · Value rule
“The Customer building block is used only for parties outside the own organisation. A unit or administration within the same organisation that receives a delivery is not a customer, even if it is called an internal customer in everyday speech.”
Affects
A process role is assigned to the employee
VR-PRC-001 · Mandatory rule
“A process role is always assigned to an employee – never directly to a person without an engagement and never to a unit.”
Affects
Process roles and activities attach only to the lowest process level
VR-PRC-002 · Cardinality rule
“A process role performs its activities exclusively within the scope of a detailed process at the lowest level. Process roles never attach to higher-level process areas or core processes, and individual activities are not modeled as standalone information building blocks.”
Affects
Process roles end with the engagement
VR-PRC-003 · Conditional rule
“When the employee's engagement ends, all process roles end – and with them the permissions the roles grant.”
Affects
The engagement type can block process roles
VR-PRC-004 · Conditional rule
“Process roles involving exercise of public authority, financial approval or managerial responsibility require the engagement type employed. Other engagement types must not be assigned such roles.”
Affects
Employees get base roles automatically
VR-PRC-005 · Mandatory rule
“The engagement type employed automatically grants base roles for payroll and time reporting, personal development, rehabilitation and work environment.”
Affects
The manager code grants manager roles automatically
VR-PRC-006 · Responsibility rule
“An active manager code automatically grants the manager roles payroll and time approver, development talk lead, rehabilitation lead, work environment lead and recruiting manager for the own unit.”
Affects
Delegation is done as a process role
VR-PRC-007 · Responsibility rule
“A manager who delegates tasks does so by assigning a process role, with a validity period and any amount limit. Delegation never creates a deputy manager or a new node in the organisation tree.”
Affects
The position can grant process roles automatically
VR-PRC-008 · Value rule
“A position can grant process roles automatically for standard assignments that everyone in the position performs. Additional roles that do not apply to everyone in the position are stated as defaults and assigned by the manager.”
Affects
Permissions are granted via process role
VR-PRC-009 · Responsibility rule
“Permissions to functions and information in applications are granted based on the employee's active process roles – never on title or placement alone.”
Affects
Organisational scope of the process role
VR-PRC-010 · Conditional rule
“By default a process role applies within the employee's own unit. When the role must cover more units, the scope is set as one or more nodes in the organisation tree and is inherited downwards.”
Affects
Competence requirements are set by process roles
VR-PRC-011 · Responsibility rule
“A position sets no competence requirements of its own. Requirements for formal and functional competence arise only when process roles are linked to the position, and the position's requirement profile is the sum of the roles' requirements.”
Affects
Competence is measured against the process role's requirements
VR-PRC-012 · Value rule
“Inventory, gap analysis and follow-up of competence are done exclusively against the competences required by process roles. Volume is stated in FTE based on the employment rate of those holding the roles.”
Affects
The individual's competence is handled outside the process model
VR-PRC-013 · Responsibility rule
“The process model only describes which competences are required. What a person actually has is retrieved through integration with registers or established in development talks.”
Affects
Process roles can be reused across multiple processes
VR-PRC-014 · Cardinality rule
“A process role can be exercised in one or more processes at the lowest level. Generic process roles are reused across processes to avoid redundancy in the role catalog and establish more efficient and secure access governance.”
Affects
Digital identity per engagement and organisation
VR-IT-001 · Uniqueness rule
“A personal digital identity is issued for exactly one engagement with exactly one legal entity. Employment is one engagement type; consultants, trainees and elected representatives receive an identity through their engagement without being registered as employees.”
Affects
The identity follows the engagement's validity
VR-IT-002 · Conditional rule
“A digital identity is active only while the engagement it was issued for is valid. When the engagement ends, the identity is blocked immediately, including any administrator account.”
Affects
Access rights are granted to accounts
VR-IT-003 · Responsibility rule
“Access rights are never granted directly to a person or to the digital identity, but to an account in the application where the right applies, based on the employee's process roles.”
Affects
The employment rate is indivisible on the employment
VR-ORG-027 · Uniqueness rule
“The employment rate is stated only on the employment and covers the total work in position, management and engagement type. It is never split per process role, unit or location.”
Affects
The committee is a political authority, not a line node
VR-ORG-029 · Value rule
“A committee is an independent authority within the municipality or region and is never placed as a node in the organisation tree.”
Affects
Committee and administration have a many-to-many relationship
VR-ORG-030 · Cardinality rule
“An administration can prepare and execute matters for several committees, and a committee can commission several administrations. Each employee still has exactly one employment in the organisation tree.”
Affects
Municipal and regional companies are separate organisations
VR-ORG-031 · Uniqueness rule
“Activities run as companies are modelled as a separate organisation with its own organisation number, part of the group. The company has no committees; its staff are employed by the company.”
Affects
Automatic assignment at every organisational level
VR-PRC-016 · Conditional rule
“Process roles can be assigned automatically at the organisational level where the precondition exists. The top level grants base roles to all employees and manager roles to everyone with a manager code. Lower levels can grant roles to everyone employed in the unit or holding a certain position there.”
Affects
The manager selects from the unit's role assortment
VR-PRC-017 · Responsibility rule
“Each unit has a role assortment with the process roles that the unit's mission requires. A manager can only assign process roles from the own unit's assortment to employees, and the assignment provides the applications the role needs.”
Affects
Automated process roles require CMMI maturity level 4 in all involved processes
VR-PRC-018 · Conditional rule
“A process role may only be used for automation – such as a system agent, RPA or a rule engine – if all involved processes have reached at least level 4 (Quantitatively Managed) according to CMMI. This covers both the business process where the role is exercised and the processes that govern and manage the applications and integrations the role interacts with.”
Affects
Exercise of public authority rests on the committee's delegation order
VR-PRC-015 · Conditional rule
“Process roles involving exercise of public authority towards individuals must be anchored in an adopted delegation order from the responsible committee.”
Affects
The committee is a confidentiality boundary for access rights
VR-IT-005 · Conditional rule
“Access to confidential information is limited by the committee under whose delegation the process role is exercised.”
Affects
The application is managed by a unit
VR-IT-006 · Responsibility rule
“Every application is owned and managed by exactly one unit in the organisation tree. The application's operating, support and base licence costs are charged to the unit's base cost center, and budget responsibility lies with the unit's manager through the manager code.”
Affects
The application has a publisher
VR-IT-007 · Mandatory rule
“Every application in the catalogue states exactly one publisher, which is an organisation – own or external. The publisher is never stated as free text or as a code value.”
Affects
An application need not support a specific process
VR-IT-008 · Cardinality rule
“An application can support zero, one or several processes. General workplace tools are not linked to any specific process but are grouped by assortment level.”
Affects
Tool needs are separate from access rights
VR-IT-009 · Responsibility rule
“A process role can state which applications the role needs in its work. The tool need gives the right to receive the program and its licence, but never gives access to functions or information.”
Affects
The client is linked to its backend
VR-IT-010 · Conditional rule
“A client application connects to zero, one or several backend applications (0..*). Clients that read or write business information in a backend state which ones.”
Affects
Application assignment is verified annually
VR-IT-011 · Responsibility rule
“An application assignment covers installation, licence, account and access rights as one package. At least once a year the responsible manager verifies employees' accounts, licences and access rights, and anything no longer needed is revoked.”
Affects
Accounts always have an owner with an active engagement
VR-IT-012 · Cardinality rule
“Each account belongs to exactly one application and has an owner with an active engagement in the organisation. Personal and administrative accounts belong to a digital identity and are active only while the identity is active. Function accounts are created per application, and an application in production can have several (0..*).”
Affects
Accounts are never shared between people
VR-IT-013 · Uniqueness rule
“A personal or administrative account belongs to exactly one digital identity and must never be used by several people. Administrative accounts are kept technically separate from the personal account and are not used for everyday work.”
Affects
Absence pauses administrative accounts but not personal ones
VR-IT-014 · Conditional rule
“During longer absence, such as leave of absence or parental leave, administrative accounts are temporarily deactivated. Personal user accounts remain active.”
Affects
Managerial position requires exclusive management work
VR-ORG-028 · Value rule
“A position with a managerial title may only be assigned to an employee whose work consists exclusively of leadership and operational management. If the employee exercises a professional occupation to any extent, the employment is assigned that occupation as its internal position. Management is governed independently via the manager code on the employment.”
Affects
Strategic goals are inherited by the whole organisation
VR-GOL-001 · Mandatory rule
“A strategic business goal set on the top unit of the organisation tree is automatically inherited by all units below it.”
Affects
Tactical and operational goals link to a parent goal
VR-GOL-002 · Cardinality rule
“A tactical or operational business goal must always link to exactly one parent goal – an inherited strategic goal or a tactical goal higher up in the own line. Free-standing local goals are not allowed.”
Affects
Goal responsibility follows the manager code
VR-GOL-003 · Responsibility rule
“A business goal is always assigned to an organisational unit. Responsibility rests with the holder of the unit's active manager code – never with a named person or employment.”
Affects
Goals, finance and staff stay in the same line
VR-GOL-004 · Responsibility rule
“A business goal may only be assigned to a unit whose manager also holds responsibility for the budget and staff needed to reach it.”
Affects
Goal definition is master data, results are transaction data
VR-GOL-005 · Value rule
“The business goal, its link to a parent goal, indicator and target value are master data. Ongoing measurements and results are recorded as transactions referring to the goal's key.”
Affects