How should Indonesian rate‑regulated businesses prepare for the PSAK 120 exposure draft (IFRS 20) before 2027?

PSAK 120 (exposure draft, aligned to IFRS 20) matters now because it turns “regulatory timing differences” into a structured, auditable accounting model—potentially changing when profit is recognised, what sits on the balance sheet, and what auditors will ask you to evidence. For Indonesian SMEs and finance teams in rate‑regulated activities, the real work is not reading the standard; it is mapping where your tariffs, allowable costs, true‑ups, and incentive mechanisms create regulatory assets or regulatory liabilities, and then rebuilding data flows and close processes to support consistent measurement.

This guide provides an implementation roadmap to (1) confirm whether you are in scope, (2) identify likely financial statement and tax touchpoints, (3) design the chart of accounts and subledger data you will need, and (4) run an audit‑ready transition plan while PSAK 120 remains in exposure draft form and ahead of expected 2027 adoption timelines.

Are you actually in scope for PSAK 120—and how can you self‑assess in 30 minutes?

The fastest way to waste effort is to treat PSAK 120 as “for utilities only” or, conversely, to assume any government‑influenced pricing is rate regulation. The exposure draft is intended for rate‑regulated activities where an entity’s pricing is constrained by a regulator and the mechanism creates enforceable rights/obligations to recover allowable amounts through future rates.

A quick scope screen (practical, not legal)

If you answer “yes” to most of these, you should treat yourself as potentially in scope and start a structured assessment:

1. Do you have a formal rate/tariff decision or approval process?

• e.g., a regulator/authority issues tariff determinations, permitted price formulae, or periodic resets.

2. Is the price you charge linked to a “regulated rate” rather than freely negotiated customer-by-customer?

3. Do the rules define allowable or disallowable costs and/or an allowed return?

• e.g., cost pass-through, capex recovery, efficiency factors, weighted average cost of capital (WACC)-type logic.

4. Is there a true‑up mechanism?

• Under/over‑recoveries are carried forward into future rates rather than absorbed permanently.

5. Are you required to provide goods/services to customers under the regulatory framework?

• Often paired with service obligations and restrictions on customer selection.

6. Do you have an enforceable right to charge customers higher/lower amounts in the future to settle past differences?

• This enforceability point is central to whether “regulatory assets/liabilities” are recognised.

Common Indonesian situations that warrant a closer look

Without trying to list every sector, in practice you see rate‑regulation characteristics where there are:

• tariff resets (periodic or formula-based),
• cost recovery frameworks,
• mandated service obligations,
• explicit under/over recovery carry-forward.

If you are in a sector where prices are influenced by government policy but there is no structured, enforceable mechanism for future recovery/return (for example, ad hoc political pricing or discretionary subsidies without a true-up), you may be out of scope—or only partially exposed.

What to do immediately

• Assign a finance owner to run a one‑page scope memo: regulator/authority involved, tariff mechanics, true-up clauses, enforceability evidence, and which revenue streams are affected.
• Collect the last 3–5 years of tariff decisions, reset letters, or formulae.
• Decide whether you need a deeper technical assessment (often yes if you have any kind of “carry-forward” or “balancing account” concept).

Where do regulatory assets and regulatory liabilities come from in day‑to‑day operations?

PSAK 120’s practical impact usually starts with a simple operational reality: your billing in a period is not always the same as the “regulated revenue” for that period under the rate-setting mechanism.

Recognition triggers you can map to real events

A good implementation approach is to map recognition to operational triggers (events your team can actually observe):

Regulatory asset (typical trigger pattern)

• You deliver service and incur allowable costs (or earn allowed returns),
• but current-period tariffs do not yet recover the full regulated amount,
• and the framework gives you an enforceable right to increase future rates (or charge future customers) to recover the difference.

Regulatory liability (typical trigger pattern)

• You bill and collect more than the regulated amount for the period,
• and the framework requires you to reduce future rates (or provide future credits) to return the over-recovery.

Measurement logic finance teams should operationalise

The ED model is designed to measure the amount you will recover/return through future rates. Practically, this means building measurement around:

• the rate-setting adjustment (what will change future tariffs),
• the timing (when recovery/return is expected),
• and any constraints (disallowances, caps, incentives, performance penalties).

A useful internal framing for implementation:

1. Identify the “difference”: regulated revenue vs billed revenue (or regulated cost recovery vs billed recovery) for each mechanism.
2. Assess enforceability: do you have contractual/regulatory support for future rate adjustment?
3. Assign a recovery pattern: over what period does the regulator allow recovery/return?
4. Apply probability/constraint judgments where the framework includes performance conditions or disallowances.

What changes compared with typical current practice (in ED context)

Many Indonesian rate‑regulated entities already track under/over recoveries in management reports. The step-change under PSAK 120 is typically:

• Formal recognition on the balance sheet (not just memo accounts),
• Defined measurement discipline tied to the regulatory agreement, and
• More robust documentation for estimates, constraints, and reversal patterns.

Where teams often struggle is that the “regulatory asset” is not simply a claim against the regulator; it is a right to bill customers differently in the future under the regulatory framework. That affects how you document enforceability and how you explain it to auditors.

What financial statement line items and KPIs are likely to move—and how do you anticipate covenant effects?

Even if total cash over the life of the regulatory cycle is unchanged, PSAK 120 can change timing—and timing drives reported profit, equity, and leverage metrics.

Likely line-item impacts (implementation view)

Your project team should pre-map where movements will land in the statements:

• Balance sheet: new or expanded lines for regulatory assets and regulatory liabilities (or disaggregated within other assets/liabilities depending on presentation decisions).
• Profit or loss: changes in the pattern of revenue recognition and/or expense presentation linked to regulated amounts.
• Equity: opening transition adjustments may affect retained earnings (depending on transition approach).
• Cash flow: usually less affected economically, but classification and reconciliation narratives may need updating.

KPI impacts that matter commercially

Finance leaders should run a “KPI sensitivity pack” early, because operational decisions and banking conversations depend on these numbers:

• EBITDA: may move if regulated revenue recognition differs from billed revenue timing, especially when true-ups are significant.
• Interest coverage: may change due to profit timing, not cash.
• Leverage ratios: balance sheet recognition of regulatory liabilities (or reduction in equity on transition) can shift debt/equity or net-debt-based covenants.
• Working capital metrics: regulatory assets are not trade receivables; internal definitions and dashboards may need to separate them.

Covenant and stakeholder management (do this before year-end)

If you have bank covenants or investor reporting:

1. Identify covenant definitions: are they based on audited PSAK financials? Are “non-cash regulatory balances” included in net debt or working capital definitions?
2. Model the transition adjustment: even a directional estimate helps you plan negotiations.
3. Prepare a reconciliation narrative: what changed, why it’s non-cash, and how it reverses through tariffs.
4. Engage early: lenders dislike surprises more than they dislike changes.

A practical control: create an internal “PSAK 120 KPI bridge” showing (a) billed revenue, (b) regulatory revenue adjustment, (c) resulting profit timing effect, and (d) reversal schedule. Auditors frequently ask for this bridge because it demonstrates you understand the mechanics, not just the journal entries.

What data do you need to capture to measure regulatory balances—and where does it usually live today?

Most implementations fail not on accounting theory but on data availability. PSAK 120 measurement depends on tariff mechanics, volumes, allowable costs, and true-up calculations—data that is often scattered across operations, engineering, billing, and regulatory affairs.

Minimum data set to build (per regulated mechanism)

Treat each tariff/true-up mechanism as a “measurement unit” and define a dataset for it:

Tariff decision and rulebook

• Tariff determination documents (approvals, formulae, reset letters)
• Effective dates and reset periods
• Allowable vs disallowable cost categories
• Allowed return parameters (where applicable)
• Incentive mechanisms (efficiency factors, quality penalties/bonuses)

Operational drivers

• Volume/usage data that drives billing (kWh, m³, tonnes, trips, connections, etc.)
• Service mix and customer class data (if tariffs differ)
• Outage/quality KPIs if linked to incentives

Financial inputs

• Cost base by allowed categories (OPEX, capex additions, depreciation base)
• Regulatory depreciation / asset base roll-forward (if the framework uses it)
• Timing of capex commissioning and inclusion in the regulatory asset base

True-ups and deferrals

