What Rifena does automatically

Modern software should do the repetitive work for you, but it must say what it does on its own. This page lists what Rifena performs automatically, when, and on which data, so you can trust it and still stay in control.

Rifena performs some transitions when their conditions are clear. “Automatic” does not mean Rifena makes a responsible person’s decision, transfers money, or submits a file to an external authority.

Swipe horizontally to see the condition, result, and check still required.

State-driven transitions

When this condition occurs	Rifena does this	A person still checks
Every required payment order for a payroll run is confirmed complete	The run becomes Paid	Order totals, exceptions, and correct payslip recipients
An approved HR event reaches its effective date	The event’s change applies to the profile	Profile, organisation, access, approvers, and related configuration
An offboarding employee passes the last working day and meets lifecycle conditions	Rifena creates the completion step and the profile becomes No longer employed	The checklist, final payroll, and access revocation genuinely completed
Pending leave or overtime is withdrawn or cancelled	The request becomes Cancelled	Reserved balance or pending period data updated correctly
A tax-exemption request meets the organisation’s automatic-approval configuration	The request may move directly to Approved	Exemption type, evidence, and Approved amount match the basis
An active code-generation rule applies to the form	A business code is created under the rule	Correct code type, format, and uniqueness

Notifications and reminders

Rifena may notify users when a record needs a decision, reaches a result, or approaches a meaningful milestone. Common groups include:

• requests and approvals;
• contracts, probation, and employee lifecycle;
• payroll runs and payments;
• insurance, reports, and due dates; and
• KPI and training.

Delivery depends on Account → Notifications, browser or device permission, and organisation configuration. Do not treat a fixed execution time in a guide as a promise that every organisation receives the same reminder at that time.

What does not happen automatically

You just did this	Do not infer this result
Added someone to a group	Primary department, roles, and approval workflows all changed
Applied an HR event	KPI, access, and payroll configuration now match completely
Marked an onboarding or offboarding checklist item complete	Assets, external accounts, or final payroll were handled in reality
Corrected a source after creating a payroll run	The existing run recalculated itself
Approved an advance or expense claim	Money was transferred to the recipient
Saved the insurance ledger or selected Mark as paid	Insurance money was remitted without the company making the payment
Generated or downloaded a statutory report	The report is complete, signed, or submitted
Recorded a report as Submitted	The portal accepted or rejected it; a user must still verify and record the matching outcome
Saved SSO provider details	The provider is Active and Enforce SSO is safe to turn on

When an expected automation did not occur

1. Confirm that the source condition is met and the state is saved.
2. Check the effective date, last working day, or every related order.
3. Check notification preferences when only the reminder is missing.
4. Refresh once and read history or the timeline.
5. If the result remains wrong, choose the symptom under Support and state which condition you believe is met.