Audit Logs

Transparency among all stakeholders and processes

When working on payroll, it is crucial to maintain a clear paper trail for all inputs used to calculate wages at the end of a payroll period. The more individuals involved in the payroll process, the more essential audit logs become. Each stakeholder is responsible for specific tasks, and each task can impact subsequent steps in the process. For example:

Employee hours: These are calculated directly from Time and Attendance data. Any changes to clocking data will directly affect the wage paid to an employee.

Once-off expenses or earnings: If the employee requires additional inputs to calculate their wages, these values must be recorded.

Employee information: Modifying employee information, such as employment start dates or taxable status, will impact statutory deductions. Changing banking details can result in the employee not being paid.

These examples illustrate some of the repetitive tasks performed by multiple stakeholders in the payroll process each period. When handling tasks for hundreds of employees, mistakes are inevitable. Managing these tasks among multiple stakeholders can lead to incorrect wages and unhappy employees.

This is where audit logs come in. They create transparency among all stakeholders and processes, allowing anyone to view changes made at each step in the process.

Audit logs enable you to inspect each action taken by:

  • Identifying the exact stakeholder who made the change and the precise date and time it was made.

  • Detailing the type of action performed, such as removing overtime, adding missing days, changing the value of a deduction, updating employee banking details, and more.

  • Displaying the original and new values side by side to easily backtrack and rectify errors.

The goal of audit logs is to empower you to hold individuals accountable for the changes they make and to assist in correcting errors. While errors are inevitable, fixing them should not be difficult.

Log Breakdown

All actions performed by users are summarized in the log list. Each log provides a summary of the action performed and by whom. Here is a detailed breakdown of each log:

  1. User: The user who performed the action.

  2. Agrigistics Specialist: For transparency, any changes made by an Agrigistics member will also be listed in your logs.

  3. Event ID: A unique identifier for each log entry.

  4. Date: The specific date and time when the action was performed.

  5. Action Type: The type of action that was performed.

  6. Context: A brief summary of the data affected by this action.

Changes Breakdown

Click on a log to view the details of what data changed. Each log contains all the values that were updated with the specific action. Here's a detailed breakdown of the log entries:

  1. Search: Use the search bar to find a specific field or employee that was changed with this action.

  2. Filters: Apply filters to narrow down your search.

  3. User: The user who made the change.

  4. Employee Name: The name of the employee whose data was changed.

  5. Property Name: The specific property that was changed.

  6. New Value: The updated value after the change was applied.

  7. Old Value: The previous value before the change was made.

Where to Access Audit Logs

Audit logs are accessible from multiple locations within the Agrigistics platform. While we're still in the process of rolling them out across the entire portal, the following locations are currently available, with more to be added soon. You can always access audit logs from the action panel on the right-hand side of the relevant pages. Please refer to the image below for guidance.

Current Pages with Audit Logs and Tracked Changes:

  • Employee Management

    • Employee information (e.g., name, surname, employee number, team, etc.)

    • Clock template scheduling

  • Employee Overview Report

    • Clocks

    • Leave

    • Harvest Items

    • Activity Items

  • Pay Run

    • Employee personal information (e.g., banking details, identification numbers, tax details, etc.)

Last updated