There is no new version of the PCC for Profit 2. The PCC of Profit 1 therefore also applies to Profit 2. Older versions of the PCC can no longer be used.
You download the PCC via InSite or Profit, or via the AFAS Customer Portal. If you are allowed to do your own installations/changes on your PC, you can update the PCC yourself.
When a new record is created via the UpdateConnector, you get a response. Below is an example of a response:
{ "results": { "KnCustomK01": [
{ "SqNo": "4" },
{ "SqNo": "5" },
{ "SqNo": "6" }
] }}
You can offer multiple rules in one call. If a rule goes wrong, that rule is skipped. The response shows only the Ids of the rules that went right. You cannot find which rule went wrong in the result.
In case of a PUT (change to an existing rule), no response is sent.
No attempt is made to fill gaps in the numbering (this has been the case for a long time). These tables have an absolute sequence number, so not per contact as with the KnCustomLinkCxx tables. If you regularly delete and re-add many lines, these tables will reach the highest sequence number faster.
The following optimisations have been made:
Response to a new record
When a new record is created via the UpdateConnector, you get a response. As the KnCustomLinkCxx tables are numbered per contact, the contactId is also in the response. Below is an example of a response:
{ "results": { "KnCustomLinkC01": [
{ "CdId": "148", "SqNo": "5" },
{ "CdId": "148", "SqNo": "6" },
{ "CdId": "102", "SqNo": "21" },
{ "CdId": "102", "SqNo": "22" }
] }}
In case of a PUT (change to an existing rule), no response is sent.
You can offer several rules in one call. If a rule goes wrong, that rule is skipped. The response only shows the Ids of the rules that went well. You cannot find which rule went wrong in the result.
The Compare Organisation by (ViSe) field has an additional method to search by a previously granted authorisation, namely by Mandate Id (value 8). You enter the number you are looking for in the Compare by (Ds) field. You can use this field when changing an mandate via UPDATE/PUT. If the number exists, you can change the following fields. These are the same fields you can change in the property screen. No free fields are possible on a SEPA mandate.
Attention:
The changes apply to all UPDATE/PUT calls! Previously, it was possible to modify a field via the connector, while it was not possible to do so via the screen. This no longer works. No error message comes up; the value submitted in the field is simply ignored.
Response to a new record
When a new SEPA mandate is created via the UpdateConnector, you get a response with the Authorisation-Id. Below is an example of a response:
{ "results": { "FiSepaDirectDebit": { "Id": "256" } }}
From Profit 1, leave balances (of one leave type) are visible in the Pocket App. This depends on the leave type you have set as preference in the Pocket settings, General tab.
From Profit 2 onwards, the administrator can decide which leave balances are shown, so you are no longer bound to a specific leave type. You use a filter to determine which types of leave and therefore which leave balances are shown. During the migration, this filter is automatically filled for you with the leave type that was set in the Leave type preference field. So after the transition to Profit 2, Pocket users will see the same leave balances as voodien.
After the transition to Profit 2, you can complete the filter yourself with the leave types you want to show in Pocket. So this determines which leave balances are displayed in Pocket. After changing the filter, users must perform Refresh configuration, or the administrator performs this in Profit via General / AFAS Pocket / Users, Access tab, action Resresh configuration.
The Total TP (Total Transfer Price) field was also used in the previous version of Profit and was then positive for both mutation type 21 and 22, so no count could be made on it. This has now been changed. Mutation type 22 is now negative.
With this, the Total TP column can now be totalised to 0 if mutation type 22 exists. In addition, you can also cumulate the three amounts in the line of mutation type 22, with the balance showing the result yet to be taken.
Note:
This change affects your self-created reports in which the sign logic has been added on Mutation type 22. So for example: if mutation type = 22, then amount *-1).
Check and modify your reports if necessary.
In InSite, you can make an actual costing entry via the Calendar. For this, you now use the same entry layout as in Profit 22, namely Post calculation from Calendar (Profit). If you had created a copy of this entry layout in Profit 22, it will be available again in Profit 2 with all the settings you had already configured. After the migration to Profit 2, this entry layout will automatically be used when making actual costing entries via Calendar.
There are two new pages (with templates of the same name). These are included in the Agenda functionality:
From Profit 2 onwards, optimisations have been made for determining the reference period for public holiday hours.
To implement the new calculation, you need to open the properties of your existing, not yet finalised public holidays.
From 2024, there will be one statutory minimum hourly wage for all employees. The standard wage scales in the Profit CLAs (including the CLA for Temporary Workers) will be updated automatically.
Update all your own (client-specific) wage scales with the amounts for 2024 in good time. If you do not do this on time, declarations may not be paid because the hourly wages have not been updated.
If you created a placement with a proof of identity that was going to expire during the placement, a check appeared for the entire duration of the placement, which meant it was not possible to create a placement with an end date that was after the proof of identity's end date. This check has been disabled from Profit 2 onwards.
If necessary, create your own signal to signal that a placement is active without valid proof of identity with the employee.