The payslip or the batch is a simulation

Symptom

A calculated batch has no Validate button, only Calculate, Take out of the batch, Reset to draft and Delete batch. A simulation notice appears at the top of the batch and of each payslip.

Message

Copied from the screen with a user that has only the Payroll Processor profile, in the batch “Simulação de novembro de 2026”.

At the top of the calculated batch:

“The batch is “Calculated” and it is a simulation: it has no official effect, so it is not validated. It can still be calculated again; while no payslip is validated, “Back to draft” or “Delete batch” undo it (a reason is asked).”

At the top of each payslip:

“Simulation: this payslip only shows what would happen. It is never validated, paid, accounted or declared, and it has no official effect.”

In Take out of the batch, when you choose a payslip of the simulation, write the Reason and press Take out of the batch (the parts in italics change from case to case):

“Payslip “employee name (01/11/2026 — 30/11/2026)” cannot change between a simulation and a real batch. What happened: that would turn a simulation into an official payslip (or the reverse). How to fix it: create a new payslip in the batch you want.”

On the screen, the batch does not refuse validation: it hides the Validate button. Whoever calls fiscaldoo through an integration receives the refusal in writing. These sentences came from a direct call, because on the screen there is no button that makes them appear:

• When validating the batch:

  “Batch “Simulação de novembro de 2026” is a simulation. What happened: a simulation has no official effect, so it is never validated, paid or closed. How to fix it: create a batch of a real type.”

• When validating a payslip:

  “Payslip “employee name and period” is a simulation and cannot be validated. What happened: a simulation has no official effect, so it is never validated, paid, accounted, declared or sent for payment. How to fix it: create a payslip in a real batch with the same data and process that one.”

• When trying to remove the simulation mark:

  “The simulation mark cannot be changed. What happened: a simulation never becomes an official payslip (and an official one is never a simulation). How to fix it: create a new payslip in the right batch.”

Verified causes

• The batch was created with Type “Simulation”. The name then starts with “Simulação”, like “Simulação de novembro de 2026”, and it is used to see the result of a month before processing it.
• A simulation does not turn into a real one. If it did, a payslip without validation would have official effect. That is why the payslip's mark does not change, and a payslip does not move out of a simulation batch nor into a real batch.

What to check

1. The Type column of the list in Payroll › Process › Process the month.
2. Whether the batch name starts with Simulação.

How to fix it

Who does it: the Payroll Processor or the Payroll Administrator. Each of these profiles, on its own, has the Reset to draft and Delete batch buttons on the simulation batch.

1. If the simulation is no longer needed, open the batch and press Delete batch. The window warns: “Batch “Simulação de novembro de 2026” and its 8 draft payslips will be deleted. Nothing validated or paid is touched: if any payslip is validated or paid the batch is refused. The deletion is recorded in the audit log with your reason.” Write the Reason and press Delete batch. Without a reason, you get “Some required fields are empty. Fill in the fields marked in red to be able to save.”
2. Open Payroll › Process › Process the month and press New.
3. In Type, choose a real type, for example Regular, and confirm the period (Period start and Period end).
4. Continue as in How to process the month's payroll.

Expected result

The new batch reaches Calculated with the Validate button, and the payslips no longer show the simulation notice.

When to contact support

• A batch with another Type shows the simulation notice on the payslips.

Information to send

Follow How to ask support for help and what information to send, with the batch name and the type.