IFRS for SMEs is designed to give eligible small and medium-sized entities a reporting framework that is easier to apply than full IFRS while still producing useful, comparable financial information. It is not “IFRS-lite” in the sense of being informal. The entity still needs a reporting basis, accounting policies, supporting records, estimates, disclosures, and review evidence.

The first question for an East African business is therefore not “Which template should we use?” It is “Which framework applies to this entity, period, lender, donor, regulator, and group?” The IFRS Foundation’s standard page is the authority for the current standard. Local law, regulator requirements, donor conditions, and financing covenants may require a different basis or additional reporting.

Confirm eligibility and the effective edition

Document why the business qualifies for IFRS for SMEs and whether it has public accountability or another reason to use full IFRS. Record the reporting period, the edition applied, and the date on which changes become effective. The IFRS Foundation’s 2025 update materials describe a major third edition; the official update notice should be checked for adoption planning rather than copied into a policy without review.

If an entity is part of a larger group, ask whether the parent requires full IFRS reporting for consolidation. A subsidiary’s local reporting basis and the group’s consolidation adjustments are related decisions, but they are not automatically the same book.

Know the practical differences

The framework choice affects system configuration and monthly work. Examples include:

  • Leases: IFRS for SMEs retains a distinction between operating and finance leases, unlike the general lessee model in IFRS 16. Capture the contract, classification rationale, payments, and review dates.
  • Borrowing costs: IFRS for SMEs generally expenses borrowing costs, whereas full IFRS may require capitalisation for qualifying assets. Do not let a full-IFRS template silently change the SME treatment.
  • Goodwill and intangibles: IFRS for SMEs includes amortisation and simpler impairment patterns in areas where full IFRS differs. The useful life, residual value, and impairment evidence still need support.
  • Financial instruments: the simplified basic-instrument and other-instrument model requires classification and impairment evidence; it is not permission to ignore receivable ageing or credit risk.
  • Revenue: straightforward sales may look similar across frameworks, while complex arrangements require the selected framework’s specific requirements and documentation.
  • Agriculture: Section 34 addresses biological assets and agricultural produce. The IFRS for SMEs supporting modules should be used for the applicable facts, measurement, and disclosures.

These differences are why a finance system should store the entity’s reporting basis and policy choices instead of assuming one global rule.

Turn the standard into a close routine

At the start of the year, maintain a reporting-basis memo, chart-of-accounts mapping, accounting-policy register, asset and lease registers, customer and supplier ageing, inventory count plan, tax reconciliation, and disclosure checklist. During the month, retain source documents and approval evidence. At close, reconcile subledgers to control accounts, review estimates and provisions, investigate unusual movements, and lock the period after approval.

The records should let a reviewer trace a reported amount back to its source. For example, inventory should connect to receipts, issues, transfers, counts, adjustments, and cost-flow policy. A receivable should connect to the invoice, payment history, ageing, and any impairment assessment. A lease should connect to the contract and the treatment selected under the reporting basis.

Avoid five common mistakes

  1. Calling a company an SME without documenting the eligibility decision.
  2. Mixing full-IFRS and IFRS-for-SMEs treatments in one reporting period without a policy decision and adjustment record.
  3. Treating tax returns as a substitute for general-purpose financial statements.
  4. Posting manual year-end adjustments without a source, reviewer, or reversal plan.
  5. Using a software default without checking the relevant section and the entity’s policy.

The ICPAU resource is a useful local professional reference point, but it does not replace the current IFRS Foundation material or the business’s own professional review.

What the ERP should preserve

A finance platform should make the policy visible. At minimum, it should retain the entity and reporting basis, period status, accounting-policy references, dimensions, supporting documents, approval trail, source-to-report links, and controlled adjustment history. It should support a reviewer asking “why is this amount here?” without rebuilding the answer from personal spreadsheets.

Kraal Code’s finance direction is aligned with the practical needs of African SMEs: a shared record across finance, inventory, sales, procurement, and operations, with audit-friendly evidence. The framework selection, accounting policies, statutory overlays, and final financial statements remain the responsibility of the entity and its qualified advisers.

Section 34 and agricultural records

Agribusinesses often have several records that should not be collapsed into one generic stock number: land or production activity, biological assets, harvested produce, inputs, processing, storage, sales, and cash collection. The applicable accounting treatment depends on the facts and the reporting basis. A system should preserve the source event, measurement date, quantity, location, responsible person, and supporting evidence so the finance team can apply the selected policy and explain changes.

