From this page you will find information about recent service disruptions in Procountor. Fixed features can be found in New features in version updates page.
Disruption in S-Bank's connection 25.9.2020 / Fixed
Fixed 25.9. at 11:50 // Payments have been transferred to bank and bank statements retrieved to the program.
A disruption in S-Bank's connection has been detected. Payments of 25.9. haven't been sent to the bank, and bank statements have not been retrieved into Procountor.
We are looking into this issue and will update this message.
Updated 24.9. / Incorrect cent differences in Accounts and Transactions report 22.9.2020
Update on 24.9.: A hotfix for this issue will be published at 03:00 AM on Monday (28.9.).
Accounts and Transactions report may display incorrect cent differences at the moment if there are expenses with a partial VAT deduction right percentage in the accounting entries. The differences may have become visible retrospectively to months that have not had any differences in the past.
When the Accounts and Transactions report includes a difference, it is good to check that a similar difference is not seen through Accounting reports. If there are no differences seen through the Accounting reports, no differences exists in reality.
The issue is under investigation. We will try to fix the situation as soon as possible. We apologize for any inconvenience.
Maintenance break on Saturday, Sep 19th at 7:00 - 11:00 am
Procountor and Mini app will be updated on Saturday, September 19th from 7:00 am until 11:00 am. Procountor and Procountor Mini cannot be accessed during this time. The maintenance break will also affect Procountor's integrations and services using the Procountor API.
We apologize for the inconvenience this service break might cause.
The following version updates will be held as follows:
Disruption in approving and sending Income tax return / Updated 15.9.2020
In January 2019, Finnish Tax Administration detected a local disruption in their service. Due to this disruption some of our customers cannot approve and/or send an income tax return from the program as normal. This disruption doesn't affect all our customers and doesn´t occur in all cases of approving and/or sending an income tax return.
In some cases, the income tax return has been approved and sent successfully without attachments. One option would be though to try to send the notification from Procountor without attachments (the ones that can be sent from Tax Administration´s own services) and then send the attachments separately in Tax Administration´s own services outside of Procountor.
Update 30.3.: The tax administration has given more details on the service disruption. The problem seems to concern users who have 500 or more Katso credentials linked with their user account, which causes problems in approving and sending the income tax with large attachments. Reducing the size of the attachments or sending them directly to the tax administration via their e-service may help with successfully sending the tax return.
Corona may effect the scanning service of OpusCapita
Due to the current Corona pandemic and shutting down borders, we have to prepare our selves to disruptions in OpusCapita scanning service considering PDF invoices and email invoices that are sent to @docinbound.com email address.
Our partner OpusCapita is operating in Tallinn and the invoices are shipped from Helsinki to Tallinn. If the boat traffic is reduced between the countries or stopped completely, the scanning service will be disrupted. Another threat is that the scanning would be shut down temporarily. The scanning cannot be done remotely and it requires people working in the factory.
Observations about the earnings payment reports of YEL insured entrepreneurs
Some of our customers have contacted us concerning YEL insurance and its insurance exceptions. Insurance companies are currently going over the reported insurance information from 2019 and have contacted their own customers concerning the missing insurance exceptions of the YEL insurances.
These may be due to the feature implemented in Procuntor in 2018 where selecting YEL insurance did not automatically select the insurance exceptions No obligation to provide: Earnings-related pension, Unemployment pension and Accident and occupational disease insurance. These selections had to be made by hand by the wages clerk. based on the feedback be received from our customers, we automated the insurance exception in late 2018, and from there on, the insurance exceptions were automatically selected if YEL insurance was selected as the pension insurance.
In Procountor, an employee who is subject to YEL insurance should have at least Earnings-related pension selected as an insurance exception. If this is not selected, the information about the employee will be directed to the same place at the insurance company as TyEL insurance.
If you have been contacted by your insurance company concerning the insufficient insurance exception information, follow these instructions:
- Check with Incomes register if the intended insurance exception has been reported to the Incomes register
- if this information is missing, make the corrections in Incomes register
- If the information is correct in Incomes register, contact your insurance company to find out why they have not received this information from Incomes register.
- If the insurance exception information in Incomes register is incorrect, check the employee’s insurance information in the Employee register in Procountor. If the insurance information in Procountor is incorrect, re-activate the YEL insurance selection by switching the selection to TyEL, then back to YEL. Make sure the insurance exceptions in Procountor are now as they should be.