Compliance with IFRS Standards does not guarantee identical presentation across different entities, because several Standards either apply only to particular categories of entity or permit a genuine choice between acceptable methods.

Both IFRS 8 (Operating Segments) and IAS 33 (Earnings per Share) apply exclusively to listed entities. Since Marwan is not yet listed, neither disclosure is compulsory for it — though nothing stops Marwan from providing them voluntarily. Once Marwan secures its own listing, both disclosures become mandatory.

As for the government grant, IAS 20 (Accounting for Government Grants and Disclosure of Government Assistance) does require grants to be recognised in profit or loss systematically, matching the related costs — but it explicitly permits two different presentation approaches. Ekramy's method nets the grant against the non-current asset's cost, reducing future depreciation charges. Marwan's method instead recognises a deferred income balance, released to profit or loss over time. Both approaches produce an identical net effect on profit or loss; only the presentation differs. Each entity simply needs to apply its chosen method consistently.

IAS 37 (Provisions, Contingent Liabilities and Contingent Assets) governs this area. Recognising a provision first requires a past obligating event, and since both customers received the allegedly faulty goods before the year end, that condition is met for both claims.

The next test is whether an outflow of economic benefit is probable, which IAS 37 defines as a likelihood exceeding 50%. Only Customer A's claim clears this threshold (60%), so a provision is appropriate for Customer A alone. Customer B's 25% likelihood falls below the bar, making that claim a contingent liability instead — disclosed in the notes rather than provided for.

The provision for Customer A is measured at the best estimate of the expected outflow, here the full $10 million.

As for the potential insurance recovery, IAS 37 treats this as a contingent asset. Contingent assets are never recognised in the statement of financial position unless the inflow is virtually certain — a materially higher bar than merely highly probable. So even though recovery from the insurer is highly probable, it remains disclosure-only rather than a recognised receivable. This is precisely why the accounts show a liability without a mirrored asset: the two items are tested against different recognition thresholds, and only the liability clears its bar.

The overall presentation framework for the financial statements comes from IAS 1 (Presentation of Financial Statements), which requires every item of income and expense to appear somewhere within the statement of profit or loss and other comprehensive income — there is no third option.

Entities do not choose freely between the two sections. Unless a specific IFRS Standard requires or permits otherwise, IAS 1's default position is that income and expense items belong in the profit-or-loss section.

Regarding tax on other-comprehensive-income items: IAS 1 allows this to be presented either as its own separate line within the other comprehensive income section, or netted directly against each individual OCI component, with the detail disclosed in the notes instead.

The practical consequence that matters most to shareholders is this: anything routed through other comprehensive income, rather than profit or loss, is excluded from the calculation of earnings per share — a headline performance measure that listed entities like Ekramy are required to report.

Under IFRS 16 (Leases), a lessee is required to recognise a right-of-use asset for essentially every lease, with only two narrow exceptions: leases of twelve months or less, and leases of low-value assets. A five-year warehouse lease qualifies for neither exception, so recognising a non-current asset here is correct regardless of who legally owns the underlying property.

The asset's initial carrying amount combines two components: the present value of the future lease payments, plus any directly attributable set-up costs. Adding these together — $1,895,000 plus $105,000 — gives an initial carrying amount of $2,000,000 as at 1 October 20X4.

This amount sits within property, plant and equipment as its own separate component and is depreciated over the lease term. For the six months from 1 October 20X4 to the 31 March 20X5 year end, depreciation comes to $200,000 ($2,000,000 ÷ 5 years × 6/12), leaving a closing carrying amount of $1,800,000 ($2,000,000 less $200,000) — matching the figure the director queried.

Recognising the right-of-use asset also brings a matching lease liability onto the statement of financial position, initially measured at the same $1,895,000 present value. Over time, this liability accretes a finance charge, calculated on the outstanding balance at the rate implicit in the lease, which is expensed through profit or loss, while each rental payment reduces the liability. Because the next rental payment falls due six months after the year end, $500,000 of the liability is classified as current, with the remainder shown as non-current.

IFRS 8 (Operating Segments) requires entities within its scope to report based on their own operating segments — not on a single, universally fixed notion of a 'segment' applied identically everywhere.

An operating segment is defined by reference to how the business is actually run: a component of the entity for which discrete financial information exists, and whose results are regularly reviewed by the chief operating decision maker (the individual, or group, responsible for assessing performance and allocating resources). Ayman evidently manages and reports internally along geographical lines, while the competitor most likely does so along product lines — IFRS 8 simply follows whichever internal structure genuinely drives each entity's own decision-making.

That said, IFRS 8 does impose some baseline disclosures regardless of segment structure — typically revenue analysed by geographical area and by product or service type, along with non-current assets by geographical area — unless obtaining that information would come at a prohibitive cost. That carve-out may well account for at least part of the difference you're seeing.

Under IAS 24 (Related Party Disclosures), your brother's firm qualifies as a related party of Ayman, because it is controlled by a close family member (your brother) of one of Ayman's key management personnel (you).

IAS 24 requires disclosure of every related party relationship, together with details of any transactions and outstanding balances between them (the exact wording is not what matters here). Critically, IAS 24 treats related party relationships as inherently material, regardless of the monetary amounts involved or how ordinary the transaction terms may be — so neither the contract's small size nor its unremarkable terms exempts it from disclosure.

IFRS 6 (Exploration for and Evaluation of Mineral Resources) governs this area.

On your first point: IFRS 6 deliberately does not prescribe which specific expenditures should be classified as exploration and evaluation assets. Instead, each entity develops its own accounting policy, applied consistently, based on the degree to which particular expenditure can be linked to finding the specific mineral resources being sought. Given how entity-specific this judgement can be, it is entirely possible for two companies in similar sectors to reach different conclusions and therefore present different category breakdowns.

