Types of notifications you may receive
Every notification type in CLVR Benefits, what each colored label means, and what to do with an expense update, an AI review, a changes-requested note, an added-as-reviewer task, an overused-allowance alert, a partner benefit update, and an answer to a report you sent CLVR.
Every notification in CLVR Benefits is written the same way: a title that says what happened, a short description, and, on the ones that are waiting on you, a small orange tag that says what they are waiting for. They all gather on the Notifications tab of your account panel, and the unread ones drive the dot on your avatar until you read them. This article walks through each kind, what it means, who it is meant for, and what to do with it.
How to read a notification
Each row shows a title in bold while it is unread, a short description, and a time such as 5 min ago or yesterday. A row that asks you for something carries one of three tags after its title until the task is done, whether or not you have read it:
- Awaiting your review on a colleague's expense report you have been asked to review, and on an expense of your own a reviewer sent back.
- Needs your decision on a request from an employee, and on an overused-allowance case, for the HR side.
- Waiting for your choice while an election window is open and you have not chosen.
Rows without a tag keep you informed and never block anything. Most rows open the thing they are about: anything about an expense opens it in a window right where you are, and the rest open the relevant page.
Everything, titles and descriptions included, is shown in the language you use CLVR in, and changes with it.
Expense update
When a reviewer finishes deciding on an expense you submitted, you get an update so you learn the outcome without opening your expenses to check. You receive one in two situations:
- Your expense was approved. CLVR waits until the report is fully approved before telling you, so if more than one reviewer is involved you hear about it once, at the end, not after each step.
- Your expense was declined. You are told as soon as a reviewer declines it.
The title names the reviewer and the decision, for example Anna has approved your expense report. Select the row to open that report where you are, with its current status and cost breakdown. If it was declined, read the reason there, fix the issue, and submit it again.
An update is informational, so it carries no tag. It stops counting toward the badge as soon as you read it, and stays in your list.
For the HR side there is one more: [Employee] updated an expense report, sent when an employee resubmits a report that was returned for changes, so the review can continue.
AI review
If your company has AI auto-approval turned on, CLVR can review a wellness (friskvĂĄrd) expense the moment you submit it and act on it within seconds, instead of waiting for a person.
AI auto-approval is a company setting your HR team controls, and today it only applies to the wellness (friskvĂĄrd) category. If your company has not turned it on, you will not see these notifications.
When AI auto-approval reviews a wellness expense, one of a few things happens:
- Approved. The expense clears for reimbursement through payroll, just like a human approval. You get the usual approval confirmation by email; there is nothing more to do.
- Declined. CLVR could not approve it. You get a notification titled Your expense report needs attention with the reason, and you can fix it and submit again.
- Returned for changes. CLVR needs something adjusted first. You get a separate needs changes notification with instructions.
- Sent to a person. If CLVR is not confident enough to decide, it leaves your expense pending and a member of your HR team reviews it as normal. You do not get a notification in this case.
If your expense was declined, open the report (from the notification or under My Benefits) to read the reason in full, then choose Edit & Resubmit: the form reopens pre-filled with your earlier details so you only correct what was flagged. A decision made by AI is not the last word; a member of your HR team can review it and reverse it.
Your HR team gets its own row for every AI decision ([Employee]'s expense report was auto-approved by AI, and so on), with the confidence and the reason, so they can keep an eye on what the AI is doing.
Your expense report needs changes
A row titled Your expense report needs changes means a reviewer looked at an expense report you submitted and needs you to change something before they can approve it. The description is the reviewer's note, so you can see what to fix without opening anything; if the instructions are long, they are shortened here and shown in full on the expense itself.
This row carries the Awaiting your review tag until you resubmit, not just until you have opened it.
Select the row to open the report where you are. Because it is waiting for your changes, it opens ready to edit, with two sections: Original Expense Report (the version you first submitted, for reference) and Update your expense report (where you make the requested changes).
The moment you resubmit, the tag is gone. There is no need to start a brand new report.
Please review a colleague's expense report
Please review [Name]'s expense report (or benefit purchase) means a colleague's expense has been routed to you for review. You receive it in two situations: someone adds you by hand as a reviewer for a specific report, or your company uses an approval flow that routes reports to a group you belong to, so CLVR assigns you automatically. If it is still waiting after a while, a Reminder: review [Name]'s expense report follows.
While your review is still pending, the row carries the Awaiting your review tag. Select it and the expense report opens in a review window right where you are, on whatever page you have open. Check the receipt and details, then leave your decision. Once it is recorded, the tag is gone.
The tag also clears on its own if someone else finalises the report first (for example another reviewer approves or declines it), or if your HR team removes you as a reviewer. For how a companion email fits in, see How email relates to your in-app review notifications.
Category changed
If your HR team moves an approved expense of yours to a different category, you get Category changed: [from] to [to], with their reason as the description. Select it to open the expense. Nothing is required from you.
Requests that need a decision (HR side)
If you are among the people who decide on employee requests, you get a row for each one:
- A red day request needs your decision, when an employee asks to move a public holiday.
- A work equipment request needs your decision, when an employee asks for a phone.
- A compassionate leave request needs your decision, when an employee applies for leave, with the dates.
Each carries the Needs your decision tag and opens the Requests page, with the request in front of you. The tag clears once the request is decided, by you or by another approver.
The employee gets a row back with the outcome (Your red day was moved, Your work equipment request was approved, Your compassionate leave request was declined, and so on), including any note the approver wrote, and it opens the benefit the request was made from.
Overused allowance on termination (HR side)
Overused benefit allowance on termination goes to everyone with the HR role at your company, not to every employee. It fires when an employee who is leaving has already spent more than the benefit allowance they are entitled to keep, as soon as a termination date is set, so you can decide how to handle the difference before the person leaves.
CLVR creates it when both of these are true at the moment a termination date is set:
- The termination date falls inside the current benefit period.
- Their approved and pending expenses in that period add up to more than their pro-rated allowance.
A pro-rated allowance is the share of the full yearly allowance that matches the days the person was employed in the period, so someone leaving partway through keeps less than the full amount. Expenses that were declined, and benefits paid through salary, are not counted toward the total.
Pro-rating and overuse are part of the Swedish benefit rules, so this notification applies to companies on the Sweden setup. Whether an allowance is pro-rated on termination is a choice you make when you set the leaving date.
The description names the employee and the overused amount in kronor (kr), for example: "Anna Andersson has overused their benefit allowance by 1 200 kr. Please choose how to handle the reimbursement." Every member of your HR group gets the same row. Selecting it opens the leaving employee on your Employees page, where you decide how to settle the amount. A common route is to recover it through payroll: the overused amount is recorded against the employee and can be included when you generate a payroll report.
This row carries the Needs your decision tag until the case is handled, even after you have read it.
Choosing your vacation days or pension
If your company runs an election for vacation days or pension, you get Choose your vacation days or Choose your pension when the window opens, with the period it covers and the date it closes. Two days before it closes, if you have not chosen, Two days left to choose follows. Both carry the Waiting for your choice tag and open the benefit page where you make the choice; the tag is gone the moment you save.
Afterwards you get a confirmation: Your vacation days are set with your days and new monthly salary, or Your pension choice is saved while the window is still open and Your pension choice is final once it has closed. Your HR team is told when an employee chooses their pension.
Manager changes
When your manager leaves and someone else takes over, you get [Name] is now your manager; the new manager gets You are now the manager for [n] team members. Both are informational and open nothing.
Partner benefit updates
When your company offers partner benefits, CLVR keeps you posted as one moves through its lifecycle, from your company first expressing interest to the benefit going live and any later changes. These rows are informational: they tell you what happened and ask nothing of you.
Partner benefits are a feature your company turns on. If your company has not enabled them, there is nothing to notify you about.
Most lifecycle updates (Partner benefit pending CLVR review, Partner benefit: next step, Partner benefit suspended, Partner benefit resumed, Partner benefit adjusted) go to your HR team, because they manage the agreement, and open the partner benefits page.
The one most employees notice is activation. When a partner benefit goes live, everyone at your company gets New partner benefit telling you it is now available in the benefit store. Select it to open that benefit page in the store, where you can read the details and use it like any other benefit.
Your reports to CLVR
When you send CLVR a report, with Report an issue in the account panel or Report a problem on the Reports page, you hear about it here as CLVR works on it. Each row names the report by its reference, such as CLVR-123:
- [Name] replied on CLVR-123, with the start of the reply as the description.
- [Name] is waiting on your answer, when CLVR needs something from you before they can go on. The description is the reference and the first sentence of their question.
- CLVR-123 is in progress, when someone at CLVR starts working on it, with your subject as the description.
- CLVR-123 resolved, with [Name] marked it resolved. as the description.
These go to whoever sent the report. For a problem in a payroll file, the rest of your company's HR team gets them too, since you share the file. Select a row to open the report: a payroll file problem opens beside its period on the Reports page, and anything else opens in My reports in the account panel, where you can read the whole thread and reply. A reply from CLVR is also emailed to the person who sent the report; status changes are not.
For the HR side there is one more: New file ready for [month year], with the description We rebuilt it after CLVR-123. Download it again. It is sent when CLVR rebuilds a payroll file after a reported problem and somebody at your company had already downloaded the old one. Select it to open that period on the Reports page and download the new file.
These rows are informational and carry no tag, not even Waiting on you: the red dot on My reports in the account panel shows that one until you answer.
Troubleshooting
- A notification I expected is not in the badge. The dot on your avatar counts only unread rows. Open the Notifications tab to see everything, including ones you have already read.
- I read it but it still shows a tag. A tag stays until the task is done, not just until you open the row. Finish the task and it clears; a review tag also clears if someone else finalises the report.
- I got an update but the expense status still looks pending. A report can need more than one approval. You only get an approval update once it is fully approved, so a "pending" status means another reviewer still has it.
- My wellness expense is still pending, with no AI notification. CLVR was not confident enough to decide, so it left the report for a person on your HR team to review. No action is needed from you.
- I am an HR user and the overused amount looks higher than I expected. It compares total spend against the pro-rated allowance for the days worked in the period, not the full yearly allowance, so a part-year leaver has a smaller allowance to compare against.
- A partner benefit update mentions setup steps I cannot do. Those updates are aimed at your HR team, who manage the agreement. As an employee you only need to act when a benefit goes live and shows up in the benefit store.
- CLVR answered my report but I got no email. Only replies are emailed, and only to the person who sent the report. A status change such as in progress or resolved comes as a notification only.
- I cannot find an older notification. Keep scrolling; older ones load as you reach the end of the list.
- A colleague's row looks different from mine. Unread rows are bold with a dot; once read they are not. The same notification can look new for you and read for someone who has already opened it.