Scaling a Saudi Bookkeeping Practice: Standard Chart of Accounts Across Many Clients

The scaling problem appears when every new client arrives with a different numbering scheme, ambiguous account names and inherited posting habits. Reviewers then relearn the ledger each month, automation rules cannot travel between clients and management reporting becomes a manual translation exercise. A governed standard chart solves that problem only when it separates common meaning from client-specific operations. The practice owns the reporting taxonomy, mapping rules and quality tests; each client retains the detail its business, contracts and statutory records require. This makes standardisation an operating control rather than a cosmetic renumbering exercise.

A standard chart is a reporting language, not one rigid ledger

An accounting practice receives trial balances from four Saudi companies. The team copies them into a group spreadsheet, posts manual eliminations and adjusts totals until the balance sheet agrees. Next month it repeats the copy. Nobody can trace a group number to the source voucher without opening several files.

That is double entry in the operational sense: entity transactions are accounted for once, then reconstructed manually in a second uncontrolled environment.

A stronger model keeps every legal entity complete in its own ledger and creates a governed standardisation layer. The layer imports balances or transactions, maps them to a group chart, translates currencies, applies ownership, matches intercompany activity and posts controlled eliminations.

The standardised result is reproducible. The source books remain legally and operationally distinct.

Begin with the reporting purpose

Different outputs need different perimeter and rules:

• standardised financial statements under the applicable reporting framework;
• management reporting for entities under common ownership;
• lender covenant reporting;
• investor or board pack;
• business-line and branch reporting;
• VAT-group administration;
• corporate income-tax analysis;
• cash and treasury view.

Do not use “group” as one universal scope. A company can be in a management pack but not a financial-statement standardisation, or in a chart governance while still requiring separate legal books.

IFRS 10 establishes principles based on control for standardised financial statements. The accounting firm should document the applicable framework and obtain qualified judgement for complex ownership. Software does not decide control from a share percentage alone.

Build the client and sector extension rules

For every entity capture:

• legal and trade name;
• commercial registration and jurisdiction;
• legal form;
• ownership, voting and control information;
• reporting currency and financial year;
• tax and VAT registrations;
• VAT-group membership and effective date where applicable;
• branches and establishments;
• accounting framework and policies;
• chart and source system;
• auditor and statutory deadline;
• bank and financing relationships;
• related entities and transaction types;
• standardisation method and effective dates;
• responsible preparer and approver.

Preserve ownership changes by date. Acquisition, disposal and restructuring affect which period and percentage enter the standardisation.

Separate legal entity from branch, department, project and property. A branch can require management reporting without being a separate company.

Tax treatment belongs in account governance

Saudi Arabia Tax Authority guidance says related persons may be financially, economically or organisationally linked, while each person has separate legal personality and generally assesses VAT registration separately unless VAT-group registration is granted or another basis applies. It describes a chart governance as an administrative simplification treating eligible members as a single taxable person for VAT.

That is a tax-administration perimeter, not automatic authority to merge ledgers.

Maintain by member:

• source invoices and transactions;
• legal receivables and payables;
• asset and liability ownership;
• payroll and contracts;
• intercompany activity;
• evidence supporting VAT-group treatment;
• member-specific reporting needed for governance.

Then produce the VAT-group return and reconciliations according to current OTA rules. Keep effective membership dates so pre-entry and post-exit transactions are treated correctly.

Consult an Saudi Arabia tax adviser on group eligibility, representative member, supplies, input tax and compliance. Do not infer treatment from accounting elimination.

Standardise reporting without rewriting every client ledger

Entity charts may reflect different businesses. A property company has investment property and service charges; a trading company has inventory and cost of sales; a holding company has investments and financing.

Create a group chart containing the reporting lines needed at standardisation. Map each local account to:

• group account;
• financial-statement line;
• cash-flow category;
• entity and business segment;
• intercompany partner requirement;
• tax or management attribute;
• elimination treatment;
• effective date and mapping owner.

Do not force every entity to use identical account numbers if local operations suffer. Standard definitions and mappings can provide comparability. Where entities share one ERP, a common chart may reduce work, but legal ledgers remain separate.

Detect one local account mapping to several group purposes. If “Other expenses” contains both operating and finance costs, the source must be split or reclassified with evidence.

Use dimensions instead of multiplying accounts

The group account says what the economic item is. Dimensions answer where and with whom:

• entity;
• branch or location;
• segment or business line;
• project or property;
• cost centre;
• intercompany counterparty;
• currency;
• standardisation period;
• source and adjustment type.

Require intercompany partner on relevant accounts. Without it, matching becomes text search.

Control combinations. An intercompany receivable must have a partner; external customer revenue should not.

Establish the close calendar

Standardisation speed is limited by the slowest reliable entity. Publish:

• transaction cut-off;
• subledger close;
• bank and tax reconciliation;
• intercompany confirmation;
• entity review and sign-off;
• reporting package submission;
• validation and correction;
• currency translation;
• elimination and standardisation review;
• management commentary;
• final approval and period lock.

