Compliance Dashboard

Overview

The compliance dashboard at Compliance module is VillaTax’s operational control surface for filing status, overdue obligations, and risk visibility. It is designed to answer a practical question: based on the records currently inside the system, what still needs attention before compliance risk gets worse?

This is not a static legal memo and it is not a government filing portal. It is an internal monitoring layer built on top of declarations, reports, bookings, documents, and other fiscal records already stored in VillaTax.

What the Compliance Module Actually Checks

The safest way to understand the module is in two layers:

1. a compact checklist of core compliance signals
2. an overdue-obligation and risk view that highlights where follow-up is needed

That distinction matters because the compliance page is not trying to express every possible Indonesian obligation in one giant legal matrix. It is giving operators a working cockpit for the obligations VillaTax actively monitors.

The Core Checklist

The checklist is built around a small number of high-value control points, including items such as:

• whether the organization has an NPWP on record
• whether NIB-related setup is present in the data
• whether recent PBJT and PPh declaration records are recorded for the due period
• whether the relevant LKPM report exists when applicable
• whether guest-passport collection signals are present in booking-linked records

The point of the checklist is not to replace detailed review. It is to make obvious gaps visible quickly.

Due Period Logic and Deadlines

VillaTax applies due-period logic from the compliance helper layer rather than from ad hoc UI copy. The important deadlines visible in code are:

• PBJT: deadline on the 15th of the current month for the prior period
• PPh: deadline on the 10th of the current month for the prior period
• LKPM: deadline on the 10th of the first month of the following quarter for the relevant quarter

Those deadlines come from the period helpers and overdue-obligation logic in the compliance layer, and they are the safe dates to describe publicly from the current codebase.

The product uses these dates to determine:

• which period is currently due
• when an obligation becomes overdue
• what should appear as needing attention in the dashboard

Overdue Obligations

The stronger part of the module is the overdue-obligation handling. VillaTax can surface when a monitored obligation is already late according to the stored record state and the due-period logic above.

Examples of obligations that can feed this layer include:

• PBJT
• PPh declaration-related status
• LKPM
• PPh 26 director-related follow-up in the cases the product supports

This is useful because it turns compliance into something operational. Instead of asking a user to remember every filing cycle manually, the dashboard can surface where the current record state still looks incomplete.

Risk Signals vs. Checklist Score

The compliance page should be described carefully here. There are multiple “risk” ideas in the product and they are not all the same thing.

The dashboard-side risk logic visible in code accumulates points from missing or problematic factors such as:

• missing NPWP
• missing NIB-related setup
• expired documents
• incomplete BPJS coverage on staff
• missing recent Banjar payments
• untaxed bookings
• unreported foreign travellers
• missing passport collection

That risk score is then mapped into levels like:

• low
• medium
• high
• critical

The safe public claim is that the compliance area helps surface both checklist completion and broader fiscal-risk signals. It is not safe to publish a simplified fake formula unless it matches code exactly.

How It Connects to the Rest of VillaTax

The compliance module is valuable because it sits in the middle of several other records:

• bookings can create passenger, passport, or tax-related follow-up
• declarations and reports feed filing-status visibility
• documents affect expiry and readiness signals
• organization setup influences which obligations matter

This makes compliance a coordination screen, not just a status board. It becomes the place where users notice whether the rest of the system still tells a coherent story.

What It Does Not Do

The module should be described honestly:

• it does not file directly with DJP or BKPM for the user
• it does not prove external submission automatically unless the user records it in VillaTax
• it does not replace formal professional review for edge-case obligations outside the supported scope

Its job is to keep supported obligations and risk signals visible, not to impersonate a government portal.

Practical Use

The best way to use the page is operationally:

1. review the checklist for obvious missing setup or filing-state gaps
2. review overdue obligations and deadline proximity
3. use that view to decide which tax, document, booking, or entity module needs attention next

That makes the compliance dashboard one of the most useful “what should we fix now?” screens in the product.