Rules for transferring documents from ZUP 2.5. Transfer of personnel data and information on planned accruals

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

“1C: Salary and Personnel 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 the new system, that is, load and unload data.

*In addition to differences in the architecture, ZUP 3.0 is distinguished by a new design, support for a Web client, and improved usability, in particular due to the ability to use the modern Taxi interface, so updating ZUP 2.5 is quite justified.

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

It is optimal to make the transition to 3.0 using a simplified transfer option, since all accruals and deductions are transferred not by documents, but by register entries.

Recommended optimal and safe method of transition: 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 eliminate work stoppages if something goes wrong in the new program.

Instructions for migrating from ZUP 2.5 to 3.1

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

• Create a clean information base with the latest release of 1C:ZUP 3.1;
• Launch it in an empty database, indicating in the first step of the starting step-by-step assistant that you want to transfer data from edition 2.5; Load data;
• Perform a complete data check after the transfer.

In detail: the procedure for switching from ZUP 2.5 to 3.0 / ZUP 3.1

• Preparing for the transition to a new program

In the old information database version 2.5, complete all documents on calculating salaries, sick leave, vacations, salary payments, calculation and transfer of taxes and contributions, etc. Make a copy of the working ZUP 2.5 database 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 latest 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 information base, you need to launch the 1C shortcut and click “Add”, indicating the creation of a new database. Next, select the latest release “1C: Salary and Human Resources Management” 3.1 from the template.

Figure 1.Creation of a clean database 1C ZUP 3

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

When you initially launch ZUP 3.1, you must select the item about transferring data from “1C: Salaries and Personnel Management 8,” edition 2.5, and then select one of two options for transferring data:

Figure 2. Transferring data to ZUP 3.1.2.213

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

Figure 3. Transferring data to ZUP 3.1.2.213

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

Transferring data from 1C ZUP 2.5 to 3.1

• When choosing this option, it is not the documents of previous years themselves that are transferred, but register data and directories.
• This option will allow you to use new opportunities in personnel records and payroll calculations.
• Only balances will be transferred for mutual settlements.
• 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.

• When you select this option, documents are transferred.
• 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 be moved: dismissal, relocation, etc.
• Planned accruals will be transferred in the form of register entries, whereas with the simplified method, only the 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 it will have to be corrected in the new database. After this, all documents and data must be verified in both databases.
• Since the amount of data being transferred is large, the process will be slow.*

*All data will be saved in the old database, which you can access at any time and find the necessary data.

Figure 5. Load data

Checking data after transfer

Before starting work with the new program 1C ZUP 3.1, 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.

Need to check:

• Organizational structure of the enterprise, directories “Organizations”, “Divisions”, “Territories”;
• Personal data of employees;
• Initial staffing;
• Accruals and deductions, correctness of formulas;
• Balances on mutual settlements.

As a result of the transition to the new version of 1C:ZUP and the preliminary steps taken, after transferring the data, we will receive two separate databases: the old information base of the ZUP 2.5 program with documents and the new one - version 3.1 of the program with initial balances. At the same time, it is recommended to carry out payroll calculations in parallel in both programs for some time, and after you are completely familiar with the new configuration, you can switch to accounting only in it. To use the widest possible functionality and tools, it is also recommended to switch to ZUP KORP.

Hello dear site visitors. Today we will talk about typical mechanism for transferring data from 1C ZUP edition 2.5 to 1C ZUP edition 3.1. I will tell you step by step about the so-called recommended (short) data transfer and show how it is performed. Let us consider in detail the documents into which data is transferred: such as “Initial staffing”, “Periods paid before the start of operation”, “Initial salary arrears”, “Data transfers”. Let's see where these documents are located and the structure of the transferred data. I will also focus on some features of this transfer that should be taken into account when processing the transferred information.

Let me immediately note that in this article I will consider the process transfer of data to the beginning of the year. The composition of the transferred data when transferring to the middle of the year is slightly different and I talk about this in detail in another publication (available). But even if you plan to transfer to the middle of the year, I recommend studying first the current article, and then the publication about transferring data to the middle of the year, since there I only supplement the information presented here.

Read also:

A series of articles with detailed step-by-step description of 1C ZUP 3:

Initial program setup when transferring data from ZUP 2.5 to ZUP 3.1

✅

✅

✅

