Integrations

Connect ERP, HR and time management to Pactos

Your data stays where it belongs. Pactos docks onto the systems you already run and takes care of the connection in between.

Book a call What can be connected

Tap a system to see what flows

Without a connection you pay twice

An external workforce always touches several systems at once. Whatever is not connected gets transferred by hand.

Master data maintained twice

Every person exists in the VMS and in the HR system. Change only one side and you create a discrepancy that surfaces at invoicing.

Double maintenance

Times travel by file

Clock-in times sit in time management, approval happens by spreadsheet and inbox. Every correction has to be entered twice.

Broken media chain

Nobody knows which system is right

If the assignment reads differently in the ERP than in the VMS, habit decides. Without a defined leading system, every discrepancy stays a negotiation.

Unclear ownership

Two routes into your systems

Which one fits depends on your integration platform and on who owns the interface. Both are open for every connected system.

Your platform distributes

Pactos supplies the format, your platform distributes it

Pactos provides documented interfaces and a fixed output format. Mapping onto your target structures is handled by the integration platform you already run.

  • Fits the integration platform you already run
  • Your integration team keeps control over field mapping
  • Changes to your target structures do not affect Pactos

The usual route when an integration platform is already in house.

Pactos takes it on

You supply the definition, Pactos handles the logic

You provide your existing interface definitions. Pactos maps them onto the target format and owns the connection, including retries after errors and logging.

  • No effort for your integration team
  • Also for systems without an integration platform of their own
  • Every field and every rule is put in writing

The usual route when ownership of the interface sits with the business unit.

What gets connected

Which systems, which direction

Every function of the user interface is available through an interface as well. What flows in the end is your decision, process by process.

Which systems are in your landscape and which fields are really needed is settled in the technical call.
SystemWhat flowsDirection
ERP and finance Staffing requests, orders and cost centers come in, verified invoices go back to accounting both directions
HR system Person master data, employment status and approvals, in the direction you define to Pactos
Time management Bookings and calculated daily values come in, absences go out. Correction and approval happen in Pactos both directions
Staffing provider systems Quotes, assignment data and records, without anyone retyping them to Pactos
Users and permissions Sign-in and roles from your central user directory, instead of a second user list to Pactos
Works standalone Pactos runs without any integration from day one. If a system offers no open interface, the same content arrives as a file on a schedule. With receipt and log both directions
Hosting Data centers in the EU, every tenant kept separate.
Permissions Roles per tenant and business unit. Everyone sees their own.
Traceable Every transfer is logged, with timestamp and trigger.
Change-proof A system change hits the connection, not your processes.

How a connection is set up

The order is not negotiable, because each step builds on the previous one. The leading system is fixed beforehand, not during operation.

Gather requirements

Which processes in the first stage, which fields, which formats, which rules. And which system leads.

Enable access

Access and users are enabled individually, per environment. We go through the list together.

Map and check fields

Every field is mapped and checked against your test environment before real data flows.

Test the chain, then go live

One run from source to approval. After that the sync runs, with a log of every transfer.

Before the first field

The questions we ask first

This list comes from real integration calls. Pass it to your IT as it is: with the answers in hand, the connection stands after one meeting.

System landscape

  • Which solution is in use, and in which version?
  • Is there an integration platform, and which one?
  • Is a migration planned, and in what time frame?

Ownership and process

  • Which data should run in which direction?
  • Who owns the interface: IT, the business unit or a partner?
  • Is there an interface definition already?
  • Which processes belong in the first stage, and which system leads?
  • When is master data handed over: on contract signature or at the start of an assignment?

Technology and testing

  • Mandatory fields, formats, validation rules?
  • How often: immediately, in scheduled runs or on every change?
  • Should roles and permissions be transferred?
  • Is there a test environment, and who tests on your side?

Frequently asked questions

Who owns the interface?
You decide that with the integration route. If Pactos supplies the format and your integration platform distributes it, ownership sits with your integration team. If you provide the definition and Pactos implements it, it sits with us. We put in writing what applies before the first field flows.
How often is data transferred?
You decide that per process. Master data usually runs on every change, times and billing data in scheduled runs. What applies to which process is one of the questions to settle before the start.
What if a system has no open interface?
Then the exchange runs as a file. Some systems deliberately offer no open interface, only a file exchange on a schedule. That is not a special case but a route of its own, with a fixed schedule, receipt and log.
What does leading system mean?
For every data field there is exactly one system whose value applies. Without that rule, the last write wins whenever there is a discrepancy, and nobody can say which state was correct. We fix it per process, not blanket for the whole connection.
What happens if we change our ERP or HR system?
The connection hangs on a layer of its own, not on your processes. A system change hits that layer and the field mapping, not the workflows in Pactos. That is precisely why it sits separately.

Go through interfaces and data flows in concrete terms

Bring your list of systems. We clarify data sources, leading systems and the realistic scope of a first integration stage.

Discuss integrations