Tervisekassa

Connect Tervisekassa so certificates of incapacity for work become absences on the schedule. A board member first grants Begin the company’s mandate.

​

Grant the mandate

​

Choose the absences colleagues see

Open Absence mappings and map each certificate type you use to a time-off policy. Create the policy first if none is available. Use Reason overrides when a particular reason should use a different policy, such as a work accident rather than ordinary sick leave. If Tervisekassa corrects a certificate’s reason, Begin moves the existing absence to the policy for the new reason rather than adding a second one. Everyone who can read the schedule sees that the person is away. They see which leave it is only if the policy has Show the leave type to colleagues on, or if they hold View others’ time-off details. The absence’s history names Tervisekassa as its source, and anyone who can open the absence sees that, even when the leave type is hidden. The certificate itself, with its type, reason and number, stays with the people who manage integrations. The reason code Begin copies onto the absence is separate: reading it on the schedule or in a report takes the View others’ time-off details permission, so colleagues see the absence without it. Downloaded report files follow the same permission. No diagnosis is fetched or stored. These absences arrive approved and published. Consider that automatic visibility before turning on the connection. A certificate over days that already hold time off is booked beside it, so both absences show. Decide which one stands: shorten or remove the other absence, or remove the Tervisekassa one, which then stays removed. While Tervisekassa still lists the certificate, shortening its absence does not last, because the next check sets it back to the certificate’s dates. Begin AI’s conflict check lists these overlaps.

​

Connect and check

Turn on the header switch. Begin checks hourly; use Check for certificates on Sync to ask now. Check the run result and the resulting absences. Closed certificates that need your data appear under Waiting for data. Turning the connection off stops future checks and leaves existing absences in place. It leaves TÖR unchanged. Begin verifies a registration number for one workspace only. If it is verified for another workspace, Begin shows an error when you save the number or connect. If another workspace saved it without being verified, your save goes through, and Begin moves the number to your workspace when it verifies your company. To correct the number, disconnect both Tervisekassa and TÖR first, then edit it in workspace settings. Begin then verifies the company for the new number before either can reconnect. The intermediation procedure explains the basis for Begin’s access and its logging.

​

Next

​

Still need help?