On your second point: IFRS 6 specifically excludes the cost of developing mineral resources from the exploration and evaluation assets figure. Once a resource moves from exploration and evaluation into development, those costs instead fall under IAS 38 (Intangible Assets).

On your third point: yes, this is acceptable. IFRS 6 allows entities to measure exploration and evaluation assets under either the cost model or the revaluation model — both are equally valid choices under the Standard.

The accounting treatment for events occurring after the year end is set out in IAS 10 (Events after the Reporting Period), which defines the relevant window as running from the reporting date up to the date the financial statements are authorised for issue — in this case, 15 November 20X5.

IAS 10 splits such events into two categories: adjusting and non-adjusting. Adjusting events provide additional evidence about conditions that already existed at the year end. The legal case falls into this category — the dispute existed at 30 September 20X5, and the October settlement simply provides more precise evidence of the amount owed — so it is correct to recognise the confirmed $5.5 million liability in the year-end financial statements.

The factory fire, by contrast, relates to a new event arising after the year end, with no connection to conditions existing at 30 September 20X5, making it non-adjusting. IAS 10 requires non-adjusting events to be disclosed in the notes rather than adjusted for in the figures themselves, which is exactly what has been done here. The only circumstance that would change this treatment is if the event threatened the entity's going concern status, which is not the case here.

As for the customer's insolvency: since it occurred on 20 November 20X5, after the 15 November 20X5 authorisation date, it falls entirely outside the reporting window defined by IAS 10, and therefore requires no disclosure at all in the financial statements for the year ended 30 September 20X5.

The rules governing an entity's first-time move to IFRS Standards sit in IFRS 1 (First-time Adoption of International Financial Reporting Standards). IFRS 1 requires both the current period and the comparative figures to be presented under the IFRS Standards in force at the entity's first IFRS reporting date — here, 30 September 20X5. This rules out simply reusing last year's national-standards figures as-is.

The starting point is an opening IFRS statement of financial position, prepared as at the beginning of the earliest comparative period presented in Ekramy's first full IFRS financial statements. For Ekramy, that date is 1 October 20X3.

Unless there is objective evidence they were wrong, the accounting estimates carried into this opening IFRS statement of financial position should be consistent with those Ekramy originally used under its national standards.

Because this opening position must be published alongside the first IFRS financial statements, Ekramy's 30 September 20X5 accounts will actually contain three statements of financial position rather than the usual two — though still only two statements of profit or loss and other comprehensive income, and two statements of changes in equity.

Any difference between net assets at 1 October 20X3 measured under national standards versus IFRS Standards is recognised through the statement of changes in equity for the comparative period, not through profit or loss.

Finally, Ekramy's first IFRS financial statements must include reconciliations of equity, previously reported under national standards, to the equivalent IFRS-based figures at every date previously reported — for Ekramy, this means reconciliations at both 1 October 20X3 and 30 September 20X4.

Because this subsidiary was previously owned by three private shareholders and does not operate in banking or finance, it qualifies as an entity without public accountability. Entities in this position are permitted — though not required — to report under the simplified framework set out in the IFRS for Small and Medium-sized Entities (IFRS SME).

The IFRS SME restricts recognition of certain assets and liabilities compared with full IFRS (for example, borrowing costs are always expensed immediately, never capitalised, under the IFRS SME), and its disclosure requirements are considerably lighter than those of full IFRS Standards.

Even now that it belongs to a group reporting under full IFRS at the consolidated level, the subsidiary itself can continue applying the IFRS SME in its own individual financial statements. The necessary adjustments to bring its figures into full IFRS compliance are simply made at the point of consolidation.

Under IFRS 10 (Consolidated Financial Statements), Mrehan would only be a subsidiary if we were able to control its operating and financial policies. Although substantial and long-term, this investment does not give us that level of control, so consolidating Mrehan would not be appropriate.

Under IAS 28 (Investments in Associates and Joint Ventures), a shareholding above 20% — our 40% comfortably clears this — creates a rebuttable presumption of significant influence over the investee's operating and financial policies. Given that we can appoint four of Mrehan's ten directors, and nothing suggests the other shareholders or directors are acting together to block our influence, this presumption holds here. Mrehan is therefore properly classified as an associate.

IAS 28 requires associates to be measured using the equity method: the investment is initially recorded at cost, then adjusted each period for our 40% share of Mrehan's post-acquisition change in net assets. This equity-accounted figure is not designed to track fair value, which is why the $40 million carrying amount can legitimately differ from the $42 million market-based fair value.

Switching raw materials from first-in-first-out to weighted average cost is a change in accounting policy, since it alters the underlying principle used to measure those assets. Under IAS 8 (Accounting Policies, Changes in Accounting Estimates and Errors), such a change is only appropriate where the new policy results in financial statements that are more reliable and more relevant to the effects of transactions, other events, or conditions on the entity's financial position, performance, or cash flows.

Under IAS 2 (Inventories), the choice of measurement formula is made by category of inventory with a similar nature and use to the entity — not necessarily uniformly across all inventory. Raw materials can reasonably be regarded as having a different nature and use from other inventory categories, so applying weighted average cost to raw materials while retaining first-in-first-out elsewhere is, in principle, acceptable.

Comparability is preserved by restating the prior year's comparative figures as though the new policy had always been applied. Any resulting difference between previously reported opening and closing equity and the equivalent figures under the new policy is presented as an adjustment to opening equity for both the current and prior period, shown within the statement of changes in equity (and its comparative) — it does not flow through profit or loss.

The Conceptual Framework is a document setting out the objectives and underlying concepts for general purpose financial reporting. It underpins the IFRS Standards but is not itself a Standard.

