Chart-of-accounts mapping

A ledger usually has far more accounts than the financial statements have lines. Juniper's ledger has 340 accounts; its balance sheet has about fifteen lines. The link between them is a mapping: a table assigning every account to exactly one reporting line. The same idea maps a subsidiary's local chart to a group reporting chart, or a ledger to a tax return or a lender's covenant schedule.

How to map well - Every account maps to exactly one line. An account mapped twice double-counts; an unmapped account vanishes from the statements. - Contra accounts map with their partner. The allowance for credit losses goes to the receivables line (as a deduction); accumulated depreciation goes to property, plant and equipment. They don't get lines of their own. - Map by meaning, not by name or number range. A rule such as "all 6xxxx accounts → operating expenses" is quick, but the day someone opens an interest account in the 6xxxx range, finance costs are misstated without any warning. Ranges are acceptable only if new accounts are reviewed before use. - Watch accounts that can change sign. A bank account that's overdrawn at month end is a liability, not cash. A customer account with a credit balance (an overpayment) is a payable. The mapping needs either a rule based on the sign of the balance or a review of these accounts every period. - Names can mislead. "Customer deposits" sounds like receivables but is money received in advance — a contract liability. "Supplier advances" sounds like payables but is a prepayment, an asset.

Testing the mapping (every period, not just when it's built) 1. Unmapped report: list accounts with a balance or activity that have no mapping. It must be empty. 2. Totals tie: the mapped lines add back to the trial balance — in signed terms, the whole mapped TB sums to zero. 3. Statements balance: total assets equal total liabilities plus equity (with current-year profit included). 4. Reasonableness: compare each line with the prior period and investigate unexpected moves, which often reveal a mapping change rather than a business change. 5. Change control: new accounts and mapping changes are approved and logged, because a mapping error repeats every month.

Presentation requirements change too: when IFRS 18 replaces IAS 1 for annual periods beginning on or after 1 January 2027, income and expenses must be classified into new categories (operating, investing, financing), so most companies' mappings will need rework.