Perusahaan Rugi tetapi terus membayar management fee: Apakah struktur ini masuk akal?

IDTAX.OR.ID KNOWLEDGE SYSTEM

Perusahaan Rugi tetapi terus membayar management fee: Apakah struktur ini masuk akal?

FormatPost
Diperbarui13 August 2026
Waktu baca8 menit
KonteksPanduan praktis

Satu anak perusahaan rugi empat tahun.

Revenue stagnan.

Cash flow ketat.

Tetapi setiap tahun membayar management fee ke parent.

Rp10 miliar.

Rp12 miliar.

Rp15 miliar.

Pertanyaan tax authority hampir dapat diprediksi:

Jasa apa yang diterima?

Apa manfaatnya?

Mengapa fee naik saat perusahaan rugi?

Bagaimana harga ditentukan?

Apakah perusahaan independen akan tetap membayar?

Pertanyaan tersebut tidak berarti perusahaan rugi dilarang membayar management fee.

Untuk memperluas konteks pada bagian ini, lihat Tax Planning untuk Dividen: Beda keputusan pemilik dengan keputusan perusahaan.

Bisnis rugi tetap membutuhkan IT.

HR.

Legal.

Finance.

Procurement.

Strategy.

Shared service.

Group support.

Bahkan saat rugi, kebutuhan support bisa meningkat.

Masalahnya adalah structure harus masuk akal berdasarkan fakta.

PMK 172 Tahun 2023 mengatur Penerapan Prinsip Kewajaran dan Kelaziman Usaha dalam Transaksi yang Dipengaruhi Hubungan Istimewa.

Pembahasan yang masih berada dalam jalur isu yang sama dapat dilanjutkan ke Tax Planning sebelum Transaksi vs setelah Transaksi: Bedanya bukan soal timing saja.

Transaksi jasa termasuk kategori yang membutuhkan tahapan pendahuluan.

Prinsipnya diterapkan berdasarkan keadaan sebenarnya dan pada saat penentuan harga atau terjadinya transaksi.

Jadi pertanyaan bukan:

“Rugi berarti fee tidak boleh?”

Pertanyaan:

“Apakah jasa nyata, bermanfaat, dan harganya wajar untuk kondisi perusahaan ini?”

Existence test harus lewat dulu

Sebelum benchmark markup, buktikan jasa ada.

Siapa yang melakukan?

Dari entity mana?

Kapan?

Berapa lama?

Apa deliverable?

System apa?

Meeting apa?

Ticket?

Email?

Report?

Management fee agreement tidak cukup.

Invoice juga tidak cukup.

Keduanya membuktikan legal billing.

Bukan performance.

Untuk shared service, evidence bisa berasal dari kegiatan normal.

Helpdesk ticket.

ERP access.

Payroll support.

Procurement negotiation.

Legal memo.

Treasury facility.

Monthly report.

Tidak perlu membuat dokumen artificial.

Service nyata biasanya meninggalkan jejak.

Benefit test berikutnya

Jasa ada.

Apakah subsidiary mendapat manfaat ekonomis atau komersial?

Parent mengirim global newsletter.

Apakah subsidiary akan membayar pihak independen untuk newsletter itu?

Mungkin tidak.

Parent menyusun konsolidasi laporan hanya untuk kepentingan shareholder.

Apakah benefit untuk subsidiary?

Perlu diuji.

Parent menegosiasikan software group dan subsidiary memperoleh license lebih murah.

Benefit lebih jelas.

Parent menyediakan cybersecurity monitoring.

Subsidiary terhindar hiring sendiri.

Benefit.

Management fee tidak boleh menjadi tempat parkir semua cost head office.

Cost harus dipilah.

Shareholder activity.

Duplicative service.

Incidental benefit.

Direct benefit.

Shared benefit.

Chargeable or not based on arm’s length analysis.

Loss membuat benefit test lebih sensitif

Perusahaan rugi.

Apa management service memperbaiki?

Mungkin turnaround support.

Restructuring.

New sales strategy.

Supply chain repair.

Cost reduction.

Kalau parent menagih strategy fee Rp15 miliar tetapi subsidiary terus kehilangan customer dan tidak ada deliverable, board juga harus bertanya.

Tax authority bukan satu-satunya stakeholder.

CFO harus menilai value for money.

Related party fee adalah corporate governance issue.

Subsidiary directors mempunyai duty mengelola kepentingan entity.

Tidak boleh hanya menerima invoice parent tanpa challenge.

Rugi bisa berasal dari faktor lain

Jangan cepat menyimpulkan fee menyebabkan rugi.

