Building an IFRS-Aligned Chart of Accounts for Ethiopian SMEs

Why the chart of accounts is the most important decision

The chart of accounts (CoA) is the spine of every accounting system. It determines what financial statements look like, what management reports can be produced, what an auditor sees on the trial balance, and how easily the business can scale into new branches, products or jurisdictions. A weak CoA constrains the business for years; a thoughtful one supports growth without rework.

Many Ethiopian SMEs inherit their CoA from their legacy accounting tool — Peachtree, QuickBooks, Sage — or from a spreadsheet template handed down through accountants. These CoAs typically work for basic bookkeeping but show their limits when audits expect IFRS for SMEs presentation, when management wants multi-dimensional reporting, or when the business adds branches or product lines.

This guide is opinionated. It describes how NYLOS Finance & Accounting structures CoAs for Ethiopian SMEs aligned to IFRS for SMEs, and the practical patterns we apply during migration.

The five top-level account classes

Standard IFRS for SMEs presentation uses five top-level classes:

1. Assets — what the business owns or controls.
2. Liabilities — what the business owes.
3. Equity — the owners' residual claim.
4. Income — revenue and other gains.
5. Expenses — costs of operation.

Within each class, the IFRS for SMEs Section 4 (Balance Sheet) and Section 5 (P&L) presentations specify the line items expected. A well-designed CoA aligns its account numbering to these expected presentations so the financial statements come out clean without restructuring.

The Ethiopian context

Several Ethiopian-specific accounts need explicit dedicated treatment:

• VAT control accounts — input VAT receivable, output VAT payable, VAT clearing.
• Withholding tax payable — by transaction class if needed.
• Pension payable — employee and employer split.
• Cost-sharing payable — for applicable employees.
• Income tax payable.
• Foreign-currency revaluation accounts — for unrealized FX.
• MOR refund receivable — when over-paid.
• Cost-sharing receivable from employees — when applicable.

These accounts are non-negotiable. Generic CoAs imported from foreign tools typically lack them and create reconciliation pain.

Numbering convention

A common convention for Ethiopian CoAs that works well with NYLOS:

• 1xxxx — Assets
• 2xxxx — Liabilities
• 3xxxx — Equity
• 4xxxx — Revenue
• 5xxxx — Cost of sales
• 6xxxx — Operating expenses
• 7xxxx — Other income
• 8xxxx — Other expenses
• 9xxxx — Tax expense

Within each class, sub-classification by activity (current vs non-current, operating vs financing) is built into the second digit. The remaining three digits leave room for industry-specific or product-specific accounts.

This is a starting framework; every business adapts it to their needs. The discipline is to think about adapting once, deeply, before importing thousands of transactions.

Industry overlays

NYLOS ships CoA templates with industry-specific overlays:

• Manufacturing — WIP inventory, raw materials, finished goods, production cost categories, variance accounts.
• Microfinance — loan portfolio classification, provisions for loan losses, interest income breakdown by product.
• Real estate — property assets, accumulated depreciation per building, deferred income from advance rent.
• NGOs & donor-funded — restricted vs unrestricted funds, project-specific tracking, donor-by-donor receivable.
• Trading & wholesale — inventory by category, cost of sales by product line, margin analysis accounts.
• Hospitality — F&B revenue subcategorization, rooms revenue, amenity income, departmental expenses.

The overlay is a starting structure, not a constraint. Every business customizes from there.

Dimensions vs accounts

A common mistake is to encode dimensions (branch, project, department, donor) into the account number — for example, "Salaries — Addis branch" as a separate account from "Salaries — Hawassa branch". This works at small scale but explodes when more dimensions or values appear.

The better practice: one Salaries account with branch as a dimension on each transaction. NYLOS supports up to five configurable dimensions per transaction. Reports — P&L, Balance Sheet — slice by dimension without exploding the CoA.

This separation keeps the CoA stable as the business grows. Adding a new branch adds a dimension value, not a hundred new accounts.

Sub-ledger control accounts

Customer receivable, supplier payable, and inventory each have a control account in the GL plus a detailed sub-ledger. The control account balance must always equal the sub-ledger sum. A well-designed CoA:

• Names control accounts clearly (Accounts Receivable Control, Accounts Payable Control, Inventory Control).
• Restricts direct journal entry to control accounts — postings must flow through sub-ledger transactions.
• Reconciles control to sub-ledger automatically at every period close.

NYLOS enforces this at the platform level: control accounts cannot be debited or credited by direct journal entry, only by sub-ledger workflow.

Migration considerations

When migrating from Peachtree, QuickBooks or Sage:

1. Don't lift-and-shift the legacy CoA — use migration as the opportunity to align to IFRS for SMEs.
2. Map old accounts to new accounts explicitly — preserve mapping documentation for audit.
3. Bring opening balances to the new CoA — not historical transactions unless specifically needed.
4. Run parallel for one cycle — validate that new CoA produces correct period-end results.

NYLOS implementation engineers walk customers through this redesign. Many Ethiopian SMEs use migration to NYLOS as the moment to clean up a CoA they've outgrown.

What audit firms expect

The major Ethiopian audit firms (EY, KPMG, PwC, BDO, Deloitte) expect to see:

1. IFRS for SMEs-aligned presentation in the financial statements.
2. Clear control accounts with sub-ledger reconciliations.
3. Distinct accounts for Ethiopian-specific items (VAT, withholding, pension).
4. Multi-dimensional reporting capability for analytical procedures.
5. A documented CoA structure that the audit team can follow.

A CoA that ticks these five boxes makes the annual audit a routine matter rather than a fire drill.

Read more

• [NYLOS Finance & Accounting](/modules/finance-and-accounting) — the platform implementation.
• [MOR-Compliant Invoicing in Ethiopia](/blog/mor-compliant-invoicing-ethiopia).
• [Bank Reconciliation Automation in Ethiopia](/blog/bank-reconciliation-ethiopia-automation).
• [NYLOS Compliance posture](/security/compliance).