Integration settings

A more specific integration setting will be given higher priority than a more general integration setting, in relation to the organisational hierarchy. This means that if there is a setting for a branch that is different from the authority or account, the branch setting will overrule. Some integration settings can only be made on a particular organisation level, described for each integration below.

BaseBibliotek

These settings are currently in use only for Norwegian customers.

Libris ILL

These settings are currently in use only for Swedish customers. See also: Quria online help in Swedish

Metadata Update Service

These settings are currently in use only for Swedish customers. See also: Quria online help in Swedish

SBD

The SBD integration makes it possible to get files from SBD.bibliotheksservice ag based on EAN or delivery note number. The integration keys below are used in Quria.

Integration key	Mapping/description
customer	Customer number
username	User name
password	Password

SEPA

Single Euro Payments Area (SEPA) is used for bank transfers denominated in Euro. The integration keys below are used in Quria.

Integration key	Mapping/description
BIC	The library bank account BIC. Configuration on authority level in Quria.
IBAN	The library bank account IBAN. Configuration on authority level in Quria.
accountName	The library name (max 70 characters). Configuration on authority level in Quria.
initiatingParty	Indicates from where the file has come. Configuration on authority level in Quria.
patronCardLength	Used as part of setting up the PaymentId for the Direct Debit Transfer information. PaymentId consists of the organisation code and the patron card number in the format organisation code / patron card number. The patron card number is padded with zeros to the appropriate length. Should be set to 0 if no padding is wanted. Configuration on authority level in Quria.
paymentId	Identifies the payment collector (the library). This parameter is also known as Creditor Identification Number. Configuration on authority level in Quria.
privateId	Used as part of the Creditor Scheme Id. Configuration on authority level in Quria.

Integration with financial systems

Visma

Quria can communicate with Visma for exchanging information for bills. Settings for Visma are added on account or authority level. The integration keys below are used in Quria.

Integration key	Mapping/description
service.userName	User name for the Visma service
externalSystem	If this is set, then integration is enabled for Visma. Configuration on account level in Quria.
division	Configuration on account level in Quria. (can only be numeric)
commodityNumber.billAdminFee	The account number for handling of library bills and credits in the library’s financial system. Configuration on account level in Quria. (can only be numeric)
profile	If set, used for orderLine.profile. If this is not to be used, then enter n/a to send to Visma as blank.
orderRef	If set, used for orderLine.orderRef. If this is not to be used, then enter n/a to send to Visma as blank.
service.url	URL for the Visma service.
service.password	Password for the Visma service
company	Configuration on account level in Quria. (can only be numeric)
principalNumber	Configuration on account level in Quria. (can only be numeric)
commodityNumber.billReplacementCharge	The account number for handling of library bills and credits in the library’s financial system. Configuration on account level in Quria. (can only be numeric)
yourRef	If set, used for orderLine.yourRef. If this is not to be used, then enter n/a to send to Visma as blank.

Agresso

Quria can communicate with Agresso for exchanging information for bills. Settings for Agresso are added on account or authority level.

The communication goes from Quria to Agresso only. The integration keys below are used in Quria.

Integration key	Mapping/description
integration.agresso.enabled	Defines if the Agresso service should be enabled.
integration.agresso.service.userName	User name for the Agresso service
integration.agresso.producer	Sender system, e.g. Vigilo, Impleo. Set to Axiell.
integration.agresso.responsible	Responsible for the invoice, e.g. AD username. (max 3 characters). Configuration on authority level in Quria. (noting max length).
integration.agresso.invoice.responsibilityNumber	Responsibility number (max 8 characters). Configuration on authority level in Quria.
integration.agresso.invoice.accountNumber	Account number (max 8 characters).
integration.agresso.invoice.ansvarsnr	Responsibility number (max 100 characters)
integration.agresso.invoice.articleNumberReplacementFee	Article number of replacement charge. Article description includes barcode of item.
integration.agresso.service.authenticationUrl	URL for the Agresso authentication server
integration.agresso.service.url	URL for the Agresso service
integration.agresso.service.password	Password for the Agresso service
integration.agresso.client	Client code, e.g. DK (must be 2 characters).Configuration on authority level in Quria.
integration.agresso.billNumber	Used for generating bill numbers in a series defined by Agresso.
integration.agresso.invoice.serviceNumber	Service number (max 8 characters). Configuration on authority level in Quria.
integration.agresso.invoice.dimvalue1	Accounting dimension 1 (max 12 characters) Configuration on authority level in Quria.
integration.agresso.invoice.articleNumberAdminFee	Article number of admin fee. Article description includes bill number.

Bills XML

Along with print-outs it is possible to download XML-files with bill data for both bills ending the overdue notification process, and bills ending the debt reminder process. You do this by setting up the integration for Peppol .

Peppol is an international standard that Quria uses to create bills in XML-format. In the integration settings for Peppol you find the fields that can be set up. For more information about what data should be used, contact your financial counterpart.

There are some settings that needs to be considered before you start with bills via XML, like VAT rates and Financial Account ID:s.

You find the integrations settings for Peppol/XML under Configuration - Settings – Peripherals and integration – Integration settings.

Choose Organisation in the dropdown and add setting for Peppol . Note that the configuration can be done on authority or account level.

The default VAT for Peppol is set to 0 % and is specified with a specific code; Z (Zero). If you want to set a different default VAT, you can set VAT code and VAT percentage under Configuration – System settings – Default VAT Code or Configuration – System settings – Default VAT Percentage.

In the integration settings you also set the default Financial account ID that the amount of the bills should be booked against.

If you want to use different VAT rates or Financial account ID:s than the default values in the integration setting for Peppol, you can specify them under the settings for:

• Articles to sell

• Membership types

• Financial information for debts types

• Replacement charges för billing

You can choose to add specified VAT or Financial account ID for one or more. If no specified value is set, the default settings in the integrations settings for Peppol and system settings are used. If the default account set in integrations settings for Peppol should be used, there is no reason to specify it on this detailed level.

Once the integration settings are done and enabled, the scheduled jobs Generate overdue bills and Generate debt reminders debts will produce bills in XML-format. Please note that patrons without National Id:s will not be included in the XML-files, they will get print outs instead.

The XML files can be found under Patron – Files. Choose Bills in XML-format in the dropdown.

Map

In agreement with a map provider, you can display maps in Arena by entering the map provider-specific URL:s for the branches that have maps. The setting can be added on any organisational level.

A map URL consists of two parts:

The initial part is specific for each map supplier and customer/map. That part ends when the first ”?” is reached and is marked in bold in the example below.
The second part starts with the first ”?” and is built up with a set of parameters that enables the map supplier to give correct map positions. Also this part is map supplier-specific, but is always the same for a specific supplier regardless if you have multiple maps for for example different branches.

Example URL:

https://provider.com/xxx/123?Lang=sv&encoding=utf-8&unit_code={{UnitCode}}&locale={{Locale}}&param0={{DepartmentCode}}&param1={{SectionCode}}&param2={{FirstCharacterAuthorOrTitle}}&shelf={{ItemShelfmark}}&text={{AuthorAndTitle}}

For Wagner guide, the second part should look like this: ?Lang=sv&encoding=utf-8&unit_code={{UnitCode}}&locale={{Locale}}&param0={{DepartmentCode}}&param1={{SectionCode}}&param2={{FirstCharacterAuthorOrTitle}}&shelf={{ItemShelfmark}}&text={{AuthorAndTitle}}

Integration key	Mapping/description
mapURL	The map provider-specific URL according to description above