The collapse of 1C information bases is understood as the process of processing documents and configuration registers, as well as the formation at the beginning of a certain year of current balances, collapsed, assembled register data. In this case, documents from previous years are deleted or marked for deletion, except for documents important for accounting for VAT, fixed assets and a number of others.

Why do they roll up the 1C information base?

Convolution is performed to reduce the size of the database, work faster, reduce the time for updating and archiving the 1C database.

In addition, it is used to store confidential information. After the roll-up, employees and inspection organizations will not have access to documents from previous years in the current working database.

Important: if necessary, you can always expand the 1C 8.3 database from the archive before collapsing and obtain the necessary information. You can add the “before convolution” base as an additional one to the 1C 8.3 launch shortcut and always have it “at hand”.

Convolution of the 1C 8.3 database

Treatment Information base collapse in configurations 1C 8.3 Enterprise Accounting, ed. 3, Trade Management, ed. 11 and in a number of others, available from the menu Administration – Service:

Tip 1. Use processing on a copy of the 1C infobase, analyze the results and then roll up the working database.

Tip 2. Before roll-up, generate reports on those configuration objects, information about which from past periods will be needed in future periods. First of all, we are talking about accounting for fixed assets, VAT, and recognition of past expenses. If you keep track of salaries in 1C 8.3 Accounting, edition 3, then you will also need data on mutual settlements with employees.

Attention: The balance sheet before the roll-up does not need to be generated, since in 1C 8.3, checking the SALT before and after the roll-up is included as one of the processing stages.

Tip 3. Think about the period until which you will carry out the roll-up. Sometimes accountants leave data from last year, as it is important for payroll. Or even data from two or three previous years, if the volume of transactions over these years is not too large.

How to roll up a 1C 8.3 Accounting database using an example

Let's consider an example of condensing a real 1C 8.3 database of some enterprise: configuration Accounting for an agricultural enterprise, edition 3. This is actually the configuration of Enterprise Accounting, Rev. 3, but expanded by adding specialized industry objects.

Let's assume that the enterprise information base, after the testing and correction process, including packaging the information base, has reached 4 GB. Users have been working in the database since 2011. Since the organization was inspected by the tax inspectorate, including the period of 2015, and since 2016, the organization no longer calculates salaries in 1C 8.3 Accounting, but in 1C 8.3 ZUP, ed. 3, it was decided to close the base until 2016.

Step 1: Create a backup copy

From the menu Administration – Service we start processing under the user with Administrator rights. In our example Admin. Enter the Admin user password to access the 1C 8.3 database. If you are performing a reduction on an already created copy of the program, then the checkbox Create a backup can be reset. Otherwise, we indicate Information security backup directory:

If we press the key F1 on the keyboard, we can get information about the purpose and features of using this processing. Having familiarized yourself, close the help and click Further proceed to the next processing step Completed stages are highlighted in green.

Step 2: Set up convolution

At this stage, we determine at the beginning of which year to form balances in 1C 8.3. The default is checked Set a ban date for changing data. It will be set on December 31, 2015 in the event of the formation of balances at the beginning of 2016:

It is possible to roll up the database for all organizations or just one. Following the example, there is one organization in the 1C 8.3 database, so there is no choice of organizations for reduction in processing.

Stage 3. Formation of residues

By button Further Let's move on to setting the rules for the formation of balances. For standard configurations they are predefined, and for 1C 8.3 Enterprise Accounting, Rev. 3 it is possible Restore recommended settings, if they were changed.

We can set folding rules for Posting log: Do not collapse or Collapse:

We can define rules separately for each accumulation register:

By default, for example, in processing for 1C 8.3 Enterprise Accounting, edition 3 it is Don't collapse at registers VAT Purchases, VAT Sales, VAT claimed and a number of others. That is, the developers analyzed which database parameters need to be preserved in full, and which can be collapsed.

But we can, for example, set Don't collapse at the accumulation register VAT included in the price:

Step 4: Review transactions

At the stage View transactions you can open the generated balances as of 01/01/2016, the transactions will be recorded in the database on 12/31/2015. It is possible to adjust balances or even create a new operation for entering balances using the button Create:

Below are the options for the created operations: accounting registers:

By information registers:

By accumulation registers:

Stage 5. Verification

Next, we move on to checking the created documents. At this stage, we see a report similar to the balance sheet, generated at the end of 2015 at the time before the reduction and after the reduction. The discrepancies between the data in our case are only for additional account 000, which was used to enter balances at the time of starting work with the database:

