All insights
AI Fairness and Inclusion

What the Dutch Childcare Benefits Scandal Teaches About AI Bias

By Jora Gill · · 6 min read

Between 2013 and 2021, the Dutch tax authorities used a risk algorithm to flag childcare benefit claims for fraud. It used nationality as a risk factor. Tens of thousands of families were falsely accused, many were pushed into serious debt, and ethnic minorities were hit hardest. In January 2021 the government resigned.

How it went wrong

The system treated not having Dutch nationality as a signal of risk. Families it flagged faced investigations and demands to repay benefits, often for small administrative errors. Amnesty International described it as a case of “xenophobic machines”. The Dutch data protection authority later fined the tax administration for processing nationality data in a discriminatory way.

No one set out to build a discriminatory system. It was designed to catch fraud efficiently. That is the lesson: bias rarely arrives as an intention. It arrives through data choices nobody tested.

Where bias hides

  • Direct use of protected characteristics, as in the Dutch case.
  • Proxies: postcode, school, first language or name can stand in for ethnicity, age or disability.
  • Unrepresentative data: a model trained mostly on one group performs worse for others.
  • Feedback loops: groups flagged more often are investigated more, which produces more data that appears to confirm the flag.

How to test for fairness

The most direct test is to send the AI requests that are identical except for one characteristic, such as a name, age or disability-related phrasing, and compare the outcomes. Then check whether the data behind the system represents the people it serves, and look for features acting as proxies for protected characteristics.

In the UK, the Equality Act 2010 applies whether a decision is made by a person or a system. An organisation cannot point to its algorithm as an excuse.

The lesson

The Dutch families were harmed for years before the pattern was proven. Independent testing at the start would have shown that the system treated people differently by nationality. That evidence is far cheaper to produce before launch than after a public inquiry.

Find out what your AI will get wrong, before anyone else does.

FireBreak independently tests AI for security, reliability, fairness and governance. We never assess systems we built, and we never sell fixes for what we find.