In this article we will look at step-by-step instructions for hiring an employee in 1C Accounting 8.3.

Before moving on not only to reflecting in the 1C:Accounting program the hiring of an employee, but also to other main personnel documents, you need to make some program settings.

Go to the "Administration" section and select "Accounting Settings".

In order for us to use basic personnel documents in 1C, it is enough to enable only two add-ons.

The first is located in the “General Settings” section. We will point out that accounting for wage expenses, as well as the personnel records we need, should be kept in this program. Below, in the “Personnel Accounting” section, set the moisture level to “Full”. This add-on will give us access to basic personnel documents, including hiring employees.

Registration of hiring an employee

Creating a new employee

In the 1C: Accounting program, just like in 1C: ZUP, there are two directories: Employees and Individuals. One person can have as many employees as there are jobs at a given enterprise he has, for example, the main place of work, part-time work, a GPC agreement.

There must be only one individual. It is unacceptable to duplicate entries in this directory, since it is based on the entries in it that personal income tax is calculated to employees.

Hiring an employee

Go to the “Salaries and Personnel” section and select “Hiring”. If you do not have this item, then go back one step higher to the initial setup of the program.

In the header of the new document you create, you need to indicate the department, position and organization where you are hiring an employee. The employee you created earlier is also indicated here.

The default reception date is the current date, but we can edit this parameter. The trial period in months can be configured in the appropriate field. Next, you need to indicate the type of employment, which is selected from the drop-down list and is limited to four items.

Now all that remains is to fill out the conditions for employment. In the tabular section with accruals, you can indicate several types of accruals at once, for example, salary, bonus, etc. In our example, we set the employee only to pay the AUP salary in the amount of 30,000 rubles.

The procedure for calculating the advance is indicated below: a fixed amount or a percentage of the tariff. You can enter any text in the “Conditions of acceptance” field.

This document will come into force after we complete the movements in the relevant information registers.

See also video instructions for registering an employee as a staff member:

An excellent video course on programming in the 1C: Enterprise system. Includes 7 courses:

1. 1C: Enterprise 8.3. Developer's first steps
- navigate the structure of the new version of the 1C:Enterprise 8.3 system;
-understand the general principles of system development;
-choose ways to further study and master the 1C:Enterprise 8 system;
-use basic skills in the 1C:Enterprise 8 environment;
-work with directories, documents and other objects, configure their properties;
-at the initial level, work with basic form controls, event handlers and other system functionality.

2. 1C:Enterprise 8.3. Introduction to configuration. Main objects
-You will understand the general principles of building the 1C:Enterprise 8 system
-Master the basic skills of working in the 1C:Enterprise 8 environment

3. Using queries in the 1C:Enterprise 8 system. Query language
-Write requests
-Work with the query builder
- Correctly use different types of information security tables
-Get acquainted with the features of working with virtual register tables

4. 1C:Enterprise 8.3. Solving operational problems
-Work with accumulation registers
-Write algorithms for conditional document processing
-Use a controlled locking mechanism
-Get acquainted with ways to improve the performance of solutions

5. 1C:Enterprise 8.3. Solving accounting problems
-Independently design a chart of accounts and an accounting register to solve problems of synthetic, multi-company, analytical, quantitative and currency types of accounting;
- Correctly fill out the register with movements for all types of accounting, both when conducting documents and when recording manual operations;
-Describe optimal complex processing of conducting primary and regulatory documents with analysis of the results of the accounting register in multi-user mode when using configuration-controlled locks;
-Use the data composition mechanism to develop any accounting reports, both summary synthetic and detailed analytical.

6. 1C:Enterprise 8.3. Solving calculation problems
-Confidently use 1C:Enterprise 8.3 tools
-Know and be able to apply in practice methods for solving problems of automation of payroll calculation and personnel accounting
-Be able to monitor the performance of the solution being developed
-Understand the relationships between configuration objects, physical tables and virtual tables of the calculation register
-Find and correctly correct errors: both methodological and software
-Proficient in the functionality of the 1C:Enterprise 8.3 platform to the extent necessary to solve calculation problems

7. 1C:Enterprise 8.3. Integration and data exchange tools
-Work with text files and documents
-Work with .dbf files
-Organize Internet connections
-Work with email and use http, ftp protocols
-Use OLE and COM technologies
-Use a consistent XML access model
-Use XDTO and mixed XML model
-Organize data exchange
-Use the mechanisms of the “Exchange Plans” object
-Use the “Data Conversion” configuration

Enterprise 8.3 Practical guide for 1C developer M. G. Radchenko

Year of Issue: 2013
Version: 3
Developer: M. G. Radchenko Publishing house Firm 1C Examples and typical techniques
Developer website: 1c.ru
Bit depth: 32bit-64
Interface language: Russian
Tablet: Not required
System requirements: Processor: 1.4-2.5 GHz RAM 1.0 GB and 10 GB of free hard disk space
Description: Book by M. G. Radchenko 1C: Enterprise 8.3. Practical guide for developers. Examples and standard techniques is a guide that allows you to quickly master the techniques of developing and modifying application solutions on the 1C:Enterprise 8.3 platform. Using the example of creating a real application solution, the structure of various system objects, their purpose and method of use are shown. Procedures are presented in the built-in language, including using the query language, which are provided with detailed comments. The book can be used both as a practical guide and as a reference guide. The application solution discussed in the book takes into account the accumulated development experience in the 1C:Enterprise 8 system and demonstrates many of the new capabilities and mechanisms provided by version 8.3. The material is intended for beginner developers who are not familiar with the 1C:Enterprise 8 system.

Clear Tutorial 1C Accounting 8.3 - How to prepare a report on retail sales.

"1C:Enterprise 8.3" - This is a significant evolution of the platform architecture towards multi-platform, mobility and web-enabled operation. All these questions, of course, are of interest primarily to experienced developers and are beyond the scope of this book.
However, even for novice developers, this version of the platform contains interesting features that need to be understood and used effectively. The new “Taxi” interface, interface operation without the use of modal windows, new search capabilities by line, convenient techniques for editing program code - these and other innovations of version 8.3 are discussed in this edition. The authors hope that the book will be useful to everyone who wants to learn how to develop application solutions on the new 1C:Enterprise 8.3 platform.

Who is this book for?

