How it works

From payroll input to a controlled payroll run

StratyPro adds a control and review layer around your existing payroll. Your payroll system continues to calculate; StratyPro helps you control, investigate and review the result.

  • Your existing payroll system or provider remains in place
  • Configured controls structure outcomes for review
  • Final review and payroll approval remain human decisions

What remains in your existing payroll environment?

Exact responsibilities depend on the implementation and available integrations.

Remains in place

  • payroll engine
  • local payroll provider
  • payroll calculation
  • local statutory configuration
  • existing HR and source systems

StratyPro adds

  • payroll control layer
  • source comparison
  • control outcomes
  • Review Actions
  • Payroll Summary
  • Payroll Intelligence

The payroll flow in seven steps

Follow one payroll run through StratyPro — from sources to human review and approval.

Context

Control

Review & decision

Context

Payroll input What was payroll expected to process?
Payroll output What did payroll actually process?
Sources

Control

Payroll Control
Control outcomes

Review & decision

Review Actions
Payroll Summary
Payroll Intelligence
Human review & approval

1 · Sources

Start with the information that explains the payroll result

Relevant control context includes what should influence payroll calculation and what the payroll system actually produced.

Payroll input

What was payroll expected to process?

  • employee or contract changes
  • variable pay
  • bonus / overtime / hours
  • other approved payroll input
  • relevant HR, time or benefits information

Payroll output

What did payroll actually process?

  • payroll export
  • payroll register
  • payslips
  • processed pay components
  • calculated payroll results

An approved variable-pay amount can be compared with the component processed in payroll output. The control layer combines the sources required for each configured control — not every answer comes from a single file.

StratyPro does not take over payroll calculation. The existing payroll system or local payroll provider remains responsible for calculation; StratyPro uses relevant input, output and supporting context for control and review.

Learn about payroll engine vs. control layer

Example of source input in StratyPro. Available sources and configuration depend on the payroll environment.

2 · Payroll Control

Run the payroll controls configured for your environment

Controls can compare, depending on configuration: source, expected value, payroll output, employee, pay component and relevant change.

Payroll Control uses configured, deterministic comparisons. AI does not determine whether payroll is correct.

Automated controls typically execute in around one minute once the required sources are available.

This refers to automated control execution only; human review and approval follow afterwards.

The objective is not to run the largest possible number of checks. It is to apply the right controls to the right payroll risks with sufficient source context.

Explore Payroll Control

Payroll Control Workbook
Employee Control Outcome Source
123 Variable pay vs output Exception Change file + payslip
087 Change processed No exception HR change

Illustration · no real payroll data

3 · Control outcomes

Make clear what needs attention — and what does not

No exception

The control ran and matched the expected outcome.

Exception

The control ran but may require review.

Not applicable

The control is not relevant for this employee or situation.

Not executable

Required source or context is missing to run the control reliably.

Not executable is not the same as no exception. An exception is not automatically an error — it is information that may require review.

Understand why a control outcome exists

A reviewer should be able to understand not only that something differs, but also the source context behind the result.

4 · Review Actions

Focus human attention on the exceptions that matter

Review Actions is not the original control outcome itself. It is the review layer where relevant exceptions can be presented with context for human investigation.

Automated control is not the same as automated approval.

StratyPro helps structure control, investigation and review. An enforced four-eyes step follows: the preparer cannot finally close the run alone — another authorized user must approve.

Explore Review Actions

5 · Payroll Summary

Review the payroll run as a whole before approval

Payroll Summary can bring together run context such as completed controls, relevant attention points, Review Actions, review status and payroll-run context.

The summary helps reviewers assess the payroll run as a whole without losing access to the underlying detail.

Explore Payroll Summary

6 · Payroll Intelligence

Ask questions in the context where they belong

Payroll Intelligence supports search, investigation and explanation across payroll context — including recorded historical payroll information where authorized access applies.

  • In-run Intelligence — Questions during the active payroll run. Information can still change. No automated payroll verdict.
  • Payroll History Intelligence — Questions across recorded historical payroll information.
  • Straty Help — Questions about product use and configuration.

Payroll Intelligence does not calculate payroll, determine control outcomes, approve a payroll run or write payroll results back into the payroll system.

Payroll History Intelligence: example questions about recorded historical payroll information.

Payroll Approval & Governance

Four-eyes approval in practice

Control and review lead to an enforced approval step. The maker prepares the run; another authorized user approves before the run can be finally closed.

Maker

Prepares the payroll run, executes controls and addresses relevant Review Actions before submitting the run for approval.

Checker

Is a different authorized user than the maker. Reviews run context (including Payroll Summary) and approves the run before it can be finally closed.

Closure

The run cannot be finally closed by the same user who prepared it. Checker approval is required.

A payroll run cannot be prepared and finally closed by the same user. It must be submitted to another authorized user for approval before the run can be closed. StratyPro enforces segregation of duties in this step; it is not an auditor and does not provide compliance certification.

More on maker-checker in payroll

Configuration

How is this payroll flow configured?

Before go-live, the relevant payroll sources, pay components, forms and controls are configured and tested against the existing payroll environment.

The implementation approach depends on the payroll systems, providers, countries and source structures involved.

  • Sources & pay components Configured and tested against the existing payroll environment before go-live.
  • Controls & forms Relevant controls and payroll forms are configured as part of the environment.
  • New or unrecognized pay codes When supplied payroll information contains a pay code not yet in configuration, it can be flagged so the control configuration can be updated. StratyPro does not automatically assign the legal or control meaning of the new pay code.
  • Versioned configuration Payroll forms can be configured as versions. Changes can be prepared, published and activated so the control flow uses the intended version.

Learn about implementation & integrations

Multi-country

The same control flow across different payroll environments

In international payroll, systems, providers, pay components and source structures can differ by country. Common control principles can remain recognizable while local configuration differs.

Explore Multi-country Payroll Control

Microsoft

Built on Microsoft technology

StratyPro is built on Microsoft Azure technologies. For the current public overview of the Microsoft architecture and assurance context, see the Microsoft environment page.

Microsoft environment

Who is StratyPro for?

Want to see this in the context of your own payroll?

This product tour shows the general StratyPro flow. In a demo, we can discuss how that flow relates to your payroll systems, providers, countries and control process.

Frequently asked questions about how StratyPro works

Does StratyPro replace my payroll system?

No. StratyPro adds a control and review layer around existing payroll systems and providers.

What sources can StratyPro use?

That depends on the payroll environment and controls being configured. Relevant context can include payroll input, employee or contract changes, variable pay, payroll exports, payroll registers, payslips and other configured sources.

Can StratyPro flag a new pay code?

Yes. When supplied payroll information contains a pay code that is not yet included in the existing configuration, it can be flagged so the configuration can be updated. StratyPro does not automatically determine its legal meaning.

What happens when a control identifies an exception?

Where review is required, the exception can be presented through Review Actions with relevant context for human investigation.

Does StratyPro approve payroll automatically?

No. Control and Intelligence support the process; final review and payroll approval remain human decisions.

What is the difference between Payroll Summary and Payroll Intelligence?

Payroll Summary provides a structured view of the payroll run. Payroll Intelligence supports interactive questions within active-run, historical or product-help contexts.

Can StratyPro work with multiple payroll systems or providers?

Yes, where the required sources and integrations for the relevant controls are available.

Does StratyPro support international payroll?

Yes. Common control principles can be applied across different payroll environments, with local configuration where required.

Book a demo

Leave your details and we'll contact you to discuss StratyPro and your payroll process.