Transition to a new program 1s. About interesting things from the IT world, instructions and reviews

When switching to a new accounting system, it is necessary to choose the optimal time for the transition, as well as solve a number of problems to ensure the continuity of accounting. It is only in theory that accounting should be operational, but in practice, the closing of a period can be extended for some time due to objective reasons - for example, documents had to be returned to suppliers for rework, etc. How best to transfer balances from the old infobase to "1C: Accounting 8", says V.N. Khomichevskaya, independent consultant, author of the book "Switching to 1C: Accounting 8! Rapid development for users of 1C: Accounting 7.7".

One common situation that influences the decision to migrate to a new accounting program is the need to time the transition.

Traditionally, the most convenient time for this is the beginning of the year as a new financial and tax period.

The main reason is that there is no need for special procedures associated with the implementation of cumulative accounting.

But, despite the fact that, according to all the canons, accounting must be operational, that is, each document must be created in a timely manner (if it is formed at your enterprise) or registered (if it is created from another source), life always makes its own adjustments. If with the first option most often there are no problems, then with the second - all the time. Either the original of the "primary" got stuck somewhere along the way or was lost, then the design is inadequate and you have to return the document for rework, then ... you never know what else! And to wait with the registration of values ​​until the arrival of the original documents or to return the document to its creator (yes, along with the arrived values), but at this moment the interests of the accounting department to comply with the "spirit and letter" of legislative requirements literally begin to threaten real business. Or invoices for services rendered to your enterprise, which absolutely must be taken into account in this period, arrive with a big delay.

That is, closing the period to receive balances that could be transferred to a new program may be extended for a more or less indefinite period.

Therefore, it is impossible to assign a certain moment "X", in which the results will be fully and reliably known, which can be immediately transferred to a new program and begin a "new life", or rather, immediately continue the "old life" in it. In addition, the transfer process itself requires some time, depending on how it is carried out.

For example (see Fig. 1), with all the desire to switch to accounting in the new program from moment A, you will need to wait in real life for a certain moment B, by which you will accurately balance the balances and carry out all the necessary routine operations (closing the accounts of costs and expenses , balance reformation, etc.). As a rule, the date of occurrence of a complete, exhaustive and verified list of balances for all accounting accounts used (both synthetic and their analytical ones) coincides with the date of the final reconciliation of the balance sheet, all forms attached to it, as well as tax reporting. And only after that you can transfer the data to the new system with confidence.

Rice. one

So, on the one hand, during the A-B period (transitional period) there is nothing left but to continue some actions in the previous program (at least - to reduce the balances for the completed period, as a maximum - to enter the entire operational primary in the previous program) . But at the same time, we will urgently need the same period in the new program (either in the form of the business transactions themselves, or in the form of consolidated entries reflecting the turnover between accounts), because without it we will not get progressive results in the new financial period. Accordingly, the question arises - where in this transitional period should all current business transactions be taken into account? Because for the sake of transferring accounting to another program, no one, of course, will stop the usual course of work. Business is business.

Let's try to detail what exactly, how and when you need to do in the process of transferring accounting to a new program. These actions depend on several reasons:

1. From what program and to what you are going to switch.
2. From how prepared the new program is to the specifics of accounting at your enterprise (or holding company).
3. Is the accounting program used in isolation, or should it exchange operational data with a specialized program (commercial and warehouse accounting, payroll, or both).
4. From the degree of training of personnel and the enterprise itself to work in a new program, etc.

Note that the most comfortable is the transition from the typical configuration "1C: Accounting 7.7", for the exchange with which "1C: Accounting 8" has a prepared list of files that provide automatic transfer of balances and turnovers of operational data between these programs. Of course, in this case, it is necessary to observe some "formalities", which will be discussed in the corresponding section. But other "non-standard", but common options will not be ignored, albeit in a short form.

We will reduce part of the question of the first paragraph of this list to only one of the options - we will only talk about switching to accounting in the 1C: Accounting 8 program (Fig. 2). In this case, various options for the original accounting program will be considered - this can be "1C: Accounting 7.7" (typical - option A or modified - option B) or some other program (option C). Each of these options will be discussed separately.

Rice. 2

The next three items in the list of influencing causes are interconnected. On the one hand, it is necessary to accurately imagine whether the functionality of the standard 1C: Accounting 8 solution fully satisfies the needs of a single enterprise or company (holding) that it is supposed to keep records of, in other words, whether the standard configuration "Enterprise Accounting" or its to be adapted. On the other hand, it is important which (or which) programs are the parties to the exchange of operational data with your accounting department, and if these programs also belong to the 1C:Enterprise family, then whether they are standard solutions or modified to suit the specifics of the activity, and if so, how much. Each of these cases must be considered individually, and only the most general recommendations can be given within the framework of the article. The factor of training accounting personnel to work with the new program and the factor of organizational preparation of the enterprise for using the new tool have already been considered in detail by us (read).

Switching to "1C: Accounting 8" from other programs

If you start working in 1C:Accounting 8 after you have kept records on some other program (Fig. 2 variant C) that is not related to the 1C:Enterprise program system, then to explain the transition methodology, let's return to Figure 1 and interpret the periods shown in it in a different way.

Rice. 2

Starting from the point indicated by pointer A, you can, as noted above, act in two ways.

The first is that you continue to enter and reflect the primary documents of business transactions in the old program, so as not to unbalance the work of your enterprise. And do this until the moment when the verified results are received, that is, until the moment indicated by pointer B. Thus, at moment B, you are ready to transfer accounting to a new program. In order to do this, it is necessary to transfer the necessary balances to "1C: Accounting 8", while (or before) filling in analytical reference books with the necessary elements.

