Implementation & integrations

StratyPro configured around your existing payroll environment

StratyPro is configured around the payroll systems, providers, sources, pay components and forms your organization already uses.

Your payroll environment stays in place; StratyPro adds a control and review layer that connects to it.

  • Existing payroll systems and providers stay in use
  • Sources, pay components and controls are configured per environment
  • Testing and review take place before go-live
Explore the implementation process

The implementation process in eight steps

From intake to go-live — each step builds on what is available and relevant in your payroll environment.

For international payroll, configuration may differ by country while central control principles stay recognizable.

Map & discover

Configure

Validate

Go-live

Map & discover

Payroll landscape

Configure

Sources Pay components Forms Controls

Validate

Testing Review

Go-live

Go-live

1 · Payroll landscape

Start with the environment that already exists

Before sources or controls are configured, we map what is already there: entities, systems, roles, exports available per run and where payroll risks matter most for you.

That defines the implementation scope — which environments, sources and controls take priority, not a generic default set.

Multi-country Payroll Control

2 · Sources

Connect the payroll information controls can use

Controls use the sources available in your payroll process — employee registers, change files, employment records, salary exports, payslips or other configured output.

During implementation we agree which sources each control needs, how they are supplied or made available, and what quality and timeliness is required. Not every control uses the same sources; configuration follows your payroll process.

Example of source input in StratyPro. Available sources depend on your payroll environment.

3 · Pay components

Map pay codes to the control configuration

Controls often compare mutations, expectations and payroll output at pay component or pay code level. Implementation maps relevant components and links them to your controls — tailored to risks, sources and payroll setup, not an automatically complete catalog.

Illustrative codes: 10001, 10049, 10120, 10450 — for illustration, not a default set per organization.

4 · Forms

Manage payroll forms with versioning

Many controls rely on structured payroll forms. Relevant forms are configured so controls use the right fields and structure — versioned, with new or updated versions when the process changes.

Before go-live we align structures, fields and expectations with payroll teams; new forms can be added to the configuration when they become part of your process.

Forms management in StratyPro: configured payroll forms and versions. Screen and scope depend on your implementation.

5 · Controls

Configure controls for your payroll risks

Controls are configured based on agreed risks, available sources and pay components — not as a generic list of hundreds of standard checks. The goal is to control the right payroll risks with enough source context, not to add as many rules as possible.

For each control we define what is compared, which sources are needed and which outcome may require review.

More controls does not automatically mean better payroll control. Relevance and source coverage matter more than volume.

Explore Payroll Control

6 · Testing

Test the configuration against your payroll environment

Before go-live, StratyPro and your payroll team validate the end-to-end flow with representative payroll data and agreed scenarios — whether configured controls behave as expected in your environment.

  • Sources per run: availability and quality
  • Controls: executability (including "not executable" without context)
  • Outcomes and Review Actions in known situations
  • Payroll Summary and review flow for approvers
  • Four-eyes approval: maker and checker as separate authorized users
  • Behavior after form or pay component updates

Test scenarios

Illustrative; the actual test set is agreed during implementation.

  • Standard run without changes Basic link sources → controls → outcomes Limited; relevant exceptions only
  • Change with known pay component Expectation vs payroll output for configured component Exception if change not visible in output
  • New pay code in payroll output Signalling flow for unconfigured code Configuration follow-up before trusting the control
  • Missing or incomplete source Status "not executable" vs incorrect "no exception" Clear context for reviewer
  • Form version changed Correct version in control flow No silent mismatch with old form

7 · Review

Review together — outcomes must fit your context

After technical tests comes a joint review with payroll and finance: do control outcomes hold, is there enough context to assess them, and do Review Actions fit how your team actually works?

Roles and expectations are aligned: who investigates exceptions, who sees Payroll Summary before approval, and which situations need escalation — including configuration adjustments where needed.

Automated control supports review; payroll approval remains a human decision within your organization.

Explore Review Actions