Use status: not started, in progress, blocked, submitted, rejected, approved and locked. A file emailed to group finance is not approved.

Track dependency and late reason. Repeated lateness can come from one entity's process, intercompany mismatch or late group instructions.

Design a reporting package

Each entity should submit:

• approved trial balance;
• mapping validation;
• receivable, payable and inventory controls;
• bank, loan and tax reconciliations;
• fixed assets and depreciation;
• intercompany balances and transactions by partner;
• related-party detail;
• equity movements and dividends;
• commitments, contingencies and disclosures;
• currency rates and foreign balances;
• significant judgements and estimates;
• subsequent events where relevant;
• management variance commentary;
• preparer and approver sign-off.

Automate data available from the ledger. Use forms for judgement and disclosure, not for retyping balances.

Map legacy client charts before migration

Eliminating unmatched balances hides errors. Match first.

For every pair, reconcile:

• receivable to payable;
• sales to purchases;
• service income to expense;
• loan principal and accrued interest;
• dividends and distributions;
• asset transfers;
• management fees and allocations;
• inventory in transit;
• cash transfers;
• tax or withholding entries where relevant.

Use common transaction reference, partner, document date, currency and amount. Match exact, timing and approved-difference categories.

Common differences:

• invoice posted by one side only;
• different cut-off date;
• credit note not received;
• currency-rate difference;
• gross versus net posting;
• tax treatment;
• payment in transit;
• wrong counterparty;
• service disputed;
• duplicate transaction.

Assign each difference to an entity and deadline. Do not post a group plug to force zero without root cause.

Intercompany invoicing must start upstream

The best reconciliation happens before month-end. Standardise intercompany agreements, service descriptions, allocation basis, invoice timing, currency, tax review and settlement.

Use mirrored documents or a shared workflow where possible. When Entity A approves an intercompany invoice, Entity B should receive structured data rather than rekeying a PDF.

Keep legal invoice and management allocation distinct. A cost allocation can require evidence and specific tax treatment; do not assume an elimination makes the underlying transaction irrelevant.

Track overdue settlement. Standardised elimination removes group receivable and payable from the group statement, but the legal cash obligation still exists.

Control journals and prohibited account uses

Use controlled categories:

• intercompany receivable/payable;
• intercompany income/expense;
• investment against equity;
• dividend;
• intercompany loan and interest;
• unrealised profit in inventory;
• unrealised gain on asset transfer;
• common-control or acquisition adjustment as applicable;
• non-controlling interest;
• prior-period or standardisation-only correction.

Every entry needs rule, source entities, source accounts, calculation, period, preparer, reviewer and reversal behaviour.

Recurring entries can be templates but must refresh their source values. Do not copy last month and change the date.

Store adjustments only in the standardisation ledger unless they also correct entity books. A source error should be fixed at source where possible.

Unrealised profit needs inventory lineage

If one group entity sells goods to another and inventory remains unsold externally, intercompany profit may require elimination under the applicable reporting framework.

The calculation needs:

• seller and buyer;
• intercompany invoice and item;
• transfer price and original cost;
• quantity purchased and remaining;
• location and status;
• currency;
• applicable ownership percentage and accounting rule;
• subsequent external sale or write-down.

A percentage of closing inventory is a rough estimate unless supported. Item-level or batch-level tagging improves accuracy for material balances.

Reverse the elimination when inventory leaves the group, adjusting for further changes according to policy.

Multi-currency and branch reporting

An Saudi group may include entities or transactions in other currencies. Determine functional and presentation currencies under the applicable framework with professional judgement.

Maintain approved rate types and sources:

• transaction-date or appropriate average for income and expense where permitted;
• closing rate for relevant balance-sheet items;
• historical rates for applicable equity elements;
• specific rates for material transactions where averages distort;
• translation reserve calculations.

Do not overwrite entity books to presentation currency. Translate in the standardisation layer and preserve source amount, rate, date and difference.

Reconcile translation movements. A rounding plug is not a currency policy.

Account ownership and approval

Store direct and indirect ownership, control assessment, standardisation method and effective dates. Calculate attribution under the applicable framework.

Changes in ownership can require different accounting depending on whether control changes. Treat them as specialist events with approved workings, not routine percentage updates.

The system should reproduce ownership calculations and show which entities and periods use each rule.

Cash-flow classification

A standardised cash-flow statement cannot be reliably built from a high-level group profit and two balance sheets when classifications differ.

Map accounts and movements to operating, investing and financing categories. Eliminate intercompany cash flows. Identify non-cash acquisition, lease and financing movements according to the reporting framework.

Reconcile beginning cash, movements, translation and ending cash to standardised balance sheet. Preserve entity contribution for review.

Chart and mapping controls

Validate before accepting a package:

