Finance management 20.8

Add Finance data set to more dimensions (US3105)

Finance data set identifies a bookkeeping entity in a finance system (e.g. company). MainManager FM supports multiple finance datasets and thus enables customers to have more than one financially isolated finance systems.

Finance data set has now been added to those modules:

• External invoice
• Asset
• Cost center
• Purpose
• Subject

Change that Finance data set is shown with number in lists. Change term Subject to Finance subject. Make it possible to have Unitprice scenario on Account that decides if unitprice or unitprice1 should be used from UnitpriceType for billed hours and material. Also go through old setcolumns functions for Incident to qualitycheck that no column has gone missing

Integration to Verpi (Tripletex) (US3143)

With an integration to Verpi, which is the common Ørn Software finance system integration platform, it is now possible to import/export customers, import/export products (articles), export invoices and get payment status of invoices so that all lease management can be handled in one place

The Ørn Software customer ID (GlobalCustomerID) is set in system settings (also known as Tenant ID)

To import the different finance data set (client customer IDs) defined in Verpi the following action is used

To be able to do this the link to the webservices must be in place as well as Consumer token and Employee token delivered from Verpi experts

The action uses following Verpi webservices

The result is one or more finance data sets imported/updated into the system

Customer/Suppliers

When the finance data sets are in place customers and suppliers can be imported and exported between MainManager and the different finance systems (finance data sets)

The Verpi webservices used for this (Suppliers web service not quite finished in Verpi, is in process)

The export/import includes company information and addresses as well as contacts

The same customer/supplier can be linked to more than one finance data set. NOTE the company ID should be the same in each finance systems but the Customer identification/Supplier identification differs between the different finance systems

When invoices are sent to finance system the customer is automatically created if it does not exist in the finance system (and connected to the finance data set)

Products (articles)

When the finance data sets are in place products can be imported and exported between MainManager and the different finance systems (finance data sets)

The Verpi webservices used for this 

When product is imported or exported to finance system the connection to it is registered in the system, i,e, the same product can (and should) coexists with the same product number in the different finance systems. 

Handling of finance data sets in lease contracts

For customers using more than one finance data set different logic can be used to assign the finance data set to the data structure (defined for site, Department etc). The mutual concept however that when a lease contract is created it should be attached to a finance data set. That defines to which finance system the invoice are sent

Invoicing

Based on accepted lease contract payments, contract basis is created in MM

These invoices are exported to the finance system through this action

The other action looks up each exported invoice to get the payment status from the finance system

These Verpi webservices are used for this