How to report an issue

The full Report an issue flow in the HR view, finding the button, choosing the issue type and affected module, writing the description, linking expenses, attaching files, submitting on desktop or mobile, what happens next, and how to fix the errors along the way.

Whenever something is not working as expected in your CLVR Benefits HR view, a translation looks wrong, or you have an idea for the product, you tell us through the Report an issue button. It is the single entry point for every kind of report, and it is built into the HR layout so it is available from every page under /hr, whether you are reviewing expenses, managing employees, or adjusting benefit settings. This article walks the whole flow from finding the button to confirming your report was sent, and fixes the errors you might hit along the way.

Find the Report an issue button

Look for the Report an issue button with a small message icon. Where it sits depends on your screen size:

• On desktop, it is at the top right of the page header, next to the page title. It stays in the same place as you move between HR pages.
• On mobile, it is inside the navigation menu. Open the menu (the menu icon at the top), and you will find Report an issue at the bottom, below the list of HR links.

Because the button reports from your HR view, the panel can reference any of your company's expenses, not just your own. That makes it the right place to flag something you noticed while working on behalf of your team.

When you select it, a panel titled Report an issue opens with the line "Tell us what happened so we can help." Because you are in the HR view, the panel also shows a second line: "Alternatively, please reach out to" followed by a link to caroline@clvrbenefits.se. Use that link if you would rather email us directly instead of filling in the form.

Choose the issue type

The first field is Issue type, with the placeholder What kind of issue is it?. Your choice here decides which CLVR team picks up the report and what the rest of the form asks for, so it is worth getting right. There are four options:

• Technical issue: something is broken or not working as expected, like a page that will not load or a button that does nothing. This is the only type that adds an Affected module dropdown so you can point us at the part of CLVR involved.
• Poor translation: a label, message, or other text that reads awkwardly or is clearly mistranslated, in either Swedish or English. Quote the wording and tell us where you saw it.
• General issue: any concern that is not technical, a translation problem, or a feature request. No extra fields appear, so you only write your message.
• Feature request: something new you would like CLVR Benefits to add. Describe the problem you want solved, not just the feature, so we understand the why behind it.

The form opens with Technical issue already selected, so if you are reporting something broken you can leave it as is. For anything else, open the dropdown and pick the type that fits. Switching away from Technical issue clears the Affected module and any Linked expenses automatically, because only technical reports use them; switch back and Expense upload returns as the default module.

Pick the affected module (technical issues)

When Issue type is Technical issue, a second dropdown appears: Affected module (placeholder Select a module). It tells the CLVR team which part of CLVR Benefits is misbehaving, so your report lands with the right people. It has three choices:

• Expense upload: anything that goes wrong while uploading or processing an expense report or receipt (a receipt that will not attach, a scan that reads the wrong values, an upload that errors out, or a report stuck in the wrong status). Choosing this also reveals the Linked expenses picker (see below) and requires at least one linked expense.
• Benefit store: problems browsing, viewing, or selecting benefits in the store.
• Other (please indicate): anything that does not fit the first two. Spell out the area clearly in your Description so the team knows where to look.

The form starts with Expense upload selected, so switch it if your issue is somewhere else. A technical issue requires a module: if it is missing, the form blocks the report and shows Select the affected module. Pick the closest match and the message clears.

Write a useful description

The Description field is required for every report, whichever Issue type you choose, and a clear description is the single biggest thing that helps us resolve your report on the first reply. The helper text just above the box changes with the Issue type you picked, so it always tells you what to include: a Technical issue asks you to describe the problem in relation to the affected module, a Poor translation asks for the exact text, a General issue asks you to outline your concern, and a Feature request asks you to describe the feature you would like to see. Each version reminds you to use at least 10 characters.

The form enforces two limits: a minimum of 10 characters (enough for a real sentence, not just "broken" or "help") and a maximum of 2000. The field stops accepting input once you reach 2000, so you cannot type past it. The placeholder in an empty field reads Type your message here, which disappears as soon as you start typing.

Inside that range, a clear description beats a long one. Aim to cover what you did (the page or step you were on and the action you took), what you expected to happen, and what actually happened instead, including any on-screen message. If a screenshot or PDF would explain it faster, add it under Attachments rather than describing every detail in text.

Link the expenses your report is about

The Linked expenses picker appears only when Issue type is Technical issue and Affected module is Expense upload. For that pair you must link at least one expense before you can send, because linking the specific records lets us reproduce and fix the issue faster instead of guessing. Change either dropdown to anything else and the picker disappears, and nothing you had selected is sent.

As an HR user the list covers expenses across everyone in your company, not just your own, so each row reads as First Last · Category · Date · Amount and you can tell whose expense it is at a glance.

Selected expenses appear as removable pills below the picker; remove one by clearing its checkbox or by selecting the small remove control on its pill. The list shows only the expense types that flow through CLVR (uploaded expense reports, benefit purchases, and manually recorded expenses), sorted newest first, and loads a large recent window (a high cap, in the tens of thousands) rather than your whole history. Amounts are shown in Swedish kronor (SEK), with dates and amounts following your interface language. For a specific older expense, reach for the Search expenses box rather than scrolling.

Add screenshots or PDFs

Attachments are optional and work with any issue type, but a screenshot of the screen where something went wrong, with any error message visible, often explains the problem faster than words. Scroll to the Attachments card and select Add files; your device opens a file picker, and you can choose more than one file at once or select Add files again to add more. The helper text reads "Optional screenshots or PDFs (PNG, JPG, PDF, max 10 MB each)", which sums up the two rules:

