Transferring data to zoom 3.1. Formation of information in the staffing table after the transfer

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 switching 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.
All documents are transferred for mutual settlements.
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.

Question: Bukh. 3.0 CORP - no separate divisions

Hi all. I noticed that in one of the bases there are no separate units, although the CORP configuration. There is a suspicion that I didn’t check some unfortunate box that was neatly hidden by the developers.
If we go into divisions, we cannot give it a separate status and there is no grouping for them in the chart of accounts.

Although it is available in other databases. For example here:

And I compared all the settings and looked at the predefined ones in the chart of accounts in the configurator, but I can’t find the reason. I ask the guru for help.

Answer: The tax office was specified, I found “Maintain Accounting for Divisions” in the constants and put “YES”. In divisions you can now select separate ones, but selection for them has not appeared in the account. Maybe there are still options?

Question: v7: Transition from complex 3.0 to ed. 4.5

Hello. The task is to transfer from 7.7 complex 3.0 to 8.3 UT 11. But first, in order to get by with the standard one, I think it needs 4.5, and then a standard transition. How was the transition from 3.0 complex to 4.5? Is it a regular association, as it is in 8, or is it somehow unique?

Answer:() In terms of labor costs, the most economical option is to develop your own upload to CD. If we are talking only about trading activities, there was no production and salaries, then the unloading turns out to be quite simple and comes down to filling out several documents for entering the beginning. residues in UT11.
You will only need rules for 10-15 directories; in the CD, before uploading the data with queries, we select all the balances and transfer them to the UT as the initial input. leftovers With this option, you have a maximum of 1 day of work.

Question: Transition of 1C server from Windows mssql to Linux

Please advise on the situation.
Installed 1C server under Windows Server and MSSql.
We need to switch to Linux and Postgresql is already there.

How to make such a transition? Perhaps there is a database conversion?

Thank you in advance.

Answer:() So why not? The most trouble-free part, IMHO

Question: Transition from ZUP 2.5 KORP to ZUP 3.1. Is there any reason?

There is ZUP 2.5 CORP.
The organization has more than 1,000 employees (there is production, production standards, wages depend on the work performed).

How to convince of the need to switch to 3.1?

What's the gain? Well, it’s clear that one day the support for CORP will stop working, and then it will be necessary to switch.
Until then?
Just - to be ready?

Who transferred “not kids” - how many months did they conduct two salary calculations (in ZUP 2.5 and in ZUP 3.1) before completely abandoning 2.5?
Or are there better options for transition practices?

Answer: I don’t see any point in switching from the corporate version. large holdings are sitting quietly and are even looking for special consultants for 2.5 more

Question: Transition to ZUP3 KORP

We are planning to switch from ZUP3 PROF to ZUP3 CORP.

Anyone who has made a similar transition, please tell me:
1) ZUP3 CORP - working or still damp? Does it have many critical errors? 2) How often are bugs fixed and updates released?
3) Does the transition from ZUP3 PROF to ZUP3 CORP occur through a simple update?
4) Do we need to increase the server capacity if we switch to ZUP3 CORP?
5) I was interested in the possibility of a “Self-Service” section in ZUP CORP. Do I understand correctly, if we have 700 employees, then to use this functionality we need a separate license for each connection?!

Answer: 3) Does the transition from ZUP3 PROF to ZUP3 CORP occur through a simple update? - it seems that there are instructions on releases. Nothing complicated.
4) Do we need to increase the server capacity if we switch to ZUP3 CORP? - No.
5) I was interested in the possibility of a “Self-Service” section in ZUP CORP. Do I understand correctly, if we have 700 employees, then to use this functionality we need a separate license for each connection?! - you can set a timeout, after which the system will turn off an ordinary employee so that he does not stay too long. In general, you won't need many licenses.

The Self-Service subsystem is very poor in functionality. I had to write a lot.

In general, the impressions from CORP are the same as from PROF. No specific glitches were noticed.

Question: Incomprehensible behavior after switching from ZUP 2.5 to 2.5 Corp

Good afternoon, colleagues.

