Skip to article
HSJGlobal

INDONESIA TAX COMPLIANCE

How to Respond to an SP2DK Tax Letter in Indonesia

Turn a data query into a documented, deadline-controlled response before it becomes a wider compliance problem.

An SP2DK is a request from Indonesia’s tax authority for an explanation of identified data or information; it is not, by itself, a tax assessment or an objection decision. A company should respond if the letter is genuine, preserve the stated issue and deadline, and reconcile each point to records that can be produced again.

This route is suitable for a taxpayer that can establish why the data is complete, belongs to another period or party, or reveals an error worth correcting. It is not a substitute for an appeal after a formal assessment: if exposure is material, records are incomplete, or the response could affect multiple tax periods, obtain a controlled tax review before giving an unsupported narrative.

Key takeaways

  • Preserve the response window first. A deadline missed while records are being gathered weakens control of the file and can move the matter into a more formal follow-up path.
  • Answer the stated data point, not the whole tax history. A line-by-line reconciliation keeps a narrowly framed letter from receiving a broad, untested explanation.
  • Separate facts from corrective action. A reconciled error may require a return or payment action; a mismatch alone does not prove an underpayment.
  • Keep a reproducible evidence pack. The response should show who prepared it, what source records support it, and how a reviewer can trace every figure.
  • Do not confuse SP2DK with a formal assessment. The procedural route changes once an assessment is issued, so the company should preserve the letter and all proof of submission.

What an SP2DK means for a company

SP2DK stands for Surat Permintaan Penjelasan atas Data dan/atau Keterangan . The current compliance-supervision framework is set out in Minister of Finance Regulation 111 of 2025 . In practical terms, the letter tells a taxpayer that the Directorate General of Taxes (DGT) wants an explanation of data it holds or has obtained. Read the exact issue, tax period, taxpayer identity, delivery details, and response channel before trying to explain any figure.

A company can receive an SP2DK where the authority sees a difference between tax filings and third-party, transaction, asset, withholding, VAT, bank, customs, corporate, or other information. The letter does not establish that the authority’s data is correct. Its practical function is to require a taxpayer-controlled explanation while the matter is still in supervision rather than a completed assessment process.

The entity record matters even when the question is tax-specific. If the issue touches the tax number, address, directors, start of activity, or a corporate record created at formation, compare it with the underlying documents used for Indonesia company formation requirements . Entity data should be explained by official corporate records, not reconstructed from memory after the letter arrives.

Check the scope before drafting a response

A focused review can identify whether the letter is limited to a data mismatch, needs a filing correction, or carries wider exposure across periods and taxes.

Control the response window before collecting everything

Under PMK 111/2025, the taxpayer is given 14 days to provide an explanation after the SP2DK is sent. Do not assume that an internal sign-off, an accountant’s absence, or an incomplete archive extends that period. Preserve the envelope, electronic notification, or Coretax delivery evidence, and verify the delivery date against the letter and the relevant tax office record.

The first day is for control, not for a long explanation. Log the inbound document, nominate one owner, freeze the original facts, and request only the records connected to the specific question. A short, supported response is safer than a broad account built from unverified assumptions.

Control point Immediate action Proof to retain
Authenticity Confirm taxpayer name, tax office, letter number, tax period, and official delivery route. Original letter and delivery evidence.
Deadline Record the 14-day response date and set internal milestones for records and sign-off. Responsibility log and calendar entry.
Issue scope Transcribe each data point without changing its wording or amount. Issue ledger with source references.
Authority Confirm who can submit, attend a clarification, and approve factual statements. Power, mandate, or internal approval record.

Build an evidence ledger, not a narrative file

The most useful response asset is an issue ledger. Give each item in the letter its own row: what the DGT data appears to state, the company record that addresses it, the reconciliation, any remaining gap, and the document reference. This makes it possible to distinguish a timing difference, a gross-versus-net difference, a duplicated item, a third-party error, or an actual filing error.

Start with primary company records: submitted returns, payment identifiers, VAT invoices, withholding evidence, general ledger extracts, bank records, contracts, corporate approvals, and correspondence that identifies the counterparty or period. Where money movements are central, the reconciliation controls described in tax-and-bank record reconciliation help avoid treating a bank credit as taxable income without checking its legal and accounting basis.

SP2DK response control path A company confirms the letter, locks the deadline, reconciles each data point, and either explains the variance or makes a verified correction. Confirm the SP2DK Lock the deadline and reconcile each data point Explained variance Evidence supports the facts Verified filing error Assess correction route Submit a traceable explanation Correct only after verification
The response path separates a supported explanation from a verified error; both routes start with the same deadline and reconciliation controls.

