How should regulated Indonesian SMEs implement PSAK 120 without breaking month-end close or audit readiness?

PSAK 120 is set to change how certain regulated Indonesian businesses recognise and disclose regulatory assets and regulatory liabilities—items that many SMEs currently park in “other receivables/payables”, defer informally, or explain outside the numbers. For finance leaders, the real problem isn’t understanding the standard in theory; it’s operationalising it into Indonesia Accounting & Tax workflows and Indonesia Audit evidence before 2027 reporting. If you’re in a tariff-, rate-, or compensation-driven sector, PSAK 120 can affect revenue timing, EBITDA optics, covenant headroom, and the story you tell lenders and shareholders. This guide gives a step-by-step roadmap to (1) screen whether you’re in-scope, (2) redesign your close to capture audit-ready regulatory evidence, and (3) align accounting and tax positions during 2026 so 2027 reporting is not a fire drill.

What practical changes under PSAK 120 will actually disrupt your close process?

For most SMEs, PSAK 120 impact shows up in workflow friction—new data you must capture, new judgments you must document, and new disclosures that require consistent mapping. The key practical shifts are below.

Recognition: you can’t “net it off” or keep it off-books informally

PSAK 120 focuses on rights to add amounts to future rates (regulatory assets) and obligations to reduce future rates (regulatory liabilities) created by a regulator’s rate-setting framework.

In practice, this pushes teams to answer, with evidence:

• What specific mechanism allows recovery/refund through future customer rates?
• When does the right/obligation arise (trigger event)?
• Is it linked to regulated rates rather than a normal commercial contract term?

If you currently manage these items via:

• “management memos” outside the ledger,
• manual tracking spreadsheets with no audit trail,
• netting against revenue/cost lines,

…PSAK 120 will likely force them into explicit balance sheet line items and reconciliations.

Measurement: you need a repeatable model, not a one-off calculation

Even where the amounts are straightforward, the disruption comes from needing a consistent measurement approach each month/quarter:

• What costs/income are included in the rate adjustment mechanism?
• How do you treat timing differences (incurred now, recovered later)?
• Are there caps, thresholds, true-ups, or clawbacks that change the estimate?

SMEs often underestimate the operational load here: measurement will not be a year-end “special project” if your regulator issues decisions during the year or if cost recovery is updated periodically.

Disclosure: you will need structured narratives backed by traceable documents

PSAK 120-style reporting is not only numbers. Expect more pressure to disclose:

• The nature of the rate regulation and how it creates the regulatory balance.
• Movements: opening balance, additions, recoveries/refunds, remeasurements.
• Uncertainties: key assumptions, exposure to regulatory change.

Disclosures fail when they are written late, by copying last year’s wording, without a document pack that supports every claim.

“Decision-impact” takeaway

If your regulatory economics are material, PSAK 120 can change:

• Timing of profit recognition (even if total cash over time is unchanged)
• Balance sheet presentation (new categories, reclassifications)
• KPI narratives (gross margin, EBITDA stability, AR days)
• Audit effort (more testing of correspondence, approvals, and the “right to recover” logic)

You don’t need textbook mastery. You need a controlled process that produces the same answers every period—supported by evidence.

Are you likely in-scope—and how do you screen applicability without a months-long project?

The quickest way to avoid wasted effort is to run a structured screening that ties to how you get paid.

Step 1: Identify whether you operate under a rate-setting or compensation framework

You are more likely to be in-scope if:

• Prices/tariffs are set or constrained by a regulator (not just market competition).
• There is a formal mechanism that allows future price adjustments to recover specific past costs or to return excess profits.
• Your cash collection is from customers, but the rate is determined by regulatory decisions or formulae.

You are less likely to be in-scope if:

• You negotiate prices freely with customers and are only subject to general sector oversight.
• Government grants/subsidies exist, but they are not embedded in customer rate-setting.
• Contract terms (rebates/penalties) are commercial, not regulator-driven.

Step 2: Map “trigger events” that create recoveries or refunds

In-scope patterns often include:

• Cost pass-through or fuel/FX adjustments approved after the fact.
• Service reliability penalties/refunds mandated through future tariff reductions.
• True-up mechanisms where under/over recovery is corrected in future billing periods.

Out-of-scope patterns often include:

• Standard customer disputes or warranty provisions.
• Normal variable consideration under contracts (commercial rebates).

Step 3: Confirm the existence of enforceable linkage to future rates

The audit question will be: what makes recovery/refund enforceable?

Evidence can include:

• regulator determinations/letters,
• published tariff decisions,
• formula references in regulation,
• meeting minutes where the regulator confirms treatment.