Additional charges have appeared according to ex. accounting after the transition.
After quickly going through the processing of the posting, I noticed that the requests for accruals had changed:
// in the basic file SELECT Results.Individual AS Individual, Results.Result AS Result, SELECT WHEN Results.Type of Calculation.Calculation Method = VALUE(Enumeration.Methods of Calculation of Payment of Labor.Piecework Earnings) THEN Results.Result OTHERWISE 0 END AS ResultPiecewise, 0 AS Result of Withholding FROM Calculation Register . Basic Accruals of Employees of Organizations AS Results LEFT JOIN Register of Information. Accounting for Employees' Earnings. Cutting Last (¶mEnd) HOW Accounting for Employees' Earnings BY Results.Individual = Accounting for Employees' Earnings.Individual WHERE Results.Registration Period = ¶msStart And Accounting for Employees' Earnings.Accounting for Organizational Accruals AND Results.Result<>0 COMBINE ALL...Additional Accruals COMBINE ALL NDFL
And in another
// ZUP Corp. Choose the results. Pino as an individual, results. The result as a result, choice when the results. Vydrasskhoporta = value (transfer. Conscious accounts. Social work) then results. The result is different as a result, 0 as a result, results. Organization. Organization. Organization HOW ORGANIZATION TO PLACE Accruals Data FROM Calculation Register. Basic Accruals of Employees of Organizations HOW Results LEFT CONNECTION Register of Information. Accounting for Employees' Earnings. Slice of the Last (¶mEnd,) HOW Accounting for Employees' Earnings BY Results.Individual = Accounting for Employees' Earnings.Individual WHERE Results.Registration Period = ¶mStart AND IS NOTNULL( Accounting for Employees' Earnings. Accounting for Accruals in the Organization, FALSE) and Results. Result<>0 COMBINE ALL...

Answer: Hmm, it turned out that in the non-updated zoom corp such a hat is a condition with a check for null. Tell me, please, I didn’t google anything... but I wish I knew what else to google =\

Question: Client-server PROF+CORP. Licenses

This is a general problem, I need some advice
Bukh PROF, Zup CORP
Planned
1. Server license
2. PROF license 50 uses
3. CORP license 20 uses

The license for the server is CORP, apparently. The question is - will there be no conflicts in this situation?

Answer:() don’t let it bother you, PROF licenses are quite suitable for accessing the ZUP CORP

Question: Hierarchy of separate divisions in BP Corp 2.0

The exchange between ZUP 2.5 and BP Corp 2.0 has been configured. The exchange is almost standard. In fact, only the document “reflection of wages in regulatory accounting” is downloaded from the ZUP.
The ZUP now has a hierarchy of divisions of this type: the parent (let’s call division A) has the “separate division” flag turned on, while the division itself (division B) has this flag not set. Those. structure of the form A -> B. When uploading to the BP CORP, the same hierarchy appears, but I noticed that when I try to write to the BP Corp of division B, the following message is written:
"This unit is separate.
A group of segregated divisions can only include a segregated division." That is, the configuration prohibits creating non-segregated divisions within a segregated division.
Maybe someone knows why such a restriction was established (and this restriction is not in the ZUP). It seems to me that just such a structure is more logical than when the separate divisions inside are also separate...
Well, since all this was somehow loaded into BP Corp, what glitches could appear because of this?
Unfortunately, it is still quite far from the characteristics of the bay. accounting, so if possible, then explain more clearly))
Thank you.

Answer:() the calculation of shares will be incorrect, because, as far as I remember, in all queries in all conditions the queries contain “= &SeparateUnit”, and not “IN HIERARCHY”, etc.

() “When in practice they want this not to be the case, they create a segregation in the program”
Who has this practice? The methodologists of the 1C company?
So, in order not to deal with such crap, but to normally distribute costs among actually existing divisions within a separate one, sex with the program is required.

Question: Transfer of Contact information from UPP 1.3 to BP 3.0 Corp

Hello, I don’t work with 1C at all - knowledge and experience are sorely lacking. Please help me figure out the conversion of data, namely the transfer of contact information, which is in UPP 1.3. is stored in information registers, and in BP 3.0 Corp in the tabular section of the corresponding directories.
I tried the option described here - in its original form, the function TRANSFERWhenUpdatingC20() for some reason does not give a result, and I can’t edit it “for myself” - I don’t have enough knowledge.
For the same reason, I can’t adapt it to my case.
I would be grateful for help and tips.