Its concepts are organised into distinct chapters, covering matters such as the overall objective of general purpose financial reporting — providing financial information useful to existing and potential investors, lenders, and other creditors — along with a chapter setting out the qualitative characteristics that make financial information useful.

A central purpose of the Framework is to help the Board develop and revise individual IFRS Standards on a consistent conceptual basis, so the principles underlying any given Standard should generally align with the Framework.

Importantly, the Framework does not override any specific IFRS Standard. On the rare occasions the Board issues a new or revised Standard that conflicts with the Framework, it must explain the departure and its reasoning in that Standard's Basis for Conclusions.

The Framework also assists preparers in developing consistent accounting policies for matters not addressed by a specific Standard (such as cryptocurrency) or where a policy choice exists, and helps all parties interpret IFRS Standards more consistently.

A brand name is an intangible asset, so its recognition and measurement is governed by IAS 38 (Intangible Assets). IAS 38 makes recognition depend on how the brand name arose: purchased brand names can be recognised as assets, but the treatment differs depending on the nature of the purchase.

Where a brand is bought in a standalone transaction, it is recognised at its purchase cost. Where a parent acquires a subsidiary, the purchase consideration is allocated across the individual identifiable assets and liabilities being brought into the consolidated accounts, with any unallocated residual presented as goodwill. A brand acquired this way can be recognised as a separate asset in the consolidated financial statements provided it is identifiable — meaning it is either separable (capable of being sold on its own) or arises from contractual or other legal rights, whether or not those rights are themselves transferable — even if the subsidiary never recognised the brand as an asset in its own individual accounts. Where identifiable, the brand is initially recognised at its fair value as at the acquisition date.

The Ayman brand itself, however, is internally generated from Ayman's own perspective. Internally generated intangible assets (aside from costs tied to developing a specific product or process) cannot be recognised, because their cost cannot be measured reliably. This is exactly why brands acquired with subsidiaries appear in the consolidated accounts while the Ayman brand does not — the difference lies in how each brand originated, not an inconsistency in treatment.

Once recognised, a brand name is amortised as an intangible asset over its estimated useful life. Where that useful life is assessed as indefinite, no amortisation is charged, but the brand must instead be tested for impairment at the end of every reporting period, regardless of whether any indicators of impairment exist.

Segmental disclosure requirements come from IFRS 8 (Operating Segments), which bases disclosure on an entity's own operating segments rather than a single fixed template. An operating segment is one that earns revenue and incurs expense, has discrete financial information available, and whose results are regularly reviewed by the chief operating decision maker — a function, not a specific job title, usually (but not always) performed by the chief executive, sometimes by a group of directors collectively.

Segments become reportable either because they clear IFRS 8's quantitative thresholds, or because reporting them helps users understand the nature of the business and the environment it operates in (products, production processes, customer types, distribution, regulatory environment). Since entities can be structured very differently internally, two outwardly similar businesses can validly identify and report quite different segments.

As for the competitor: IFRS 8 applies only to listed entities. Since this family-run business is unlisted, it is simply outside IFRS 8's scope and has no obligation to provide segmental disclosures at all, regardless of its size.

IFRS 10 (Consolidated Financial Statements) sets out the relevant principles. Ordinarily, a subsidiary's financial information should be prepared to the same reporting date as its parent; where the dates differ, additional financial information is normally drawn up for the subsidiary as at the parent's reporting date.

Where this is impracticable, IFRS 10 permits the parent to consolidate using the subsidiary's most recent financial statements instead, provided adjustments are made for any significant transactions occurring between the subsidiary's reporting date and the parent's — but only where the two reporting dates are no more than three months apart.

Since Ekramy's 31 December 20X4 year end sits within three months of Ayman's 31 March 20X5 year end, it is acceptable to use Ekramy's existing financial statements (adjusted for any significant intervening transactions) when preparing the Ayman group's consolidated accounts. There is no requirement for Ekramy to change its year end following the acquisition, though aligning the dates might simplify future consolidations.

Segmental disclosures are governed by IFRS 8 (Operating Segments), which applies only to listed entities. Since Ekramy itself is unlisted, it has no obligation to provide these disclosures in its own individual financial statements.

However, now that Ekramy is part of the Ayman group, its operating segments must in principle be considered for disclosure within Ayman's consolidated financial statements — provided they meet IFRS 8's reportability criteria. Specifically, a segment must be regularly reviewed by the group's chief operating decision maker and be material in the context of the whole group: broadly, its reported revenue, profit, or assets must reach at least 10% of the combined total for all operating segments across the group. Even where a segment falls short of these quantitative thresholds, IFRS 8 still permits its disclosure if management judges the information would be useful to users.

Investment property is governed by IAS 40 (Investment Property), which requires initial measurement at cost, but then permits a policy choice for subsequent measurement: either the cost model or the fair value model, applied consistently to all investment property held.

Ekramy's use of the cost model in its own financial statements is not, in itself, incorrect — IAS 40 permits either model. However, at the date Ayman acquires Ekramy, the 'cost' of Ekramy's investment properties for consolidation purposes becomes their fair value as at the acquisition date. From that point on, the Ayman group must measure these properties under the fair value model for consolidation purposes, requiring ongoing adjustments at the group level. Ekramy is not required to change its own individual accounting policy, though doing so might make future consolidations more straightforward in practice.

The overall presentation requirements sit in IAS 1 (Presentation of Financial Statements), which mandates that certain key items — such as revenue and income tax expense — must appear on the face of the statement of profit or loss and other comprehensive income.

Beyond these mandated items, IAS 1 requires only that additional line items be presented in whatever manner best supports understanding of the entity's financial performance. In particular, operating expenses may be classified by either their nature or their function, whichever produces more reliable and relevant information for that specific entity.