You can display and compare data for tax accounting (TA). To do this, use the button on the right, as in all standard 1C reports. Show settings and check the box next to the NU indicator:

We generate a report with data on BU and NU. Then we switch the check to Information and accumulation register:

It is possible to display information on individual registers of information and accumulations. By button More We can check or uncheck the registers for which we want to receive information:

Step 6: Deleting old documents

There is a button option Back go to the previous stages of reconciliation, including deleting the created balance documents. Or by button Further move to the next stage - Deleting old documents. At this stage we receive a warning about the irreversibility of the process in 1C 8.3. But old documents will only be marked for deletion for now. This stage is much longer than all the previous ones and can be quite lengthy:

Stage 7. Done

Upon completion of this stage, we receive a message about the successful completion of the convolution:

Stage 8. Deleting documents marked for deletion

Having opened the Operations Log, we see that documents from 2011 are marked for deletion:

Tip 4. Use in processing Removing marked objects opportunity Partial removal of objects. Delete related groups of objects. Perform the removal in stages, and take breaks between stages. Or schedule a roll-up around major holidays.

But before deleting documents marked for deletion, build the necessary reports that will tell you whether all the data remains for correct accounting of fixed assets, salaries, and VAT.

In 1C 8.3 Accounting, it will be useful to generate reports for the rollup date before and after the rollup:

• Statement of depreciation of fixed assets;
• A universal report on various accumulation registers for analyzing expenses during simplification, for controlling VAT, mutual settlements with employees, etc.;
• And other reports depending on the accounting policy of the enterprise.

Additionally, you should find 1C processing partners that will point to unused configuration objects. For example, find elements of the Nomenclature directory, links to which no longer exist, since documents from previous periods have been deleted. And, if we no longer intend to sell or buy this item, then we can delete it.

Dear reader, convolution is not the most successful solution in optimizing a 1C database; it is much faster and less labor-intensive to switch to SQL. As a result of switching to SQL, you will retain access to all documents, increase the speed of the database several times, and you will not need to minimize the database annually and worry about the correctness of data transfer.

1C v7.7 is considered obsolete at the moment, but there are companies that still use it. Since progress does not stand still, most 1C specialists have long since retrained for the 1C:v8 platform and have forgotten the “seven”, and therefore do not want to work on it. In this article I will tell you how to collapse a database (archive a period). It was not by chance that I chose to collapse the database; the fact is that for those who currently use the “seven”, the database configurations have been greatly changed and they will not be able to use standard tools. This article will be written based on a configuration based on 1C: Trade and Warehouse 9.2.

Lyrical digression: All treatments presented here belong to their authors and I in no way claim their authorship.

Let us introduce the following notation:

1. The full base is our working base, which we will be winding down.
2. Empty base - a base containing only constants and reference books.
3. A database without documents is a database that contains balances, but does not contain movement documents for the period.
4. Collapsed base - a base containing balances and movement documents for the period.

So, let's develop a small algorithm to perform database convolution:

1. Checking the information base for errors;
2. Adding a document to the configuration for working with registers;
3. Creating a copy of the information base;
4. Removing all documents and periodic details from the database;
5. Formation and transfer of balances from the “Full database” to the “Empty” one;
6. Transfer of documents carrying out movement during the roll-up period from the “Full database” to the “Base without documents”;
7. Posting documents and restoring sequences in the "Collapsed Database".

And now each step in order with pictures and explanations:

1. Checking the information base for errors - this step is carried out in the configurator. (Administration - Testing and Correction).

Now we need to set up the testing and correction process; to do this, click the “Settings” button:

We put all the checkboxes as in the pictures, click “OK” and “Run”. The testing and correction process is quite long, especially if the database is large. It will seem like everything is frozen, but in fact everything is working.

2. Adding a document to the configuration for working with registers - this document allows us to create a document containing the data of the register we need. You can download the document. Inside the archive there is an explanation of how to add a document to the database, but I will duplicate it here. Open the configurator and call the wizard for merging configurations (Configuration-Merging Configurations), a window for selecting a configuration file will open. Let's indicate the path to the place where we unpacked it and select the file 1Cv7.MD.

We only need one document, so we uncheck all the checkboxes except “Documents”, check that the switches at the bottom of the window are as in the screenshot and click “OK”. The program will add the document and open the configuration. Now you need to save the changes; to do this, click the "Save" button and accept the changes.