Submit the explanation and correct only when the record supports it

A good response is a short covering explanation plus a controlled evidence pack. It should identify the letter and taxpayer, restate each issue accurately, give the factual explanation, point to the supporting record, and state any action actually taken. Keep documents indexed rather than attaching a large unlabelled archive. If the tax office asks for a meeting or a different submission route, record the request and use the authorised person named by the company.

  1. Transcribe the issue exactly. Do not paraphrase an amount, a tax period, or a counterparty into a different question.
  2. Reconcile the source records. State the accounting, tax, and commercial explanation for each difference.
  3. Have the answer reviewed by the accountable owner. A director, tax lead, or properly appointed representative should confirm facts that carry legal consequences.
  4. Use the formal delivery channel stated for the case. Retain proof of submission, attachments, and any meeting minutes or official acknowledgement.
  5. Separate a correction decision from the initial explanation. If reconciliation proves a filing error, identify the tax type, period, payment implications, and procedural route before submitting a correction.

A voluntary correction can be appropriate where the company has identified a real error and the applicable procedural conditions are met, but it should not be used as an automatic response to uncertainty. Do not manufacture a payment or an amended return merely to make the SP2DK disappear. First confirm the legal character of the item and the status of any subsequent action by the tax authority.

Pressure-test the evidence before submission

Use a second review when one data point affects several tax periods, related-party transactions, VAT, payroll, or an intended filing correction.

Response failures that create avoidable exposure

The recurring failure is treating an SP2DK as informal correspondence. A vague email, unnumbered attachments, or a response that answers a different tax period gives no reliable trail. So does a finance team replying before it has checked whether the item is gross revenue, a balance-sheet movement, a third-party reporting error, or a transaction booked by another company.

Build the file so that a different finance manager could reproduce it. Each attachment should have a reference number, the ledger should show its source period and preparer, and the covering letter should point to the exact supporting item rather than asking the reviewer to infer a conclusion. If a record cannot be found, identify the missing record, the owner of the archive, and the limited fact that can still be supported. Preserve the request and the document-retrieval trail as well, particularly where an archive sits with a former provider. Record the time and source of every late addition. That is more defensible than filling the gap with a general assurance that the company is compliant.

Escalate before answering when any of these conditions applies

  • The question affects several tax periods, more than one tax type, or an unfiled historical return.
  • The data involves related parties, a foreign counterparty, cross-border payments, customs, or a disputed beneficial owner.
  • Company records are incomplete, a predecessor service provider cannot produce files, or a director is asked to sign facts they cannot verify.
  • The company has already received an audit notice, assessment document, collection letter, or another formal action for the same issue.
  • A proposed correction could create penalties, cash-flow effects, financial-statement restatement, or disclosures beyond the issue in the SP2DK.

Deciding how to respond to an SP2DK tax letter

For a narrow and well-documented variance, the right route is a timely, issue-by-issue explanation with a clear document trail. The company should finish with proof that the response was submitted and with a retained copy of every version of the ledger and attachment pack.

Pause and obtain specialist review before making admissions, corrections, or broad statements where the evidence is incomplete or the effect reaches outside the stated issue. The desired outcome is not the fastest reply; it is a response that remains consistent with the company’s filings, accounts, source documents, and later procedural position.

Get a controlled response plan

Bring the letter, delivery evidence, and the source records already available so the response scope can be assessed without guessing.

Frequently asked questions

Is an SP2DK the same as a tax audit?

No. It is a request for clarification in the compliance-supervision process. An audit is a separate formal process with its own documents and safeguards.

How long does a company have to respond?

PMK 111/2025 provides a 14-day response period after the SP2DK is sent. Confirm the delivery date and any instructions on the specific letter immediately.

Should the company correct its tax return before replying?

Only after a documented reconciliation establishes an actual error and the procedural position is clear. A mismatch in the letter is not, by itself, a reason to amend a return.

What records normally help explain an SP2DK?

The answer depends on the issue, but may include tax returns, payments, invoices, ledgers, bank records, contracts, corporate records, and correspondence with identifiable counterparties.

What should be kept after a response is sent?

Keep the original letter, deadline calculation, submitted explanation, evidence index, all attachments, delivery acknowledgement, meeting records, and any later communication from the tax office.

On this page
Chat with an Expert