Since Ayman and Mrehan can each validly choose the classification approach that best suits their own circumstances, it is entirely possible — and fully compliant with IFRS Standards — for their detailed expense line items to differ substantially even while both satisfy IAS 1's requirements.

On the allocation question: IAS 1 requires all income and expense items to be presented within profit or loss, unless another IFRS Standard specifically requires or permits otherwise — so there is no free choice, and no clean theoretical dividing line between 'profit or loss items' and 'other comprehensive income items' as separate categories in their own right.

That said, a practical pattern does emerge: gains are more often routed to other comprehensive income than losses are (revaluation gains on property, plant and equipment typically go to OCI, for instance, while revaluation losses typically hit profit or loss instead).

Why this matters for performance assessment: only amounts recognised in profit or loss feed into earnings per share, a key performance indicator listed entities must disclose. Anything parked in other comprehensive income sits outside that calculation entirely.

IAS 41 (Agriculture) covers exactly this situation. Agricultural activity means managing the biological transformation and harvest of biological assets, either for sale or for conversion into produce or further biological assets. A biological asset is a living plant or animal — cattle and sheep qualify directly. Agricultural produce is what's harvested from those assets — meat and milk both qualify. Much of this subsidiary's asset base therefore falls squarely within IAS 41.

Biological assets are measured at fair value less costs to sell, both on initial recognition and at every subsequent year end. For purchased cattle or sheep, a reliable market-based fair value is straightforward to establish. Newly born animals follow exactly the same principle — they are recognised immediately at fair value less costs to sell, with the corresponding gain recognised in profit or loss at birth, even though no cash changed hands to acquire them.

IAS 41 does permit a cost-model fallback where fair value cannot be reliably measured, but this is unlikely to apply to cattle or sheep, given how readily market values are typically available for livestock.

Agricultural produce, meanwhile, is measured at fair value less costs to sell specifically at the point of harvest — defined as either detachment from the biological asset (milking a cow) or the end of the biological asset's life (slaughtering an animal for meat). Recognising the produce at that point typically triggers an equivalent gain in profit or loss. From then on, however, the produce moves out of IAS 41 and into IAS 2 (Inventories), with any further profit or loss recognised only when it is actually sold.

Other assets belonging to this subsidiary — farmland, machinery, trade receivables, and so on — continue to be measured under whichever IFRS Standard would normally apply to assets of that type.

IAS 10 (Events after the Reporting Period) governs all three situations. It defines an event after the reporting date as one occurring between the year end and the date the financial statements are authorised for issue, and splits such events into adjusting and non-adjusting categories.

An adjusting event provides additional evidence of conditions that already existed at the year end. The legal settlement fits this description precisely: the unfair dismissal itself occurred on 31 December 20X4, well before the year end, so the October settlement simply confirms the final amount of a liability that already existed at 30 September 20X5. IAS 10 requires adjusting events to be reflected in the financial statements, so we recognise a $560,000 liability at 30 September 20X5 and a corresponding $560,000 expense for the year, along with any additional disclosure that would help users.

Non-adjusting events, by contrast, relate to conditions arising only after the year end, and are disclosed in the notes (if material) rather than recognised in the figures themselves. The factory fire fits here — nothing about it existed at 30 September 20X5. The only circumstance that would override this non-recognition rule is a threat to going concern, which does not apply since the subsidiary can fund the repairs itself.

The competitor's product launch, on 10 November 20X5, falls after the 31 October 20X5 authorisation date entirely, so it does not qualify as an event after the reporting period for these financial statements at all. Its effect, if any, will instead be reflected in the year ending 30 September 20X6.

Since this purchase is denominated in a foreign currency, it is a foreign currency transaction under IAS 21 (The Effects of Changes in Foreign Exchange Rates), which requires initial recognition at the exchange rate prevailing on the transaction date. Here, that means recording both inventory and a payable of $140,000 (840,000 ÷ 6).

The payable was settled on 31 August 20X5, by which point the rate had moved to 7, meaning only $120,000 (840,000 ÷ 7) of cash was actually needed to clear it. The difference — an exchange gain of $20,000 ($140,000 less $120,000) — is recognised in profit or loss.

The inventory itself, however, is a non-monetary item once recorded at cost, so it is not retranslated at the year end; it remains at $140,000.

IAS 2 (Inventories) then requires inventory to be measured at the lower of cost and net realisable value. Net realisable value here is $125,000 (the $1 million expected sale proceeds ÷ the closing rate of 8, since NRV is inherently a monetary measure and must use the year-end rate). Because $125,000 is lower than the $140,000 cost, the inventory is written down to $125,000, with a further loss of $15,000 ($140,000 less $125,000) recognised in profit or loss for the year ended 30 September 20X5.

Rewan must be disclosed because it qualifies as a related party of Ayman under IAS 24 (Related Party Disclosures). A director of an entity is automatically part of that entity's key management personnel, and key management personnel are automatically related parties — so Khalifa's MD, being an Ayman director too, is a related party of Ayman. IAS 24 also treats close family members of related parties as related parties in their own right, bringing the MD's spouse within scope. Since Rewan is controlled by that spouse, Rewan itself becomes a related party of Ayman by extension.

The required disclosures for Rewan would cover the nature of the relationship, the value of transactions during the period, and any outstanding balances (most likely payables) at the year end. Related party materiality is judged on qualitative grounds as much as quantitative ones, which is exactly why the comparatively small Rewan transactions still warrant disclosure — users need to be able to assess the significance of the relationship itself, not just the dollar amounts involved.

Dixon, by contrast, is not a related party at all under IAS 24, however large the transaction values — so disclosure there would only be needed if considered otherwise relevant to understanding the consolidated financial statements as a whole.