3. Creating a copy of the infobase - everything is simple here, we just copy the infobase directory (the one we checked and added the document to) to a new directory and specify the path to it in the 1C configuration selection window.

4. Removing all documents and periodic details from the database - to perform this procedure we will need a *.bat file. Download, copy to a folder with a copy of the infobase and run - this action will allow you to delete all documents from the database. The next step is to launch 1C in exclusive mode in 1C:Enterprise mode (You need to run a copy without documents), the database will be re-indexed. Now we need to clear the database of periodic details - to do this, we will start testing and correcting the database in the configurator (similar to point 1).

5. Formation and transfer of balances from the "Full database" to the "Empty" - to complete this step, open the "Full database" and create the document "Balances by Register" which we have integrated into the configuration. Documents must be generated on the day previous to the day of roll-up, for example, if we roll up the database on 01/01/2011, then the documents must be generated on 12/31/2010. To create a document, we need to open the general document journal, press the "Insert" button on the keyboard or "Enter a new line" in the general journal window.

Then you need to select the document “Balances According to the Register” and click “OK”. A document form should open as shown below:

Now we need to generate balances for each register of our database. To do this, select the register we need in the drop-down list and click the “Fill” button, the main thing is not to forget on what date we are creating the balances. If the base rollup is performed on 01/01/11, then the balances are formed on 12/31/10. After filling out the document, click the “Record” and “Close” button; the document cannot be posted. This operation must be performed for each register in your database (select the desired register from the drop-down list, do not forget about the date). All “Balances According to the Register” documents must be generated in one day.

After generating all the “Balances According to the Register” documents, we need to transfer them to the “Empty Base”. For transfer we need processing. Download, unpack and open the file “Universal.ert” in the “Full Database” (File->Open-Universal.ert). A window will open as shown below:

Now you need to set up processing; to do this, step by step (as in the screenshot below) fulfill all the processing requirements:

Remember that in processing you specify the path to the “Empty Base”. After you have completed all the processing requirements on the first tab, we proceed directly to transferring balances. To do this, go to the “Documents” tab, mark the only document “Balances According to the Register” and set the date on which the documents were generated.

We check the correspondence with the screenshot above, if everything matches, then click “OK” -> “Transfer documents”.

The transfer of balances to the “Empty Base” will begin; after the transfer is completed, you need to open our “Empty Base” into which the balances were transferred and post all documents to the “BalancesAccording to the Register”. To do this, open the general document journal, go to the transfer date (in our case, 12/31/10) and post all the documents “Balances According to the Register”.

7. Transfer of documents moving during the roll-up period from the “Full Database” to the “Base without Documents” - this step is performed like the previous one, using processing. We already know how to use it, so we do everything as in the screenshot from point 6:

Go to the "Documents" tab, select absolutely all documents and set the date range from the beginning of the period to the current moment, in our case from 01/01/11 to 10/13/11. We also set the switches “On marked for deletion” and “On carried out” according to the screenshot.

The next step is to go to the "Advanced Settings" tab. You need to check the boxes as in the screenshot, indicate your date range:

After setting all the checkboxes and switches, click “OK” -> “Transfer documents” (screenshot from step 6):

7. Posting documents and restoring sequences in the “Collapsed database” - upon completion of the transfer of documents, it will be necessary to repost the entire “collapsed” database from the beginning of the period to the current date (in our case, 01.01.11-13.10.11). "Operations" -> "Posting documents":

P.S.: Solving problems with the document “Balances According to the Register”:

After the publication of the article, I received a lot of requests by email asking why the document “Balances According to the Register” is not filled out and gives an error. To solve this problem and answer everyone’s question, I will leave here a guide to finalizing the document.

1. Open the configurator and select the “Register Balances” document.

2. Open the document form:

3. Click the "New" button and add the required number of Resources and Dimensions.
a) For the resource, the settings are as follows:

b) To measure the settings are like this:

For my base, I created about 10 dimensions and 9 resources.

4. Open the document form in the configurator and click the "Form" button:

5. In the form that opens, select the tabular part and click the button shown in the figure “Add details”:

6. At the bottom, select all new resources and dimensions and paste into the document:

7. After inserting, save the document.

P.S.: If something is not clear, mail is always open for you!

