{"id":1635,"date":"2025-03-11T18:38:56","date_gmt":"2025-03-11T18:38:56","guid":{"rendered":"\/enterprise\/?post_type=ht_kb&p=1635"},"modified":"2025-03-11T18:39:00","modified_gmt":"2025-03-11T18:39:00","slug":"vacation-cash-out","status":"publish","type":"ht_kb","link":"\/enterprise\/knowledge-base\/vacation-cash-out\/","title":{"rendered":"Vacation Cash-out"},"content":{"rendered":"\n

Current State<\/strong><\/h2>\n\n\n\n

\n When an employee is terminated, the user needs to manually reset vacation balances.\n
\n When the balances are reset, the next payroll run includes a specific usage transaction, aka \u201ccashout\u201d, that pays-out the balance in Payroll.\n
\n Balance-cashout process is semi-manual and error prone.\n<\/p>\n\n\n\n

Improvement<\/strong><\/h2>\n\n\n\n

\n Added a new option in Absence configuration (ABCNF) for automatic cash-out upon employee termination.\n<\/p>\n\n\n\n

\n Employee termination can be done by using \u201cDe-activate\u201d from CoreHR or by changing \u201cEmployment End\u201d date from CoreHR \/ Master Adapter \/ API.\n<\/p>\n\n\n\n

\n When enabled: \n<\/p>\n\n\n\n

    \n
  • Period calculation will create a specific ABSTRX record with the current balance value for the selected Absence codes, e.g., Paid Vacation.
    <\/li>\n\n\n\n
  • Timecard reports will display the ABSTRX record.
    <\/li>\n<\/ul>\n\n\n\n

    Activation Settings<\/strong><\/h2>\n\n\n\n

    Absences – Configuration<\/strong><\/h3>\n\n\n\n

    \n Setup > Absences > Absences \u2013 Configuration\n<\/p>\n\n\n\n

    \n VacationBuyOut\n<\/p>\n\n\n\n

    \n New Parameters: \n<\/p>\n\n\n\n

      \n
    • Enable Buyout\u200f \u200f\u200e
      <\/li>\n<\/ul>\n\n\n\n

      \n (SYSEXT2.[CASH_OUT])\n<\/p>\n\n\n\n

      \n Values = Yes \/ No (Default)\n<\/p>\n\n\n\n

      \n When enabled, ABSTRX transaction will be generated upon employee termination. \n<\/p>\n\n\n\n

      \n At least one absence code should be selected from the list. \u200e\n<\/p>\n\n\n\n

      \"Inserting<\/figure>\n\n\n\n

      <\/p>\n\n\n\n

      \"\"<\/figure>\n\n\n\n
        \n
      • Absence Codes in use
        <\/li>\n<\/ul>\n\n\n\n

        \n (SYSEXT2.[CASH_CODES])\n<\/p>\n\n\n\n

        Specify a list of absence codes that should be reset upon employee termination.
        E.g., Paid Vacation and Personal Time Off.
        Other absence codes will not be reset.
        <\/p>\n\n\n\n

          \n
        • Buyout Abstrx Justification Code
          <\/li>\n<\/ul>\n\n\n\n

          \n (SYSEXT2.[CASH_REASON])\n<\/p>\n\n\n\n

          \n Use a dedicated justification code for Buyout. \n
          \n The Justification code will be used for payroll export. \n<\/p>\n\n\n\n

          Period calculation \u200e<\/strong><\/h3>\n\n\n\n

          \n Period calculation will create the selected Buyout Abstrx Justification Code. \n<\/p>\n\n\n\n

          \n When the balance is > 0, the usage = Balance value (Positive) to be paid out in employee\u2019s salary. \n
          \n When the balance is < 0, the usage = Balance value (Negative) to be deducted from employee\u2019s salary.\n
          \n When the balance is = 0, no ABSTRX transaction will be created. \n<\/p>\n\n\n\n

          User Operation<\/strong><\/h2>\n\n\n\n

          Examples<\/strong><\/h3>\n\n\n\n
            \n
          • Absence Codes in use = (2) Vacation in Days, (6) Sickness in Hours, (16) Recreation in Days
            <\/li>\n\n\n\n
          • Buyout Abstrx Justification Code = (1007) Cashed Out
            <\/li>\n<\/ul>\n\n\n\n
            <\/td>

            Scenario<\/strong>\n<\/p><\/td>

            Result <\/strong>\n<\/p><\/td><\/tr>

            1<\/strong>\n<\/p><\/td>

            Future date \u2013 Next PP<\/strong>: \n
            \n The user enters a future termination date in the next PP\n<\/p><\/td>

            \n Transaction will be created\n<\/p><\/td><\/tr>

            2<\/strong>\n<\/p><\/td>

            Future date > Future PP<\/strong>: \n
            \n The user enters a termination date in future PP which is NOT the next one\n<\/p><\/td>

            \n The transaction will be created when the future PP arrives\n<\/p><\/td><\/tr>

            3<\/strong>\n<\/p><\/td>

            Current date<\/strong>: \n<\/p>

            \n The user enters a termination date in the current PP \n<\/p><\/td>

            \n Transaction will be created\n<\/p><\/td><\/tr>

            4<\/strong>\n<\/p><\/td>

            Previous PP date<\/strong> \n<\/p>

            \n The user enters termination date on previous PP\n<\/p><\/td>

            \n The transaction will be created ONLY if the user \n
            \n re-runs PP summary for the previous PP. \n<\/p><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

            Scenario 1<\/strong><\/h3>\n\n\n\n

            Future date \u2013 Next PP<\/strong> \n<\/p>\n\n\n\n

            \n Current PP – November 2024\n<\/p>\n\n\n\n

            \n Balance for 30\/11\/2024: \n<\/p>\n\n\n\n

            \n (2) Vacation = 5.75 Days\n<\/p>\n\n\n\n

            \n (6) Sickness = (-3.54) Hours\n<\/p>\n\n\n\n

            \n (16) Recreation = 0 Days\n<\/p>\n\n\n\n

            \n Setup > Absences > Benefit Accruals Browser\n<\/p>\n\n\n\n

            \"A<\/figure>\n\n\n\n

            <\/p>\n\n\n\n

            \n Employee 1 \u2013 Pay Period Type (5) Calendar\n<\/p>\n\n\n\n

            \n De-activation date = 01\/12\/2024\n<\/p>\n\n\n\n

            \"A<\/figure>\n\n\n\n

            <\/p>\n\n\n\n

            \n PP Summary for Next PP \u200e- December 2024\n<\/p>\n\n\n\n

            \"A<\/figure>\n\n\n\n

            <\/p>\n\n\n\n

            \n Balance for 31\/12\/2024: \n<\/p>\n\n\n\n

            \n (2) Vacation = 0 Days, Usage = 5.75 Days with Justification Code 1007\n<\/p>\n\n\n\n

            \n (6) Sickness = 0 Hours, Usage = (-3.54) Hours with Justification Code 1007\n<\/p>\n\n\n\n

            \n (16) Recreation = 0 Days, No Justification Code 1007\n<\/p>\n\n\n\n

            \"A<\/figure>\n\n\n\n

            <\/p>\n\n\n\n

            \"A<\/figure>\n\n\n\n

            <\/p>\n\n\n\n

            \"A<\/figure>\n\n\n\n

            <\/p>\n\n\n\n

            Scenario 2<\/strong><\/h3>\n\n\n\n

            Future date \u2013 Future PP<\/strong> \n<\/p>\n\n\n\n

            \n Current PP – November 2024\n<\/p>\n\n\n\n

            \n Balance for 31\/03\/2025: \n<\/p>\n\n\n\n

            \n (2) Vacation = 0 Days\n<\/p>\n\n\n\n

            \n (6) Sickness = 1.115 Hours\n<\/p>\n\n\n\n

            \n (16) Recreation = (-0.50) Days\n<\/p>\n\n\n\n

            \"A<\/figure>\n\n\n\n

            <\/p>\n\n\n\n

            \n Employee 1 \u2013 Pay Period Type (5) Calendar\n<\/p>\n\n\n\n

            \n \u201cEmployment End\u201d date = 01\/04\/2025\n<\/p>\n\n\n\n

            \"\"<\/figure>\n\n\n\n

            <\/p>\n\n\n\n

            \n PP Summary for Future \u200e PP \u200e- April 2025\n<\/p>\n\n\n\n

            \"A<\/figure>\n\n\n\n

            <\/p>\n\n\n\n

            \n Balance for 30\/04\/2025: \n<\/p>\n\n\n\n

            \n (2) Vacation = 0 Days, No Justification Code 1007\n<\/p>\n\n\n\n

            \n (6) Sickness = 0 Hours, Usage = 1.15 Hours with Justification Code 1007\n<\/p>\n\n\n\n

            \n (16) Recreation = 0 Days, Usage = (-0.50) Days with Justification Code 1007\n<\/p>\n\n\n\n

            \"\"<\/figure>\n\n\n\n

            <\/p>\n\n\n\n

            \"A<\/figure>\n\n\n\n

            <\/p>\n\n\n\n

            \"A<\/figure>\n\n\n\n

            <\/p>\n\n\n\n

            Scenario 3<\/strong><\/h3>\n\n\n\n

            Current PP<\/strong>\n<\/p>\n\n\n\n

            \n Current PP – November 2024\n<\/p>\n\n\n\n

            \n Balance for 31\/10\/2024: \n<\/p>\n\n\n\n

            \n (2) Vacation = 0.75 Days\n<\/p>\n\n\n\n

            \n (6) Sickness = (-3.55) Hours\n<\/p>\n\n\n\n

            \n (16) Recreation = 0 Days\n<\/p>\n\n\n\n

            \"A<\/figure>\n\n\n\n

            <\/p>\n\n\n\n

            \n Employee 1 \u2013 Pay Period Type (5) Calendar\n<\/p>\n\n\n\n

            \n \u201cEmployment End\u201d date = 30\/11\/2024\n<\/p>\n\n\n\n

            \"Inserting<\/figure>\n\n\n\n

            <\/p>\n\n\n\n

            \n PP Summary for Current \u200e PP \u200e- November 2024\n<\/p>\n\n\n\n

            \"A<\/figure>\n\n\n\n

            <\/p>\n\n\n\n

            \n Balance for 30\/11\/2024: \n<\/p>\n\n\n\n

            \n (2) Vacation = 0 Days, Usage = 1.75 Days with Justification Code 1007\n<\/p>\n\n\n\n

            \n (6) Sickness = 0 Hours, Usage = (-3.55) Hours with Justification Code 1007\n<\/p>\n\n\n\n

            \n (16) Recreation = 0 Days, No Justification Code 1007\n<\/p>\n\n\n\n

            \"A<\/figure>\n\n\n\n

            <\/p>\n\n\n\n

            \"A<\/figure>\n\n\n\n

            <\/p>\n\n\n\n

            \"A<\/figure>\n\n\n\n

            <\/p>\n\n\n\n

            Scenario 4<\/strong><\/h3>\n\n\n\n

            Previous PP<\/strong>\n<\/p>\n\n\n\n

            \n Current PP – November 2024\n<\/p>\n\n\n\n

            \n Balance for 20\/10\/2024: \n<\/p>\n\n\n\n

            \n (2) Vacation = (-3) Days\n<\/p>\n\n\n\n

            \n (6) Sickness = 4.30 Hours\n<\/p>\n\n\n\n

            \n (16) Recreation = 0 Days\n<\/p>\n\n\n\n

            \"A<\/figure>\n\n\n\n

            <\/p>\n\n\n\n

            \n Employee 23 \u2013 Pay Period Type (4) Close 20th\n<\/p>\n\n\n\n

            \n \u201cEmployment End\u201d date = 20\/09\/2024\n<\/p>\n\n\n\n

            \"\"<\/figure>\n\n\n\n

            <\/p>\n\n\n\n

            \n PP Summary for Previous\u200e PP \u200e- September 2024\n<\/p>\n\n\n\n

            \"A<\/figure>\n\n\n\n

            <\/p>\n\n\n\n

            \n Balance for 20\/09\/2024: \n<\/p>\n\n\n\n

            \n (2) Vacation = 0 Days, Usage = (-2.84) Days with Justification Code 1007\n<\/p>\n\n\n\n

            \n (6) Sickness = 0 Hours, Usage = 11.37 Hours with Justification Code 1007\n<\/p>\n\n\n\n

            \n (16) Recreation = 0 Days, Usage = 0.72 Days with Justification Code 1007\n<\/p>\n\n\n\n

            \"\"<\/figure>\n\n\n\n

            <\/p>\n\n\n\n

            \"A<\/figure>\n\n\n\n

            <\/p>\n\n\n\n

            \"A<\/figure>\n\n\n\n

            <\/p>\n\n\n\n

            Employee termination<\/strong><\/h2>\n\n\n\n

            \n Employee termination can be done by changing \u201cEmployment End\u201d date from CoreHR \/ Master Adapter \/ API.\n<\/p>\n\n\n\n

            Master Adapter<\/strong>\n<\/p>\n\n\n\n

            \"A<\/figure>\n\n\n\n

            <\/p>\n\n\n\n

            \"A<\/figure>\n\n\n\n

            <\/p>\n\n\n\n

            API<\/strong>\n<\/p>\n\n\n\n

            \"A<\/figure>\n\n\n\n

            <\/p>\n\n\n\n

            Reports <\/strong><\/h2>\n\n\n\n

            \n These reports show BuyOut transactions for the selected period: \n<\/p>\n\n\n\n

              \n
            • Standard TimeCard – RPERIOD5
              <\/li>\n\n\n\n
            • TimeCard (Standard+ Audit Trail) – RPER5AT
              <\/li>\n\n\n\n
            • Detailed TimeCard – RPERIOD6
              <\/li>\n\n\n\n
            • Detailed TimeCard (Extended) – RPER6EXT
              <\/li>\n\n\n\n
            • Weekly Summary Report – RP6WEEK
              <\/li>\n<\/ul>\n\n\n\n

              \n E.g., Report for Period 2024-11 shows BuyOut transactions when they exist in the same Abstrx period.\n<\/p>\n\n\n\n

              \n Reports Graphs > Pay-Period Summary Reports > TK – Pay-Period Summary Reports >\n<\/p>\n\n\n\n

              \n Standard TimeCard – RPERIOD5\n<\/p>\n\n\n\n

              \"A<\/figure>\n\n\n\n

              <\/p>\n\n\n\n

              \"Inserting<\/figure>\n\n\n\n

              <\/p>\n\n\n\n

              \"\"<\/figure>\n\n\n\n

              <\/p>\n\n\n\n

              Payroll \u200eImplementation<\/strong><\/h2>\n\n\n\n

              \n Implementation is needed for exporting to payroll the vacation buyout in TableQ. \n
              \n In the following screenshot, Justification code 8920 is used for buyout: \n<\/p>\n\n\n\n

              \"A<\/figure>\n\n\n\n

              <\/p>\n\n\n\n

              \n When the vacation buyout is negative, the vacation buyout may go to a different pay code in payroll (TableQ). \n<\/p>\n\n\n\n

              \n TRX_EX _D(EMPLOYEE->EMPLOYEE,PERIOD->PERIOD_KEY,2,1,0,1007)\n<\/p>\n\n\n\n

              \n TRX_EX _H(EMPLOYEE->EMPLOYEE,PERIOD->PERIOD_KEY,6,1,0,1007)\n<\/p>\n","protected":false},"excerpt":{"rendered":"

              Current State When an employee is terminated, the user needs to manually reset vacation balances. When the balances are reset, the next payroll run includes a specific usage transaction, aka \u201ccashout\u201d, that pays-out the balance in Payroll. Balance-cashout process is semi-manual and error prone. Improvement Added a new option in…<\/p>\n","protected":false},"author":4,"comment_status":"closed","ping_status":"closed","template":"","format":"standard","meta":{"_lmt_disableupdate":"","_lmt_disable":"","footnotes":""},"ht-kb-category":[45],"ht-kb-tag":[56],"class_list":["post-1635","ht_kb","type-ht_kb","status-publish","format-standard","hentry","ht_kb_category-absence-management","ht_kb_tag-enterprise"],"_links":{"self":[{"href":"https:\/\/help.synerion.com\/enterprise\/wp-json\/wp\/v2\/ht-kb\/1635","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/help.synerion.com\/enterprise\/wp-json\/wp\/v2\/ht-kb"}],"about":[{"href":"https:\/\/help.synerion.com\/enterprise\/wp-json\/wp\/v2\/types\/ht_kb"}],"author":[{"embeddable":true,"href":"https:\/\/help.synerion.com\/enterprise\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/help.synerion.com\/enterprise\/wp-json\/wp\/v2\/comments?post=1635"}],"version-history":[{"count":1,"href":"https:\/\/help.synerion.com\/enterprise\/wp-json\/wp\/v2\/ht-kb\/1635\/revisions"}],"predecessor-version":[{"id":1702,"href":"https:\/\/help.synerion.com\/enterprise\/wp-json\/wp\/v2\/ht-kb\/1635\/revisions\/1702"}],"wp:attachment":[{"href":"https:\/\/help.synerion.com\/enterprise\/wp-json\/wp\/v2\/media?parent=1635"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/help.synerion.com\/enterprise\/wp-json\/wp\/v2\/ht-kb-category?post=1635"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/help.synerion.com\/enterprise\/wp-json\/wp\/v2\/ht-kb-tag?post=1635"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}