Such data entry can be manual, while there is a good opportunity for visual expert control over which analytical objects from those that have accumulated in it over the years of work are expedient to transfer, and which ones will not be useful at all in the new information base. This is the positive side of the "medal", but there is also a negative one - labor intensity. Firstly, it is the laboriousness of manually transferring balances at the end of the period and turnovers for the period from point A to point B. It is technically possible to transfer data to "1C: Accounting 8" from any database, the only question is the ratio of resources that will be required for writing migration rules if your old program supports the ability to upload data in XML format, or handle data migration if it does not. Depending on how much data is to be transferred, you will have to evaluate what is more expedient - to spend time on an independent "manual" data entry or to order the writing of a transfer processing. It is worth noting that if the latter is assumed, then it must be done in advance - so that the processing is written and debugged before the moment B arrives.

In addition, you must keep in mind that in the previous program you led the entire primary program during the transition period (in the period from point A to point B). Therefore, the issue of manual entry of documents reflecting your business transactions may well complement the complex of work on the transition to a new program. Note that the automatic download of such data (in one or another volume and detail) can also be included in the data transfer processing, which obviously will not reduce the time for writing and debugging it - plan it too!

Of course, when choosing a manual data entry option, you should take care in advance of training the accountants who will take part in this process to work with the new program. This will help to avoid possible operator errors (taking into account getting used to the new interface), and the chief accountant should organize this work organizationally. Obviously, when manually entering data into a new program, there is no particular need to wait for moment 2 to start entering the initial balances - they can be entered into "1C: Accounting 8" as they are reconciled and approved (as a result of inventory or otherwise). That is, as soon as verified balances appear, for example, according to materials, they can be safely entered into a new database. And the reconciliation of the balance sheet results of the old and new programs can be postponed until the moment when all balances are entered into the new program.

An important point is that after all the balances and documents for the transition period are entered, the documents should be posted. To do this, you need to use the processing located in the menu Service -> Group reposting of documents. This is necessary in order to observe the sequence, the chronology of data entry. This is all the more relevant in the (most common) case when documents for the transition period are entered according to accounting areas (bank, cash desk, receipts, etc.), and not according to their actual chronology of receipt (registration) and creation.