• File types: PNG, JPG, and PDF only. Other formats (HEIC, GIF, Word and Excel documents, ZIP archives) are rejected.
• Size: each file must be 10 MB or smaller. There is no limit on the number of files, only the per-file size.

When a file uploads, a Files attached notification confirms "Your files were attached to this report," and each file is listed with a document icon and its name (long names are shortened with a trailing "..."). To take one off, select the Remove (X) button on its row any time before you submit. While a file is still uploading, both Add files and Submit show a loading state, so wait for them to finish. Attachments only live in the form while it is open: sending or closing the form clears them, so reopening starts empty.

Submit your report

The form has two buttons at the bottom: Submit sends your report, and Cancel discards it. While the report is sending, Submit shows a spinner and is disabled, so you cannot send the same report twice.

When the report goes through, a green Report sent notification appears: "Thank you. We will review your report." The form then resets and closes on its own. There is no separate "sent" page: the green confirmation is your receipt. You will not receive a copy of the report by email, and there is no status tracker for reports, so if you want a written trail, copy your description before submitting or take a screenshot of the green confirmation.

What happens after you submit

As soon as the report is sent, the panel tidies itself up so it is ready for the next one: the Issue type resets to Technical issue and the Affected module back to Expense upload, your Description is cleared, and any Attachments and Linked expenses are removed. Because the form resets and closes, there is no on-screen history of past reports.

Each report carries everything the CLVR team needs to act on it without asking you to repeat yourself: your description, any linked expenses, references to your attachments, and who sent it and from which company. The Issue type decides how it is filed: Technical issue and Poor translation are recorded as bug reports, while General issue and Feature request are recorded as issues to review and prioritise. You do not need to choose where a report goes; picking the issue type is enough.

There is no in-app reply thread or status stage to watch. The CLVR team reviews each report and, if they need more detail or want to confirm a fix, they follow up by email, so make sure the email address on your account is one you check. Each Submit creates a new report, and you cannot edit or recall one once it is sent, so put everything we need into a single report. When you genuinely need a back-and-forth, or for anything urgent, email is the better route (see Contact CLVR Benefits by email).

Using Report an issue on a phone or small screen

When your window is roughly 48em (about 768px) wide or narrower, selecting Report an issue opens a full modal titled Report an issue rather than the popover that drops out of the button on desktop. The modal gives the form more room, which makes typing and attaching files easier on a touch screen. Everything inside is identical to desktop, including the intro line, the HR email line ("Alternatively, please reach out to" caroline@clvrbenefits.se), the same fields, and the same Submit button.

The fields you see still depend on your answers: Affected module appears only for a Technical issue, and Linked expenses only for a technical issue about Expense upload. Under Attachments, Add files opens your device's file picker, which on a phone includes your camera roll, so you can attach a photo of the screen straight from the gallery (still PNG, JPG, or PDF, up to 10 MB each). To leave without sending, close the modal with the X in the title bar or the Cancel button.

Troubleshooting

The form will not send and a message appears under a field. This is validation. The form checks your entries before sending and tells you what to fix:

• Select the affected module. You picked Technical issue but left Affected module empty. Choose Expense upload, Benefit store, or Other (please indicate).
• Please describe the issue. The Description is empty.
• Please provide more detail (minimum 10 characters). The description is too short.
• Message is too long (maximum 2000 characters). Trim it, or move the extra detail into an attachment.
• A Check the form notification with Select at least one expense. means a Technical issue on Expense upload has no linked expense. Open the Linked expenses picker and tick one.

Fix the highlighted field and the message clears, so you can submit again.

A red "Could not send report" message appears. This means "Something went wrong. Please try again later." The report did not reach the CLVR team and nothing was saved; it is a temporary problem on our side or with your connection, not your form. The panel resets, so copy a long description somewhere safe first, then reopen the form, re-enter it, and submit again. Two other things can trigger the same message: a linked expense you chose has since been removed or no longer belongs to your company (refresh the page so the Linked expenses list reloads, then reselect the available ones), or your session lapsed after a long time signed in (sign in again, then resubmit). If it keeps failing, email caroline@clvrbenefits.se with what you were reporting so the team can pick it up directly.

An "Upload failed" message when attaching a file. This means "We could not upload one or more files. Try again or use a smaller file," and it almost always comes down to the file type or the size:

• Wrong type. Only PNG, JPG, and PDF are accepted. Save an HEIC photo as JPG, export a Word, Excel, or Pages document to PDF, and attach the individual images or PDFs inside a ZIP rather than the archive.
• Too large. Each file must be 10 MB or smaller. Resize or re-export a large screenshot or photo, or split a long PDF into smaller files (you can attach more than one).
• One file in a batch failed. Remove it with the Remove button, then add the remaining files again.
• Nothing uploads and you may be signed out. Attachments only upload while you are signed in; if your session expired, refresh the page, sign in again, and re-add the file.

Attachments are optional, so you can always send the report without the file and describe the issue in the Description instead.

The Linked expenses picker looks empty. The two messages mean different things: No expenses are available to link yet. means no company expenses of a linkable type have been recorded so far, so choose a different module or describe the problem in the Description instead; No expenses match your search. means your filter text is too narrow, so clear the Search expenses box and try a shorter term, such as a colleague's first name, the category, the date, or the amount.