Below you can watch the video and read the article where I discuss this topic in detail, but let me remind you that if you want to always stay up to date with 1C ZUP updates, as well as learn various tricks of working with this program, then I highly recommend joining the TRADE CLUB 1C ZUP 3 . Here you can attend the monthly review of all changes in 1C ZUP 3, receive answers to your questions about record keeping during the month, and also receive productive communication with lecturers and colleagues.

So, first, let’s look step by step at how data is transferred from one program to another. When we launch a new empty ZUP database version 3.1, we are prompted on the initial page of the program to configure it. Here we can select the data transfer option we need. Those. we can either load data from the previous program or start from a “Clean Slate”. For our example, set the switch Transfer data from the program “1C: Salaries and Personnel Management 8”, edition 2.5. Click the “Next” button.

In the next step, a list of all databases installed on the computer will be offered and in it you need to select the information base from which we want to transfer data. I call this database ZUP 2.5 (transfer 2). It’s worth noting right away that the 2.5 edition base must have a specific release. In this case, data transfer is possible from the release not lower than 2.5.114.1, as indicated in the assistant (you can read more about how to update 1C yourself in the article). I have this done.

If you have some users in ZUP version 2.5 and a password has been set for them, then you should enter this information in the appropriate fields. I did not create users separately in ZUP 2.5, so I leave the fields empty. Click the “Next” button.

The next step is to select the data transfer option. To do this, follow the “Settings” link. In the window that opens, two options for transferring data will be offered. The short recommended option that I want to consider in this article is selected by default in the program. This is an option - Use new HR accounting and payroll capabilities. Here is a description of what it is. If you want to select the full transfer option, then you need to indicate this yourself, that is, reinstall the switch (this method will be discussed in a separate article).

Next, in a special field, we will add the month from which the records will be kept in the new edition. The transfer can be made in any month of the year, but before that it is necessary to close the previous month in version 2.5, make all accruals and payments on the transfer date. In this article I will consider the option when we transfer information to the beginning of the year, i.e. I select the month of start of operation January 2017. But I’ll make a reservation once again that it is possible to transfer data in the middle of the year. Click the “Next” button.

In the next step, we can already start the data transfer process itself. Click the “Load data” button. Transferring information takes some time, its duration depends on the volume of data being transferred.

Upon completion of the transfer process, we will see the corresponding inscription - The data transfer was successful.

Checking the transferred data in the document log “Data at the beginning of operation” in ZUP 3.1

So, the first group of documents that will interest us is located in the Main menu section in the document log “”.

There are three types of documents here:

• Initial salary arrears;
• Initial staffing;
• Periods paid before the start of operation.

Let's look at each of these documents in more detail.

Transferred data from ZUP 2.5 to the document “Initial staffing” ZUP edition 3.1

✅ Seminar “Lifehacks for 1C ZUP 3.1”
Analysis of 15 life hacks for accounting in 1C ZUP 3.1:

✅ CHECKLIST for checking payroll calculations in 1C ZUP 3.1
VIDEO - monthly self-check of accounting:

✅ Payroll calculation in 1C ZUP 3.1
Step-by-step instructions for beginners:

The most important and basic thing is the document Initial staffing, since it is into it that a slice of data about the current employees of the organization is transferred. Those. information about all working employees is transferred to this document to the month of commencement of operation (in our case, January 2017). Data on dismissed employees is not included here.

The tabular part of this document provides the following information: full name of the employee, type of employment, date of hire, department in which the employee works and position held. The elements of the Divisions and Positions directories themselves are also transferred to the program; we can view them in the Settings section. Information about the employee’s current planned accruals is transferred to the “Salary” column of the document. Here I would like to draw your attention to the fact that not only supplied (predefined) accrual types are transferred, such as Payment according to salary, but also, for example, the type of accrual Bonus percentage, which I created in the ZUP 2.5 program myself and assigned to an employee as planned. In the directory “Basic accruals of an organization” in ZUP 2.5, initially there was no such type of accrual.

This kind of planned accruals are also transferred to the ZUP 3.1 program and end up in the Accruals directory.

