What is IBCS®? The reporting standard in 10 minutes

The management meeting opens with the revenue report. Page three: a chart in which green is budget. Page seven, from Sales: a chart in which green is actual. Page eleven, from Production: green means "fine". The head of Sales spends two minutes explaining what his chart shows before anyone can ask why the Service margin has dropped.

Every report speaks its own language

What is IBCS®, and why should a CFO care? The short answer: because in most companies every report speaks its own visual language, and the reader has to learn it afresh each time. Controlling has its colour scheme, Sales has another, the production manager's Excel a third. Scales change from page to page, so a minor unit looks as big as the core business. Budget sits to the left of actual on one page and to the right on the next. Variances appear as a percentage in the table, as a traffic light on the dashboard and as an arrow in the slide deck.

None of this is wrong. All of it together has a cost. Do the arithmetic: a 90-minute management meeting, a report pack of eight pages and six different presentation logics. If each page burns one minute on "which one is which?", that is eight minutes – close to ten per cent of the meeting, every month, spent on decoding rather than deciding. With six people at the table, that is roughly ten person-hours a year, not counting the time Controlling spends preparing the explanations.

The more expensive part is less visible. Someone who does not understand a chart at first glance does not ask – they skip it. The variance in the spare-parts business, which was in the report all along, gets treated as a surprise three months later. And because the presentation leaves room for interpretation, the meeting argues about the presentation: Is the axis truncated? Is that cumulative or monthly? Why is the bar so short when the number is so big?

There has been a standard for this problem for more than ten years. It is free to use, long since adopted in many large groups, and since June 2026 its core is an international standard as well. Yet many finance leaders in Swiss SMEs know it only by hearsay – usually as "the thing with the black and grey bars".

What IBCS® is and where it comes from

IBCS® stands for International Business Communication Standards. It is a set of rules for how reports, presentations and dashboards are structured and drawn so that readers understand them without explanation. The standard says nothing about accounting, cost management or software. It says how a number gets onto the page, how a comparison is shown and how a message is worded.

The concept was initiated by Rolf Hichert, who spent years developing and implementing rules for the design of management reports. Since 2013 the IBCS Association, a not-for-profit body, has owned the standard, developed it further through public consultation and published it free of charge. The licence is Creative Commons BY-SA 4.0: anyone may use, adapt and share the standards, provided the source is credited and adaptations are shared under the same licence. The name IBCS® itself is a registered trademark of the IBCS Institute, which is why it carries the ® symbol and why not everyone may call themselves "IBCS certified". We are not, and we will never claim to be – we work in line with the standard, more on that below.

Version 1.2 of the standards was current for a long time. On 11 June 2026 the IBCS Association released version 2.0, and on the same day ISO published ISO 24896 "Notation for business reporting". Version 2.0 is now split into two parts: the notation part, which is fully aligned with ISO 24896, and the composition part, which holds the rules on message, structure and density. In practice this means the presentation conventions many companies have used for years now have an international standard behind them – one a reporting guideline can refer to.

The seven SUCCESS rules in plain language

IBCS® organises its rules into seven areas whose initials spell SUCCESS. The official titles are short and abstract. Translated into the language of a monthly management report, they read like this:

SAY – message. Every page makes a statement, and the statement is the title. Not "Revenue by business unit" but "Revenue 4% below budget – Plant Engineering short, Service partly compensates". Whoever reads the title knows the news; the chart is the evidence.

UNIFY – notation. The same things always look the same. Actual is solid dark everywhere, budget is outlined everywhere, prior year is grey everywhere. Anyone who has read one report can read them all. This is the area that is now an ISO standard, and the one to start with in practice.

CONDENSE – density. More information per page, not less. A single large chart with four bars wastes space; four small charts with the same scale side by side reveal the pattern. For the management page this means business units, months and variances on one page, not on four.

CHECK – integrity. The picture must not lie. No truncated axes, no different scales for the same measure, no logarithms without a note. If the bar for Service is half the length of the bar for Plant Engineering, then revenue is half as large.

EXPRESS – the right visualisation. The right form for each question. Time series as columns or lines with time running left to right; structures (units, products, countries) as horizontal bars from top to bottom; variances as bars of their own with a sign – never as a percentage in the small print. And no pie charts when the task is comparison.

SIMPLIFY – declutter. Remove everything that carries no information: frames, gridlines, shadows, 3D effects, gradients, redundant legends. What remains is the number, its comparison and its label. An IBCS® report looks austere at first sight. After the third meeting nobody wants to go back.

STRUCTURE – organisation. Content is complete, non-overlapping and ordered the same way throughout: first the group, then the units, then the detail – on every page alike. The page for Service looks like the page for Trading, only with different numbers. One page per unit, the same position for the same measure.

