Fiscal Setup

Overview

Fiscal setup is the configuration layer the rest of VillaTax's tax stack depends on. Before compliance checks, tax calculations, Coretax readiness assessments, or annual reporting can produce reliable results, the system needs to know what kind of entity it is working with. That is exactly what Fiscal Setup is for.

This is not a one-time admin step that can be approximated. Incorrect setup propagates errors into every downstream module, compliance scores become unreliable, tax rates resolve incorrectly, obligation chips on the organizations page route to the wrong modules, and Coretax readiness flags become meaningless. Getting this right at the beginning matters.

What Gets Configured Here

Fiscal setup collects the entity-level inputs that shape how tax logic is applied across the product.

Legal form: the organization type (Perorangan, CV, PT local, PT PMA) determines which tax regimes apply, which obligations are relevant, and how income is taxed. The wrong legal form produces the wrong tax calculation framework.

Tax identity

• NPWP (15-digit tax registration number), required for DJP declarations, withholding records, and Coretax interaction. Missing NPWP triggers compliance warnings across the entire product.
• NIK (national ID), required for Perorangan owners. Since PMK 112/2022, NPWP is linked to NIK for individual taxpayers.

PKP status: declares whether the organization is registered as a PKP (VAT taxpayer). This controls whether PPN (11%) applies to bookings and whether e-Faktur invoice numbering is required. Organizations above the annual revenue threshold are required to be PKP.

KBLI codes: the business activity classification codes (Kode Baku Lapangan Usaha Indonesia) that define the formal nature of the business. These affect which obligations apply and which investment reporting requirements (LKPM) are triggered.

Fiscal nature: whether rental income is treated under the final PPh 4(2) regime or as general income. This is one of the most consequential configuration choices: PPh 4(2) final means a flat 10% rate on rental income; general income flows into the broader income tax calculation instead.

PTKP status (for Perorangan), the personal tax exemption category (TK/0, K/0, K/1, K/2, etc.) used in calculating the individual owner's income tax.

Why Each Field Matters Downstream

None of these fields is cosmetic. Each one changes real behavior:

• Legal form → determines PPh regime, BPJS obligations, and which corporate tax modules are shown
• NPWP → compliance warnings across the compliance dashboard, Coretax readiness, and export packages
• PKP status → triggers PPN on bookings, enables the VAT invoices module, affects e-Faktur readiness
• KBLI codes → shapes which fiscal obligations are displayed on the organizations page as obligation chips
• Fiscal nature → changes whether bookings generate PPh 4(2) final journal entries or general income entries
• PTKP → affects PPh calculations for Perorangan

What Happens If Setup Is Incomplete

VillaTax does not silently ignore incomplete setup. It surfaces gaps:

• Missing NPWP → a persistent compliance warning appears across the dashboard
• Missing legal form → tax calculations default to the most conservative interpretation
• Missing PKP status → PPN module is inactive even if the organization should be registered
• Unset KBLI codes → obligation chips on the organizations page show a limited set

These signals make incomplete setup obvious without blocking the product from being used. But reports, compliance scores, and declarations produced before setup is complete should be treated as provisional.

Relationship to Other Modules

Fiscal setup feeds into almost every tax-facing module:

• Tax engine: uses legal form and fiscal nature to choose the right calculation path per booking
• Compliance: uses NPWP presence and legal form to determine which obligations are active for the organization
• Coretax readiness: validates NPWP format, PKP consistency, and NSFP configuration
• Organizations: uses legal form and KBLI to generate obligation chips and route each chip to the right module
• Corporate financials: uses legal form to show or hide PT/CV-specific tax review panels
• Staff declarations: uses legal form to determine BPJS obligation scope

When to Update Setup

Fiscal setup is not locked after initial creation. If the organization's status changes, the setup should be updated promptly. Outdated configuration means the product is working from wrong assumptions.

Common update triggers:

• Reaching the PKP revenue threshold and registering as a VAT taxpayer
• Converting from Perorangan to CV or PT
• Adding new business activities (new KBLI codes)
• Change in PTKP status (Perorangan) due to marriage or children

After updating, re-check the compliance dashboard and Coretax readiness panel to confirm the new configuration resolved any previous flags.

What Setup Does Not Replace

Fiscal setup captures the facts about the entity as they exist today. It does not provide legal advice about what those facts should be. If an organization's structure is uncertain (for example, whether it should be PKP, or which fiscal nature applies) the regulatory assistant at Regulatory Assistant can help navigate the question, but a licensed tax advisor should make the final determination for complex cases.

Getting Started

Open Fiscal Setup and complete all required fields before using the tax engine, compliance dashboard, or export workflows. The correct sequence: legal form first, then NPWP and NIK, then PKP status and fiscal nature, then KBLI codes. Each field you complete reduces the number of warnings and improves the reliability of everything downstream.