Ekramy is not a subsidiary of Ayman. Under IFRS 10 (Consolidated Financial Statements), a subsidiary is an entity the investor controls — and a 35% stake with the ability to appoint only two of six directors does not give Ayman control over Ekramy.

That combination of shareholding and board representation does, however, point toward significant influence rather than control. Under IAS 28 (Investments in Associates and Joint Ventures), Ekramy is therefore treated as an associate of Ayman — consistent with IAS 28's rebuttable presumption that a 20%-or-greater equity stake confers significant influence.

Since Ayman prepares consolidated financial statements, IAS 28 requires the investment in Ekramy to be accounted for using the equity method: initially recorded at cost, then adjusted each period for Ayman's share of Ekramy's post-acquisition change in net assets, with that adjustment flowing through profit or loss or other comprehensive income as appropriate. Any profits arising from transactions between Ayman and Ekramy are eliminated to the extent of Ayman's ownership share, and the investment is written down if it becomes impaired.

The movement from $60 million to $63.5 million implies Ekramy's net assets have grown by roughly $10 million since acquisition, with Ayman's 35% share of that increase — $3.5 million — added to the original cost. This equity-accounted carrying amount is not designed to track the market value of the shares, which is instead driven by market forces independently of this calculation.

IFRS 10 (Consolidated Financial Statements) requires uniform accounting policies to be applied across all group entities when preparing consolidated financial statements. Where an individual group entity's own policies differ from the parent's, appropriate adjustments must be made when bringing its assets, liabilities, profits, and losses into the consolidated accounts — which is exactly what has happened with Ibrahim.

The likely explanation is that Ibrahim reports under the IFRS for SMEs Standard, while Mariam applies full IFRS Accounting Standards. Eligibility to use the SMEs Standard does not depend on an entity's size, but on whether it has public accountability. Entities without public accountability may choose — but are never required — to use the SMEs Standard instead of full IFRS, which likely explains why Ibrahim uses it while Mariam does not.

The SMEs Standard carries lighter disclosure requirements and simpler accounting treatments in several areas. One clear example: under the SMEs Standard, all research and development costs are expensed immediately, with no exceptions. Under full IFRS, development costs fall under IAS 38 (Intangible Assets), which requires capitalisation as an intangible asset once a project is separately identifiable, expenditure can be measured reliably, adequate resources exist to complete it, and future economic benefits are reasonably certain to exceed the capitalised cost. Research costs, by contrast, must always be expensed under IAS 38 too, since at the research stage there is no definite prospect of future benefit.

Requiring Ibrahim to adopt full IFRS Standards in its own future accounts could simplify the consolidation process going forward, by removing the need for this kind of adjustment altogether.

Whether fair value applies at all is determined by individual IFRS Accounting Standards, which collectively produce a mixed measurement model across different asset types — there's no single overarching rule.

The Standard governing how fair value is measured, once it applies, is IFRS 13 (Fair Value Measurement). IFRS 13 defines fair value as the amount that would be received to sell an asset in an orderly transaction between market participants — an exit price, not an entry price, with transaction costs excluded from the calculation entirely. For listed shares quoted with separate buy and sell prices, it is the sell price that is relevant to fair value.

Fair value should be based on observable market prices wherever possible. If an asset trades in more than one market, as can easily happen with listed shares, the relevant market is the principal one in which the asset is actually traded.

Where no direct market price exists — unlisted shares, for instance — IFRS 13 requires fair value to be estimated using an appropriate valuation technique. This might involve referencing the market price of a comparable listed entity's shares, adjusted for the target company's relative lack of marketability, or discounting projected future earnings at a suitable rate.

A property's fair value is established using IFRS 13's principles. In practice, this almost always means referencing recent open-market sale prices for comparable properties in the same location, reflecting the highest and best use the property could be put to (not necessarily its current use), since IFRS 13 requires fair value to reflect how market participants would actually value the asset.

Two separate Standards govern property recognition and measurement: IAS 40 (Investment Property) and IAS 16 (Property, Plant and Equipment). IAS 40 defines investment property as property held to earn rental income and/or capital appreciation — exactly matching the properties we rent out. IAS 40 permits either the cost model or the fair value model for investment property, and it appears Ayman has chosen the fair value model, under which investment properties are revalued every year with all gains and losses recognised in profit or loss.

Owner-occupied properties instead fall under IAS 16, which similarly permits either the cost model or the revaluation model for a given class of assets — so using fair value for these properties too is entirely consistent with IAS 16. Under the revaluation model, however, properties only need to be revalued regularly enough that their carrying amount doesn't materially diverge from fair value at each year end; this does not require annual revaluation, which explains the less frequent cycle you've observed. As for gains and losses: a revaluation surplus goes to other comprehensive income, unless it reverses a previous revaluation deficit on the same asset that had gone through profit or loss, in which case it is recognised in profit or loss instead (up to the amount of that original deficit). A revaluation deficit works the mirror-opposite way: it hits profit or loss unless reversing a previous surplus recognised in other comprehensive income on the same asset. This explains why the treatment sometimes flips between the two.

The difference comes down to how each subsidiary joined the group. Ekramy's assets, including any goodwill and its brand name, arose through internal development within the Ayman group — making them internally generated intangible assets. IAS 38 (Intangible Assets) prohibits recognising internally generated goodwill and brand names outright, except where they arise from a qualifying research and development project. That is why neither Ekramy's goodwill nor its brand name appears in the consolidated accounts.