The peculiarity of this transfer also lies in the fact that some “ one-time charges", i.e. such accruals that were not assigned as planned to employees at the time of transfer, and those that were accrued one-time, will not be transferred to ZUP 3.1. For example, in my ZUP 2.5 database, the data from which was transferred to ZUP 3.1, there is an employee A.B. Semenov. and in August 2016 he was paid a one-time bonus in the amount of 10,000 rubles. For this payment, a special type of accrual was created in ZUP 2.5 - One-time bonus.

These types of accruals from the directory Basic accruals of the organization (ZUP 2.5) are not transferred to the directory Accruals ZUP 3.1. Therefore, if you have some one-time accruals that you periodically use, then you will have to create them again manually in the ZUP 3.1 program.

Also, information about the option of paying employees an advance is transferred to the document. ZUP 2.5 uses two methods of paying an advance, these are Fixed amount And Calculated for the first half of the month. If the employee was given some fixed amount of advance payment (in the ZUP 2.5 program, this is done, let me remind you, in the Employees directory), then this same amount will be transferred to ZUP 3.1 and the “Fixed amount” payment option will be automatically selected.

If the fixed amount in 2.5 was not specified, then during the transfer the program assumes that such an employee should set the type of advance payment for the first half of the month, which is established in ZUP 3.1.

But in the ZUP 3.1 program, another method of paying an advance has appeared - Percentage of the tariff. There was no such option in 2.5. Therefore, if you decide to use this method of paying an advance to an employee or several employees, then you can directly in the document Initial staffing install this option and indicate the percentage that will be applied from the start of the program.

At the bottom of the table we may have not one row, but several, if the balance consists of several working years.

Quite often, when transferring data from clients, I come across the fact that the accounting of vacation balances in ZUP 2.5 was not kept entirely correctly. Therefore, it is quite convenient to immediately view and correct vacation balances in the document Initial staffing.

I would like to draw your attention to the fact that employee T.V. Semenova’s planned accruals are not indicated in the “Salary” column. The fact is that, according to the conditions of my example, she is on maternity leave, so the planned accruals were not transferred, but the document was transferred Holiday to care for the child, into which all the necessary data for calculating benefits was loaded. There is no need to manually enter any additional information here; the document has been completely transferred from the ZUP 2.5 program.

It is also worth noting that after such a brief recommended transfer We will not see data in ZUP 3.1 of personnel documents, such as hiring, personnel transfer, dismissals, etc. We, I repeat once again, transfer a cross-section of current employees to the document “Initial staffing,” but we will not see the personnel documents themselves in ZUP 3.1. Therefore, if you need to look at some personnel documents or print something, then it is advisable to save the ZUP 2.5 database.

Transferred data from ZUP 2.5 to the document “Periods paid before the start of operation” ZUP 3.1

The document is intended for such situations when an employee was entered and calculated for some absence in the month in which records were kept in ZUP 2.5 and the same absence continues in the month when we begin to keep records in ZUP 3.1. In my example, employee Petrov S.I., in December 2016, the main vacation was issued, which ends on January 16, 2017. The accrual and payment of vacation pay were made in December, but the employee will still be absent in January 2017. It is for such cases, a document has been developed “Periods paid before the start of operation”, into which information about the employee’s absence was loaded from the start date of the program to the end date of the vacation. In my example, this is the period from 01/01/2017 to 01/16/2017. This information will be taken into account when calculating salaries for January.

Also, with such a brief transfer, information about existing planned deductions from employees is transferred from ZUP 2.5. For example, from Semenov A.B. in ZUP 2.5 alimony was withheld according to the writ of execution. When transferred to ZUP 3.1, this data was loaded into the log Alimony and other deductions(Salary section). The document “Writ of Execution” was transferred in full with all the established parameters for deduction and, accordingly, will be taken into account when calculating wages in ZUP 3.1 from the moment of commissioning.

Information about applied deductions when calculating personal income tax has been transferred to the ZUP 3.1 program; we can see them in the document log Applications for deductions(section Taxes and fees).

Now, after we have loaded the data into the above documents into the program "Initial staffing" And " Periods paid before the start of operation", as well as deductions under the executive document and deductions for personal income tax, we can try to calculate the salaries of our employees for January.

Let’s create a document “Calculation of salaries and contributions” for January 2017 and fill it out. So, the employees’ planned accruals were loaded into the document and the salaries were calculated. From employee Petrov S.I. Days spent on main leave have been superseded; wages have been accrued only for 11 days out of 17 according to the January norm. On the “Benefits” tab we see the accrued child care allowance for Semenova T.V. On the “Deductions” tab, the calculated deduction according to the writ of execution from Semenov A.B. was displayed. On the “NDFL” tab, the tax was calculated for employee S.I. Petrov. in this calculation, a deduction of 1,400 rubles was applied.

