Knowledge base MessagesEntitiesAttributesCode listsErrors and fixesProcessesRolesReleasesGlossaryEcosystemCompare Validator NL EN

Process / protocol

Duplicate messageId after acceptance (HTTP 400 with feedback)

Symptom

The receiver answers HTTP 400 with a feedback message (statusType 0) to a message that looks correct in content.

Cause

A previously accepted message with the same messageId was sent again, for example the final NAV of message 13 with the messageId of the preliminary one. Release 2027 prescribes that a reused messageId after acceptance is rejected and requires human coordination.

Fix

Give every message a new messageId. If it is a correction of an accepted message: consult the receiver first and refer to the original message with originalMessageId. Message function 54 is not meant for a correction: it stands for sending unchanged content again.

Wrong and right

Wrong

{ "commonTechnical": [ { "messageId": "00555B-202609-NAV" } ], "commonFunctional": [ { "function": "01" } ] }

Right

{ "commonTechnical": [ { "messageId": "00555B-202609-NAV-FINAL" } ], "commonFunctional": [ { "function": "54", "originalMessageId": "00555B-202609-NAV" } ] }

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

Attribution. Source: SIVI – VB-PUO Standard. Schemas, attribute descriptions and code lists are taken unchanged from the VB-PUO Standard (owned by the Pensioenfederatie, managed by SIVI) and shown with their release and version. Explanations, examples, error descriptions and translations are by WTP Data Lab and are not part of the standard. GitHub Stichting-SIVI/VBPUOdsk · Manual · sivi.org