Insurance and reporting issues
Rifena stores operating data and states confirmed by users. It does not transfer money or submit a report to an external authority automatically.
The insurance preview shows Missing salary or Zero amount
- The contribution period, policy, and employee are correct.
- The contract has a salary and effective dates covering the period.
- The employee is enrolled in the intended insurance policy.
- The active contribution settings were confirmed by the company.
Correct the contract, enrolment, or policy on its owning screen. Return to Payroll → Insurance → Create contribution batch and create a new preview. Do not enter a temporary amount merely to make the row valid.
Expected result: the row becomes Ready with a reviewed contribution amount.
Still not working? Prepare the period, policy, contract state, and exception label. Mask real salary in any screenshot.
A row cannot be selected, or a saved row is no longer Ready
- The row is Recorded, Remitted, Zero amount, or another exception.
- The period and policy match a row already in Payment history.
- The previous Save to ledger action reported success.
Open Payment history and find the period first. Continue from the existing row when present; only Ready rows need to be selected and saved. For an exception, correct its cause and generate another preview.
Expected result: each employee and period has the necessary history row without a duplicate.
Still not working? Send the period, policy, row label, and latest save result. Do not save repeatedly.
Reconciliation still differs after the company paid
- The reconciliation month is correct.
- The matching Payment history row is marked Paid.
- Payroll and contribution-ledger rows belong to the same employee and period.
- The row is Mismatch, No ledger entry, or No payroll deduction.
If the money was genuinely remitted, record that result on the correct history row. If one side is missing, follow the payroll-run or ledger link and correct its source. Refresh reconciliation after one change. Do not edit the aggregate difference directly.
Expected result: the row becomes Matched, or has an explained cause and owner.
Still not working? Prepare the month, difference group, payroll deduction, and recorded remittance. Mask unrelated personal data.
The required report type is missing, or the report has data warnings
- The report type appears among those currently supported by the interface.
- The year, state, and original-or-amendment chain are correct.
- The warning points to company, employee, payroll, or tax data.
For a supported report, correct the named source and then regenerate or create an amendment according to the current state. If D02 is absent from the dialog, use the external process verified by the company; this is a current product limitation.
Expected result: the correct report and period are available for review, or work moves to a controlled external process.
Still not working? Send the report type, year, state, and warning text. Do not attach a complete real tax report.
The filing was submitted, or the portal returned an outcome, but Rifena is not in the corresponding state
- The external portal returned a submission reference or receipt.
- The correct report and version in the chain are open.
- Rifena displays Generated, Submitted, Accepted, Rejected, or another state.
After receiving the reference, open the report, select Mark as submitted, and enter it. When the portal returns an outcome, use Portal accepted or Portal rejected only on the Submitted version and only after verification. Do not reverse a recorded portal outcome directly.
Expected result: Rifena stores the reference and the matching Accepted or Rejected state, while the company retains the external receipt.
Still not working? Send a partially masked reference, submission time, portal state, Rifena state, and visible actions. If an outcome was recorded incorrectly, stop and escalate instead of creating an opposing record.
See Insurance and statutory reports for the complete journey and boundaries.