Is re-documentation a frequent occurrence or should it be eliminated?

Question

1C

Is there any standard in the work environment that documents should not be reposted, because this can lead to negative consequences or it doesn’t matter at all, you can repost at least how many times?
It’s just that I’m thinking now, if I have several documents posted, and on the basis of the posted documents, something is calculated for me, and so I decided to re-post some of the past documents, and everything will break down for me, and even if I I will fix this, if you have to make changes, add details or new fields, then when you re-do everything will break again, and so on ad infinitum.

Answer 1

This is what sequences are for. In general, reconducting (most likely it means changing the data retroactively) may or may not be. Moreover, in 1s there is a separate right to this - and it can be taken away from everyone. And to design the system so that instead of retroactive changes, adjustments and so on are introduced, but usually because of this, the system becomes much more complicated.

Answer 2

It all depends on the Business, i.e. what the program is for, what actions it solves. For this, a set of actions / prohibitions / regulations is drawn.
For an example / study, take a typical Accounting Department (RF). There is everything incl. RS - where the earliest document is written, restoration of the sequence, complete/partial reposting.

add details or new fields, then when re-drawing everything will break again and so on ad infinitum

.
this is already an extreme ... which should not be present in the working version.