• Under/over recovery calculations by period
• Carry-forward schedules and recovery horizons
• Disallowance decisions and historical precedents

Where the data typically sits (and why close breaks)

• Tariff documents: emails, PDF folders, regulatory affairs team drives
• Volumes: operations systems, SCADA/production databases, manual logs
• Billing: billing engine / ERP AR module
• Cost allocations: spreadsheets, cost centre reports, project accounting
• True-ups: Excel models owned by one person

This “distributed ownership” creates three predictable problems:

1. Uncontrolled spreadsheet logic becomes the de facto accounting model.
2. Timing mismatch: volume data finalises after finance close.
3. Weak audit trail: you can’t reproduce last quarter’s numbers.

Practical fix: create a “regulatory data pack” with owners

Build a recurring monthly/quarterly pack with named owners and deadlines:

• Regulatory affairs owns tariff documents and interpretations.
• Operations owns volumes/quality metrics.
• Finance owns allowable cost mapping and reconciliation to GL.
• Tax/accounting policy owner signs off on judgments (constraints, recovery periods).

Make the pack a controlled artifact (versioning, approvals). This becomes the backbone of your audit evidence file.

How should you redesign the chart of accounts and subledgers so PSAK 120 does not become a spreadsheet-only process?

A spreadsheet may be unavoidable for modelling early on, but your target state should be system-supported accounting, with clear posting rules and traceability.

COA design principles (what works in practice)

1. Separate regulatory balances from trade balances

• Regulatory assets/liabilities should not be mixed with trade receivables/payables; they behave differently and reconcile differently.

2. Tag by mechanism

• Use dimensions (cost centre / profit centre / segment / custom fields) to track which tariff mechanism generated the balance.

3. Track reversal profile

• If you can, tag expected reversal timing buckets (e.g., <12 months, 1–3 years, >3 years) for disclosure and planning.

4. Minimise manual journals

• Design recurring entries (templates) and automated feeds where possible.

Suggested account structure (illustrative)

• Regulatory assets – under-recovery (by mechanism)
• Regulatory assets – incurred costs not yet recovered (by mechanism)
• Regulatory liabilities – over-recovery (by mechanism)
• Regulatory income/expense – movement in regulatory balances (by mechanism)
• Contra/clearing accounts for true-up settlement through billing (to avoid double counting)

Subledger vs GL: deciding where calculations should live

Ask two questions:

• Will the calculation be re-performed by auditors? If yes, it needs inputs and logic that are stable and reproducible.
• Does it tie to billing or volumes at transaction level? If yes, consider a subledger or a controlled calculation engine that can ingest transaction detail.

For many SMEs, the pragmatic approach is:

• Keep transaction detail in billing/operations systems.
• Build a controlled calculation model (could be a governed spreadsheet initially).
• Post summarized monthly journals into the ERP with strong references (mechanism, period, version).

The key is governance: spreadsheet is acceptable as a tool, not as an uncontrolled system.

What month‑end close workflow changes should you plan for (journals, estimates, reversals, consolidation)?

PSAK 120 adds a new close stream: regulatory accounting close. If you bolt it on after the fact, you will extend close timelines and increase audit adjustments.

A workable close sequence (road-tested)

Step 1 — Pre-close cut-off alignment (Day -2 to Day 0)

• Confirm the volume/usage data cut-off.
• Lock key tariff parameters effective for the month.

Step 2 — Calculate under/over recovery (Day 1–Day 3)

• Run the regulatory model: billed revenue vs regulated revenue (or allowed recovery) by mechanism.
• Produce movement schedules for regulatory assets/liabilities.

Step 3 — Book journals with standard templates (Day 3–Day 5)

• Movement in regulatory asset/liability
• P&L impact (regulatory income/expense) tied to mechanism
• Any reclassifications needed for presentation

Step 4 — Reconciliations and analytics (Day 4–Day 6)

• Reconcile to billing totals (billed revenue, customer classes, volumes)
• Reconcile allowable costs to GL
• Variance analysis vs prior month and vs tariff assumptions

Step 5 — Consolidation and eliminations (if group) (Day 6–Day 8)

• Confirm intercompany implications where regulated charges occur within a group
• Ensure consistent mechanism tagging across entities

Estimates and reversals: define rules early