Company mungkin rugi karena:

start-up phase.

new factory.

market downturn.

commodity price.

FX.

high depreciation.

customer loss.

regulation.

Management fee hanya 2 persen cost.

Dalam kondisi ini, loss tidak banyak menjelaskan fee.

Buat loss bridge.

Revenue.

gross margin.

fixed cost.

depreciation.

interest.

management fee.

one-off.

Kalau fee kecil, narrative berbeda.

Kalau fee mengubah profit sebelum fee Rp5 miliar menjadi loss setelah fee Rp20 miliar, scrutiny lebih tinggi.

Quantify.

Jangan hanya bilang “company rugi”.

Pricing harus dipisah per service

Satu invoice “management fee 5% revenue” terlalu kasar.

Apa hubungan revenue dengan cost of service?

IT service mungkin driver user count.

HR service employee count.

Procurement purchase volume.

Finance number of transactions.

Legal time.

Strategy direct charge.

PMK 172 meminta penerapan PKKU secara terpisah untuk tiap jenis transaksi, kecuali transaksi saling berkaitan sehingga agregasi lebih andal sesuai ketentuan.

Management fee package sebaiknya mempunyai service catalogue.

Service.

Cost pool.

Allocation key.

Markup.

Recipient.

Benefit.

Evidence.

Ini lebih defensible.

Cost allocation harus nachvollziehbar

Parent cost Rp100 miliar.

Dibagi ke 10 subsidiary.

Bagaimana?

Revenue?

Headcount?

Assets?

Transaction?

Equal?

Allocation key harus mencerminkan consumption atau benefit secara reasonable.

Jangan pilih driver hanya karena memindahkan lebih banyak fee ke negara tarif tinggi.

Test.

IT cost with headcount may make sense.

Treasury cost with debt volume.

Procurement with purchases.

HR with employees.

One key for all cost often weak.

Cost pool juga harus exclude shareholder cost.

Board listing cost.

Investor relation.

Parent tax return.

Acquisition solely for shareholder.

Need analysis.

Markup tidak selalu satu angka universal

“Semua management fee markup 10 persen.”

Kenapa?

Jenis service berbeda.

Routine support vs high-value unique service.

Independent comparable.

Function.

Risk.

Asset.

Metode transfer pricing dipilih berdasarkan reliability and transaction characteristics.

Cost plus sering relevan untuk certain routine service providers, tetapi bukan otomatis semua management fee.

Tax team harus memilih method sesuai PMK 172.

Benchmark document should match tested transaction.

Jangan benchmark generic consulting margin jika service sebenarnya payroll processing.

Loss subsidiary tidak otomatis berarti markup nol

Jika independent service provider memberikan jasa, ia tetap ingin profit meskipun client rugi.

Jadi subsidiary loss bukan alasan otomatis menghapus markup.

Tetapi independent client juga punya options.

Renegotiate.

Reduce scope.

Terminate.

Insourcing.

Delay.

Jika subsidiary terus rugi dan fee naik tanpa challenge, arm’s length behavior question.

Management perlu menunjukkan commercial review.

Annual budget.

Service need.

Cost saving.

Renegotiation if needed.

Related party should behave with commercial discipline.

Cash payment juga perlu realistis

Subsidiary rugi dan cash poor.

Management fee accrued Rp30 miliar.

Tidak dibayar tiga tahun.

Parent terus mengenakan interest atas unpaid fee.

Structure semakin kompleks.

Apakah independent supplier akan terus memberikan service tanpa payment?

Mungkin jika strategic, with credit arrangement.

Tapi terms need review.

Unpaid balance bisa become financing.

Transfer pricing analysis may need both service and financial transaction.

Don’t ignore.

Aging report is evidence.

If parent forgives fee later, another characterization arises.

Withholding tetap perlu dianalisis

Management fee dapat menimbulkan PPh withholding tergantung recipient, residence, nature, treaty, dan applicable rule.

Domestic related party service can trigger PPh 23 in relevant categories.

Foreign service can involve PPh 26 or treaty analysis.

VAT can arise.

Cross-border service may involve VAT on utilization from outside customs area.

Do not focus only deductibility.

One fee has multiple taxes.

Service exists but withholding wrong still compliance issue.

Tax map:

deductibility.

transfer pricing.

withholding.

VAT.

treaty.

Documentation.

Related-party disclosure.

Double deduction risk

Shared service parent costs include third-party invoice.

Subsidiary also directly books same vendor invoice.

Then parent charges allocation again.

Duplicate.

