Skip to content

Between the handshake and the payslip

A placement is only done when the payslip and the invoice are right. For an international staffing group with several labels across several European countries, we implemented an ATS on Salesforce and built the mid and back office, custom for each label: one platform from first intake to payroll and invoicing.

Abstract illustration of connected labels around one shared platform
Layers on one platform
3

This is the story of one placement and the platform that carries it. Qantara implemented a complete ATS on Salesforce for an international staffing group, for every label in the group. On top of it we built the mid and back office, custom for each label. Together they form one platform for the front, mid and back office: from first intake to payslip and invoice.

Friday, half past four

The office is emptying out. Coats go on, someone switches off the coffee machine. Then a consultant's phone rings. She knows the number. She has been waiting for it all week.

The client wants the candidate. He can start in two weeks.

She hangs up and sits still for a moment. Weeks of calls, a candidate who wavered, a client who wanted one more interview. This is the moment she does the job for. Her week is done. For everyone else in the business, the work starts now.

Because behind that one yes sits a whole chain. Which legal entity becomes the employer? Is the margin right, and who needs to approve it? Has the ID been checked? Is the right contract ready, in the right language, and signed before day one? And later, when the month closes: do the hours, the pay, the invoice and the payslip all match?

A single agency with one office can run that on quick conversations and a good spreadsheet. A group with several labels across several countries cannot. A mistake doesn't show up on Friday afternoon. It surfaces weeks later, somewhere down the chain, on the desk of someone the consultant has never spoken to.

One group, many faces

The client is an international group in staffing, secondment and recruitment. It runs several labels, each with its own brand, its own market and its own way of working. The labels have offices in several European countries and place specialists with clients, often large organisations with long-running projects.

They place people in more than one way: secondment on the agency's payroll, project staffing, freelance contracting and permanent recruitment. Each model comes with its own contracts, its own rules and its own money flow.

Consultants, account managers and recruiters from every label work on the platform. Next to them sit contract management, compliance, payroll, billing and credit control. They are in different teams, sometimes in different countries, and they rarely talk. Yet they all work on the same placement.

Front, mid and back office in staffing

In staffing, the front office finds candidates and clients. The mid office turns a placement into a complete and lawful assignment. The back office turns hours into a payslip and an invoice.

  • Front office: client relationships, vacancies, candidates, matching and the submission to the client. This is where the ATS and CRM live.
  • Mid office: rates and margin, contracts and signatures, ID checks and other compliance, extensions, changes and the end of an assignment.
  • Back office: hours, payroll, invoicing, credit control, the right legal employer for every placement, and the numbers per label and country.

Software vendors often sell these three layers separately and join them with integrations. For this group we set them up as one chain, with the placement as the shared starting point. We held to one rule: a placement is only done when the payslip and the invoice are right.

01

Challenge

Every label, its own voice

A label is more than a logo. It is its own pitch, its own circle of clients, its own tone in an email to a candidate. The labels wanted to keep that, and rightly so. At the same time the group wants one view of candidates, placements and margins. And a candidate known to one label today may be a better fit for another label tomorrow.

That was the first tension. Every label wanted to feel at home. The group wanted one foundation.

Every country, its own rulebook

Then there is the border. Placing people across borders means playing by different rules in each country. And what differs per country is exactly what makes a placement lawful:

  • The Netherlands: terms equivalent to the hirer's own staff under the agency collective agreement (a full package since 2026), enforcement of the rules on freelance contracting (Wet DBA), and the Wtta licensing regime for staffing providers, in force from 1 January 2027 and enforced from 1 January 2028.
  • Other EU countries: their own licensing or recognition rules for staffing providers, sometimes a maximum term with the same hirer, their own equal-pay rules and requirements for a written contract per assignment.

On top of that, licences and recognitions belong to legal entities, not to brands. The label's name is on the contract, but every contract and every invoice has to point to the employer that legally stands behind it. Link the wrong entity and the paperwork no longer holds, however good the placement is.

Month end: the payroll run

Fast forward to the end of the month. In payroll, the run is ready to go. Line after line: a rate, a pay component, an employer. This is where you find out whether Friday afternoon was recorded properly.

In staffing, margin is the gap between what an hour earns and what it costs. Across the industry, a wrong hourly rate often surfaces weeks later as a credit note or a payroll correction. By then the consultant is long busy with the next placement.