The book is based on a real example of developing an application solution for a small company providing personal services. As you study this book, you will learn basic development techniques in the 1C:Enterprise system, master various areas of business automation, including accounting, payroll, etc.
Why was this particular example chosen? On the one hand, the area of ​​service provision is well known to most of us. One way or another, we are constantly faced with a variety of services. This includes repairing various household appliances, car maintenance, laundry and dry cleaning, hairdressing and beauty services and much more.
On the other hand, the activities of a repair company are well suited for demonstrating the capabilities of 1C:Enterprise. Here there are a variety of services provided to clients, the supply of the company with the necessary materials and their consumption in the provision of services. The work of such an enterprise allows us to consider personnel accounting and payroll calculations. There is an opportunity to illustrate accounting. This variety of activities makes it possible to demonstrate quite broadly the possibilities of generating various reports and summary data based on available information.
The book is addressed primarily to novice developers taking their first steps in developing application solutions. The explanations given in the book are detailed and accessible even to those who are only vaguely familiar with the basics of programming.
If you are just starting to work with 1C:Enterprise or are even completely unfamiliar with this system, but really want to learn, then this book is for you. The purpose of the book is to “guide you by the hand” through the main stages of developing a simple application solution in the 1C:Enterprise system and show that there is nothing inaccessible to a person with intelligence.
For more experienced developers, this book will also be useful and will allow them to recall or study in more detail certain aspects of development.

In this section, we begin a review series of articles that will help you master the “1C: Manufacturing Enterprise Management” configuration.

Introduction

"1C:Manufacturing Enterprise Management 8" is a comprehensive application solution covering the main contours of management and accounting at a manufacturing enterprise. The solution allows you to organize a comprehensive information system that meets corporate, Russian and international standards and ensures the financial and economic activities of the enterprise.

The application solution creates a unified information space for displaying the financial and economic activities of an enterprise, covering the main business processes. At the same time, access to stored information is clearly delineated, as well as the possibility of certain actions depending on the status of employees.

At enterprises of a holding structure, a common information base can cover all organizations included in the holding. This significantly reduces the labor intensity of record keeping due to the reuse of common information sets by different organizations. At the same time, end-to-end management and regulated (accounting and tax) accounting is maintained for all organizations, but regulated reporting is generated separately for organizations.

The fact of a business transaction is registered once and is reflected in management and regulated accounting. There is no need to re-enter information. The means of registering a business transaction is a document, and to speed up the work, mechanisms for substituting “default” data and entering new documents based on previously entered ones are widely used.

In the applied solution, the following ratio of various accounting data is adopted:

• independence of management, accounting and tax accounting data;
• comparability of management, accounting and tax accounting data;
• coincidence of sum and quantitative estimates of assets and liabilities according to management, accounting and tax accounting data, in the absence of objective reasons for their discrepancy.

Data entered by users is quickly controlled by the application solution. Thus, when registering a cash payment, the system will check the availability of funds, taking into account existing requests for their spending. And when registering the shipment of products, the system will check the status of mutual settlements with the recipient of the goods.

The application solution comes with a set of interfaces, which provides each user with priority access to the data and mechanisms of the application solution that he needs.

Regulated (accounting and tax) accounting for organizations is carried out in national currency, while for management accounting for the enterprise as a whole, any currency can be chosen. Different organizations of a single information base may use different taxation systems: in some organizations - a general taxation system, in others - a simplified one; Different tax and accounting policies may be used. In addition, a taxation system in the form of a single tax on imputed income can be applied to certain types of activities of an organization.

In addition to management and regulatory accounting, you can maintain accounting according to international financial reporting standards (IFRS). In order to reduce labor intensity, accounting under IFRS is carried out non-operatively, using translation (recalculation) of data from other types of accounting.

When developing the “1C: Manufacturing Enterprise Management 8” solution, both modern international enterprise management techniques (MRP II, CRM, SCM, ERP, ERP II, etc.) and the experience of successful automation of manufacturing enterprises accumulated by 1C and partner companies were taken into account. community. Specialists from the companies “ITRP” (production management) and “1C-Rarus” (accounting according to IFRS) participated in the design and development of the configuration. On methodological issues of implementing management, financial accounting and reporting according to IFRS, consulting support is provided by the world-famous auditing and consulting company PricewaterhouseCoopers.

The solution "1C:Manufacturing Enterprise Management 8" was developed on the modern technology platform "1C:Enterprise 8". In addition to the platform, the software package includes the “Manufacturing Enterprise Management” configuration.

High reliability and performance of the application solution, scalability, construction of geographically distributed systems, and integration with other information systems are ensured. The internal structure of the application solution is completely open for study and customization to the specific needs of the enterprise.

The 1C company is finalizing and developing the “Manufacturing Enterprise Management” configuration in order to reflect changes in legislation and expand functionality. Ensured prompt updating of installed application solutions. 1C and its partners provide a multi-level technical support system.

"1C: Manufacturing Enterprise Management 8" is the flagship application solution of the 1C company with the widest range of functionality. The general concept of the solution is illustrated by the diagram.

All application solution automation mechanisms can be divided into two large classes:

• mechanisms for maintaining the operational activities of the enterprise; mechanisms for maintaining non-operational accounting.
• Areas belonging to operating activities can be distinguished in each type of accounting (with the exception of accounting under IFRS).

In addition, the application solution is divided into separate subsystems responsible for solving groups of similar problems: a cash management subsystem, a personnel management subsystem, an accounting subsystem, etc. This division is a certain convention that makes it easier to master the application solution. In the current work of users, the boundaries between subsystems are practically not felt.

The latest edition of the Manufacturing Enterprise Management configuration, which is numbered 1.3, clearly demonstrates the advantages of the new version 8.2 of the 1C:Enterprise platform. The configuration can be used in normal application mode, familiar to users of previous editions.

"1C: Manufacturing Enterprise Management 8" can be used in a number of departments and services of manufacturing enterprises, including:

• directorate (general director, financial director, commercial director, production director, chief engineer, human resources director, IT director, development director); economic planning department;
• production workshops;
• production and dispatch department;
• chief designer department;
• chief technologist department;
• chief mechanic department;
• sales department;
• department of logistics (supply);
• marketing department;
• warehouses for materials and finished products;
• accounting;
• Human Resources Department;
• department of labor organization and employment;
• IT service;
• administrative and economic department;
• capital construction department;
• information and analytical department;
• department of strategic development.

It is expected that the implementation of the application solution will have the greatest effect at enterprises with a workforce of several tens to several thousand people, with tens and hundreds of automated workstations, as well as in holding and network structures.

