The universal message endpoint introduces an unified request structure, while performing pre-validation and generating a valid ELSTER XML-structure.
The ELSTER dataset is not consistent within context naming, field naming and element order. The universal message endpoint uses consistent naming for alike fields, and takes care about the element order.
Every request must contain:
elsterTaxNumber (or elsterFileNumber)
at least one contact in contacts[] (with provided type personA)
Other fields are message type dependant.
Mapping
Correlation between universal key name and ELSTER field.