Answer:

Open the standard exchange rules. When you don’t know which ones you need specifically, the search mechanism is approximately the following.
You understand that you need to transfer the CI from the register to the tabular part. That is, from the old mechanism to the new one. The old one was implemented on conferences with a regular application, such as BP 2.0, UT 10.3, etc. And the new one is already managed forms. BP 3.0, UT 11, etc. Open a new conf. See what old confs you can set up an exchange with there.
For example, you open BP 3.0 and see there an exchange with UT 10.3. Then look where it is in the configurator to find the rules. You understand that there is an exchange plan and that it has rules. Then save these rules to your computer (this is not easy to do, you need to read it. There is a lot of information on the Internet), then load it into the conversion and see how it is implemented.
--- Message merging, 9 Nov 2016 ---
Better yet, go to the installed configuration template and take it from there

The typical functionality of ZUP 3 allows you to perform the initial transfer of data from the program, edition 2.5. One of the transfer options is the so-called “full” data transfer. Let's take a closer look at what information is loaded and where when performing this data transfer option.

General information

What data is loaded

With the full option of data transfer, you will need to indicate the year from which you want to transfer the calculation data to ZUP 3. Information about the calculations made for the entire period from the specified year will be loaded into ZUP 3.

Upon complete transfer, the following data will be loaded into ZUP 3:

reference information – filling out reference books Organizations,Divisions ,Positions ,Opening hours , Individuals ,Employees ;
personnel data – the entire personnel history is transferred directly to personnel documents ( Recruitment,Personnel transfer ,Dismissal );
information about accruals and deductions made is loaded into the document Data transfer (with code Salary And WIP) for the entire period from the year that was specified when performing the transfer;
types of accrual and deduction - all types of accrual and deduction assigned as planned in personnel documents are transferred, as well as types of accrual and deduction present in the document Data transfer (with code Salary And WIP );
settings for personnel records and payroll calculations - the program, based on the transferred information, performs only those settings that it can calculate based on this data;
information on mutual settlements with employees – all information on mutual settlements for the period from the year specified when performing the transfer is transferred;
data for calculating average earnings - data for calculating total average earnings (vacation pay, business trips, etc.) are transferred for the previous year and a half, and for calculating benefits calculated based on average earnings (sick leave, parental leave, etc. ) for the previous 3 years;
data on personal income tax and insurance premiums - information is transferred for the period from the year specified when performing the transfer.

What objects are the data loaded into?

With a “full” transfer, information is loaded either directly into accounting documents or into documents Data transfer .

The following accounting documents are used:

documentation Recruitment , Personnel transfer , Dismissal ;
Holiday to care for the child ;
journal documents Alimony and other deductions ;
Applications for deductions ;
Agreements (including copyright) ;
Loans to employees.

A fairly significant amount of information from ZUP 2.5 is loaded into the document Data transfer (Administration - See also - Data transfers). These documents have letter numbers, by which you can understand what data each document contains:

Codes that apply to both data transfer options:

RKD, ROtp - register of personnel orders for the T-2 card;
ZP_ SZO, ZP_SZFSS - initial data for calculating average earnings (information on annual bonuses is loaded into a document with the code ZP_GP); IL - calculations of deductions according to executive documents;
Personal income tax – tax accounting data for personal income tax;
PSS - social insurance benefits, to be reflected in 4-FSS;
SV – accounting data for insurance premiums;
DnSost – information about employee absences;
РВ – working time registered by document Report card ;
OSO – data for calculating vacation balances;
ZP – data on accruals and deductions;
WIP – data on accruals and deductions for employees, source data for salary reports;
ZS - settlements for loans to employees;
VO – data on mutual settlements with employees (accrued, paid).

Transfer of reference information

“Full” data transfer to ZUP 3.1 involves loading the following reference information from ZUP 2.5:

Directory Organizations — information about all organizations for which accounting was kept in ZUP 2.5 is loaded: names, registration information (TIN, KPP, OGRN and other codes), addresses and telephone numbers, responsible persons, basic accounting policy settings;
Directory Divisions , Opening hours , Positions— all departments, schedules and positions are transferred.
Directory Employees— information about all employees who are present in the transferred personnel documents and documents is loaded Data transfer ;
Directory Individuals — information about those individuals for whom the corresponding directory element is loaded is transferred Employees, as well as individuals present in the documents Data transfer .
reference books Accruals And Holds– the types of accruals and deductions that are assigned to employees as planned in the transferred personnel documents are transferred, as well as the types of accruals and deductions that are present in the documents Data transfer (with code Salary And WIP ).

Transfer of HR accounting and payroll settings

Compared to the “recommended” data transfer, in which only a slice of data was loaded on the date of transfer, a larger amount of information is “moved” as part of the “full” transfer. Therefore, the program has more options to determine program settings.

For example, since data on the history of accrued wages is being transferred (this information is loaded into documents Data transfer - more about it below), then the program has the ability to determine some initial settings based on the loaded accruals. If in this data the program detects accruals for a business trip or for working on weekends and holidays, then the corresponding checkboxes will be automatically selected in the payroll settings.

The filling principle is similar for other settings for payroll calculation, personnel records and accounting policies. To fill out the settings, the program takes information from documents Data transfer , from transferred personnel documents, information on planned accruals and deductions, as well as from directories.

Transfer of personnel data and information on planned accruals

“Full” data transfer involves transferring the entire personnel history from ZUP 2.5 directly into personnel documents 1C ZUP 3. You can view these documents in the document log All personnel documents (Personnel – All personnel documents).

These documents contain the following information:

positions occupied by employees;
work schedules used;
right to holidays;
number of bets taken;
type of employment;
planned accruals - with a “full” transfer, all planned accruals that have ever been assigned to employees in a planned manner are loaded into ZUP 3.

advance payment option - if in ZUP 2.5 in the directory Employees a fixed advance amount was filled in for the employee, then in ZUP 3.1 for such an employee in the document Recruitment will also be established Fixed advance . If the fixed amount of 2.5 is not filled in, then the option will be substituted Calculated for the first half of the month .
Also in ZUP 3.1 there is another way to calculate the advance Percentage of the tariff . If you want to assign exactly this option for calculating an advance payment to an employee, you can use the document Advance change (enter it on the first day of the month from which accounting in ZUP 3.1 begins).

information about the employment contract.

Formation of information in the staffing table after the transfer

After completing the “full” transfer to ZUP 3.1, a staffing table is formed, but it is formed on the basis of information about occupied staff units.

Also, information about the presence of “harmful”/“difficult” positions for which additional contributions must be calculated is loaded into the staffing table. If the organization at the time of data transfer has an employee working in a position for which additional contributions are calculated, then this information will be transferred to the corresponding position in the staffing table.

And it is on the basis of this information in the accounting policy settings ( Organization directory - Accounting policies and other settings tab - Accounting policies) the checkbox will be checked There are employees with the right to early retirement . And perhaps the checkbox will be checked The results of a special assessment of working conditions are applied , if an employee is present during the transfer, for whose staffing unit a class of working conditions is assigned.

Transferring information about planned deductions

Information about current planned deductions in ZUP 3.1 is loaded through the relevant journal documents Alimony and other permanent deductions (Salary - Deductions).

For example, if at the time of transferring data to ZUP 2.5 the employee had a valid deduction under a writ of execution, then a document will be created in ZUP 3.1 Performance list with similar information for calculation.

Another example is the withholding of voluntary insurance contributions to the Pension Fund. If in ZUP 2.5 this type of deduction is valid for an employee at the time of data transfer, then in ZUP 3.1 a specialized document will be created Withholding of voluntary insurance premiums .

If we are talking about some kind of arbitrary planned withholding, for which there is no corresponding document in ZUP 3.1, then in the reference book Holds a new type of deduction will be created, and a document will also be generated in the journal Alimony and other deductions , to whom this deduction is scheduled to be assigned to the employee.

Transferring information about settlements with employees

The history of mutual settlements with employees for the period specified in the data transfer assistant is loaded into documents with number VZ. Due to the fact that all information about mutual settlements for the period is transferred, in the salary reports of ZUP 3 it is possible to track the history of balances for employees during the transfer period.