8 · Go-live

Go-live when the organization is ready

Go-live is not an automatic switch on a fixed date. Your organization decides when there is enough confidence to use the configured flow in production — often phased by country, entity or payroll environment.

After go-live, StratyPro remains available to support changes in pay components, forms, sources or control needs; the configuration can grow with your payroll environment.

More complex payroll environments

Ongoing setup

Payroll control is not a static setup

New pay codes, changed forms, other sources, reorganizations or provider changes can be reasons to update controls. StratyPro supports that lifecycle with signalling, versioning where relevant and joint alignment — not a one-time static setup.

Payroll and finance stay involved periodically; implementation is not a project that sits on the shelf afterwards.

International

Implementation for international payroll

With multiple countries, systems, providers, pay components and sources may differ by location. Implementation can be built per country or entity, with recognizable central control principles and review for HQ and shared services.

Local statutory setup and payroll calculation stay in the existing environment; StratyPro adds the control and review layer per scope that fits available data and agreed risks.

View multi-country payroll control

Multiple environments

Multiple payroll systems and providers

Organizations with more than one payroll engine or provider can configure StratyPro as long as the required sources and integrations for the desired controls are available. The same implementation steps apply per environment — with scope per system or provider.

We do not claim a universal connection to every system; feasibility depends on your specific payroll stack and data exchange.

Integrations

Integrations: what is possible in your environment

StratyPro can connect to payroll and HR sources through options that fit your Microsoft environment and governance — for example file exchange, automated jobs or other agreed connections. We define the route during implementation with IT and payroll.

We do not show vendor logos or implied "certified integrations" on this page: each connection is assessed for availability, security and maintainability in your tenant.

Microsoft environment

Who does what?

Implementation is a joint effort; responsibilities stay with the right party.

StratyPro

  • guide intake, configuration and testing
  • technical configuration of the control layer
  • support for forms, components and controls
  • documentation of agreed configuration and test results
  • support after go-live for in-scope changes

Organization

  • provide payroll landscape, risks and priorities
  • make sources, test data and subject matter experts available
  • validate whether outcomes hold in practice
  • decide on go-live, roles and approval
  • ownership of payroll engine, provider and statutory setup

No software over the fence: StratyPro does not replace your payroll team, provider or governance. We configure control and review within what you already have — you retain ownership of payroll decisions and data.

How it works follows one payroll run through StratyPro — from sources and Payroll Control to Review Actions, Payroll Summary, Payroll Intelligence and human approval. Implementation builds that flow in your environment.

Frequently asked questions about implementation

Does StratyPro replace our payroll system?

No. StratyPro adds a control and review layer around the existing payroll calculation.

Do all payroll systems need to be the same?

No. Different payroll systems or providers can remain in place where the required sources and integrations for the configured controls are available.

How are pay components configured?

Relevant pay codes or payroll components are mapped to the control context required for the implementation. Different payroll environments may use different codes or structures.

What happens when a new pay code appears?

If supplied payroll information contains a pay code that is not yet included in the current configuration, StratyPro can flag it so the configuration can be reviewed and updated. It does not automatically assign its legal meaning.

Can payroll forms change after go-live?

Yes. Forms can be prepared as versions, published and activated so processing uses the intended version.

Does implementation require direct API integrations?

Not always. Depending on the payroll environment, file-based sources, system integrations or a combination can be used.

Can StratyPro be used across multiple countries?

Yes. Common control principles can be applied while local payroll configuration and source structures remain country-specific where necessary.

How long does implementation take?

The implementation scope depends on the number of payroll environments, source structures, forms, component mappings, controls and testing required.

Is StratyPro custom software for every customer?

No. StratyPro is a standard product that is configured around the organization's payroll environment.

Discuss your payroll environment

In a demo, we can discuss the systems, providers, countries, source structures and control process relevant to your organization.

See when StratyPro is a strong fit

Discuss your payroll environment See how StratyPro works

Book a demo

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