Payment reminders received from suppliers on 26.7.2022
Invoicing is currently busy
Our invoicing is currently extremely busy, and replies to service requests may take longer than usual. We are doing our best to process our backlog and will try to answer your messages as quickly as possible.
Thank you for your patience!
Error with purchase invoices' total sum / FIXED 12th of July
There was an issue in Procountor, where purchase invoices received in Procountor from 30th of June to 6th of July had an incorrect total sum. The total sum presented on the invoice was incorrectly the sum without VAT, not with VAT. The issue affected invoices received through Apix.
The issue was fixed 12th of July. However we recommend checking the total sum of invoices before paying them in any case.
Addition 8th of August 11:12: If a purchase invoice is in Procountor with an incorrect total sum, it's possible to modify the row information of the invoice when it's in Unfinished or Received status so that the correct total sum is calculated from the rows. The invoice must have a correct total sum before making the payment.
If an invoice has already been paid with an incorrect, too small total sum, it's possible to manually create a new invoice with the remaining sum and pay it, or pay the remaining sum with the Direct bank transfer tool. Accounting can be manually corrected on a purchase invoice's accounting page or with a Journal receipt for example.
Error situation in Procountor Mini application 4.7.
We have received individual contacts where invoices have gone double for payment in Procountor Mini application. The situation may have been caused by the fact that when you click Pay in Procountor Mini and if the Finago Avain application does not open by itself (to confirm the payment) - you could have made a new payment for the same invoice.
This should not be possible and we have the matter under investigation.
Error in reporting travel invoices to Incomes Register with earnings payment report
An error has been discovered in the program when reporting travel invoices with the earnings payment report in situations where the employee is employed under Keva. The earnings payment report will fail to send with an error message "Payer suborganisation identifier is missing and it is mandatory".
Earnings-related pension insurance information does not need to be reported on travel invoices.
This issue can be corrected as follows:
1. Go to Salaries > Employee register, select the employee, and click on the Salary info tab.
2. Write down all the information in the Insurances section, such as the Employees' pension Act (TyEL) agreement and all selected insurance exceptions.
3. Select Not used as the pension insurance.
4. Report the travel invoices with an earnings payment report.
5. Return to the salary info and reset the insurances information to the previous settings, including the original TyEL pension insurance and possible insurance exception types.
Alternatively, the travel invoices can be reported to the Incomes Register via their own online service.
Error in printing financial statements, employers separate report, and salary list payment reports 7.3.2022Some of our users are getting an error message when attempting to print out financial statements, employers separate report, and salary list payment reports. We are investigating the issue and will update this announcement once we have more information.
Update 26.4.2022: We are still working on a fix. This error message can be avoided in some situations by printing out the report on another web browser.
Error message when accepting salary list 24.2.2022 /UPDATED July 20th 2022
Possibly missing row names and translations in Default report formulas view
In some environments using new chart of accounts functionalities, there is a situation in which the default income statement and/or balance sheet in Default report formulas view is missing content in Name column and in the translation column for the company’s language set in Basic info view. However, generating the income statement and balance sheet can be done normally in that language in Accounting reports (new) view and in Closing of accounts tools view.
Instructions for checking and making possible fix can be found from this Word file: