Staff Declarations

Overview

Generating payroll is only part of the staff workflow. The next problem is making sure the related declaration and payment follow-through does not get dropped once salary records have been created. The staff declarations module at Staff Declarations module exists specifically to keep those downstream obligations visible, organized, and actionable.

Payroll failures often happen not at calculation time, but after it. The numbers are produced, but the team loses visibility on which period still needs a declaration submitted, which payment is pending, and which record needs later review. This module addresses that gap.

What It Tracks

The staff declarations feature keeps payroll-related obligations visible across periods. That includes:

• Declaration status per period: whether payroll-related obligations for a given month have moved from generated to declared
• Payment status visibility: whether the corresponding BPJS contributions and PPh 21 withholding amounts reflect actual payment follow-through
• Employee annual summary context: the trail of payroll records per employee across the year, which matters at year-end and during staff-related compliance review

The module does not replace the underlying payroll calculation. It picks up after payroll has been run and gives the admin team a way to track what still needs to happen.

Why This Matters Operationally

Indonesian payroll obligations are periodic and legally time-sensitive. BPJS contributions are due monthly. PPh 21 withholding must be deposited and reported on schedule. Missing a period does not just create an administrative gap; it can create penalties and inconsistencies in declarations that take effort to correct.

The practical value of this module is that it surfaces period-by-period status in a single view instead of relying on calendar reminders, side spreadsheets, or informal knowledge about which months were handled.

Relationship to Payroll and Accounting

This feature sits downstream of payroll, not parallel to it:

1. Employee records are set up at Staff & Payroll module
2. Payroll is calculated and payslips are generated at Payslips module
3. Staff declarations track the follow-through after that point

That sequence mirrors how real admin teams work. Payroll produces numbers. Declarations confirm those numbers have been handled on the administrative and payment side.

The staff declarations layer is also adjacent to accounting. Payroll-related costs and withholding amounts feed into journal entries in the general ledger. Keeping declaration status visible helps ensure the accounting record reflects what actually happened, not just what was computed.

BPJS Contribution Context

BPJS is part of what staff declarations help track. The contributions involved in a standard payroll period include both employee-side deductions and employer-side contributions. For JKK, JKM, JHT, JP, and JKes, the obligation does not end when the payslip is generated. The contributions need to be submitted to BPJS. Keeping that follow-through visible is part of what the declarations module supports.

What It Does Not Do

This module should not be framed as a direct portal submission engine for BPJS or DJP. Its value is workflow visibility and status tracking inside VillaTax. Actual submission to external portals (BPJS, e-SPT) still requires the relevant external system. VillaTax keeps the operational record and helps the team stay aware of what is pending.

Getting Started

Use Staff Declarations module after payroll has been generated for the month. Review the period status to confirm which obligations have been handled and which still require follow-through. The module is most useful when payroll is run consistently each period and the declaration status is updated as follow-up is completed. Over time, the period-by-period trail becomes a reliable operational record of how staff obligations were managed.