Articles in this section

Disruption Info

  • Updated

From this page you will find information about recent service disruptions in Procountor. Fixed features can be found from New features in version updates page.  

 

Connection issues between Procountor and Finago Key June 5th, 2020 / Fixed 5.6.2020

Some of our users are experiencing issues when verifying their login with Finago Key application. We are currently investigating the issue.

You can verify your login with the one-time password list. If you do not have your one-time password list, go to secure.procountor.com and click Problems signing in?

1.    Select Lost one-time password
2.    Fill in your username and password and click Continue
3.    Your one-time password will be sent to you as a text message to the phone number saved in your Personal info after you click Send one-time password
4.    After logging in, you can get a new one-time password list in Personal info and settings > Change passwords lists. Please note you do not have to save a new password list if you have only forgotten your password list at home.

You can find more instructions here: One-time password is lost

Fixed Jun 5th: The problem has been fixed.

 

Service break in Ilmoitin.fi (Katso-services) 9th of June 2020 morning

On Tuesday 9th of June 2020, the Tax service's Ilmoitin-service is being updated. During this update www.ilmoitin.fi and external program integrations are not in use.

This affects Procountor so that Katso-service is not in use 9th of June 2020 from 6:55 to 9:05 am.

More information about the update can be found from this link.

 

Maintenance break on Sat, June 6th at 7 am - 1 pm

On Saturday 6th of June, we will have a technical service break related to improving disk system components in the data center.

The service break starts at 7 am and lasts until approx. 1 pm. 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.

 

Disruption in approving and sending Income tax return / Updated 27.4.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.
 
An error message due to this disruption indicates that the notification couldn't be received successfully. 
 
This error message comes directly from the tax service of Tax Administration. Unfortunately, we have not received any further information from Tax Administration regarding this disruption so far. So far, Tax Administration has not found the reason for this error message.
 
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.
Our product development is working on solving the issue.
Update 27.4: Users are still experiencing disruptions when approving and sending income tax returns. We recommend reducing the size of the attachments or sending them directly to the tax administration via their e-service.

 

 

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. 
That is why we are recommending our customers to inform their suppliers, that are sending their invoices to the scanning service, that the invoices should be sent by using other delivery methods (for example electronic invoices).
We are currently looking for another solution to bring the PDF invoices to Procountor and we will tell more as soon as we have a better solution. 

 

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:

  1. 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.
  2. 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.

 

Disruption Info Archive

Related articles