Chart of Accounts coding in SAP, NAV/Business Central & Oracle
A practical coding model that shows how the same economic account can be represented across major ERP architectures.
What good account coding must achieve
A chart of accounts must support statutory reporting, management reporting, consolidation, controls and future growth. The account code identifies the economic nature of a transaction; dimensions identify where, why and for whom it occurred.
Recommended natural-account ranges
| Range | Class | Examples |
|---|---|---|
| 100000–199999 | Assets | Cash, receivables, inventory, prepayments, fixed assets |
| 200000–299999 | Liabilities | Payables, accruals, tax, debt, provisions |
| 300000–399999 | Equity | Capital, reserves and retained earnings |
| 400000–499999 | Revenue | Product, service, subscription and other income |
| 500000–599999 | Cost of sales | Materials, delivery, direct labour and hosting |
| 600000–699999 | Operating expenses | Payroll, marketing, rent, IT and professional fees |
| 700000–799999 | Other operating items | D&A, impairment and exceptional operating items |
| 800000–899999 | Finance and tax | Interest, FX, income tax and non-operating items |
| 900000–999999 | Technical / statistical | Allocations, consolidation and reporting-only accounts |
Illustrative cross-ERP mapping
| Account | SAP G/L | NAV / BC G/L | Oracle combination |
|---|---|---|---|
| Bank—operating | 110000 | 10100 | 01-000-110000-000-000 |
| Trade receivables | 120000 | 11000 | 01-000-120000-000-000 |
| Inventory | 130000 | 12000 | 01-000-130000-000-000 |
| Prepaid expenses | 140000 | 13000 | 01-000-140000-000-000 |
| Fixed assets—cost | 150000 | 14000 | 01-000-150000-000-000 |
| Accumulated depreciation | 159000 | 14900 | 01-000-159000-000-000 |
| Trade payables | 210000 | 21000 | 01-000-210000-000-000 |
| Accrued expenses | 220000 | 22000 | 01-000-220000-000-000 |
| VAT / sales tax payable | 230000 | 23000 | 01-000-230000-000-000 |
| Share capital | 310000 | 31000 | 01-000-310000-000-000 |
| Product revenue | 410000 | 41000 | 01-000-410000-100-000 |
| Service revenue | 420000 | 42000 | 01-000-420000-200-000 |
| Cost of goods sold | 510000 | 51000 | 01-000-510000-100-000 |
| Direct service cost | 520000 | 52000 | 01-000-520000-200-000 |
| Salaries | 610000 | 61000 | 01-100-610000-000-000 |
| Employer contributions | 611000 | 61100 | 01-100-611000-000-000 |
| Marketing | 620000 | 62000 | 01-200-620000-000-000 |
| Rent | 630000 | 63000 | 01-300-630000-000-000 |
| IT and software | 640000 | 64000 | 01-400-640000-000-000 |
| Depreciation | 710000 | 71000 | 01-100-710000-000-000 |
| Interest expense | 810000 | 81000 | 01-000-810000-000-000 |
| Income tax | 850000 | 85000 | 01-000-850000-000-000 |
SAP-oriented design
Use the G/L account for natural classification and organisational objects for responsibility and reporting. Common objects include company code, controlling area, cost centre, profit centre, segment, functional area, internal order and WBS element.
| Field | Illustrative value | Meaning |
|---|---|---|
| Company code | GR01 | Greek legal entity |
| G/L account | 620000 | Marketing expense |
| Cost centre | CC200 | Sales & Marketing department |
| Profit centre | PC10 | Consumer business unit |
| Internal order | CAMPAIGN25 | Temporary campaign tracking |
Oracle segment-oriented design
Oracle commonly uses a multi-segment account combination. The natural account is one segment; other segments represent organisational and reporting attributes.
| Segment | Value | Meaning |
|---|---|---|
| Company | 01 | Greek entity |
| Cost centre | 200 | Sales & Marketing |
| Natural account | 620000 | Marketing expense |
| Product | 100 | Product family A |
| Intercompany | 000 | External transaction |
| Future | 000 | Reserved expansion segment |
Cost centres, profit centres and dimensions
| Code | Responsibility area | Typical accounts |
|---|---|---|
| CC100 | Finance | Payroll, audit, banking and professional fees |
| CC200 | Sales & Marketing | Commissions, travel, events and advertising |
| CC300 | Operations | Warehouse, delivery, utilities and maintenance |
| CC400 | IT | Software, cloud, telecom and support |
| CC500 | Human Resources | Recruitment, training and benefits |
Coding governance rules
One economic purpose should map to one active natural account.
Use specific names and definitions; avoid “miscellaneous”.
Keep expansion capacity within each family.
Restrict system, reconciliation and header accounts.
Enforce department, product or project where needed.
New accounts require rationale, mapping, owner and approval.
ERP migration and mapping controls
Create a crosswalk from legacy accounts to the target ERP and management hierarchy. Every source account must map once, with documented split rules when one-to-one mapping is impossible.
| Legacy | Target | Action |
|---|---|---|
| 6401 Software | 640000 IT software | Direct map |
| 6402 Cloud hosting | 521000 Direct hosting / 640000 IT | Split by usage |
| 6999 Miscellaneous | Multiple target accounts | Analyse transactions; no blind mapping |
