There is a new version of the PCC for Profit 7. You can download the PCC through Profit or InSite. A download is also available on the AFAS Customer Portal. If you are allowed to do your own installations/changes on your PC, you can update the PCC yourself. The PCC for Profit 7 can also be used in Profit 6.
The PCC for Profit 6 can also be used for Profit 7. Compared to Profit 6, the PCC of Profit 7 has one change: If you send a new email message, the PCC will try to find the contact in Profit, based on the addressees e-mail address. The recognition of the e-mail address in Profit has been improved.
The new version of the PCC is not required. If you still have the PCC from Profit 1 installed, it can be used in Profit 7. If you want to install the PCC or roll it out as an administrator, use the latest version.
From Profit 7 onwards, the AFAS token in the header of the connector call should always be sent Base64-encoded. This applies to both REST/JSON and SOAP/XML. If not, an error message will be given. There is one exception: with SOAP, it is also possible to include the token in the SOAP body. In that case, everything just keeps working without Base64 encoding being required.
We have already announced this in de releasenotes of Profit 6. Since then, we have monitored connector calls on this aspect and proactively approached our partners when necessary.
You can find all the information and code examples on the Help Centre
On a GetConnector call, AFAS' SQL server compiled the response. From Profit 7 onwards, this has been changed and the response comes directly from Profit. These include both JSON for REST and XML for SOAP.
Note:
The format of the results is different. These adjustments may affect custom string processing of raw JSON / XML. If you use a standard XML/JSON parser, this will not cause a problem.
The changes are:
This change provides the following benefits:
To improve the performance of metainfo calls, the format of the response has been changed. The calls in question are metainfo, metainfo/get and metainfo/update. The response to a metainfo call now results in a string without spaces or enters, or in other words the result is no longer a formatted JSON.
From Profit 7, you can add an explanation when rejecting an applicant. The Explanation Rejection field is immediately visible after the release of Profit 7. To use this explanation effectively, you need to link the field to the message template being sent. This way, you make sure the recipient clearly understands why he or she is not considered for the job.
We introduced a new communication profile for Google Maps in Profit 6 and in Profit 7, TomTom (ANWB) joins it. You use (per employer) one of these profiles to automatically calculate employee travel distances. Switch to Google Maps or TomTom as soon as possible, as Google is discontinuing the Directions API. This means that distance calculations can no longer be calculated with the Directions API. Below are several situations where you may need to take action.
I had already set up the Google Maps communication profile and continue to use it
No action is required for distance calculation in Profit and InSite. Since TomTom is now also available for distance calculation, you do have to specify for each employer whether you want to use Google Maps or TomTom for distance calculation. If you had already set up Google Maps, then during the transition to Profit 7, this choice will be automatically populated with Google Maps. See also the description below regarding Conversion distance calculation and the roadmap.
I want to use Google Maps or TomTom after switching to Profit 7
Note:
The following applies to Profit 7 in combination with a yet-to-be-released Pocket version. If your users do not yet have this Pocket version, the situation as it was in Profit 6 applies. As soon as it is known when the version of AFAS Pocket will be delivered, we will mention it on this page.
If you have chosen Google Maps or TomTom by employer, this choice also applies to the Pocket app. In Pocket, a route map is shown when calculating distance via Google Maps. When calculating distance via TomTom, this is unfortunately not possible; however, the distance is of course calculated via TomTom.
If you have not set up the communication profile or have not made a choice per employer, the distance calculation in Pocket will (for now) still be done based on the Directions API (based on the Google Maps API Key in the Pocket settings). We advise you to switch to TomTom or Google Maps as soon as possible, as Google is discontinuing the Directions API.
The following applies to displaying addresses in Pocket (e.g. in CRM, Who's Who, properties project etc.):
With the introduction of TomTom (ANWB) , a second way of calculating distances has emerged, in addition to the existing ability to do so via Google. We have made it possible to choose from these options per employer. When transitioning from Profit 6 to 7, some environments are automatically converted. The conversion causes the 'Calculate distances by' field at employer level to be changed to the value 'Google Maps API'. This avoids as much as possible the disappearance of the existing roadmap for customers who have always used Google. A route map shows the route from the location 'From' to the location 'To'.
Whether your environment is converted depends on whether the ‘Record work locations at employee' activation is on:
The following fields and tabs have been added for the new functionality e-invoicing via Peppol:
As from Profit 7 onwards, we support RCSFI version 3.7. In the transition from RGS version 3.6 to 3.7, 185 RGS codes were added and 1 RGS code replaced. Seven RCSFI codes have also been set to inactive and deleted from Profit. If an inactive code was linked to a ledger account, we cleared the RCSFI reference code field.
What does this mean for you and what should you do? If you use the RCSFI and/or the RCSFI bridging statement, check for which general ledger accounts this RCSFI reference code field is now empty. You need to link a new code here.
Recipe calculation allows you to calculate raw materials, nutritional values, ingredients and cost prices from these compositions with multiple layers.
This functionality is only available under R&D mode and in combination with the Bakery licence. Discuss with your consultant whether you can use this in your Profit environment and test it first in a test or acceptance environment.
In the UpdateConnector for receipts (FbGoodsReceived) and the Pocket app, the administration determination has been changed. If the purchase relationship and the project are included but the administration is not, Profit will look at 1 to determine the administration. Purchase contact profile, 2. Standard procurement relationship profile and 3. Project.
Besides month, from 1 January 2026, 4-weeks will also be allowed as the return period for StiPP submission. You use the 4-week return period for the pay periods 'week' and '4 weeks'.
If you have two payroll periods, both month and 4-week, you have to create two declaration files! Previously, you only had to create one file because everything was converted to month.
In the Profit reports for the placement/order confirmation received by the employee, the fields Method accrual holiday pay, Method minimum holiday pay, Accrual from week, Base date holiday pay and Percentage holiday pay have been added.
Do you have your own reports? Then adjust those.
The following changes have been implemented in planned tasks:
The following changes are important:
Mutatieniveaus bij Soort loonschaal
Als je op een bestaande plaatsingsregel het veld Soort loonschaal wijzigt, dan moeten daarnaast ook de velden Loonschaal en Trede opnieuw gekozen worden en bij het wijzigen van het veld Loonschaal ook het veld Trede. Voor deze drie velden zijn de volgende mutatie niveaus van toepassing: 1. Soort loonschaal, 2. Loonschaal en 3. Trede. Kortom, als je op een hoog niveau afwijkt (Soort loonschaal), moet je ook de lagere velden invullen (Loonschaal en Trede).
UpdateConnector PtPlacementContract en import
Het volgende is gewijzigd voor plaatsingen en de velden Soort loonschaal, Loonschaal en Trede:
Boekingslay-out Prijsafspraak plaatsing
Vervang in je eigen boekingslay-out die gebaseerd zijn op Prijsafspraak plaatsing en Prijsafspraak plaatsing InSite het oude veld Soort loonschaal van de functie door het nieuwe veld Soort loonschaal van de plaatsingsregel (onder Algemene velden) om bij Rekenen met de juiste loonschaal te zien.
In Profit 7 set the Method Compaction field in the sales relationship profile. Profit then merges the lines based on the method you chose on the invoice. Previously, you could only manage this by creating a grouping on the project invoice report. This grouping is no longer needed on the report if you use Method Compaction on the sales relationship profile or deviation on the project.
Check whether you still need the grouping or switch to the new functionality.
In Profit 7 several optimisations were delivered for OHW method 3. The optimisations below affect the calculations within Profit. Check your reporting on these points:
In the UpdateConnector for receipts (FbGoodsReceived) and the Pocket app, the administration determination has been changed. If the purchase relationship and the project are included but the administration is not, Profit will look at 1 to determine the administration. Purchase contact profile, 2. Standard procurement relationship profile and 3. Project.