Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Click the Add Payment button. This opens the Add New Payment dialog:

    kadmos_functionality_add_net_payment.png

  2. On the dialog, select Advance Payment. This invokes the Advance Payment dialog where you can see a list of payment records ready for transfer:

    kadmos_functionality_advance_payment_dialog.png


    Please note that employees are filtered out based on the assigned entry code and Kadmos balance action.

  3. Select the record(s) to be transferred and click Create New Payment.

  4. On the Payment Details dialog, fill out the payment details to be processed and click OK to proceed:

    • Payment Name. Enter the payment name. The field is grayscaled, and, thus, locked for editing, in case the default payment name is defined in Setup (see General Settings).

    • Description. Enter the payment description.

    • Currency. Select the currency for payment processing. In case the default currency is defined in Setup (see General Settings), it appears in the field, however, you can still change it based on your preferences.

    • Package (available only in case predefined in General Settings). From the drop-down list, select the

    • Payment Date. In the calendar picker, select the date for payment processing. Please note the selected payment date will be displayed in Payroll after locking transactions marked as PAID.

      kadmos_functionality_advance_payment_details.png

      Once completed, click OK to proceed.

...

Info

All the transferred advance entry codes are automatically locked. This means that the amounts of the transactions will not be modified after calculation even if any of the parameters such as Payscale rate, Activity dates, etc get changed. The entry code will be marked as PAID proceeding with the date when the transaction was processed.:

advance_payment_locked_transaction.pngImage Added

The transactions can be unlocked (Payroll > Set > Unlock Payroll Transactions) provided that a user has corresponding access rights.

...

  1. Click the Add Payment button. This opens the Add New Payment dialog:

    kadmos_functionality_additional_payment_add_new_payment.png

  2. On the dialog, select Additional Payment. This invokes the Additional Payment dialog where you can see a list of payment records ready for transfer:

    kadmos_functionality_additional_payment_dialog.png


    Please note that employees are filtered out based on the assigned entry code and Kadmos balance action.

  3. Select the record(s) to be transferred and click Create New Payment.

  4. On the Payment Details dialog, fill out the payment details to be processed and click OK to proceed:

    • Payment Name. Enter the payment name. The field is grayscaled, and, thus, locked for editing, in case the default payment name is defined in Setup (see General Settings).

    • Description. Enter the payment description.

    • Currency. Select the currency for payment processing. In case the default currency is defined in Setup (see General Settings), it appears in the field, however, you can still change it based on your preferences.

    • Package (available only in case predefined in General Settings). From the drop-down list, select the

    • Payment Date. In the calendar picker, select the date for payment processing. Please note the selected payment date will be displayed in Payroll after locking transactions marked as PAID.

      kadmos_functionality_additional_payment_added.png

      Once completed, click OK to proceed.

...

Info

All the transferred additional entry codes are automatically locked. This means that the amounts of the transactions will not be modified after calculation even if any of the parameters such as Payscale rate, Activity dates, etc. get changed. The entry code will be marked as PAID proceeding with the date when the transaction was processed.:

kadmos_functionality_additional_payment_locked.pngImage Added

The transactions can be unlocked (Payroll > Set > Unlock Payroll Transactions) provided that a user has corresponding access rights.

...