[Concept 002]HKAS 1 / IAS 1 Presentation in Plain English: Going Concern, Materiality and “No Offsetting” Rules

[Concept 002]HKAS 1 / IAS 1 Presentation in Plain English: Going Concern, Materiality and “No Offsetting” Rules

Note: This article provides a focused explanation and extended discussion on a specific standard. If you’d like to see the full list of articles and short summaries for this standard, please visit the “Series Overview” page.

Since 2025, most standard‑related articles on this site have been available in both Chinese and English versions. If you’d like to read the English explanation, please visit the 「系列總覽」 page and look for the corresponding article.

Plain‑English explainer of HKAS 1 / IAS 1 for students, junior accountants and non‑specialists who find official standards too dense to read.


This article is based on Hong Kong Accounting Standards (HKAS / HKFRS), which are fully aligned with IAS / IFRS except for minor local tweaks, so the same principles generally apply under IAS / IFRS unless noted otherwise. The goal is to unpack HKAS 1 Presentation of Financial Statements (equivalent to IAS 1) using plain English and practical, real‑life examples instead of technical jargon. It is written for students, junior accountants, audit juniors and finance professionals who want to understand not just “what the standard says” but how to actually read and prepare financial statements in line with it.

When you see “the company” or “the entity” below, you can think of any entity that prepares general purpose financial statements under HKFRS / IFRS.


What Does HKAS 1 / IAS 1 Really Do?

When you read financial statements from different companies, you will quickly see that, even across very different industries, the basic “skeleton” of the statements looks similar. You will always see ideas like true and fair presentation, going concern, accrual basis, materiality and aggregation, and the general “no offsetting” rule appearing again and again. HKAS 1 Presentation of Financial Statements (equivalent to IAS 1) is the standard that sets these cross-cutting principles for how information is presented, classified and disclosed.

Most standards feel topic-based: leases, revenue, financial instruments and so on. HKAS 1 is different: it acts like a backbone across all topics, telling you how to present amounts, how much detail to show, when to split line items, and when extra disclosures are needed so users can actually understand the numbers. Once you understand this mindset, every set of financial statements becomes easier to read, and your working papers will look much more well‑reasoned.


What You Should Be Able to Do After Reading?

By the end, you should be able to:

  • Explain the relationship between “true and fair presentation” and compliance with HKFRSs / IFRSs, and describe the very rare conditions for departing from a standard and the related disclosures.
  • Understand what going concern and accrual basis mean, and why significant uncertainty about going concern (for example, in restructuring or near‑bankruptcy situations) must be clearly disclosed.
  • Apply the principle of “materiality and aggregation”: when to split out important items, when it is acceptable to combine smaller ones, and how to avoid burying key information.
  • Explain why assets and liabilities, income and expenses generally must not be offset, and recognise common situations where net presentation is allowed or required.
  • Use the updated materiality definition, including the ideas of “could reasonably be expected to influence” and “obscuring information”, to design sensible disclosure decisions in practice.

1. True and Fair View vs Following HKFRSs / IFRSs

What does “true and fair view” actually mean?

HKAS 1 says the main objective of a complete set of financial statements is to present a true and fair view of the entity’s financial position, financial performance and cash flows. In simple terms, this means the statements should faithfully represent the economic reality of the company’s transactions and events, not just follow rules mechanically. The amounts and descriptions should be complete, neutral and free from error to the extent possible, so that users can rely on them for decisions.

Why does compliance with HKFRSs / IFRSs matter?

HKAS 1 states that, if a company complies with all applicable HKFRSs and provides any additional disclosures needed, it is presumed to have achieved a true and fair view. There are two key ideas here:

  • The standards are meant to work as a complete framework, not a menu where management picks only the standards it likes.
  • Even if the minimum wording of a standard is followed, the company still has to add extra disclosures whenever necessary to avoid misleading users or leaving important risks unexplained.

So in exams and in practice, you can think of it like this: following HKFRSs / IFRSs is the normal route to a true and fair view, but management and auditors must still ask, “Is this enough for users to understand the entity’s situation?”

The “extremely rare” departure from a standard

HKAS 1 allows that, in extremely rare cases, following a specific requirement in a standard might actually make the overall financial statements misleading, rather than true and fair. In such a situation, the entity may depart from that particular requirement, but only if strict conditions are met and extensive disclosures are provided.

