Your Tech Club
INTEGRATIONSAFAS PROFIT + LOKET.NL

Loket and AFAS integration

An integration between Loket.nl and AFAS comes down to two questions. How does the journal entry from Loket get into AFAS's accounting? And if HR works in AFAS Profit, how does a new employee reach the payroll firm in Loket? A standard integration exists for the first, but it's described for AFAS SB.

More on AFAS Profit integration
4.8 from 127 reviews
Kiwa ISO 9001 certification markKiwa ISO 27001 certification markISO 9001 & 27001
AFAS ProfitHR and payroll
  • New employee as a concept goes to Loket.nl
  • Changes to the employment goes to Loket.nl
  • Journal entry to AFAS SB comes from Loket.nl
  • Journal entry to AFAS Profit comes from Loket.nl
Loket.nlHR and payroll

Built for clients including Tata Steel, M&G Investments, Digistore24, Toppers in Concert, Bar-le-Duc and Loogman

  • Tata Steel
  • M&G Investments
  • Signal.Stream
  • Amsterdam Dance Event
  • Tyson 2.0
  • Digistore24
  • Bar-le-Duc
  • Verkade
  • RUMAG
  • ADC
  • TOTO
  • Data Science Lab
  • Qualogy
  • Complex
  • Xplct
  • DGI
  • Jack's Casino
  • Kosso Nutrition
  • Crocodile
  • Tata Steel
  • M&G Investments
  • Signal.Stream
  • Amsterdam Dance Event
  • Tyson 2.0
  • Digistore24
  • Bar-le-Duc
  • Verkade
  • RUMAG
  • ADC
  • TOTO
  • Data Science Lab
  • Qualogy
  • Complex
  • Xplct
  • DGI
  • Jack's Casino
  • Kosso Nutrition
  • Crocodile
The situation

The standard integration with Loket transfers the journal entries from payroll to AFAS SB automatically every night. Only an accountant can activate it, in the Admin Center. If you use AFAS Profit, check whether it also applies to your environment. Otherwise it goes through Loket's API and Profit's UpdateConnectors.

The second question comes up when AFAS Profit is your HR system but payroll sits with a firm in Loket. A new employee then exists in AFAS first. Loket needs many mandatory fields for a full employee, which an HR system often doesn't have. That's why Loket recommends a concept employee, which the firm completes.

What moves between them

For each item: which direction it goes, when, and why. This is the starting point; in the first conversation we fit it to your situation.

  1. 01New employee as a conceptAFAS Profit → Loket.nlwhen someone joins in AFAS

    A GetConnector returns the new employee with the data HR has. The integration turns it into a concept employee in Loket. The payroll firm completes and converts it.

  2. 02Changes to the employmentAFAS Profit → Loket.nlon a change in AFAS

    A new department or function goes to the employment in Loket. Pay and terms stay with the firm in Loket, unless you agree otherwise together.

  3. 03Journal entry to AFAS SBLoket.nl → AFAS Profitevery night

    With the standard integration, the journal entries from payroll go to AFAS SB automatically.

  4. 04Journal entry to AFAS ProfitLoket.nl → AFAS Profitafter a payroll run is approved

    The integration fetches the journal run through Loket's API and posts it with the FiEntries UpdateConnector in the right Profit administration.

Off the shelf or custom

Not always. If an existing integration for AFAS Profit and Loket.nl does exactly what you need, we'll tell you.

What already exists

For AFAS SB there's a standard integration with Loket. You request it by email, follow the step-by-step plan and test it before activating it for good. Only an accountant can activate it, in the Admin Center.

If no standard integration fits your situation, for example for AFAS Profit or for the flow from HR to Loket, you build it on Loket's API and Profit's connectors. We can connect Loket to any system, including AFAS Profit.

When you need custom work
  • HR works in AFAS Profit and new employees have to be ready in Loket as concept employees.
  • Journal entries from Loket have to land in AFAS Profit, in the right administration per employer.
  • You want to manage departments and cost centres in one place and have the other system follow.
  • You want a check on the journal entry before it's posted in AFAS.
AI in between

AI reads, sorts and prepares a suggestion. Where it matters, a person decides.

Completing the concept

AI compares the concept employee with the data in AFAS and reports what the firm still needs, such as a missing IBAN or a different start date. The firm completes it; AI changes nothing in Loket.

Checking the journal entry

Before the posting goes into AFAS, an AI step compares it with previous months and flags anything unusual. The controller decides whether it's posted.

What to watch

Which system leads

AFAS leads for what HR records, such as name, address, department and start date. Loket for everything payroll needs. Decide per field which system wins, or they overwrite each other.

The right administration in Profit

The FiEntries UpdateConnector uses the administration from the UnId field. Leave it empty and it posts in the administration the integration's user last used. So always fill it in.

Rights on both sides

In Loket, the client needs access to the action and the user needs the rights; the firm usually manages that user. In AFAS, give the integration its own user with only the connectors it needs.

Sensitive data

BSN, pay and bank account only belong in the connectors and flows that genuinely need them. Don't put them in a general GetConnector that other integrations also use.

How we build an integration

  1. What goes where

    Which data moves, in which direction, and which system wins when two values differ. That is written down before anything gets built. For this integration, that means: New employee as a concept, Changes to the employment, Journal entry to AFAS SB, Journal entry to AFAS Profit.

  2. Fields and rules

    For every field, how it translates between the systems: statuses, VAT codes, general ledger accounts, item numbers. And what happens with a duplicate or a missing value. For this integration, that means: Which system leads, The right administration in Profit, Rights on both sides, Sensitive data.

  3. Testing with real cases

    In a sandbox or test administration, with the exceptions you actually run into: credit notes, partial deliveries, changed customer details.

  4. Live, with logging and monitoring

    Every sync is logged, and when something fails, someone gets an alert. If a vendor changes its API, we update the integration.

The Your Tech Club team at the office in Amsterdam
Amsterdam
Who you'll talk to

No account manager. You talk to someone who builds integrations themselves, and who will tell you when a standard integration is enough.

Joey van VlietJoey van VlietFounder
Yassine SeghrouchniYassine SeghrouchniFounder
  • Office on the Duivendrechtsekade in Amsterdam
  • ISO 9001 and ISO 27001, certified by Kiwa
  • 500 projects delivered
  • 4.8 from 127 reviews
Frequently asked questions

Is there a standard integration between Loket and AFAS?

For AFAS SB, yes: journal entries from Loket go to SB automatically every night, and an accountant activates the integration in the Admin Center. For AFAS Profit, you build the integration on Loket's API and Profit's UpdateConnectors, unless an integration for your environment already exists.

How do journal entries from Loket get into AFAS Profit?

The integration fetches the journal run through Loket's API and posts it with the FiEntries UpdateConnector in Profit. The employer needs the journaliseren module in Loket.

Can a new employee go from AFAS to Loket automatically?

Yes, as a concept employee. AFAS supplies what HR knows, the payroll firm completes the rest and converts it into an actual employee. That's the route Loket itself recommends.

Who manages the integration between Loket and AFAS?

That's up to you to agree. In Loket, the firm usually manages the user and its rights, and Loket the client. In AFAS, you manage the user and the app connector yourself. Agree who gets notified when something goes wrong.