If the payroll statement continues to display employees who were already dismissed in a previous period, the cause is almost always the same — the report's own selection settings. This is not an accounting error and not a data problem: it is enough to adjust the condition on the dismissal date in the filter. Open the payroll statement settings, go to the "Selection" section, find the parameter related to the dismissal date, and change the boolean value of this condition to "No value". After this, employees dismissed earlier will no longer be included in the calculation for the current month.
Why dismissed employees appear in the statement
The payroll statement in 1C:Accounting for Kazakhstan is built based on data about accruals and deductions for the selected period. The selection in the report determines which employees to include in the sample. When the condition on the dismissal date is set as a boolean value (that is, rigidly "true" or "false"), the report may interpret it so that the sample includes all employees with a filled or unfilled dismissal date — depending on how the checkbox is set. As a result, those who were dismissed in previous periods "stick" to the statement for the current month.
It is important to understand: the accruals themselves are most often zero or absent, but the employee's row is still displayed, which makes it difficult to check and reconcile the totals. This is especially noticeable when there have been several dismissals during the period and the list of employees in the report turns out to be longer than the actual staff.
Step-by-step correction procedure
- Open the payroll statement for the required period.
- Go to the report settings (the "Settings" or "Show settings" button, depending on the report form).
- Find the "Selection" section.
- In the list of selection conditions, find the parameter related to the employee's dismissal date — it is precisely responsible for whether to show dismissed employees in the statement for the current period.
- Find the boolean value of this condition and change it to "No value".
- Generate the statement again.
After this change, the statement will be generated correctly, and employees dismissed in the previous period will no longer be included in the calculation for the current month.
If the correction did not help
If after changing the value the selection still works incorrectly, check whether the condition is duplicated in other parts of the report settings. Sometimes an identical or conflicting condition on the dismissal date is set in several places at once — for example, in the main selection and in a nested grouping or in the user selection settings. In this case, one condition "overrides" the other, and the report continues to display extra employees. However, most often a single correction is enough.
What else to pay attention to if the problem persists:
- Make sure that you are making changes to exactly the report variant that you use when generating (the report may have several saved setting variants).
- Check whether the "problematic" selection is saved as the default setting — then the changes need to be saved, not just applied once.
- Verify the report period: if it covers the month of dismissal, the employee will naturally be included in the statement with the final calculation for the month of dismissal.
How to make sure the data is correct
Before changing the settings, it is useful to understand the nature of the rows for dismissed employees. Open the card of such an employee and check the dismissal date in the HR documents. If the dismissal is processed correctly and refers to a previous period, and there are no accruals in the current month — then the matter is indeed only in the report selection, and not in the accounting data. But if a dismissed employee has accruals in the current period (for example, an additional accrual, compensation, a payment upon dismissal), then they appear in the statement justifiably, and there is no need to remove them from the report — this would be a discrepancy with the actual accruals and deductions.
Typical mistakes
- Changing the period instead of the selection. Narrowing the period does not solve the selection setting problem and may distort the statement totals.
- Editing a one-time setting but not saving it. The next time it is opened, the report again pulls up the old selection.
- Deleting rows manually. Manually deleting employees from a finished report does not eliminate the cause and leads to discrepancies upon regeneration.
- Confusing a dismissed employee without accruals and a dismissed employee with a payment upon dismissal. In the second case, the row must be in the statement.
- Not checking for duplicate conditions. The same condition in different parts of the settings conflicts with itself.
What to check
- The value of the condition on the dismissal date in the "Selection" section is set to "No value".
- The selection is not duplicated in other parts of the report settings (nested groupings, user selections).
- The changed setting is saved in the report variant being used, not applied once.
- The report period corresponds to the required month and does not cover the month of dismissal unnecessarily.
- For dismissed employees remaining in the statement, there are no real accruals or deductions in the current period.
- The dismissal date in the employee's HR documents is filled in correctly.
After performing these checks, the payroll statement will reflect only those employees who actually belong to the current settlement period, and the reconciliation of accruals, deductions, and totals will become clear and correct.