Page Comparison

Leave Days values were included in calculation even if corresponding activity code didn’t have Leave Factor 2 linked to any accumulator

When payroll operates with global option Payroll Calculation by Voyage set, we improved Close & Create New Period function, so that the new Period ID will not be limited by 12 periods within a year but will always use next incremental numeric, except of case when the dialog year is defined as next year. In such case the numeration will restart from YYYY01

Leave Days were not calculated properly if 2 activities existed in one period & calculation performed with option 30 days calendar for leave days full and partial months set under Organization Structure > Company > Leave Days Accounting

Activities might appear overlapped when performing Move Subsequent Shift operation back & forth, that results in shifts overlap

We provided possibility to define several family members with the same allottee priority

ATP Employer Amount was not included into export file although setup for Organization

When an activity was created by payroll transaction as auto-generated Leave Days Paid, its rank was set as in Personal Details but should be from transaction’s rank

Extra days were not generating transactions when Split auto-entry by vessel location was set.

For Accounting Voucher report the fields Amount and Amount CALC had different numeric values although the same currency was used for both.

Field L103 calculated number of weeks independent on if a transaction existed already for the same week. That resulted in L103 counting the same week twice if 2 transactions existed so the reported number was different from actual

Payroll periods are now fetched from a vessel if it is the Open Client & periods’ setup performed on this organization level & Period By Voyage option is set

Field PIN not found when locking period of a person finalizing the payment list.

Some users were not able to add attachment to a Competence document as access was erroneously restricted with routine 303 responsible for Documents module Merge property

Error when trying to sign a person off & he has time portion for his activity dates

Seaman's deduction was not deducted when the system had option Split Year To End Values By Employer set under Global Options > Payroll

A-Melding interface was not showing Total values for Svalbard setup

Field L103 will count the distinct nr of weeks covered by the contract/onboard activities in the payroll period. If counted in the previous payroll period the week will not count.

Fixed, we removed the connection made to the master database. 

Improved values handling for the fields as:

epr7m6t0r1c19b – Sum(calculatedamount1) for all the target crew for the selected month where entrycode=691 (NHS Employee contribution). Same as previously reported in epr7m6t0r1c19e

epr7m6t0r1c19e – hardcoded to 0

epr7m6t0r1c19f – hardcoded to 0

epr7m6t0r2c13 - Total for epr7m6t0r1c19b (should equal to epr7m3t0r13c1)

epr7m6t0r2c16 - hardcoded to 0

epr7m3t0r13c1 - sum for the selected month: PAY/PYH.calculatedamount1 where EC=691 for all the target employees, as previously was epr7m3t0r16c1

epr7m6t0r2c17 - hardcoded to 0

epr7m3t0r16c1 – hardcoded to 0

epr7m3t0r17c1 - hardcoded 0

Extra Sign On/Off activity days are now processed in payroll for open activity if its payscale is set with option Include planned activities in the calculation and always calculate opened activity to estimated end date

Modified E-Indkomst export (Danish tax reporting) so that AS Code 11 doesn’t create record type 6003 in the exported file

Reverted earlier modifications in xml header ISO20022 for balance actions other than Credit Suisse