Is it possible to change the typical configuration so that no changes are visible when compared through the support setting?

Question

1C

Hello, I am not a 1s developer, so you need to consult with experienced developers. The business owner has suspicions of embezzlement of funds at a very large enterprise. Therefore, I would like to clarify whether it is possible to make changes to the typical configuration in such a way that these changes are not displayed during the comparison? Or, speaking in another language, is it possible to create a modified configuration in such a way that it is considered "typical"? And if there is such a possibility, how can it be determined? Maybe I'm thinking too much, but still, when I can get changes in the configuration and see with the accountant what is happening there, I would like to be sure that there are no "windows" =). So far, what comes to mind is exporting a typical configuration to code and comparing via git with the current version. I would also like to hear about possible options for cheating the system if someone has experience in these matters. Unfortunately, nothing is known about the version or the edition.

Answer 1

Therefore, I would like to clarify whether it is possible to make changes to the typical configuration in such a way that these changes are not displayed during comparison? Or, in other words, is it possible to create a modified configuration in such a way that it is considered "typical"?

In general, it is possible, of course I didn’t do this myself, but based on the experience of creating my own configurations, I dare to assume that: 1) Take the supplier’s configuration and refine it. 2) Make a delivery configuration out of it. 3) Update the working configuration from your modified delivery configuration.
In this case, when comparing your configuration with the supplier's configuration, no changes will be visible.
Download the current release (the one you are working with) from the 1C website or ITS disks, deploy and compare your configuration with it already. Then you can 100% understand whether the configuration has been finalized or not.

Answer 2

The business owner has suspicions of embezzlement of funds at a very large enterprise.

and
you're dribbling in the wrong direction.
The program is a fixation of the user's action. If something does not suit, an audit of the enterprise's activities is carried out.
Not satisfied with how the program thinks, you take a sheet and do a parallel calculation. If it does not match, either you did not take into account, or the developer has a different algorithm, or a program error. As you find out which of these is in the program, you ultimately make a decision.

Answer 3

The changed configuration will not match the typical one during the upgrade. The only option is to use configuration extensions. In this case, the main configuration does not change.