Transferred data from ZUP 2.5 to the document “Initial salary arrears” ZUP 3.1

✅ Seminar “Lifehacks for 1C ZUP 3.1”
Analysis of 15 life hacks for accounting in 1C ZUP 3.1:

✅ CHECKLIST for checking payroll calculations in 1C ZUP 3.1
VIDEO - monthly self-check of accounting:

✅ Payroll calculation in 1C ZUP 3.1
Step-by-step instructions for beginners:

Another document into which data from ZUP 2.5 on the status of mutual settlements with employees at the beginning of the month of transfer is transferred is "Initial salary arrears." It can be accessed from the document log " Data at the beginning of operation» in the Main section, and it is also present in the Payments section. In my example, the balance of the unpaid salary for December, which will be paid in January, was transferred to this document.

There is one tricky feature here, if you have already entered the document “ Salary to be paid" for December and carried it out, then the data will not be transferred to ZUP 3.1. To transfer information about salary arrears to employees, this document must be distributed. Please take this into account when transferring data.

Formation of documents in the journal “Data Transfers” in ZUP 3.1

Next, let's talk about another document journal, into which, when transferred, information that is very important for future accounting moves. It is called "Data Transfers" and is located in the section Administration.

Each document created during the transfer in this journal will have a certain set of characters as a number. In our example, the list contains documents with the following numbers:

• ZP SZO;
• ZP NWFSS;

Let's look at each of these documents and see what information is carried in them.

In documents with number Salary SZO information about hours worked and wages of employees in a specific month is transferred to calculate average earnings when calculating vacation pay, business trips, i.e. in all documents where average earnings are calculated (except for the average for accruals from the Social Insurance Fund).

On the tab Data on accruals for calculating average earnings (total) displays the amounts accrued to employees in July 2016. Thus, based on this information, the average earnings will be calculated.

Let's test whether this is true. We will arrange a vacation for employee A.B. Semenov. from January 2 to February 5, 2017. And we see that, indeed, when calculating the average employee’s earnings, the data loaded from ZUP 2.5 into documents with the number Salary SZO for the period from July to December 2016.

Separately, I would like to draw your attention to the fact that with a short data transfer, we will not be able to generate salary reports for the previous period. The information transferred to the above documents is used only to calculate average earnings in the documents Vacation, Business Trip, Sick Leave, etc. This data is not used to generate salary reports. Those. if we try, for example, to generate a “Full set of accruals, deductions and payments” or a “Payslip” (section Salary - Salary Reports) for the period before the date of transfer of data to ZUP 3, then the reports will be empty. Keep this in mind. It will be possible to create such reports only in ZUP 2.5, so again I repeat that it is recommended to save this database.

To document TDK information about concluded employment contracts with employees is transferred, which will be used to generate a personal T-2 card. Since the Hiring document is not transferred, but it displays information about the employment contract, the developers implemented in the program the creation of just such a separate document - TDK.

In a document with a number RKD information about personnel orders is transferred, for example, in our case, information about hiring was transferred. I already said above that when transferring data, the personnel documents themselves, such as Hiring, Personnel Transfer, Dismissals, etc. do not move from one program to another, but the register of these documents is still formed in the Data Transfer document with number RKD. And it is on the basis of this data that the register of orders in the T-2 card will be filled out.

In documents with number IL information about deductions according to writs of execution is transferred . In my database ZUP 2.5 from September to December from employee A.B. Semenov. alimony was withheld according to the writ of execution; accordingly, documents were created for each month in ZUP 3.1 IL indicating the amounts withheld. This information is necessary and applies if the conditions in the writ of execution change and the checkbox is checked in it Stop holding when limit is reached indicating the amount.

Separately, it is worth noting that the magazine "Data Transfers" personal income tax and insurance premium accounting data for the current year can also be downloaded. In my example there is no such information, because the transfer was carried out to 01/01/2017. But if we transferred information, for example, to 04/01/2017, then to the journal "Data Transfers" data on employee income, as well as calculated personal income tax and insurance premiums, would move for the period from January to March 2017.

