FixControl
AFAS Profit integration

AFAS data read-only, answers only after approval

An employee of your organization asks about their leave balance or a line on their payslip. FixControl reads the named fields it needs from your own AFAS Profit views, filtered on that one person, and writes nothing back. The answer about their own situation is a draft until someone on your team approves it.

Book a demoSee the HR permission model
Read-only — nothing is written backNamed fields, not a personnel fileCredentials per organization
What it does

What the AFAS Profit connection covers

Read-only by construction

The connection has read methods and nothing else. No leave request, no profile change, no record created in AFAS — FixControl reads what an answer needs and leaves your HR system exactly as it was.

Your own GetConnector views

FixControl talks to AFAS Profit through three GetConnector views you define yourself, with prescribed field ids: employee, leave and payroll. If your system names fields differently, you map them in your own view — FixControl never guesses a field.

One person per call, projected onto named fields

Every call filters on a single person and takes at most one row, then projects the response onto the fixed shape those field ids describe. Widening a view on your side cannot leak extra personal data into an answer.

Credentials per organization

An app-connector token — encrypted at rest — plus your ProfitRestServices URL and the three view names. A half-filled entry is ignored rather than merged with platform defaults, so one environment's token can never be paired with another environment's host.

A connection check, before an employee runs into it

A periodic check reads the employee view with a filter value that can match no person. A revoked token or a rotated secret surfaces as a failing check, an audit event and an administrator notification — not as a failed answer to an employee.

The data is read; the answer still needs a person

What comes back from AFAS does not become an outgoing answer on its own. A question about someone's own situation becomes a draft or a review case, bound to a named reviewer, and a second person approves before it is delivered.

Capabilities & health

What the AFAS connection can and cannot do

The connection has one health capability on purpose: the connection itself. A single missing employee record is a data condition, not a broken integration, so it routes that one question to a person instead of colouring the connection red for everyone.

Remaining leave hours
Configuration-dependent

Read from the leave view you define, with the as-of date that belongs to the value. Available where that view exists and exposes the prescribed field ids.

Payroll explanation code
Configuration-dependent

An explanation code with an as-of date — never an amount, never a payslip document. Reading it also requires the separate payroll permission on the reader's project role.

Field projection on every call
Supported

Filtering on one person and projecting onto the prescribed fields is not configurable — the raw row never leaves the connector, so it cannot end up in an answer or in a prompt.

Connection check
Supported

A filtered read that can match no employee proves the endpoint is reachable and the token is authorised for that view, without touching a real person's record.

Writing anything back to AFAS
Not available — by design

Not part of the connection, at any level. There is no create, update or delete path — no leave request, no absence registration, no profile change.

Salary amounts & payslip documents
Not available — by design

Out of scope on purpose. The payroll view returns an explanation code and its as-of date; amounts and documents are not read, so they cannot appear in an answer or in an audit record.

When AFAS cannot answer

A missing value never becomes a made-up one

Honest failure, with a reason on record
A missing record, a value that cannot be parsed, an unexpected response shape and an unreachable endpoint all lead to the same place: the question is handed to a person, and the reason is recorded. No number is invented, and a leave balance is never quietly defaulted to zero. Error messages carry a stable code and at most an HTTP status — never a token, a URL, a response body or an e-mail address. The model never sees any of this: it receives the question text to propose a classification, and personnel data, retrieved documents and answer bodies are not sent to a model at all.
FAQ

Questions about the AFAS Profit integration

Does FixControl write anything back to AFAS?+
No. The connection is read-only by construction: it has read methods and no create, update or delete path. An employee cannot request leave or change a record through FixControl, and no answer flow can either.
Which fields does FixControl read?+
The ones your three GetConnector views expose under prescribed field ids: employee id, e-mail, employment percentage, employment type and collective agreement; remaining leave hours with an as-of date; and a payroll explanation code with an as-of date. Never a salary amount, never a payslip document.
What happens if AFAS is unreachable or a value is missing?+
The question goes to a person and the reason is recorded. A missing record, an unparseable value or an unexpected response shape are treated the same way as an outage — the one thing that never happens is an invented number or a leave balance defaulted to zero.
Where do the credentials live?+
With your own organization. The app-connector token is encrypted at rest and stored against your organization's connection entry, together with your ProfitRestServices URL and view names. A half-filled entry is ignored rather than merged with platform defaults, so credentials from one environment can never be paired with another environment's host. Creating that entry — and naming the projects that may use it — is done together with us during onboarding; there is no self-service connection screen for AFAS yet.
Can a project start reading from AFAS on its own?+
No. Configuring the credentials only makes the connection available to your organization; a project has to list it as an active connection before anything is read, and answering has to be switched on for that project at all. An organization that configured nothing simply has no such connection.
Does an answer about my leave balance go out automatically?+
No. Anything touching an employee's own situation becomes a draft or a review case. The approval is bound to that exact answer text, the person who requested it cannot decide it, it expires after 72 hours on the server, and delivery consumes it so a double click cannot send twice.
Keep exploring
HR questions with the right permissions

The permission model, assignment and approval around the answer.

Visma Raet Youforce

The same read-only contract on a Youforce domain API.

AI approval ledger

Who approved what, from which channel, on which grounds.

See what an AFAS-backed answer has to pass

Book a demo and follow one leave question from the AFAS read through assignment, approval and delivery.

Book a demoTalk to us