How to Avoid Common Compilation of Accounts Errors
Compilation of accounts preparing your company’s unaudited financial statements for ACRA filing looks straightforward from the outside: pull the numbers from your accounting software, format them, submit. In practice, most of the errors we see happen at the judgment calls software can’t make for you. Here are the ones that come up most often.
1. Using the wrong reporting framework
Singapore allows smaller companies to use the simplified SFRS for Small Entities framework instead of full SFRS, but eligibility depends on meeting size criteria (total revenue, assets, and employee count) across two of the last three years. Companies sometimes default to whichever template their software provides, without checking which framework they actually qualify for or continue using the simplified framework after they’ve outgrown it.
Fix: Check eligibility against current thresholds each financial year, not just once at incorporation.
2. Missing or incomplete disclosure notes
The financial statements themselves (balance sheet, P&L) are often fine, but the accompanying notes accounting policies, related party transactions, significant estimates get truncated or copy-pasted from a template without being updated for the company’s actual circumstances. ACRA and auditors both look at these notes closely.
Fix: Review notes to accounts as their own checklist item, not an afterthought once the numbers balance.
3. Not reconciling the trial balance to source documents before compiling
A trial balance that “balances” mathematically doesn’t mean every account is correct a misclassified expense and a similarly-sized missing entry can offset each other and still balance. Compiling statements straight from an unreconciled trial balance carries these errors into the final report.
Fix: Reconcile major accounts (bank, receivables, payables) against source documents before compilation begins, not after.
4. Incorrect related party transaction disclosure
Transactions between the company and its directors, shareholders, or related entities need specific disclosure treatment. These are easy to miss when a director’s personal expense or loan moves through the company informally rather than through a documented process (see our related note on director’s loans in our bookkeeping guide).
Fix: Flag any transaction involving a director or related entity at the bookkeeping stage, so it’s already identified by the time compilation happens.
5. Rounding and presentation inconsistencies
Small inconsistencies rounding to the nearest dollar in one statement and nearest thousand in another, or inconsistent date formatting don’t affect the numbers materially but signal a lack of care that can prompt closer scrutiny during review.
Fix: Set and apply one consistent rounding and formatting convention across all statements.
6. Treating XBRL conversion as a separate, later step
Some companies compile their financial statements first and only think about XBRL tagging afterward, as a technical conversion exercise. This often surfaces classification questions (is this line item “trade receivables” or “other receivables” under the XBRL taxonomy?) that should have been settled during compilation, not discovered afterward.
Fix: Consider XBRL classification requirements while compiling, not as a separate step done after the fact.
How we help
We compile financial statements against the correct framework for your company’s size, cross-check disclosures against your actual transactions rather than a generic template, and handle XBRL conversion as part of the same process rather than a separate afterthought.gulatory red tape, secure your local filing pathways on time, and build an ironclad compliant foundation around your enterprise.