Long standing processes can feel safe simply because they are familiar. This article explains why “it’s always been done this way” is one of the biggest hidden risks in strata accounting, and how to question processes without creating disruption.
The danger is not that the process is old. The danger is that the process is no longer examined.
Strata environments change constantly. Systems evolve. Legislation updates. Interest rates shift. Audit expectations tighten. Staff change. What was once acceptable can slowly become incorrect, non compliant, or misleading without anyone noticing a clear breaking point.
When a process is repeated without review, three things tend to happen:
The ledger may reconcile. Reports may generate. Nothing appears broken. But correctness quietly drifts.
Long standing processes often survive because they are easy to execute, not because they are correct.
Examples we regularly see include:
These practices rarely look alarming in isolation. The risk comes from accumulation. Over time, small assumptions stack on top of each other until no one can clearly explain why something exists, only that it always has.
Many strata accounting issues trace back to system transitions.
A process may have made sense under a previous platform or regulatory environment. When systems change, those processes are often carried forward without being re-validated. The system still allows the entry, so the assumption is that it must still be acceptable.
This creates a false sense of system protection.
Systems enforce rules, but they do not enforce judgement. They cannot tell you whether a historical balance was correct to begin with, or whether a long standing journal still reflects reality.
When trust is placed in the system instead of the evidence, risk grows quietly.
This is not about capability. In fact, experienced and conscientious staff are often the most exposed to this risk.
Reasons include:
Over time, familiarity becomes a coping mechanism. The goal shifts from accuracy to continuity.
The real cost of “it’s always been done this way” is not immediate error. It is delayed discovery.
When an issue is finally identified, it is often:
At that point, fixing the issue is more complex, more visible, and more stressful than if it had been questioned earlier.
In many cases, the organization then has to explain not only the issue, but why it was not identified sooner.
Questioning a process does not mean dismantling it. It means re establishing evidence.
Practical, low risk ways to do this include:
This does not require immediate correction. It requires clarity first.
Not every long standing process is wrong. Many are sound, tested, and appropriate.
The difference is documentation and understanding.
A defensible process can be explained clearly. It has a reason, a trigger, and a known outcome. It is supported by evidence, not habit.
If a process can be explained without using the words “we always do it,” it is usually on safer ground.
Instead of asking “have we always done it this way,” a safer question is:
“Does this still accurately reflect what is happening now?”
That single shift moves the focus from habit to accuracy.
Strata accounting does not fail loudly. It drifts quietly.
The most dangerous risks are rarely the ones people argue about. They are the ones no one thinks to question.
If a process exists only because it always has, it is worth stopping and checking. Not to assign blame, but to restore confidence that what looks right is actually correct.
Sometimes the most responsible action is not to fix, but to verify.