A Notice of Inspection from the CMRAO names one of your client corporations, points to the records checklist, and gives you four weeks. You read the covering paragraph twice, because one sentence in it is not about the filing cabinet. The inspector may use the systems your business uses to produce records.
Here is what that sentence rests on. Section 60 of the Condominium Management Services Act, 2015 lets an inspector require you to produce any relevant record and to provide whatever assistance is reasonably necessary, including using any data storage, processing or retrieval system to produce it, in any form, and lets the inspector use any such system the licensee uses to produce information. You have always thought of the software as a tool, the way a phone is a tool. The Act does not. The software is not where the records are kept. Under s. 60, it is one of the records.
Consider what an inspector at your screen would find, because you already know. The plumbing invoice that was entered in June with an April date, because April was still open and the invoice said April. The bank reconciliation that was completed on the 8th, reopened on the 19th to move one deposit, and completed again, with nothing between the two versions to say why. The statement that went to the board on the 5th, and the three entries the same month accepted afterward, quietly, because nothing refused them. The user who left in March and could still sign in until somebody noticed in July. Each one was defensible on the day. None of them was written down, because the system did not ask, and a system that does not ask gets exactly the record it asked for.
That is the cost you have stopped noticing. Not the corrections themselves, which every office makes, but the reconstruction they demand later: four weeks in which someone with a good memory sits with the checklist and explains, from recollection, what the software cannot explain for itself. The explanation goes in the notes column. The inspector reads it as an explanation, which is to say as something the record did not contain.
The software is not where the records are kept. It is one of the records.
What changes when the system keeps the reason as it happens is the shape of the four weeks. The closed month refuses the back-dated invoice, so booking it becomes a decision with a written reason attached to a recorded reopen, or a June entry that says what it is. The completed reconciliation stays completed unless someone with the authority to reopen it says why. A changed field carries its author, its time, and the value it replaced. Producing the record for the checklist becomes a filter, not a memory: this client, this date range, this field, print. The person who sits with the inspector reads what the system already wrote instead of writing it.
Scaalr refuses a posting, an unposting, or a deletion dated in a closed month; reopening the month takes a permission no default role holds and a written reason that is recorded; a completed bank reconciliation is locked, and matching a mismatched amount requires a variance reason; and on the Scale plan the field-level audit log keeps who changed which field, the before and after values, and when, with a PDF export. What the regime actually requires of a licensee's records, the three layers vendor pages blur together, and the gaps stated plainly are in When the CMRAO Inspector Asks, Scaalr Has the Receipt.
For the full crosswalk, from the three layers of records to the vendor checklist, see: When the CMRAO Inspector Asks, Scaalr Has the Receipt.
A 20-minute walkthrough on your own workflows shows where each of those records lives, gaps included.