P.P.S.: The period roll-up process described in this article is not suitable for roll-up of accounting totals. To roll up accounting results, you should use the standard processing wrap.ert, or develop a new methodology.

The beginning of the year is the ideal time to roll up the database

Over time, the size of the database, especially in large organizations, increases. When the 1C database has been maintained for a long time and occupies a significant volume, this leads to a slowdown in work.

The convolution has the following goals:

• Speed ​​up the program
• Reduce database size
• Clear directories of irrelevant entries

What does convolution help with?

Speed ​​up the program (by reducing the size of the database)

If you do not plan to increase the number of workstations in 1C (and buy a new server for them), but you are not satisfied with the speed of 1C, you should roll up the database. This will reduce the load on computers. It will be possible to delay the purchase of new hardware for the server or the transition from the file version to SQL.

In addition, huge databases more often fail, “fall” and generally work very unreliably.

Hide historical data

Rolling up is a good way to hide information about previous years' work. The data will simply not be in the database. This is more secure than restricting access rights and passwords.

Get rid of irrelevant items and other records

During the work process, unused items accumulate in the 1C database. It interferes with the processing of receipts and sales, and when selecting goods from the list. This leads to errors and re-sorting. In addition, a large number of items slows down the unloading to an autonomous cash register, for example, to Frontol, when, along with 3 thousand used goods, another 10 thousand unused ones are unloaded. By collapsing your database, you will get rid of old products. Together with convolution, we use the Removal of irrelevant items processing.

Inconveniences of working in a collapsed database

Documents and reports for the “collapsed period” will become unavailable. You will have to have a separate database for the old period and look at the history there; it will no longer be possible to collect data for the entire period in one report.

How convolution works

The essence of the event is as follows: a date is selected (the ideal option is the beginning of the year or quarter), for example January 1, 2016. On this date, a “snapshot” of balances is taken for all accounting sections (inventory balances, mutual settlements with customers, suppliers and commission agents, cash and settlement balances accounts), and the received data is uploaded to files on the hard drive. Then, based on the previous one, a new information base is created, which contains all the necessary reference books (nomenclature, price types, units of measurement, prices, counterparties and contracts, banks and current accounts, warehouses, cash desks, materially responsible persons, etc.) and by creating the appropriate documents for entering balances into the new database, balances are entered for all accounting sections (based on data from files saved on the hard drive) as of 01/01/2016. The balances in the new and previous databases are reconciled. Their complete coincidence serves as an indicator of the success of the work performed. If there are small errors, they can be easily corrected by hand.

As a result, the speed of operation increases significantly and, most importantly, the risk of failures of the 1C:Enterprise program itself is reduced.

How to do base folding

In an ideal world, convolution is done using specialized processing from 1C, which is on the ITS disk for both 1C 7.7 and versions 8.2, 8.3. In this case, the program will create documents for entering balances and mark unnecessary documents for deletion. Directories can be deleted if they are not used in the remaining documents. Before collapsing the database, you need to restore the sequence of documents.

It is important to remember that collapsing the database by processing from the ITS disk can only be done with a standard configuration. Otherwise, errors will appear that will not be immediately visible. If you don’t have a standard configuration, you’d better contact an experienced 1C specialist to roll up the database.

Doing a reconciliation yourself is more or less possible in accounting and almost impossible in trading. And there are many reasons for this, for example, necessary information may be deleted and unnecessary information may remain. The user won’t even know about it, because... doesn't know how to check.

Convolution of the 1C database: Trade Management

Speaking about the 1c trade management package, we need to mention the problems that we often have to solve.

1. The program often uses registers that are not needed. For example, VAT (there are 7 registers there). Firstly, because of them, the rollup takes longer, and secondly, they interfere with the removal of documents.

2. If batches of goods are used. In this case, this will also prevent you from deleting a number of documents. We can set it according to the average, or in entering balances we can replace the batch document with an auxiliary document - thereby, after re-entering, we will clear the links to deleted documents.

3. Mutual settlements according to documents. We can re-close debts or also at the beginning of entering balances we can hang everything on an auxiliary document.

4. There are a whole bunch of information registers (price, written-off goods, access to documents, correspondence during exchange, etc.) that “hold” documents and directories.

5. Standard removal takes a long time. And if there are a lot of elements, then it doesn’t cope at all. We have developed our own, faster processing to remove unnecessary documents.

Package cost