"1C:Manufacturing Enterprise Management 8" provides:

• for the management of the enterprise and managers responsible for business development - ample opportunities for analysis, planning and flexible management of the company's resources to increase its competitiveness; heads of departments, managers and employees directly involved in production, sales, supply and other activities to support the production process - tools , allowing you to increase the efficiency of daily work in your areas;
• employees of the enterprise's accounting services - tools for automated accounting in full compliance with legal requirements and corporate standards of the enterprise.

Production accounting and costs as the main subject of its study

The main component of managing a manufacturing enterprise is production accounting.

Production accounting is a complex and interesting technology, with its own methods and techniques. The task of production accounting is to take into account the entire process of cost transformation: costs change their nature, merge, split, transform in various ways during production, i.e. The subject of production accounting is dynamically changing objects. For example, production accounting gives an answer to the question: what is the cost of a product if its production required a certain amount of incurred cost No. 4, consisting of parts costs No. 1 and No. 2 and fully accounted costs No. 3. Why parts? Because, for example, materials of a certain large volume are purchased, and first you need to calculate what part of this total volume of materials was spent per unit of production. The same applies to many other costs - electricity, etc. In this case, it is necessary to take into account the entire history of the passage of costs through production - from the moment the cost arises in accounting until it is included in the cost price and sold as part of the product, and its occurrence in accounting and inclusion in the cost price may be in different reporting periods.

Installation and launch of the soft starter

To work, we need the 1C 8.2 platform. Release UPP can be taken from any latest edition 1.3.
We will work with the “demo” database. In the database settings, select “Thick client” as the main launch mode. The rest of the settings can be left as default.

For those who are not yet familiar with the 8.2 platform, we will give a brief reference to the term “thick client”.
A thick client in a client-server architecture is an application that provides (as opposed to a thin client) advanced functionality, independent of the central server. Often the server in this case is only a data storage, and all the work on processing and presenting this data is transferred to the client’s machine.
Advantages of a fat client
The thick client has a wide range of functionality, unlike the thin client.
Multi-user mode.
Provides the ability to work even when communication with the server is interrupted.
It has the ability to connect to banks without using the Internet.
High performance.
Flaws
Large distribution size.
Much of the client's performance depends on the platform for which it was developed.
When working with it, problems arise with remote access to data.
Quite a complex installation and configuration process.
The complexity of updating and the associated irrelevance of data.

When launching the installed demo database, select the user “Abdulov”, he has full rights. There is no need to specify a password.

In order to study the UPP, when you first start, redefine the “Abdulov” user interface to “Full”: menu “Users - Users - Administration - Abdulov - double-click to open the Abdulov form - field "Main interface" - Full - button Record and close." Then in the toolbar, click on the “Switch interface” button and select the “Full” option.

On the concepts of “Enterprise” and “Organization”, “Regulated” and Management Accounting.” An enterprise is a collection of all organizations for which records are kept in the database. « Regulated accounting“is determined by the fact that the rules for its conduct are determined by law. " Management Accounting“Each enterprise can have its own; the rules for its operation are not regulated in any way and are determined by the management of a particular enterprise. The configuration of the management accounting system contains a certain vision of how best (more convenient, more visual, more rational) to conduct management accounting, but each specific enterprise may have its own vision of its management due to the fact that there are no uniform rules and standards, and in this case it will need to be modified. In the typical configuration of UPP, management accounting is actually based on the requirements of primarily accounting, while reporting in management accounting is aimed at realizing the need for planning purchases, costs, etc. The implementation of management accounting does not use the principle of double entry, i.e. for example, you can capitalize something “out of nowhere”, and there will be no debt, etc. Regulated accounting conducted for each organization separately. Managerial- partly for the enterprise as a whole.

About international accounting. The introduction stated that it is possible to maintain international records in the UPP. It is worth noting that this option appears only if batch accounting is specified in the accounting policy settings. If (see in the “Accounting Manager” interface in the “Accounting Settings - Accounting Settings” menu) you select advanced cost accounting analytics (instead of batch accounting), then it will not be possible to maintain international accounting.

Terms used, designations of objects that 1C operates and that need to be understood when working with the database

• Directories
• Transfers
• Constants
• Plans for types of calculations
• Characteristic type plans
• Register of information
• Document
• Accumulation register
• Chart of accounts
• Report
• Treatment

Directories

A directory is a collection of different meanings for something. The directory consists of Directory elements. Each value of a directory element is characterized by a given set of parameters. Usually one of the parameters of a directory element is non-repeating - for each element of the directory its value is unique. Typically this is the dictionary element code. Usually the directory is replenished, i.e. You can add new elements to it as you work with the database (there are also directories that are not updated, usually some kind of classifiers downloaded from other places).
Directories are useful because they allow you to fill out documents many times faster, while the element will be named and presented the same everywhere; once you have set the parameters of the element, you can use them wherever needed.

Each directory element is an object that can be referenced from other places. For example, there is such a directory “Counterparties”:


Let's say you need to enter data about the next arrival of goods and services into the database. Instead of writing in the appropriate place the name of the counterparty “InnoTrade LLP” and indicating all its characteristics that may be required in order to process the receipt, it will be enough to select the appropriate element of the “Counterparties” directory.

Or, for example, there is such a reference book - “Currencies”:

Instead of writing the name of the currency and indicating its rate in each receipt, we can simply select the value of the currency directory in the right place:

Information registers

An information register is a type of information storage device that looks very similar to a directory. But unlike a directory, a line in the information register cannot be specified as an object - a register line cannot be referenced, such as, for example, a specific counterparty in the “Counterparties” directory. But in the information register you can store, for example, the history of changes to some element of the directory. For example, the history of changes in the values ​​of elements of the “Currencies” directory is stored in the “Currency Rates” information register:

By storing currency history in the “Currency Rates” register, there is no need to indicate the rate many times for each receipt. The program itself will determine it, if necessary, by date.

Transfers

Enumeration is a special case of a directory. An enumeration is a given fixed set of values ​​for something. Unlike a directory, each enumeration value has no additional parameters.

Constants

A constant is the value of something, usually determined when starting to work with the database once and for all. In particular, accounting policy settings are stored in SCP constants.

Plans for types of calculations

A special type of directory that describes the algorithms for accruals and deductions, and some other information necessary for calculating accruals and deductions.

Characteristic type plans