Or local staff perform same function and parent also bills.

PMK 172 service analysis should look at duplication.

Company should run duplicate test.

Compare service catalogue with local functions.

If local HR team 20 people and parent charges full HR service, what exactly parent adds?

Specialist?

System?

Policy?

Benchmark?

Define.

Avoid generic “support”.

Management fee agreement must match conduct

Agreement says parent gives:

finance,
tax,
legal,
HR,
IT,
strategy.

Actual billing cost pool includes:

M&A team,
investor relation,
board cost,
parent audit,
share issuance.

Mismatch.

Contract cannot save.

Update cost pool and contract.

If service scope changes, amendment.

If new function added, document.

Annual refresh.

Do not let 2019 agreement run unchanged in 2026 if group changed.

Loss company needs stronger board documentation

Board should review:

Why fee?

What services?

How much?

Benefit?

Alternatives?

Cash impact?

Transfer pricing?

Could scope reduce?

Approval?

This is not only tax defense.

It is governance.

Minor routine fee can follow policy.

Material fee exceeding profit before fee should get higher approval.

Independent director or audit committee may be relevant depending company governance.

Related-party transaction policy should define threshold.

Tax documentation threshold does not replace governance threshold.

Turnaround period can justify unusual support

Company in crisis may receive more service.

Parent sends turnaround team.

Renegotiates suppliers.

Implements new ERP.

Restructures debt.

Closes factories.

Fee increases.

Company still loses because restructuring costs.

This can be commercially sensible.

Evidence:

project plan.

team list.

deliverables.

cost saving.

board approval.

temporary duration.

Expected benefit.

Loss itself doesn’t invalidate fee.

Absence of business explanation does.

Low-profit company can also be limited-risk entity

Transfer pricing model may characterize subsidiary as limited-risk distributor expected to earn stable margin.

If it loses repeatedly while related parties earn high returns, entire model may need review.

Not just management fee.

Are risks actually limited?

Market shock?

Extraordinary cost?

Pricing policy?

Inventory?

FX?

Related-party purchase price?

A management fee may be only one factor.

Tax review should look at whole related-party architecture.

Don’t isolate invoice if transactions interact.

PMK 172 allows combined analysis for interrelated transactions in conditions specified.

CFO should ask whether losses are structurally shifted

If every Indonesia subsidiary loses but regional HQ earns steady profit, ask.

Not accuse.

Analyze.

Who creates value?

Who bears market risk?

Who controls?

Where people?

Where customer relationship?

Where inventory?

Who decides price?

If local company bears substantial risk, persistent loss may be arm’s length in bad years.

If HQ claims all upside but local bears downside, model inconsistent.

Transfer pricing is about allocation of return consistent with functions and risks.

Management fee becomes lens.

Use a three-layer file

Layer 1: service existence.

Agreement.

People.

Deliverables.

Ticket.

Meeting.

Layer 2: benefit and allocation.

Service catalogue.

Cost pool.

Allocation key.

Duplicate test.

Layer 3: price.

Markup.

Benchmark.

Method.

TP conclusion.

Then layer tax compliance.

Withholding.

VAT.

Invoice.

Payment.

SPT disclosure.

This file is much stronger than one TP report with generic paragraph.

It also helps management understand cost.

Rugi empat tahun adalah trigger review, bukan automatic disallowance

Set trigger.

Two consecutive loss years and management fee material.

Review.

Fee > x% revenue.

Review.

Fee > profit before fee.

Review.

Unpaid > 12 months.

Review.

Service scope changed.

Review.

These thresholds internal, not tax law.

Purpose risk management.

When trigger hits, tax and business revalidate.

Do not wait examination.

If fee still justified, document.

If not, change future arrangement.

Past transaction follows actual facts.

Don’t retroactively erase.

Structure masuk akal jika independent logic masuk

Tanya:

Would subsidiary buy this service from independent party?

Would it pay this amount?

Would provider deliver on these terms?

Would a loss-making customer renegotiate?

Would provider continue without payment?

Would board approve?

If answer mostly yes with evidence, structure can be reasonable.

If answer only:

“Group policy requires it,”

that is not enough.

Group policy can organize transaction.

Arm’s length and business rationale still need analysis.

Perusahaan rugi boleh membayar management fee.

Yang tidak boleh diabaikan adalah apakah fee tersebut benar-benar membeli sesuatu yang bernilai.

Loss is not proof of abuse.

But persistent loss plus weak evidence plus rising related-party fee is a strong reason to investigate before tax authority does.

Leave a Comment

Your email address will not be published. Required fields are marked *