And the cost of an hour is more than the hourly wage. In the Netherlands it includes reserves for holiday allowance (at least 8 percent), paid leave and public holidays, plus employer contributions and pension. That differs per collective agreement, per country and per year. On the invoice side, large clients expect a purchase order number, the right VAT treatment and, in the Netherlands, often part of the amount paid into a blocked G-account. Get one detail wrong and the invoice comes back and payment slips.

The lesson is simple and strict: record every rate once, then use it the same way everywhere.

Two roads, both dead ends

Every label works differently: other contract types, other approval limits, other templates, sometimes another language. Off-the-shelf software then forces a choice. Put every label into the same mould, and nobody recognises their own work any more. Or give each label its own package with its own links to payroll and invoicing, and the group loses the overview.

Neither suits a group where every label sets its own course. There had to be a third road.

02

Approach

The turning point: one core, a custom layer per label

That third road starts with two axes: label and country. Access, email and document templates, portals, margin calculation and approval rules all hang off that combination.

Underneath sits a core that is the same across the group: candidates, clients, placements and legal entities. Everything above it we built to fit each label. So a consultant across the border works with their own label's templates and margin rules, while finance sees the whole group. The label keeps its voice. The group gets its foundation.

Front office: the ATS implementation on Salesforce

We implemented the ATS on Salesforce for every label. This is where the consultant's Friday afternoon begins. Among other things, she can:

  • create companies from Dutch Chamber of Commerce data and manage contacts, with email and meetings logged automatically
  • drop a CV into a form that fills itself in, with a duplicate check across all labels
  • search on skills, talent pools and distance
  • move candidates through a fixed pipeline, from shortlist to ready to start
  • put a candidate forward with a branded CV, a margin calculation and a short pitch in a single email
  • publish vacancies on the label websites and on job boards

If another label already knows the candidate, the consultant requests access. That way there is one profile per person, with clear agreements between the labels.

Mid office: from yes to ready to start

The mid office is where most of the custom work sits, and most of the tension. This is where Friday's yes becomes an assignment that holds up legally and financially. For each label we built the steps between the handshake and the first working day:

  • Margin calculator per country: cost price, margin in euros and percent, the rate needed for each margin tier and, for the Netherlands, the uplift for equal pay with the hirer's staff.
  • Tiered margin approval: a matrix per label and contract type decides who signs off a placement below target.
  • Contracts and letters: generated from templates in the recipient's language and sent straight to e-signature.
  • Compliance per placement: document types with approval and expiry dates, ID verification and onboarding checklists that update themselves.
  • Changes with a fixed route: edits to contract-critical data go to sales for review first, then to legal. Extensions, offboarding and bulk pay and rate increases follow set steps too.

Rates and wages are stored per type of work with an effective date. A rate is recorded once and used the same way everywhere after that. Anyone looking back can see exactly which rate and which contract applied on a given day.

Back office: the right employer, the right numbers

Every placement is tied to a legal employer with its own company code in the ERP system. The platform sends placements, rates and contacts to the ERP system for payroll and invoicing. Every night the payroll and billing data flows back, so by morning the platform shows what has been paid and invoiced.

The people behind the scenes have work queues for payroll, billing, credit control, compliance and legal, mid office and HR. Anything that needs attention is there for the whole team to pick up. Nobody has to wait for someone else to remember.

Portals in each label's branding

Candidates and clients have their own portal in the label's branding. Professionals on assignment also use the candidate portal for their own admin. The portal copy is multilingual, so candidates and clients work in their own language. The portals are not a bolt-on: they are part of the same platform and read from the same core.

How we worked

Qantara is one founder working with trusted developers and specialists. The custom layer for each label follows how a placement actually runs at that label. We didn't impose a standard process. Each label keeps its own way of working, on one shared core.

03

Result

Friday, half past four, again

Back to the empty office. The phone, the number she knows, the yes she waited all week for. The consultant records the placement. From there, the rest follows a set route.

The platform calculates the margin and, where needed, puts it in front of whoever decides. The contract comes out of her label's template, in the candidate's language, and goes out for signature. The documents run through the checklist. In payroll, the placement arrives with the right employer and the right rate.

She closes her laptop. The rest of the chain knows what to do.

Monday morning, in another country

A label manager in another country opens the same platform. She sees her own label's templates, the margin rules that belong to her country and a candidate portal in her candidates' language. She mostly notices the group when it helps: a candidate another label already knows, a colleague in finance looking at the same numbers.