The seven SUCCESS areas in the monthly report
Area	The question behind it	Example from the monthly report
SAY	What is the message?	Title: "Revenue 4% below budget – Plant Engineering short"
UNIFY	Do the same things always look the same?	Actual dark, budget outlined, PY grey – on every page
CONDENSE	Is there enough on the page?	Four units × twelve months on one page
CHECK	Does the picture match the number?	Same scale for all units, no truncated axis
EXPRESS	Does the form fit the question?	Time as columns, structure as bars, variance as signed bars
SIMPLIFY	Does every element carry information?	No gridlines, no shadows, no third colour
STRUCTURE	Is the organisation complete and consistent?	One page per business unit, identical layout

SUCCESS at a glance: seven areas, one test question and one example each.

The notation you recognise at once

The most visible part of IBCS® is its notation, and it takes a few sentences to explain. Scenarios are distinguished by fill, not by colour: actual is solid dark, plan or budget is outlined with a dark border, prior year is filled light grey, forecast is hatched. That makes it clear at a glance which number was measured, which was planned and which is an estimate – with no legend, and printable in black and white.

Variances are not placed as a number next to the value; they are drawn as bars of their own – to the right or upwards when positive, to the left or downwards when negative, with a sign. Good variances are green, bad ones red – the only place where colour carries meaning. Scales are uniform within a page: a bar of CHF 300k is exactly as long in Trading as in Plant Engineering. Time runs horizontally from left to right; structures such as business units or products are stacked vertically. And where several scenarios are compared, a fixed order applies: prior year, actual, budget – left to right, on every page.

Sample report in IBCS® notation: prior year grey, actual dark, budget outlined; variance to budget as signed bars on the right.

Once you have read a report this way, you see the difference immediately. In the example above nobody needs to compare numbers to know that Plant Engineering is the problem: the red bar on the right says so. That is the idea we have described for years as "variance instead of value": the target is the baseline, the value itself matters only as a deviation from it – and beyond a defined threshold, say ±5%, it demands attention. A report that shows only values leaves the arithmetic to the reader.

Time series in IBCS® notation: time left to right, actual dark, budget outlined, prior year grey; the gap in the second quarter is visible without a table.

Once the notation is fixed, people argue about numbers – not about colours. That is the real benefit of the standard: it takes the presentation question off the meeting's agenda so that time is left for the substance.

What IBCS® does not solve

IBCS® says how to show. It does not say what to show. Whether revenue by business unit belongs on the first page of the management report at all, whether the management team decides anything with that number or merely notes it, what cadence the measure needs and how you would notice things going wrong – on all of this the standard is silent, and rightly so. It is not its job.

That is the most common mistake in implementation: taking the existing report pack with its 40 measures and redrawing it in IBCS® notation. The result is a handsome report nobody needs. The question "What are these numbers supposed to tell us? What are they for?" must be answered before the notation. For that we use the framework "From decision to measure": first the decision, then the question, then the measure, then the data – and only then the report. IBCS® is the answer to step five. Whoever starts there has skipped the first four.

Nor does the standard fix data problems. An outlined budget bar next to a solid actual bar is information only if both numbers rest on the same definition and reconcile to the close. Reconcilability comes before beauty.

Starting pragmatically: a notation concept on two pages

The full standard runs to well over a hundred pages. Nobody has to implement all of them to get the benefit. The approach we have used in reporting projects for years is "pragmatic notation rules in line with IBCS®" – and it fits on two pages.

Page one covers notation: scenarios (actual, budget, prior year, forecast) and their fill; variance bars with colours for good and bad; comparison order PY – actual – budget; time horizontal, structure vertical; uniform scales per page; unit and period in the title; the threshold above which a variance is commented on. Page two covers structure: title convention with a message, one page per unit, a fixed position for every measure, a comment block following the pattern "What – So what – Now what". Points where the company deliberately departs from the standard are marked as such. That is not a dilution; it is the condition for the rule holding up in daily use.

Then comes the pilot: one report, usually the monthly management report or the report of a unit that needs reworking anyway. It is rebuilt to the concept, used in the real meeting for two cycles and then adjusted. Only when the pilot stands is the concept declared the standard and rolled out unit by unit. Standardise, then scale – not the other way round.

Whether that is built with Zebra BI, with native Power BI visuals, with Excel templates or with think-cell is a tooling question, not a concept question. Zebra BI saves a lot of manual work and is a good choice when many reports are involved; native visuals are enough for a five-page management cockpit if you are prepared to configure the notation properly once. We recommend the tool after the concept, never before.

From practice

