Chart of Accounts — Singapore

Overview

SMEOne delivers a Singapore Statutory Compliance Chart of Accounts (COA) combining:

• Singapore chart template — standard Singapore chart and GST control accounts
• smeone_coa_sg — motherboard extensions for CPF, SDL, FWL, CIT provisions, trade receivables/payables, and revenue tiers

Account groups (account groups) provide reporting hierarchy — they structure financial statements without replacing ledger accounts.

Customer value (from SMEOne COA brief):

• Faster go-live with pre-built structure
• Audit-friendly grouping aligned with IRAS expectations
• Sustainable expansion via documented SOPs

Step-by-Step Guide

View chart of accounts

1. Accounting → Configuration → Chart of Accounts.
2. Expect ~170–200 accounts on a correctly configured Singapore company.
3. If you see only ~51 accounts, fiscal country may be wrong — contact Adneti.

Understand payroll liability conventions

1. SMEOne recommends granular statutory accounts under 230100–230130 (CPF employee/employer, SDL, FWL).
2. The base Singapore chart may also define CPF/SDL lines (201001–201004 style).
3. At go-live, pick ONE convention per customer — perform 科目归集 mapping before opening balances.

Use account groups in reports

1. Accounting → Configuration → Account Groups.
2. Review prefix ranges (e.g. 101xxx Current Assets, 600xxx Expenses).
3. Financial reports aggregate by group for management readability.

Add a new account (controlled process)

1. Follow SOP_COA_MOTHERBOARD_BASELINE — do not create ad-hoc codes without review.
2. Create account with correct code and type.
3. Sync account group membership per SOP_COA_ACCOUNT_GROUP_SYNC.
4. Export COA snapshot for auditor.

Opening balances at go-live

1. Use implementation templates for opening balance import.
2. Reconcile AR/AP aging to subsidiary ledgers.
3. Verify payroll liability mapping before first payroll feed.

FAQ

Q: Why are there two CPF account styles? A: Base Singapore template vs SMEOne extension. Implementation chooses one mapping — mixing causes duplicate liabilities.

Q: What is code 201000 in the CSV reference? A: Historical export code — not recreated in live chart due to collision with the base Singapore chart. Use delivery notes for authoritative codes.

Q: Can I rename accounts freely? A: Cosmetic renames are possible; code changes affect reports and integrations — follow COA SOP.

Q: Where is the COA delivery pack? A: docs/accounting/delivery_notes.txt and coa_reference_account_export.csv on the motherboard.

Q: Who approves COA changes after go-live? A: Finance controller and Adneti consultant per change control policy.