Thus, data transfer can be performed at any time, not necessarily from the beginning of the year. All necessary information for generating regulated reporting will be transferred. I discuss this transfer option in detail in the article.

That's all I have for today. Subscribe to blog updates. All the best!

Today we will talk to you about the initial filling of data in 1C ZUP 3.0, provided that before that you kept everything in Accounting 3.0. In general, this opportunity only appeared (December 2014). Previously, if you worked in Accounting 3.0 and bought an additional box with a salary program, then you would have to enter all the initial data from scratch. When performing the procedure for synchronizing accounting and payroll, you received only a couple of reference books.

In addition to how this is done (it is SOOO easy), I will tell you about a couple of “rake” that I stepped on. I think this will be the most valuable thing in the article.

Although, I will say as a programmer, the internal data structure of Accounting 3.0 and Salaries and Personnel Management 3.0 is almost the same. I even wrote to 1C technical support asking why such things as hiring, transfers, income information for accounting for personal income tax and insurance premiums, the contributions themselves and taxes were not synchronized. Mutual settlements with employees. All this data in 1C Accounting 3.0 is in the same registers as in ZUP. With the same names and fields.

But fortunately, this year we were lucky, and at the first launch of the latest release of ZUP 3.0, we were offered to transfer data from Accounting.

Well, let's see what it looks like and what our beloved 1Sovtsy from Moscow have programmed.

Everything described below was done on the release "Salaries and HR Management, Edition 3.0 (3.0.20.43)".

Based on this, changes and improvements are possible in future releases.

So we have the 1C Accounting 3.0 database, release 3.0.37.35, and an empty, never launched 1C Salary and Personnel Management 3.0 database, release 3.0.20.43.

We launch ZUP and the first thing we see is the taxi interface and the advertising block. We close advertising and the ITS access form.

On the screen we still have processing for the initial filling of the database.

We select the second (in this release it is the second) option - Transfer data from the program "1C: Accounting 3.0" and click "NEXT"

Here we need to select a database from the list and correctly specify the username and password. You must transfer the calculation data so that you have two years of completed data. Those. at the beginning of 2015 it is necessary to postpone the year 2013. This is necessary to calculate the average due to the Social Insurance Fund.

The next window shows us the process of uploading/downloading data. It all has one button, press it boldly :)

Here I stepped on the first rake!

When connecting to the database I received an error. At the very first step. Apparently I'm a lucky person. Here's the bug report:

Failed to connect to the infobase:

Error when calling the context method (Connect)

An exception occurred (V83.COMConnector.1): The version of the component "comcntr" (8.3.4.496) is different from the version of the root module "core83" (8.3.5.1248)

What to do about it? What is the reason?

The reason is that I regularly install the latest platform, but do not erase old versions. I launched 1C:ZUP under the latest version of the platform. For some reason, when connecting via OLE to another Windows database, the COM object of the previous version was returned to it. There are two solutions:

2. Right here in the loading processing there will be a “Save the Planet” button. It will appear at the bottom, next to the error messages and a link to the report. Clicking this button will re-register the com object to the required version.

The upload was successful in my case, but the upload failed many times with errors. The reason was the same.

Here I stepped on the SECOND rake!

At the beginning of 2014, the database was trimmed in 1C: Accounting. Trimming, in addition to the postings, also trimmed the information registers. In particular, the rights to deductions, planned accruals for employees...

All of them were inserted during the process of convolution in the form of a slice of the last ones at the end of the previous year into an operation entered manually. Moreover, each register was registered as a separate operation.

This is rather a jamb of the “creators”. When loading this data, the program complained that the recorder could not be empty, i.e. in the conversion rules there was no rule for the data type "document. Accounting operation". This is disgusting. There is no accounting operation in ZUP, but there is a document “Data Transfer”, which can also move any registers and was created for things like this.

In general, I struggled as follows:

1. The contents of the transactions have been erased. It was he who went inside the operation and erased all movements.

2. Reviewed all personnel documents. Some of the movements of personnel orders were erased during the process of collapsing, but the orders themselves remained in the database. This allowed me to return some of the movements. In particular, planned accruals.

That's it, I've forgotten about some of the registers. Because for example, the right to deduct personal income tax is introduced every year.

