What changed
When a landlord imports compliance dates from a spreadsheet, Tenaqo records the source of those dates alongside the compliance row. Previously, a failure during that recording step could leave a compliance row stored without its source marker, making it appear indistinguishable from a record entered natively in the product.
That gap has been closed. If the source-recording step cannot complete, the compliance row is now rejected and reported as an error rather than being stored in an ambiguous state. Valid rows in the same file are unaffected.
What this did not change
Attested-import records were already kept separate from native records in Compliance Safe and Command Centre. Portfolio Health has always excluded imported compliance from its scoring. Those boundaries are unchanged.
The improvement affects how reliably the custody marker is applied when it should be, not the definitions of what the marker means.
What this means for you
Imported compliance records remain visibly distinct from records created natively in Tenaqo. Their review counts stay separate and they do not affect Portfolio Health scoring. You do not need to take any action.