However, transferring the full history of mutual settlements for all employees (even dismissed ones), and not the balances of mutual settlements of only working employees, as happens with the “recommended” transfer, may lead to the transfer of “non-existent” debts due to accounting errors in ZUP 2.5.

If such a situation arises, then the employee’s debt can be adjusted directly with the document Data transfer . The adjustment is performed using the following accumulation registers:

Salary payable – based on the balances in this register, the amount for filling out documents is formed Statement... ;
Mutual settlements with employees – based on the balances in this register, the balance for mutual settlements with employees in the salary reports of the ZUP is formed.

It is worth keeping in mind that “receipt” movements increase the debt to the employee, and “expense” movements, on the contrary, reflect the fact that the debt has been written off. Taking this into account, if necessary, “non-existent” balances should be adjusted.

Information about accruals and deductions made during the transfer period

A “full” transfer, in contrast to a “recommended” transfer, involves uploading information about accruals and deductions made during the transfer period. This information is stored in documents Data transfer , which have the following numbers:

Salary– in this document, information is loaded into the calculation register Accruals And Holds. The transfer of this information, in particular, will make it possible to take into account accruals and deductions for past periods in current calculations.

WIP– these documents store information about accruals, deductions and hours worked, which will be used to generate salary reports for the transfer period ( Pay slip ;A complete set of charges, deductions and payments ;Salary analysis by employee and so on.).

Information for calculating average earnings

Information for calculating average earnings is transferred to documents with the following numbers:

ZP_SZO– the documents contain information about time worked and accruals, which will be used in ZUP 3.1 when calculating vacation pay, business trips and other cases in which the retained average earnings are calculated (except for cases of calculating benefits). Information for each month is loaded into a separate document.

Data on hours worked is filled in the accumulation register Time data for calculating the average (general) , and information about accruals in the accumulation register Data on accruals for calculating average earnings (total) .

ZP_SZFSS– the documents contain information about accruals and “outlier” periods (illness, parental leave, etc.), which will be used to calculate benefits based on average earnings (sick leave, parental leave). A separate document is also created for each month.

In addition to information about accruals and time in this document in the savings register Policyholder data for calculating average earnings (FSS) may contain information about the earnings of employees from previous places of work, if this information was filled out in ZUP 2.5 in the document Certificate of earnings from other policyholders .

Accounting data for personal income tax and insurance premiums

Applications for personal income tax deductions

Information about deductions that were configured at the directory level in ZUP 2.5 Employees in ZUP 3.1 are loaded into separate documents in the journal Applications for deductions (Taxes and contributions - Applications for deductions).

Data on personal income tax, insurance premiums and benefits

Information about income, calculated insurance premiums and calculated, withheld and transferred personal income tax, as well as applied deductions, is loaded into documents Data transfer with codes NE,Personal income tax. With a “full” transfer, this data is loaded into ZUP 3 for the period starting from the year that was specified in the initial transfer assistant, and not just for the current year, as was the case with the “recommended” transfer.

It is also worth noting that in the document with the code PSS information about benefits at the expense of the Social Insurance Fund that were accrued during the transfer period is loaded. This information is also used to fill out regulated reports (4-FSS, ERSV).

A simplified option for transferring data from 1C ZUP 2.5 to 1C ZUP 3.0

When transferring data from 1C ZUP 2.5, pay attention to the “Settings” button, where you can set the data transfer option. By default, 1C ZUP 2.5 offers a new simplified option for data transfer. But you can use the transfer of accruals from the previous program if there is a lot of data:

1C developers indicated that it is not recommended to use the transfer of accruals from the previous program. However, each 1C 8.2 ZUP information base is unique, and you need to look at which data transfer option is best suited. Each data transfer option has its own pros and cons, which are reflected in the table “Comparison of data transfer options”:

Transfer of personnel data and planned accruals to 1C ZUP 3.0

In the old transfer, the entire personnel history of current employees will be transferred, that is, the entire directory of departments will be transferred, everything will be transferred to the directory of positions, etc. for the entire period.