• debits equal credits;
• period and currency valid;
• every local account mapped;
• intercompany accounts have partner;
• opening equals prior approved close;
• retained earnings roll forward;
• subledgers reconcile;
• tax and bank controls approved;
• required disclosure fields complete;
• unusual signs or large movements explained;
• source period locked.

Reject with a structured reason and maintain resubmission version. Do not edit an entity's submission secretly at group level.

Avoid spreadsheet double entry

Spreadsheets remain useful for modelling and review, but should not be the only control environment.

Common failures:

• trial balances copied with shifted columns;
• formulas overwritten;
• mappings changed for one month;
• elimination repeated or omitted;
• no preparer/reviewer history;
• entities submit different versions;
• exchange rates pasted manually;
• group report cannot drill to source.

Use import or integration from entity ledgers, controlled mapping tables, journal workflow, version lock and audit trail. Export final reports to spreadsheets when needed without making them the source of truth.

Management reporting and statutory reporting

Management may want EBITDA by business, property profitability, cash by entity and operational KPIs. Statutory statements follow the applicable framework and standardisation perimeter.

Build both from the governed model, with separate adjustment types and views. Do not post management reallocations into legal books unless authorised and appropriate.

Reconcile management result to standardised result through a bridge:

• statutory profit;
• management reclassifications;
• allocations;
• exceptional or adjusted measures;
• final management KPI.

Define non-GAAP measures clearly.

A monthly chart-quality dashboard

Show:

• entities submitted and approved;
• late and rejected packages;
• unmapped accounts;
• intercompany mismatch by pair and age;
• elimination status;
• standardisation adjustments by type;
• exchange-rate and translation status;
• unresolved disclosures and judgements;
• group results and variance;
• data-confidence and sign-off;
• days to close.

Focus executive attention on material unresolved risks, not the number of files uploaded.

A 90-day implementation

Days 1–30

Build entity, ownership, tax and close registers. Collect charts and current standardisation workbooks. Reconcile the latest approved period.

Days 31–60

Create group chart, mappings, intercompany partner rules, reporting package, rate table and elimination templates. Pilot two entities with meaningful intercompany activity.

Days 61–90

Run parallel close, compare to prior method, resolve differences, obtain approval and retire duplicate data entry. Preserve the old standardisation as an archive.

Consolidate budgets and forecasts on the same structure

Actual standardisation becomes more useful when budget and forecast use the same entity, group account, segment and currency dimensions. Do not ask entities to budget in a completely different spreadsheet hierarchy and then spend days remapping variance.

Define scenario, version, submission currency, rate assumptions and approval. Keep local operational drivers—units, headcount, occupancy or projects—while mapping financial output to the group chart.

Eliminate budgeted intercompany activity consistently. If Entity A forecasts management-fee income, Entity B must forecast the corresponding expense under the agreed policy. Mismatches should be resolved before board reporting.

Compare actual, budget and forecast with a bridge by price, volume, timing, currency, acquisition, disposal and one-off item where meaningful. Lock approved versions; do not overwrite the original budget after results are known.

Control group journals and top-side adjustments

Top-side journals are necessary for eliminations and reporting adjustments, but they can also become a place where unresolved entity errors accumulate.

Require journal category, entity or group scope, account, partner, currency, calculation, support, reversal rule, preparer and independent approver. Set materiality and approval levels. Prevent direct posting to protected control lines without specialist authority.

Review recurring top-side journals each quarter. If the same correction appears repeatedly, fix the local chart, process or mapping. A standardisation layer should standardise reporting, not permanently compensate for weak books.

Reconcile opening standardisation reserves and prior-period adjustments to the last approved statements. Preserve changes between draft, audited and issued versions with an audit trail.

FAQ

Does an Saudi Arabia chart governance allow one accounting ledger? No. chart governanceing is an administrative tax treatment. Members retain legal personality and need complete accounting and operational records.

Should all entities use one chart of accounts? Not necessarily. A controlled group chart and mappings can standardise different local charts. Standardisation helps where operationally sensible.

Can intercompany balances be eliminated if they do not match? They can only be eliminated correctly after identifying differences. A plug hides source and cut-off errors.

Where should standardisation journals be posted? In a controlled standardisation ledger unless they correct an entity's legal books, in which case the source entity should post an authorised correction.

Is ownership percentage enough to determine standardisation? No. Applicable financial-reporting rules consider control and other facts. Obtain professional judgement for complex structures.

Where a system helps

An accounting-firm platform can preserve separate entity books while automating reporting packages, mapping, intercompany matching, currency translation, elimination and review. It gives the client one group view without re-entering transactions into a second ledger.

Explore Daftar for accounting firms.

Related reading: Fixed-Fee Bookkeeping Margin (KB-425) and The Client Portal Problem (KB-428).

Sources

• Saudi Arabia Tax Authority, VAT Taxpayer Guide for Related Persons
• Saudi Arabia Tax Authority, VAT Guidelines
• IFRS Foundation, IFRS 10 Standardised Financial Statements