If your “right to recover” is more political than enforceable, you may be dealing with a different accounting issue (e.g., contingent asset) rather than a regulatory asset.

Step 4: Decide your materiality threshold for implementation depth

Even if technically in-scope, SMEs should triage:

• Is the potential regulatory asset/liability material to total assets, profit, or covenant ratios?
• Is it volatile (likely to swing year to year)?
• Does it affect lender reporting packs?

Materiality determines whether you build a lightweight quarterly process or a full monthly subledger.

A practical output from screening

By end of the screening, you should have a one-page decision note:

• In-scope / out-of-scope conclusion (with rationale)
• Likely balance types (asset vs liability)
• Data owners (regulatory, finance, operations)
• Estimated materiality range

This note becomes the anchor for your 2026 gap assessment and your auditor alignment conversations.

Implementation note: Effective dates and transition details should be confirmed against DSAK IAI publications/current pronouncements available at the time of adoption; build your timeline with flexibility if the final effective date or transition approach is updated.

What should your 2026 gap assessment cover to avoid rework in 2027?

A good gap assessment is not a workshop. It produces an implementable design with owners, controls, and evidence mapping.

Workstream 1: Accounting policy and scope boundaries

Deliverables:

• Defined unit of account: what you treat as a “regulatory balance” (by mechanism, by tariff type, by site).
• Recognition triggers: when you record additions/reversals.
• Measurement method: how you estimate amounts and when you remeasure.
• Presentation approach: where it sits in the balance sheet and P&L mapping.

Common SME failure: letting policy remain “principle-based” with no decision rules. Your close team needs rules they can execute.

Workstream 2: Data inventory and source-of-truth design

List each input you need and assign an owner:

• Tariff/rate determinations and effective dates (Regulatory/Legal)
• Under/over recovery calculations (Finance/Commercial)
• Cost pools eligible for recovery (Operations/Costing)
• Billing volumes and timing (Sales Ops/Billing)
• Correspondence and approvals (Regulatory Affairs)

Decide:

• What stays in ERP vs what sits in a controlled calculation file.
• Version control, approvals, and retention.

Workstream 3: Controls and audit trail

Design controls that match the risk:

• Completeness: have all regulator decisions been captured?
• Accuracy: are calculations checked and reviewed?
• Cut-off: are additions/recoveries recorded in the correct period?
• Authorization: are assumptions approved by accountable leaders?

The goal is not more controls; it is controls that prevent a restatement.

Workstream 4: Disclosure readiness

Draft disclosure templates early:

• Nature of regulation and how it affects billing.
• Movement tables.
• Key judgments and estimation uncertainty.

Then link each disclosure line to a document source.

Workstream 5: Tax and management reporting alignment

Even if tax law does not follow accounting, you need a plan for:

• deferred tax implications (where applicable),
• reconciliation between accounting profit and taxable income,
• management KPI continuity (so operational leaders don’t lose trust).

Outcome of the gap assessment: a signed-off implementation plan with a prototype calculation and sample disclosure—before you build anything at scale.

How do you redesign month-end close so regulatory balances are captured cleanly (and repeatably)?

Treat PSAK 120 as a new close module: a set of tasks, inputs, review steps, and postings that occur every period.

Build a “regulatory balances close pack” (monthly or quarterly)

Minimum components:

1.  Regulatory event log

• New decisions, draft determinations, correspondence received
• Effective dates and impacted periods

2. Calculation workbook / model (controlled)

• Under/over recovery roll-forward
• Eligible cost pools
• True-ups and caps

3. Posting sheet

• Proposed journal entries with accounts and narratives

1. Evidence index

• Links or references to signed letters, meeting minutes, publications

4. Review checklist

• Reviewer sign-off, exception notes, follow-ups

Put the work where it belongs: roles and RACI

A typical SME RACI that works:

• Preparer (Finance): maintains model, drafts postings and movement schedules
• Input owners (Regulatory/Operations/Billing): provide source docs and key parameters
• Reviewer (Financial Controller/CFO): approves assumptions and postings
• Audit liaison: ensures evidence is stored and retrievable

Add two non-negotiable cut-off rules

• Regulator decision cut-off: define what constitutes “issued” vs “expected” for recognition (document the rule, apply consistently).
• Billing cut-off: ensure recoveries/refunds are matched to the period they relate to, not merely cash receipt timing.

Design the ledger structure early

To avoid disclosure pain, implement:

• separate GL accounts for regulatory assets and liabilities (not buried in other receivables/payables),
• sub-accounting dimensions (by mechanism or tariff category),
• movement tracking that ties to the note disclosure tables.

Decide how much automation is realistic

You do not need a new system to be compliant. But you do need control:

