Skip to content

Traditional Payroll Software vs. Ason Event-Driven Payroll

Traditional payroll software requires payroll expertise. Users must understand which functions to execute, when to execute them and how one change affects the rest of payroll.

With Ason, users report what happened. The Payroll Engine determines the relevant consequences and coordinates the payroll work.

Same payroll change. A completely different way of handling it.

Traditional Payroll Is Function-Driven. Ason Is Event-Driven.

Traditional Payroll Software

The user operates the software.

A change happens

The user recognises the payroll impact

The user selects the required functions

The user manages the correct sequence

The user checks whether anything was missed

Payroll is updated

Ason Payroll Engine

The engine coordinates the payroll work.

A change happens

The user reports what happened

Automatic, inside the Ason Engine

Ason evaluates the payroll impact, recalculates and validates

Required actions or exceptions are shown

Payroll is updated

Traditional software provides payroll functions. Ason embeds payroll expertise into the engine.

One Change. Many Payroll Decisions.

An employee changes from hourly pay to a monthly salary. The input is simple, but the change can affect several payroll processes.

With Traditional Payroll Software

The payroll specialist must recognise and coordinate every relevant step.

  1. Change the employee’s pay basis
  2. Enter the monthly salary and effective date
  3. Prorate the salary correctly
  4. Recalculate the current payroll period
  5. Check whether previous periods are affected
  6. Process any required retroactive corrections
  7. Review social security and insurance effects
  8. Validate the applicable Swissdec requirements
  9. Generate the updated payslip
  10. Update the relevant accounting and payment outputs
  11. Verify that every necessary step has been completed

Payroll completed after the specialist has coordinated the complete process.

With Ason Payroll Engine

The user reports what changed.

  1. Change the pay basis from hourly pay to monthly salary
  2. Enter the monthly salary and effective date

Handled automatically by the Ason Engine

  • Applies the right rules and recalculates every affected period
  • Takes social security and insurance dependencies into account
  • Validates against regulatory requirements
  • Updates payslip, accounting and payment data

Every action is logged. Anything that needs a decision is flagged.

Payroll is updated and salaries can be paid out at any time.

Not every change requires every possible payroll action. The engine determines which consequences are relevant to the specific employee, effective date and payroll period.

The user reports one change. Ason coordinates the payroll consequences.

The Difference at a Glance

Recognising changes

Traditional Payroll Software: A payroll specialist identifies which changes are payroll-relevant.

Ason Payroll Engine: The engine evaluates the impact of the reported event.

Recalculations

Traditional Payroll Software: The specialist decides what must be recalculated.

Ason Payroll Engine: The engine recalculates the affected payroll results.

Retroactive changes

Traditional Payroll Software: Previous periods and corrections must be coordinated manually.

Ason Payroll Engine: Relevant previous periods are identified and recalculated.

Validations

Traditional Payroll Software: Checks depend on specialist knowledge and checklists.

Ason Payroll Engine: Rule-based validations identify missing information, discrepancies and impacts.

Next steps

Traditional Payroll Software: The specialist must know which process to initiate next.

Ason Payroll Engine: The engine performs the applicable steps and shows anything requiring attention.

Payroll status

Traditional Payroll Software: Payroll is prepared through a sequence of functions.

Ason Payroll Engine: Payroll is updated after relevant changes and remains ready for review.

Outputs

Traditional Payroll Software: Payslips, payment files and accounting outputs require separate actions.

Ason Payroll Engine: Relevant outputs are updated as part of the payroll process.

Transparency

Traditional Payroll Software: The specialist documents and verifies the completed steps.

Ason Payroll Engine: Engine actions, validations and required follow-up remain visible.

The User Reports the Change. The Engine Does the Payroll Work.

Ason turns real-world payroll events into the relevant calculations, validations and follow-up actions. Users remain informed and in control without having to operate every payroll function themselves.

Questions About Event-Driven Payroll

What is the main difference between traditional payroll software and Ason?

Traditional payroll software provides functions that specialists must operate in the correct sequence. With Ason, users report the business event and the Payroll Engine determines the relevant payroll consequences.

What does event-driven payroll mean?

Event-driven payroll begins with what happened in the business, such as a salary change, absence or bonus. The engine translates that event into the relevant calculations, validations and follow-up actions.

Do users still need payroll expertise?

Ason significantly reduces the specialist knowledge required for routine payroll work. Payroll professionals can focus on complex cases, policies and oversight instead of manually coordinating every processing step.

Does Ason perform every action automatically?

Ason performs or prepares the applicable payroll processes supported by the engine. When information, review, a decision or authorisation is required, the user is informed and guided to the next step.

Can users see what the engine has done?

Yes. The engine shows relevant actions, validations, impacts, exceptions and required follow-up so users remain informed and in control.