Schema error

afdDefinitionVersion incorrect (001.04 versus 001.05)

Symptom

Schema error 'must be equal to one of the allowed values' on afdDefinitionVersion, or the receiver validates against the wrong schema and reports unknown fields.

Cause

The message was built according to Release 2026 (001.04) but states 001.05, or the reverse. Note: the July 2026 pre-release and the final Release 2027 of 12 October 2026 both carry 001.05. A message built on the pre-release therefore states the right version and can still be rejected, for example on afdDefinitionName, on netDate per cohort in message 2 or on the codes of message 15. Release 2026 v1.3.1 corrected the '(prerelease)' label in all schemas.

Fix

Fill the schema version the message was actually built with and agree per link which release is active.

{ "afdDefinitionVersion": "001.04 (prerelease)" }

{ "afdDefinitionVersion": "001.05" }

Check your own message for this and all other errors with the free validator: schema, code lists and consistency checks in one report. Validate a message