Indonesian financial reporting standards — Standar Akuntansi Keuangan, or PSAK — have been converging with IFRS for well over a decade. For a group consolidating an Indonesian subsidiary, the practical question is narrower than “are they the same?” It is: where do the remaining differences bite, and what does that mean for the reporting pack?
Where convergence stands
Indonesia has pursued convergence rather than wholesale adoption. Standards are issued by the Indonesian Financial Accounting Standards Board and are based on IFRS, but they are adopted deliberately, with a lag, and occasionally with modification to reflect the local environment.
The direction of travel has been consistent: the gap has narrowed with each cycle, and recent revisions have moved PSAK numbering and content into closer alignment with the corresponding IFRS. For most conventional commercial entities — recognising revenue, holding fixed assets, leasing premises, employing staff — the recognition and measurement outcome under PSAK will be the same as under IFRS.
That similarity is what makes the exceptions worth knowing.
Where differences tend to arise
Effective dates
This is the most common source of divergence, and the least discussed. A standard adopted internationally in one year may become effective in Indonesia a year or more later. During that window a group reports on the new basis while its Indonesian subsidiary reports statutory figures on the old one — and the consolidation adjustment has to be identified, quantified and carried.
Groups that track only the content of standards, and not their local effective dates, discover this during the year-end close.
Functional currency
The functional currency assessment follows the same principles under both frameworks, and an Indonesian entity may legitimately determine that its functional currency is not the rupiah. However, statutory filings, tax reporting and regulatory submissions have their own currency and language requirements, and the accounting conclusion does not override them.
The practical result is that entities reporting in a foreign functional currency still maintain a rupiah reporting capability for statutory and tax purposes. That should be designed into the chart of accounts and the system configuration from the beginning, not bolted on at the first year end.
Employee benefits
Indonesian labour law establishes statutory termination entitlements that accrue with length of service. These constitute a defined benefit obligation requiring actuarial valuation, and they exist regardless of whether the company operates any pension scheme.
Foreign parents whose home jurisdiction has no equivalent frequently overlook this. The provision can be material for an entity with long-serving staff, and it is a recurring audit finding for companies preparing their first statutory accounts.
Deferred tax
The framework mirrors IAS 12, but the temporary differences themselves are driven by Indonesian tax rules — depreciation categories and rates, the treatment of specific provisions, expenses that are permanently non-deductible, and rules on loss carry-forward. Applying a group deferred tax model without re-deriving the local differences produces a number that will not survive audit.
Related party transactions
Disclosure requirements are broadly aligned, but the intersection with Indonesian transfer pricing documentation is where effort concentrates. Intercompany charges, management fees, financing arrangements and cost allocations need to be supportable in substance, priced consistently, and disclosed in a way that agrees to the transfer pricing documentation. Inconsistency between the two is a well-known audit and examination trigger.
Practical implications for the reporting pack
- Maintain a standing difference schedule. Document each PSAK-to-group-GAAP difference, its driver, and how it is adjusted. Rebuild it annually rather than rediscovering it.
- Align the reporting calendar. The statutory audit and the group reporting deadline rarely coincide. Agree which set of numbers is prepared first, and how changes flow between them.
- Obtain the actuarial valuation early. It is a common cause of delay in the Indonesian close and depends on a third party.
- Reconcile the accounts to the tax returns monthly. The annual corporate return must agree to the audited statements; differences found in April are differences found too late.
- Keep local documentation in Indonesian where required. Statutory records and certain filings have language requirements independent of the group’s working language.
The useful summary
Treat PSAK as IFRS with a local timetable and a set of locally driven inputs. The recognition principles will mostly agree. The effective dates, the employee benefit obligation, the deferred tax inputs and the statutory filing requirements will not take care of themselves — and those, rather than any conceptual divergence, are what actually determine whether an Indonesian close runs smoothly.
Accounting standards and their effective dates are revised periodically; the position applicable to a particular reporting period should be confirmed. Corevia Prima International supports statutory reporting and group reporting for companies operating in Indonesia — get in touch to discuss your requirements.