One platform for the whole group, and still it feels like hers. That was the brief. And the group has one source for placements, rates and margins.

The platform in numbers

This is the scale of the platform the group runs on, in rounded figures:

  • every label in the group, with offices in several European countries
  • internal users in many roles, from sales to payroll
  • several legal employers, each with its own company code in the ERP system
  • dozens of teams across the offices
  • more than 500 automations and guided screens
  • more than 100 business rules that check a placement is complete and correct before it moves on
  • hundreds of email and document templates, per label and per language
  • more than 10 integrations, including the ERP system, email and calendar, the label websites, job boards, e-signature, ID verification and the Dutch Chamber of Commerce register
  • the candidate and placement history of every label on the same platform

What we take from it

This project showed how much work sits between recruitment and invoice, and how little of it fits a standard ATS. That knowledge goes into everything we build for the industry, including Qantara Recruit, our own ATS and CRM for staffing agencies.

A placement starts with a phone call on a Friday afternoon. It is only done when the payslip and the invoice are right. Everything in between is our craft.

Delivered

Salesforce ATS for every label

Client management, intake, search, pipeline and submissions, set up for every label in the group.

Margin calculation and approval

A calculator per country, including Dutch equal-pay rules, and an approval matrix per label and contract type.

Contracts and e-signature

Contracts and letters from templates, in the recipient's language, sent straight for signature.

Compliance per placement

Documents with expiry dates, ID verification and onboarding checklists that update themselves.

Payroll and invoicing hand-off

Placements, rates and contacts go to the ERP system. Payroll and billing data comes back every night.

Multiple entities and work queues

Every placement under the right legal employer, with queues for payroll, billing, credit control and legal.

Questions

Frequently asked questions

The front office is where you find candidates and clients: relationship management, vacancies, matching and submissions, usually in an ATS. The mid office turns a placement into a complete assignment, with rate, margin, contract, signature and compliance. The back office turns hours into a payslip and an invoice and keeps the numbers per entity. The better the three connect, the less anyone has to retype.
Yes. In this case, label and country form the axis for access, templates, portals and margin rules. Each label works with its own branding and agreements, while candidates, clients and placements sit in one shared core. If another label already knows a candidate, the consultant requests access, so there is one profile per person.
Keep one process model and capture the differences per country in configuration: a margin calculator per country, contract templates per language and legal employer, and rules that follow each country's labour law. Licences and recognitions belong to entities, so every placement is tied to the right employer. Payroll and accounting stay connected to the books of each entity.
Because labels in a group really differ: other contract types, other approval limits, other templates and sometimes another language. A standard setup forces everyone into one mould. Separate packages per label mean double work and extra integrations. We keep the core the same and build what each label needs on top. The platform stays manageable and every label recognises its own work.
Yes. The ATS in this case runs on Salesforce, and the mid- and back-office processes are built on it. Relationship management, automation and integrations are part of Salesforce's core, so most of the effort goes into the process itself. Qantara is not tied to one platform. We choose what fits the process and the organisation, and implement and integrate Salesforce when it is the best choice.
Start with the placement. It has to be complete before anything moves on: employer, rates, pay components, contacts and start date. In this case the platform sends placements, rates and contacts to the ERP system for payroll and invoicing, and the payroll and billing data comes back every night. Work queues show what still needs attention.
The Wtta, the Dutch licensing act for staffing providers, takes effect on 1 January 2027. From 1 January 2028 the Labour Inspectorate enforces it, and hirers may then only work with licensed or exempt providers. For the mid office this means recording, per placement, which entity is the employer, under which licence and with which pay terms. A system that tracks this per assignment makes the evidence easier to produce.
Because we treat client information as confidential. The client, its labels and their clients stay anonymous, and we only publish rounded figures we can back up. Want to know what a project like this looks like for your organisation? Ask us in a conversation. We still won't share confidential details about the client.
Yes. Not every agency needs a custom platform for a whole group of labels. For those agencies there is Qantara Recruit, our own ATS and CRM for staffing and recruitment agencies, built with the same knowledge of the chain from recruitment to invoice. Running several labels or countries, or does off-the-shelf software not fit your process? Then we work out together which approach suits you best.

Facing something similar?

Bring the problem. Then we decide together how to tackle it.

The first call is short and practical. If there is a fit, you get a clear next step.