Axiell Quria Ideas


Welcome to the Ideas Portal for Quria users!

Axiell wants to get our customers to be involved in the roadmaps suggesting ideas for features or functions. Unfortunately we cannot develope each and every function suggested but we want to make sure that you have your say. Add your ideas, and opinions to Axiell's roadmap for Quria, creating new features that yours and other libraries would benefit from. You can also vote for other peoples suggestions as well.


In order to make this portal more useful for all the contributors and for us that work with your ideas, we kindly ask you to write in English.


Please note: If you have an error or a misbehaving function, please contact your local Support for the best possible service. If you are not sure what forum that is the most appropriate for your issue, please choose local support as a first step.


How it works:
The ideas are read and reviewed on a regular basis, by product manager and/or local representative. Your ideas will then be available for others to see, vote on and discuss. We encourage discussions between the idea contributors.

Successful ideas will the be prioritzed within our backlog.


What does the status mean?


Under investigation - often there needs to be a discussion between developers and system specialists before we can say if something can be developed, how and when.

Planned - this suggestion or need will be fufilled in some way in a forseable future.


Future consideration - this status means that we think that it's good idea with no technical obstacles but it's not decided if it can be prioritized and put on the roadmap.

No action - in some cases it is impossible to meet some requirements for technical or other reasons, and sometimes there is another alternative way to solve the need.


Right to reject and close
We reserve the right to reject ideas, and also close issues after 3 months if we don't receive an answer to our follow up questions.

Innvoice configurations between VISMA and QURIA

We need a configuration which includes all fees with the innvoice.

After 7 days we give adults a notification fee of 50 NOK and after 14 days they get a notification fee of 75NOK. To the total of 125 NOK (a sum that we should be able to code into the notification fee letters)

If they deliver the books back before the innvoice is sent, they pay this with cash or by “vipps” to the library staff.

When they do not deliver their loans back afer receiving notification fees, they will receive the innvoice from us where the notification fee is included. The due date defines if it is allowed to deliver back the books and get the innvoice deleted. If they deliver the book, they still have to pay the notification fee. And if they do not deliver they must pay everything before they are able to loan again.

Therefore it is crucial to have the notification fee included on the innvoice. It it also importat that the patron is able to pay their full debt for the loan they get innvoice for. Even tho they can generate notification fees for other loans they may have with different due dates. When an innvoice is created, there is not possible to pay the notification fee in cash og with “vipps” with the system we uses today.

We do not have an administration fee.

It is very important that the integration functions well for us, but it will be a problem if the notification fee is not included on the innvoice. And when the innvoice is payed, the notification fee should be deleted. To manage this fee seperately is a lot of extra work for the staff. The patron should not be asked to pay this seperatly either. They should be able to pay the notification fee to the staff when an invoice is not yet created.

And all lists and text that generates must be in Norwegian Nynorsk. – We can help find good words to translate the Bokmål.

We also need to find a solution for the inter-library loans because they may have different fees than us.

  • TrineHelene Pete
  • Nov 10 2020
  • Shipped
  • Attach files