In the new version, only a slice of personnel data is transferred to the accounting start date. That is, only those divisions, those positions and those employees are transferred that are relevant on the start date of accounting in the new 1C ZUP 3.0 database. In this case, the personnel history for the T-2 card is lost.

During a new transfer, a slice of personnel data is reflected in the Personnel section - the document “Data for the start of operation” and it was not carried out initially. The document is not completely filled out, the employees, department, position, work schedule, vacation balances are indicated:

In this case, data on planned accruals is not transferred, since planned accruals under the new option are not transferred from ZUP 2.5 to ZUP 3.0. It is assumed that the user must enter planned accruals independently. This might actually be easier than dealing with the old settings:

In addition, planned accruals can be assigned to employees in the staffing table, because the staffing table is also transferred as a staffing arrangement to the start date of accounting. Then in the document “Data for the start of operation” you need to click the “Update according to the staffing table” button and all planned accruals according to the staffing schedule will be automatically filled in:

After updating the staffing table, the document is ready to calculate salaries, because there is a list of employees and a list of planned accruals.

After transferring data according to the new simplified version from 1C ZUP 2.5 to 1C ZUP 3.0, while planned accruals are not assigned to employees, salaries will not be accrued in 1C ZUP 3.0.

Transfer of accruals and deductions to 1C ZUP 3.0

When choosing to transfer accruals and deductions from the previous 1C ZUP 2.5 program, the 1C ZUP 3.0 user can create a summary for the previous period of accrued wages and see: how much was accrued, withheld, paid, etc. In the new simplified transfer, accruals and deductions from previous periods are not loaded.

Transferring data to calculate average earnings in 1C for personnel 3.0

Data for calculating average earnings is transferred from 1C ZUP 2.5 to 1C ZUP 3.0 in both versions, but in different ways. When transferring accruals from the previous database, the data is saved in the “Data Transfer” document. You can also correct the data for calculating average earnings in this document.

In the new transfer option, data for calculating average earnings in 1C ZUP 3.0 is stored in information registers and can be edited in the average earnings calculator. But there is one nuance here. For example, when creating a vacation document, as soon as you specified the vacation period, the average earnings will be immediately calculated, because the data on average earnings was transferred automatically during the transition:

Data on average earnings can be edited if an error is found:

The “Use the same data when calculating sick leave and child care benefits” checkbox is automatically checked:

Reset this checkbox; it cannot be installed in 1C ZUP 3.0. If you enter data or simply open data on average earnings, then check the box and post the vacation document, then this data will replace the base for calculating sick leave and the data will be lost.

The same thing applies to sick leave, when you enter data for average earnings in the calculator, you need to uncheck the box. Since the document reflects data for calculating benefits, and this is a completely different base, not for vacations. Therefore, the checkbox needs to be unchecked:

Transfer of data on mutual settlements to 1C ZUP 3.0

When completely transferring from the previous database with data on mutual settlements, it is necessary to understand and bring the balances back to normal. After a simplified transfer to 1C ZUP 3.0, data on mutual settlements is entered manually.

Transfer of data on personal income tax and contributions to 1C ZUP 3.0

Data on personal income tax and contributions, when fully transferred from the previous database, are reflected in 1C ZUP 3.0 for the entire period.

In the new transfer method, data on personal income tax and contributions are transferred using the “Data Transfer” document, but only for the current year, and those that need to be reflected in the reporting. In 1C ZUP 3.0, select the “Administration” section and open the “Data Transfer” document, which displays information only for the current year:

For example, for personal income tax, information that needs to be shown in reporting is reflected:

Comparison of options for transferring data from 1C ZUP 2.5 to 1C ZUP 3.0

When completely transferring data from the previous 1C ZUP 2.5 information base, more data is reflected in the new 1C ZUP 3.0 database. But the transfer process takes more time and places increased demands on data quality in 1C ZUP 2.5. If there were errors or incorrect settings in 1C ZUP 2.5, all this will be transferred to the new 1C ZUP 3.0 program. You'll have to tweak it and waste time.

The new simplified transfer uses the minimum required data. This is a quick transfer. In the new 1C ZUP 3.0 database, you can apply the new necessary settings, but manual data entry is required. In particular, in order for the salary to be calculated, it is necessary to complete the planned accruals.

Please rate this article: