DMQC and enclosed SSH budget

Here are analysis files one of our own Arvor floats from the upwelling area in the South Atlantic. It is very stable since the beginning but has always shown an negative offset at the lower range of our expected mapping uncertainty. In the past I have always acted on the credo ‘trust your float’ and have not corrected offsets when they were smaller than +-0.01. But since the discussion at las AST I am worried about the unclosed SSH budget. But I am also worried about overcorrecting and forcing all the float data towards climatology, knowing how imperfect the climatology is.
For this float a deployment CTD exists with calibrated data and this comparison does not show a need for a negative correction of the float data. If ever the float is too fresh. And I would not have a good explanation why the lab calibration should have been so bad, that the float measures wrongly from the start with a bias of ~-0.01. Therefor I have applied no correction, and since I trust my float I have also left the Qc at 1. But I would like to get your opinion on this. And maybe we need to communicate with the other dm operators how to deal with situations like this.