Two areas need explicit policies:

• Estimates: what do you estimate (volumes, incentive penalties, disallowances) and when do you true-up?
• Reversals: do you reverse accruals next month, or carry forward with updated estimates?

Document these rules so your close is consistent. In Indonesian audit practice, inconsistency is a frequent root cause of extended audit queries.

Controls auditors will expect to see evidence for

• Review/approval of tariff parameter updates
• Change control for the calculation model (who changed what, when, why)
• Reconciliation sign-offs (billing to model; model to GL)
• Evidence that significant judgments were reviewed (constraints, recovery periods)

If you cannot evidence these controls, the numbers may still be “right,” but you will spend disproportionate time defending them.

How do you run an audit‑ready transition project while PSAK 120 is still an exposure draft?

Because PSAK 120 is in exposure draft form, you need a plan that is robust to change. The aim is to build capabilities that will still be useful even if details evolve.

A practical transition roadmap (now → 2027)

Phase 0 — Mobilise (4–6 weeks)

• Appoint a project owner (usually Financial Controller) and an executive sponsor (CFO/Finance Director).
• Identify in-scope mechanisms and revenue streams.
• Create a document repository for tariff decisions and true-up calculations.

Phase 1 — Diagnostic & gap assessment (6–10 weeks)

• Current state mapping: where are under/over recoveries tracked today?
• Gap analysis: data missing, timing issues, weak controls.
• High-level accounting position memo (assumptions clearly labelled as ED-based).

Phase 2 — Prototype measurement & reporting (8–12 weeks)

• Build a controlled regulatory calculation model.
• Run parallel numbers for a few periods (e.g., last 6–12 months) to understand volatility.
• Produce a management pack: movement schedules, KPI bridges, and reversal profile.

Phase 3 — System and process design (12–20 weeks)

• COA changes, dimensions, and journal templates.
• Close workflow integration (deadlines, owners, sign-offs).
• Draft accounting policy and estimate methodologies.

Phase 4 — Dry run with auditors (timing depends on audit cycle)

• Share methodology early; ask what evidence format they prefer.
• Walk through one mechanism end-to-end (inputs → calculation → journal → disclosure).

Phase 5 — Go‑live readiness (leading into adoption)

• Training for finance and operations data owners.
• Finalise transition approach and documentation.

Managing uncertainty without freezing

You can move now without locking into final details by:

• building data discipline (tariff docs, volumes, allowable cost mapping),
• creating repeatable workflows (close steps, reconciliations, approvals), and
• defining judgment governance (who approves assumptions and how changes are tracked).

This keeps you ready to adjust when PSAK 120 is finalised, without starting from zero.

Where are the main Indonesia tax touchpoints—and how do you prevent accounting changes from becoming tax surprises?

PSAK 120 is an accounting change, but in Indonesia the practical tax risk is often process-related: inconsistencies between accounting recognition, fiscal adjustments, and supporting documentation that later complicate DJP queries.

Tax touchpoints to map early

1. Profit timing vs taxable income timing

• If accounting profit shifts due to regulatory balance movements, you need to assess whether fiscal treatment follows accounting or requires adjustments.

2. Deferred tax considerations

• New balance sheet amounts can create temporary differences. Your tax team needs to know what is new, what reverses, and when.

3. Invoice/VAT and billing mechanics

• True-ups and credits processed through billing can affect how you explain revenue movements and settlement patterns.

4. Deductibility and “allowable cost” vs “fiscal deductible”

• Regulatory allowability is not the same as tax deductibility; maintain separate classifications.

A practical way to keep accounting and tax aligned

Build a monthly “three-way bridge”:

• Billing: what customers were invoiced/credited
• PSAK 120 regulatory adjustment: what moved into/out of regulatory assets/liabilities
• Tax view: what is treated as taxable/deductible now vs later (and why)

Keep this bridge as part of your close file. Even if positions evolve, you will have a disciplined record of how you arrived at outcomes.

Governance point for SMEs

Many SMEs rely on one person to manage both accounting and tax adjustments. Under PSAK 120, create at least a two-step review:

• Finance prepares the bridge and journals.
• Tax reviewer (internal or external) validates the fiscal implications and flags documentation gaps.