This concludes my story. The second rake was serious, because... Nobody gives any normal errors. To catch enemies I used the following method.

I am more than pleased with the result of the download. The ZUP had everything that could be transferred. I just had to tinker with setting up the types of calculations by hand. I had to create indicators and re-enter them in personnel documents, but this is logical, because in 1C Bukh 3.0 there are no indicators at all. The data on the average was transferred, which could not but please.

That's all, thanks for your attention.

ATTENTION!!! more recent materials on initial data migration

Hello, dear blog readers. I think many people are aware that a new edition of the “Salary and Personnel Management” program has recently appeared in the 1C software product line - 1C ZiUP edition 3.0. The final version of this edition was published in September 2013. If the transition to 1C BUKH 3.0 is gradually gaining momentum, the transition to the new salary edition is not yet progressing so actively. As in previous years, when the “seven” was replaced by a new generation of eighth versions, the main issue remains the process of transition to a new edition of the program. Therefore, today I will try to consider this topic in detail; I will present tips on preparing for the transition to the new edition and some features of the work.

✅

✅

Firstly, I want to immediately note that the very fact of the transfer Doesn't oblige you to anything. Your work base will not go anywhere, if you don’t like something, you can continue to keep records in edition 2.5 or keep records in parallel in two programs until you master the new version. By the way, this is how the transition to new programs is usually organized in large organizations.

In this case, you must present the registration card that I wrote about, and, if you have the PROF version of the program, a valid ITS subscription. This subscription is not required for Basic version owners. Just check that you are provided with the latest version of the distribution. If they refuse to provide you with a free distribution, feel free to contact support. webits-info@1c.ru and they will contact their intractable partner and help resolve the issue. After that ZUP 3.0.

There is an option don't apply at all to 1C partners. On the resource users.v8.1c.ru, where 1C developers publish updates to their programs, a complete distribution of ZUP 3.0 has been posted. This is the very first version of the program dated September 13, 2013. Read more about how to register and download files on this resource. Those. You can download this full release, . After that, until the current release, .

I’ll also note one more detail. It is better to carry out the transfer after in version 2.5 the month was closed: salaries are accrued and paid, contributions are calculated.

How to test and fix

✅

✅ CHECKLIST for checking payroll calculations in 1C ZUP 3.1
VIDEO - monthly self-check of accounting:

✅ Payroll calculation in 1C ZUP 3.1
Step-by-step instructions for beginners:

Immediately before starting the transfer, we should do a little work with the information base from which we are transferring data. Firstly follows this base. It would also be a good idea to do the so-called "testing and fixing" structure of the information base. To do this, you need to exit the “Enterprise” mode and enter the database in the “Configurator” mode. Run testing through the main menu: Administration -> Testing and Correction. As a result, a window with settings will open.

Notice how I checked the boxes. It was no coincidence that I missed the point "Restructuring infobase tables". If you install it, then during the testing process all database tables will be recreated. These are areas of memory that we do not physically see when we work with the program, but in which all the data of our reference books, documents, etc. is stored. Restructuring is a good thing, but it can take a long time. Therefore, take this into account if you have a large database. It is advisable to perform the remaining verification modes. But I remind you once again that a backup copy is made before performing the “Testing and Correction” procedure.

Just in case, I’ll explain all the other checkboxes. If you're not interested, you can skip it, but I always try to understand what I'm doing and it seems to me that I'm not alone, so I'll give an explanation:

• Reindexing infobase tables– I wrote about tables above. So, these tables are numbered in a certain way, but due to the fact that we are constantly deleting or adding something, the numbering ceases to be sequential. As a result, the system begins to slow down. Reindexing renumbers all tables in the desired order:
• Logical integrity check– searching for errors in the correct organization of data storage in the database;
• Referential integrity check– checks the database for broken links. A broken link is a link to a non-existent element. Most often, this occurs if some directory element or document that is used in other documents is deleted from the database. In this case, in the testing setup, you can choose what to do if there are references to non-existent objects: create, clear, or not change. It is better to clear such links.
• Recalculation of results– this is more relevant for 1C Accounting, but I’ll explain anyway. In 1C, at certain time intervals, results are calculated for certain areas of accounting (registers) so that at the time the user generates a report, the program does not summarize data for the entire period, but takes previously calculated data and displays it to the user. In 1C Accounting, this significantly speeds up the generation of reports such as the “Turnover balance sheet”.
• Compressing infobase tables– To be honest, I don’t know for sure how the compression is carried out. I read somewhere that those documents and directories that we delete in Enterprise mode are not actually deleted, but continue to be stored, but we do not see them and it is this compression procedure that finally deletes them. If anyone knows reliably how compression is performed, you can write in the comments.

