Known limitations
This page contains only limitations that remain true in the current interface. A limitation is not always a defect. The important point is to know which part Rifena does not complete for you and how to continue without damaging data.
An organisation-chart draft does not appear on another device
Current boundary: Save draft keeps edits in the browser and device in use. A draft is not the published organisation structure.
Finish review on the same device. When the structure is ready for others, select Publish from draft and check for Synced.
Reviewed 23 August 2026.
D02 is absent from Generate statutory report
Current boundary: new-report generation currently supports 05/QTT-TNCN and 01/PLI. D02-TS and D02-LT do not have a qualified new submission journey; historical records may remain visible for reference.
Prepare and submit D02 through the external process verified by your company. Do not use a historical file or one marked as draft as an official submission without separate verification.
Reviewed 23 August 2026.
A generated statutory file is not ready to submit immediately
Current boundary: the interface warns that 05/QTT-TNCN and 01/PLI may be only partially populated. Rifena does not confirm the contents, apply a digital signature, or submit the report to an external portal.
Open every file, verify all mandatory fields, complete the company's statutory review, and use its approved submission channel. Mark the report submitted only after receiving a real submission reference.
Reviewed 23 August 2026.
A group or HR event changed, but related configuration did not
Current boundary: group membership, primary department, roles, data scope, approvers, KPI, and payroll configuration have separate owners. One people change does not update every other layer automatically.
After the change takes effect, use the hand-off checklist to inspect every affected layer. Update each item on its owning screen and verify with a representative account.
Reviewed 23 August 2026.
SSO remains Configured and Enforce SSO is unavailable
Current boundary: saving provider details does not make the provider active. The external OIDC/SAML sign-in connector is not live, so employees cannot sign in through the saved configuration.
Keep Rifena-account sign-in and a safe administrative recovery path. Escalate connector activation to the identity team; test and consider Enforce SSO only after the interface confirms the provider is genuinely Active.
Reviewed 23 August 2026.
Payment or submission was recorded in Rifena, but nothing was sent externally
Current boundary: actions such as Mark as paid and Mark as submitted record a result completed by the user. They do not transfer money, sign a file, or submit it for the user.
Complete the transaction or submission through the bank, signing software, and external portal verified by the company. Update Rifena only after receiving a real result, reference, or receipt.
Reviewed 23 August 2026.
For behaviour outside these boundaries, choose a symptom under Support or prepare a support request.