Mrehan, by contrast, joined the group through a business combination, governed by IFRS 3 (Business Combinations). IFRS 3 requires the difference between the fair value of consideration paid and the fair value of net assets acquired to be recognised as goodwill, and requires the acquired entity's identifiable assets and liabilities to be separately recognised at fair value as at the acquisition date. Provided Mrehan's brand name can be reliably fair valued, it is recognised as an intangible asset for exactly this reason. Similarly, Mrehan's property, plant and equipment is carried in the consolidated accounts at its fair value on the acquisition date, whereas Ekramy's equivalent assets remain at their original historical cost to the group — almost certainly a lower figure, given how the two subsidiaries came to be part of Ayman.

IFRS 8 (Operating Segments) is the relevant Standard, requiring entities within its scope to disclose based on their own operating segments. Crucially, IFRS 8 only applies compulsorily to listed entities; unlisted entities may choose to disclose voluntarily, but if they do, must follow IFRS 8's requirements in full. This is almost certainly why Ekramy provides segmental disclosures (voluntarily) while Mrehan provides none at all.

An operating segment is a component of the business with discrete financial information available, whose results are regularly reviewed by the chief operating decision maker — the individual or group responsible for assessing performance and allocating resources. It appears Ayman manages performance geographically, while Ekramy does so by product type; each entity's segments simply follow its own internal management structure.

IFRS 8 does, however, impose some baseline disclosures on all applicable entities regardless of segment structure — typically revenue by geographical area and by product type, plus non-current assets by geographical area — though the geographical-area requirement can be dropped if obtaining that data would be excessively costly, provided that fact is itself disclosed. This may well account for some of the remaining differences between Ayman's and Ekramy's disclosures.

I. What counts as a financial asset? IAS 32 (Financial Instruments: Presentation) defines a financial asset broadly to include: cash itself; an equity instrument issued by another entity; a contractual right to receive cash (or another financial asset) from another party; or a contractual right to exchange financial instruments with another party under potentially favourable terms.

II. Is fair value the same as resale value? Not quite — fair value has a specific technical meaning under IFRS 13 (Fair Value Measurement): the price that would be received to sell the asset in an orderly transaction between market participants at the measurement date. It's a market-based concept, not simply 'whatever we could personally get for it'.

III. What does amortised cost mean? Under IFRS 9 (Financial Instruments), amortised cost starts from the asset's initial recognition amount, then adjusts over time for the cumulative effect of the effective interest method spreading any gap between that initial amount and the eventual maturity amount, further adjusted for any expected credit loss allowance. In effect, interest income is recognised at whatever constant rate exactly discounts the asset's expected future cash receipts back to its original carrying amount.

IV. Is there a real choice, and how is it made? Classification under IFRS 9 depends on two tests applied together: the business model under which the asset is held, and the nature of its contractual cash flows. A financial asset is measured at amortised cost only where (1) it is held within a business model whose objective is to collect the contractual cash flows, and (2) those contractual cash flows are solely payments of principal and interest on the amounts outstanding. Where the business model instead aims both to collect contractual cash flows and to sell the asset — with the same 'solely principal and interest' cash flow test still satisfied — the asset is measured at fair value through other comprehensive income instead. Anything falling outside both these categories defaults to fair value through profit or loss.

V. Where fair value applies, how is profit-or-loss versus OCI decided? For an equity instrument not held for trading, an entity may make an irrevocable election at initial recognition to present fair value changes through other comprehensive income instead of profit or loss. Any equity instrument without this election defaults to fair value through profit or loss. Separately, IFRS 9 also allows an irrevocable election, at initial recognition, to designate any financial asset at fair value through profit or loss where doing so removes or significantly reduces a measurement or recognition inconsistency that would otherwise arise.

I. Timing of revenue recognition. IFRS 15 (Revenue from Contracts with Customers) governs this. Contracts with customers create performance obligations, and the general principle is that revenue is recognised as each performance obligation is satisfied — either at a single point in time or over a period, depending on the obligation's nature. Construction contracts typically satisfy their performance obligation over time, so revenue should likewise be recognised progressively as construction proceeds, not deferred until completion.

II. Cost recognition. IFRS 15 does not mandate one specific method for measuring progress toward completion of an over-time performance obligation, but it does describe acceptable approaches, broadly grouped as output methods (based on the proportion of contract value delivered) or input methods (based on the proportion of expected total costs incurred). Whichever method is chosen must then be applied consistently to similar contracts. Where the relevant criteria are met, the direct costs of fulfilling the contract's performance obligations should first be recognised as an asset, then amortised to cost of sales in a pattern consistent with how revenue is being recognised — not simply expensed as incurred.

III. Loss-making contracts. Where expected future costs exceed expected future revenue on a contract, an impairment loss equal to that shortfall is recognised immediately in profit or loss. Such a contract is treated as onerous under IAS 37 (Provisions, Contingent Liabilities and Contingent Assets), which requires recognition of the future net cost of fulfilling it.

IV. Variable consideration. IFRS 15 recognises that many contracts combine fixed and variable elements, meaning the final receivable amount may genuinely be unknown at the outset. Rather than waiting for certainty, IFRS 15 permits estimating variable consideration using either the expected value method (probability-weighted) or the most likely amount method, whichever better predicts the amount the entity will be entitled to — applied consistently for the life of the contract.

(i) Relevant Standard and scope. IFRS 6 (Exploration for and Evaluation of Mineral Resources) addresses exactly this. It applies specifically to expenditure incurred after legal rights to explore a defined area have been obtained, but before the technical feasibility and commercial viability of extracting the mineral resource have been demonstrated. Examples given in IFRS 6 include the acquisition of exploration rights and the cost of exploratory drilling, though the list is not exhaustive.

(ii) Asset versus expense. IFRS 6 does not mandate a single approach; instead, it allows each entity to develop its own accounting policy specifying which categories of exploration and evaluation expenditure are treated as assets versus expenses, provided that policy is then applied consistently.