Typical disclosures include:

  • Which exact requirement(s) the company has departed from.
  • Why following the requirement would have resulted in information that is not true and fair, and how the departure improves faithfulness.
  • What the amounts and presentation would have looked like if the standard had been followed as written.

In normal work you are very unlikely to see a genuine departure from a standard. Almost all issues are solved by applying the standard and adding suitable additional disclosures. For study and exams, the key takeaway is: true and fair view is the top-level principle, and compliance with HKFRSs / IFRSs is the usual way to meet it, supported by extra disclosure when needed.


2. Going Concern and Accrual Basis Accounting

Going concern: can the entity keep operating?

HKAS 1 requires management to assess whether the company can continue as a going concern for the foreseeable future, usually at least twelve months from the reporting date. If there is no intention or realistic ability to continue operations, the financial statements should not be prepared on a going concern basis; instead, a liquidation or other appropriate basis is used.

Management must pay close attention when, for example:

  • Cash is tight, major bank loans are about to mature and refinancing is uncertain.
  • The company is planning a major restructuring or significant downsizing of operations.
  • The company faces events that may cause it to lose key licences, contracts or major customers.

Even if the financial statements are still prepared on a going concern basis, any material uncertainties that cast significant doubt on the entity’s ability to continue as a going concern must be clearly disclosed in the notes, along with management’s assessment.

Accrual basis vs cash information

HKAS 1 also requires that, except for the statement of cash flows, all financial statements are prepared on an accrual basis. That means:

  • Income and expenses are recognised when they are incurred, not when cash is received or paid.
  • Assets and liabilities represent existing rights and obligations, not just cash balances.

The statement of cash flows (under HKAS 7, equivalent to IAS 7) complements this by giving a cash-based view of the period’s inflows and outflows. This helps users see how accrual‑based profit links (or does not link) to cash generation. For example, a company can show a profit while its trade receivables increase significantly and operating cash flows are negative, signalling liquidity risk.

In practice, when going concern is in doubt—such as during restructuring or near insolvency—auditors will pay particular attention to cash flow forecasts and whether the accrual profits are masking short‑term liquidity problems.


3. Materiality and Aggregation: When to Split, When to Combine

What is “materiality” under HKAS 1 / IAS 1?

HKAS 1 emphasises that only material information needs to be presented or disclosed separately; immaterial information can be aggregated, and in some cases need not be disclosed at all. The updated definition says that information is material if omitting it, misstating it or obscuring it could reasonably be expected to influence decisions of the primary users of the financial statements.

Key points in this definition include:

  • Both size and nature matter; for example, a related party transaction may be material by nature even if the amount is not huge.
  • Materiality applies to narrative disclosures as well as numbers; items like accounting policies, key assumptions and estimation uncertainties can be material even if not directly tied to a large numerical amount.

When must items be presented separately?

If assets, liabilities, income or expenses differ significantly in nature, risk or meaning for users’ analysis, they should be presented as separate line items. For example:

  • Combining trade receivables with loans to related companies into one line could hide both credit risk and related party risk.
  • Mixing one‑off restructuring costs with routine operating expenses can distort the picture of underlying, recurring profitability.

Separate presentation helps users see important drivers of performance and risk, instead of forcing them to dig through notes or guess what is included.

When is aggregation acceptable?

For smaller items that are similar in nature and provide limited additional insight on their own, HKAS 1 allows aggregation into an “other” category on the face of the statement, with breakdowns given in the notes if needed. However, the standard warns that you must not use aggregation to bury important information in a big “other items” bucket.

For example, if “other expenses” includes a one‑off, material litigation settlement, that element should either be separately presented on the face of the statement or clearly highlighted in the notes. Simply hiding it in “other” would risk obscuring material information.


4. The No‑Offsetting Principle and Its Common Exceptions

General rule: no offsetting

HKAS 1 takes a clear position: assets and liabilities, and income and expenses, should not be offset against each other and presented as a net figure, unless another standard explicitly requires or permits it. The reason is straightforward—offsetting hides transaction volumes, gross exposures and risk, reducing transparency for users.

