Tax Return Filing Due Dates in Indonesia: Organise Annual and Periodic Deadlines

Identify the company and periods before importing dates

Start with one legal entity and one Taxpayer Identification Number (NPWP). Record its tax-year start and end, VAT registration status and the categories of payments or transactions that may trigger withholding. The calendar belongs to that taxpayer; a group finance team can supervise it without substituting the group’s reporting year.

For annual filing, a tax year normally follows the calendar year unless the taxpayer uses a different financial year. The DGT filing-deadline schedule ties the corporate deadline to that tax-year end. A monthly tax period, or Masa Pajak, remains the anchor for the relevant periodic obligation. Moving the annual closing date does not turn monthly returns into quarterly returns.

For a new entity, reconcile the legal name and incorporation documents with its tax registration before populating the first reporting periods. The underlying documents produced through company registration in Indonesia establish the entity being tracked; tax-period and filing responsibilities still need their own documented setup.

Keep director and shareholder personal income tax returns outside the company’s task list. A corporate annual return cannot discharge an individual’s separate obligation. Likewise, an employment-related PPh 21/26 return and a company annual income tax return are different reporting objects, even if the same finance employee prepares both.

Build an applicability note for each recurring obligation. Payroll, supplier payments, final-tax transactions and VAT registration can produce different rows. No sales is not a sufficient reason to delete every tax task. Require the preparer to identify the specific return, period and basis for any “not required” conclusion; leave unresolved classifications visible to the reviewer.

Use the standard filing and payment grid

For an ordinary Indonesian corporate taxpayer, the annual income tax return is due within four months after its tax-year end; common monthly income tax returns are due by the 20th of the following month, while a VAT-registered business files its monthly VAT return by the following month-end. Apply the relevant payment rule separately. The grid shows ordinary baselines before an applicable exception.

DGT’s Coretax payment and reporting summary distinguishes the general income tax payment date from its filing date. The official filing schedule supplies the annual and periodic filing baselines. “Following month” below means the month after the relevant monthly tax period, not after the accountant finishes the books.

The payment provisions in PMK 81/2024 require ordinary monthly VAT settlement before submission and annual underpayment settlement before the annual return. Import taxes, designated collector arrangements and transaction-specific obligations need their own rule check; do not force them into the general income tax row.

Treat these as statutory outer limits , then set earlier internal preparation, approval and treasury dates. Those internal dates are management choices. They should reflect who supplies payroll data, who reconciles the ledger and who can release funds, rather than being presented as additional government deadlines.

Translate each obligation into a calendar record

Use the following record design as a working control, not as a tax-authority form. Create one record per obligation and period, with linked payment and filing tasks where both are needed. A record must explain how its date was obtained; a recurring reminder labelled only “Indonesia tax” cannot do that.

Preserve the baseline date and adjusted date in separate fields. If an adjustment is later found inapplicable, the reviewer can identify the original exposure immediately. Record whether the change affects payment, filing or sanctions only; a single overwritten date hides this distinction.

Choose a primary owner and a backup for submission. The preparer may be an external accountant, but the company should retain a person who receives unresolved questions, authorises the final data and retrieves the result. Treasury needs the payment task early enough to resolve banking access or approval limits before the outer deadline.

Use four practical states: applicability unresolved, in preparation, submitted awaiting evidence, and closed. Add an overdue flag independently of those states. This prevents an overdue return from looking complete merely because it has moved into a submission workflow.

The annual and monthly clocks can now sit in the same calendar without sharing the same calculation. Keep their anchors visible when you review the workload and evidence requirements together.

Test July when annual and monthly work overlap

Consider a hypothetical company with a tax year ending March 31, 2026. Its ordinary annual filing deadline falls on July 31, 2026. Separately, its applicable June 2026 monthly obligations produce July tasks. This example tests resource allocation; it does not assume that every company has all the obligations listed.

The July 31 entries should remain separate records. One is a June VAT obligation; the other covers the completed tax year. A combined “month-end done” message cannot establish which one was filed. Assign separate evidence references even if the same person submits both.

Work backwards from the annual return to the accounts, tax adjustments and supporting schedules needed for review. Detailed annual return preparation and reconciliation addresses the underlying annual reporting work; the calendar should identify who must deliver those outputs and when, without substituting a reminder for the calculation.

As an internal planning exercise, place the data handover and technical review ahead of the treasury release, and put a backup submission slot before the statutory limit. Do not give the annual team the only available signer on the day the VAT team also needs approval. Check the combined cash requirement as well as the combined filing workload.

For comparison, a company whose tax year ends December 31, 2026 has an ordinary annual filing deadline of April 30, 2027 under the four-month rule. That forward calendar entry is a baseline derived from the current rule, not a prediction of future relief. It should carry a review reminder for later official announcements.