This is particularly important when physical activity and financial reporting use different calendars. A harvest count, warehouse receipt, sale, and cash settlement may happen on different dates. Good cut-off evidence is more useful than a late spreadsheet adjustment whose source has disappeared.

Receivables, inventory, and estimates

Three monthly reviews deserve attention:

  • Receivables: reconcile invoices and receipts, review ageing, document credit-risk judgements, and identify disputes rather than hiding them in an unexplained balance.
  • Inventory: reconcile receipts, issues, transfers, counts, returns, and the selected cost-flow method. Investigate negative or unusual balances before the close is approved.
  • Estimates and provisions: record the basis, data used, reviewer, period, and subsequent outcome. An estimate is not made reliable by placing it in a separate spreadsheet.

The system should distinguish source transaction, accounting entry, tax amount, and management classification. It should also keep posted history immutable and use linked correction or reversal entries where the policy requires an adjustment.

Prepare a framework decision memo

The memo can be short, but it should answer:

  1. Which entity and reporting period are covered?
  2. Why is IFRS for SMEs appropriate, and are there public-accountability or group-reporting exceptions?
  3. Which edition and effective dates apply?
  4. Which policies require a documented choice or estimate?
  5. Which local statutory, tax, donor, lender, or regulator overlays apply?
  6. Who reviewed the decision and when will it be revisited?

Store that memo with the chart-of-accounts mapping, disclosure checklist, registers, reconciliations, and close evidence. Kraal Code’s accounting capability, reporting capability, and security guidance describe the kinds of system evidence a reviewer should expect; they do not certify the entity’s accounts.

A practical close test

Select one balance from the draft financial statements and trace it backwards: report line, ledger account, subledger, source transaction, supporting document, approval, and reviewer. Then trace one correction forward into the next report. If the chain breaks at a personal workbook or an undocumented adjustment, the organisation has a process gap to fix before presenting the result as final.

Section 34 and agricultural records

Agribusinesses often have several records that should not be collapsed into one generic stock number: land or production activity, biological assets, harvested produce, inputs, processing, storage, sales, and cash collection. The applicable accounting treatment depends on the facts and the reporting basis. A system should preserve the source event, measurement date, quantity, location, responsible person, and supporting evidence so the finance team can apply the selected policy and explain changes.

This is particularly important when physical activity and financial reporting use different calendars. A harvest count, warehouse receipt, sale, and cash settlement may happen on different dates. Good cut-off evidence is more useful than a late spreadsheet adjustment whose source has disappeared.

Receivables, inventory, and estimates

Three monthly reviews deserve attention:

  • Receivables: reconcile invoices and receipts, review ageing, document credit-risk judgements, and identify disputes rather than hiding them in an unexplained balance.
  • Inventory: reconcile receipts, issues, transfers, counts, returns, and the selected cost-flow method. Investigate negative or unusual balances before the close is approved.
  • Estimates and provisions: record the basis, data used, reviewer, period, and subsequent outcome. An estimate is not made reliable by placing it in a separate spreadsheet.

A framework decision memo in practice

The memo can be short, but it should answer:

  1. Which entity and reporting period are covered?
  2. Why is IFRS for SMEs appropriate, and are there public-accountability or group-reporting exceptions?
  3. Which edition and effective dates apply?
  4. Which policies require a documented choice or estimate?
  5. Which local statutory, tax, donor, lender, or regulator overlays apply?
  6. Who reviewed the decision and when will it be revisited?

Store the memo with the chart-of-accounts mapping, disclosure checklist, registers, reconciliations, and close evidence. Kraal Code’s accounting capability, reporting capability, and security guidance describe the kinds of system evidence a reviewer should expect; they do not certify the entity’s accounts.

A practical review test

Select one balance from the draft financial statements and trace it backwards: report line, ledger account, subledger, source transaction, supporting document, approval, and reviewer. Then trace one correction forward into the next report. If the chain breaks at a personal workbook or an undocumented adjustment, the organisation has a process gap to fix before presenting the result as final. For a plain-language introduction to Kraal Code’s finance workflow, start with the accounting capability and reporting capability pages.

Do not confuse system readiness with compliance

A system can enforce a posting workflow, retain an audit trail, and produce a useful report while the entity still has an unresolved policy or statutory question. Conversely, a technically correct policy can fail in practice if the source documents, approvals, counts, and reconciliations are not retained. The release decision therefore needs both: a framework memo reviewed by the right professional and observable evidence that the monthly process follows it.

Schedule a policy refresh when the entity changes its activities, adds a country, enters a new financing arrangement, acquires another business, changes reporting requirements, or adopts a new edition of the standard. Record the trigger and the reviewer in the finance governance calendar.