Examples include:

  • Bank deposits should not be directly netted off against bank loans on the face of the balance sheet.
  • Revenue should not simply be shown as “gross profit” without disclosing the gross revenue and cost of sales amounts (unless these are clearly presented elsewhere).

Typical exceptions where net presentation makes sense

Although the default rule is no offsetting, HKAS 1 and other standards acknowledge that in certain specific situations, net presentation better reflects the economic substance. Common examples are:

  • Disposal of non‑current assets or investments: entities typically present a single line item “gain or loss on disposal”, which is the net of disposal proceeds minus carrying amount and directly related costs.
  • Provisions and reimbursements under HKAS 37 (IAS 37): where an expense is expected to be reimbursed (for example, by an insurer or a supplier) and the criteria are met, it may be appropriate to present the expense net of the reimbursement or show the reimbursement as a separate asset, depending on the specific guidance.
  • Offsetting financial instruments under HKAS 32 (IAS 32): financial assets and liabilities may be presented on a net basis if the entity has a legally enforceable right to set off and intends to settle on a net basis or simultaneously.

In practice and in exams, common mistakes include:

  • Netting different types of income with discounts or rebates in a way that makes revenue appear artificially small and less transparent.
  • Presenting receivables and payables on a net basis when there is no legally enforceable right of set‑off, or no intention to settle net.

A simple way to think about it: start with the assumption that everything should be shown gross, and only consider net presentation when a specific standard clearly allows it or when net figures more faithfully depict the transaction as a single item.


5. The Evolving Definition of Materiality and “Obscured” Information

From “might affect” to “could reasonably be expected to affect”

Earlier versions of materiality definitions used phrases like “could influence users’ decisions”, which some felt set the bar too low and made it hard to distinguish truly important matters from tiny differences. The updated definition in HKAS 1 and HKAS 8 now uses the idea that omission, misstatement or obscuring of information could reasonably be expected to influence decisions of primary users.

“Could reasonably be expected” carries two ideas:

  • There does not need to be 100% certainty that decisions will change, but there must be a realistic possibility of influence.
  • The assessment is made from the perspective of a rational, informed primary user, not based purely on management’s subjective view.

Some stakeholders suggested tightening the wording to “would influence decisions” to raise the threshold, but this was not adopted because it risked making the bar too high and might let genuinely important matters be treated as “not material”.

Bringing “obscuring” into the materiality definition

Recent amendments explicitly incorporate obscuring into the definition of materiality and provide examples of how information can be obscured even when no numeric error or omission occurs. Common patterns include:

  • Using vague or unclear wording that leads users to misunderstand the underlying issue.
  • Scattering key information across many different parts of the financial statements so that users struggle to piece together the full picture.
  • Aggregating items with different natures into a single line in a way that hides important differences in risk or behaviour.
  • Overloading the notes with large volumes of immaterial detail so that truly important information gets lost in the noise.

Even if there is no wrong number or missing disclosure, these patterns can still amount to a materiality problem because users cannot form a proper understanding of the entity’s situation.

Mini‑case: omission, misstatement and obscuring

Consider a related party transaction that is not large in amount, but sensitive in nature:

  • Omission: the transaction is not disclosed at all, even though related party disclosures are required.
  • Misstatement: the transaction is disclosed but wrongly described as a third‑party transaction instead of a related party one.
  • Obscuring: the transaction is lumped into a large pool of “normal customer transactions” without flagging that it involves a related party.

All three situations can create a materiality issue, not only the first two. The “obscuring” case is particularly relevant in practice, where there is a temptation to hide sensitive items inside broad categories.


6. A Practical Step-by-Step Approach to Disclosure Decisions

A simple decision process for materiality

Bringing all the concepts together, you can use a simple step‑by‑step process when deciding what and how to disclose under HKAS 1 / IAS 1.

  1. Identify relevant mattersLook for items that could require specific presentation or disclosure, such as major lawsuits, restructuring costs, changes in accounting policies, new financing arrangements, or related party transactions.
  2. Assess both nature and sizeDo not only ask “how big is it?”; also consider the nature of the item. Transactions involving regulation, related parties or one‑off significant events may be material by nature even if they are not huge in percentage terms.
  3. Consider whether information might be obscuredAsk yourself: if this item is buried inside an “other” category or described only in vague terms, can primary users still reasonably understand the company’s performance and risk profile? If the answer is no, there is a risk of obscuring material information.
  4. Choose the appropriate presentationBased on your assessment, decide whether to:
    • Present a separate line item on the primary statement.
    • Provide a detailed note explaining the nature, amount, timing and risk.
    • Aggregate items but still give enough detail that users can follow the story.
    • Conclude that the matter is not material and does not require specific disclosure.