(iii) Subsequent classification and measurement. Recognised exploration and evaluation assets are classified as tangible or intangible depending on their nature, initially measured at cost, and subsequently measured under either the cost model or the revaluation model.

(iv) Interaction with research and development requirements. IAS 38 (Intangible Assets) governs research and development costs generally, requiring research costs to be expensed but permitting development costs meeting specific criteria to be capitalised. Exploration and evaluation expenditure under IFRS 6 could reasonably be seen as analogous to 'research' costs, which is consistent with IFRS 6 leaving the accounting policy choice to each entity rather than mandating capitalisation. Once a specific exploration and evaluation project demonstrates technical feasibility and commercial viability, any assets already recognised are reassessed for reclassification under IAS 38 or IAS 16 (Property, Plant and Equipment), after first being tested for impairment.

Both arrangements fall under IFRS 11 (Joint Arrangements), since both display joint control — the contractually agreed sharing of control that exists only where decisions about relevant activities require unanimous consent among the controlling parties, as is the case here for both arrangements. IFRS 11 distinguishes two types of joint arrangement: a joint operation and a joint venture, with the distinction turning on whether the investors have direct rights to the arrangement's individual assets and obligations for its individual liabilities, or instead simply hold a right to the arrangement's overall net assets.

Where a joint arrangement exists mainly to help investors operate their own existing businesses more efficiently, the investors typically retain direct rights and obligations over its specific assets and liabilities — making it a joint operation. This describes Arrangement 1: since the invested cash funds specific vehicles and their operating costs, each investor recognises its own share of those vehicles as property, plant and equipment, together with its share of the running costs as expenses, directly in its own financial statements.

Where a joint arrangement instead runs an essentially separate business of its own, distinct from what the investors do individually, it is typically a joint venture. This describes Arrangement 2, given its distinct new product line and its own external financing. Joint venture investments are measured as a single line item using the equity method — the investor's share of the investee's net assets at each reporting date — meaning each investor's share of the entity's post-acquisition profits flows through profit or loss over the life of the investment, rather than each investor separately recognising individual assets and liabilities.

(i) Relevant Standard and scope. IAS 41 (Agriculture) covers agricultural activity specifically, rather than a farming business's financial statements as a whole — other assets, such as property, plant and equipment, remain governed by the Standards that would normally apply (IAS 16, in that case). IAS 41 introduces the concept of a biological asset — a living plant or animal — which covers both the dairy cow herd and the sheep herd.

(ii) Recognition, measurement, and presentation. A biological asset is recognised once control is established — for Mrehan, when cattle or sheep are purchased, or born and appropriately marked as belonging to the herd. Biological assets are measured at fair value less costs to sell both on initial recognition and at every subsequent reporting date, with changes in that fair value recognised in profit or loss. IAS 1 (Presentation of Financial Statements) further requires biological assets to be shown as their own separate category on the statement of financial position.

(iii) Measuring harvested produce. IAS 41 defines agricultural produce as the harvested output of biological assets — milk from the dairy herd and meat from the sheep herd both qualify. Agricultural produce is measured, at the point of harvest, at fair value less costs to sell; this becomes the produce's initial 'cost' once it is reclassified as inventory and brought within the scope of IAS 2 (Inventories) from that point onward.

Operating segment versus reportable segment. IFRS 8's core principle is that an entity should disclose enough information for users to understand the types of business activity it engages in and the economic environments it operates within. An operating segment is a component of the entity that engages in activities generating revenue and expense (including from transactions with other parts of the same entity), whose operating results are regularly reviewed by the chief operating decision maker (CODM) for resource-allocation and performance-assessment purposes, and for which discrete financial information is available. Even a component that sells almost exclusively to other segments within the same entity can qualify as an operating segment if that's how the entity is actually managed.

A reportable segment, by contrast, is simply any operating segment that clears at least one of three quantitative thresholds: (1) its reported revenue — external plus intersegment — is 10% or more of all segments' combined revenue; (2) its reported profit or loss, in absolute terms, is 10% or more of the greater of the combined profits of all profitable segments or the combined losses of all loss-making segments; or (3) its assets are 10% or more of all segments' combined assets. If reportable segments in total capture less than 75% of the entity's total external revenue, additional segments must be added as reportable until that 75% threshold is reached.

Chief operating decision maker. IFRS 8 identifies operating segments based on internal reports reviewed by whoever allocates resources and assesses performance — and this role is a function, not a specific individual, so it may be performed collectively by a group such as the executive board. Since she is a board member and the board as a whole reviews segment performance and allocates resources, she would indeed be considered part of the chief operating decision maker function, collectively with the rest of the board.

Which segments are reportable.

Americas clears the 10% revenue threshold (71.1%) on its own, so it is reportable — only one threshold needs to be met. Asia Pacific misses the revenue test but clears the 10% profit threshold (17.9%), making it reportable too. Australia and Europe individually clear none of the three thresholds. However, Americas and Asia Pacific together capture only $2,325,000 ($2,010,000 + $315,000) of external revenue — 73.9% of the $3,145,000 total — short of the 75% requirement, so at least one further segment must be added as reportable. Either Australia or Europe would suffice to clear 75% if included. Whichever segment remains unreported would then be shown within an 'all other segments' category, to reconcile back to the total financial statement figures.

Scope and objectives of IFRS S2. IFRS S2's objective is for an entity to disclose information about its climate-related risks and opportunities that is useful to the primary users of general purpose financial reports when making resource-provision decisions — specifically, risks and opportunities that could reasonably be expected to affect the entity's prospects. IFRS S2 requires disclosure of both the climate-related risks an entity faces and the climate-related opportunities available to it. These risks split into physical risks (driven by specific climate events or long-term shifts in climate patterns) and transition risks (arising from the broader move toward a lower-carbon economy). Risks and opportunities unlikely to affect the entity's prospects fall outside the Standard's scope entirely.

