How to View Payroll Notification Details

🔍 Note:

The ByteHR notifications page displays the payroll history and edits to payroll blocks, as well as the payroll status. 

Notifications in ByteHR can be viewed by:

1. Clicking Notifications at the top menu bar and then click View All.


💬 Note:

To rearrange columns, you can click and drag the column headers.



Meaning of columns on the Payroll Notifications page:

  1. Event Name

    There are six Event Names for payroll notifications:

    1. Generate Payrolls: Clicking the New Payroll button on the Payroll page.
    2. Approve Timesheets: Approving timesheets on the Timesheets page.
    3. Delete Payroll: Clicking Delete Payroll for each payroll block. 
    4. Mark As Draft: Clicking Mark As Draft for each payroll block. 
    5. Mark As Approved: Clicking Mark As Approved.
    6. Notify Payslip: Clicking "Notify Payslip"

  2. Each payroll block displays the following Event Types:
    1. System Process: Payroll calculations via the system, including the following event names
      1. Generate Payroll 
      2. Approve Timesheets
    2. User Process: Actions performed by the user, including the following event names
      1. Delete Payroll 
      2. Mark As Draft
      3. Mark As Approved
      4. Notify Payslip

  3. Created Date: Displays the date and time the action was performed. Created dates are sorted from newest to oldest. 

  4. Company, Branches, Pay Period: Displays the company name, branch name, and pay period for each payroll block.

  5. Status: There are three statuses for payroll notifications:

    1. In Progress: The system is processing.

    2. Success

    3. Failed: Hover over the icon to view the error message.

      Click eye icon to go to that payroll block.

      If the payroll block has been deleted, the icon will not appear in that row.


🏷️ Case

To view the history of your payroll uploads or other income uploads,

please see the History tab on the Upload Payments page.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.