Second the way is that in the old program, starting from moment A, you no longer enter incoming primary documents and do not register incoming documents - all this is done in the new program, in "1C: Accounting 8" (it is highly desirable that at the same time there were maximum all the main directories have been filled in and the main analytical objects have been introduced (Nomenclature, Counterparties, etc.).

In the previous program, you leave only the work of additional registration of those business transactions that for some reason were not entered into the database in a timely manner (for example, according to long-term documents from service providers), reconciliation of inventory balances of goods and materials and mutual settlements. In other words - you "close the balance" in the old program. As these works are carried out, you have verified balances that can be transferred either manually (gradually or immediately), or automatically, using special processing (everything related to this - see above, in the description of the first option).

The advantage of this method is that you no longer have to duplicate the input of primary operations, no matter how you have to do it. And the disadvantage (temporary, for the transition period) is that, due to the lack of initial balances, during the transition period, you will have to "give up" the usual desire to receive operational information - because you will have movements (turns), but the final balances due to the absence of initial balances will be distorted . True, only until the moment when all the balances are entered into the new database. After that, just as in the method described above, it is necessary to process the group reposting of documents.

In both cases of the described ways of "living" the transition period after the final entry and reconciliation of incoming balances and group posting of documents, we can assume that your transition to the new system was successful.

Transition from "1C: Accounting 7.7" - one-company accounting

Let us now consider the option when the data is transferred from the predecessor program. If accounting was carried out in a typical configuration, then this case is the simplest of all possible, since a special processing for uploading data from "1C: Accounting 7.7" and a specially configured file of exchange rules have been created for it. They just need to be used. How exactly - this is described in detail in the data transfer files accompanying the package (which is located in the Convert folder, located, in turn, in the folder with the template for updating or installing "Enterprise Accounting" configurations from 1.5.12.1 and higher) two text files:

• Acc77_80.txt - for information bases, taking into account the traditional taxation system;
• USN_Acc8.txt - for infobases with a simplified taxation system.

Technically, the actions to carry out the data transfer cost the accountant only a couple of dozen mouse clicks, and enter the name of the data upload file. But those who want to perform a truly correct data transfer should read the file corresponding to their configuration very carefully. It, among other things, stipulates certain actions that, even in this, the simplest case, are required in order for the transfer to become successful. I would like to highlight them here, based on the questions asked by visitors to the transition booth at Accounting Day on December 14, 2006.

The data transfer procedure has two stages. The first is uploading data from "1C: Accounting 7.7", the second is uploading to "1C: Accounting 8".

THE FIRST STAGE - uploading data, should be carried out no earlier than all the necessary accounting actions that are related to regulatory ones. This is the closure of all accounts that are subject to closure at the end of the month, the reconciliation of mutual settlements (until the balances match the attribute of the account (active, passive) on which they are recorded). If this is the last month of the year, the balance sheet should be reformed. By what means you will do it - your choice. You can work with standard reports, or you can go the shortest way - refer to the wonderful processing located in "1C: Accounting 7.7" in the menu Reports -> Technological analysis of accounting. With its help, firstly, you will not miss a single error, and secondly, you will be able to quickly and compactly see the results of your corrections.

A separate issue, which now and then arose at the stand - the transfer of the directories themselves. It's no secret that in the long-running information bases, over time, a significant amount of "ballast" accumulates - elements of directories (most often - Counterparties), either once erroneously entered (and not deleted in time), or those with whom the relationship ended long ago , or the balances of mutual settlements are not verified (literally "for a penny").

The question is asked - is it necessary to transfer such objects to a new database?

Of course, something, and the removal of marked objects before uploading data for a new program should be done in "1C: Accounting 7.7" before uploading and thereby get rid of records that may not be needed at all in the new database. If among them there are not to be deleted - check, maybe these are echoes of "doubles" once created by mistake. In this case, it makes sense to return links to the correct place.

Using the Search for Object References mode (Operations menu), you can find objects that contain invalid references and reassign them.

If among the elements of directories there are those that have not been used for a long time, you can select them in a separate folder before uploading - in this way, it will be easier to find them in the new infobase and decide on their value and finally delete unnecessary ones.

Thus, it is possible to "revise" the data of the old infobase, and then the data downloaded from "1C: Accounting 7.7" will not contain "information garbage", or its amount will be reduced to a minimum.

SECOND STAGE - loading data into "1C: Accounting 8". Of course, for these purposes you will take a new, "empty" base. It is possible to discuss the question of whether it is necessary to carry out the initial filling of the base, which is offered at the first start? Like many other options, this one is left to your personal choice to best suit your particular situation. The initial download largely saves the time of the accountant working with the database, and this, you see, is an important factor. In addition, one of its advantages is that the initial structure of such directories as Nomenclature and Counterparties is created. When loading data, they are used to place various thematic folders of the old database, with which you can agree or disagree. In the latter case, it will not be difficult to reorganize directories at your own discretion, for the sake of your own convenience and expediency, and reorganization in "1C: Accounting 8" has become much easier - up to the possibility of using drag and drop of folders or elements with the mouse.

If you think over and take into account all of the above points, the transfer of data to a new platform will be easy and successful. Which, of course, does not exclude the stage of checking the transferred data, which, in particular, has already been described (read ). It should be noted that by implementing the option of transferring not only balances, but also account turnovers, you ensure the continuity of the data of the new database on an accrual basis, so before the transfer you can continue to work with primary documents in the usual form in the old database.

Things are somewhat different if you are switching from the adapted configuration "1C: Accounting 7.7" (Fig. 2 option B). Since it is impossible within the framework of the article to assess the amount of changes in each specific case, it remains only to note that with minor changes in the typical configuration, it is possible to make adjustments to the data exchange file (Acc77_80.xml or USN_Acc8.xml for traditional or simplified forms of taxation, respectively), or go along the path that was described above for the option of switching from another accounting program (Fig. 2, option C).

Transition from "1C: Accounting 7.7" - multi-company accounting

However, there is another option for transferring data, which is based on one of the most significant features of "1C: Accounting 8" - the possibility of maintaining multi-company accounting. At the same time, data from several old infobases should be collected in one new database, while the possibility is not ruled out that they were previously maintained in various accounting systems, including "1C: Accounting 7.7", and using the configuration for simplified taxation system.

What can be said about this case? With regard to the technical side of data transfer of each individual database, you can use all the descriptions and recommendations that are given above in this article. The very combination of information from several databases in one has its own characteristics. Which? They can be both fundamental, based on the difference in the composition of economic activity, and subjective, because in the general case different people organized the accounting data space. This could affect both the structuring of multi-level directories and the style of forming the names of their elements.

Why should this be given attention? Yes, because when loading data unloaded from various databases, in one way or another, but there will be a merging of information from directories of the same name from various databases. How exactly this can happen, and how you can influence it - we will look at several important reference books. For this, we take as an example the situation depicted in Fig. 3, where data from two databases - IB No. 1 and IB No. 2, also based on a typical configuration, but already "1C: Accounting 7.7" should be transferred to the information base of IB No. 3 based on the standard program "1C: Accounting 8". Of course, we are talking about two databases of different organizations and using the standard data transfer procedure mentioned above, while using the option of selecting all the rules for uploading data in the V77exp.ert processing form.

Rice. 3

Directory "Organizations"

When loading data, information from the constants of IB No. 1 and IB No. 2, related to data about the enterprise and some of its information, such as TIN, statistics codes, etc., must be transferred to it in IB No. 3 when loading data. enter it manually, since the selection of data in this information register is made from the directory Individuals. As for the accounting policy of organizations, both in accounting and in tax accounting, the entries in the relevant registers are formed upon loading, but are subject to significant editing. This is due to the fact that the possibilities of setting accounting policy parameters in "1C: Accounting 8" are much richer than in "1C: Accounting 7.7", for example, using the possibility of batch accounting allows you to use the methods of writing off inventory items - FIFO and LIFO *, and not only on average, as it was possible in the typical "1C: Accounting 7.7".

Directory "Individuals"

When transferring data, information is loaded into it in IB No. 3 from directories Employees of IB No. 1 and IB No. 2. If we assume that part of the employees of two organizations are the same individuals, then when loading different employees will supplement the list of individuals, and the same ones (according to the entered TIN) will be replaced when loading the data of the second base.

Directory "Contractors"

When transferring data, information is loaded into it in IB No. 3 from the directories of the same name in IB No. 1 and IB No. 2. Here, the state of the structure of the directory before starting data loading is quite important. If during the initial launch of IB No. 3, initial filling was performed, then in this case, when loading the first of the two infobases, the existing structure of groups of Counterparties is used. If the initial filling was not performed, then a new group structure is formed during loading. When loading the second base, the created structure is used, and the counterparties of the second base are added to those previously loaded. Most likely, after automatic loading of all counterparties from all old infobases, visual control and, possibly, reorganization of the directory for its more convenient use should be carried out.

Of particular interest is the loading of data on Contracts of counterparties, based on the analysis of turnovers and balances of settlements with specific counterparties under this contract and various accounting accounts. More precisely - automatic qualification of the type of contract (such a requisite was not in the directory Contracts of counterparties "1C: Accounting 7.7"). It is important in this case how correctly and close to the standards the accounts of settlements with counterparties were used in the databases of IB No. 1 and IB No. 2. The presence of settlements on sub-accounts of account 60 will most likely determine the contract as an agreement "with a supplier", on sub-accounts of account 62 - as "with a buyer", on accounts 76 - as "other". If movements on different accounts are detected under the same contract, then the priority qualification of the contract type remains with the latest movements.

Directory "Nomenclature"

Downloading this directory "1C: Accounting 8" is very specific in relation to the unloaded directories "1C: Accounting 7.7". This is due to the fact that the Nomenclature of IS No. 3 will include elements of the directories Nomenclature of bases No. 1 and No. 2, and their elements from the directories Materials, Non-current assets, Equipment.

In this case, it is important how the initial (before loading) group structure of this directory (tree) in IB No. 3 looks like. If the group tree was formed during the initial launch of the new configuration database, then it will be used, if not, the groups will be formed. Moreover, it is especially interesting that in the reference book Nomenclature, the Nomenclature group of the same name is formed, and in it, in turn, second-level groups corresponding to the Type of nomenclature (goods, services, products, semi-finished products, works), in which, respectively, nomenclature elements of the base are placed IB No. 1 of a certain type. The elements of the former directory Materials are placed separately, grouped into groups similar to the groups of the source directory. Other goods and materials from IB No. 1 are also located in the corresponding groups of the same name.

Here, as well as in other cases, it may be necessary to reorganize the directory in the interests of sharing access by users of different holding organizations to the same list. Moreover, it must be borne in mind that often in a holding of goods and materials of the same type, owned by one organization, upon transfer (sale, transfer for processing, etc.) to accounting for another, they can change their appearance and purpose. This can seriously redefine the group structure of the Nomenclature reference book, especially since it is recommended to “link” the set of accounting accounts entered “by default” into operational accounting documents to the groups.

Directory "Nomenclature groups"

Represents one of the simplest objects in terms of data loading. Firstly, in "1C: Accounting 8" it is single-level. Secondly, data is transferred to it from the reference books Types of products, works, services of the IB No. 1 and IB No. 2 databases with already entered lists of the Nomenclature objects belonging to this nomenclature group. However, visual control will not interfere with this guide after the download is complete.

Directory "Cost Items"

Its peculiarity is that in IB No. 3 ("1C: Accounting 8") it contains all types of cost items, distribution costs and commercial expenses, which in IB No. 1 and IB No. 2 were located in several directories. Of course, in the latter case, there were many overlapping cost items and costs that had to be entered in each of the directories. When loaded, they will honestly merge into one directory, and it remains to decide what to do with these seemingly "doubles" next.

The decision lies entirely in the sphere of interests and responsibility of the management personnel and accounting departments of all enterprises (organizations) in the totality, accounting for which is supposed to be in this database (IB No. 3 in our example). There can be many options, and the extreme ones are: to keep all the transferred directory positions, giving them a structure resembling the previous one, or to delete most of them, leaving one belonging to a specific type of tax expense, according to the principle of uniqueness. In the first case, the structuring of the directory groups can be started at the first level from groups - analogues of cost accounts, further detailed to the types of costs or groups corresponding to the enterprises of the holding, or you can start structuring by types of expenses. In any case, it should be borne in mind that no matter what sets of cost items you arrange in this directory, the result of their use will be divided into their accounting accounts, that is, you simply will not see "excess" in the balance sheet for a specific cost account. But there is always a question of manual ergonomics, its user convenience as a factor in reducing the risk of operator errors. And technically, the reorganization of the directory, as already noted, has become extremely simple.

This article discusses only the most general aspects of the transition to accounting in "1C: Accounting 8". And each specific case requires detailed consideration for the optimal transition.

Have you set a goal to switch to a new program? And save the accumulated data?

In this article I will tell you how to organize the process of switching to a new program so that you do not have to quit.

The most common misconceptions

1. Data transfer, configuration, reconciliation was performed by a programmer or system administrator. Other employees (heads of departments, accountants, personnel officers, etc.) did not participate in the transfer process (“once”, “a lot of work”, “you already know how we work”).
2. Immediately after the transfer, they began to keep records in the new program.

Claims in both cases, as a rule, are of the same type - “the program is raw”, “data is not being pulled up”, “everything has to be done by hand”, “what kind of programmer are you”.

Data transfer is always a project! And therefore, you need to approach it in the same way as any other project - plan the stages, control their implementation and results.

Preliminary actions

Most best project transition to a new program - when its results are known even before the data transfer itself.

Explore capabilities new program. You should know in advance what to expect from her. Use the documentation, materials from the website of information technology support, thematic forums.

Describe reflection techniques business transactions in the current program. Do you use standard mechanisms or are they based on modifications? Is it possible to implement these techniques in a new program without making changes? If you change, then what - the methodology or plan for improvements?

Check if the new program supports your hardware, operating systems, and other software. Make an update list.

If compiled update list(OS, software, hardware) - select suppliers, agree on specifications, plan and approve the budget.

Select transition tool. If you use a third-party solution - study its documentation, consult on the possibility of making the necessary improvements, corrections, terms and schedule of the technical support service.

Prepare for the inevitable

Refresh hardware, operating systems, other software.

Train users(and learn yourself) how to work in the new program. Particular attention - methods of reflection of your business transactions. Just starting to work with a new infobase, your users should already be able to take them into account.

Prepare brief instructions on the reflection of business transactions in the new program for those accounting methods that are planned to be used. If old methods are not supported, develop new ones.

Select time to transfer. The most convenient time is the beginning of a new financial and tax period. Especially - for programs designed for payroll. Especially - in order to correctly draw up the 6-NDFL form (for programs designed for payroll and personnel records). When choosing a time, be sure to consider whether your current program is supported by the manufacturer. It is highly recommended that you plan your transition before the end of support.

For consultations, system settings, be sure to involve key personnel- heads of departments, accountants, personnel officers, etc. They are your assistants. It is their interest in the results of the project that determines how the program will be perceived by other users.

First, make a list of those who will:

1. Transfer data(develop transition tools, if third-party tools are used - contact the solution developer, provide support).
2. Fulfill system setup(separate sections, sections).
3. Prepare the necessary data(if they are not stored in the current system).
4. Be responsible for hardware, software.

Be sure to agree with the head of the project team and the list of works, develop plan - schedule their participation in the project.

Remember there is only one programmer, system administrator(directly performing the transition) cannot and should not be responsible for the success of the project as a whole. Transferring data (especially big data) is always a team effort.

Make up Plan b". There should always be an opportunity to return to the old program or work in a new one, but in a different mode, if something does not go according to the planned scenario.

Data transfers and everything connected with them

Prepare the original program- update, delete marked objects, find and fix errors, recalculate totals.

Test migrations

Perform test data transfers. Your goal is to achieve comparability transferred data. Be sure to take into account the difference in program architecture. Not all data can be compared head-on. Make a list of reports to review.

Give users opportunity to work in the test base. They will get used to the new program, check the transferred data, enter new documents and check their work, and receive the necessary reports. I'm satisfied with the result of the transfer - agree on the settings, fix the agreements on paper.

Make up scenario of your actions when transferring data, so as not to forget anything and save time.

After you have achieved comparability of results as a result of test data transfers, proceed to the final transfer.

Final transfer

In advance notify users about the date and time of the data transfer, if possible - forbid the entrance to the previous program for this time.

Highlight necessary resources. Suddenly running out of hard drive space or a power outage significantly reduces the chances of meeting pre-agreed deadlines.

Transfer data and perform the final steps - create and configure users, assign groups and access templates, connect the program to Internet support, download basic classifiers, configure the program according to pre-agreed agreements.

Prohibit the entry of current period data into the old program.

First time after transfer

Be prepared for surprises. No matter how thoughtful and well-organized the project for switching to a new program is, there are almost always little things that they forgot to take into account, did not pay attention to in time, etc.

Continue to develop plan "B" - plan for the parallel operation of 2 systems or the opportunity to return to the previous one.

In conclusion…

Due to the fact that the 1C company in 2018 stops supporting the configuration “1C: Payroll and Human Resources Management” version 2.5, it is highly desirable to plan and organize the transition to ZUP 3.0 (3.1) without delay.

"1C: Payroll and HR Management" 3.1 is a completely new program with a new architecture for storing and processing data *, which does not allow you to switch to a new configuration release in the usual way - by installing an update. You will need to transfer data from 1C ZUP 2.5 to a new system, that is, download and upload data.

*In addition to the differences in terms of the architecture, ZUP 3.0 features a new design, support for the Web client, improved usability, in particular due to the ability to use the modern Taxi interface.

You can switch to the version of the 1C ZUP 3.1 program from the new month, without waiting for the beginning of the year. Closed the month - switched to a new edition.

It is best to do this using a simplified transfer option, since all accruals and deductions are transferred not by documents, but by register entries.

The recommended optimal and safe way to switch: parallel payroll calculation simultaneously in 2 versions (old and new) of the 1C ZUP program during one (or several) reporting periods. Parallel payroll calculation in both databases will allow users to learn and get used to the new program, comparing it with the previous version, and will exclude a stop in work if something goes wrong in the new program.

Instructions for the transition from ZUP 2.5 to 3.1

In order to correctly transfer credentials from one program to another, you will need to prepare the ZUP 2.5 database first. It consists in closing the reporting period (month) in ZUP 2.5, making a copy of the working IS of this version, and using the configurator to test and correct (if necessary, which is most likely) the database.

• Create a clean infobase with the latest release of 1C:ZUP 3.1;
• Run it in an empty database, indicating at the first step of the start-up step-by-step assistant that you want to transfer data from edition 2.5; Perform data loading;
• Perform a full data check after migration.

In detail: the order of transition from ZUP 2.5 to 3.0 / ZUP 3.1

• Preparing for the transition to a new program

In the old version 2.5 infobase, complete all the documents on payroll, sick leave, vacations, salary payments, calculation and transfer of taxes and contributions, etc. Make a copy of the ZUP 2.5 working base and deploy it in a separate directory. Enter the program in the "Configurator" operating mode, select the "Testing and correction" command in the "Administration" menu. If the ZUP has not been updated for a long time, update to the latest release.

• Creation of a new information base ZUP 3.1

The latest fresh release of 1C ZUP 3.1 can be downloaded from the 1C update site. In addition, you may need to install a newer version of the 1C:Enterprise 8 platform, updates of which can also be downloaded from the website.

To create a clean infobase, you need to launch the 1C shortcut and click "Add", indicating the creation of a new database. Next, select the latest release of "1C: Salary and Human Resources" 3.1 from the template.

Figure 1. Creating a clean base 1C ZUP 3

• Setting up the start assistant and choosing the data transfer option

At the initial launch of ZUP 3.1, you must select the data transfer item from "1C: Payroll and HR 8", edition 2.5, and then select one of the two data transfer options:

Figure 2. Data transfer to ZUP 3.1.2.213

From the list of databases, you must select the appropriate version 2.5 database, the data from which you want to transfer:

Figure 3. Data transfer to ZUP 3.1.2.213

Figure 4. Selecting an option for transferring data to ZUP 3.1.2.213

Data transfer from 1C ZUP 2.5 to 3.1

• When choosing this option, it is not the documents of past years that are transferred, but the data of registers and directories.
• This option will allow you to use new opportunities in personnel accounting and payroll.
• According to mutual settlements, only balances will be transferred.
• Transfer of personnel history (T-2), data for calculating average earnings. *
• The fastest transfer option.

*However, data on employees under GPC agreements, as well as data on loans, will not be transferred.

• If you select this option, the documents are migrated.
• New features of the program will not be used, documents from the previous edition will be used.
• In terms of personnel data, all documents will move: dismissal, relocation, etc.
• Planned accruals will be transferred in the form of register entries, while with the simplified one, only a slice was transferred.
• According to mutual settlements, all documents are transferred.
• With a complete transfer, it is necessary to correct all accounting errors that most likely occurred in previous periods, otherwise you will have to correct them in the new database. After that, all documents and data must be verified in both databases.
• Since the amount of data being transferred is large, the process will be slow.*

*The old database will retain all the data that you can access at any time and find the necessary data.

Figure 5. Download data

• Checking data after migration

Before starting work with the new 1C ZUP 3.1 program, as already mentioned, you should check the completeness and correctness of the transferred data from the old version - 2.5. To do this, feel free to use reports to reconcile data.

You need to check:

• Organizational structure of the enterprise, directories "Organizations", "Subdivisions", "Territories";
• Personal data of employees;
• Initial staffing;
• Accruals and deductions, correctness of formulas;
• Remaining balances.

As a result of the transition to 1C: ZUP of the new version and the preliminary actions taken, after the data transfer, we will receive two separate databases: the old information base of the ZUP 2.5 program with documents and the new version of the program 3.1 with initial balances. At the same time, it is recommended to keep payroll for some time in parallel in both programs, and after you are fully familiar with the new configuration, you can switch to accounting only in it.

Our answer is of course “Yes”!
According to Japanese wisdom, "if you don't get better, you get worse." This is especially true in an increasingly competitive marketplace.

The main advantages of 1C: Enterprise 8 for the enterprise as a whole:

• Accounting across multiple organizations in one database.
• All taxation systems are available in one database .
• Monitor compliance with the requirements of PBU 18/02 much easier now.
• batch accounting .
• Reports are built quickly, due to the technology of processing large data arrays.

• Individual customization of instruments, columns and panels
• Automatic document sequencing
• Reporting Scheduler
• "Accountant Monitor" - all relevant information for you on one screen
• « Express check of accounting»- search for errors for you before the document and posting and recommendations for their elimination
• Control of filling in the details - does not allow you to make mistakes!
• Significant expansion of functionality for complex accounting cases
• Indirect costs - distribution according to your desire.
• A lot of pleasant little things for the work of an accountant

The organization of the transition includes the construction of a data transfer algorithm and the choice of tools for implementing this algorithm. There is no completely universal procedure suitable for any enterprise. We can distinguish the following factors that affect the transition algorithm: the time when you started keeping records in the new program, the presence of improvements in the current version of your configuration, the need to save the history of business transactions for past periods. Depending on the combination of these factors, the data migration strategy may be different. Transition projects are the most interesting to consider if they include balance transfer processes. Therefore, in this article we will comprehensively consider the project of transition to a new platform in relation to the 1C: Accounting configuration.

Advice from the company RG- Soft: It is best to start working in the new accounting program from January 1st of the new year. This is due to the fact that most taxes are calculated on an accrual basis. Therefore, in order not to invent means of correctly transferring the accumulated results, try to tie the start of work in the program to the beginning of the reporting period for taxes. Of course, you can start work from the beginning of the quarter and even from the beginning of the next month, but such a transition traditionally entails more significant costs.

Let's look at the most common situations.

1. The transition is carried out from the new year, from the standard configuration, and at the time of the transition, the correct balances on the accounts were formed in the old program.

This option is extremely simple and clear, but rarely applicable in practice. It is possible to form the correct balances in the old program immediately before the start of work in the new program only in a number of small companies, and then on condition that all the “primary” for the past period is provided and included in the program. Most often, the closing of old transactions of the previous period in the program is carried out by the time VAT returns are submitted (January 20), and in some cases this process can stretch for a longer period. There is a second common situation.

1. The transition is carried out from the new year, from the standard configuration, and at the time of the transition in the old program there are no correct balances on the accounts.

Depending on the circumstances, in this situation, you can also act in various ways. The essence of these methods is to work in two programs simultaneously. During the “transition period”, employees have to close old transactions in the old program and start entering documents for new transactions into the new system. This situation is clearly shown in Figure 1. The presence of such a period in the transition project is a standard practice, and there is no reason to be afraid of it. To overcome this period with the least losses, you can use the following strategies.

• Transfer balances "as is" to the beginning of the year and keep records based on these data, as in the first proposed situation. At least the program will have information about the balance of funds and the number of goods in warehouses. However, as soon as the correct balances in the "seven" are obtained, it is necessary to immediately correct them "backdating" and in the "eight".
• An alternative option is to refuse to transfer incorrect balances and enter primary documents for new transactions into the G8 without their subsequent execution. In this case, it does not matter whether there are balances in the program or not, unposted documents will not make any movements on the accounts. So you need to act until you get the correct balances in 1C: Enterprise 7.7. Further, the received balances are transferred to the new program at the beginning of the year. The final step is the consistent implementation of the “primary work” introduced into the new program during the transition period using the built-in processing “Group processing of directories and documents”.

1. The transition is carried out from the middle of the year with a typical configuration.

• Start work, if not from the beginning of the year, then at least from the beginning of the quarter.
• Carry forward balances to the beginning of the year.
• Transfer all primary documents for the current reporting period (year) to the new system and restore accounting and tax accounting data using group processing of directories and documents.

Since several thousand documents can be generated even in one quarter, we also advise you to use automated data transfer tools.
Such means can be:

1. Standard solution "1C: Data conversion". This software product can be used to transfer information between any configurations on the 1C platform. In our case, to upload documents from 1C: Accounting 7.7 to 1C: Accounting 8.
2. Atypical developments of Franchisee firms. Many companies, including ours, have proven methods for solving this problem, which can significantly reduce the time and budget for data transfer.

1. Transition from a typical configuration with additional transfer of documents of the past period.

It is possible to implement such a transfer using the same mechanisms as in the previous situation. The difference of this process is that there is no need to transfer all documents, you can limit yourself to transferring only a few types of documents, and the remaining account balances are entered through standard processing. In this case, additional transferred documents are usually left unposted.

Advice from the company RG- Soft: Although documents for the past period can be transferred from the old program to the new one, such a transfer leads to a noticeable increase in the size of the database, and hence the size of the processed tables. This, in turn, can slow down the system. Therefore, this transition option should not be used unless absolutely necessary. Documents transferred from previous periods are recommended to be left unposted so that the information contained in them does not affect the current accounting and tax reporting. Use documents from the past period only as a reference.

1. Transition from atypical configuration on the 1C:Enterprise platform 7.7.

• If the configuration is changed slightly and in the main mechanisms is similar to the typical 1C solution, you can use the standard transition tools, as in the previous options. You only need to adjust or slightly modify them for your program. Perhaps the most tested and reliable tool is the already mentioned "1C: Data Conversion". This tool will require certain skills from the user, however, it can be used to organize an automated transfer of objects between configurations. In this situation, this is background information and documents, if necessary.
• If the configuration has been radically redesigned over the years of use, then setting up typical migration tools can be more labor-intensive than writing your own processing for these purposes. A similar situation arises in the case of organizing the transition from an accounting program that is not related to 1C platforms. It is also possible to make such a transition, but it will not be possible to come up with a universal exchange in advance. In each case, an individual approach to the problem is needed.

Multi-company transition.

Due to the lack of a mechanism for multi-company accounting, many enterprises had to keep several databases in 1C:Enterprise 7.7 at the same time. Since this problem is solved in the eighth version, the task arises of connecting several databases into one as part of a data migration project. Moreover, each of the bases of the seven can have its own characteristics. Using the techniques given above, you will be able to establish interaction with each of the bases separately. However, there are a number of subtasks that are specific to this particular case.

• Unification of documents related to a particular organization. This problem is easily solved using the prefix mechanism. Each organization registered in the program is assigned its own letter prefix. This prefix is ​​added to the document number, thereby ensuring the uniqueness of the numbers.
• Control of duplicate elements of directories. When transferring data from several information sources to a single information system, a situation may arise when the same elements of directories, for example, the same counterparty, will be repeated several times in a new directory. Therefore, after data transfer, it is necessary to perform the procedure for comparing and merging duplicate elements of directories.

What problems might arise?

By planning in advance all the steps of the transition, you can avoid many problems, but this is not all that is needed to achieve success. There are also a number of specific features that are already detected at the project implementation stage. Below are a few factors that many companies face when organizing transition work.

Initial data

First of all, these are the most diverse "mistakes" of users made when entering data into the database. In the general case, an unambiguous identification of an object is possible by the details of the TIN and KPP. In the seven, both of these values ​​were stored in the same TIN/KPP variable, and there were no checks for the correctness of the data entered in this variable. It was possible to enter fewer numbers, and put the separator in the wrong place, and enter completely abstract TINs (sometimes there are such: 22222222223). A typical transfer, when forming a directory, counterparties separates the TIN and KPP by simply cutting off the required number of characters. Therefore, absolutely incorrect data can be written into the details of the new database. Of course, the correct identification of objects during transfer using such data is very difficult.
Another problem is the complete absence of a single format for entering data. Each user can enter the name as he likes. Let's imagine that in one base of seven, the user, filling in the requisite "Name" of the counterparty, wrote "MC Vympel", and in the other base of seven, the same counterparty is indicated as "Vympel Management Company". In such a situation, automatic processing will not be able to understand that this is the same counterparty and will transfer it to the eight twice. It will be difficult to work further in such a database, since part of the balance will be on one element, the second part on another.

Configuration Differences

Another group of migration errors is caused by technological differences in configurations. Some business transactions are reflected in 1C: Enterprise 7.7 by several types of documents, and in 1C: Enterprise 8 by one. For example, receipts of both materials and goods are reflected in the new program with one document, and in the old one - with two. Thus, when trying to transfer the documents "Receipt of materials No. 22" and "Receipt of goods No. 22", a uniqueness control error occurs. Since it is impossible to record two documents with the same number in a given period, it is necessary to artificially introduce differences into them, and the system for introducing these differences is agreed in advance. For example, this problem is solved by adding an additional prefix to the uploaded document number.

For each feature of the document, this prefix is ​​allocated separately. This may be a characteristic of the database from which the documents are loaded or the type of document from which the load was made. Here is an example of the formation of such a prefix. The base of the branch in Krasnoyarsk gives the prefix "KR". The type of document "Receipt of goods" from which the loading is made, gives the prefix "M". So, if the document number in the seven was 00000031, then the eight number will be as follows:
"KR" + "M" + "00000031" = "KPM00000031"

As a result, a number will be written to the database, which will be unique.

Technical problems

Data transfer errors can also occur due to the technical features of the 1C:Enterprise platform. Let's say that the standard search mechanism by name does not distinguish between large letters in the name of a directory element and small letters. There is confusion when using this mechanism.

For example, in the database there are two counterparties "m-video" and "M-Video". When searching for the “m-video” counterparty, the system will find “M-Video”. The result is an incorrectly completed document. This situation is shown in Figure 2.

It is also necessary to pay attention to the chosen method of data transfer. The example described above with doubling counterparties, when transferred from the bases of the company's branches, may not actually be doubling. Companies operating in different cities may well have counterparties also operating in different cities.

The branch of the M-Video company in Nizhny Novgorod and the M-Video company itself in Moscow can rightly be called exactly the same in the databases. To avoid such confusion, you need to choose a transfer method in advance. In our example, you can separate counterparties into different groups of the directory, depending on the source database. The choice of such a methodology will also affect the mechanisms for loading data.

Combination of data identification methods

The methods described above for solving emerging problems may also not be universal enough. When migrating data, it is very important to be able to combine the methods used in the migration tool. For example, we identify most elements of directories by name.

At the same time, when transferring the document “Acceptance of fixed assets for accounting”, this method will give undesirable results in the case when a number of small fixed assets of the same type (stationery, furniture, etc.) are entered, differing only in the inventory number. In each document of acceptance for accounting, the same object will be indicated. And the acceptance of one object for accounting several times is impossible. Therefore, it is very important to provide the ability to customize the data migration tool used. In this case, we simply indicate that the OS must be searched for by the inventory number (code).

Advice from the company RG- Soft: An independent transition between 1C:Enterprise platforms is not an easy decision, but in certain situations the most correct and economical. If you are not sure that you can overcome all possible difficulties yourself, use the services of franchisees. Our company has implemented many similar projects and has created a well-defined "method of successful migration".

Successful Migration Methodology

The main criteria for evaluating any project are time, budget and compliance with customer requirements. Let us analyze in more detail each of the parameters and ways to take into account their influence on the result.

• Time.

• Generate and post all the necessary documents for past periods (Closing the month, Sales book entries, Purchase book entries). This is necessary for the correct formation of balances on the transfer date. Performing these operations during the transition only lengthens the transition period.

• If you plan to use external processing, you need to allocate time for writing and testing them before the start of the transition period. Our company has repeatedly had to write such processing and, based on the experience gained, we have created our own solution for transferring documents. Therefore, on new transfer projects, we do not spend time and budget on writing new processing, but only customize our transfer tool to the specifics of a particular client.

• Take measures to train staff in advance on the features of the new product being introduced. This will reduce the period of users' "getting used" to the new interface, and, consequently, will allow them to switch to a new platform in a shorter time.

• Budget.

• To have and constantly improve their own means of data exchange in various formats. Thus, we take into account the experience of past transfers and do not spend extra money on re-writing similar mechanisms.

• Involve only experienced employees to work on the project. Statistics on past projects show that if any difficulties arise, then the “experienced” specialist copes with the task faster.

• Know as much information as possible about typical tools and their functionality. The use of typical transfer tools or their minor modification/configuration also helps to minimize your costs.

• Understand accounting mechanisms in different versions of the program. If the project requires the implementation of additional functionality, this will entail additional costs only for development, but not for study.

• Compliance with customer requirements.

Are you still thinking? Others are already working!

Currently, there are still quite a lot of companies working using 1C:Enterprise 7.7. This is due to factors such as a lack of understanding of the benefits of the new platform, unwillingness to learn new technologies, and fears of encountering a large number of difficulties during the transition. Using the example of 1C: Accounting, we tried to prove that most of these reasons are not so significant. Within the framework of one article, it is difficult to analyze the features of the transfer for any configuration, however, unsolvable problems cannot arise in any of the cases. Throughout our activities, we help our clients to cope with any problems associated with the implementation of programs on the 1C: Enterprise 8 platform. If you are interested in the issue of transition or you have any other questions regarding the 1C: Enterprise 8 platform and the configurations created on it - we are at your service!

Why does this happen?

In order for the software product to remain useful for you, 1C Firm constantly updates, adds new features, and takes into account your wishes.

But there comes a time when new solutions cannot be implemented in the old version. To implement all the new mechanisms and features, developers create a "new format" of the program and stop supporting the previous version.

How can I find out when a new edition is released?

And also on our website or from our e-mail newsletter.

informational
mailing list

What does "ended support" mean?

Termination of support means that the software product will not comply with new changes in legislation, additional functionality will not be developed, which means that accounting in the program will be incorrect, reporting from the program will not be possible, and many convenient features will not be used.

When should you switch?

1C company warns in advance about future changes, and program users have a year or even more. It is best to plan the transition to the new edition in advance - this will help you fully master the new program, understand all the intricacies of accounting without haste, train employees and start working in the new reporting period without panic.

How to switch?

There are different options for the transition - if desired, the user can do it on their own by downloading the necessary update (distribution kit) on the 1C website. And you can use the help of specialists. Each of the options has its own characteristics. An independent transition is not suitable for everyone, since there is a high probability that not all data will be transferred, or it will be transferred incorrectly, get a lot of errors and get completely confused. Going with the help of a specialist guarantees a high-quality data transfer, in addition, if you have questions, you can always ask for help.

How much does it cost?

The cost depends on many factors:

• typical or modified 1C configuration;
• number of information databases;
• the amount of data transferred;
• correctness of accounting by users;
• compliance with the accounting methodology.

Our managers will calculate the estimate of the cost of the transition, based on the conditions specifically for your organization.

What happens if you do not upgrade to a new version of the program?

As mentioned above, a program left without support ceases to be relevant.

You will still be able to use the program, but at the same time, the forms of regulated reporting will not be updated, the state values ​​will not change, and therefore reporting will cause great difficulties.