A special type of directory that describes some additional information that database objects contain.

Documentation

A document is a means of entering data, processing entered data with the ability to take into account existing data and convert existing data, taking into account the input data, into an information database.

Documents can be divided into several types:

• reflecting the fact of economic activity - for example, a registration document in the database of receipt of goods and services (as a result of the document, goods must be posted to the warehouse, a debt must appear to the supplier, VAT must be recorded, transactions must be registered, etc.) or the “Report” document production per shift" (records the fact of production of products, their movement to the warehouse, registers transactions, etc.)
• regulatory documents - documents that carry out actions that must be performed at a given frequency - for example, calculate depreciation or calculate wages, reflect wages in accounting, calculate the cost of production, pay off the cost of production, close the year (with balance sheet reform), distribute materials for production, distribute costs, etc.
• planning documents - registration of the fact of planning of some events, recording of planned indicators (sales plan, production plan, production by shifts, procurement plan, buyer order, supplier order, production order, order for maintenance of fixed assets)
• managers - are entered to control the work of other documents (for example, setting discounts - the document specifies the conditions for granting a discount, so that then, if the buyer reaches these conditions, he is automatically given a discount)
• inventory - documents for clarification, updating balances, for example, balances of work in progress or fixing balances of defective costs (note: in the SCP configuration, inventory documents do not write information in the register, but store it only in themselves).

Accumulation registers

Accumulation registers are the main storage of quantitative and total data in the database. Each of the accumulation registers stores its own specific information. Accumulation registers can be divided into groups according to the type of information stored:

• Fixed assets
• Production
• Stock

Moreover, this data can be stored in different registers depending on the accounting section, for example, the register Defects in production (international accounting), Defects in production (accounting), Defects in production (tax accounting).

From the point of view of the method of storing information, accumulation registers are residual And negotiable.

Residual accumulation registers are designed to store only residuals at any given time. Current registers store data on how the balance has changed over time, i.e. at this moment, so much was received as a result of such and such an action, at that moment, so much was lost as a result of another action. Circulating registers allow you to analyze the history of changes in an amount or quantity over a period of time in the context of certain parameters. For example, a sales register will show how much and for what amount a specific product was sold to which counterparties over a certain period of time.

Information appears in accumulation registers when working with documents, i.e. the documents put it there.

Chart of accounts

A typical UPP configuration contains four charts of accounts (and, accordingly, 4 accounting registers - physically, information on charts of accounts is stored in the corresponding accounting registers):

• Budgeting
• International
• Tax
• Self-supporting

Because In the implementation of management accounting, the principle of double entry is not observed, then a chart of accounts is not needed for it. Accordingly, in the standard configuration of the SPP, a management balance is not formed. To do this, you can either modify the configuration, or, which is preferable, use the budgeting subsystem (it allows you to store very different information, you can create a special scenario “Management Balance Sheet” and, using management accounting data, enter information according to this scenario in order to ultimately obtain a management balance sheet, but more on that later)

The UPP contains information that is stored only on the chart of accounts (for example, information on 80-90 accounts, data on the initial cost of intangible assets, acquisition of intangible assets (account 08.05), Performance of research, development and technological work (account 08.08 ), R&D expenses, part of the costs of the 29th account, etc.), there is also information that is stored only in accumulation registers (everything that relates to planning, orders, reservations, etc.) and there is information stored both on the chart of accounts and in the accumulation register (warehouse accounting, cost accounting, etc.). Note. Examples in brackets are given in the “accounting” section. The same features exist in other types of accounting.

Let's look at an example. Open the document “Receipt of goods and services” - menu “Documents - Purchasing Management - Receipt of Goods and Services”. For example, open the first document. Look at its postings using the icon. Pay attention to what analytics account 10 has: i.e. After the receipt is processed, information about the item and warehouse will be stored on the chart of accounts.

Now look at the movements of the document using the “Go – Document movements by registers” button:

A report on document movements will open. You can collapse the group tree by clicking in the report field and then simultaneously pressing the key combination “Ctrl + Shift + MINUS key in the NumLock keyboard section.” Look at (expand) the group “Accumulation register “Batch of goods in warehouses (accounting)””:

Pay attention to the details circled - this analytics was not on the chart of accounts. But it is on this accumulation register.

There are documents that correct only the entries in the chart of accounts, and there are, so to speak, full-fledged documents that correct all the required information, including advanced analytics in registers.

You need to understand that full-fledged documents record information primarily in registers, and only the extracts of this information required for the balance sheet are written on the chart of accounts. In addition, any calculations required "as you go" always use ledger data, and only the results of these calculations can be recorded as entries on the chart of accounts. Accordingly, if you correct only chart of accounts transactions, this does not mean that everything will get better everywhere on its own, because... nothing will get into the registers with advanced analytics. Those. all work should be carried out in the appropriate, “correct” documents, and not by adjusting entries in the chart of accounts.
If, however, you start manually adjusting the entries in the chart of accounts, you will have to adjust them further - for example, the “Calculation of Costs” document for the coming month will not take into account any transactions adjusted in the chart of accounts, it works with registers and only writes the result to the chart of accounts , - as a result, the amount of work may increase so much that it will become impossible to use the program.
Before using a document, the accountant must understand whether this document adjusts only entries, or whether it corrects information wherever necessary. To check, you can use the report, which was already mentioned above, which opens by clicking the “Go – Document movements by registers” button.

In extreme cases, when the problem cannot be solved with a complete document existing in the database that records information both in the accumulation registers and in the chart of accounts, you should use not only the transaction adjustment document, but also a special document for adjusting the accumulation registers. At the same time, of course, you need to understand well not only what entries should be made on the chart of accounts, but also in which accumulation registers, and how, the information should be corrected so that the adjustment ultimately turns out to be complete - this is a very delicate matter and complex, it is better to trust it only to a very good specialist.

Reports

A report is a means of obtaining information from a database, processed and specially prepared in a form that is understandable, convenient and required by the user. There are a lot of reports in the configuration, they all have their own purpose.

Examples of existing reports:

• Reports generated based on chart of accounts data:
• Turnover balance sheet
• Chess sheet
• Account analysis, etc.

• Regulated reports

In the SCP version 1.3.7.1 configuration, calling the tool for working with regulated reports is not available in the “full interface”. Therefore, in order to find it, switch to the “Accounting and Tax Accounting” interface:

In this interface, the tool for working with regulated reporting is located in the “Accounting” menu:

• Reports based on data from accumulation registers, information registers, directories, etc. (product output, production plans, production defects, analysis of the availability of goods in warehouses, analysis of the availability of funds, etc.). Typically, if a report is generated based on data from one register, its name contains the word “statement”. If a report is generated based on data from several different registers, then the word “analysis” is usually used in the title of the report.

• Custom reports.

For advanced users, there is a mechanism for creating their own reports. We will talk about them in more detail a little later.

Treatments

Processing is a 1C:Enterprise tool with which some program-specified data transformation is performed. Unlike reports, processing writes this converted data to the database. For example, in the “Nomenclature” directory, you need to replace the person responsible for its purchase with S.G. Chugunova. on Ubeikin V.Ya. To do this, you can use the “Group processing of directories and documents” processing:

Fill in the processing fields as follows:

And click on the “Select” button. Then go to the “Processing” tab:

Select “Action” and new value. And click on the “Run” button. As a result, the entire nomenclature to which the responsible purchasing manager was assigned was S.G. Chugunova. There will be a new manager responsible for purchasing.

The configuration also contains special processing that performs some routine actions. For example, calculation of product costs performed according to a schedule.

Principles of working with documents

In this section we will look at the basic principles of working with documents: creation, recording, holding (operational and non-operative, deferred), marking for deletion, deleting documents.

Creating documents

A document can be created in different ways. Let's look at the example of the document “Receipt of goods and services”

Method 1. - using the “Add(Ins)” tool. Creating a new document can be done by clicking on the “Add” icon from the list of documents that opens directly from the main menu of the program. Let's say you want to create a document “Receipt of goods and services”. From the main menu of the program you can open a list of these documents:

Then, in the list of receipts that opens, select one of the methods circled in the figure (they are equivalent, the same thing is done):

As a result of this, a new document “Receipt of goods and services” will open and then you will need to fill in all its fields sequentially (and do not forget about the different tabs of this document - circled in a frame):

Method 2. - using the copy mechanism. Creating a new document can be done by clicking on the “Add by copying” icon:

In this case, the document on which the cursor is positioned in the list of documents will be copied and its copy will open. This copy will already have the document fields filled in. All that remains is to edit them if necessary:

Of course, this method is most often much faster than simply creating a document.

Method 3. - using the input mechanism on the base. You can create a new document from the base document. For example, “Receipt of goods and services” can be created by entering based on the document “Receipt order for goods”. In this case, firstly, the original receipt order for goods will become the basis for the created document “Receipt of goods and services” and secondly, the thus created “Receipt of goods and services” will be automatically filled with data from the basis document. To call the input mechanism on the basis, you need to open the document “Receipt order for goods” and click on the input icon on the basis. Moreover, the same can be done without opening the “Receipt Order for Goods” itself, but directly from the list of “Receipt Orders for Goods”, only by first positioning the cursor on the desired document. See the figure, the input methods on the base are circled:

The created new receipt document will “take” the list of goods from the parent receipt order:

Method 4. - using special treatments. The creation of a new document can be done automatically when some special processing is running. Usually in this case, many documents are created at once (processing is needed to speed up the process when some kind of mass actions or a given sequence of actions are required). This method will be discussed in more detail later.

Recording documents

The document is written to the database when you click the “Write” button. Until this button is pressed in a new document, the document will not be saved in the database, and in the event of some unexpected interruption (for example, a power outage), the unrecorded document will be lost. This is especially important to know when working with documents containing a lot of information, for example, a large tabular part filled out manually. Write down documents often so you don't have to enter data again. At the time of recording a document, no important changes occur in the database that affect other data not related to this document, i.e. when recording, the data is simply saved, and this data is saved only within the document; the information does not go anywhere further yet.

Note. It is at the moment of recording that the document takes its place in the database on the time line among documents of the same type. Let us explain in more detail. Look at the "from" field with the date and time of the document:

When creating a document, the time is not filled, but when recording, it is filled to the nearest second. At the same time, at the same second, documents of the same type can be written down by other users of your database (i.e. suppose that several users of the same database clicked on the “Write” button, each in their own “Goods Receipt” document and services” and it happened at the same second). Each of the recorded documents, despite the same time, will occupy its own position within one second. Those. even within one second on the “time line” of document creation, each document will have its own unique place - it is when the document is recorded that this place is assigned to it.

In general, depending on the type of document, it may be that apart from the recording, nothing else is needed, i.e. the document is intended only for storing data within itself (*see the list of such documents below), but for most types of documents the record is not enough. The fact is that, in general, a document is not the most convenient storage of information; its capabilities in this regard are limited.

*List of documents that are only recorded:

“Act of reconciliation of mutual settlements”, “Power of attorney”, “Document of settlements with the counterparty (manual accounting)”, “Request for information services for the taxpayer”, “Inventory of defects in production” and all other types of inventory, “Unformalized document of the tax authority”, “ Non-formalized taxpayer document”, “Survey”, “Report on shift composition”, “Distribution of questionnaires”, “Calculation of planned production costs”, “Regulated report”, “Register of invoices”, “Invoice for payment to the buyer”, “Invoice for payment to the supplier” ", "Transport connection".

Carrying out documents

As already mentioned, when recording a document, the entered data is simply saved within the document. But for most types of documents, recording is not enough; it is also necessary to conduct it.

Posting a document is a special action that is performed in order to record some information in order to protect it from further accidental modification. In this case, this information can either remain in the document itself (i.e. the document does not make movements somewhere else, for example, in the accumulation register), or be recorded in the form of document movements somewhere: in accumulation registers, information registers, charts of accounts, calculation registers, etc.

That is, documents that do not perform movements anywhere can also be processed. Typically, the point of conducting them is to record some information in a document in order to prevent its further modification. In the typical configuration of UPP version 1.3.7, only two types of documents are carried out, but no movements are performed: “Application for opening accounts” and “Setting item accounting parameters.”

Operational and non-operational processing of documents

Conducting documents can be operative or non-operative.
An operative procedure is one in which the possibility of carrying it out is being checked. What it is?

Let's assume we created and recorded a document that increases the debt of a counterparty. Let's assume that a certain limit on receivables has been established with the counterparty. Let's say a couple of days passed after the document was created and someone entered and posted another document that increases the debt of the same counterparty, and this last document has exhausted the limit of this debt. And here different options for further developments arise.

If the organization still wants prevent release of goods when the counterparty's receivables exceed the balance, we need to check its balance when carrying out. But if we do not change the date, then according to the program the debt will not yet be exceeded - after all, the document that exhausted it was entered later and the balances for mutual settlements for our document recorded earlier will be irrelevant. It is for this purpose that the operational mechanism was introduced - i.e. moving the document to the end of the queue of posted documents, because only in this case can all the necessary checks be performed.

Another way is if it is important for the organization to reflect the fact of a business transaction exactly when it happened. That is, for example, despite the fact that accounts receivable are exceeded, the goods already released and in fact, the client owes more than what was established as acceptable for him. In this case, it is important for us to disable the check and allow it to proceed. Then it would be correct to post the document non-operatively, i.e. without all these checks.

In both cases - both operative and non-operative, all necessary movements of the document will be performed. However, it is important to understand that If carried out non-operatively, there is a high probability of obtaining irrelevant data in the database, in particular due to user errors. Let's look at a simplified example.

Let’s say, according to the program, there are 10 units of some product in the warehouse. Let's say two orders have arrived for the release of this product: for 7 units and for 5 units. Let’s say a document for the release of the first 7 units has been created, but not posted. Then, after some time, a document was posted for the release of 5 units, the balance according to the program data after this release of goods is 5 units. And now it’s time to submit a document for the release of the first 7 units of goods. If the warehouse really doesn’t have seven units, then it’s important for us to try to carry out an operational execution - only in this case the program will perform a check and tell the user that there is a shortage of goods. But what if these 7 units are physically in the warehouse? Those. what to do if you need to reflect the fact of a completed business transaction? As already mentioned, in this case the user needs to process the document non-operatively, no checks will be completed, the document will be processed, the movements will be performed, but according to the program the balance will be minus two units.

As a result, we get a double-edged sword. On the one hand, the user can release the product, because He physically has it. On the other hand, we have irrelevant balances. Those. It is obvious that in reality there cannot be a minus of two units and, most likely, some kind of receipt document has not been carried out.

If all documents were always carried out on time and always promptly, then this would not have happened. But this is a human factor. If data could appear in the program simultaneously with physical changes in the same warehouse... but the data needs to be entered into the program by a person, i.e. this also takes some time.

To update balances, there is a mechanism for re-posting documents. This mechanism is launched only in exclusive mode, i.e. Users will not be able to work with the database at this time. But the longer this is postponed, the larger the chain of documents that needs to be restored and the longer it will take. Therefore, it would be optimal to launch this mechanism quite frequently and regularly.

During operational posting, the document moves in time to the last (current) instant, i.e. defined as last in line.
Of course, the user does not need to specifically track some kind of document queue. This tracking occurs automatically in the program. It is only important for the user to understand that if the program asks a question about whether to carry out the document inoperatively, this means that the recording date of his document does not coincide with the current date, and the user needs to decide whether he agrees to change this date to the current one. To ensure that there is no “conflict of interest in documents”, the user needs to agree to the movement of his document in the queue and still move it quickly. Or the user needs to understand that by agreeing to non-operative processing, the user gives the go-ahead for the possible loss of relevance of the balances (and in this case, sooner or later, it will be necessary to restore the order and update the balances, so it is still better to always try to process the documents promptly).

We already mentioned above that when recording a document, it is assigned some position in the queue of recorded documents. If the recording date is not on the current day, then prompt execution is impossible, even if no other document was created after this document. And first you need to change its date to the current one, or the document will not be processed promptly.

During operational processing, the date no longer changes, only the time of the document changes - it becomes the very last in the queue of documents “on the time line”. As a result of this shift in the queue, it may happen that a document written later than it is, thereby, written before it. However, this does not matter, because... when that document recorded later also begins to be processed, it will in the same way move to the end of the queue - it will move at the moment in time when it will be processed - and it will become the last one.

What will happen then when we launch the mechanism for re-posting all documents in order to update the balances? The program will check the possibility of execution each time and at the moment when, for example, the amount of accounts receivable is exceeded, the execution will stop. And the user will be required to solve this problem: either increase the loan size, or credit some unaccounted advance, or something else... we’ll talk more about the mechanism for re-posting documents later.

In the latest edition of “1C: Trade Management” on platform 8.2, a new methodology for controlling document processing has been implemented: “The mechanism for document processing has been completely redesigned in the configuration. Operational control of the results of the execution is carried out after the formation of the movements, in contrast to edition 10.3 (where control was performed before the execution). This solution made it possible to completely separate the execution logic and control logic, radically simplifying the corresponding program code, which, in turn, is important for facilitating configuration modifications, reducing the number of possible errors, and increasing system performance. If necessary, control is carried out both when reposting retroactively and when canceling the posting of a document. For example, the system will not allow you to cancel an order for the shipment of goods to the extent that it has already been executed.” It can be expected that similar changes will gradually flow into new versions of the SCP.

Postponed processing and further processing of documents

As mentioned earlier, when posting documents, movements are often performed in some kind of data storage - accumulation registers, information registers, etc. In order to perform these movements, documents lock register tables. If at the time of posting our document, when trying to block a register, it turns out that this register is already blocked (that is, at the same moment in time some other document is performing operations with this register), then our document will not be able to block it. He will be forced to wait until the register is free. When posting a document, movements are most often performed in a large number of registers at once. Each of these registers is designed to store some kind of information. As a result, the likelihood that there will be a need to wait until one of them is free is quite high.

Mechanisms for delayed execution and additional execution are needed in order to reduce to a minimum the likelihood of the need for such a wait due to the fact that when they are turned on, movements are not performed immediately in all registers in which it is required, but only in the most “urgent” ones - i.e. . in some registers of operational and management accounting. Then, according to a schedule or manually, the follow-up mechanism is launched, i.e. all other movements are performed.

To enable the deferred posting mechanism, you need to create a “Delayed posting setting”: “Switch interface - Accounting manager - Deferred posting - Document follow-up settings” - Add a new element, specify the name and method, for example, “only requiring follow-up” - Then in the same menu “Delayed posting” - item “List of organizations for deferred posting” - add a new line, indicate the date*, organization and the newly created setting.
*The date indicated is usually regular, i.e. shifts monthly. Those. for more efficient work, you need to shift it monthly to the first day of the current month - then at the end of each month the user working with period end documents will be able to normally complete the documents he needs and complete the period. 1. Carrying out: movements are formed along parts registers
2. Follow-up: forms movements along the rest registers