Common mistakes to watch out for

Typical errors seen in practice and exams include:

  • Mechanical “shopping list” disclosures: disclosing every possible item without any materiality screening, leading to long notes with no clear focus.
  • Blind reliance on a fixed percentage: using a single quantitative threshold (for example, 5% of total assets) as the only test for materiality and ignoring qualitative factors and the wider context.
  • Over‑disclosure for “safety”: including large amounts of minor details to feel safe, but actually reducing clarity and making it harder for users to find truly important information.

In real life, management might ask, “Can we delete this disclosure so the report looks cleaner?” Your job is not just to say yes or no, but to use HKAS 1’s materiality principles to explain why certain repeated or trivial disclosures can reasonably be simplified, while key information must remain prominent. This is how you move from “just following rules” to understanding the logic behind them.


7. Looking at the Whole Set of Financial Statements Through the HKAS 1 / IAS 1 Lens

HKAS 1’s general features are not “small print”; they form the underlying mindset for preparing and reading financial statements: true and fair presentation, going concern, accrual basis, materiality and aggregation, no arbitrary offsetting, and the handling of obscured information. When you next work on financial statements—either drafting or auditing—try asking yourself:

  • Does the set of statements as a whole achieve a true and fair view, or is more disclosure needed for key risks and transactions?
  • Has management seriously assessed going concern, and are any material uncertainties clearly described if they exist?
  • Are important items appropriately separated and minor items sensibly aggregated, instead of burying the main message in long lists of immaterial details?
  • Have any items been improperly offset in a way that hides risk or reduces transparency?

If you add just one or two lines in your working papers explaining why you consider certain information material or immaterial, or why you chose gross vs net presentation, you will clarify your own thinking and show to managers and auditors that you understand not only the rules, but also the rationale behind them.

To deepen this, you can combine the general principles of HKAS 1 with the sections that describe the structure of each primary statement, and then connect them to other standards like HKAS 7 (cash flows) and HKAS 8 (accounting policies and errors). Over time, this builds a more complete framework for how financial reporting works under HKFRSs / IFRSs.


Key Takeaways for Students and Junior Accountants

  • Use HKAS 1 / IAS 1 as a thinking framework: whenever you prepare or review statements, consciously check going concern, accrual basis, materiality, aggregation and offsetting.
  • In exams and at work, clearly link “true and fair view” to compliance plus additional disclosure—do not assume that following minimum wording is always enough.
  • Be especially careful with going concern, related party transactions, major one‑off items and offsetting; these areas are frequent sources of mistakes and exam questions.
  • When reading contracts, drafting journals or building working papers, document your materiality and presentation judgments in short, clear notes: why is this item separate, aggregated, gross or net?
  • Remember that “over‑disclosure” can also be a problem: avoid drowning users in immaterial detail that hides what really matters, and always ask whether information is being obscured.

If this article was helpful, you’re very welcome to subscribe to my Substack for free:

  • All full articles are published on my website first.
  • Whenever I finish a mini‑series on a standard, I’ll send one email that pulls the whole series together and links everything in one place, so you can revise without hunting around.
  • I occasionally share small, practical tips from real‑life accounting work.
  • When I release new PDF notes, in‑depth case studies or paid content in the future, email subscribers will be the first to know.

If you’d like to ask me questions or chat about your learning, you can follow me on Threads / IG and send me a DM — I’ll reply as far as I can.
And if you feel these resources have helped you, you can also buy me a coffee to support me in writing more.

[Concept 002]HKAS 1 / IAS 1 Presentation in Plain English: Going Concern, Materiality and “No Offsetting” Rules

罔相心室: https://chinese.iamdelusionman.com/
Zero-to-Acct Substack: https://zerotoacct.substack.com/
Thread: https://www.threads.com/@yickki_mong
IG: https://www.instagram.com/yickki_mong/

Comments

No comments yet. Why don’t you start the discussion?

    Leave a Reply