Risk management basics
Risk Management Lexicon, IKS & Compliance
Detailed explanations of the key terms used in risk management, internal control system, compliance management, supply chain, ESG and information security – with legal framework, methodology and practical implementation tips.
Fundamentals of risk management
The concept of risk, the control loop, the risk management system and its organizational integration – the foundation upon which all other subject areas are built.
Basics
Risk
A risk is the possibility that the actual development deviates from a planned target or expectation. It is described in terms of two dimensions: the probability of occurrence and the magnitude of the impact. In a business context, the term also includes positive deviations – opportunities are risks with the opposite sign.
Definition: Risk, cause, effect
In practice, three levels are regularly mixed, which makes subsequent evaluation useless. The Cause is the trigger („failure of a single supplier"), the Risk the event („production stoppage of more than two weeks"), the Effect the consequences („loss of revenue of 3 to 8 million euros, contractual penalties"). Only when these three levels are separately recorded can measures be meaningfully assigned: preventive measures address the root cause, mitigating measures mitigate the effect.
There is always a risk associated with a specific objective. Without a defined objective – result, liquidity, ability to deliver, reputation, compliance – there is no measure of deviation and therefore no assessable risk. For this reason, any risk identification begins with the question of which objectives can actually be compromised.
Risk types at a glance
| Category | Examples | Special feature in the evaluation |
|---|---|---|
| Strategic risks | Business model, technological change, market shifts | Low data base, high impact – scenario analysis instead of statistics |
| Operational risks | Production failure, quality defects, project delays | Good data from previous incidents, quantitatively well-accessible |
| Financial risks | Currency, interest rate, commodity price, debt default | Market data available, distributions can be modeled and calculated |
| Legal and compliance risks | Cartel violations, corruption, data protection, product liability | Rare events with very high damage levels |
| IT and cyber risks | Ransomware, system failure, data loss | Increasing frequency, potential endangering the stock |
| Sustainability risks | Climate consequences, supply chain, reputational damage | Long time horizons, driven by regulations |
Properly describing risks
The quality of a risk inventory is determined by the wording. Inappropriate terms such as „talent shortage" or „digitalization" are useless – they name a topic area, not an assessable event. A description that includes the cause, event, affected target, and mechanism of action is acceptable and can therefore be understood by any third party.
- Inoperable: „Risk of IT security"
- Usable: „Encryption of production systems by ransomware leads to a standstill of 5 to 15 working days with loss of coverage premiums and conventional penalties"
Practice
Few fields have proven to be necessary for recording in the system: risk description, cause, affected target, category, risk owner, gross and net assessment, associated measures, and the date of the last update. Everything else is optional – additional fields, as experience has shown, reduce the willingness of the relevant departments to report, without increasing the accuracy of the data.
See also: Risk management · Risk matrix · Risk aggregation
Basics
Risk management
Risk management is the systematic, recurring handling of risks: identifying, analyzing, evaluating, controlling, monitoring, and reporting on them. The goal is not to avoid every risk, but to consciously take on risks within one’s own risk tolerance – and thereby provide a reliable basis for entrepreneurial decisions.
Purpose: Decision basis instead of mandatory exercise
The economic purpose of risk management lies not in documentation but in better decisions. Those who know the range of possible outcomes can align investments, financing structures, contractual terms and conditions, and hedges accordingly. A company with reliable risk quantification can justify to banks and investors why a plan is achievable – and this is reflected in ratings and financing costs.
The second benefit is in terms of liability: in the event of a dispute, business managers must demonstrate that they made their decision based on reasonable information. A documented risk management process is the central evidence for this.
The control circuit
Legal framework in the DACH region
| Basis | Addressee | Key requirement |
|---|---|---|
| Section 91, paragraph 2 of the AktG | Joint-stock companies, broadcasting on large GmbH | Monitoring system for the early detection of developments that endanger the stock |
| Section 91, paragraph 3 of the AktG | Listed public company | Appropriate and effective risk management and internal control system |
| § 1 StaRUG | All companies with limited liability | Ongoing crisis detection and countermeasures by the management |
| IDW PS 340 n.F. | Audit criterion of the auditor | Risk aggregation and comparison with risk tolerance |
| Section 289 of the German Commercial Code | Companies subject to reporting requirements | Presentation of key opportunities and risks in the status report |
Tire grades in practice
There are several development stages between an Excel list and a control-relevant system. Categorizing helps to determine the next sensible step, rather than trying to do everything at once.
- Documenting: Risks are collected annually in a list, usually shortly before the final exam. No influence on decisions.
- Structured: Uniform categories, assessment scales and risk indicators; regular collection; measures are monitored.
- Quantified: Risks are evaluated and aggregated across bandwidths; the overall risk position is compared to the risk-bearing capacity.
- Integrated: Risk data is incorporated into planning, the investment calculation, and the target agreements; opportunities are treated equally.
Typical mistakes
- Once a year: An inventory that is created only on the cut-off date does not reflect the current risk situation and does not meet the requirement of ongoing monitoring.
- Only identify known risks: Workshops regularly reproduce the past damage patterns. Strategic and external risks are then completely absent.
- Assessment in classes: „High" and „medium" cannot be added – without quantification, aggregation is not possible.
- Actions without follow-up: If implementation is not monitored, risk management remains an intention statement.
- Risk management as a department task: The department is responsible, as the risk owner, not the central function.
Introduction in twelve months
The most common reason for failed introductions is the attempt to do everything at once. A sequence in which each step provides a usable intermediate result has proven to be effective.
| Phase | Content | Result |
|---|---|---|
| Month 1–2 | Define risk strategies, roles, categories, and scales | Risk manual, approved by management |
| Months 2–4 | Initial inventory of workshops by area | complete risk inventory with owners |
| Months 4–6 | Quantitative assessment of the essential risks | Bandwidth, first aggregation |
| Months 6–8 | Comparison with risk tolerance | Statement on the threat to the species |
| Months 8–10 | Measures, early warning indicators, reporting formats | running operation, first group report |
| Months 10–12 | System support, integration with IKS, and compliance | Reproducible routine, ability to pass exams |
Anyone who already runs a planning process with scenarios can significantly shorten phases three and four: The bandwidths already exist and only need to be assigned to the risks.
Economic benefit beyond the obligation
- Financing: Those who quantify their risk situation negotiate with banks on the basis of facts rather than on security charges.
- Investment decisions: Projects can be compared on a risk-adjusted basis instead of just based on expectations of returns.
- Insurance: The deductible and coverage amounts can be optimized based on the actual distribution.
- Quality of planning: The discussion about bandwidth covers unrealistic planning assumptions before they are included in the budget.
- Protection of liability: Documented decision bases are the central evidence in a dispute.
Frequently asked questions
Is risk management mandatory for the GmbH as well?
Yes, in the end. Under § 1 StaRUG, the management of limited liability companies is responsible for the obligation to continuously detect crises; in addition, § 91, paragraph 2, of the AktG applies to larger GmbHs. The scope depends on size, complexity, and risk profile.
How often must the risk assessment take place?
There is no fixed legal frequency. Ongoing monitoring is required. A quarterly cycle is common, with an annual full survey supplemented by ad-hoc reports on significant changes.
Who is responsible?
The management as a whole organ. It can delegate tasks, but not the responsibility for setting up, equipping, and monitoring the system.
See also: Risk management system · Risk management process · Three Lines Model
Basics
Risk management system (RMS)
The risk management system encompasses all the regulations, processes, roles, methods, and instruments with which an organization identifies, assesses, controls, and monitors risks. It is the organizational framework within which the risk management process takes place—and the subject that the auditor and supervisory board assess for adequacy and effectiveness.
Components of an RMS
The IDW PS 981 examination standard divides the risk management system into basic elements. They also form a useful checklist for your own structure: Each element must be documented, assigned, and implemented.
| Element | What lies behind it | Typical evidence |
|---|---|---|
| Risk culture | Basic approach to dealing with risks openly | Core values, leadership behavior, handling of negative feedback |
| Risk targets | What the system is supposed to accomplish | Risk strategy, risk appetite, limit |
| Risk organization | Roles and responsibilities | Organigram, Role Descriptions, Three Lines Model |
| Risk identification | Methods of collection | Workshops, checklists, early warning indicators |
| Risk assessment | Methodology and scales | Risk handbook, assessment matrix, aggregation model |
| Risk management | Managing assessed risks | Action plan with deadlines and responsible parties |
| Risk communication | Reporting channels and escalation | Reporting cycle, ad-hoc reporting thresholds |
| Monitoring and improvement | Effectiveness control of the system itself | Audit reports, system reviews |
Testing the system
There are two levels to distinguish: Appropriateness assess whether the system is suitable in its design for achieving the set goals. The Effectiveness It assesses whether such operations were actually carried out over a period of time. A system that is cleanly documented but not implemented is appropriate but at the same time ineffective – a common finding in initial inspections.
In listed public companies, the auditor obligates to assess the early detection system in accordance with § 317(4) of the German Commercial Code. Outside this framework, an assessment is carried out voluntarily, often at the request of the supervisory board or as part of a transaction.
Construction in eight steps
- derive risk strategy and risk appetite from the corporate strategy and have them approved by the management body
- Defining roles: Risk owners in the relevant departments, central coordination, reporting recipients
- Define uniform categories and evaluation scales and make them binding in the risk manual
- First inventory of workshops and interviews per area is being compiled
- Rating in bandwidths instead of classes, so that aggregation is possible
- Establish an aggregation model and compare it to risk-bearing capacity
- Record and track actions with responsible parties and deadlines
- Define reporting formats and reporting thresholds, then start the routine
Separation from the internal control system
The RMS identifies and assesses risks; the IKS limits them through process controls. Both complement each other: the effectiveness of controls is exactly the difference between gross and net risk. If the RMS and IKS are built separately, double reporting is created and contradictory statements arise for the supervisory board and the auditor.
See also: Internal control system · Risk aggregation · Risk management
Basics
Risk management process
The risk management process is the recurring cycle of identification, analysis, evaluation, control, monitoring, and reporting. ISO 31000 supplements it with communication and consultation as process-related elements, as well as the definition of the scope of application at the beginning of each cycle.
The phases in detail
| Phase | Result | Methods |
|---|---|---|
| Identification | Risk inventory | Workshops, interviews, process analysis, checklists, damage assessment |
| Analysis | Cause-effect understanding | Bow-tie, error tree, FMEA, root cause analysis |
| Rating | Quantified risk, total risk position | Bandwidths, distributions, Monte Carlo simulation |
| Control | Action plan | Avoid, reduce, transmit, or bear the burden yourself |
| Surveillance | Current risk situation, proof of effectiveness | Early warning indicators, target-actual comparison, reviews |
| Reporting | Risk report internally and externally | Dashboard, Group report, Status report |
Routine and occasion-related triggers
An annual review is not sufficient to meet the requirement of ongoing monitoring. The combination of an annual full survey, quarterly updates of the key risks and defined ad-hoc triggers has proven effective. Typical triggers are: an early warning indicator being exceeded, a significant loss occurring, the acquisition or entry into the market, new regulatory requirements, and the loss of a major customer or key supplier.
Roles per phase
- Risk owners: identifies, assesses and controls the risks in its own area and is responsible for the measures.
- Central risk management: provides methodology and scales, consolidates, aggregates, plausibilizes, and reports.
- Management: decides on risk appetite, essential measures and the acceptance of residual risks.
- Supervisory body: monitors the effectiveness of the system and questions the methodology and overall risk position.
- Internal audit: independently verifies that the process is running as described.
See also: Risk management · Three Lines Model
Basics
Risk matrix (heatmap)
The risk matrix represents risks in a matrix of entry probability and damage severity and makes action priorities visible at a glance. Typical 4×4 or 5×5 grids with traffic light colors are used. It is a communication tool – for assessing developments that pose a threat to the stock, it is not methodologically sufficient.
Construction
The axes are not arbitrary: The impact is defined in monetary units, based on a uniform reference period – usually a fiscal year. Without these specifications, different sectors evaluate it differently, and the matrix compares the incomparable.
Defining scales
| Great | Probability of entry per year. | Impact on EBIT |
|---|---|---|
| 1 – very low | under 5 % | less than € 0.25 million |
| 2 – low | 5 to 15 % | 0.25 to 1 million € |
| 3 – medium | 15 to 35 % | 1 to 3 million € |
| 4 – high | 35 to 60 % | 3 to 8 million € |
| 5 – very high | over 60 % | over 8 million € |
The thresholds are determined individually for each company based on the results and equity capital figures. As a guideline, it is often assumed that the highest class begins to pose a threat to the company’s assets – this makes the matrix compatible with the risk tolerance level.
Limits of representation
- No addition is possible: Classes are orderedly scaled. Twenty risks in the yellow zone can be collectively life-threatening without the matrix showing it.
- Expectation trap: A rare risk with extreme damage levels ends up in the same cell as a frequent one with low damage – the control consequence is completely different.
- Sharpness of focus: The positioning suggests precision, but is based on class classifications with wide intervals.
- Correlations invisible: Risks that occur together appear as independent points.
The risk matrix remains valuable as a communication format for committees. However, for assessment according to IDW PS 340 n.F., it must be supplemented by quantitative aggregation – it does not replace it.
Frequently asked questions
4×4 or 5×5?
5×5 offers a finer gradation; 4×4 prevents the player from fleeing to the center. Those who use 5×5 should define the middle class narrowly so that it does not become a catch-all category.
To represent gross or net?
Both – ideally in a graph showing the shift from gross to net position using an arrow. This makes the effect of the control system immediately visible and is a strong argument against the supervisory body.
See also: Risk assessment · Risk aggregation · Risk
Basics
Three Lines Model
The Three Lines Model of the Institute of Internal Auditors divides responsibilities into three levels: operational areas, oversight functions such as risk management and compliance, and independent internal audit. It answers the question of who takes on risks, who sets the framework, and who independently audits both.
The model
The three lines
The First line It covers all areas that incur risks in day-to-day operations: sales, production, purchasing, IT. It is responsible for the risks within its area of responsibility and carries out the controls. The second line provides methodology, scales, and frameworks, supports the first line professionally and monitors whether the framework is being followed – without taking on any responsibility. The Third line Independently examines whether the first two lines are working effectively and reports directly to management and the supervisory board.
The former designation „Three Lines of Defense" was deliberately abandoned in 2020. The defense concept had shaped perception; risk management was purely defensive; the updated model instead emphasizes the contribution to value creation and the achievement of corporate goals.
Typical design flaws
- Mixing the lines: If the second line assesses risks itself and implements measures, it assumes responsibility for the first line – and cannot monitor it anymore.
- Revision without independence: If the internal audit reports to the area it is auditing, the third line is not actually present.
- Empty second line: A compliance function without resources and authority creates documentation, but no effect.
- Overcrowded second line: Functionalities that work in parallel for risk, compliance, IKS, data protection and information security process the same data multiple times – the starting point for integrated GRC.
See also: Internal control system · Compliance management system · Risk management system
Basics
Risk strategy
The risk strategy is derived from the company’s strategy and determines which risks the company is willing to take, which it limits, and which it avoids. It concretizes the appetite for risk within limits for each risk category and forms the benchmark against which operational decisions are measured.
What goes in
- Derivation from the company strategy: Which objectives are to be protected?
- Risk appetite by category, preferably expressed in quantitative terms
- Limits and thresholds above which escalation takes place
- Basic decisions regarding risk transfer: insurance strategy, deductible, contract clauses
- Accurately accepting risks with justification – that is the part that counts in the case of liability
Practice
A risk strategy that contains only general statements („We manage risks responsibly") does not fulfill its purpose. It becomes viable only through numbers: maximum acceptable range of results, minimum liquidity reserve, upper limit for lump-sum risks for customers and suppliers. It is approved by the management body and reviewed at least annually.
See also: Risk appetite · Risk-bearing capacity · Risk policy
Basics
Risk policy and risk manual
The risk policy describes the binding principles for dealing with risks. It is usually documented as a risk handbook and serves as the written basis on which auditors and the supervisory board rely when assessing the risk management system.
Contents of the risk management manual
| Chapter | Subject of regulation |
|---|---|
| Objectives and scope | Which companies, sectors and risk types are covered |
| Roles and responsibilities | Risk owners, central function, committees, internal audit |
| Risk categories | Binding system for the entire company |
| Assessment methodology | Scales, bandwidths, distributions, gross-net logic |
| Aggregation | Model, assumptions, correlations, confidence level |
| Reporting channels | Turnover, ad-hoc thresholds, escalation levels |
| Documentation | Obligations to provide evidence, storage, use of the system |
The manual should be concise and usable. Fifty pages that no one reads create less security than fifteen pages that are actually used.
See also: Risk strategy · Risk management system
Basics
Risk culture
Risk culture describes the values and behavioral patterns that are practiced in dealing with risks – whether bad news is openly addressed or withheld out of concern for consequences. It determines the quality of risk identification and thus the value of the entire system.
How to recognize them
- How does management react when someone reports an unpleasant risk?
- Are the targets set in such a way that they are only achievable with the risk of violating the rules?
- Are the damage incurred processed or personalized?
- Are risk discussions part of the decision-making process or a separate process?
A technically sophisticated system provides useless data if employees do not report negative developments. The key therefore often lies not in the methodology but in the behavior of the first two levels of management.
See also: Compliance management system · Risk identification
Basics
Risk appetite
The risk appetite expresses how much risk a company intends to deliberately take to achieve its goals. It is a strategic determination by the management body and ideally is formulated quantitatively – as the maximum acceptable range of results, as a limit per category or as a minimum distance from the risk of default.
Examples of formulations
| Inoperable | Usable |
|---|---|
| „We are risk-conscious." | „The aggregated result burden may not exceed % 40 in the 95 scenario % of the plan result." |
| „We avoid the risk of lumps." | „No customer with over 15% share of % sales, no single supplier without a qualified secondary source for A-parts." |
| „Compliance is a top priority." | „Zero tolerance for corruption and cartel violations; no business in countries with a corruption index grade X without board approval." |
See also: Risk tolerance · Risk strategy
Basics
Risk-bearing capacity
The risk-bearing capacity indicates how much risk a company can absorb on its own without endangering its assets. The comparison of aggregated total risk and risk-bearing capacity is the central test for any developments that endanger the assets in accordance with IDW PS 340 n.F.
Investigation
| Component | Availability | Note |
|---|---|---|
| Free equity | bilaterally, in the medium term | minus committed funds and minimum quotas from covenants |
| Liquid funds | Immediately | Buffer for operational fluctuations |
| Unused credit lines | short-term | Attention: often shortened in times of crisis |
| Silent Reserves | in the long term | only limitedly liquidable |
| Planned outcome | about the planning period | Even if it involves some risk, proceed with caution |
The assessment is as follows: If the aggregate risk exceeds the coverage potential at the chosen confidence level, there is a situation of material risk to the business – with immediate action required by the management.
Practical implementation
Two horizons are considered separately for assessment: short-term liquidity: what funds are available within a few weeks to cover a loss event? Medium-term equity capital: what losses can the balance sheet absorb without violating covenants or jeopardizing the rating?
Both horizons are compared against the aggregate risk. The result is one of the few metrics of interest to management, the supervisory board and banks alike – and the basis for deciding whether risks need to be reduced, transferred or covered by additional reserves.
See also: Risk coverage potential · Development endangering the stock · Risk aggregation
Basics
Risk tolerance
Risk tolerance describes the permissible range around the risk appetite – from when an overshooting is still acceptable to when it must be escalated. While the risk appetite is formulated strategically, the tolerance is operational: it is expressed in limits, thresholds, and traffic light boundaries.
In practice, both terms are often used synonymously. The distinction is nevertheless useful: Appetite answers the question of how much risk is acceptable; tolerance answers the question of what deviation from that risk is acceptable in day-to-day business without escalation. Without defined tolerance, any overshoot of a limit value either ends in a special meeting or in indifference.
See also: Risk appetite · Early warning indicator
Basics
Risk inventory
The risk inventory is a structured overview of all identified risks, grouped by categories and organizational units. It is the result of risk identification and the starting point for evaluation, control, and aggregation.
Quality characteristics
- Completeness: All essential areas and risk types covered, including strategic and external risks
- Freedom from overlap: the same risk does not appear in three different-named areas
- Appropriate granularity: 40 to 120 risks are common in medium-sized structures; 400 individual risks are no longer controllable
- Up-to-date: Each risk carries the date of the last review.
Care over time
An inventory loses its value faster than it is created. Two mechanisms currently maintain its value: the periodic confirmation by risk owners, in which each risk is either confirmed, modified, or closed with justification; and the ad hoc addition for new business areas, acquisitions, or regulatory changes.
Just as important as adding something is closing it: risks that no longer exist must be documented as having been terminated, not silently deleted. The history of closed risks is one of the few sources from which later experience can be drawn to inform assessments.
See also: Risk registers · Risk categories
Basics
Risk registers
The risk register is the operational data base for risk management. For each risk, a description, cause, category, risk owner, assessment, measures, and status are kept – it is thus the working instrument, while the risk inventory represents the overall overview.
Data fields
| Field | Purpose | Obligatory |
|---|---|---|
| Name and description | Clear identification of the event | yes |
| Cause | Starting point for preventive measures | yes |
| Category | Analysis and aggregation | yes |
| Risk owners | Responsibility and questions | yes |
| Gross/net valuation | Making the effects of the controls visible | yes |
| Actions with deadlines | Control and tracking | yes |
| Affected plan position | Prerequisite for aggregation | recommended |
| Early warning indicator | ongoing monitoring | recommended |
| History of the ratings | Understandability for testers | system-side |
Excel-based registers typically fail at three points: version conflicts when they are being edited in parallel, a lack of history of the changes in the evaluations, and no separation of rights between the different areas.
See also: Audit Trail · Risk inventory
Basics
Risk identification
Risk identification is the first step in the regulatory framework and aims to capture all relevant risks as fully as possible. Its quality determines everything else: an unidentified risk is neither evaluated nor controlled nor reported.
Methods compared
| Method | Strength | Weakness |
|---|---|---|
| Risk workshop | Wide participation, common understanding | Group dynamics, dominance of individual participants |
| Individual interview | Openness, even on sensitive topics | Cost, less comparability |
| Checklist / Risk catalog | Systematics, against blind spots | Teaches to click without reflection |
| Process analysis | Detects operational vulnerabilities | Blind to strategic and external risks |
| Damage assessment | Empirically proven | Reversed direction |
| Early warning indicators | Continuous, automated | Only records known |
The most common mistake
Workshops reproduce the past’s damage patterns. Strategic risks – business model, technological change, regulation, dependencies – are then completely absent, even though they have the greatest impact. The antidote is a structured journey along value chains, stakeholders, and goals, complemented by a conscious questioning of what the business model could fundamentally compromise.
Sources that are often overlooked
- Minutes of management and supervisory board meetings – where the strategic concerns are already formulated
- Complaints, warranty and good faith data from the quality management system
- Audit reports, certification findings and audit letters from the auditor
- Insurance contracts: What was insured has already been identified as a risk
- Contractual clauses with liability, penalty and availability clauses
- Reports from the Whistleblower System and Incident Management
According to experience, going through these six sources yields a third of the final inventory before the first workshop has taken place – and prevents the inventory from merely reflecting what the participants thought about on the workshop day.
See also: Risk inventory · Delphi method
Basics
Risk analysis
The risk analysis examines the causes, causal relationships, and possible effects of a risk. It answers the question of how a risk arises, how it spreads, and what the level of damage in different scenarios is realistically—thus providing the basis for assessment and the choice of measures.
Set the analysis depth
Not every risk warrants a thorough analysis. A grading system has proven to be effective: risks with potentially damaging effects on the stock are examined using formal methods – error tree analysis, Bow-Tie analysis, FMEA –, risks of medium importance are assessed using structured expert judgment, and secondary risks are only qualitatively assessed.
See also: Bow-Tie Analysis · FMEA · Risk assessment
Basics
Risk management
Risk management encompasses all measures that are used to influence risk. Traditionally, four strategies are distinguished: avoid, reduce, transfer, and self-bear. Each measure requires a responsible person, a deadline, and an effectiveness control.
The four strategies
| Strategy | Effect | Example | Costs |
|---|---|---|---|
| Avoid | Risk is completely eliminated | Refusing to do business in a high-risk country | Giving up on profits |
| Reduce | Probability or impact decreases | Second supplier, redundancy, controls | ongoing effort |
| Transmit | Third party bears the damage | Insurance, limitation of liability in the contract | Premium, deductible |
| Self-carrying | Risk remains consciously present | Retirement, liquidity buffer | Capital commitment |
The deliberate self-infliction of harm is a legitimate decision – but it must be documented and compared with the risk tolerance involved. In the event of liability, it cannot be distinguished from inaction.
What constitutes a reliable measure
- Direction of action named: Does the measure reduce the probability of an incident or the level of damage? Both at the same time is rarely the case.
- Responsible with decision-making authority: not the person who only reports
- Time limit with intermediate steps: Actions over twelve months without milestones expire silently
- Visible result: How can it be determined that the measure is effective?
- Costs and benefits weighed: A measure that is more expensive than the expected damage is not risk management, but a waste of money.
The effectiveness control is the step that is most often missing. Without it, it remains open whether the net risk has actually decreased – and the net assessment in the risk register is then an assumption, not a determination.
See also: Action management · Risk costs
Basics
Risk monitoring
Risk monitoring continuously examines whether the risk situation and the effectiveness of the measures have changed. It is based on early warning indicators, comparison between the current situation and the target situation, and the periodic updating of the inventory – and represents the difference between a snapshot and a functioning early detection system.
The process-related monitoring by the second line is distinguished from the independent review by the Internal Audit as a third line. Both are necessary: The second line detects changes early, while the third assesses whether the system as a whole functions properly.
See also: Three Lines Model · Key Risk Indicator
Basics
Risk reporting
The risk reporting summarizes the risk situation in a targeted manner – for management, the supervisory board, and external reporting recipients. A reliable report not only shows individual risks, but also the aggregated total risk position, its changes, and the status of the measures taken.
Target-oriented compaction
| Recipients | Turnus | Content |
|---|---|---|
| Department | ongoing | Own risks, status of measures, indicators |
| Management | monthly to quarterly | Top risks, overall risk position, boundary value violations |
| Supervisory body | quarterly to annual | Development of the risk situation, methodology, and significant changes |
| Situation report | annually | Significant opportunities and risks under § 289 HGB |
| Ad hoc | related to a particular occasion | New inventory-endangering risks, significant damage cases |
See also: Situation report · Risk dashboard
Basics
Risk Owner
The risk owner is responsible for evaluating, controlling, and monitoring a specific risk. This is usually the leader of the area concerned – not the risk manager, who provides and consolidates the methodology.
Clear assignment is a prerequisite for ensuring that measures are actually implemented, and is regularly questioned by auditors. A risk without a named owner is a risk without responsible parties – and that is exactly the finding that ends up in the audit report. In the case of cross-departmental risks, a lead owner is named, not several equally responsible parties.
See also: Three Lines Model · Risk registers
Basics
Risk categories
Risk categories structure the inventory and make risks comparable across areas. A consistent system is essential for aggregation, evaluation, and reporting – and it should start at the root cause, not the affected department.
A two-stage taxonomy with five to eight main categories and three to six subcategories has proven to be effective. The key is the degree of differentiation: a cyberattack is an IT risk, its impact on operations is an operational risk, and the breach of reporting obligations is a compliance risk. Without a clear allocation rule in the risk management manual, the same event will be classified differently in different areas.
See also: Risk inventory · Risk
Basics
Gross risk and net risk
The gross risk describes a risk before taking into account existing measures and controls; the net risk is the remaining size after that. The difference is the measurable contribution of the internal control system.
Why both sizes are necessary
- The gross valuation shows which risks would be life-threatening without controls – and thus justifies investments in the IKS.
- The net assessment is crucial for aggregation and comparison with risk-bearing capacity.
- The difference makes the dependence on individual controls visible: If a key control fails, the net risk jumps to the gross level.
Precondition: The effectiveness of the controls must be proven. If it is merely assumed, the net assessment is wishful thinking – a point that the auditor specifically questions.
See also: Internal control system · Control effectiveness
Basics
Probability of entry
The probability of occurrence indicates how likely a risk is to occur within a defined period of time – usually based on a business year. Without a uniform reference period, assessments of different sectors are not comparable.
Two sources of error regularly occur. First, the unclear reference period: „Occurs once every five years" corresponds to 20 percent per year – if this conversion step is not regulated in a binding manner, there will be evaluation differences of the factor of five. Second, the confusion between frequency and probability in the case of risks that can occur multiple times per year; here, an expected frequency and the magnitude of the damage per event must be taken into account.
See also: Amount of damage · Risk assessment
Basics
Amount of damage
The level of damage quantifies the financial impact of an occurring risk – as an effect on EBIT, cash flow, or equity capital. For aggregation, not a single value is relevant, but a range with a minimum, most likely value, and maximum value.
The reference size must be determined in a binding manner. A risk that reduces sales by 5 million euros burdens the EBIT by a significantly smaller amount depending on the contribution to the coverage – when sales and earnings effects are mixed, the overall statement is worthless. It is also necessary to determine whether to include consequential costs such as contractual penalties, reputational damage or increased financing costs.
See also: Probability of entry · Triangular distribution
Basics
Opportunity management
Opportunity management systematically identifies positive deviations from plans and manages them using the same methods as risks. Since opportunities and risks stem from the same causes, the integrated approach is methodically consistent – and it significantly increases acceptance within the company.
In the status report, § 289 HGB requires the presentation of the essential opportunities anyway. and Risks. Those who separate the two produce double effort; those who completely ignore opportunities do not meet the reporting requirement and at the same time waste the strongest argument with the functional areas: risk management is then not just control, but also a systematic search for potential.
See also: Situation report · Bandwidth planning
Basics
Risk early detection system
A risk early detection system is intended to detect developments that endanger the company at an early stage so that countermeasures can still be taken. For public limited companies, this is legally required under § 91(2) AktG and is the subject of the final audit under § 317(4) HGB for listed companies.
Ingredients
- Defining the risk areas to be monitored, derived from the business model
- Early warning indicators per risk area with defined measurement frequency
- Threshold values whose exceeding triggers a notification
- Binding escalation paths to the management level
- Aggregation to the overall risk position and reconciliation with the carrying capacity
- Documentation of all steps as proof to inspectors and supervisory bodies
The crucial difference to general risk management lies in the time frame: what is required is not the recording, but the timely Recognition – that is, a preliminary step that still makes the action possible.
See also: Section 91, paragraph 2 of the AktG · Development endangering the stock · Early warning indicator
Basics
Early warning indicator
A early warning indicator is a measurable measure that indicates an emerging risk development before the damage occurs. A defined threshold value, a fixed measurement frequency, and a pre-agreed escalation path are crucial.
Examples per risk area
| Risk field | Indicator | Qualifying |
|---|---|---|
| Sales | Order intake, offer success rate | 1 to 2 quarters |
| Liquidity | Debt collection period, proportion of overdue receivables | 4 to 8 weeks |
| Supply chain | Credit index key suppliers, delivery date deviation | 1 to 2 quarters |
| Personnel | Fluctuation in key functions, sick leave | 2 to 4 quarters |
| Quality | Complaint rate, overtime hours | Weeks |
| IT security | Number of security-related incidents, patch backlog | Weeks |
Five to fifteen well-chosen indicators with clear thresholds have a value of more than fifty, which no one evaluates.
See also: Key Risk Indicator · Risk early detection system
Methods & Quantification
How to turn individual risks into a reliable overall statement – aggregation, simulation, and the key performance indicators that can be used to measure risk and hold it against the carrying capacity.
Methods
Risk aggregation
Risk aggregation brings all individual risks together to form a total risk position and answers the crucial question: Can the company bear its total risk without falling into an unsustainable situation? Since the revision of the IDW PS 340, it has become a more explicit subject of examination – and the point at which most mature risk management systems fail.
Why risks cannot be added together
The obvious approach – all damage levels add up – systematically leads to incorrect results. The reason lies in probability: A risk with €10 million in damage and a 5 percent probability of occurrence burdens planning differently than one with €10 million and a 60 percent probability. When both are added together, a maximum damage occurs that practically never occurs and therefore has no control relevance.
Conversely, the sum of the expected values leads to underestimation: it describes the average case, not the bad scenario that determines the survival. Correlations also come into play – a downturn in the economy, defaults on loans, and a decline in utilization rates all occur together. Ignoring them regularly significantly underestimates the overall risk.
Aggregation is therefore not a calculation exercise but a simulation: it answers the question of how likely a given outcome and liquidity situation is if all risks can act simultaneously.
Comparison of procedures
| Procedure | Action | Credibility | IDW PS 340 n.F. |
|---|---|---|---|
| Addition of the damages | All maximum damages add up | Unrealistic extreme value with no probability | not sufficient |
| Sum of the expected values | Damage × Probability, then sum | Average case, blind to extreme scenarios | not sufficient |
| Scenario technology | Calculating consistent combinations manually | Understandable, but without a statement of probability | complementarily suitable |
| Monte-Carlo simulation | Tens of thousands of iterations over the planning process | Complete distribution of results with probabilities | State of the art |
Read the result
From this distribution, the key figures can be derived that are actually needed for control:
| Indicator | Statement | Use |
|---|---|---|
| Value at Risk | Loss threshold at selected confidence level | Comparison with the risk coverage potential |
| Capital requirement | Capital that is required to cover | Capital planning, rating discussion |
| Probability of Covenant violation | Share of scenarios in which KPIs are broken | Funding structure, negotiation with banks |
| Probability of endangerment of the species | Share of scenarios with illiquidity or overindebtedness | Proof in accordance with § 91(2) of the AktG |
Action in six steps
- Planning as the basis: Aggregation relies on GuV and liquidity planning, not on a separate risk list.
- Assigning risks to plan positions: Each significant risk affects a specific position – revenue, material costs, personnel costs, investments.
- Bandwidth instead of classes: Determine the minimum risk, most likely value, and maximum value, as well as the probability of occurrence.
- Choosing and justifying distributions: For most cases, the triangular distribution is sufficient; rare large damages are modeled using a combination of the probability of occurrence and the distribution of damage.
- Establishing correlations: At least they illustrate the obvious connections between cyclical risks.
- Simulate and compare: Calculate the distribution of results and compare them with the risk coverage potential; document the results, assumptions, and model.
Typical mistakes
- Aggregation without planning context: When calculated independently of corporate planning, the result cannot be plausibly justified nor used to inform decisions.
- Modeling all risks individually: The cost explodes without any gain in knowledge. Usually, ten to twenty risks determine the distribution.
- Set correlations to zero: That is an assumption, not neutrality – and it leads to a systematic underestimation.
- Model not documented: Without comprehensible assumptions, the result is worthless in the examination interview.
Computational example: why the sum is misleading
An enterprise faces five key risks. The following table shows how the overall risk profile differs depending on which method is chosen.
| Risk | Probability | Damage (max.) | Expected value |
|---|---|---|---|
| Main customer failure | 10 % | 6.0 million € | 0.6 million € |
| Rise in commodity prices | 45 % | 4.0 million € | 1.8 million € |
| Production failure | 8 % | 9.0 million € | 0.7 million € |
| Cyber incident | 12 % | 12.0 million € | 1.4 million € |
| Warranty case | 25 % | 3.0 million € | 0.8 million € |
- Addition of maximum damages: 34.0 million € – a scenario in which all five risks occur simultaneously at maximum. Computable, practically almost impossible, unusable as a control variable.
- Sum of the expected values: 5.3 million euros – the average case. He fails to mention that in unfavorable circumstances, a multiple can occur.
- Simulation: provides the distribution. Typically, the Value at Risk is % significantly above the expected value and well below the maximum sum – and this very value can be compared with the risk coverage potential.
The statement then no longer reads „we have five significant risks"; instead, it reads: „In 5 out of 100 years, the risks will affect the result by more than X million euros; our coverage potential is Y million euros." This is a statement that a supervisory board can work with.
Requirements for system support
- Linking risks to plan positions instead of isolated risk lists
- Allocating bandwidth and distribution types based on risk
- Illustration of common drivers for correlated risks
- Understandable history of all assumptions and changes in assessments
- Reproducibility: the same inputs must yield the same result
- Exportable documentation for inspectors and supervisory bodies
Frequently asked questions
Can risk aggregation be done in Excel as well?
Technically, yes, with a simulation add-in or custom programming. Practically, it usually fails due to comprehensibility and version control: The auditor wants to see which assumptions were made by whom when. Exactly this history is missing in large tables.
How many simulation runs are necessary?
For stable results in the range of usual confidence levels, 10,000 to 100,000 runs have been established. What is crucial is that the result remains stable when repeated – this must be documented.
Does every company have to aggregate data?
The obligation to detect emerging issues early applies to every limited liability company. Without aggregating the individual risks, it is not possible to make this assessment methodically – however, the depth of the model must be based on size and complexity.
See also: Monte-Carlo simulation · Risk matrix · Risk management system
Methods
Monte-Carlo simulation
The Monte Carlo simulation calculates the overall risk position by running the planning period many thousands of times with randomly drawn representations of all risks. The result is not a single number, but a distribution of possible business outcomes – the basis for Value at Risk, capital requirements, and the assessment of the risk to the business.
This is how it works
In each run, the model calculates a random value for each risk from the stored distribution—for example, a 4.2 percent sales decline and an 11 percent increase in material prices—and runs the complete planning with these values. The result is stored and the process is repeated. After tens of thousands of runs, a frequency distribution of all possible outcomes is available, from which any desired probability statement can be derived.
| Position | Planned value | Der derived deviation | Results in progress |
|---|---|---|---|
| Sales | 200.0 million € | −4,2 % | 191.6 million € |
| Material costs | 96.0 million € | +11,0 % | 106.6 million € |
| Personnel costs | 52.0 million € | +1,5 % | 52.8 million € |
| IT damage incident | — | not occurred | 0.0 million € |
| EBIT | 18.0 million € | — | −1.8 million € |
A single run does not tell us anything – it is one of many conceivable scenarios. Only the distribution across all runs answers the question of how likely a negative EBIT, a Covenant violation, or a liquidity shortage is.
What input data are needed
- Planning model: GuV, balance sheet and liquidity in consistent correlation – the simulation repeatedly calculates this model.
- Bandwidth per risk: Minimum, most likely value, maximum; in the case of event risks, the probability of occurrence additionally.
- Distribution type: Triangular, PERT or normal distribution for continuous variables, binomial or Poisson approaches for events.
- Correlations: At least the cyclical relationships between sales, price and the failure to meet demands.
Boundaries
The simulation is only as good as its assumptions. It does not generate information but makes existing assessments computable. Therefore, two points should be noted: The quality of the bandwidth determines the result, and risks that are not included in the model do not appear in the distribution either. The simulation thus does not replace the careful identification or the professional discussion of the assumptions – it only forces both to be precise.
See also: Risk aggregation · Risk assessment
Methods
Risk assessment
The risk assessment assigns each risk a probability of occurrence and an impact – either qualitatively through classes or quantitatively through ranges and distributions. The choice between the two approaches is not a matter of taste: Only quantitative assessments can be aggregated and compared with risk tolerance.
Qualitatively or quantitatively
| Criterion | Qualitatively (Classes) | Quantitatively (bandwidth) |
|---|---|---|
| Cost per risk | low | medium |
| Aggregateable | no | yes |
| Comparison with load capacity | not possible | possible |
| Suitability | Prioritization, secondary risks | Key risks, overall statement |
| Test strength | limited | given |
In practice, a two-stage approach proves to be effective: all risks are first qualitatively assessed, and the essential ones are subsequently quantitatively evaluated within certain ranges. This keeps the effort manageable, and the overall statement remains credible.
Gross and net
The gross assessment considers the risk without the existing measures and controls; the net assessment with them. The difference is the measurable contribution of the internal control system and at the same time the strongest argument in the discussion with the supervisory body about investments in controls. For aggregation and comparability of robustness, the net assessment is decisive – provided that the effectiveness of the controls is actually proven and not merely assumed.
Avoid distortions
- Availability distortion: Recent events are overestimated; long-ago events are underestimated. Remedy: structured checklists instead of free association.
- Excessive confidence: Bandwidths are estimated to be too narrow. Remedy: First query the extreme values, then use the most likely value.
- Anchor effect: The first number mentioned shapes all the other estimates. Countermeasure: independent individual estimates before the group discussion.
- Conflict of objectives: Those responsible for a risk tend to assess it more leniently. Remedy: Clarification by the second line.
See also: Risk matrix · Risk aggregation · Monte-Carlo simulation
Methods
Value at Risk (VaR)
The Value at Risk quantifies the loss that will not be exceeded within a given period with a specified probability – for example, 8 million euros with a 95 % % confidence level and a one-year observation period. It compresses an entire distribution into a single number and is therefore the most commonly used risk measure.
Read correctly
An VaR of 8 million euros at 95 % means: In 95 out of 100 scenarios the loss is lower, in 5 out of 100 higher. The statement is explicit. No, That the maximum loss is 8 million euros – the VaR does not say anything about the level of losses beyond the threshold. The Expected Shortfall fills exactly this gap.
| Confidentiality | Meaning | Typical use |
|---|---|---|
| 90 % | 1 in 10 years worse | Operational control |
| 95 % | 1 in 20 years worse | Standard in corporate management |
| 99 % | 1 in 100 years of deterioration | Capital requirement, stock depletion |
| 99,9 % | 1 in 1,000 years of poor quality | Banking supervision, rating logic |
Limits and typical applications that are not suitable
In practice, three points often lead to errors. First, the look at the number without the confidence level: a VaR without a confidence level and a time period is meaningless. Second, the interpretation as the maximum loss – in fact, the VaR describes the threshold at which things get worse, not how much worse. Third, the addition of VaR values from different areas: the VaR is not subadditive; the sum of the area VaR can be smaller than the total VaR.
For corporate management, a simple rule follows: the VaR is suitable as a communication measure to committees and banks; the decision to manage is additionally based on the expected shortfall and the probability of violating defined thresholds such as covenants or minimum liquidity.
See also: Expected Shortfall · Risk aggregation
Methods
Cash Flow at Risk (CFaR)
The Cash Flow at Risk translates the Value-at-Risk logic into the payment stream: it indicates the amount by which the planned cash flow can be exceeded with a given probability.
For industrial and commercial companies, it is usually more meaningful than the VaR on a results basis, because it is not market value fluctuations but liquidity shortages that are the typical cause of insolvency. In practice, it is held directly against the available liquidity reserves and credit lines – the result is the most reliable answer to the question of how long the company can withstand a stress event.
See also: Value at Risk · Risk coverage potential
Methods
Expected Shortfall
The Expected Shortfall – also called Conditional Value at Risk – indicates the average loss in exactly those cases where the Value at Risk is exceeded. This describes the extent of the extreme scenarios that the VaR does not cover.
Methodically speaking, it has another advantage: it is sub-additive, meaning the risk of a portfolio is never greater than the sum of the individual risks. The VaR does not meet this requirement, which can lead to paradoxical results when aggregating partial portfolios. Bank regulation has therefore gradually shifted from the VaR to the Expected Shortfall.
See also: Value at Risk · Risk measure
Methods
Scenario analysis
The scenario analysis examines the impact of consistent future scenarios on results, liquidity, and balance sheet ratios. It is particularly suitable for strategic risks that are not amenable to statistical evaluation and is explicitly required as part of climate reporting under the CSRD.
Building a scenario set
- Base Case: the approved plan with its assumptions
- Downside: plausible deterioration of several drivers simultaneously, consistently traced
- Upside: the corresponding counter-direction, the basis of opportunity management
- Extreme scenario: Unlikely, but relevant to existence – basis for the stress test
What is essential is internal consistency: a scenario with a decline in demand and at the same time rising sales prices is mathematically possible, but economically implausible and therefore unusable as a basis for decision-making.
See also: Stress test · Climate risks
Methods
Sensitivity analysis
The sensitivity analysis measures how much a target variable changes when a single influencing variable is changed – for example, EBIT at ten percent higher raw material prices. It identifies the critical levers of the business model.
In practice, it is preceded by a more elaborate simulation: it shows which five to ten drivers dominate the result. These drivers are then loaded with bandwidth and simulated – all the others can be treated qualitatively without distorting the overall result.
See also: Monte-Carlo simulation · Bandwidth planning
Methods
Stress test
A stress test examines resilience under extreme but plausible conditions – such as a 30 percent sales decline while a key supplier goes down simultaneously. It aims to determine at what point capital adequacy or liquidity begin to decline.
Invers Stress Test
The reversal of the question is particularly revealing: not „What happens in scenario X?" but „What combination of events would make us insolvent?". The inverse stress test identifies the actual breaking points of the business model and is established in banking supervision. For discussion in the supervisory board, it is usually more valuable than any scenario table.
See also: Scenario analysis · Development endangering the stock
Methods
Bandwidth planning
The bandwidth planning replaces rigid planning values with ranges of values containing a minimum, a most likely value, and a maximum. It explicitly addresses planning uncertainty and integrates controlling and risk management in a single step.
The practical advantage is significant: The ranges are also the input variables for risk simulation. Where planning is inherently based on scenarios, a separate risk survey for the planning positions is almost completely eliminated – the relevant departments provide information instead of two separate ones, and planning and the risk report no longer conflict with each other.
See also: Triangular distribution · Risk aggregation
Methods
Triangular distribution
The triangular distribution describes a risk based on three parameters: minimum, most likely value, and maximum. It is the most common distribution form in risk simulation because these three values can be determined reliably through expert assessment even without statistical history.
Their weakness lies in the strict limits: values outside the specified range are excluded. Where extreme values are relevant, the PERT distribution – a smoothed variant with stronger weighting of the most likely value – or a combination of probability of occurrence and separate damage distribution is the better choice.
See also: Distribution function · Monte-Carlo simulation
Methods
Distribution function
A distribution function describes the probability with which a risk will take on a particular form. The choice of the distribution significantly influences the simulation result and should be justified in the risk management manual.
| Distribution | Parameters | Suitable for |
|---|---|---|
| Triangular distribution | Min, most likely value, Max | Plan deviations without a history |
| PERT | like a triangle, smoothed out | Expert estimates with a focus on the middle |
| Normal distribution | Mean, standard deviation | Sizes with existing time series |
| Binomial distribution | Probability of entry | Events that happen or do not happen |
| Poisson distribution | expected frequency | rare, potentially damaging events |
| Logarithmic | Mean value, variance | Damage heights with a long right edge |
See also: Triangular distribution · Standard deviation
Methods
Expected value
The expected value is the weighted average of all possible outcomes of a risk, weighted by the probabilities of occurrence. It is useful for prioritizing, but it systematically underestimates the risk of rare large losses.
An example illustrates the problem: A risk with a probability of 1 % and a damage of 50 million euros has the same expected value as one with 50 % and 1 million euros – 500,000 euros. For corporate management, both are fundamentally different: the second is a cost factor, the first an existential question. Therefore, for assessing developments that threaten the business, the expected value is inherently unsuitable.
See also: Value at Risk · Risk assessment
Methods
Standard deviation
The standard deviation measures the dispersion of possible results around the expected value and serves as a simple measure of the magnitude of a risk.
Since it treats positive and negative deviations equally, an unexpectedly good development is evaluated just as much as a bad one as a „risk." However, corporate management is primarily interested in the downside, which is why it is increasingly supplemented by downside measures such as value at risk, expected shortfall, or the probability of failure.
See also: Risk measure · Distribution function
Methods
Risk correlation
The risk correlation describes the statistical relationship between risks. Positively correlated risks occur together and become stronger – if they are treated as independent in the aggregate, the overall risk is regularly significantly underestimated.
Handling in practice
Exact correlation coefficients cannot usually be determined empirically for corporate risks. A pragmatic approach is common and proven: risks are assigned to common drivers – economic cycle, commodity prices, exchange rates, industry cycles – and the simulation draws a common random value for the driver for each run. This creates dependence on the model without requiring coefficients to be estimated.
See also: Risk aggregation · Monte-Carlo simulation
Methods
Risk measure
A risk measure concentrates the distribution of risk into a single metric. Commonly used metrics are standard deviation, value at risk, expected shortfall, and equity requirement. The choice determines which characteristic of the distribution is visible.
The selection should be based on the control objective: if it is about variance in results, the standard deviation is useful; if it is about capital allocation, the equity requirement; if it is about stock exposure, the value at risk or expected shortfall at a high level of confidence. There is no single measure for all questions.
See also: Value at Risk · Expected Shortfall
Methods
Risk costs
Risk costs are the calculated costs of risk: insurance premiums, provisions, self-insurances and the capital costs of the equity capital tied to the risk.
Assigning risk management to specific areas, projects, or contracts makes it operationally effective. A large contract with a high percentage of upfront payments and weak customer creditworthiness attracts more risk capital than a standard business – if this is taken into account in the calculation, the pricing will change. It is precisely at this point that a documentation obligation becomes a management tool.
See also: Risk management · Risk coverage potential
Methods
Risk coverage potential
The risk coverage potential refers to the resources available to cover incurred risks: free equity, silent reserves, unutilized credit lines, and liquidity reserves. It is the quantitative expression of risk-bearing capacity.
Caution is advised when making determinations. Credit lines are regularly unavailable during a crisis precisely when they are needed; silent reserves are hardly available for short-term use. A responsible approach therefore distinguishes between availability horizons and focuses on only the short-term assets that are available in the event of a stress situation.
See also: Risk-bearing capacity · Cash Flow at Risk
Methods
Development endangering the stock
An entity-threatening development exists when risks endanger the continued existence of the company – typically through impending insolvency, over-indebtedness, or the loss of the ability to generate capital. Identifying these risks in a timely manner is the core of the legal obligation under § 91(2) AktG and § 1 StaRUG.
How to achieve proof
- Quantify risks and assign them to plan positions
- Aggregate the overall risk position, taking correlations into account
- Determine the risk coverage potential based on the availability horizon
- Compare both and determine the probability of undercoverage
- Document the results, assumptions, and conclusions
The evidence cannot be derived from a purely qualitative risk matrix. This is the practical core of the new version of the IDW PS 340 – and the most common reason for findings in the audit report.
Typical signs
- Declining order intake over several periods with a constant cost base
- Extended debtor payment periods and increasing share of overdue receivables
- Extending credit lines as a permanent state of affairs instead of as a temporary measure to compensate for shortfalls
- Approaching Covenant limits without buffers in the planning scenario
- Dependence on a large customer or single supplier without alternative
- Repeated postponement of investments due to liquidity issues
Taken individually, none of these signs is a threat to the existence of the species. Their combination is often the case – which once again shows why aggregation rather than individual consideration determines compliance with legal obligations.
See also: StaRUG · Risk-bearing capacity · IDW PS 340 n.F.
Methods
FMEA
The error-probability and impact analysis is a structured method for the preventive avoidance of errors in products and processes. Each potential error is evaluated based on its significance, probability of occurrence, and probability of detection.
Risk priority number and its criticism
Classically, the three ratings are multiplied on a scale from 1 to 10; the product is the risk priority number. The criticism of this is justified: different combinations result in the same number, although the urgency of action is different. The current AIAG-VDA system therefore replaces the simple multiplication with a task priority that weighs the importance more heavily.
For enterprise-wide risk management, the FMEA is an important source: The technical risks identified there are – insofar as they are significant – transferred into the risk inventory.
See also: Error analysis · Risk analysis
Methods
Failure analysis (FTA)
The failure analysis works in a deductive manner: Starting from an undesirable event, all possible cause chains are traced back through logical connections.
The advantage over purely qualitative methods lies in their computational feasibility: if the probabilities of the base events are known, the probability of the peak event can be calculated using the AND and OR operations. This makes FTA particularly suitable for technically complex systems with redundancies – for example, the question of how likely a complete failure of the power supply is despite two independent emergency systems.
See also: FMEA · Bow-Tie Analysis
Methods
Bow-Tie Analysis
The Bow-Tie analysis graphically represents a risk as a fly: on the left are the causes with preventive barriers; in the middle is the event; on the right are the consequences with mitigating measures. It combines risk analysis and control system into a single picture.
See also: Internal control system · Risk analysis
Methods
Delphi method
The Delphi method structures expert assessments into several anonymous rounds of questioning. Between the rounds, participants receive the aggregated results and can revise their assessment.
The anonymity mitigates the effects of authority and group pressure that, in conventional risk workshops, are generally dominant in the assessment process. For risks without a statistical data base – strategic developments, regulatory changes, technological breakthroughs – the process provides significantly more reliable assessments than a vote in plenary.
See also: Risk identification · Risk assessment
Methods
Risk Scoring
Risk scoring evaluates risks using point values in categories such as probability, impact, and controllability and aggregates them into a total score. The process is quick and broadly applicable.
The methodological boundary must be strictly observed: scores are ordinally scaled. A risk with a score of 40 is not twice as dangerous as one with a score of 20, and scores may not be added together or converted into monetary amounts. Scoring is nevertheless useful as a prioritization aid for selecting the risks to be evaluated in depth – but not as a basis for aggregation.
See also: Risk assessment · Risk matrix
Methods
Key Risk Indicator (KRI)
A key risk indicator is a metric that continuously measures the development of a risk. Unlike key performance indicators, which measure past performance, KRI looks ahead.
Criteria for good indicators
- Preliminary round: The indicator reacts before the damage occurs – otherwise it is just a damage statistic.
- Availability: The data are generated anyway within the system; indicators that have to be collected manually will no longer be maintained after two quarters.
- Clarity: A change can be clearly interpreted.
- Threshold value and escalation: Without a defined boundary and a prepared response, the indicator remains unobserved.
See also: Early warning indicator · Risk monitoring
Methods
Risk quantification
Risk quantification expresses risks in monetary units and probabilities, rather than simply assigning them to classes. It is a prerequisite for aggregation, viability comparison, and risk-adjusted decisions.
The most common objection is that the data are not available. This misses the point: Classifying a case also relies on an estimate – it merely makes it invisible. Quantification forces the disclosure and discussion of the assumption. A justified range of 2 to 9 million euros is superior to classification as „high" in every respect: it is verifiable, aggregable, and corrigible.
See also: Risk assessment · Risk aggregation
Regulatory framework & standards
Laws, audit standards and frameworks that define requirements for risk management, control systems and compliance in the DACH region – with a target audience and practical consequences.
Regulatory framework
Overview: Who needs what
The requirements for risk management and compliance arise from several sources simultaneously: corporate law, insolvency law, commercial law, auditing standards, industry-specific oversight, and European regulations. This overview organizes the most important regulations according to their intended audience.
| Requirement | Applies to | Demands at its core |
|---|---|---|
| Section 91, paragraph 2 of the AktG | AG, medium-sized GmbH | Early detection system for developments that threaten the stock |
| Section 91, paragraph 3 of the AktG | listed company | adequate and effective RMS and IKS |
| § 1 StaRUG | all companies with limited liability | ongoing crisis early warning |
| Section 130 of the OWiG | All companies | Supervisory measures against violations |
| Section 289 of the German Commercial Code | Companies subject to reporting requirements | Opportunity and risk report in the status report |
| HinSchG | from 50 employees | internal reporting point |
| SCDDA | from threshold value of the number of employees | Duty of care in the supply chain |
| CSRD / ESRS | tiered according to size and capital market exposure | Audited sustainability reporting |
| NIS2 | Companies in the sectors covered | Cyber risk management and reporting obligations |
| DORA | Financial sector | Digital operational resilience |
| MaRisk | Credit institutions | Risk-bearing capacity, control procedures, revision |
The scope of application and deadlines for CSRD, LkSG and CSDDD are being revised as part of the European Omnibus procedure. The current status for each of these is to be reviewed on a case-by-case basis – the substantive requirements for risk analysis, measures and documentation remain essentially unchanged.
Regulatory framework
KonTraG
The Act on Control and Transparency in Corporate Governance of 1998 is the starting point of legal risk management in Germany. It introduced § 91(2) AktG and for the first time explicitly obliged the board of directors to establish a monitoring system to detect emerging developments that could endanger the company.
The KonTraG was a response to a series of spectacular corporate collapses. It also expanded the duties of the auditor and the supervisory board. The so-called leverage effect applies to large GmbHs: Although the standard is directed at AGs, the duty of due diligence of a proper businessman is measured by it.
See also: Section 91, paragraph 2 of the AktG · FISG
Regulatory framework
Section 91, paragraphs 2 and 3 of the AktG
Section 91(2) of the AktG is the central standard of legal risk management: the board must take appropriate measures and, in particular, establish a monitoring system so that developments that threaten the continued existence of the company are detected early. Paragraph 3 was added with the FISG, which explicitly requires a proper and effective risk management and internal control system for listed companies.
Practical consequence
- The system must early Recognize – a snapshot at the end of the year is not enough.
- Developments that threaten the continued existence are recorded, namely illiquidity, over-indebtedness and the loss of capital-servicing capacity.
- Proof requires aggregation: individual risks in themselves are rarely a threat to the stock, but their combination certainly is.
- The arrangement must be documented – in the event of a dispute, the board of directors bears the burden of proof.
See also: Risk early detection system · IDW PS 340 n.F. · Section 317(4) of the German Commercial Code
Regulatory framework
Section 93 of the AktG and the Business Judgement Rule
Section 93 of the AktG regulates the duty of care and responsibility of the board members. The business judgment rule enshrined therein protects entrepreneurial decisions from liability when they were made based on adequate information and free from conflicts of interest for the benefit of society.
For risk management, this leads to tangible benefits: „adequate information basis" means that the risks associated with a decision have been identified and assessed. Anyone who decides to invest without documented risk assessment loses the protection of the rule – not because the decision was wrong, but because the basis was lacking. The burden of proof lies with the organ member.
See also: Managing director liability · D&O insurance
Regulatory framework
StaRUG
The Corporate Stabilization and Restructuring Act has been in effect since the beginning of 2021. § 1 StaRUG requires the managers of limited liability companies to continuously monitor developments that could endanger the company’s continued existence, to take appropriate countermeasures, and to immediately report to the supervisory authorities.
Why this has changed the world of limited companies
Prior to the StaRUG, the obligation to detect crises in shareholding law was enshrined and could only be derived from the general duty of care for GmbHs. Since 2021, this duty has been applied across all legal forms and explicitly so. This means that every GmbH, UG and GmbH & Co. KG is obliged to maintain a system that detects developments that threaten the existing business – regardless of size and the context of the capital market.
The law also includes the restructuring framework: a procedure that allows for a restructuring outside of insolvency with majority decisions by the creditors. Access requires the threat of insolvency – that is, exactly the condition that early detection should make visible in time.
What business managers need to do specifically
- Continuous monitoring of developments that could endanger the survival of the species – not on an ad hoc basis but continuously
- Integrated planning with liquidity forecasts over an appropriate period, usually rolling for at least twelve months
- Detection of crisis signs via defined indicators and thresholds
- Taking appropriate countermeasures when an endangered species is identified
- Immediate reporting to the monitoring authorities
- Documentation of all steps – in the event of liability, it is the only proof
Obligation does not end with the determination of a violation. Those who recognize a situation that threatens the existence of the business and remain passive are personally liable – early detection without subsequent action even worsens the position in the event of a dispute.
See also: Development endangering the stock · Risk early detection system
Regulatory framework
IDW PS 340 n.F.
The newly established IDW examination standard for testing the risk early detection system is to be applied for financial year end audits starting from December 15, 2021. A defining feature is the explicit requirement to aggregate individual risks into a total risk position and compare this to the risk-bearing capacity.
What has changed compared to the old version
| Aspect | Old version | Revising |
|---|---|---|
| Aggregation | not explicitly requested | specifically requested |
| Rating | qualitatively sufficient | Quantitative analysis is necessary |
| Reference for planning | loose | Link to corporate planning |
| Durability | implied | Explicit matching required |
| Documentation | System description | Understandability of methodology and assumptions |
Consequences for practice
Companies that have built their risk management into a risk matrix and action list no longer meet the standard. Quantitative assessments across a range of dimensions are required, an aggregation model, and a documented comparison with the risk coverage potential. The effort required is manageable when it is integrated into existing planning – and considerable when a second system is built in parallel.
See also: Risk aggregation · Risk-bearing capacity · IDW PS 981
Regulatory framework
IDW PS 981
IDW PS 981 describes the principles for the proper auditing of risk management systems. It divides the RMS into eight basic elements and serves as a reference framework for voluntary performance audits – for example, at the request of the supervisory board, the shareholders, or as part of a transaction.
There are three types of audits: the concept audit assesses the description, the suitability audit assesses the suitability for the target date, and the effectiveness audit assesses the operation over a period of time. The workload increases significantly in this order; for the first verification against an oversight body, the suitability audit is often sufficient.
See also: Risk management system · IDW PS 340 n.F.
Regulatory framework
IDW PS 980
IDW PS 980 is the authoritative standard for testing compliance management systems. It defines seven basic elements from compliance culture to monitoring and improvement and is the standard proof of an adequate CMS in the German-speaking world.
The examination can be limited to individual sub-areas – such as corruption prevention or cartel law – which significantly reduces the effort involved and is the standard in practice. An unqualified examination of effectiveness serves as a strong indicator to authorities, courts, and business partners that the organizational obligations have been fulfilled.
See also: Compliance management system · ISO 37301
Regulatory framework
IDW PS 982
The standard regulates the examination of the internal control system of corporate reporting. It describes the adequacy and effectiveness of controls along the reporting-relevant processes and follows the COSO framework in its structure.
With the expansion of reporting on sustainability information, it is gaining additional importance: ESG data also require a control system that ensures completeness, accuracy, and traceability – with the same requirements that have long applied to financial data.
See also: Internal control system · Sustainability reporting
Regulatory framework
IDW PS 983
IDW PS 983 describes the principles of proper auditing of internal audit systems. It is the benchmark for quality assessments that the IIA standard requires every five years from an external third party.
The structure and operation of the audit function will be examined: independence, reporting lines, qualification, risk-oriented audit planning, implementation, and follow-up of findings. For companies without their own audit function, the standard is indirectly relevant because it describes what to expect from an outsourced audit function.
See also: Internal audit
Regulatory framework
COSO ERM Framework
The COSO framework „Enterprise Risk Management – Integrating with Strategy and Performance" from 2017 explicitly links risk management with strategy and business performance. It is the most widely used ERM reference model internationally.
| Component | Key question |
|---|---|
| Governance and Culture | Who is responsible for risk, and what attitude is being taken? |
| Strategy and objectives | What risks arise from the chosen strategy? |
| Performance | How are risks identified, evaluated, and prioritized? |
| Review | Does the system still work under changed conditions? |
| Information and Communication | Do the information reach the decision-makers in time? |
See also: ISO 31000 · COSO Internal Control
Regulatory framework
COSO Internal Control Framework
The COSO framework for internal control systems defines five components – control environment, risk assessment, control activities, information and communication, and monitoring – and subdivides them into seventeen principles.
It is the de facto standard worldwide for the design of the IKS and the reference model for compliance with IDW PS 982 as well as for US SOX compliance. Its practical value lies in its completeness: the principles can be used as a checklist to check whether a mature control system contains structural gaps.
See also: Internal control system · IDW PS 982
Regulatory framework
ISO 31000
ISO 31000:2018 is the international guideline for risk management. It describes principles, frameworks, and processes, is formulated across industry sectors, and is explicitly not certification-eligible.
Its value lies in the uniform terminology and the clear anchoring of risk management within leadership responsibility. The standard is deliberately kept lean and leaves open which methods are used for evaluation – this gap is filled by the complementary IEC 31010. Those seeking a verifiable basis turn to the ONR 49000 in the DACH region.
Regulatory framework
IEC 31010
IEC/ISO 31010 supplements ISO 31000 with a catalog of assessment methods – from brainstorming and checklists to FMEA, fault tree analysis and Bow-Tie analysis, as well as Monte Carlo simulation.
For each method, the standard specifies suitability, effort, the data base required, and limitations. Therefore, for creating a risk management manual, it is the most useful source to justify the method selection – a point that the auditor regularly questions.
See also: ISO 31000 · Risk analysis
Regulatory framework
ONR 49000 ff.
The Austrian standard series ONR 49000 concretizes ISO 31000 for use in organizations and is – unlike that standard – capable of being certified.
It includes terms and principles, the risk management process, and requirements for the qualification of risk managers. In the German-speaking countries, it is particularly widespread in Austria and is often the basis for certifications that German companies find in Austrian subsidiaries.
See also: ISO 31000
Regulatory framework
ISO 37301
ISO 37301:2021 is the international standard for compliance management systems and replaces the previous ISO 19600. Unlike it, it is formulated as a requirements standard and therefore can be certified.
It follows the high-level structure and can therefore be combined with ISO 9001, ISO 14001, ISO 27001 and ISO 37001 to form an integrated management system – common leadership, common document management, common internal audits. For companies with multiple management systems, this is the biggest efficiency lever.
See also: Compliance management system · IDW PS 980
Regulatory framework
ISO 37001
ISO 37001 defines requirements for management systems to combat corruption: anti-corruption policy, due diligence of business partners, controls on payments, donations and sponsorship, and protected reporting channels.
The certification serves as an international proof of appropriate prevention measures and is increasingly required by companies from suppliers and distribution partners in high-risk markets. It does not replace an individual risk analysis, but rather structures the measures along an accepted framework.
See also: Corruption prevention · Third Party Due Diligence
Regulatory framework
FISG
The Financial Market Integrity Strengthening Act of 2021 was the legislative response to the Wirecard scandal. It requires listed companies under § 91(3) AktG to have an appropriate and effective risk management and internal control system.
In addition, it strengthens the audit committee, tightens rotation and liability rules for auditors and expands the powers of BaFin. Practically significant is the shift: What was previously a recommendation in the Corporate Governance Code is now law for the group covered by it.
See also: Section 91 of the AktG · Examination Committee
Regulatory framework
German Corporate Governance Code
The DCGK compiles principles, recommendations, and best practices for good corporate governance for publicly traded companies. It includes concrete recommendations on risk management and compliance, including an internal control and risk management system, including sustainability aspects, as well as a whistleblowing system.
The Code is not a law, but it does have effect through the compliance declaration under § 161 of the AktG: Deviations must be disclosed and justified. For non-listed companies, it serves as a guide – especially family businesses often resort to their own governance codes, which are adapted to it.
See also: Governance · Board of Supervisors
Regulatory framework
Situation report and risk report
According to § 289 HGB, the prospective development with its essential opportunities and risks must be assessed and explained in the status report. The risk report is thus the external interface of risk management.
Requirements for the risk report
- Presentation of the essential risks, not a list of all risks
- Understandable derivation from the internal risk inventory
- Indication of the assessment criteria and the overall risk situation
- Consistency with the forecast report: The risks describe deviations from the expectations presented there.
Discrepancies between internal risk situation and external presentation are a classic area of audit focus. Anyone who internally faces an asset-threatening risk and externally reports a stable situation has a problem that goes beyond accounting.
See also: Forecast report · Risk reporting
Regulatory framework
Section 317(4) of the German Commercial Code
The provision requires the auditor of listed companies to assess whether the board of directors has established the monitoring system under § 91(2) AktG in an appropriate manner and that it is capable of fulfilling its duties.
It is the legal basis for the testing according to IDW PS 340 n.F. The testing assignment is deliberately narrowly defined: The assessment is of the facility and basic functionality, not of the effectiveness over a period of time. A more extensive effectiveness assessment only takes place in a separate assignment.
See also: IDW PS 340 n.F. · Annual financial statement audit
Regulatory framework
MaRisk
The minimum requirements for risk management at BaFin concretize § 25a KWG for credit institutions. They regulate risk-bearing capacity, strategies, internal control procedures, stress tests, outsourcing management, and the design of the internal audit.
Even outside the financial sector, it is worth taking a look inside: the MaRisk describe a highly regulated risk management with high levels of detail and serve many industrial companies as a reference for topics such as outsourcing management or risk tolerance concept. For insurers, the MaGo is considered the equivalent.
See also: KWG · Outsourcing management
Regulatory framework
KWG
The Credit Institutions Act is the regulatory framework for credit institutions in Germany. § 25a KWG requires proper business organization with adequate risk management, an internal control system, and a compliance function.
For non-banks, the KWG is indirectly relevant when financial services are provided – for example, in payment processing, factoring, or corporate sales financing. The distinction between permissible activities falls within the scope of the compliance risk analysis in these cases.
See also: MaRisk
Regulatory framework
Solvency II
Solvency II is the European regulatory framework for insurance companies and is based on three pillars: quantitative capital requirements, qualitative governance requirements including the company-specific risk and solvency assessment, and reporting and disclosure obligations.
The second pillar is also insightful for industrial companies: ORSA requires a forward-looking assessment of the overall risk profile and capital adequacy over the planning horizon – methodically speaking, exactly what the IDW PS 340 n.F. requires for non-insurers.
See also: Risk-bearing capacity
Regulatory framework
Basel III and IV
The Basel frameworks define international capital and liquidity standards for banks and are implemented in the EU through the Capital Requirements Regulation and Directive.
For companies outside the financial sector, they are indirectly significant: they shape rating processes, credit conditions, and the information needs of banks. A company that can quantify its risk profile improves its bargaining position measurably – because the bank otherwise works with security surcharges.
See also: Risk aggregation
Regulatory framework
CSRD
The Corporate Sustainability Reporting Directive significantly expands sustainability reporting in the EU: reporting content according to the ESRS, the obligation to be audited by an independent third party, digital tagging, and integration into the management report instead of a separate report.
What this changes
- Inspection obligation: For the first time, sustainability data are subject to external auditing – with corresponding requirements regarding data quality and controls.
- Double significance: Reports are being made about the effects of the company and financial impact on the company.
- Value chain: The reporting limit does not end at the own work station.
- Integration: ESG risks are methodically integrated into existing risk management.
The scope of application and the initial application dates will be revised as part of the EU omnibus procedure and must be examined on a case-by-case basis.
Preparation in five steps
- Clarify applicability and timing: Consider criteria for size, capital market relevance and involvement of the company – including the question of whether an exemption via the group report is possible.
- Double materiality analysis: methodically clean, documented, and with stakeholder involvement – it determines the entire scope of the report.
- Identify data gaps: For each required entry, clarify whether the data exists, where it comes from, and who is responsible for it.
- Establishing processes and controls: Sustainability data are subject to audit and require the same level of scrutiny as financial data.
- Test run: run through a complete reporting cycle before first use, including coordination with the reviewer.
The time-critical bottleneck is regularly step three: Collecting data on locations, interests, and suppliers takes longer than the actual reporting process itself.
See also: ESRS · Double materiality analysis
Regulatory framework
ESRS
The European Sustainability Reporting Standards concretize the reporting obligations of the CSRD. They include overarching standards for general requirements and disclosures as well as thematically specific standards for environment, social and governance.
| Group | Content |
|---|---|
| Transcendent | General requirements and general information – mandatory for all |
| Environment | Climate change, pollution, water, biodiversity, circular economy |
| Social | Own workforce, workers in the value chain, affected communities, consumers |
| Governance | Corporate governance, business practices, anti-corruption |
Which topic standards to apply is determined by the double materiality analysis – with the exception of the overarching standards, which always apply.
See also: CSRD · Double materiality analysis
Regulatory framework
EU taxonomy
The EU taxonomy is a classification system for ecologically sustainable economic activities. An activity is considered taxonomy-compliant when it contributes significantly to one of the six environmental objectives, does not significantly harm others, and adheres to minimum protection standards.
Reportable companies indicate which portion of revenue, investments, and operating expenses is taxonomically and taxonomically compliant. The practical difficulty lies in the data base: the assignment requires a division of revenues and investments by activity, which accounting in this form usually does not allow for.
See also: CSRD · Sustainability reporting
Regulatory framework
Supply Chain Due Diligence Act (SCDDA)
The LkSG requires companies to implement human rights and environmental due diligence obligations in their own business operations and in the supply chain starting from a certain number of employees. It is designed as a duty of effort: an appropriate, documented approach is required, not a supply chain that is free from violations.
The nine duties in summary
| Obligatory | Specifically |
|---|---|
| Establishing risk management | Processes, responsibilities, and integration into business processes |
| Determine jurisdiction | Human rights officer or equivalent function |
| Risk analysis | annually and on occasion, abstract and concrete |
| Basic statement | approved by management, publicly |
| Preventive measures | own area and immediate suppliers |
| Remedial measures | in the event of established injuries, with a timetable |
| Complaints procedure | accessible, confidential, effective |
| Moderate suppliers | related to the occasion with substantial knowledge |
| Documentation and report | continuous, with a duty to store |
Implementation in practice
The effort focuses on three points: First, the data base: Many companies know their immediate suppliers from the ERP system, but not their production sites – these are crucial for the country risk assessment. Second, prioritization: With several thousand suppliers, it is impossible to examine each one individually, which is why the abstract analysis using portfolio criteria has to reduce the list to a manageable number. Third, the connection with purchasing: If sustainability criteria are not incorporated into awarding and contract drafting, the risk analysis remains ineffective.
For companies that are not directly affected, the obligation applies indirectly: they are required to report to reporting customers via supplier codes, self-disclosure forms, and audit rights. Therefore, a separate, streamlined approach is also advisable below the threshold values.
See also: Risk analysis according to LkSG · CSDDD
Regulatory framework
CSDDD
The Corporate Sustainability Due Diligence Directive is the European directive on corporate due diligence obligations. It extends the logic of the LkSG to the entire value chain, requires a climate transformation plan and provides for civil liability.
The scope, thresholds and timeline are being adjusted within the framework of the omnibus package; national implementation must be monitored accordingly. Regardless of the final scope, companies that have already built their supply chain processes according to LkSG must expand them within their reach, not reinvent them methodically.
See also: SCDDA · Duty of care
Regulatory framework
Whistleblower protection law (HinSchG)
The HinSchG translates the EU Whistleblower Directive into German law. It obliges companies with 50 or more employees to establish an internal reporting mechanism, protects individuals who report wrongdoing from retaliation, and sets deadlines for receipt confirmation and response.
Implementation steps
- Set up a reporting point and designate the responsible person – internally, outsourced, or in combination
- Provide reporting channels, at least in writing and verbally, for personal interviews upon request
- Create a procedural code of conduct and data protection policy, involve the works council
- Implement the authorization concept that technically ensures confidentiality
- Employees inform about the system and protection against reprisals
- Ensure deadline monitoring and documentation on the system side
- Regulate the storage of case documentation in accordance with legal requirements
Group-wide reporting channels are permissible, but individual subsidiaries with 50 or more employees are not exempt from their own responsibility – the responsibility for follow-up measures must remain clearly assigned.
See also: Internal reporting system · Prohibition of Repression
Regulatory framework
Sections 30, 130 of the OWiG
The two regulations of the Code of Administrative Offenses are the legal basis for corporate liability in Germany. § 130 of the Code of Administrative Offenses sanctions the violation of the duty of supervision, § 30 of the Code of Administrative Offenses allows the imposition of fines against the company itself.
The practical significance is significant: Not only those who commit a violation are punished, but also those who could have prevented it through proper supervision. What „proper supervision" means is determined by the company’s risk profile – and this is precisely the reason why a documented compliance risk analysis is necessary.
See also: Organizational shortcomings · Compliance management system
Internal control system
Controls as the operational implementation level of risk management – design, effectiveness, verification, and the distinction from audit and compliance.
Internal control system
Internal control system (IKS)
The internal control system encompasses all the principles, procedures, and measures that ensure the effectiveness of business operations, the reliability of reporting, and compliance with legal requirements. While risk management identifies and assesses risks, the IKS limits them through concrete controls in the process – the difference between gross and net risk is precisely its measurable performance.
The five components according to COSO
The COSO framework is the de facto standard internationally and also the reference for auditing according to IDW PS 982. It describes five interacting components – if one of them is neglected, the others lose their effectiveness.
| Component | Content | Practical implementation |
|---|---|---|
| Control environment | Integrity, values, organizational structure, competence | Code of conduct, job descriptions, four-eyes principle at management level |
| Risk assessment | Identification of the error risks per process | Risk Control Matrix, Thresholds of Significance |
| Control activities | The controls themselves | Authorizations, approvals, authorization concepts, system tests |
| Information and Communication | Availability of relevant information | Process documentation, training, reporting channels |
| Surveillance | Ongoing and separate efficacy study | Control tests, self assessments, internal audits |
Control types
| Distinction | Type A | Type B | Example |
|---|---|---|---|
| Time | preventive (prevented) | detective (covers up) | Grant limit vs. account approval |
| Design | manually | automated in the system | Visual inspection vs. system lock-out in case of exceeding the limit |
| Meaning | Key control | additional control | Payment release vs. sample verification master data |
| Frequency | related to the event | periodically | per order vs. monthly vote |
Automated controls are superior to manual ones because they are not forgotten and generate their own proof of compliance. The effort required for effectiveness tests is significantly reduced: in a system control, proof is sufficient that the configuration remained unchanged during the testing period, whereas a manual control requires evidence from samples.
Building along the processes
- Process map: Distinguish between leadership, core, and support processes and appoint responsible parties.
- Defining materiality: Only deepen processes with relevant impact on completion, legality, or operational capability.
- Identify risks at each process step: What can go wrong – completeness, accuracy, legitimacy, timing?
- Assigning controls and closing gaps: Start existing controls, formulate control objectives, and add missing ones.
- Key controls determine: Select and justify risk-orientedly which controls are to be tested.
- Create a test plan: Determine the sample size, method, and frequency of each inspection.
- Transferring findings into measures: With responsible party, deadline, and proof of the remedy.
Appropriateness and effectiveness
Both terms are frequently confused, but they refer to different exam questions. The Appropriateness asks: Is the control designed in such a way that it can achieve the control goal? The Effectiveness It asks: Was it actually performed consistently and correctly throughout the examination period? A perfectly described control that has no evidence of having been performed is considered not to have been performed in the test.
Practical rule: No control without proof. If it is not documented who checked what when, the control does not exist for the auditor – regardless of how reliably it is actually implemented.
Legal framework
- Section 91, paragraph 3 of the AktG: Listed public companies require an adequate and effective internal control system.
- Section 289, paragraph 4 of the German Commercial Code: Capital market-oriented companies describe the key features of the accounting-related IKS in their annual reports.
- IDW PS 982: Standard for the separate review of the IKS for corporate reporting.
- Industry-specific: MaRisk for credit institutions, DORA for the financial sector, GoBD for tax-related processes.
Controls along the core processes
| Process | Central risk | Key control |
|---|---|---|
| Shopping to payment | Payment without performance | Three-way reconciliation of orders, incoming goods, and invoices |
| Order until payment received | Revenue without creditworthiness | Credit limit check before order approval |
| Personnel | fictitious employees, false benefits | Matching personnel records with salary records by a second person |
| Fixed assets | Activation of non-existent goods | Inventory with reconciliation against asset accounting |
| Payment transactions | Reversal of payments | Four-eye approval, bank data change with callback verification |
| Conclusion | Inappropriate bookings | Evaluation of manual journal entries based on thresholds |
| IT permissions | Uncontrolled access | Periodic recertification of critical roles |
Typical weaknesses in practice
- Checks without proof: The test takes place, but it is not documented – in the test it does not exist.
- Control description without response: It is regulated what is being tested, but not what happens in the event of a deviation.
- Person-related controls: Descriptions list names instead of roles and become useless when personnel changes.
- Four-eye principle only on paper: The second reviewer draws up the report without having access to the examination basis.
- No adjustment for process changes: The control system describes a process that no longer exists.
- Overcontrol: Hundreds of documented inspections without prioritization tie up capacity that is lacking for the essential ones.
Frequently asked questions
How many controls does a medium-sized company need?
There is no fixed number. There are 80 to 200 documented inspections, of which 30 to 60 are tested as key inspections. What matters is not the quantity but the coverage of the essential risk of errors.
How is the IKS different from internal auditing?
The IKS is part of the ongoing process and is carried out by the first line. The Internal Audit department, as a third line, independently examines whether this system is appropriate and effective. The audit is therefore not part of the IKS, but its monitoring.
Is an Excel control matrix sufficient?
For entry-level use, yes. As soon as test results, evidence, and measures must be traceable over multiple periods, the table reaches its limits – especially when it comes to versioning and proving who did what evaluation when.
See also: Risk management system · Three Lines Model · Compliance management system
Internal control system
Accounting-related IAS
The accounting-related internal control is the part of the control system that ensures the regularity of bookkeeping and the preparation of financial statements. It is the focus of the audit and the audit according to IDW PS 982.
The closing-related processes – procurement and liabilities, sales and receivables, personnel, fixed assets, inventories, liquidity, and the closing process itself – are covered; this includes IT application controls and general IT controls. Capital market-oriented companies additionally describe the essential features in the annual report under § 289 (4) of the German Commercial Code (HGB).
See also: Internal control system · IDW PS 982
Internal control system
Control target
A control objective describes the risk that a control is intended to cover – for example, the completeness of captured sales or the eligibility of payment releases. Without a formulated control objective, neither adequacy nor effectiveness can be assessed.
For accounting purposes, standardized control objectives have been established: completeness, accuracy, existence, evaluation, ownership, and periodization. Each control is assigned to one or more of these objectives; gaps in the assignment are also gaps in the control system.
See also: Risk Control Matrix · Control design
Internal control system
Control design
The control design describes how a control is designed: who carries it out, how often, on what information basis, with what evidence and with what response in the event of deviations.
The five Ws of the control description
- Who performs the control – role, not person
- What is checked against the target value
- When and how often
- With what – which evaluation, which system, which evidence
- What comes next in case of deviation – correction, escalation, documentation
If one of these elements is missing, the control cannot be tested. The most common gap is the last point: Many control descriptions end with testing and leave open what happens with a finding.
See also: Control effectiveness · Proof of compliance
Internal control system
Control effectiveness
The effectiveness of the control assesses whether an appropriately designed control was actually carried out consistently and correctly during the audit period. The verification is done through sample tests based on documented control evidence.
| Frequency | Population p. a. | Sample (reference value) |
|---|---|---|
| annually | 1 | 1 |
| quarterly | 4 | 2 |
| monthly | 12 | 2 to 3 |
| weekly | 52 | 5 to 8 |
| daily | 250+ | 15 to 25 |
| related to the event | variable | 25 to 40 |
Appropriate but not implemented control is considered ineffective. The finding „Design effective, operating ineffective" is the standard in initial inspections – mostly because evidence was not kept.
See also: Verification test · Gross and net risk
Internal control system
Key control
Key controls are those controls whose failure would directly lead to a significant error or damage. Limiting the effectiveness tests to them keeps the testing effort manageable.
The selection must be justified and documented with a risk-oriented approach. Criteria include the level of risk covered, the absence of compensating controls, and the dependence on further process steps. As a rule of thumb: if the failure of a control leads to a significant error without additional safeguards, it is a key control.
See also: Verification test · Risk Control Matrix
Internal control system
Preventive and detective controls
Preventive controls prevent errors in advance – authorization concepts, permission limits, plausibility checks during input. Detective controls detect already occurring errors – reconciliations, evaluations, recalculations.
A robust ICS combines both types. Pure detective systems react systematically too late: The error has occurred, the damage has often already occurred. Pure preventive systems, on the other hand, remain blind to errors that have circumvented prevention – for example through management override.
See also: Management Override · Separation of functions
Internal control system
Risk Control Matrix (RCM)
The Risk Control Matrix connects process steps, risks, control objectives, and controls into a structured overview. It is the central working document of the IKS.
| Columns | Content |
|---|---|
| Process / Sub-process | Assignment along the process map |
| Risk | What could go wrong in this step? |
| Control target | Completeness, accuracy, legitimacy … |
| Control description | The five Ws of control design |
| Type | preventive / detective, manual / automated |
| Key control | yes / no with reason |
| Responsible | Role, not person |
| Evidence | which document documents the execution |
| Test result | Date, sample, finding, measure |
See also: Internal control system · Process land map
Internal control system
Verification test
The control test examines whether a check was carried out during the period under review using a sample. The test procedures are questioning, observation, inspection, and verification – in that order, with increasing probative value.
The result is classified as effective, limited effective, or ineffective. Any deviation must be documented and evaluated: is it an isolated case or a systematic failure? This distinction determines whether further work is required or the control design must be modified.
See also: Control effectiveness · Action management
Internal control system
Walkthrough
During the walkthrough, a single business case is fully tracked through the process to understand the actual control design and verify the process documentation.
It serves to assess adequacy and does not replace an effectiveness test – a single observation does not allow for an assessment of the entire period. Its practical value lies elsewhere: walkthroughs regularly reveal that the documented process description differs from the lived practice.
See also: Verification test · Control design
Internal control system
Functional segregation (Segregation of Duties)
The separation of functions prevents a person from creating, sharing, and billing a process alone. It is the most effective preventive control against fraudulent actions.
| Area | To be separated | Risk if violated |
|---|---|---|
| Shopping | Order, goods receipt, invoice verification | Fake deliveries |
| Payment transactions | Master data management, payment release | Reversal of payments |
| Accounting | Booking, account reconciliation | Disguising differences |
| Personnel | Personnel policy, salary approval | fictional employees |
| IT | Development, Release, Productization | Uncontrolled changes |
In small units, complete functional separation is not always possible. Then compensatory controls are required – such as the downstream review by the management – and this decision must be documented.
Implementation in the system
Technically, functional separation is represented through role concepts and conflict matrices. A conflict matrix lists combinations of permissions that must not be held by one person; it is regularly checked against the roles actually assigned. Violations are rarely intentional, but result from delegation arrangements, accumulation of roles during position changes, and project-specific additional rights that are not withdrawn.
Therefore, two controls are included: the periodic recertification of critical permissions by the relevant departments and the automated evaluation of role conflicts after each permission change. Where separation is not possible organizationally, a compensatory control is documented – for example, the subsequent individual review of all processes by an independent authority.
See also: Role and rights concept · Management Override
Internal control system
Management Override
Management Override refers to the circumvention of existing controls by the management level. It is the structurally most severe control risk because controls against their own exceptions are hardly designed.
Therefore, countermeasures are being taken elsewhere: complete logging of all exceptions and manual bookings, the four-eyes principle also at the management level, the evaluation of unusual journal entries, a functioning whistleblowing system, and independent auditing by internal review and oversight bodies. In almost all major balance sheet scandals, management override was the central mechanism.
See also: Whistleblower system · Internal audit
Internal control system
Process land map
The process map divides the company into leadership, core, and support processes and forms the structure on which risks and controls are anchored.
It ensures that the IKS is built in a process-oriented rather than department-oriented manner – and thus also applies where processes cross departmental boundaries. It is precisely at these interfaces that most control gaps arise: Each department assumes that the other has already conducted an audit.
See also: Risk Control Matrix · Internal control system
Internal control system
Action management
The action management system controls the correction of identified weaknesses: Each finding is accompanied by a measure with a responsible party, deadline, status and proof of effectiveness.
It is the interface where risk management, internal audit, internal control, and compliance come together – and in practice, it is the most common reason to replace Excel with a workflow-based solution. The reason is simple: findings arise in four systems, the implementation of which is overseen by the same departments, and no one knows the overall status.
See also: Action tracking · Risk management
Internal control system
Internal audit
The Internal Audit is the independent, objective auditing and advisory function of the third line. It assesses the adequacy and effectiveness of risk management, internal control, and governance and reports directly to the management and the audit committee.
Requirements for independence
- Direct reporting line to the management and monitoring body
- No responsibility for the operational processes that they oversee
- Unrestricted right of information and access
- A budget of your own, independent of the areas audited
In medium-sized structures, the function is often outsourced or carried out as a part-time position. Both are permissible as long as the independence is maintained – it becomes problematic when the same person designs and subsequently audits processes.
Procedure of an exam
- Notice of examination and request for documents
- Opening meeting with the audited area, coordination of scope and schedule
- Examination procedures: document analysis, interviews, sampling, data analysis
- Findings with facts, cause, risk and recommendation
- Final meeting with a statement from the department
- Report to Management and Audit Committee
- Traceability to the proven implementation – the step that determines effectiveness
Good determinations identify the cause, not just the symptom. „Three out of twenty payments without a second approval" is a finding; „the approval limit is not set in the system; it is organized in an organizational manner" is the cause that a measure can address.
See also: Three Lines Model · IDW PS 983
Internal control system
Exam planning
The risk-oriented testing planning is based on the risk inventory to determine which processes and units are tested at what intervals.
It combines risk management and internal audit methodically: audit priorities follow the risk situation, not the habit. A multi-year plan is common, covering all essential processes within a defined cycle, supplemented by annual focus areas and a reserve for ad-hoc audits.
See also: Internal audit · Risk inventory
Internal control system
Proof of compliance
The audit trail documents that an audit was performed – a release log, a recorded vote, a system log. Without proof, an audit in the test is considered not performed.
Evidence generated by the system has higher probative value than manual evidence because it cannot be created retrospectively. What matters is its preservation: Evidence must be available and discoverable throughout the entire examination period – a confirmation of release by email in the personal mailbox does not meet this requirement.
See also: audit compliance · Audit Trail
Compliance Management
Development, testing and effectiveness of compliance management systems – from risk analysis to the program and the termination of the management team.
Compliance
Compliance management system (CMS)
A compliance management system brings together all measures to prevent, detect, and address regulatory violations. It is not a self-standing goal: an appropriate and demonstrably effective CMS can have a mitigating effect on fines, is a central element of management accountability, and is increasingly required by business partners as a prerequisite for admission.
The seven basic elements according to IDW PS 980
| Element | Content | Evidence |
|---|---|---|
| Compliance culture | Basic attitude and behavior of management | Tone from the Top, Dealing with Violations, Employee Survey |
| Compliance goals | Which rules should be adhered to in what extent | Compliance guideline, target system |
| Compliance organization | Roles, resources, reporting paths | Organigram, Job description Compliance Officer |
| Compliance risks | Systematic analysis of legal risks | Documented compliance risk analysis |
| Compliance program | Derived measures | Policies, processes, controls, training plan |
| Compliance communication | Information and reporting channels | Training certificates, whistleblower system, reports |
| Monitoring and improvement | Effectiveness control of the system | Monitoring, audit reports, follow-up of measures |
Compliance risk analysis
It is the starting point of the entire system and at the same time the element that is first questioned in the audit case. Without documented risk analysis, it is not possible to justify why certain measures were taken or why others were omitted – and it is precisely this justification that determines the adequacy.
The analysis takes into account industry, markets, sales model, procurement structure, involvement of public contracting authorities, and experience from previous incidents. The resulting prioritization is as follows: In an export-oriented plant builder, corruption, export and sanctions risks dominate; in a consumer-oriented trading company, cartel, product and data protection risks predominate.
Effect of liability
According to §§ 30 and 130 of the German Civil Code (OWiG), fines can be imposed on companies and management personnel when reasonable supervisory measures are lacking – even without the involvement of the company itself in any wrongdoing. The jurisprudence recognizes that an effective CMS is taken into account when determining the amount of fines; what is crucial is not the existence of documents, but the demonstrable effectiveness in practice.
A CMS that is reviewed and documented following an incident also acts as a mitigating factor. However, the significantly more cost-effective way remains to be able to demonstrate the appropriateness beforehand.
Standards and certification
| Standard | Character | Special feature |
|---|---|---|
| IDW PS 980 | Examination standard | Examination judgment regarding conception, adequacy and effectiveness |
| ISO 37301 | Certifiable management system standard | Integrable with ISO 9001 and ISO 27001 through the High-Level Structure |
| ISO 37001 | Certifiable, thematically focused | Specifically, combating corruption, internationally recognized proof |
Construction in practice
- Inventory overview: What policies, processes, and controls already exist – often more than assumed, but not systematically implemented.
- Compliance risk analysis: Legal cadastre, risk drivers, assessment, prioritization.
- Clarifying responsibilities: Compliance function, interfaces to the law, revision, data protection, personnel.
- Organizing the rules: Code of conduct as a framework, including guidelines on prioritized risks.
- Establishing processes and controls: Business partner verification, approvals, sanctions screening – where the risk arises.
- Set up reporting paths: Whistleblower system with case processing and deadline monitoring.
- Schools and communicating: risk-oriented according to target groups, with documented participation.
- Monitor and improve: Key figures, samples, annual update of the risk analysis.
How effectiveness can be measured
| Indicator | What it shows | Caution |
|---|---|---|
| Training rate per risk group | Reaching the target groups | says nothing about understanding |
| Number of received tips | Trust in the system | Low numbers are not success |
| Processing time for cases | Efficiency of the reporting point | Fulfillment of deadlines is mandatory, not performance. |
| Share of audited high-risk business partners | Covering due diligence | The depth of the examination determines it |
| Urgent measures | Power of the function | the most meaningful of all |
Frequently asked questions
At what company size is a CMS required?
There is no threshold for size. The duty of supervision under § 130 of the German Insurance Act applies to every company; the scope and depth depend on the risk profile, industry, and the degree of internationalization. An exporting medium-sized company with intermediaries in high-risk countries needs more than a regionally based service provider.
What does certification cost?
This depends on size, number of locations, and level of preparation. The majority of effort is not incurred by the audit itself, but by closing the gaps that become apparent in advance – usually during risk analysis, evidence gathering, and action follow-up.
Can the CMS be connected to risk management?
Yes, and it is highly recommended. Compliance risks are a category of the enterprise-wide risk inventory. The same scales, the same action logic, and a common data base prevent duplicate surveys and conflicting reports to the supervisory body.
See also: Internal control system · Three Lines Model · Risk management system
Compliance
Compliance
Compliance refers to the adherence to all legal requirements applicable to the company as well as to internal rules established by the company itself. The term encompasses more than regulatory compliance: it includes the organizational responsibility of the management to prevent violations through appropriate structures.
This organizational requirement is the core of the matter. A violation by an employee does not in itself constitute corporate liability – it only arises when reasonable supervisory measures have been omitted. Compliance is thus less a question of intention than of proof: what is not documented is considered not to have occurred in the proceedings.
See also: Compliance management system · Organizational shortcomings
Compliance
Compliance risk analysis
The compliance risk analysis identifies the legal risks relevant to the company and assesses them according to their probability of occurrence and potential damage. It is the starting point for any CMS and the element that is first questioned in the audit.
Action
- Creating a legal framework: Which legal areas are relevant to the business model and markets?
- Risk drivers determine: Foreign business, intermediaries, public contracting authorities, cash business, regulated products
- Evaluate based on potential damage – fines, compensation for damages, exclusion from tenders, damage to reputation
- Compare existing measures and identify gaps
- Prioritize and include deadlines in the compliance program
Without documented risk analysis, it is not possible to justify why certain measures were taken and others were avoided. It is precisely this justification that determines the adequacy of the system.
See also: Compliance program · Compliance management system
Compliance
Compliance culture
The compliance culture describes the basic attitude within the company regarding compliance with regulations. It is significantly shaped by the behavior of the management level and determines whether guidelines are followed or circumvented.
Reviewers assess them through employee surveys, the handling of past violations, and the consistency of target goals and compliance expectations. The most revealing indicator is the goal conflict: If sales targets are only achievable under the threat of questionable practices, the culture is defined regardless of any code of conduct.
See also: Tone from the Top · Risk culture
Compliance
Compliance program
The compliance program brings together the measures derived from the risk analysis: guidelines, processes, controls, training, and communication formats.
Risk-oriented prioritization is crucial. A program that treats all issues equally ties resources to secondary risks and leaves the actual main risks understaffed. Practically speaking, this means that in a company with intensive international sales through intermediaries, anti-corruption prevention and business partner vetting should be at the top of the list—not annual data protection training for everyone.
See also: Compliance risk analysis · Training management
Compliance
Compliance Officer
The compliance officer is responsible for the development and operation of the CMS, advises the departments, monitors compliance with the rules, and reports to the management. Professional independence, sufficient resources, and a direct reporting line are crucial.
Jurisprudence has assigned a special role to the function: Those who assume compliance responsibility can themselves be liable in individual cases if they fail to pursue recognized violations. However, the overall responsibility remains with the management – tasks can be delegated, not the duty to select, equip, and monitor.
See also: Compliance responsibility of management · CMS
Compliance
Code of Conduct
The code of conduct sets out the binding principles for the conduct of employees and managers – regarding corruption, conflicts of interest, gifts, competition, discrimination, and the handling of information.
It will only become effective through three additions: concretization in guidelines with clear value limits and procedures, mandatory training with documented knowledge, and consistent sanctions for violations. A code without these three elements is an image document and worthless in the process.
See also: Guidelines management · Training management
Compliance
Guidelines management
The policy management controls the lifecycle of internal regulations: creation, approval, publication, awareness, periodic review, and termination.
Compliance can only be proven if it is documented which version applied at which time and which employees were aware of it. A common failure is the lack of an override process: Over the years, contradictory regulations accumulate, and in an emergency, it is no longer possible to determine which rule applied at the time of the incident.
See also: Document management · Code of Conduct
Compliance
Training management
The training management plans, conducts, and documents compliance training based on target groups. Traceability is crucial: participation rates, tester results, and repeat intervals are the evidence that supports the appropriateness in the event of an emergency.
| Target group | Topic | Turnus |
|---|---|---|
| All employees | Code of Conduct, Reporting channels | Upon entry, then every 2 years |
| Sales and Purchasing | Corruption, gifts, cartel law | annually |
| Executives | Duty of supervision, handling of warnings | annually |
| Export, logistics | Sanctions, export control | annually |
| IT, Personnel | Data protection, information security | annually |
See also: Compliance program
Compliance
Corruption prevention
Corruption prevention encompasses all measures against bribery and the granting of benefits: conduct rules regarding gifts and invitations with value limits, approval processes for donations and sponsorship, controls on intermediaries and consultants, and the screening of business partners.
Typical risk areas
- Intermediaries and sales representatives: Excessive commissions as hidden payment methods
- Official contact: Authorizations, customs, award procedures – stricter standards apply here than in private business
- Donations and sponsorship: Grants with close ties to decision-makers
- Invitations and catering: Appropriateness and context
- Facilitation Payments: criminal in Germany, even if it is common practice locally
Effective individual measures
| Action | It acts against | Evidence |
|---|---|---|
| Value limits for gifts and invitations | Slewing of benefits | Guidelines, release protocols, registers |
| Grant process for donations and sponsorship | Hidden subsidies | Application, decision, recipient verification |
| Provision limits and proof of service for intermediaries | Payment channels for bribery | Contract, proof of employment, payment release |
| Due diligence of business partners | Risk from third parties | Test report, release, resubmission |
| Rotation requirement in sensitive functions | solid relationships | Personnel process |
| Whistleblower system | Disclosures | Case statistics, processing documentation |
The most effective leverage is rarely an additional guideline; rather, it is the integration of the review into the process: a mediation agreement that cannot be put into place without documented due diligence in the system is more effective than any training.
See also: ISO 37001 · Third Party Due Diligence
Compliance
Compliance with cartel law
Cartel law compliance aims to prevent restrictive agreements that restrict competition, the abuse of dominant market positions, and unlawful vertical agreements such as second-hand price fixing.
Key risk areas include association meetings, trade shows, and any exchange of information with competitors – including about prices, capacities, or customer assignments. Due to the fine amount of up to ten percent of the company’s turnover and the whistleblower regulation that privileges the first whistleblower, clear rules of conduct for competitive contacts and a functioning internal reporting system are standard practice.
See also: Whistleblower system · Compliance risk analysis
Compliance
Money laundering prevention
The money laundering law obliges certain companies to exercise due diligence towards their contractual partners: identification, determination of the economic operator, investigation of the business purpose, ongoing monitoring, and reporting of suspicious cases to the FIU.
Obligated parties are not only financial service providers, but also, among others, freight forwarders up to a certain cash payment limit, real estate agents and trustees. They require internal risk management with documented risk analysis, internal security measures and – for certain amounts – a money laundering officer.
See also: Sanction review · Third Party Due Diligence
Compliance
Sanction and embargo review
The sanctions review compares business partners, recipients, and payments with the sanctions lists of the EU, the United Nations, and, if applicable, the United States. Violations are subject to fines regardless of fault and may have criminal consequences.
The review must be carried out continuously, as lists are subject to change at short notice – a check at contract conclusion is not sufficient. In practice, it is carried out via automated screening runs in the ERP or compliance system against updated lists, with documented hit processing. Ownership control must also be taken into account: companies that belong to the majority of the listed individuals may be blocked without actually being listed themselves.
See also: Business partner verification · Money laundering prevention
Compliance
Third Party Due Diligence
The business partner due diligence checks suppliers, intermediaries, consultants, and sales partners in a risk-oriented manner before the conclusion of a contract – on economic conditions, ownership structure, sanctions list hits, corruption index of the country of residence, and negative press reports.
| Risk class | Criteria | Examination scope |
|---|---|---|
| low | EU seat, standard performance, no contact with officials | Trade register, sanction lists |
| medium | Foreign presence, recurring volume | in addition, ownership structure, media research, self-disclosure |
| high | Intermediary, high-risk area, contact with authorities | in addition, references, external research, board approval, contractual clauses with audit rights |
Process and documentation
The process begins with a risk assessment based on fewer objective criteria – country of residence, type of service, volume, contact with officials, mediating role. Only then does the depth of the review take place. This prevents the same effort being applied to every supplier, and makes prioritizing against reviewers more justifiable.
The classification, the testing steps performed, the results, any findings made, and the decision to grant approval must be documented. Any decision to grant approval must include any conditions. In the case of non-rejection findings, the rationale must be kept particularly carefully in mind – these cases are examined in the event of an emergency. In addition, testing and audit rights, compliance assurances, and extraordinary termination rights must be included in the contract.
See also: Corruption prevention · Supplier evaluation
Compliance
Business partner verification in the database
The business partner review is the ongoing continuation of the due diligence: periodic resubmission according to risk class, ad hoc review for suspicious activities, and automated monitoring of sanction and negative list.
It prevents a one-time review from becoming a routine matter at the start of a contract. Triggering factors for a case-specific review include shareholder changes, changes to the bank account details, unusual commission demands, payments in third-party countries, and negative media reports.
See also: Third Party Due Diligence · Sanction review
Compliance
Conflict of interest
A conflict of interest exists when personal interests can influence the objective perception of official duties – in the case of side jobs, involvement in suppliers or contracting with employees.
A conflict in itself is not a violation; the problem arises only when the conflict is inexplicable. Therefore, typical controls include the disclosure of the conflict, the keeping of a record, the exclusion from the decision in question, and – in serious cases – the documentation of the protective measures taken.
See also: Code of Conduct · Compliance management
Compliance
Breach management and case management
The compliance management regulates the handling of warnings and suspected cases: recording, plausibilization, internal investigation, decision on consequences and the derivation of preventive measures.
Principles of the internal investigation
- Separation of investigation and decision-making regarding consequences
- Preservation of the confidentiality and the rights of the persons concerned
- Evidence gathering before the first interview, not after it
- Inclusion of data protection and, if applicable, the works council
- Complete documentation of every step
- Conclusion with measures that address the cause – not just the individual case
See also: Case handling in the whistleblower system · Action management
Compliance
Compliance Reporting
The compliance reporting informs management and the supervisory board about risk situations, number of cases, training rates, status of open measures, and regulatory changes.
A meaningful report does not stop at activity metrics alone. The number of training sessions conducted says little; the question of whether the measures cover the identified main risks and whether the controls are effective answers the information needs of the oversight body. Notably low reporting rates are not a success, but a warning sign of a lack of confidence in the reporting system.
See also: Whistleblower system · Risk reporting
Compliance
Tone from the Top
Tone from the Top describes the visible attitude of the company management towards integrity and compliance with regulations – expressed in communication, target systems, promotion decisions, and in the handling of discovered violations.
It is considered the most important individual factor for the effectiveness of a CMS. The reason is simple: Employees do not base their decisions on documents but on what remains unaddressed in their environment. If a sales manager with strong sales figures is promoted despite evidence of wrongdoing, every training session becomes worthless – hence the term „tone from the middle" is increasingly being used, as middle management shapes everyday life.
See also: Compliance culture
Compliance
Organizational shortcomings
Organizational negligence refers to the violation of the duty to organize operations in such a way that legal violations are prevented. Under §§ 30 and 130 of the German Civil Code (OWiG), companies and management personnel can be fined if supervisory measures are not taken.
This is the central legal justification for a documented CMS – and at the same time the reason why documentation is not a self-standing goal: In the proceedings, the company must explain which supervisory measures were taken. If this is not done, the authority assumes that they were not carried out.
See also: Sections 30, 130 of the OWiG · Compliance management system
Whistleblower system
Reporting points, channels, deadlines, and case processing under the Whistleblower Protection Act – and why the reporting system is the most effective detection instrument of all.
Whistleblower system
Whistleblowing and whistleblower system
A whistleblower system allows employees and third parties to report legal violations confidentially. It is also a legal obligation and the most effective detection tool: a significant proportion of all economic crimes is discovered through tips, not through inspections or audits.
What determines acceptance
- Trust in confidentiality: separate authorization concept, no oversight by superiors
- Accessibility: multiple channels, also for external third parties and in the languages of the workforce
- Feedback: Anyone who never finds out whether something happened will not report it a second time.
- Visible consequences: anonymized reporting on processed cases
- Protection from Repressals: not only legally, but also visibly lived by
Low reporting rates are not proof of quality. A system without reporting is usually a system without trust – not a company without violations.
Introduction and operation
The introduction determines the later use of the system. It has proven beneficial to design the system together with the works council before launch, to publish the procedures, and to formulate communication not as a mandatory notification but as an invitation: the goal is to learn about problems early on, not to point the finger at colleagues.
In operation, three key indicators are significant: the number of reports relative to the size of the workforce, the proportion of reports that lead to action, and the average time until the first follow-up. What is striking is not so much a high number of reports as a persistently very low number – it indicates a lack of trust or a lack of awareness, not a commitment to compliance.
See also: Whistleblower protection law · Internal reporting system
Whistleblower system
Internal reporting system
The internal reporting line receives reports, confirms receipt, checks their accuracy, maintains contact with the person who submitted the report and takes follow-up action. Companies with 50 or more employees must establish one.
The persons appointed must be independent and knowledgeable. The task can be assigned internally – for example to compliance, legal or internal audit – or outsourced to an external third party, often to a law firm or an ombudsman. The responsibility for setting up and fulfilling the obligations remains in each case with the company.
See also: External reporting point · Confidentiality obligation
Whistleblower system
External reporting point
In addition to the internal reporting line, people who provide information are also able to use an external reporting line – in Germany with the Federal Office of Justice, and in special cases with BaFin and the Federal Cartel Office.
Whistleblowers have the choice between an internal and an external route; there is no requirement for prior internal reporting. This is exactly the company’s own interest: an easily accessible, trustworthy internal system increases the likelihood that a wrongdoing will first be known internally and can be rectified internally.
See also: Internal reporting system · HinSchG
Whistleblower system
EU Whistleblower Directive
Directive (EU) 2019/1937 establishes minimum protection across Europe for individuals who report breaches of Union law. It obliges to internal reporting channels, defines deadlines and prohibits reprisals.
For companies with subsidiaries in several Member States, national implementation is relevant: it differs in details, such as the admissibility of group-wide reporting and the scope of application in fact. A system that is uniform across the group is possible, but it must meet the stricter national requirement in each case.
See also: Whistleblower protection law
Whistleblower system
Anonymous report
Anonymous reports are made without disclosing the identity. According to the HinSchG, they are to be processed; there is no requirement to maintain anonymous reporting channels.
They are nevertheless practically recommended. The barrier to entry is significantly lowered, and through anonymized dialogue functions, the inquiry remains possible – the crucial point, because anonymous reports without the ability to request access are often too generic for investigation. Digital systems solve this problem through an anonymous mailbox with a code of access.
See also: Reporting channel · Case handling
Whistleblower system
Reporting channel
Reporting channels are the ways in which information can be submitted – verbally by phone, in person if desired, in writing or through a digital reporting system.
| Channel | Advantage | Weakness |
|---|---|---|
| Digital reporting system | anonymous possible, time limit monitoring, complete documentation | Implementation effort |
| Ombudsman / Law firm | high level of trust, legal confidentiality | ongoing costs |
| Telephone hotline | low threshold | Documentation is elaborate, anonymity is limited |
| Email mailbox | Quickly set up | No anonymity, access control difficult |
| Personal conversation | legally make it possible upon request | Recording required |
See also: Anonymous report · Internal reporting system
Whistleblower system
Case handling in the whistleblower system
The case processing follows a defined sequence of steps: initial confirmation, plausibility check, investigation, decision on measures, and notification to the person who reported the issue.
Every step must be documented – for the purpose of proving compliance with deadlines and to provide evidence for subsequent employment or criminal proceedings. In addition, the handling of cases that concern the reporting body itself or the management must be regulated: for this scenario, a predefined escalation path is needed, usually directly to the supervisory body.
See also: Compliance management · Deadlines in the reporting process
Whistleblower system
Confidentiality obligation
The confidentiality requirement obliges the reporting body to protect the identity of the person reporting the information, the affected individuals, and other named individuals. Any further disclosure is permitted only in strictly limited statutory exceptions.
Organisationalally, this requires a strictly separated authorization concept: Supervisors should not have access to cases within their own area of responsibility, and IT administrators should also not be able to view case content. This exact requirement is where improvised solutions through email folders or network drives fail.
See also: Role and rights concept · Prohibition of Repression
Whistleblower system
Prohibition of Repression
Persons who report wrongdoing must not be disadvantaged due to a legitimate report – neither through termination, warning, or transfer, nor by withholding promotions or further training.
The law reverses the burden of proof: If a person suffers a disadvantage following a report, the company must prove that this is based on other reasons. Practically, this leads to a clear recommendation: Personal measures against persons who have reported incidents must be documented meticulously and should be legally reviewed beforehand.
See also: HinSchG · Whistleblower system
Whistleblower system
Deadlines in the reporting process
Under the HinSchG, the receipt of a notification must be confirmed within seven days; the response regarding planned or taken follow-up measures must be provided no later than three months after the receipt of the confirmation.
Both deadlines apply regardless of whether the notice proves to be justified, and its violation is punishable by a fine. The notification must not jeopardize ongoing investigations – it is therefore permissible and customary to provide information about the status of the proceedings without details regarding the content and the persons involved. The monitoring of the deadlines is necessarily ensured system-wide, not in a recurring reminder in the calendar.
See also: HinSchG · Case handling
Supply chain & ESG
Due diligence obligations in the supply chain and sustainability reporting – risk analysis, measures, reporting standards and integration into existing risk management.
Supply chain & ESG
Duty of care in the supply chain
The duty of due diligence requires identifying, avoiding, and minimizing human rights and environmental risks in one’s own business activities and with suppliers. It is designed as a duty of effort—an appropriate, documented approach is required.
Appropriateness is measured by four criteria: the nature and scope of the business activity, influence over the perpetrator, severity and reversibility of the violation, and the nature of the contribution to the violation. These criteria are the benchmark against which the audit case is measured – and the reason why a small supplier company owes other measures than a conglomerate with direct links from high-risk countries.
Supply chain & ESG
Risk analysis according to LkSG
The LkSG risk analysis identifies annually and on an occasion-based basis the human rights and environmental risks in its own business area and with its immediate suppliers.
Two-stage approach
- Abstract risk assessment: Assessment of the supplier portfolio based on country indices, industry risks, and commodity risks – this is done based on data across the entire portfolio.
- Concrete risk assessment: Deepening of relationships with prioritized suppliers through self-declarations, audits, on-site visits, and complaints data.
- Prioritization: Weighting based on severity, reversibility, probability, contribution to causation, and influence.
- Derivation: Translation into prevention measures and, where appropriate, remedial measures with deadlines.
The analysis should be repeated based on the specific circumstances when the risk profile changes – for example, in the case of new procurement markets, new products, or substantial knowledge of violations by indirect suppliers.
See also: Supplier evaluation · Preventive measures
Supply chain & ESG
Preventive measures
Preventive measures should not allow recognized risks to lead to violations at all. They should be implemented within the company’s own area of responsibility and with regard to immediate suppliers, and should be reviewed at least annually for effectiveness.
- Anchoring expectations in purchasing conditions and the supplier code of conduct
- Taking sustainability criteria into account when selecting and awarding contracts
- Training in purchasing, quality assurance and the relevant departments
- Contractual guarantees with a transmission obligation to the chain
- Risk-based control mechanisms such as audits and spot checks
See also: Supplier audit · Remedial measures
Supply chain & ESG
Remedial measures
If a violation has occurred or is immediately threatened, corrective measures must be taken. The violation must be stopped within the company’s own sphere of influence; a plan with a concrete timeline must be created with suppliers.
The termination of the business relationship is expressly the last resort. The legislator assumes that a withdrawal usually worsens the situation of those affected – therefore, cooperation to improve the situation is initially expected, possibly in conjunction with other customers.
See also: Preventive measures · Complaints procedure
Supply chain & ESG
Basic statement
The Basic Statement is the public declaration of commitment to respect human rights adopted by the management. It is not a guiding text, but a document with a predetermined minimum content.
- Description of the procedure for determining the risks
- Identification of the risks that are of priority for the company
- Setting human rights and environmental expectations for employees and suppliers
- Communication to employees, works council, suppliers and the public
See also: SCDDA · Human rights officer
Supply chain & ESG
Reporting to the Authority
Reporting companies document the fulfillment of their duty of care and submit a report to the competent authority, which is also made publicly available.
The content describes identified risks, measures taken, their effectiveness evaluation and the conclusions drawn from them. Scope, format and rhythm are subject to ongoing European harmonization; the underlying documentation obligation remains unaffected – those who document cleanly can use any reporting format.
Supply chain & ESG
Human rights officer
The Human Rights Officer oversees the risk management regarding the duty of care and reports regularly to the management, at least annually.
The function can be linked to existing roles – compliance, sustainability, or purchasing management – but it must be clearly assigned and equipped with sufficient authority. A conflict of interest must be avoided: Those responsible for purchasing prices should not decide alone whether to replace a supplier due to human rights risks.
See also: Basic statement
Supply chain & ESG
Complaints procedure
The complaint procedure enables those involved along the supply chain to point out risks and violations. Requirements include accessibility – also in terms of language –, confidentiality, protection from discrimination, and a publicly accessible procedure.
In practice, it is often combined technically with the whistleblower system. This is permissible and makes sense, but it does require adjustments: a multilingual interface, low-threshold access without corporate login, and case processing that appropriately handles reports from external affected parties.
See also: Whistleblower system · Remedial measures
Supply chain & ESG
Supplier evaluation
The supplier assessment ranks suppliers according to their risk profile and combines quality, delivery, and sustainability criteria with country- and industry-specific risks.
| Dimension | Criteria | Source |
|---|---|---|
| Country risk | Human rights situation, rule of law, corruption | Indices of international organizations |
| Sectoral risk | Workload intensity, known problem areas | Industry studies, NGO reports |
| Supplier-specific | Size, certifications, audit results, incidents | Self-disclosure, audits, the media |
| Business relationship | Volume, Dependence, Influence | own purchase data |
See also: Risk analysis according to LkSG · Third Party Due Diligence
Supply chain & ESG
Supplier audit
The supplier audit verifies on-site or remotely whether a supplier complies with the agreed standards. It complements self-declarations, which on their own are often not sufficient as evidence.
It becomes effective through three elements: unannounced or short-notice appointments with increased risk, the inclusion of employee discussions instead of purely document review, and binding action plans with post-audit. An audit without follow-up generates documentation but no improvement.
See also: Supplier evaluation · Preventive measures
Supply chain & ESG
Sustainability reporting
Sustainability reporting discloses environmental, social, and governance information in accordance with binding standards. With the CSRD, it becomes part of the management report, verifiable and digitally assessable.
Thus, non-financial data are subject to the same requirements as financial data: defined processes, controls, traceability of origin, and record-keeping. This is the real transformation – not the content of the reports, but the need for a control system for data that previously came from Excel queries and estimates.
See also: CSRD · IDW PS 982
Supply chain & ESG
Double materiality analysis
The double materiality analysis determines which sustainability topics must be reported on. It examines two directions: the company's impact on people and the environment, and the financial impact of sustainability topics on the company.
| Perspective | Key question | Evaluation criteria |
|---|---|---|
| Impact importance (inside-out) | What impact does our actions have? | Severity, extent, irreversibility, probability |
| Financial materiality (outside-in) | What risks and opportunities arise for us? | Probability of entry, financial impact |
A matter is subject to reporting if it is one The two perspectives are essential. The analysis, including stakeholder involvement, threshold values and the justification of the results, must be fully documented – it is the first subject of examination.
Action in practice
- The topics that form the universe are: based on the ESRS topics, supplemented by industry-specific issues along the company's value chain
- Identifying and involving stakeholders: Employees, customers, suppliers, financiers, affected communities
- Evaluate impact: by severity of the issue, scope, irreversibility and – in the case of potential effects – probability
- Evaluate financial significance: Risks and opportunities with probability of occurrence and financial impact, methodically identical to risk management
- Set and justify thresholds – the most frequently complained about step
- Documenting the result: List of topics, evaluation, thresholds, parties involved, decisions
The financial perspective should be fed from the existing risk process, not created in parallel. Otherwise, two assessments of the same matter will arise, which in the event of doubt will contradict each other – a finding that any auditor would immediately recognize.
See also: ESRS · Significance
Supply chain & ESG
ESG risks
ESG risks are risks arising from environmental, social, and governance factors that can have financial implications – carbon pricing, supply chain disruptions caused by extreme weather, reputational damage, and difficulties accessing capital.
They are not a separate risk universe, but a category of causes. Methodically speaking, they belong in the existing risk inventory with the same scales and the same aggregation logic. Their specificity lies in the time horizon: While operational risks manifest themselves during the planning period, climate risks often only become effective over five to fifteen years – which requires a separate consideration of time horizons.
See also: Sustainability risks in the RMS · Climate risks
Supply chain & ESG
Climate risks
Climate risks are distinguished from physical and transient risks. Physical risks arise from extreme weather events and long-term climate changes, while transient risks arise from the transition to a climate-neutral economy.
| Type | Examples | Time horizon |
|---|---|---|
| Physically acute | Floods, Storm, Heatwave | short-term, already occurred |
| Physically chronic | Water scarcity, temperature rise, sea level rise | medium to long-term |
| Transient – Politics | CO₂ price, bans, reporting obligations | short- to medium-term |
| Transient – Technology | Substitution of products and processes | in the medium term |
| Transient – The market | changed customer behavior, financing costs | short- to medium-term |
| Transient – Reputation | Public criticism, loss of customers | short-term |
Both types of scenarios are to be analyzed over several time horizons – the ESRS explicitly require scenario analyses for this purpose.
See also: Scenario analysis · TCFD
Supply chain & ESG
Scope-1-, -2- and -3 emissions
The Greenhouse Gas Protocol divides greenhouse gas emissions into three categories: direct emissions from own sources, indirect emissions from consumed energy, and all other emissions from the value chain.
| Scope | Includes | Data available |
|---|---|---|
| Scope 1 | Combustion in own plants, fleet, process emissions | Okay, based on my own consumption data |
| Scope 2 | Connected electricity, district heating, steam | Okay, from the billing records |
| Scope 3 | Purchasing, logistics, business travel, use and disposal of sold products | difficult, mostly secondary data |
Scope 3 is by far the largest component in most industries – often accounting for over eighty percent of total emissions – and at the same time the most difficult component in terms of data. The usual approach involves averaging factors in the first step and gradually replacing primary data from the main suppliers with primary data.
Action regarding Scope 3
- The fifteen Scope-3 categories are evaluated for relevance – usually three to five are essential
- Estimate average factors for the first year based on purchasing volume and quantities
- Identify the largest emission sources and request primary data from suppliers there
- Document data quality by category – primary data, secondary data, or estimation
- Plan gradual improvement instead of immediate full implementation
The reporting standard does not require a perfect dataset, but it does require transparency regarding methodology and uncertainty. An open-ended estimate with a plausible derivation is more reliable than a seemingly accurate figure without any source reference.
See also: Carbon dioxide accounting · ESRS
Supply chain & ESG
Carbon dioxide accounting
Carbon accounting systematically captures a company's greenhouse gas emissions, usually according to the Greenhouse Gas Protocol. It is the basis for reduction targets, transformation plans, and reporting under the ESRS.
The balance sheets first need to be clarified: Which companies are included, based on ownership or control? Without this determination, comparisons over the years are worthless. Equally important is a fixed base year with defined rules for recalculations in case of acquisitions and disposals – otherwise emissions will decrease numerically without any change having occurred.
See also: Scope emissions · Greenwashing
Supply chain & ESG
TCFD
The recommendations of the Task Force on Climate-related Financial Disclosures structure reporting on climate risks along four pillars: governance, strategy, risk management, and metrics and targets.
They have largely been incorporated into the ESRS and international standards and have shaped their structure to this day. For companies that have already reported to TCFD, the transition to the ESRS is therefore more of an extension than a new start – especially the risk management pillar can largely be adopted.
See also: Climate risks · ESRS
Supply chain & ESG
Greenwashing
Greenwashing refers to the representation of products or companies as being more sustainable than they actually are. It is a risk of compliance and liability, not just a communication issue.
Incorrect environmental statements are vulnerable to competition law; legal action for defamation and injunctions are common in practice. In the case of information subject to reporting requirements, there are additional regulatory consequences. The most effective prevention is a disclosure process for sustainability statements with documented data basis – the same logic that has long been taken for granted in financial communications.
See also: Sustainability reporting · Carbon dioxide accounting
Supply chain & ESG
Sustainability risks in the risk management system
Sustainability risks are methodically integrated into the existing risk management system: the same evaluation logic, the same scales, the same aggregation.
A separate ESG risk register leads to contradictory statements to the supervisory board and auditors and prevents sustainability risks from becoming visible in the overall risk profile. Practically speaking, integration means that ESG is added as a causal category, the assessment is carried out within the same scope, and the time horizons are expanded to include medium- and long-term considerations.
See also: ESG risks · Risk categories
Supply chain & ESG
ILO Core Labour Standards
The core labor standards of the International Labour Organization include freedom of association and the right to collective bargaining, the prohibition of forced and child labor, the prohibition of discrimination, and occupational safety and health.
They form the substantive standard for the protected legal positions in the LkSG and in the European regulations. For practice, this means that the Supplier Code, Self-Declaration and Audit Catalogue should be based on these standards, so that the evidence is compatible with the legal requirements.
See also: Duty of care · Supplier audit
Supply chain & ESG
Conflict minerals
The EU Conflict Minerals Regulation obliges importers of tin, tantalum, tungsten and gold to exercise due diligence in the supply chain to avoid funding armed conflicts.
Management systems, risk identification along the chain up to smelting, independent third-party audits, and the annual disclosure of results are required. Companies that do not import themselves are also indirectly affected: they are asked by customers for information on the origin of their products and need to provide details of their own suppliers.
See also: Duty of care
IT, cyber and information security risks
Management systems, regulatory requirements and operational procedures for information security, emergency preparedness and incident management.
IT & Information Security
ISMS
An information security management system is the structured framework for protecting the confidentiality, integrity, and availability of information. It includes security policy, roles, risk analysis, measures, and continuous improvement.
Methodically speaking, it corresponds to risk management – which is why ISMS and RMS ideally use the same evaluation scale. In practice, they often operate separately: IT assesses in protection-need categories, while risk management uses euros. The result is that an IT risk classified as „high" does not appear in the overall risk position. The connection between the two scales is therefore one of the most effective integration steps.
See also: ISO 27001 · Protection needs assessment
IT & Information Security
ISO 27001
ISO/IEC 27001 is the internationally leading, certified standard for information security management systems. The 2022 edition divides the measures in Annex A into four thematic areas: organizational, personnel, physical, and technological.
Certification is increasingly becoming a requirement for supplier approval in the B2B business, especially in the cloud and IT service sectors as well as in the automotive and healthcare sectors. The effort involved is less in the technology itself than in documentation: scope of application, risk management plan, declaration of applicability, and proof of a continuous improvement cycle.
Typical project progression
- Define the scope of application – which locations, processes, and systems are included?
- Adopting a safety guideline and assigning roles
- Valuing and cataloguing values and systems, identifying protection needs
- Conduct risk analysis and create a risk management plan
- Review, select, and create the declaration of applicability for the measures in Annex A
- Implementation, training, internal audit and management evaluation
- Certification audit in two stages, followed by annual monitoring audits
It takes nine to eighteen months to obtain the certificate, depending on the level of maturity. The largest individual item is rarely the technology itself, but rather the documentation of existing processes – much of it is already safely operating, just not being documented.
See also: ISMS · BSI IT Basic Protection
IT & Information Security
BSI IT Basic Protection
The IT Basic Protection of the BSI provides a methodological approach with extensive components for typical systems and processes. It covers management systems, procedures, risk analysis, and business continuity through the BSI standards 200-1 to 200-4.
Compared to ISO 27001, it is much more specific: Instead of demanding „appropriate measures," it lists them in a step-by-step manner. This significantly reduces the design effort, but increases the documentation requirements. In the public sector and among its contractors, it is the de facto standard; certification based on ISO 27001 is possible.
See also: ISO 27001 · Business Continuity Management
IT & Information Security
Protection needs assessment
The protection needs assessment assigns applications, systems, and data a protection need in the categories of confidentiality, integrity, and availability – usually at the normal, high, and very high levels.
It controls the depth of the subsequent risk analysis and the selection of measures and prevents that equally strong investments are made everywhere. Two inheritance rules are important: the protection needs of an application are transferred to the systems on which it runs (maximum principle), and the accumulation of many systems with normal needs can, in aggregate, constitute a higher need (cumulative effect).
See also: ISMS · Business Impact Analysis
IT & Information Security
Business Impact Analysis (BIA)
The Business Impact Analysis determines which business processes are time-critical and which damage a failure causes per unit of time. The result is recovery times and priorities.
Action
- Gathering business processes and naming responsible parties
- Determine the course of damage over time: What does a failure cost after 4 hours, 1 day, 1 week?
- Define a maximum tolerable downtime per process
- Determining dependencies: IT systems, locations, personnel, suppliers
- derive RTO and RPO from this for the supporting systems
The most common mistake is to let the IT department perform the BIA. The department is responsible for determining how long a process can be delayed – the IT department then derives the technical requirements from this.
See also: Business Continuity Management · RTO and RPO
IT & Information Security
Business Continuity Management (BCM)
Business Continuity Management ensures the maintenance of critical business processes in the event of serious disruptions. It includes business impact analysis, emergency strategies, emergency plans, exercises, and ongoing updates.
Training formats
| Format | Effort | Acquisition of knowledge |
|---|---|---|
| Plan discussion | low | Timeliness of documents, understanding of roles |
| Tabletop exercise | medium | Decision-making paths, interfaces, communication |
| Technical re-entry test | high | Does the recovery actually work? |
| Full exercise with failure simulation | very high | Realistic testing including time behavior |
An annual tabletop exercise with the crisis management team and a technical re-testing of the most critical systems are the realistic minimum. The crucial aspect is the follow-up: Without documented lessons learned and the measures derived from them, the exercise remains ineffective.
See also: Business Impact Analysis · Emergency management
IT & Information Security
Emergency management
Emergency management regulates alarm notification, crisis management, communication, and resumption in the event of acute disruptions. It defines roles and decision-making authorities for situations where regular procedures do not work.
Typical weaknesses are outdated contact lists, plans that exist exclusively in the outdated systems, and unclear decision-making authorities – for example, the question of who is allowed to decide on the shutdown of production at night. A crisis management team also needs a defined group of representatives: emergencies do not follow holiday plans.
See also: BCM · IT emergency handbook
IT & Information Security
RTO and RPO
The Recovery Time Objective specifies the time within which a system must be available after a failure. The Recovery Point Objective describes the maximum tolerable data loss, measured as the period since the last backup.
| RTO / RPO | Technical implementation | Cost level |
|---|---|---|
| Minutes / close to zero | synchronous mirroring, active secondary location | very high |
| Hours / 1 hour | asynchronous replication, standby systems | high |
| 1 day / 1 day | daily backup, recovery on replacement hardware | medium |
| Days / 1 day | Security of bands, re-stocking in case of need | low |
Both values are determined by the department in the Business Impact Analysis – they are a business-oriented decision, not a technical one.
See also: Business Impact Analysis
IT & Information Security
IT emergency handbook
The IT emergency handbook documents systems, dependencies, resumption sequences, contact points, and immediate actions.
It must be available offline and at an alternative location – a manual that resides only on the encrypted network drive is worthless in the event of a ransomware attack. Printed copies at designated locations and a copy with an external service provider have proven to be effective, supplemented by an annual update check as part of the emergency drill.
See also: Emergency management · Cyber risk
IT & Information Security
NIS2
The NIS-2 Directive expands European cybersecurity requirements to significantly more sectors and companies. Risk management measures are required for network and information security, reporting obligations in the event of significant incidents, requirements for the supply chain, as well as explicit responsibility and training obligations for management bodies.
The areas of action required
- Risk analysis and concepts for the security of information systems
- Handling security incidents
- Maintaining operations, backup management, and crisis management
- Security of the supply chain, including relationships with service providers
- Security in the acquisition, development and maintenance of systems
- Evaluation of the effectiveness of the measures
- Cyber hygiene and training
- Cryptography, access control, asset management, multi-factor authentication
What is new and practically significant is the personal responsibility of the management bodies: they must approve the measures, monitor their implementation, and be self-trained.
First steps towards implementation
- Check for concern: Sector, size criteria and role in the supply chain – even companies that are not directly involved are taken into account based on customer requirements.
- Gap analysis: Existing measures against the required areas ideally mirror ISO 27001 or IT basic protection.
- Start the reporting process: Who recognizes a significant incident, who decides on the report, who reports within the deadlines?
- Incorporate the supply chain: Include security requirements in contracts with IT service providers.
- Training management staff and documenting decisions – the approval of the measures must be demonstrated.
Those who already operate an ISMS according to ISO 27001 meet a significant portion of the requirements. The gaps typically lie in reporting processes, supply chain security, and the documented involvement of the management.
See also: Incident Management · Outsourcing management
IT & Information Security
DORA
The Digital Operational Resilience Act creates uniform requirements for digital operational resilience in the European financial sector.
The regulation covers five areas: ICT risk management, handling and reporting of ICT-related incidents, testing digital resilience, including threat-driven penetration tests, management of third-party ICT risks with binding contractual content, and the exchange of information on cyber threats. It is also relevant for service providers in the financial sector outside the industry: their contracts must include the required clauses.
See also: Outsourcing management · MaRisk
IT & Information Security
Cyber risk
Cyber risks include attacks such as ransomware, data leakage and social engineering, as well as outages caused by technical failure. A characteristic feature is the combination of a high probability of occurrence and a potentially life-threatening level of damage.
Damage components
- Operational interruption – usually the largest expense
- Recovery costs for systems and data
- Forensics, legal advice, crisis communication
- Contractual penalties and damages to customers
- Fines for violations of data protection or reporting obligations
- Reputation damage and customer churn
In risk aggregation, cyber risks regularly rank among the key drivers of the overall risk position – and they are one of the few cases in which an insurer changes the valuation materially.
See also: Incident Response · BCM
IT & Information Security
Incident Management
Incident management is the structured handling of incidents: recording, classifying, prioritizing, processing, resolving, and evaluating them.
Beyond fault elimination, it provides the empirical data base for risk management. Incidents that occur are the most reliable source for calibrating entry probabilities and damage levels – provided that they are fully recorded and evaluated against their actual costs. Exactly this feedback is lacking in most companies.
See also: Incident Response · Risk assessment
IT & Information Security
Incident Response
Incident response refers to the planned response to security incidents in the phases of preparation, detection, containment, elimination, recovery, and follow-up.
Predefined roles, secure communication channels outside the potentially compromised environment, and compliance with legal reporting deadlines are essential – according to the GDPR, usually 72 hours to the supervisory authority, according to NIS2 with an initial report within 24 hours for affected facilities. Anyone who only investigates these deadlines in an emergency loses them.
See also: NIS2 · Emergency management
IT & Information Security
Vulnerability management
The vulnerability management systematically detects, assesses, and remediates technical security vulnerabilities: asset inventory, regular scans, assessment for exploitability and criticality, prioritized patching, and tracking of open points.
Without a complete asset inventory, any vulnerability management remains incomplete – uninventoried systems are not scanned and patched. The second critical point is prioritization: The number of known vulnerabilities exceeds any patch capacity, which is why it must be weighted based on actual exploitability within the organization’s environment, not solely on severity.
See also: ISMS · Cyber risk
IT & Information Security
Outsourcing and third-party management
Outsourcing management controls risks arising from the involvement of external service providers: risk assessment before contracting, contractual safeguarding of information, command and control rights, and audit rights, ongoing monitoring, and exit scenarios.
| Phase | Checkpoints |
|---|---|
| Before awarding | Criticality, risk analysis, creditworthiness, certificates, subcontractors |
| Contract | Service level, information and inspection rights, reporting obligations in the event of incidents, data protection, termination rights |
| Operation | Performance monitoring, incident reports, annual reassessment, audit reports from the service provider |
| Exit | Exit strategy, data return, transitional support, alternative providers |
It is regulated by MaRisk, DORA, and NIS2 – and it is the area where cyber risks most commonly occur: not within the company’s own network, but with the service provider.
IT & Information Security
TISAX
TISAX is the testing and exchange mechanism for information security in the automotive industry, based on the VDA-ISA catalog.
Ratings are shared via a central platform between manufacturers and suppliers, replacing repeated individual audits. Evaluation takes place in stages, depending on the protection needs of the processed information – from self-assessment to on-site inspection with extended requirements for prototype protection. A valid label is regularly a prerequisite for awarding contracts to suppliers.
Governance & Liability
Organization, oversight, and responsibility – how risk management and compliance are embedded in corporate governance and where personal liability arises.
Governance
Governance
Governance refers to the framework for the organization’s management and supervision: responsibilities, decision-making processes, control mechanisms, and reporting lines between the management, the supervisory body, and the shareholders.
It creates the structure within which risk management and compliance can actually be effective. Practically speaking, it is concretized in business regulations, approval reservations, representation arrangements, reporting obligations, and the composition of committees. Missing governance rarely manifests itself as an abstract problem, but as a concrete question: Who actually had the authority to make this decision?
See also: GRC · Corporate Governance Code
Governance
GRC
GRC stands for Governance, Risk and Compliance and describes the integrated approach to managing these three disciplines with common methodology, a unified data base and coordinated processes.
The goal is to eliminate duplication of work. In complex structures, risk management, internal audit, compliance, data protection, information security, and internal audit employ the same processes multiple times, with different scales and in separate files. For the departments, this means five inquiries per year regarding the same issues – and for the management, five reports that contradict each other.
Where integration actually saves effort
- A process map Instead of four – usable for IKS, revision, data protection, and emergency planning
- One control, used repeatedly: Once tested, used for IKS reports, net risk assessment, audits and certification
- A pool of measures Instead of separate lists for each function
- One round of surveys instead of four surveys per year in the specialist departments
- A reporting basis for management and supervisory bodies
Resistance to integration rarely comes from the technical departments – they benefit the most – but from the second-line functions that have to abandon their own methodology and reporting procedures. The implementation is therefore predominantly an organizational project, not a software project.
See also: Integrated GRC · Three Lines Model
Governance
Integrated GRC
Integrated GRC brings together risks, controls, measures, audit findings, and regulatory requirements in a common data model.
| Once raised | Used for |
|---|---|
| Process land map | IKS, Revision, Data Protection Processing Register, BIA |
| Inspection description and test result | IKS report, net risk assessment, audit, certification |
| Risk assessment | Risk report, audit planning, protection needs, situation report |
| Action with deadline | Risk management, ICS remediation, audit follow-up, compliance program |
| Supplier master data and evaluation | Risk analysis for LkSG, sanctions review, outsourcing management, ESG report |
The gain is not primarily the savings in software, but the freedom from contradiction: There is one version of the truth, and it is current.
See also: Single Source of Truth · GRC
Governance
Examination Committee
The Audit Committee of the Supervisory Board deals with accounting, the effectiveness of the internal control system, the risk management system and internal auditing, the audit of financial statements, and sustainability reporting.
At least one member must possess specific expertise in accounting or audit; the expansion to include sustainability reporting adds corresponding expertise. The committee is also the intended audience to which internal audit and the reporting unit immediately report in critical cases – it thus serves as the institutional counterpart to management override.
See also: Board of Supervisors and risk monitoring · FISG
Governance
Risk Committee
A risk committee focuses primarily on risk strategy, risk-bearing capacity, and key individual risks.
In credit institutions, it is provided for by regulatory requirements. Outside the financial sector, the task is usually carried out by the audit committee or the overall supervisory board. A separate committee is worthwhile where the risk profile is complex – for example, in cases of high internationalization, project business with long lead times, or a strong dependence on raw materials.
See also: Examination Committee
Governance
Board of Supervisors and risk monitoring
The supervisory board monitors the management and seeks to verify the effectiveness of the risk management system. This is more than just accepting reports.
Questions that an oversight body should ask
- What is the aggregate total risk position, and how does it compare to risk-bearing capacity?
- What assumptions and correlations underlie the aggregation model?
- Which risks have emerged or disappeared since the last meeting – and why?
- What measures are overdue, and what is the reason?
- Does the internal risk situation match the presentation in the status report?
- What do auditors and internal auditors say about the effectiveness of the system?
See also: Risk reporting · Internal audit
Governance
Annual financial statement audit
The annual financial statements audit assesses whether the financial statements and the management report comply with legal regulations. The auditor gains an understanding of the internal control system related to the financial statements.
It is important to distinguish between the following: The final exam is not an assessment of the effectiveness of the IKS. The examiner only assesses controls to the extent that he or she intends to rely on them in order to reduce the scope of his or her own examination procedures. A statement regarding the effectiveness of the entire control system is only provided in a separate assignment according to IDW PS 982.
See also: Section 317(4) of the German Commercial Code · IDW PS 982
Governance
Forecast report
The forecast report, as part of the management report, presents the expected development of the company with its key assumptions.
It is closely related to the risk report: the risks accurately describe the deviations from the expectations presented here. Inconsistencies between the two parts – an optimistic forecast while the risk situation is at the same time serious, or vice versa – are among the most common findings of audits and are also a liability risk for investors.
See also: Situation report · Bandwidth planning
Governance
Managing director liability
Managing directors and executives are liable to the company for negligence in performing their duties. In the event of a dispute, they must demonstrate that they made a decision based on reasonable information and that they took the necessary organizational measures.
Typical liability areas
| Field | Trigger | Prevention |
|---|---|---|
| Insolvency evasion | late submission of the application | ongoing liquidity and over-indebtedness review |
| Lack of early crisis detection | § 1 StaRUG, § 91 AktG | documented early detection system |
| Organizational shortcomings | Section 130 of the OWiG | CMS with risk analysis and verification |
| Taxes and social contributions | Non-deduction | Processes and controls in payment transactions |
| Inadequate information | Decision without foundation | documented risk assessment in templates |
A documented risk management and compliance system is therefore less bureaucratic than evidence. The burden of proof lies with the member of the organization – not with the company.
Practical self-protection
- Decision templates with documented risk assessment and alternatives
- Logged resolutions with voting behavior – record dissenting votes in writing
- Regulate the distribution of responsibilities in writing, without ignoring the duty of oversight for other departments.
- Regular reports to the supervisory body, including on negative developments
- Obtain external expertise for complex legal matters and document the acquisition of such expertise
- Continuously provide liquidity and survival forecasts, not only in times of crisis
The common denominator is detectability: The Business Judgement Rule does not protect the correct decision, but the carefully prepared one. Anyone who cannot demonstrate this preparation loses protection regardless of how reasonable the decision was.
See also: Business Judgment Rule · D&O insurance
Governance
D&O insurance
Directors-and-Officers insurance covers property damage resulting from organ liability. It does not replace risk management.
Three points should be noted: intentional breaches of duty are excluded, statutory self-insurances are provided for directors of a limited liability company, and insurers are increasingly asking for detailed information regarding the maturity of risk management and compliance during the risk assessment process. A demonstrably functioning system thus directly affects the availability and premium of coverage.
See also: Managing director liability
Governance
Compliance responsibility of management
The responsibility for compliance lies with the management as a whole and cannot be delegated. Tasks can be transferred – the duty to select, equip, instruct, and supervise the employees remains with the management.
In the division of responsibilities, the duty of supervision for all members of the organ remains in place. It becomes an obligation to act as soon as there are indications of wrongdoing. It is precisely this residual obligation that the fine liability under § 130 of the German Motor Vehicle Act (OWiG) is based on – „that was not my responsibility"; exoneration does not apply.
See also: Organizational shortcomings · Compliance Officer
Governance
Significance
Significance determines which matters are subject to reporting obligations or are relevant for audits. In accounting, it is derived from quantitative thresholds and qualitative criteria; in sustainability reporting, it is derived from the double materiality analysis.
For risk management, defining is practically important: it determines which risks are reported to management and supervisory bodies and which remain at the departmental level. The threshold is an assessment decision, but it must be justified, documented, and applied consistently over time.
See also: Double materiality analysis · Risk reporting
Systems & Data
Technical terms of system-based implementation – Understandability, permissions, workflows, and data quality as prerequisites for reliable risk and compliance processes.
Systems & Data
audit compliance
Audit security means that data and documents are stored in an unchanged, complete, traceable manner and available throughout the retention period. In Germany, the GoBD serves as the standard.
For risk and compliance data, it is a prerequisite for assessments and audit evidence to be valid as evidence later on. Specifically, the following requirements are required: immutability after release, complete logging of any changes, protection against loss, recoverability within a reasonable time, and documented procedural documentation that describes how the system meets these requirements.
Checkpoints in the system selection
- Are data records that are released technically protected against modification, or only organizationally?
- Does the system log every change with timestamps, users, and before-and-after values?
- Can the status be reconstructed to any date in the past?
- Are deletions excluded or at least logged and subject to a justification requirement?
- Is there any documentation of the process that describes these characteristics?
- Are the data still readable and exportable even after a provider change?
The last point is often overlooked: retention periods often exceed the contract term with the system provider. An export format that remains readable without the software therefore belongs in the contract.
See also: Audit Trail · Storage periods
Systems & Data
Audit Trail
The audit trail records in a complete manner who created, modified, or deleted which data when. It makes it possible to trace evaluation changes to risks, approvals, and audit evidence.
It is one of the key testing criteria that distinguishes a GRC software from a spreadsheet. The crucial question in the review meeting is regularly: Who changed this risk assessment from „high" to „medium" when, and with what reason? In Excel, this question is not answerable.
See also: audit compliance · Risk registers
Systems & Data
Role and rights concept
The role and rights concept regulates which user groups are allowed to view and edit which data. In the GRC context, it is doubly relevant: it technically implements functional separation and protects sensitive content.
| Role | Right | Special feature |
|---|---|---|
| Risk owners | identify and assess their own risks | no access to other areas |
| Central risk management | Read all the risks, maintain methodology, consolidate it | no independent modification of other people's reviews without a record |
| Controller responsible | Controlling documents, filing evidence | no access to other testers' results |
| Internal audit | Right to read everything, own conclusions | no editing rights in professional processes |
| Reporting point | Whistleblower cases | strictly segregated, even from administrators |
| Administration | System configuration | no technical content access, logged exceptions |
See also: Separation of functions · Confidentiality obligation
Systems & Data
Client ability
Client capability refers to the ability to manage multiple companies, locations, or divisions separately within a system while simultaneously evaluating them in a consolidated manner.
In corporate structures, it is a prerequisite for local responsibility and a holistic view across the entire group to coexist without duplicate data management. Three points need to be clarified: which master data are uniform across the entire group, which are local? What evaluation scales apply to everyone? And who may evaluate across borders – a question that is also relevant from a data protection perspective for foreign-based companies.
See also: Role and rights concept · Data quality
Systems & Data
Workflow management
Workflow management automates recurring processes in the risk and compliance process: collection rounds, approvals, duplicate submissions, escalations, and reminders.
It replaces manual follow-up via email and at the same time generates the documentation required for meeting deadlines and auditing. The practical effect is significant: The central function spends a large part of its time following up on open feedback – exactly this work is taken care of by the workflow, without anyone having to act as a reminder.
See also: Release workflow · Action tracking
Systems & Data
Risk dashboard
A risk dashboard consolidates the risk situation in real time: overall risk position, top risks, changes compared to the previous period, status of measures, and exceedance of limit values.
The key is address-oriented reporting. The management needs aggregate data, trends, and outliers; the functional department needs a detailed view of its own risks; the supervisory board needs to view developments over several periods with methodological guidance. A dashboard that shows the same information for everyone is not right for anyone – and leads to confusion between completeness and meaningfulness.
See also: Risk reporting
Systems & Data
Action tracking
The measures tracking system monitors the implementation status, deadlines, and effectiveness of all the measures decided upon by a single point of reference regarding risk management, internal control, audit, and compliance.
It prevents the typical situation where the same determination is documented differently in several systems and no single instance knows the overall status. It is made meaningful by three key metrics: the proportion of overdue actions, the average duration of delays, and the proportion of actions with a verified effectiveness – not just with the status „completed".
See also: Action management · Workflow management
Systems & Data
Release workflow
The release workflow generates multi-stage approvals system-wide – for example, the confirmation of risk assessments by the risk owner and the subsequent approval by central risk management.
He enforces the four-eyes principle and automatically documents approvals with timestamps and person information. It is important to have a designated representative system: without it, the process is suspended during vacations or illness, and the exact same workarounds are created via email that should prevent the workflow from functioning properly.
See also: Separation of functions · Audit Trail
Systems & Data
Versioning and document management
Document management ensures that it is always clear which version of a document was valid, who released it and who took it into account.
For guidelines, process descriptions, and evidence, it forms the basis of any credible compliance documentation. The practical benchmark: Is it possible to determine, at any date in the past, which version of the travel expense policy applied at that time and which employees had approved it? If not, the evidence in the proceedings is vulnerable to challenge.
See also: Guidelines management · audit compliance
Systems & Data
Storage periods
Retention periods determine the length of time documents must be kept – in commercial and tax law, they are governed by staggered deadlines, with specific areas subject to derogations.
In the context of the data protection law’s obligation to delete data, a deletion plan is needed that clearly defines the start and end dates of the deletion process and the exceptions for each type of document. Particular attention should be paid to cases where a deletion obligation is hindered by an ongoing process – in such cases, a legal hold is required that suspends the automatic deletion process.
See also: audit compliance · Document management
Systems & Data
Interfaces in the GRC context
Interfaces connect GRC systems with ERP, HR, purchasing, ticketing systems, and data warehouses. They enable the automated capture of master data, key performance indicators, and early warning indicators.
The benefit lies less in time savings than in timeliness: manually maintained risk data is already outdated at the time of its collection, while automatically imported indicators are not. Typical initial interfaces are supplier master data from ERP, KPIs from controlling, and incidents from the IT ticket system.
See also: Data quality · Key Risk Indicator
Systems & Data
Data quality in risk management
The quality of risk data determines the reliability of all analyses. Criteria include completeness, timeliness, consistency of the assessment criteria, and the traceability of the source.
Weaknesses typically manifest themselves in inconsistent scales between areas: What sales classifies as „high" is a medium risk in production. This is a methodology problem, not a software problem – the solution lies in clear scale definitions with Euro values and plausibility through the second line.
See also: Risk assessment · Risk handbook
Systems & Data
Single Source of Truth
A single source of truth is the one leading data base on which all analyses are based.
In the GRC environment, it prevents risk registers, IKS documentation, and audit findings from becoming confused, and management and the supervisory board from receiving contradictory figures. Implementation rarely fails due to technology, but rather due to clarifying the question of which system is the leading one for which data set—and who is allowed to make changes to it.
See also: Integrated GRC · Data quality
Systems & Data
Automated risk reporting
With automated risk reporting, defined events or threshold exceedances automatically trigger a notification in the system – for example, when an early warning indicator is exceeded or a damage event occurs.
It supplements the regular collection with the context-specific component explicitly expected by the IDW PS 340 n.F. The triggers, recipients, escalation level, and response time must be defined. It is important to calibrate the thresholds: too many reports lead to habituation, too few to create a false sense of security.
See also: Early warning indicator · Risk early detection system