Sengketa pajak yang dikelola buruk selalu terasa seperti keadaan darurat.
Surat datang.
Deadline dicari.
Tax manager menghubungi advisor.
Finance mencari pembayaran.
Legal mencari kontrak.
Business owner lupa transaksi.
Auditor eksternal bertanya.
CFO baru tahu nilainya saat seminggu sebelum filing.
Padahal sengketa pajak dapat dikelola seperti proyek.
Bukan berarti hasilnya dapat diprediksi.
Tetapi prosesnya dapat dikendalikan.
Tax Dispute Playbook adalah kerangka internal yang menjelaskan apa yang dilakukan sejak koreksi muncul sampai perkara selesai.
Dokumen apa.
Siapa PIC.
Deadline apa.
Siapa memutuskan.
Bagaimana cash dikelola.
Bagaimana accounting dan auditor diberi informasi.
Bagaimana lesson masuk ke current-year compliance.
Playbook bukan template keberatan.
Ia operating system sengketa.
Tahap 0 dimulai sebelum sengketa
Perusahaan yang baru membuat playbook setelah SKPKB sudah terlambat.
Fondasi dimulai dari transaksi.
Contract.
Invoice.
Payment.
GL.
Tax document.
Approval.
Deliverable.
Email.
System log.
Transfer pricing documentation.
Treaty file.
Reconciliation.
Dokumen ini bukan litigation document.
Ia business record.
Tetapi nanti menjadi evidence.
Karena itu, playbook harus terhubung ke document retention.
Tidak ada sengketa yang kuat tanpa audit trail.
Trigger 1: pertanyaan pemeriksa menjadi potential issue
Saat pemeriksaan, jangan tunggu SPHP.
Buat issue log.
Pemeriksa bertanya management fee tiga kali.
Flag.
Pajak Masukan sample gagal.
Flag.
Transfer pricing method dipertanyakan.
Flag.
PPh 26 treaty document tidak ditemukan.
Flag.
Setiap potential issue:
Description.
Amount.
Examiner question.
Company position.
Evidence.
Owner.
Status.
Dengan log, SPHP bukan surprise.
Tax team sudah punya preliminary response.
Trigger 2: SPHP diterima
PMK 15 Tahun 2025 mengatur SPHP dan Pembahasan Akhir Hasil Pemeriksaan.
Tanggapan atas SPHP mempunyai batas waktu sesuai aturan.
Playbook harus langsung menjalankan sprint.
Day 0: register.
Day 1: issue confirmation.
Day 1-2: evidence update.
Day 2-3: legal and technical position.
Day 3-4: management approval.
Before deadline: submit.
Timeline internal harus lebih cepat dari formal deadline.
Jangan membuat SOP yang baru bergerak hari terakhir.
Decision Gate 1: Pembahasan Akhir
Sebelum Pembahasan Akhir Hasil Pemeriksaan, management harus menentukan per issue:
Pembahasan yang masih berada dalam jalur isu yang sama dapat dilanjutkan ke Settlement Mindset vs Litigation Mindset: Bagaimana Manajemen Menilai Biaya Sengketa?.
Agree.
Disagree.
Partially agree.
Need more evidence.
Potential dispute.
Cash.
Recurring.
Tax manager tidak boleh masuk meeting tanpa mandate pada koreksi material.
One-page issue sheet.
Amount.
Facts.
Law.
Evidence.
Weakness.
Decision.
Meeting result masuk risk register.
Agreed correction juga menghasilkan remediation.
Trigger 3: ketetapan terbit
Begitu SKPKB atau surat ketetapan lain diterima:
Register number.
Date.
Sent date.
Received date.
Tax.
Year.
Amount.
Due date.
Dispute deadline.
Compare to SPHP.
Compare to closing minutes.
Jangan asumsi angka sama.
Reconcile.
Ketetapan adalah object baru.
Playbook harus membuat assessment review dalam beberapa hari.
Decision Gate 2: keberatan atau tidak
KUP memberikan hak keberatan atas objek tertentu dan PMK 118 Tahun 2024 mengatur tata cara keberatan yang berlaku sejak 1 Januari 2025.
Checklist:
Object eligible?
Deadline?
One objection per decision?
Company calculation?
Reasons?
Payment of amount agreed in final discussion?
Authorization?
Submission channel?
Evidence?
Cash?
Probability?
Recurring?
Management approval?
Kalau satu formal item gagal, jangan filing sebelum diperbaiki.
Keberatan bukan hanya technical memo.
Ia formal legal action.
PIC structure harus jelas
Executive sponsor: CFO atau finance director.
Case lead: head of tax atau tax manager.
Technical owner: tax specialist or advisor.
Evidence owner: function owner.
Legal: internal/external counsel if relevant.
Treasury: cash.
Finance accounting: recognition/disclosure.
Audit coordinator: external auditor communication.
Document controller: submission/version.
Business witness owner: relevant function.
Tidak semua case membutuhkan tim besar.
Tetapi setiap role harus ada, meskipun satu orang memegang dua role.
Satu case harus punya one control tower.
Buat case ID
Contoh:
IDTAX-DISPUTE-2026-003.
Gunakan di semua file.
Email subject.
Payment.
Legal invoice.
Risk register.
Court folder.
Accounting provision.
Auditor pack.
Satu identifier mencegah file tersebar.
Kalau ada banyak tax years, child case.
003A 2023.
003B 2024.
Portfolio tetap terlihat.
Case ID adalah hal kecil dengan efek besar.
Folder standard
00 Case Admin.
01 Assessment.
02 Examination Record.
03 Facts and Chronology.
04 Tax Computation.
05 Legal Analysis.
06 Evidence.
07 Objection.
08 Appeal.
09 Court.
10 MAP if relevant.
11 Payment and Cash.
12 Accounting and Audit.
13 Management Decision.
14 Risk and Remediation.
15 Final Outcome.
Jangan semua folder wajib terisi.
Structure tetap.
Tim baru tahu di mana mencari.
Version control wajib.
Master chronology
Buat sekali.
Update.
Transaction chronology.
Tax filing chronology.
Audit chronology.
Dispute chronology.
Court chronology.
Setiap event:
Date.
Description.
Document reference.
Owner.
Chronology adalah backbone.
Kalau dispute lima tahun, orang lupa.
Chronology menjaga memory.
Jangan menulis ulang dari nol untuk setiap tahap.
Master issue matrix
Setiap issue punya:
Number.
Description.
Tax amount.
Examiner position.
Company position.
Facts.
Law.
Evidence.
Weakness.
Probability.
Recurring.
Accounting effect.
Status.
Next action.
Keberatan, banding, MAP, dan risk register memakai matrix sama.
Update outcome.
Satu source.
Jangan advisor punya issue names berbeda dari internal.
Consistency penting.
Evidence index
Document code.
Description.
Date.
Source.
Issue linked.
Original or copy.
Confidential?
Submitted at which stage?
Version.
Jangan hanya folder.
Index membuat traceability.
Kalau hakim bertanya contract, A-001.
Kalau auditor bertanya payment, A-007.
Kalau tax manager resign, file tetap dapat dibaca.
Evidence management adalah litigation infrastructure.
Decision Gate 3: Surat Keputusan Keberatan
Saat keputusan keberatan diterima:
Outcome per issue.
Reason.
Amount.
Deadline banding.
Denda exposure.
Cash.
Evidence gap.
Recurring.
Banding recommendation.
Red-team.
Management approval.
Jangan automatic banding.
Jangan automatic stop.
Decision baru memakai information baru.
Buat board paper jika material.
Case kecil dapat approval sesuai authority matrix.
Decision Gate 4: banding
KUP dan UU Pengadilan Pajak mengatur banding atas Surat Keputusan Keberatan dengan deadline dan persyaratan formal.
Playbook banding harus mencakup:
Court jurisdiction.
Deadline.
Copy decision.
One appeal per decision.
Clear reasons.
Authority.
e-Tax Court administration according to current guidance.
Court bundle.
Chronology.
Issue list.
Evidence.
Witness.
Expert.
Cash and penalty model.
Auditor update.
Formal review dan substantive review dilakukan orang berbeda.
Jangan satu reviewer.
Court folder harus issue-based
Pemeriksaan folder request-based.
Banding folder issue-based.
Ini perubahan penting.
Hakim perlu melihat cerita per issue.
A management fee.
B royalty.
C PPN.
Untuk setiap, evidence.
Jangan upload dump audit folder.
Document controller memastikan pagination, naming, reference, submission proof.
Litigation quality dimulai dari organisation.
Surat Uraian dan Bantahan punya tracker
Saat Surat Uraian Banding diterima:
Date.
Deadline rebuttal.
New arguments.
New documents.
Facts agreed.
Facts disputed.
Response owner.
Draft.
Review.
Approval.
Submit.
Jangan sekadar copy Surat Banding.
Bantahan adalah response terhadap position lawan.
Playbook harus memaksa narrowing.
Semakin sedikit disputed questions, semakin fokus hearing.
Hearing preparation
Witness list.
Expert.
Issue.
Likely questions.
Documents.
Chronology.
Who speaks.
Who takes notes.
No coaching to change facts.
Witness speaks only what experienced, saw, heard, or knows within role.
Expert speaks expertise.
Tax lead coordinates.
After each hearing:
Minutes internal.
Questions.
New request.
Deadline.
Risk update.
Accounting update if material.
Court process menjadi data.
Cross-border branch: MAP
Jika P3B issue atau double taxation muncul, playbook harus punya MAP trigger.
Treaty.
Competent authority.
Deadline.
First notification.
Domestic dispute status.
Affiliate country.
Bilateral reconciliation.
MAP request.
Information request.
Negotiation status.
Potential corresponding adjustment.
PMK 172 Tahun 2023 menjadi current framework Indonesia untuk MAP dan APA.
MAP calendar berjalan bersama domestic.
Banding dapat memengaruhi MAP dalam kondisi tertentu.
Jangan biarkan treaty team terpisah.
Decision Gate 5: Putusan Pengadilan Pajak
Begitu putusan:
Outcome.
Issue.
Reasoning.
Tax due/refund.
Penalty.
Implementation.
Accounting.
Cash.
PK ground review.
Future-year effect.
Risk register.
Remediation.
Auditor.
Board.
Putusan bukan “case closed” sampai administrative implementation selesai.
Payment/refund tracker tetap open.
Kalau PK potential, separate decision.
Decision Gate 6: Peninjauan Kembali
PK bukan automatic next stage.
UU Pengadilan Pajak membatasi ground PK.
Playbook harus memaksa field:
Ground under Pasal 91.
Fact.
Evidence.
Trigger date.
Deadline.
Legal assessment.
Cash impact.
No ground, no filing.
PK hanya satu kali.
Tidak menangguhkan pelaksanaan putusan.
Management approval harus tinggi untuk material case.
Jangan filing karena fatigue atau pride.
Accounting track berjalan paralel sejak awal
Untuk setiap reporting date:
Gross dispute.
Cash paid.
Tax position.
Accounting standard.
Recognized amount.
Disclosure.
External opinion.
Change.
Subsequent event.
Auditor communication.
Di SAK Indonesia, ketidakpastian perlakuan pajak penghasilan terkait PSAK 212 dan ISAK 123.
Nature lain dapat melibatkan standar lain seperti PSAK 237 sesuai fakta.
Tax team memberi case facts.
Finance menentukan accounting dengan standards.
Playbook harus menghubungkan.
Treasury track juga paralel
Cash agreed before objection.
Assessment payment.
Court outcome.
Refund.
Interest.
Foreign tax.
MAP relief.
Advisor fee.
Budget.
Forecast.
Jangan CFO mengetahui cash requirement dari surat due date.
Treasury masuk case desde awal.
Setiap case punya cash forecast.
Update saat stage berubah.
External auditor communication
Quarterly case pack untuk material disputes.
Population completeness.
Accounting analysis.
Legal status.
Evidence.
External counsel.
Cash.
Disclosure.
Subsequent event.
Privilege protocol.
Jangan data dump.
Auditor dapat meminta detail.
One source.
Tax risk register adalah dashboard lintas kasus
Case.
Tax.
Year.
Gross.
Accounting.
Cash.
Stage.
Deadline.
Probability.
Recurring.
Control issue.
Owner.
Next action.
Management decision.
Open remediation.
Portfolio view menunjukkan resource.
Advisor budget.
Court load.
Cash.
Recurring theme.
Dispute management menjadi enterprise risk.
Remediation wajib, bahkan saat menang
Kalau menang karena evidence kuat, standardize evidence.
Kalau kalah karena contract, fix contract.
Kalau kalah karena tax code, fix system.
Kalau issue recurring, review all years.
Kalau legal interpretation berubah, update policy.
Kalau tim lambat, update SLA.
Case tidak selesai sebelum remediation action mempunyai owner.
Sengketa adalah feedback loop.
KPI playbook
Jangan win rate saja.
Deadline compliance 100%.
Zero formal rejection due to filing error.
Document retrieval time.
Issue recurrence.
Tax exposure resolved.
Cash recovery.
Forecast accuracy.
Remediation closure.
Case cycle.
Evidence completeness.
Advisor cost.
KPI membantu melihat process.
Menang atau kalah tetap tergantung fakta dan hukum.
Process quality dapat diukur.
Annual simulation
Pilih satu historical assessment atau hypothetical issue.
Run.
Surat diterima hari ini.
Siapa PIC?
Folder?
Deadline?
Cash?
Keberatan?
Evidence?
Auditor?
Board?
Kalau tim bingung, playbook hanya PDF.
Simulasi membuat nyata.
Update contact.
Access.
Coretax.
e-Tax Court.
Advisor.
Template.
Law.
Regulation berubah.
Annual refresh wajib.
Playbook harus memakai current rules
Sengketa adalah high-stakes dan prosedurnya berubah.
PMK 118 Tahun 2024 berlaku sejak 1 Januari 2025 untuk keberatan dan mekanisme administratif terkait.
PMK 15 Tahun 2025 mengatur pemeriksaan.
PMK 172 Tahun 2023 mengatur MAP dan APA dalam framework transfer pricing.
Coretax dan administrasi digital terus berkembang.
Pengadilan Pajak mempunyai e-Tax Court.
Karena itu, jangan hard-code seluruh prosedur teknis tanpa version date.
Setiap checklist punya:
Verified date.
Source.
Owner.
Next review.
Before filing, live verify.
Playbook bukan pengganti peraturan.
Ia memastikan orang tahu peraturan mana yang harus dicek.
Satu halaman pertama harus sangat sederhana
Jika surat datang hari ini:
1. Jangan jawab spontan.
2. Register.
3. Scan deadline.
4. Notify case lead.
5. Preserve documents.
6. Build issue.
7. Determine route.
8. Quantify cash.
9. Escalate by materiality.
10. Do not miss formal requirement.
Sepuluh langkah ini cukup sebagai emergency card.
Detail ada di belakang.
Playbook yang terlalu tebal tetapi tidak dapat dipakai hari pertama gagal.
Tax dispute playbook bukan buku hukum
Ia jembatan antara hukum dan operasi.
Peraturan menjelaskan hak dan prosedur.
Playbook menjelaskan siapa yang melakukan apa di perusahaan.
Tax.
Finance.
Legal.
Treasury.
Business.
Auditor.
Advisor.
Management.
Sengketa akan tetap mempunyai uncertainty.
Namun organisasi tidak perlu ikut uncertain tentang process.
Ketika dokumen, timeline, PIC, dan decision gate sudah jelas, management dapat fokus pada pertanyaan yang benar-benar sulit:
Apakah posisi pajak perusahaan layak dipertahankan?
Bukan lagi:
“File-nya ada di mana dan deadline-nya kapan?”