From a conceptual point of view, follow-up is similar to off-line execution by batch.

Follow-up is carried out:

The mechanism is useful if, when entering and posting primary documents:

• requirements to productivity And parallelism are tough
• movements on all registers are not necessary “right now”
• Some of the information necessary for the formation of movements may be unknown - they will become known later.

The mechanism does not apply to all documents, but only to massive, entered simultaneously by a large number of users.

Deferred posting is not used for documents that:

• are introduced rarely
• it is important to carry out straightaway across all registers

For a list of documents for which deferred posting is applied, see.

How to operate the mechanism

The “Delayed posting of documents” mechanism is optional. Its use is customizable down to the organization in the form. Postponement is valid from the specified date.

How documents will be posted depends on the location of the document date relative to the start date of the deferred posting:

It makes sense to use delayed posting in a period in which intensive input of primary documents occurs. Therefore, it is recommended to set the start date of the deferred posting at the beginning of the month for which the primary documents are entered.

Additional documentation is carried out in accordance with. It can be launched either automatically according to a schedule or manually.

It makes sense to launch additional processing after the end of intensive input of primary documents. Before starting follow-up, you should make sure that you know all the data for reflecting documents in regulated accounting.

If, after completing the additional posting, the data that affects the reflection of documents in regulated accounting has changed (for example, default account settings), you should re-post all the documents. This can be done by selecting the appropriate completion method in.

The follow-up must be completed before the start of regulatory procedures for closing the month (see the diagram of the “closing the month” procedure).

After the intensive entry of documents for the period has been completed and the documents have been processed, it is advisable to move the start date of the deferred posting forward to the beginning of the next month.

Description of the mechanism

Registers, movements along which are formed when posting a document

If delayed posting is used, when posting documents, movements are generated in the same registers as in the “full” posting mode when the “Reflect in ex.” flag is set. accounting". Typically, these registers are used to make operational decisions.

There are features for the “Cost Accounting” register: movements are formed only when posting “production” documents, documents “Receipt of goods and services”, “Advance report”. When posting all other documents, movements in this register are not generated.

When carrying out documents are not formed movements through registers that are not used for making operational decisions:

Sold goods

Sales cost

Postponed incompatible with modes:

• Write-off of batches when posting documents

  Determination of advances when carrying out documents.

These modes are used when

no performance issues

there is no goal to ensure flexibility in accounting

the higher priority is to get “accurate data right away.”

That is, delayed execution is not required when using such modes.

Cancellation of posting (distribution) of documents

After posting a document, you can cancel its posting using the icon

When you cancel posting, the document again becomes available for modification, and all its previously executed movements are deleted (or become inactive). Then the document can be posted again (possibly quickly, with a shift on the time line, or non-operatively, i.e. without changing the date and time).

Deleting documents

In the case when the user decides that, for example, the document he entered is not needed, he can delete it. Documents are deleted using a deletion mark. Then you can run the “Delete marked objects” processing and delete it permanently, but until then the deletion mark can be removed and the document can be restored. This multi-step deletion is also useful because the "Delete Marked Objects" processing performs data control before deletion and protects objects that are used elsewhere in the database from deletion. For example, it would be wrong to directly and immediately delete any counterparty if it is already indicated in some documents, because in this case, the integrity of the data will be violated - such a document will contain a link to some “unknown object”.

In addition, sometimes documents can be deleted “directly”, i.e. straightaway. Usually direct removal is done by processing: when there are , it would be logical that the same processing could delete them.

****************************************************************************************************************************************

The program “1C: Manufacturing Enterprise Management 8.2” was initially created as a universal solution for any type of business, be it manufacturing, trade, services, that is, for a wide variety of sectors of the economy.

In addition to universality, the goal of 1C was to create a finished product that did not require major modifications by programmers. Therefore, this product included a large number of opportunities to ensure the management of commodity, material, financial flows, support the activities of accounting and personnel services, marketing, and for maintaining regulated and internal accounting, etc. This can be judged by the variety of functionality, a large selection of reference books , characteristics, classifiers and settings.

In light of this, we can say that 1C UPP is a multifunctional complex application that has all the necessary tools to ensure the operation of an enterprise of any size. But at the same time, UPP 8.2 is still more focused on medium and large enterprises with a number of employees of several dozen, since due to the developed functionality, the costs of purchasing the product and maintaining accounting with its help are quite high. Therefore, in UPP you can maintain multi-currency accounting for an almost unlimited number of organizations. Developed management accounting has been introduced, along with simultaneous maintenance of regulated accounting, including IFRS. There is end-to-end consolidated accounting for the company (holding).

If we talk about the disadvantages of the solution, they include the lack of a clear structure of modules (as in more modern ERP systems, where you can completely disable unused modules) and a dedicated marketing section. Marketing functions are located in various sections - production management, purchasing, sales and pricing.

Let's consider the capabilities of 1C UPP using the example of a demonstration base in edition 1.3 (version 1.3.97.5). UPP has a standard interface for software products on the 1C:Enterprise 8.2 platform.

Potential features are shown in general informational form in the menu items “Documents”, “Reports” and “Directories”.

Excessive functionality clutters the system, lengthens the time of searching and selecting in the menu, and as a result, slows down the work. The developers have solved this problem. In the 1C UPP configuration, the ability to select a specialized interface is implemented.

In “his” interface, the employee sees only those menu items and settings that are necessary for his work. Even the form of documents will be different for different interfaces.

Typical interface configuration is more consistent with subsystem configuration. If necessary, you can change the interface functionality in accordance with company regulations. You can also define the available interfaces for specific employees and set the default one when entering a database session.

Another feature of 1C UPP is that any document has a setting for selective registration in management, accounting and tax accounting. But this approach requires a clear understanding of all processes in the enterprise.

Let's give a brief overview of the main functional subsystems of 1C UPP.

Manufacturing control

In 1C UPP, much attention is paid to production management, since this product was created specifically for manufacturing companies (but it can also be used where there is no production). The most important thing is that the program can be successfully used for businesses with a complex structure, where there are various production, services, wholesale and retail trade.

Any production begins with planning, and often not with planning production, but sales, and on this basis a production plan is built, and specific deadlines are indicated based on the capacity of the enterprise. Next, shift planning is carried out in detail for the entire product range. The shift production summed up for the period is compared with the enlarged plan, after which the production plan is clarified. Standard planning periods in 1C UPP are day, week, decade, month, quarter, year.