Control extensions, non-working days and temporary relief

An annual filing extension, a non-working-day adjustment and a penalty waiver have different effects. Give each a separate exception entry. Before changing a task, identify the taxpayer category, covered period, affected action and official instrument; retain the unadjusted deadline for comparison.

Annual extension: create a second filing date

A taxpayer can notify an annual filing extension of up to two months. DGT’s current corporate extension explanation describes submission through Coretax for tax year 2025 onward and explains that the extension concerns filing, not a general payment deferral. Submit a compliant notification before the ordinary filing limit; an unfinished draft or a notification treated as invalid does not establish the extension.

Prepare the reason, provisional tax calculation and financial statements, underpayment evidence where applicable, the auditor’s statement if an audit is unfinished, and representative authority where relevant. Save the notification and its outcome. Then assign the revised filing date, the final accounts delivery date and the person responsible for resolving any difference from the provisional calculation.

Non-working days: adjust the relevant periodic task

PMK 81/2024’s non-working-day provisions allow covered periodic payments and periodic filings due on a qualifying non-working day to move to the next working day. The provisions include weekends, national holidays, designated election holidays and national collective leave. Apply the rule to each affected task and check consecutive non-working days. Do not automatically apply a periodic-return provision to the annual return or to every deadline in a tax notice.

Keep the holiday basis with the adjusted entry, and retain an earlier operational target. A company’s own office closure or a staff member’s leave does not by itself establish a statutory adjustment. Where the annual deadline or a special transaction date needs different treatment, resolve that rule before extending the calendar entry.

2026 relief: preserve the tax-year-2025 boundary

DGT announcement PENG-31/PJ.09/2026 , implementing KEP-71/PJ/2026, concerns corporate tax year 2025, including part-year returns. It provides administrative penalty relief for specified annual filing and PPh 29 payment actions performed after the relevant due date and within one month afterward, including the stated extended-return underpayment category. It does not create a permanent May corporate deadline.

For a calendar-year 2025 return, keep April 30, 2026 as the ordinary annual filing date and record the relief separately when its conditions are met. For a different year-end, use the actual relevant due date rather than copying the calendar-year headline. Do not carry this relief into the company’s 2026 tax-year calendar without a new applicable basis.

The Ministry of Finance regulation history identifies subsequent amendments to PMK 81/2024, including PMK 1/2026 . Keep a source-check date in the calendar so an old spreadsheet remains reviewable when the legal framework or official guidance changes.

Close entries against evidence and expose failures

A payment instruction, billing code and submitted return are different objects. Require the close reviewer to inspect the evidence belonging to the correct obligation. A payment receipt does not generally prove that a separately required return was filed. Conversely, a return receipt does not prove that every amount entered in the return has been paid correctly.

There are specific exceptions. Under the periodic reporting rules , validated PPh 25 payment can fulfil reporting, while a nil PPh 25 installment is exempt from that reporting obligation. Unified-return reporting also has a no-relevant-transaction exception, and employment-related reporting has its own conditions, including final-period rules. Record the applicable basis instead of demanding the same receipt from every row.

1. Match payment evidence to the taxpayer, tax type, period and amount. Retain the validated payment reference, not just the request to pay.
2. Match each separately required return to its electronic filing receipt, such as Bukti Penerimaan Elektronik (BPE), and preserve the submitted return version with its timestamp.
3. For a reporting exception, retain the reviewer’s basis and supporting period assessment. Distinguish “not required” from “not yet prepared.”
4. Reopen a task if the evidence names another period, the return was rejected, the payment failed or the recorded exception does not cover the obligation.

When submission fails near a deadline, preserve the error, attempted action, time and account context, assign a person to resolve the problem and escalate internally. A support request or screenshot is useful incident evidence; it should not be entered as a successful filing receipt or assumed to suspend the legal deadline.

Review outstanding entries after the due date as well as before it. A return that was omitted needs completion and an assessment of its consequences; shifting its reminder into the next month conceals the original failure. Where an amendment becomes necessary, link the replacement evidence to the earlier record so the audit trail identifies the version that remains operative.

Finally, test retrieval. A calendar marked closed is weak if only a former employee or provider can locate the receipt. Store company-accessible copies and give the reviewer enough identifying information to recover the official record without relying on a message that says “filed.”

Approve the tax calendar only when every entry is supported

Approve the calendar when each applicable obligation has a period anchor, an evidenced date calculation, an owner and a defined completion record. Give unresolved applicability questions and unsupported extensions a visible escalation status, then resolve them ahead of the earliest payment or filing exposure.

At the next review, start with changes in tax status, year-end, transactions, responsible people and official rules. Update the affected entries and preserve their history. The useful output is a calendar the company can operate and prove, with annual and periodic duties remaining identifiable even when their deadlines fall on the same day.