Paul Hype Page & Co. often supports clients by setting up these bridges and review routines so accounting changes do not cascade into year-end tax rework.

What documentation will Indonesian auditors ask for—and how do you build it into controls rather than scramble later?

Audit readiness under PSAK 120 is less about producing a large binder and more about demonstrating that your numbers come from controlled processes with traceable inputs.

Build an “audit evidence file” by mechanism

For each material mechanism, maintain:

1) Regulatory framework evidence

• Tariff determinations and effective dates
• Documentation of enforceability (why recovery/return is expected under the framework)

2) Methodology memo (plain language)

• What you measure and why
• Key judgments (constraints, disallowances, incentive probabilities)
• How you determine recovery period and reversal profile

3) Input controls

• Source reports for volumes and billing
• Allowable cost mapping to GL accounts
• Change log for tariff parameters

4) Calculation outputs

• Movement schedules and roll-forwards
• Reconciliations to billing totals and GL
• Variance explanations

5) Posting and reporting

• Journal entries with references to model version and approver
• Draft disclosures / presentation mapping

Control design that reduces audit friction

• Model governance: version control, locked cells, peer review, and documented checks.
• Reconciliation discipline: standard formats, thresholds for investigation, and sign-offs.
• Judgment committee (lightweight): a monthly/quarterly meeting where finance, regulatory affairs, and operations approve key assumptions.

What usually goes wrong (and how to fix it)

• “We can’t reproduce last quarter’s number.”
• Fix: store the exact model version and input extracts used.
• “The tariff document says one thing; your model does another.”
• Fix: maintain a tariff rule summary with references to clauses/pages.
• “Your reversal profile is not supported.”
• Fix: link recovery assumptions to the regulator’s reset cycle and historical practice, and document deviations.

If you treat documentation as part of the monthly workflow, audit becomes confirmation—not reconstruction.

How do you keep the project commercially grounded (cost, people, timelines) while still meeting 2027 readiness?

PSAK 120 readiness is not only a finance initiative. It touches operations data, billing, and management reporting. The commercial risk is either over-building too early or under-building and paying for it later through audit overruns and rework.

Resourcing model that fits SMEs

A common, workable structure:

• Executive sponsor: CFO/Finance Director (decision-maker on policy and priorities)
• Project owner: Financial Controller (drives delivery)
• Regulatory liaison: regulatory affairs/contract manager (tariff rules)
• Operations data owner: ensures volumes and KPIs are timely and reliable
• Systems lead: ERP/reporting owner (COA, dimensions, integrations)
• Tax reviewer: validates fiscal implications and deferred tax mapping

Time and cost drivers to watch

• Number of mechanisms/tariffs you must model
• Quality and timeliness of volume and billing data
• Extent of allowable cost allocations and capex roll-forwards
• ERP flexibility (dimensions, reporting, journal automation)
• Audit expectations and whether you can do a dry run

Implementation sequencing that avoids “big bang” failure

• Start with one material mechanism and build the end-to-end workflow.
• Expand to the next mechanisms only after the first closes cleanly.
• Only then automate or integrate further.

Progress measures (simple and useful)

Track readiness with operational metrics, not just milestones:

• % of mechanisms with complete data packs
• Close days added by regulatory close stream (target: stable, predictable)
• # of manual journal entries (target: declining)
• Audit queries related to regulatory balances (target: declining over cycles)

This is where an implementation partner can help: not by “owning the standard,” but by helping you run the project discipline—data, workflow, controls, and audit alignment.

Conclusion

Preparing for PSAK 120 is mainly an implementation challenge: identifying which of your activities are truly rate‑regulated, translating tariff mechanics into measurable regulatory assets and regulatory liabilities, and then building the data packs, COA structure, and close controls so the numbers are repeatable and auditable. The teams that manage the transition well start with a mechanism-by-mechanism scope screen, build a controlled calculation model, and integrate it into month-end workflows with reconciliations and sign-offs—while also running an early KPI and covenant impact assessment and mapping tax touchpoints.

If you want support, Paul Hype Page & Co. can assist with a structured diagnostic, system/data design, and audit-ready documentation so your finance team can run PSAK 120 reporting with confidence as requirements are finalised and 2027 approaches.