Usefulness to external users. These disclosures let users understand the governance structure an entity uses to monitor, manage, and oversee climate-related risks and opportunities, along with the strategy adopted to manage them and how they're integrated into the entity's broader risk management processes. Disclosed metrics and targets further let users assess an entity's actual performance against its climate-related goals, whether those targets are self-imposed or set by law or regulation.

Impact of the errors and comparatives. Under IAS 8 (Accounting Policies, Changes in Accounting Estimates and Errors), a material prior period error must be corrected retrospectively — restating the figures as though the error had never happened, unless doing so is impracticable, in which case a prospective adjustment is made instead. For the inventory error: closing inventory at 31 March 20X4 was overstated by $300,000, meaning cost of sales for that year was understated and profit overstated by the same amount. That overstated closing inventory becomes 20X5's overstated opening inventory, meaning 20X5's cost of sales is now overstated and its profit understated. Since IAS 1 (Presentation of Financial Statements) requires comparative figures, both the 20X4 and 20X5 figures presented within the 20X5 financial statements must be restated, with the correction ultimately adjusting the carried-forward retained earnings at the end of 20X4.

The missing depreciation on the building is likewise a prior period error requiring retrospective correction: all comparative amounts affected must be restated, with the depreciation that should have been charged in the prior year adjusted directly against opening retained earnings for 20X5 — it does not affect the current year's profit or loss at all.

Comparison to the change in useful life. A change in an asset's estimated depreciation pattern is a change in accounting estimate, not an error, since it reflects new information and genuine measurement uncertainty rather than a mistake, and IAS 8 confirms that reasonable estimates don't undermine financial statement reliability. Changes in accounting estimate are applied prospectively only, from the date of change onward, with no restatement of opening balances required — only disclosure of the nature and amount of the change affecting the current year.

IAS 10 (Events after the Reporting Period) governs both situations, since neither set of financial statements has yet been authorised for issue. IAS 10 splits post-year-end events into adjusting and non-adjusting categories.

Adjusting events provide additional evidence about conditions that already existed at the reporting date, and require the financial statements themselves to be adjusted. The customer's formal insolvency declaration on 7 July 20X9 almost certainly reflects a financial position that already existed at 30 June 20X9 — reinforced by the fact we already knew of the customer's difficulties before the year end — so recognising the $6 million impairment loss in the 30 June 20X9 financial statements is entirely correct; the insolvency simply confirms conditions that already existed.

Non-adjusting events relate solely to new conditions arising after the year end, and are disclosed in the notes (where material) rather than reflected in the figures themselves. The factory fire fits this description precisely — the factory was undamaged as at 30 June 20X9 — so no adjustment to the financial statements is required, only disclosure. The sole exception that would override this treatment is a threat to going concern, which does not apply here.

IAS 37 (Provisions, Contingent Liabilities and Contingent Assets) governs all of this. A provision is recognised where a present obligation exists from a past event, an outflow of economic benefit to settle it is probable, and the amount can be reliably estimated.

1. Customer A's claim satisfies all three conditions: the supply occurred before 30 June 20X9, success is probable at 60%, and the likely damages are quantifiable — so a provision is required. Employee B's claim fails the probability test at only 25%, so no provision is appropriate. Where a single obligation like this is being measured, IAS 37's 'best estimate' is normally the single most likely outcome — not a probability-weighted average across multiple possible outcomes (that expected-value approach is reserved for large populations of similar items). The most likely outcome for Customer A is the full $2 million, which is why that figure — not $1.45 million — is the correct provision, shown as a current liability. Employee B's claim, with only a possible (not probable) outflow, is instead a contingent liability: not recognised in the statement of financial position, but disclosed in the notes along with its potential financial impact and likelihood.

2(a). IAS 37 does not require a legal obligation specifically — a constructive obligation, created by an established pattern of past practice that generates a valid expectation the entity will act, is equally sufficient. Our consistent history of restoring previous extraction sites creates exactly this kind of constructive obligation for the new site.

2(b). Where the time value of money is material, IAS 37 requires the provision to be measured at the present value of the expected future expenditure. Here, that means discounting the $20 million payable in ten years' time back to its present value using the 5% rate (via the 0.614 discount factor), producing the $12.28 million figure.

2(c). Since this provision relates to the estimated future cost of restoring the site on which the related asset sits, IAS 16 (Property, Plant and Equipment) requires the corresponding debit to be capitalised as part of that asset's initial cost, rather than being expensed to profit or loss immediately.

(a) Differing treatments. IFRS Accounting Standards do generally require capitalisation of borrowing costs directly attributable to constructing a qualifying asset — IAS 23 (Borrowing Costs) is explicit on this. However, the IASB has also issued a separate, standalone IFRS for SMEs Standard, available as an alternative to full IFRS for entities without public accountability. Given Ekramy's size and unlisted status, it likely qualifies to use this simplified framework. One key difference between the two frameworks is that the IFRS for SMEs Standard prohibits capitalising borrowing costs under any circumstances, requiring them to be expensed instead — meaning Ekramy's own individual financial statements are entirely correct on this point, just prepared under a different (and equally valid) framework from Ayman's.

(b) Why adjust on consolidation. IFRS 10 (Consolidated Financial Statements) requires uniform accounting policies to be applied across all group entities when preparing consolidated financial statements. Since Ekramy's individual accounts follow the IFRS for SMEs Standard while Ayman's group reporting follows full IFRS Accounting Standards, an adjustment is necessary purely to align Ekramy's figures with the group's full-IFRS policies for consolidation purposes — it does not mean Ekramy's own accounts were prepared incorrectly.