Please note: The algorithm descriptions in English have been automatically translated. Errors may have been introduced in this process. For the original descriptions, go to the Dutch version of the Algorithm Register.
Determination of income class for poverty benefits
- Publication category
- Impactful algorithms
- Impact assessment
- Field not filled in.
- Status
- In use
General information
Theme
Begin date
Contact information
Link to publication website
Responsible use
Goal and impact
Objective:
To quickly and correctly determine the income class (and income type and total earnings) of the applicant in a household (in combination with the partner in the household, if any) on a submitted application for one or more Poverty Benefit(s) for a given year, to determine whether the income class meets the income test (percentage of the WML for the relevant reference year) applicable to the relevant Poverty Benefit.
Operation:
The algorithm calculates 'under water' - via a technical link between Suwinet and the CareNed automation system of the Poverty Benefits Department, and on the basis of the data from Suwinet, on the basis of BSN - the relevant annual income from employment and/or benefit(s) of the individual selected person, who has submitted an application (with possibly a partner as co-signatory, and then also co-determines his/her income) for one or more Poverty Benefit(s) for a given year.
This annual income in the relevant reference year may not exceed an income standard set for Poverty Benefits based on the relevant WML. The result of the calculation is the relevant annual income by means of the income class in which that annual income falls in relation to the relevant WML, i.e. as a calculated percentage class in relation to that WML.
Apart from the Income Class, the income type is also shown.
The constituent income components and the mutual level of the components give a description of the income situation, for example: Income type = 'Income from work', 'Benefit', 'Compound income', and so on. This description is determined in the same way (arithmetically the largest income component) as in the manual retrieval.
The income type gives the handler further insight into the income situation of the household in question.
This information is needed to determine 'certain' and 'uncertain' minima. This data can also be used for the purpose of target group outreach. This information is needed for determining 'certain' and 'uncertain' minima. This data can also be used for the purpose of target group outreach.
Considerations
The automatic connection between ZorgNed and Suwinet uses simple search rules, calculation rules and annual standards. Income data from work and benefits are retrieved via Suwinet for a certain period, the 'reference period'. The total income is calculated and compared with a fixed amount, the 'test income'.
In Amsterdam, the legal minimum wage (WML) is determined every year. This amount is often slightly more favourable than the national standard. It is communicated in time to the data team, which enters it in the calculation tool. The test income is a percentage of the WML: 130% for adults and 150% for children. If the income is lower than the test income, the provision can be granted.
In 2025, the automatic link is only used for people whose family situation has not changed during the reference period. If the family situation changes, data will be retrieved and calculated manually. Both ways use the same rules. From 2026, the linkage will be extended to also take into account changes in family situation.
The results of the income data will be included in the application file:
The total income as a percentage of the test income, e.g. [116% - 120%].
The main part of the income, e.g. 'Wages'.
The total income in the reference period, which is used in the decision.
Calculations are stored for 3 months and then automatically deleted. This is long enough for an objection procedure, which can be started within 6 weeks of the decision. The handler decides whether someone is entitled to the provision based on the calculations and other data.
Suwinet is also used to request other data, such as:
Whether someone has a car (for an asset test).
Whether someone receives child benefit.
Whether someone has had study financing (via DUO).
Whether someone has their own business (via the Trade Register).
Whether there is a one-off high income that does not count.
There are rules for the use of Suwinet within Poverty Services. Every consultation is recorded, including the name of the handler and the BSN(s) of the persons involved.
Human intervention
Staff assessed the quality of the algorithm by comparing it with the manual calculation. Where discrepancies were found, the error was found to be in the manual calculation and not in the algorithm.
Since the outcome is purer, the impact for the citizen (namely a rejection of the application) will be lower.
There is human in the loop.
The link with Suwinet is a secure environment, based on authorised access to the relevant data. The link is aligned according to applicable municipal guidelines and realised with relevant municipal departments.
- The link is actively managed by Functional Management ZorgNed in cooperation with WPI Datateam 10 and ZorgNed.
Risk management
The algorithm is not risky. It retrieves only the data that is needed. It then adds up the data and compares it to the rules. This is done in the same way as if done by hand.
The connection is well secured according to the rules of the Amsterdam municipality. Several departments collaborated on this, such as Architecture, ISO and Privacy.
In October 2025, the algorithm will only be used for situations where households have not changed. Later, it can also be used for households that have changed. This will then be done per period, indicating exactly how the household was composed during that period.
The data comes from Suwinet, a reliable source. Suwinet retrieves these data from other official sources. Only people who have permission through ZorgNed can use Suwinet. This permission is officially regulated. Changes in permission go through a fixed process, and only management is allowed to adjust it.
All times Suwinet is used are recorded. A record is kept of who requested the data, which BSNs were viewed, and at what date and time this occurred. This information can only be viewed by Functional Management. They can display it on a screen or create a report. This is done to prevent wrong or unnecessary use of Suwinet.
The supplier of Suwinet, BKWI, also keeps track of who logs in and what data is viewed. They make a general report every month. If necessary, they can also make a specific report.
The municipality's AIB (Advisering Interne Beheersing) department checks whether Suwinet is being used properly. They can request data from ZorgNed and reports from BKWI if necessary.
The algorithm's calculations and results are also stored. This data is automatically deleted after three months. This is important because an applicant can object to a decision within six weeks. If that happens, the data can be reviewed again. If necessary, Suwinet can be accessed again.
If an error in the connection is detected, it is adjusted and retested.
risk factors:
- Personal data
- Income profile (belonging to category Amsterdam minima)
- Vulnerable group
Legal basis
Implementation of statutory duties, such as Participation Act (Pwet), Social Support Act (Wmo) and Municipalities Act (GW).
See relevant DPIA Poverty provisions and/or processing.
Links to legal bases
Elaboration on impact assessments
Using the algorithm simplifies and speeds up the work process for the handler. In addition, handling applications in this way is less error-prone. Moreover, using this algorithm is less privacy-sensitive because the handler does not see the underlying data, only the result of the calculation.
There is a privacy statement and a DPIA.
Operations
Data
- Income (from work or benefits) is retrieved from Suwinet, based on:
- BSN
- Reference period
- Based on the specified BSN(s) and the specified start and end date of the reference period, the algorithm calculates the income class and the most decisive income at the push of a button; the practitioner can have the displayed data copied into ZorgNed.
Links to data sources
Technical design
Architecture
- Processing in the system:
In the application assessment process, the employee enters in ZorgNed the start and end dates of the reference period and the form of living during that period (by default, the reference period is set to last year: 1-1-(T-1) to 31-12-(T-1), where T-1 is the previous year).
If the application has a cosignatory, his/her BSN is also already filled in; otherwise, this BSN (if there is no single or single parent living form) must be looked up and filled in manually. By then clicking on the "Retrieve income class" button, the DKD_connection with Suwinet is started.
The outcome of the calculation of the income class and the most decisive income type is determined by the algorithm and shown to the practitioner in a screen. The latter can then adopt (or not) the outcome, recording (or cancelling) this outcome in the ZorgNed database.
This then looks as follows, for example:
The data included in the response message (below) are not recorded in ZorgNed's database but only adopted in the report in ZorgNed.
- Functioning of the algorithm
- Based on the BSN of the applicant (and possibly the BSN of the partner BSN, if present in the household), via a so-called 'API' (= automatic system link), the data on income from employment and benefits for the specified reference period for this household are collected and arithmetically added up, and the (year) income is compared percentage-wise with the relevant (year) WML. The result is displayed as an income class.
So for example, for reference year 2024 falling in Income Class [116% - 120%] relative to the WML.
- It is also determined what the (arithmetically) most important income type was in that reference year.