The cost depends on the complexity of your configuration (retail is cheaper, complex is more expensive) and the volume of data (the cost of rolling up a database of 3 Gig and 30 Gig will vary).
To find out the cost, leave a request. We will contact you, analyze your database and determine the final cost.
The average price range is from 8,000 to 15,000 rubles.

Cons and alternatives to convolution

However, rollup is a rather radical operation that deletes data for previous years, replacing them with balance entry documents.

The main disadvantage is that you have several databases. For example, “Base 2011-2012” and “Base 2013”.

And it will not be possible to build one report that displays data for 2012 and 2013. Such useful things as analyzing sales of goods before ordering from a supplier or comparing how much more certain goods were sold in January 2013 than in January 2012 will no longer be available.

Collapsing databases really only makes sense in two cases:

1. if she is really old (at least older than 4-5 years)
2. if the data needs to be not only protected (with passwords, for example), but securely hidden (by physically deleting it from the computer)

In all other cases, it is worth paying attention to alternatives.

Alternative: Disable unused modules

Even if you do not use some of the program's features, this does not mean that it does not waste your computer's resources on them.

There are not many such potentially unnecessary but resource-intensive sections of the program:

• Record-level access control
• Accounting for balances by organizations (in addition to accounting for balances by warehouses)
• Accounting for data for purchase/sale books when you generate them in accounting

The following features are not used by some organizations, although they certainly cannot be called unnecessary:

• Cost calculation (to calculate sales profit, margin)
• Calculation of cost by batch (even though in your case the “average” calculation is sufficient)
• Settlements with clients in the context of settlement documents

As an example, I did a little research. I took the base of a company that does not use the ability to calculate profits. The initial database size is 1.6 GB. After deleting records related to cost calculations, the size of the database decreased to 1 GB. After removing all other unused tables, the size dropped to 0.8 GB.

Alternative: Remove irrelevant items and contractors from sight

Manufacturers are constantly updating their product range. Because of this, items that will never be sold again accumulate in the product directory.

The main inconvenience is that such products

• 1. get in the way of the list of managers who process receipts or sales. This increases the likelihood of errors and re-grading.
• 2. Uploading to an autonomous cash register (to Frontol, for example) is slow. Because it is not 3,000 items that are on the shelf that are unloaded, but another 10,000 that have not been sold for several years.
• 3. If barcodes are not used at the checkout and the cashier selects an item from a list, then a large list also increases the likelihood of errors and mis-sorting.

These particular problems can easily be eliminated without the help of convolution.

It is enough to add the “Archive” attribute to the nomenclature and automatically add it to those goods for which there has been no movement for the last year or two.

Additionally, such an irrelevant product can be marked for deletion, moved to the “_Cart” folder and added to the name “yay_” so that the product does not interfere with the search by the first letters.

For this case we have a treatment in stock

Alternative: Increase system security

If the data needs to be hidden, then you can use some tricks (for example, place the working database not in your office, but on a remote server. Perhaps even in another country. And prepare a local white and fluffy database for the inspectors). But collapsing the base is of course easier.

If you need to protect yourself from your employees, then a SQL server and a clear access system will come to the rescue.

Alternative: increase server power

1C 8 together with a SQL server is capable of working normally with huge databases. A database of 20-50 GB is not a problem at all, provided that the computer is powerful enough.

During the process of collapsing an information database, the following actions are performed in it:

• documents are generated for entering balances on the date when the reconciliation is carried out;
• documents and movements in registers that were in the program up to and including the roll-up date are deleted.

Collapsing the information database allows you to:

• speed up the system;
• reduce the size of 1C IBD.

ATTENTION! Before you begin collapsing the information base, you must:

• perform a preliminary test rollup on a copy of the working 1C IDB;
• If the test roll-up is completed successfully, only then can you begin to roll-up the working information database, having first backed it up.

To collapse the information database, processing for the configuration (revision 1.6), which is on disk, is used. This processing is not suitable for edition 2.0, since it does not contain the “Adjustment of register entries” document. You can order on our website.

Order a package

Step-by-step instructions for rolling up a base

