Kreluna ecosystem

AI for payroll providers and HR consultancies

Kreluna Office is being designed to help coordinate repetitive, document-heavy work while leaving specialist or legally regulated advice, review and responsibility with the appropriate professionals.

Kreluna is in active development. Early access, feature availability and integration coverage are confirmed individually for each request.

A clearer operational workflow

Files and documents

Organise authorised information and highlight missing items.

Deadlines and priorities

Prepare tasks and reminders for review before action.

Team collaboration

Make assignments, roles and approvals visible to managers and staff.

Coordinate files and deadlines

Kreluna Office can prepare tasks, organise documents and surface priorities or missing information. Configuration begins with the firm’s real process and the software it actually uses.

  • Clearer recurring workflows
  • Visible ownership across the team
  • Reminders prepared for review

Keep specialist or legally regulated advice under professional control

Calculations, regulatory interpretation and client-facing actions require review by the appropriate professional. Kreluna supports preparation and coordination rather than replacing specialist judgment.

  • Human control over decisions
  • Least-necessary permissions
  • Integrations checked in advance

Frequently asked questions

Does Kreluna provide payroll or employment advice?

No. Calculations, regulated interpretation and client actions require review by the appropriate specialist.

What is a suitable first workflow?

A recurring document process with clear owners, such as information intake, priority checks or draft communication.

How should employee data be protected?

Use restricted access, the minimum necessary data and agreed procedures before any real information is introduced.

Built around control and clarity

Every project starts with a defined objective, authorised information and a clear review process. Capabilities are enabled progressively and important actions remain subject to approval.

  • Defined scope and responsibilities
  • Human review for important actions
  • Clear limits and measurable outcomes
Practical applications

Support the administrative payroll workflow

Kreluna is not presented as a payroll engine or employee-decision system. These examples cover intake, completeness and coordination before professional payroll processing.

Monthly changes

Collect messages and attachments, associate employer and period, and flag missing information for review.

Files and deadlines

Prepare checklists, tasks and reminders while calculations and statutory work remain in official systems and professional control.

Recurring enquiries

Classify client questions and prepare drafts from approved content, escalating situation-specific requests.

Work allocation

Make status, owner and priority visible without assessing employee performance or making employment decisions.

Project method

An administrative workflow, not an employment decision

The first use case should avoid special-category data where unnecessary and clearly separate organisational support, professional processing and employer decisions.

  1. Define the outcome

    Describe the problem, who performs the work today and which observable result should improve.

  2. Map data and exceptions

    Identify sources, permissions, manual hand-offs, unusual cases and points where a person must decide.

  3. Test a narrow scope

    Run the pilot on authorised sample data against acceptance criteria agreed before the test.

  4. Measure and decide

    Compare the workflow with its baseline, then extend, revise or stop it on evidence rather than enthusiasm.

Data and accountability

Employee data and high-impact uses

Health, union or assessment information requires particular care. AI used for recruitment, management or employment decisions may fall under specific rules and is not included by implication.

  • Minimise data for each task
  • Separate employers, employees and processing periods
  • Exclude employment decisions from an administrative pilot
  • Keep approval for material changes
  • Verify provider, retention and transfers before use
Measuring value

Measures for preparatory work

Completeness and timeliness fit better than raw throughput. The final output remains under the firm’s and system’s control.

Complete changes

Requests reaching processing with agreed fields and documents available.

Follow-ups

Additional communication caused by missing or inconsistent information.

Preparation time

Work spent classifying, checking and assigning incoming items.

Sensitive exceptions

Cases correctly stopped and escalated rather than handled automatically.

Before you begin

What is not delegated to AI

Does Kreluna calculate payroll?

No. This page describes workflow support; payroll calculations and statutory work remain in authorised systems and professional control.

Can it make decisions about employees?

No. An administrative project excludes employment decisions. Such uses need a separate assessment and may be regulated as high risk.

How is special-category data protected?

The first control is not to use it unless necessary. Where required, purpose, access, security, retention and legal basis need competent assessment.

References for responsible design

The AI Act and GDPR can apply together: duties and safeguards depend on the organisation’s role, the data and the system’s actual use. Assessment therefore comes before configuration.

These sources help frame the work; they do not replace legal, privacy or security advice for a specific situation.