• If ERP can’t hold the detail, use a controlled workbook with:
• locked formula cells,
• change logs,
• versioning,
• documented inputs.

A lightweight workflow tool or document management system can help, but only if you set ownership and retention rules.

KPI continuity: protect management reporting

If you change revenue/expense timing, operational teams may see “profit swings” that are accounting-driven.

Practical fix:

• Maintain a bridge report: “management view” to “PSAK 120 view”, at least during transition.
• Explain drivers: additions vs recoveries vs remeasurements.

This avoids destabilising pricing decisions, bonus calculations, and internal performance debates.

What documentation will auditors actually ask for—and how do you map it to evidence now?

Indonesia Audit outcomes are heavily influenced by how quickly you can produce primary documents and show a consistent chain of reasoning.

Build an evidence map (not a folder dump)

Create a table that links each assertion to evidence:

• Existence/rights: regulator decision confirming recovery/refund mechanism
• Completeness: log of all decisions/communications in the period
• Accuracy: calculation model, input reconciliations, review sign-offs
• Cut-off: timeline of decision issuance vs effective dates
• Presentation/disclosure: mapping of balances to FS notes and movement tables

What “good evidence” looks like for regulated balances

Auditors typically look for:

• Formal tariff determinations and the sections that describe the adjustment mechanism
• Written correspondence confirming treatment of specific cost categories
• Documented methodology for under/over recovery
• Reconciliations to billing data (volumes, rate application)
• Approval trails (who reviewed, when, what changed)

Common weak points (and quick controls)

 1. Uncontrolled spreadsheets

• Control: locked templates + versioning + reviewer sign-off

2. Missing linkage between costs and recovery

• Control: eligibility matrix of cost pools and mapping to regulator framework

3. “We expected approval” accounting

• Control: recognition gate—no posting without a defined evidence threshold

4. Disclosure narrative not consistent with numbers

• Control: disclosure draft updated alongside the movement roll-forward, not after.

Retention and retrieval: plan for staff turnover

SMEs in regulated sectors often lose institutional memory when one person leaves. Your evidence pack should be self-explanatory:

• index of documents,
• short memo of key judgments,
• annual “regulatory timeline” summary.

This is one of the highest-ROI activities you can do in 2026: it reduces audit delays and lowers the chance of late-stage rework.

How do you handle opening balances, parallel runs, and 2027 reporting readiness without surprises?

Even if the final transition mechanics are subject to the exact DSAK IAI wording, SMEs can still plan the operational moves with confidence.

2026: build and test with a shadow ledger

Recommended approach:

• Run a parallel calculation for regulatory balances during 2026 (at least for the last 6–9 months), even if you don’t post to statutory accounts yet.
• Compare outputs to your current accounting treatment.
• Track differences by category: timing, classification, measurement, disclosure.

Deliverables by end-2026:

• validated model and movement roll-forward,
• evidence map tested with internal review,
• draft note disclosure tables populated with real numbers.

Opening balance approach: treat it like a mini-close

Regardless of transition method, you will need a clean starting point.

Do this work early:

• Identify all historical under/over recoveries that would be in scope.
• Gather historical regulator decisions and effective dates.
• Reconstruct movement schedules back to the starting date you will adopt.

If reconstruction is hard, document why and define a pragmatic approach—aligned with your auditors—rather than leaving it to year-end.

2027: lock the operating cadence

By 2027, your target state should be:

• regulatory event log updated monthly,
• model updated and reviewed on a fixed close day,
• postings booked with clear narratives,
• disclosure tables produced as part of close pack,
• variance analysis included in CFO reporting.

Readiness scorecard (use monthly)

Track progress with 5 measures:

• Timeliness: days to produce the regulatory close pack
• Completeness: % of decisions captured in the log
• Quality: number of review adjustments required
• Auditability: time to retrieve requested evidence
• Management clarity: reconciliation between KPI view and statutory view

If any measure degrades, your process is not stable yet.

How will PSAK 120 affect financial statement line items, KPIs, and banking covenants for SMEs?

Even when cash doesn’t change, reported performance can.

Likely line-item impacts (practical view)

Depending on your sector and mechanism, you may see:

• New or reclassified regulatory assets (separate from trade receivables)
• New or reclassified regulatory liabilities (separate from trade payables)
• Changes in the timing of revenue and expense recognition
• Expanded note disclosures: movement tables and narrative explanations

KPI impacts you should pre-brief internally

• EBITDA volatility: timing changes can shift expenses or income between periods.
• Working capital optics: regulatory assets may increase apparent “non-cash receivables”.
• Cash conversion: mismatch between profit and operating cash flow can widen.
• Segment performance: business units may appear better/worse depending on where regulatory balances are allocated.