That's all! Now you can click “Run”.

We carry out data transfer to ZiUP 3.0

✅ Seminar “Lifehacks for 1C ZUP 3.1”
Analysis of 15 life hacks for accounting in 1C ZUP 3.1:

✅ CHECKLIST for checking payroll calculations in 1C ZUP 3.1
VIDEO - monthly self-check of accounting:

✅ Payroll calculation in 1C ZUP 3.1
Step-by-step instructions for beginners:

So, after you have created an empty ZUP 3.0 database (read how to install 1C here), open this database. The program launches “Initial program setup” by default. At the first step, you need to choose whether you want to configure the system to work from scratch (i.e. no transfer required), carry out the transfer from the program "1C Salary and Personnel 7.7, edition 2.3" or transfer data from "Salaries and Personnel Management, edition 2.5". We select the second one and click next.

The next step is to select the information base from which we will download data. The choice comes from a list identical to what we see when starting 1C. You also need to specify the username (if they were created in database 2.5) and password (also if there was one).

Separately, I would like to draw your attention to the fact that at the top of the window at this step the release number is indicated. Release of the information base from which we transfer data must be no lower this indicator. Otherwise, the program will not allow the transfer to be completed and an error will be displayed. Read about how to properly update 1C.

Now pay attention to transfer period. In this case, the minimum required period for transfer is indicated, i.e. for the two previous years (2012 and 2013).

ATTENTION!!! In 2016, a new transfer option appeared, the so-called recommended (short) option. I highly recommend reading it in this article:

So, decide on the period and click “Next”. The next step is to press the button "Load data" and the data transfer process will begin. It can be quite lengthy depending on the amount of information in the source database. The process is automatic, we observe.

During the transfer process, the program may notify you of errors. Don’t be scared and give up everything, just read the messages displayed, correct the shortcomings and perform the transfer again. Repeated transfer will not duplicate those already transferred, because the transferred information will be compared with what is already available using unique identifiers individual for each type of information (for example, for an individual, this is full name and date of birth).

Soon there will be new interesting materials on.

To be the first to know about new publications, subscribe to my blog updates:

To migrate from ZUP 2.5 to ZUP 3, you must perform an initial data transfer. Since ZUP 3 differs significantly from ZUP 2.5, the transition is carried out precisely by data transfer, and not by updating.

To successfully migrate from ZUP 2.5 to 3.1, you should perform the following sequence of actions:

1. “Close” the month in ZUP 2.5.
   The transfer can be made not only to the beginning of the year, but also to any month. You must first complete the final calculation for this month in ZUP 2.5: calculate wages, contributions, reflect the payment and transfer of personal income tax.
   

   It is important to completely “close” the month in ZUP 2.5 before transferring. You cannot start calculating a month in ZUP 2.5, and finish it in ZUP 3 - this option is not provided!
   

2. Expand the EMPTY ZUP database 3.
3. Update the ZUP 2.5 and ZUP 3 databases to the latest releases.
   Developers regularly fix transfer errors and improve the transfer, so the likelihood of getting the most correct transfer results is higher if you update the databases to the most current releases.
4. In ZUP 3, in the initial setup assistant for a new information base, indicate that the transfer will be made from ZUP 2.5.
   Before ZUP 3.1.8:
   Starting from ZUP 3.1.8:
   
   
5. Further when working in ZUP 3.1.8 it is necessary to indicate how the data will be loaded: by direct connection to the database or through files:
   
   Read about the possibility of loading data through files in the publication
   Up to ZUP version 3.1.8 Only the option of downloading by direct connection was possible in the ZUP 2.5 database.
   The rest of the article discusses data transfer using a direct connection to the database.
6. To download data from the ZUP 2.5 database, you must specify the ZUP 2.5 information base from which you want to transfer data:
   If a list of users was configured in the ZUP 2.5 database, then indicate the user name and password under which the connection to ZUP 2.5 will be made (this must be a user with full rights).
