A list of assessed individual risks is usually not enough. Only aggregation shows whether several risks together can threaten the company's continued existence. Can you show in the audit meeting, in a traceable way, how this overall view was produced? CRISAM® aggregates using integrated Monte Carlo simulations and delivers metrics such as value at risk and expected shortfall.
As of: 23 September 2026
| Risk | Area | Gross | Net |
|---|---|---|---|
| Loss of a key customer | Sales | ||
| Price spike in energy and raw materials | Purchasing | ||
| Extended production outage | Production | ||
| Cyber incident with production shutdown | IT |
IDW PS 340 is the auditing standard issued by the Institute of Public Auditors in Germany (Institut der Wirtschaftsprüfer, IDW) for the audit of the early risk detection system under Section 317 (4) of the German Commercial Code (HGB). It is addressed to the statutory auditor and describes how the auditor measures the effectiveness of such a system. The authoritative version is the new IDW PS 340 (revised), dated 10 January 2022, published in IDW Life 3/2022 and aligned with the new German generally accepted standards for financial statement audits.
The full text of the standard is available from the Institut der Wirtschaftsprüfer for a fee. This page therefore does not reproduce any paragraph numbers. It describes what early risk detection has to deliver in practice and how this can be mapped in CRISAM®.
Identification and assessment are usually straightforward to implement. Aggregation is where it is decided whether the system is reliable.
Which risks can affect the company at all, across all areas and not just where something last went wrong.
How big is a risk? Assessment is qualitative where that is sufficient and quantitative where amounts matter.
Combining the individual risks into an overall view. Only here does it become visible whether several risks together can threaten the company's continued existence.
The information reaches company management in time and in a form that enables a decision.
Ongoing checks verify whether the system works and whether the assessments still reflect the current situation.
Spreadsheet solutions reach their limits at aggregation. Individual risks can be added up, but the result is rarely accurate: risks do not occur at the same time, they depend on each other, and their distributions are rarely symmetrical.
The standard is addressed to the statutory auditor. But the party affected is the company whose system is audited.
A single risk rarely threatens a company. The combination is what becomes dangerous: several medium risks that occur in the same year, or risks that reinforce each other. An aggregation that takes distributions and dependencies into account makes exactly that visible. Simple summation cannot.
If an economic downturn simultaneously lowers sales, worsens payment behavior and puts a key customer at risk, these are not three independent risks. Calculating them independently underestimates the overall risk.
What is asked for is not just the result, but also the methodology and its traceability: which assessments were included, which period they come from, who approved them and how the overall view was derived from them.
Eight requirements along the five stages. In the audit meeting, each of them must not only exist but also be traceable.
| Requirement | Stage | What matters | How you map it in CRISAM® |
|---|---|---|---|
| Capture risks completely | Identification | A procedure that systematically collects risks across all areas, not just where something last occurred | Risks can be identified and assessed in a structured way using intuitive wizards. Company structures are modeled flexibly from a risk perspective. |
| Assess appropriately | Assessment | The assessment method must match the significance of the risk. Where amounts matter, simply assigning classes is not enough | Depending on maturity level, qualitative and quantitative assessment methods are available, including across multiple periods. |
| Show the effect of measures | Assessment | It must be clear how high a risk is without and with the existing measures | Risks are assessed in a gross and a net view to show the effectiveness of measures transparently. Risk mitigation measures are planned, implemented and monitored with workflow support. |
| Aggregate risks | Aggregation | Individual risks must be combined into an overall view so that it becomes clear whether several risks together can threaten the company's continued existence | Integrated Monte Carlo simulations aggregate risks using modern methodology. Metrics such as value at risk or expected shortfall support the risk-bearing capacity analysis. |
| Account for dependencies | Aggregation | Risks that occur together or reinforce each other must not be calculated as independent | Correlations between risks can be taken into account in the aggregation. |
| Keep assessments current | Monitoring | Assessments must be reviewed and updated on schedule, with clear responsibility | Risk owners update risk assessments on schedule with workflow support, automated reminders and individually configurable approval processes. |
| Report to management | Communication | The information must reach company management in time and in a form that supports decisions | Interactive dashboards show risks, workflows, measures and aggregation results. Risk reports and risk-bearing capacity analyses are aimed at management and decision makers. |
| Document traceably | Monitoring | The statutory auditor must be able to trace the methodology and the path to the result, not just see the result | The versioning function stores the data in an audit-proof way. An individual authorization concept controls which risks and measures a user may view, assess and create. |
From the individual risk to the statement of whether the company can bear its overall risk position.
The wizard guides you through capturing the risk. Whether the assessment is qualitative or quantitative depends on how the risk takes effect, not on what is quicker to complete.
Where amounts matter, simply assigning classes is not enough. Quantitative assessment is the prerequisite for reliable aggregation.
Define correlations earlyDependencies between risks are recorded on the risk and take effect later in the aggregation.
Responsibility and due dateEvery risk has an owner and an update date. The statutory auditor checks both.
The comparison shows how high the risk would be without measures and how high it is with them. The difference demonstrates the effect of the measures.
| Risk | Method | Gross | Measures | Net | Updated |
|---|---|---|---|---|---|
| Loss of a key customer | quantitative | 2 effective | 04.09.2026 | ||
| Price spike in energy and raw materials | quantitative | 3 effective | 04.09.2026 | ||
| Extended production outage | quantitative | 4 effective | 21.08.2026 | ||
| Cyber incident with production shutdown | quantitative | 6 effective | 21.08.2026 | ||
| Loss of skilled staff | qualitative | 2 effective | overdue | ||
| Delay in a major project | qualitative | 1 effective | 12.06.2026 |
The Monte Carlo simulation calculates and aggregates thousands of possible scenarios based on distributions instead of averages, with correlations if desired. The result is a range of possible outcomes instead of a single number.
| Risk | Contribution | Correlated with | Without correlation | With correlation |
|---|---|---|---|---|
| Loss of a key customer | Economic downturn | lower | decisive | |
| Economic downturn | Sales, payment default | lower | decisive | |
| Price spike in energy and raw materials | Economic downturn | comparable | slightly higher | |
| Extended production outage | none defined | comparable | comparable | |
| Payment default on major receivables | Economic downturn | lower | higher |
The overall view is compared with the risk-bearing capacity. This answers the supervisory board's question: can the company bear its risk position?
| Scenario | Assumption | Aggregated risk | Coverage potential | Result |
|---|---|---|---|---|
| Expected case | Mean of the simulation | low | sufficient | |
| Adverse case | Confidence level 95 percent | medium | sufficient | |
| Severely adverse case | Confidence level 99 percent | high | tight | |
| Extreme case with correlation | Economic downturn and customer loss | very high | not sufficient | |
| Extreme case without correlation | the same risks, calculated independently | high | tight |
| Item | Effect | Owner |
|---|---|---|
| Correlations not defined for three risks | Overall risk is probably underestimated | Risk management |
| Coverage potential from the previous year | Risk-bearing capacity statement not up to date | Finance |
Assessments become outdated. The workflow reminds risk owners, documents the approval and shows what is overdue.
At the end comes the report for the executive board, supervisory board and statutory auditor. It shows not only the figures but also how they were arrived at.
| Document | Content | As of | Owner | Status |
|---|---|---|---|---|
| Risk inventory | 87 risks with owners | 04.09.2026 | Risk management | |
| Assessment methodology | qualitative and quantitative, per category | 18.02.2026 | Risk management | |
| Aggregation result | Simulation with correlations | 04.09.2026 | Risk management | |
| Risk-bearing capacity analysis | five scenarios | under revision | Finance | |
| Evidence of updates | Workflows and approvals | ongoing | Risk owners | |
| Report to the supervisory board | Overall position and scenarios | planned 12/2026 | Executive board |
Responsibility for the system, decisions on risk-bearing capacity and measures.
Methodology, inventory, aggregation, report to management.
Assessment and scheduled updating of their own risks.
Oversight, audit of the system and its traceability.
A cyber incident is both an information security risk and a business risk. Integrating the ESG, ICS, audit and compliance modules makes interrelationships visible, breaks down silos and strengthens steering.
The integrated risk management module covers ISO 31000, IDW PS 340 and 981, and ONR 49001.
The financial side of double materiality under the CSRD is assessed using the same methodology and flows into the same aggregation.
Internal audit derives its audit priorities from the same risk model instead of from a list of its own.
CRISAM® can be developed step by step, from simple assessment models to quantitative analyses. No system change is needed for this.
Both deal with risk management, but they are aimed at different audiences. IDW PS 340 is an auditing standard: it defines how the statutory auditor measures an early risk detection system. ISO 31000:2018 is a guideline for the organization itself and explicitly cannot be used for certification purposes. Working to ISO 31000 does not automatically meet the expectations of the audit.
| Criterion | IDW PS 340 (revised) | ISO 31000:2018 |
|---|---|---|
| Type | Auditing standard of the Institut der Wirtschaftsprüfer | International guideline, second edition, February 2018 |
| Addressee | The statutory auditor | The organization itself |
| Subject | The audit of the early risk detection system under Section 317 (4) of the German Commercial Code (HGB) | Principles and guidelines for risk management |
| Binding nature | Authoritative for the audit, and therefore indirectly for the audited company | Voluntary, explicitly cannot be used for certification purposes |
| Focus | The audit of the early risk detection system, from identification to monitoring | Comprehensive approach from identification through analysis, evaluation and treatment to monitoring and communication |
| What you get at the end | An audit opinion on the effectiveness of the system | A framework the organization can measure itself against |
| Mapping in CRISAM® | Assessment, aggregation via Monte Carlo simulation, workflows, audit-proof history | The same stages, aligned with the principles of the guideline |
ISO 31000 gives the organization the framework, IDW PS 340 gives the audit its benchmark. The two do not contradict each other, but they are not congruent either: aggregation, which is decisive for the audit, does not carry the same weight in the guideline. The integrated risk management module covers ISO 31000, IDW PS 340 and 981, and ONR 49001. You can find an overview of all frameworks under Standards and frameworks.
The first step depends on where you stand today.
You start with the import. Existing data can be transferred via a CSV or REST API interface. After that, assessment, measure and responsibility are linked to an object instead of being recorded in a spreadsheet row.
Then aggregation is the next step. The prerequisite is that the material risks have been assessed quantitatively. After that, the Monte Carlo simulation calculates thousands of possible scenarios based on distributions, with correlations if desired, instead of adding up individual values.
Then the workflow takes center stage. Scheduled updates run with automated reminders and configurable approval processes instead of an annual mass email.
For this you need the CRISAM® GRC Platform and the CRISAM® IRM Module. In the demo, we discuss your starting point and show what you already have in place.
IDW PS 340 is the auditing standard issued by the Institute of Public Auditors in Germany (Institut der Wirtschaftsprüfer, IDW) for the audit of the early risk detection system under Section 317 (4) of the German Commercial Code (HGB). It is addressed to the statutory auditor and describes how the auditor measures the effectiveness of such a system. The authoritative version is the new IDW PS 340 (revised), dated 10 January 2022, published in IDW Life 3/2022 and aligned with the new German generally accepted standards for financial statement audits.
The new version IDW PS 340 (revised) with the version designation 01.2022 applies. It is titled “Die Prüfung des Risikofrüherkennungssystems” (The Audit of the Early Risk Detection System) and was published in IDW Life 3/2022. The revision was prompted by the new German generally accepted standards for financial statement audits.
Both deal with risk management, but they are aimed at different audiences. IDW PS 340 is an auditing standard: it defines how the statutory auditor measures an early risk detection system. ISO 31000:2018 is a guideline for the organization itself and explicitly cannot be used for certification purposes. Working to ISO 31000 does not automatically meet the expectations of the audit.
Because the result is rarely accurate. Risks do not all occur at the same time, they depend on each other, and their distributions are rarely symmetrical. A sum of individual values reflects none of these three characteristics. It can overstate the overall risk just as easily as underestimate it, depending on the assumption behind the individual values.
Risk aggregation means combining the assessed individual risks into an overall view. Only there does it become visible whether several risks together can threaten the company's continued existence. In CRISAM®, integrated Monte Carlo simulations aggregate risks using modern methodology. Metrics such as value at risk or expected shortfall support the risk-bearing capacity analysis.
Through correlations. If an economic downturn simultaneously lowers sales, worsens payment behavior and puts a key customer at risk, these are not three independent risks. In CRISAM®, correlations between risks can be taken into account in the aggregation so that the overall view reflects the combined effect.
By being updated on schedule, not via an annual mass email. In CRISAM®, risk owners update risk assessments on schedule with workflow support, automated reminders and individually configurable approval processes. The versioning function keeps it traceable which status applied at what time.
What matters is whether identification, assessment, aggregation and reporting are linked in a shared model. CRISAM® models company structures from a risk perspective, assesses qualitatively and quantitatively in a gross and a net view, aggregates via Monte Carlo simulation and documents changes with full version history. The integrated risk management module covers ISO 31000, IDW PS 340 and 981, and ONR 49001. Existing data can be transferred via a CSV or REST API interface.
The information about the standard on this page comes from the following sources. The full text of the standard is subject to a fee, so no paragraph numbers are reproduced.
The information reflects the status of the cited sources as of the review date stated above.
In the demo, we walk through your case: risk inventory, gross and net assessment, aggregation via Monte Carlo simulation, correlations and the report to company management.
You are currently viewing a placeholder content from Facebook. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou need to load content from reCAPTCHA to submit the form. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Hubspot Embedded Content. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from HubSpot. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Hubspot Meetings. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Instagram. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from X. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More Information