• First you need to create a backup copy of the information database. Then log into the database using the mode 1C: Enterprise, and check whether all documents have been completed at the end of the month on the roll-up date.
• Next, you need to make a Turnover Balance Sheet report for the period for which you plan to roll up the base.
• Using the “Open” command (File menu), we load the external processing Database 2.0.
• The database is collapsed after clicking the corresponding button on the bottom panel, during which objects are deleted for the period specified in the processing. It should be noted that the process can take quite a long time to complete. After the roll-up of 1C IBD, it is under no circumstances possible to correct and repost documents for the roll-up period.
  It is also impossible not to say that if there were errors during the convolution process, due to which the removal of objects was interrupted or not completed completely, this may lead to the fact that the totals for some registers will be disabled. This fact, in turn, makes it impossible to obtain totals for some registers. You can view the list of registers for which totals are disabled on the “Registers with disabled totals” tab. Here, if necessary, you can include results.
  If the convolution process was interrupted for any reason, then the list of documents for entering balances can always be restored using the “Fill in the list” button on the “Documents for entering balances” tab, specifying the date interval.
• The last stage is deleting marked objects. It can be carried out if all the above-described convolution stages have been successfully completed.
  • In the “Operations” menu, select the “Delete marked objects” command.
  • The upper part of the window contains a dialog with a list of objects detected in 1C IBD and marked for deletion. The user can open and view any of them. Using flags, the user can also determine which objects need to be checked for deletion. The “Control” button will help you determine whether there are links to objects to be deleted. Having carefully checked the objects to be deleted and found no errors, you need to start the process of deleting objects by clicking the “Delete” button.

At the end of the database rollup, you need to make sure that everything went correctly. To do this, open the Turnover Balance Sheet and compare it with the one that was saved before the roll-up. If they are identical, then the base folding was performed correctly.

First, a little theory.

The 1C:Enterprise 8 program can be operated in two modes:

• file(the database is located on the user’s computer or local network),
• client-server(the database is located on a separate server).

This article is relevant only for the first option. In the case of file hosting, the program has a significant limitation - the size of one database table cannot exceed 4 GB. As soon as the size of any database table (and in the case of the 1C: Accounting 3.0 configuration, the heaviest table is the accounting register) exceeds 4 GB, the database will stop starting, and when approaching this threshold you will experience a noticeable decrease in program performance (in other words, "brakes" will appear).

So, folding allows you to reduce the size of database tables (primarily the accounting register). The base folding operation is as follows:

• the date on which the database needs to be collapsed is determined (as a rule, this is the beginning of the year),
• the program determines the balances for each accounting account on this date and enters these balances by creating documents Operation,
• all movements in all system registers before the specified date are canceled (except for those selected when setting up convolution),
• documents entered before this date are deleted (if the movements of these documents are completely cleared) or marked for deletion,
• documents entered after the specified date remain in the system in their original form.

This operation allows you to significantly reduce the size of the accounting register in the program.

How to make a convolution

In chapter Administration open convolution processing:

The following window appears:

Set the sign Create a backup, indicate the user data under which you want to make a copy, and the directory where to save the copy. Click Further.In the window that appears, select Yes:

We encounter a platform error.

When restarting, the situation repeats. Let's make a copy manually. Let's go to the configurator:

Select the path to save the copy and give it a name:

A message appears:

We return to convolution processing. We remove the sign of creating a copy. Click Further:

On the next screen you need to select the year at the beginning of which the rollup is made. It is also advisable to set the sign Set ban date so that nothing will be entered into the database before 2016. From the list of organizations, you can select only a few to collapse by, or you can collapse the database across all organizations:

On the next screen we see how the program plans to process the database tables (the system suggests collapsing some tables, leaving others unchanged). For example, many information registers and accumulation registers related to VAT will remain unchanged. This is not critical for us; the priority is to reconcile the accounting register.

In the next window the program displays a list of documents Operation, which will be created to enter initial balances as of December 31, 2015 for all accounting accounts that have balances. Let's move on.

The next screen displays a summary table with an analysis of the correctness of the initial balances at the beginning of 2016. Correctness is checked by comparison with the initial balances at the time preceding the convolution. In the above screenshot we see that there are no deviations.

Just in case, let’s also check the reconciliation table for information and accumulation registers:

On the next screen, the program warns that the procedure for deleting documents before 2016 has begun. We agree

After deleting the documents, a message appears indicating that the rollup was successful.

Draw your attention: Due to the fact that movements in the accumulation registers regarding VAT and in many information registers remained unchanged, the documents that made movements in such registers also remained in the system.

Don’t let this confuse you - our goal was to “simplify” the accounting register, and we achieved it.

If necessary, you can go through a full (and free) course on the website.