7. In the next step follow the link Settings You can choose the data transfer option:
   The developers have implemented two options for switching to ZUP 3 from ZUP 2.5:
   - the so-called “recommended” transfer – the switch is in position (this option is also called “new transfer”, “residue transfer”);
   - the so-called “full” transfer - switch to position (for this option you can also find the name “old transfer”).
   For the recommended transfer, you will need to indicate the start month of accounting in ZUP 3, for a complete transfer - the year from which all calculated data will be transferred to ZUP 3.
8. Start transferring data from 1C ZUP 2.5 to ZUP 3.1.
   

Selection and comparison of options for transferring data from 1C ZUP 2.5 to ZUP 3.1

Selecting a data transfer option

Before starting the transfer procedure, you need to decide which data transfer option to use. The developers recommend the option Use new HR accounting and payroll capabilities , however, an option Use accruals from the previous program can also be used, it is fully functional, and objectively it cannot be said that it is worse than the “recommended” option. The choice should be made based on the characteristics of the ZUP 2.5 database, as well as the needs of the program users. Below we discuss the features of the first and second options for transferring data from 1C ZUP 2.5 to ZUP 3.1.

• Transferred slice personnel data as of the start date of accounting - information is loaded only on employees working on the date of transfer, their current staffing, planned accruals in force at the time of transfer, entitlement to leave, leave balances and current periods of absence;
• The results of accruals/deductions are NOT transferred - this means that in ZUP 3 it will not be possible to generate information about accruals/deductions for the period before the start of maintenance in ZUP 3 in salary reports;
• Data on mutual settlements – balances are loaded on the accounting start date;
• Data on personal income tax – balances of unwithheld/untransferred personal income tax are transferred to the beginning of the year, and also, if the transfer is not performed to the beginning of the year, then - data on personal income tax for the period from the beginning of the year to the date of transfer;
• Data for calculating the average - all necessary data is transferred (for calculating benefits - data for the previous 3 years is transferred; for calculating vacation pay, business trips, etc. - for 1.5 years).

What you need to add and configure manually:

• Configure HR accounting and payroll settings;
• Create and configure “one-time” (unplanned) types of accruals and deductions that were periodically used in ZUP 2.5 and will be used in ZUP 3.

The advantage of the “recommended” transfer is that unnecessary information does not “arrive” in ZUP 3. This eliminates the possibility of transferring erroneous program settings and types of charges from ZUP 2.5. This also contributes to the fact that the transition to ZUP 3 from ZUP 2.5 is completed quite quickly.

But it is worth considering that with this transfer option it will not be possible to view and generate reports for previous periods, so you need to save the ZUP 2.5 database in order to have access to this information.

Features of “full” data transfer

The second transfer option corresponds to the switch position Use accruals from the previous program . This is a more complete transfer option when switching to ZUP 3 from ZUP 2.5. It involves the following data transfer:

• The entire personnel history of current employees is transferred, and the transfer is made directly to personnel documents Recruitment , Personnel transfer , Dismissal– thus, all personnel documents on the reception and transfer of employees will be available in ZUP 3;
• The results of accruals/deductions and data on mutual settlements are transferred during the period of data transfer. This means that in ZUP 3 it will be possible to generate salary reports (records, payslips) for the entire period of data transfer, including for the period when accounting in ZUP 3 has not yet been maintained;
• Data on personal income tax and contributions - the entire history of personal income tax and contributions for the transfer period will also be available;
• Data for calculating the average - all necessary data for calculating the average is transferred (for calculating benefits - data for the previous 3 years is transferred; for calculating vacation pay, business trips, etc. - for 1.5 years).

The disadvantage of this transfer option is the large amount of information transferred. This leads to a long time for the transfer itself and to the fact that accounting errors from ZUP 2.5 can “move” into ZUP 3.

A detailed description of the structure of the transferred data for the “full” transfer option is available in the publication.

Comparative table of options for transferring data from ZUP 2.5 to ZUP 3.1

What data is not transferred to ZUP 3

None of the data transfer options transfer the following data to ZUP 3:

• Staffing table (it is already formed in ZUP 3 according to the current staffing arrangement);
• Accounting reflection settings;
• Additional details and information;
• Management accounting data.

See also:

If you are a subscriber of the BukhExpert8: Rubricator 1C ZUP system, then see the materials