Requests, placements, hours and invoices according to the standard Client and staffing agency without retyping One integration for multiple parties

Custom SETU integration development

Appfront builds integrations according to the SETU standards, the agreements for electronic messaging between staffing agencies and their clients. Requests, placements, hours worked and invoices travel as standardised messages between the client's system and the staffing agency's back-office system. This way hours are not retyped, and the invoice matches what the client has approved.

What is a SETU integration?

SETU, the Stichting Elektronische Transacties Uitzendbranche (Dutch foundation for electronic transactions in the staffing industry), manages standards for messaging between staffing agencies and their clients. There are standards for requesting and proposing candidates, for placement data, for hours worked and costs, the digital timesheet, and for invoices. In 2024 the standards for the process from request to payment were modernised into 2.0 versions.

Without an integration, requests go by email, hours are entered on a form by the flex worker, approved by the client and retyped by the staffing agency. The invoice follows, and the client checks it by hand against their own records. A difference of a few hours leads to a credit note, and a large client with ten staffing agencies gets ten different ways of submitting.

We build custom because the parties differ: which back-office system the staffing agency uses, which system the client uses, which messages and versions of the standard are used, and how many parties connect. The standards are managed by SETU; we make sure your systems work with them.

According to the standard

Requests, placements, hours and invoices as messages according to SETU, validated before sending.

No retyping

Approved hours go straight to payroll and invoicing, and the invoice matches the hours.

Multiple parties

One integration for all staffing agencies or clients that use the standard.

How we build your SETU integration

We start with your messaging: which parties, which systems, which messages and versions, and where retyping currently happens. Clients and staffing agencies often use different versions of the standard. We map this out, so the integration can talk to everyone and the move to new versions remains possible.

1
Mapping message traffic

Your parties, systems, messages and versions of the standard.

2
Building messages

Requests, placements, hours and invoices according to SETU.

3
Testing with parties

Testing with real staffing agencies or clients, and validation.

4
Go-live and maintenance

Go-live, monitoring, and maintenance when new versions arrive.

What a SETU integration does in practice

The components below appear in almost every SETU integration. Which ones you need depends on your role.

Applications

Requests and candidate proposals.

Placements

Placement data between the parties.

Timesheets

Hours worked and costs, digitally.

Approval

Hours approved by the client.

Invoices

Invoices with corrections according to the standard.

Validation

Messages checked before sending.

Who we build a SETU integration for

The integration is meant for parties that exchange messages in the staffing industry.

Temping agencies

Large clients ask for it. Timesheets are at the core.

Hirers

Multiple staffing agencies. One way of submitting matters most.

Vendor management platforms

A portal for suppliers. The requests are what's needed.

Software suppliers

Back office for staffing agencies. The standard is at the core.

Technology and integrations

This page is about integrations based on SETU. For staffing agencies, see our page on staffing agency software; for a widely used back-office system, our page on an Easyflex integration; and for flexworkers' hours, our page on an app for hours registration for flexible staffing. You can read about our approach on building software.

If you hold the SNA certification and want to go into every inspection well prepared, take a look at our software for the SNA inspection file.

SETU standards Ordering and Selection Assignment Timecard Invoice Version 2.0 Message validation Hours approval Back-office integration Log per message

Why Appfront for your SETU integration?

An hour that is retyped three times has three chances to go wrong. That is what we build on: messages that follow the standard, hours that go straight through, and a single integration for all parties.

Fewer credit notes

The invoice matches the approved hours.

Paid faster

No discussion about what was worked.

One way

All parties through the same standard.

Security and privacy in a SETU integration

The integration processes data about flex workers, their hours and rates. Only the data the standard requires is exchanged, connections are encrypted, and every message is logged.

The integration runs in a European data centre or in your own environment, with encrypted storage and daily backups.

Frequently asked questions about a SETU integration

Questions that staffing agencies and hirers ask before they get started.

The Stichting Elektronische Transacties Uitzendbranche (SETU) maintains standards for message exchange between staffing agencies and their clients, from the request for a candidate to the invoice. The standards are free to use. SETU was founded by parties from the industry, and the standards are maintained in consultation with staffing agencies, clients and software suppliers.

Among others, messages for requesting and proposing candidates, for placement details, for hours worked and costs, and for invoices. Which ones you need depends on what you exchange with your parties. Many integrations start with the timesheet and the invoice, because that is where most retyping happens, and then expand to requests and placements.

In 2024, the standards for the process from request to payment were modernised. Not all parties switched at the same time, so an integration sometimes has to handle multiple versions. We take that into account in the first step.

No. The integration can use SETU with parties that support it, and another route with parties that do not, such as a file or a portal. The more parties use the standard, the more you benefit. A client with many staffing agencies can also ask for the standard in new agreements.

The timesheet goes to the hirer, who approves or rejects it. Approved hours go straight to the staffing agency for payroll and invoicing. A rejection comes back with a reason, so the discrepancy is resolved before invoicing.

The integration validates messages against the standard before they are sent. An error is reported with the reason, and a received message that is incorrect is set aside for review. The log shows for each message when it was sent, received and processed, so a question from a party can be answered quickly.

For staffing agencies with clients who ask for SETU, for hirers who work with multiple staffing agencies, and for suppliers of back-office or workforce procurement software who want to support the standard.

Hours and invoices without retyping?

Tell us which parties you exchange messages with, which systems you use and where data is retyped today. We'll show you what the integration would look like.

Edit content