Covenants and lender reporting: manage the story early

If you report to banks, prepare a covenant sensitivity pack:

• covenant calculation under current method vs PSAK 120 method (parallel-run numbers help),
• explanation of “accounting change vs economic change”,
• proposed covenant language discussions if needed (handled through your normal banking relationship).

Do not wait until the audited financial statements are issued to explain a covenant shift.

Board and shareholder communications

Prepare a short briefing that answers:

• What changed in accounting?
• Why does profit timing shift?
• What is the expected steady-state effect?
• What controls ensure the numbers are reliable?

This protects trust—especially if your results swing in the first adoption year.

How do you align PSAK 120 accounting outcomes with Indonesia Accounting & Tax positions without overreaching?

Tax outcomes may not follow financial reporting. The objective is not to force alignment; it’s to prevent avoidable disputes and messy reconciliations.

Start with a clear mapping between book treatment and tax treatment

Create a reconciliation framework:

• PSAK 120 additions/recoveries/remeasurements (book)
• What is treated as taxable/deductible and when (tax)
• Permanent vs temporary differences
• Documentation supporting the position

Because tax interpretation depends on facts and current guidance, avoid assumptions. Use the mapping to identify where tax advice is required.

Practical alignment checkpoints

• Invoice/billing evidence: does the regulatory recovery/refund flow through VAT-able invoices or billing adjustments? Ensure billing supports the accounting story.
• Timing differences: if book recognises a regulatory asset before cash billing, consider the tax timing implications and maintain clear schedules.
• Withholding and other taxes: confirm whether adjustments change the basis for any withholding calculations in your specific fact pattern.

Governance: one set of numbers, multiple views

Implement a controlled bridge:

• Statutory (PSAK 120) view
• Tax computation view
• Management view

The bridge should be produced by finance with review by tax advisers where needed, not reconstructed at year-end.

Where Paul Hype Page & Co. can help in practice: teams often need a combined workflow covering accounting policy, close design, and audit evidence mapping, with a separate workstream to coordinate tax reconciliations and documentation. The value is less about “knowing the rule” and more about keeping 2027 reporting on schedule with fewer late surprises.

What is a realistic implementation roadmap from Oct 2026 to 2027 reporting?

Below is a sequencing that fits how SMEs actually operate: limited bandwidth, tight closes, and heavy reliance on a few key people.

Phase 1 (Oct–Dec 2026): Scope, design, and prototype

Outputs:

• applicability screening memo (in/out + materiality)
• accounting policy decisions (recognition triggers, measurement, presentation)
• prototype model + draft movement schedules
• evidence map + document retention rules
• initial auditor touchpoint: confirm what evidence will be persuasive

Phase 2 (Jan–Jun 2027): Parallel run and workflow hardening

Outputs:

• monthly/quarterly regulatory close pack produced on schedule
• issues log: data gaps, late regulatory inputs, calculation uncertainties
• training for finance + regulatory/billing teams
• first “audit simulation”: can you answer evidence requests in 48 hours?

Phase 3 (Jul–Dec 2027): Stabilisation and reporting readiness

Outputs:

• stable cadence with minimal review adjustments
• disclosure tables and narratives updated each period
• covenant/KPI communications pack ready
• year-end audit pack structured around PSAK 120 assertions

Ownership and resourcing (SME-friendly)

A workable resourcing model:

• CFO/Finance Head sponsors and clears roadblocks
• Controller owns the close pack design
• One “regulatory liaison” (part-time) owns the event log and document capture
• Operations provides cost pool inputs with defined deadlines

How to know you’re ready

You’re ready for 2027 reporting when:

• you can produce the regulatory balances roll-forward without heroics,
• your evidence map is complete and current,
• your disclosures reconcile to the ledger,
• your tax bridge is repeatable,
• your bank reporting pack anticipates questions.

If any of these rely on a single individual’s memory, you’re not ready yet.

Conclusion

PSAK 120 will feel “new” for many regulated Indonesian SMEs because it forces regulatory economics into the core of month-end close: explicit recognition of regulatory assets/liabilities, consistent measurement, and disclosure backed by primary evidence. The most effective way to prepare is to treat 2026 as a build-and-test year—screen applicability, lock accounting policy decisions, build a regulatory close pack, and run parallel calculations early enough to see where your data and controls break. By the time 2027 reporting arrives, your goal is a stable cadence: numbers that reconcile, evidence that’s retrievable, and a clear bridge between statutory results, management KPIs, and Indonesia Accounting & Tax positions. If you need support, use an advisor as an implementation partner—focused on workflow, documentation, and audit readiness—rather than a last-minute technical reviewer.