Maker
Prepares the run, sees control outcomes, addresses relevant exceptions and submits the run for approval.
StratyPro demo
See StratyPro in the context of your payroll environment
See how StratyPro brings payroll input, payroll output, controls, relevant exceptions, Review Actions, Payroll Summary and Payroll Intelligence together before human approval.
We can then relate that flow to the payroll systems, providers, countries and control process used by your organization.
What will you see in a StratyPro demo?
The demo follows a payroll run from source context through Payroll Control, relevant exceptions and human review.
We show how Review Actions, Payroll Summary and Payroll Intelligence support different parts of the process, and then discuss how the same control flow could relate to your payroll environment.
A single demo is not intended to resolve every integration detail or technical design question for your organization.
The product demo
From payroll input and output to human approval
-
Payroll input What was payroll expected to process?
-
Payroll output What did payroll actually process?
Sources
Payroll Control
Control outcomes
Review Actions
Payroll Summary
Payroll Intelligence
Four-eyes approval
Four-eyes approval
Four-eyes approval in practice
The demo explicitly shows how maker, checker and closure are separated in StratyPro — a core proof point alongside control, review and summary.
Checker
Must be another authorized user. Reviews run context and approves before the run can be closed.
Closure
The maker cannot finally close the payroll run alone. Required checker approval is technically enforced.
What you will see
The core product areas in one connected workflow
A. Payroll Control
The demo can show configured source context, configured payroll controls, expected vs observed values and control outcomes.
Payroll Control uses configured, deterministic comparisons. AI does not determine whether payroll is correct.
The objective is not to run the largest number of checks, but to apply relevant controls with sufficient context.
B. Review Actions
We show which exceptions require attention, context around the exception, human investigation and the review workflow.
C. Payroll Summary
We show a run-level overview, relevant attention points and the relationship between control and review before approval.
D. Payroll Intelligence
- In-run Intelligence
- Payroll History Intelligence
- Straty Help
AI supports investigation and understanding. It does not approve payroll.
E. Payroll Approval & Governance
We show the enforced four-eyes step: submit for approval, review by another authorized user, then closure. StratyPro does not autonomously decide whether payroll should be approved.
Automated control is not the same as automated approval.
Your environment
Then we look at your own payroll landscape
Practical discussion points can include:
- how many payroll environments exist?
- which payroll systems are used?
- which payroll providers are involved?
- in which countries is payroll processed?
- what payroll input sources matter?
- how are payroll controls performed today?
- where does review happen?
- who is involved in approval?
- where does historical investigation take time?
The product demo shows how StratyPro works. The discussion about your payroll landscape helps determine where a control layer may be relevant.
You do not need to replace the payroll landscape before evaluating StratyPro.
StratyPro adds a control and review layer around existing payroll calculation. Local payroll systems or providers can remain responsible for gross-to-net calculation.
Central payroll control therefore does not automatically require centralized payroll calculation.
Preparation
You do not need a full implementation dossier before the first demo
For an initial product demo, you generally do not need to provide full payroll files or real employee data.
A high-level view of the payroll environment is enough to make the discussion more relevant.
Useful information if available:
- number of countries;
- payroll systems;
- payroll providers;
- main control challenge;
- who is involved in payroll review.
No real employee data is required to see the product flow
The StratyPro demo environment can be used to demonstrate the product workflow. Your own payroll landscape can initially be discussed without uploading real employee data into the demo.
Who should join?
The demo can be relevant to several roles around payroll
Payroll / Global Payroll
Typically interested in:
- controls;
- exceptions;
- review;
- multi-country payroll;
- historical questions;
- provider complexity.
Finance / Internal Control
Typically interested in:
- traceability;
- explainability;
- review context;
- approvals;
- run-level summary.
IT / Enterprise Architecture
Typically interested in:
- where StratyPro fits;
- what is added;
- what is not replaced;
- Microsoft architecture;
- access;
- sources and integrations.
Management / Transformation
Interested in:
- central control;
- scalability across payroll environments;
- governance;
- transformation roadmap.
Technical questions can be included in the evaluation
StratyPro is deployed within the organization's Microsoft Azure environment.
Access to StratyPro can be aligned with the organization's Microsoft Entra ID.
If IT, Security or Enterprise Architecture is involved, we can discuss how StratyPro fits into the organization's Microsoft architecture and governance.
A standard product configured around your payroll environment
StratyPro is not rebuilt as a separate custom software product for every customer.
The standard StratyPro product is configured around the relevant payroll administrations, sources, pay components, forms, controls and review requirements.
After the demo
What happens if StratyPro looks like a good fit?
Product demo
Payroll landscape / scope
Implementation approach
Configuration & testing
If StratyPro fits the control need, the next step is to define the implementation scope: relevant payroll environments, sources, pay components, forms and controls.
See Implementation & integrations
The demo is intended to assess the product and potential fit. Detailed configuration follows when the implementation scope is defined.
Book a demo
Book a StratyPro demo
Leave your details and we will contact you to align the demo with the payroll context of your organization.
Frequently asked questions about the demo
What will StratyPro show during the demo?
The demo follows the flow from payroll input and payroll output through Payroll Control, control outcomes, Review Actions, Payroll Summary, Payroll Intelligence and human review and approval.
Do I need to provide payroll data before the demo?
For an initial product demo, full payroll files or real employee data are generally not required. The product can be shown in the StratyPro demo environment while your own payroll landscape is discussed at a high level.
Can our IT team join?
Yes. If Microsoft architecture, identity, access, sources or integrations are relevant, those topics can be included in the discussion.
Is the demo relevant if we use multiple payroll providers?
Yes. Organizations with multiple systems, providers or countries can use the demo to discuss how a more centralized control layer could fit around local payroll.
Does StratyPro replace our payroll system?
No. StratyPro adds a control and review layer around existing payroll calculation.
Will we receive a complete implementation plan during the demo?
Not necessarily. The demo is intended to assess the product and potential fit. Detailed implementation scope is defined afterwards if there is a reason to continue.
How long does the demo take?
The duration depends on the topics that are relevant to your organization. When arranging the demo, we can determine which areas should be covered.