The meter seems to no support a classical auto zero. One has to do a manual zero with an external short at some time after warm-up (can take quite long as there is no fan, but not sure how much the zero drifts with warm up). After that the zero point should be pretty stable. The Zero may even be stable over a limited time, like a few days or weeks. For a new bought meter it would be a good idea to do a careful zero for all the ranges.
The zero should be separate for both polarities (offset from the ADC and offset from the input amplifier) and AFAIK the meter does both togehter - there would be essentially no good way to tell it which polarity.
As the polarity reversal is with a relay one may not need a separate calibration for the positive and negative sign. The point around zero is adjusted with the zero adjust and not just calibration. It could still make sense to have both - more like a test, that usually passes.
Getting quite difference readings in the 2 V and 20 V range is a bit surprising. The zero adjustment does not look perfect (difference between the polarities), but the zero error still looks small
As you can see you have a ~.00009V constant offset that reverses itself with polarity. Just like the 3 units Branadic measured.
What does it measure with a shorted input? If this is a design issue, I don't see how it could ever meet its specifications of 5ppm + 1ppm/range (20uV).
The error that brandic saw is on the order of some 25 µV extra 'step' in the +-50 mV region. So this would still be just in the +-1 ppm of the range.
I would consider this rather high to be a design issue, though having nearly the same type of error with 3 meters is suspecious. There could still be a variation of the parts used (e.g. different batch of OP77).
The data from RAX look much worse. I did a quick plot of the low end data for the 20 V range. The attached graph shows about 10 x the step. The parts for the pos and neg sign still look linear and with the same slope. Part of the step could still be from an old zero setting or possibly an issue for the KVD (adding some offset) - though not likely.