At an industrial company I introduced the notation concept in exactly this way: two pages of rules, one pilot report from the unit that had been first to move to Power BI, then a roll-out unit by unit. The biggest argument was not about measures but about colours – whether actual should be dark blue or black, whether the corporate colour had to appear somewhere, whether red for negative variances was too harsh. That took two meetings, then the rule stood. After that, nobody in any review talked about presentation any more, only about the numbers. That was the moment I realised the standard is not primarily a design topic but a time saving for meetings.

In his ten rules for controlling success, Dirk Fischer puts two sentences that capture the core of IBCS® better than some pages of the standard itself: "Analyse in detail. Present the big picture." (Fischer, in Mehlfeld et al. 2018, p. 12) and, as rule ten, "Simplicity before precision" (p. 18). Fischer describes the controller's inclination towards precision – and the reproach that follows from it: complicated and unintelligible. The IBCS® notation is the answer to that in the form of a drawing rule. It forces you to leave the detail in the analysis and to show on the page only the line that carries the decision.

Frequently asked questions about IBCS®

Is IBCS® a tool?

No. IBCS® is a set of rules, not software. There are tools that make the notation much easier – Zebra BI for Power BI and Excel, think-cell for PowerPoint, extensions for SAP Analytics Cloud or Tableau – but the standard can be applied with any software that can draw bars and set colours. The tooling question comes after the concept question.

Do I need a certification?

No. The IBCS® standards are free to use; nobody needs a certification to build reports to the rules. Certifications exist for people (analysts, consultants, trainers) and for software, and they are awarded by the IBCS Institute. Anyone who is not certified may not call themselves "IBCS certified" and should distinguish clearly between the standard and their own services. For an implementation in your own company this is irrelevant: a good notation concept needs consistency, not a certificate.

Does it apply to Excel as well?

Yes, and Excel is often the best place to start. The notation can be built in Excel with standard charts: fill and border per data series, variances as a separate series, fixed axis scaling. What Excel does badly is scaling to many reports – that takes templates and discipline. For the pilot phase and for companies with one monthly report it is entirely sufficient.

What does the standard cost?

Nothing. The IBCS® standards are published under the Creative Commons licence CC BY-SA 4.0 and can be read online free of charge. Costs arise from implementation: concept, pilot, templates, possibly software and training. That is the part where it is worth asking whether to do it yourself or have it guided – and where a fixed price for a clearly defined result offers more certainty than a day rate for an open-ended task.

What does ISO 24896 change?

In substance, little for most users; formally, quite a lot. ISO 24896 "Notation for business reporting" was published in June 2026 and adopts the notation part of IBCS® – the rules on labelling, the layout of charts and tables, and the representation of scenarios and variances. The rules themselves are familiar to experienced users. What is new is that a reporting guideline can now refer to an international standard, which carries weight in corporate groups, with auditors and in software tenders. Also new is the terminology: version 2.0 speaks of notation and composition rather than conceptual, perceptual and semantic rules.

The next step

Tomorrow, take your current management report pack and count: how many different colour schemes, scales and comparison orders does it contain? If it is more than one per category, you have the case a notation concept is designed for. The checklist above helps you write down the rules you need – and drop the ones you do not.

If you would rather not take that step alone: in a scoping sprint we clarify, within two to three weeks at a fixed price, which decisions the report is meant to carry, which measures that requires and what the notation concept looks like – the result is a decision-ready target picture including a pilot page. What you build yourself afterwards and what we build, we agree together.

Sources

IBCS Association: IBCS® Standards 1.2, © IBCS Association, www.ibcs.com, CC BY-SA 4.0. IBCS® is a registered trademark of the IBCS Institute.
IBCS Association (2026): IBCS® Version 2.0 – aligned with ISO 24896, released 11 June 2026, www.ibcs.com/ibcs-version-2-0/
IBCS Association (2026): ISO 24896 Notation for business reporting, www.ibcs.com/iso-24896/
IBCS Association: Creative Commons FAQ and Terms of Use, www.ibcs.com/creative-commons-faq/, www.ibcs.com/terms-of-use/
Fischer, D. (2018): Zehn Regeln für den Controlling-Erfolg. In: Mehlfeld, T.; Schneider, C.; Stahl, K.-U.; Wiener, A. (eds.): Reporting- und Business-Intelligence-Werkzeuge für den Controller, pp. 10–19 (in German; quotations translated).
Hamid, S. (2023): The Ultra Guide – Storytelling & Presentations for Finance Professionals (comment pattern "What – So What – Now What").
Ossola-Haring, C.; Schlageter, A.; Schöning, S. (2019): 11 Irrtümer über Kennzahlen, 2nd ed., Springer Gabler (in German).