At the same time, the need for materials, raw materials, parts - that is, production resources - is planned, and on this basis the necessary reserves for production, cost planning and procurement planning are calculated. From this, a budget is drawn up by item of expenditure.

1C UPP uses a very well-developed cost accounting system. Costs are classified by type and nature of use. This analytics is used to distribute production costs. An integral part of production are specifications that determine the composition of manufactured products. Based on the specifications, the cost of manufactured products is calculated according to established standards.

In the process of executing the production plan, you can analyze indicators and their deviation from the specified ones, control the consumption of materials and resources, clarify delivery plans, and recalculate costs. And, if necessary, adjust the planning of already launched production.

The plans introduced the concept of a scenario, i.e. obtaining the expected result depending on various parameters and period. Scenarios allow you to create different planning options in the short, medium and long term, as well as when planning sales and purchases.

Procurement management

The subsystem is designed to provide the enterprise with inventory items (TMV) for sale and production needs. The subsystem carries out end-to-end management of orders to suppliers and from buyers, inventory control of goods and materials, and a unified product distribution system is formed. The planning mechanism makes it possible to automatically generate procurement and production calendar plans based on the sales plan. The procurement plan can be generated according to various scenarios depending on the parameters and planning period. Using the built-in assistant, you can automatically create a package of procurement plans on a monthly or quarterly basis according to specified conditions. There is control over the implementation of the plan and the possibility of dynamic adjustments. Implemented flexible pricing by product range, price groups, counterparties, contracts, use of settlement prices, setting a range of base prices, discounts based on various criteria. To analyze purchase prices, data from suppliers and competitors is used. The subsystem has the ability to control mutual settlements with counterparties.

Sales management

The subsystem processes and fulfills customer orders. For pricing, sales planning and inventory control, the same mechanisms (processing, reporting documents) are used as in the procurement management system. The formation of a sales plan can be carried out on the basis of data from previous periods, preliminary orders from customers, and sales forecasts. It is possible to reserve goods based on customer orders, on the basis of which you can form orders for suppliers and for production. You can track orders from customers both by timing and degree of completion. Using specialized reports, analyze sales in various sections, evaluate turnover, profitability, classify goods and rank customers according to various indicators.

Customer Relationship Management (CRM)

The subsystem allows you to save various information on current and potential buyers, maintain a history of interaction with them, evaluate the effectiveness of contacts, track the stages of transactions, register events and remind about upcoming contacts, and classify buyers. The built-in email client speeds up the exchange of information with counterparties. The subsystem is closely related to sales management.

Financial management

This is a subsystem for managing cash flows, planning upcoming receipts, spending money, as well as conducting cash and non-cash payments. There is a mechanism for reserving money through applications for spending money after approval. The approval route is set according to the authority of the employees. You can monitor the movement of finances and record deviations from planned values. Using the payment calendar, you can plan receipts and expenditures for different periods - day, week, decade, month, etc.

The subsystem is designed for long-term planning of the receipt and expenditure of financial resources in various analytical sections, such as organization, project, financial responsibility center (FRC) and others, for a selected time interval. Unlike the financial management subsystem, which records upcoming receipts and expenditures of money, budgeting uses estimated indicators. There are functions for monitoring budget implementation. The subsystem is closely related to production planning, sales and purchases, and payroll calculation.

Personnel management and payroll

A large subsystem with many functions, including maintaining personal data of employees, maintaining personnel records and work and vacation schedules, calculating wages, insurance premiums, personal income tax (NDFL), as well as other charges and deductions. The system records all personnel documents, time sheets, salary slips and payslips. There are opportunities to analyze staffing, motivate employees, monitor employment and staffing needs, manage recruitment, register training and recertify employees, and conduct surveys for job candidates.

Fixed Asset Accounting

A subsystem for maintaining records of fixed assets (FPE), logistics support for departments of the enterprise. Includes accounting, depreciation and maintenance of fixed assets, maintenance plans (schedules), inventory.

Accounting and IFRS

These subsystems responsible for accounting are closely related. The “Accounting” subsystem contains all reporting in accordance with RAS standards (Russian accounting system). There is a full range of standard reports on working with accounting accounts, various tools for analyzing the current state of the enterprise, cost calculation, accounting for the movement of resources and inventory. Registration of all production, purchasing, sales and financial transactions. For correct transformation, there is a setting for matching the accounting and tax accounts. Calculation of all taxes, in particular a large package of tools for VAT accounting, preparation of regulated (tax) reporting.

To cooperate with foreign companies, it is also necessary to maintain accounting according to IFRS (International Financial Reporting System) standards. Due to certain differences in methodology and approaches to accounting, this system is quite different from the Russian standard, despite the fact that there were a number of changes to bring RAS closer to the IFRS standard. Therefore, a separate subsystem has been allocated for accounting according to international accounting rules. There is no automatic end-to-end accounting under IFRS. The information system needs to periodically run processing to translate transactions into IFRS. For correct transfer, you must first set the correspondence of the accounts to RAS and IFRS.

Let's sum it up

1C UPP is a good solution for manufacturing and multidisciplinary businesses that require broad functionality and for which implementation time is critical. The production subsystem is well developed. A mechanism for detailed calculation of costs and their distribution among manufactured products has been introduced. For this purpose, various cost classifiers are initially included and product specifications and product characteristics are used. A powerful mechanism for planning enterprise activities in different areas, taking into account many parameters. In addition, based on 1C UPP 8.2, specialized industry solutions have been developed that are created for specific production.

But 1C UPP 8.2 appeared on the market quite a long time ago, and despite its advantages, it is gradually becoming outdated. Currently, a more modern product “1C:ERP Enterprise Management 2” is actively developing on the technology platform “1C:Enterprise 8.3” with support for new capabilities and services. In this regard, the 1C company decided to remove 1C UPP from the official price lists from April 30, 2018. It will be possible to purchase the product only from 1C partners who have the status “1C: Competence Center for ERP Solutions” upon applications with confirmation of the need for purchase. Support for the product in version 1.3 will continue and a notice of termination of support will be made no less than 3 years in advance, however its cost will gradually increase, and from 01/01/2020 it will double.

Upon expiration of the current 1C:ITS agreement, receiving further support from 1C partners is possible only by purchasing the additional service “Extension of support for the Manufacturing Enterprise Management configuration.”