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.

AiBezwaar (Taxation)

AiBezwaar supports the processing of objections by reducing the administrative burden. Incoming e-mails are analysed automatically, identifying relevant data such as the submitter, main parties involved and reasons for objection. The algorithm then suggests a text to answer the objection.

Last change on 7th of October 2025, at 13:05 (CET) | Publication Standard 1.0
Publication category
Other algorithms
Impact assessment
Field not filled in.
Status
In use

General information

Theme

Organisation and business operations

Begin date

02-2025

Contact information

gemeente@aalten.nl

Responsible use

Goal and impact

The aim is more efficient handling of objections, reduction of administrative burden and shorter processing time.


AiBezwaarwaar:

  • Identifies the applicant and main parties involved.
  • Identifies the WOZ object of objection.
  • Identifies whether the objection is a pro-forma objection.
  • Identifies the grounds of the objection (grievances).
  • Identifies whether a hearing is requested.
  • Prepares a draft response based on previously given answers to certain grievances.


Based on this, a case is immediately created in the objections module.

When not all required data can be recognised automatically, the e-mail is flagged for manual processing by an employee. Here, the employee can quickly and efficiently complete the missing information and register the objection correctly.

Considerations

It is about more efficient handling, with the resident getting a quicker response.

Human intervention

AiBezwaar is mainly aimed at booking objections to ease the administrative burden. The official should always assess the suggested text and draft his/her own objection letter. For this purpose, he/she can use the suggested texts, modify them, generate new suggestions or draft a new text himself/herself. When a suggested text is modified or newly created, it is included in the suggestion options at the next objection analysed. A case can never be completed without an employee himself indicating whether an objection is founded or unfounded. This is not something that the algorithm automatically fills in the application. Without this judgment, an objection cannot be finalised either.

Risk management

Potential inaccuracies in automatic processing and categorisation to be mitigated by human control and continuous model improvement.

Legal basis

AWR, WOZ Act, AwB, Municipalities Act, Administrative Law Litigation Decree

Operations

Data

All information contained in an objection will be processed by the algorithm, which may include (sensitive) personal data. The software integrates with existing tax system and databases to automatically retrieve and enter relevant data.

Technical design

The system optionally uses a large language model to automatically parse and categorise the content of grievances. The large language model analyses the text, identifies the main grievances and enters them into the appropriate categories in the system. This process also includes automatic input of relevant data into the administration system, minimising manual input.

External provider

PinkRoccade

Similar algorithm descriptions

  • AiBezwaar supports the processing of objections by reducing the administrative burden. Incoming e-mails are analysed automatically, identifying relevant data such as the submitter, main parties involved and reasons for objection. The algorithm then suggests a text to answer the objection.

    Last change on 6th of June 2025, at 12:21 (CET) | Publication Standard 1.0
    Publication category
    Other algorithms
    Impact assessment
    Field not filled in.
    Status
    In use
  • This algorithm helps e-mail users determine when an e-mail contains sensitive information and should be sent securely.

    Last change on 5th of September 2024, at 11:29 (CET) | Publication Standard 1.0
    Publication category
    Other algorithms
    Impact assessment
    Field not filled in.
    Status
    In use
  • This algorithm helps e-mail users determine when an e-mail contains sensitive information and should be sent securely.

    Last change on 15th of October 2024, at 8:14 (CET) | Publication Standard 1.0
    Publication category
    Other algorithms
    Impact assessment
    Field not filled in.
    Status
    In use
  • This algorithm helps e-mail users determine when an e-mail contains sensitive information and should be sent securely.

    Last change on 21st of August 2025, at 11:26 (CET) | Publication Standard 1.0
    Publication category
    Other algorithms
    Impact assessment
    Field not filled in.
    Status
    In use
  • This algorithm helps e-mail users determine when an e-mail contains sensitive information and should be sent securely.

    Last change on 7th of August 2024, at 9:43 (CET) | Publication Standard 1.0
    Publication category
    Other algorithms
    Impact assessment
    Field not filled in.
    Status
    In use