Applications for spending money in 1s. Document "Application for payment". Description of the form of the document "Application for payment"

Send this article to my mail

In accounting, an invoice for payment in 1C is a document that an organization presents to a buyer for a delivered product or service in order to inform about the need to deposit funds.

1C presents two options for working with invoices for payment in 1C:

As a document that is stored in the database and the corresponding printed form. It is designed to control mutual settlements with buyers in the system and display relevant information on paper.

A printed form of the Invoice for payment, which is generated from a customer order or a sales document and is needed to be sent to the buyer. You can print it at any time, as well as the displayed form can be saved to your PC in any format.

Which of the above options will be applied depends on the value of the constant Use invoices for payment to customers and is set in the section Master data and Administration → Sales → Wholesales → Payment invoice.

Document Invoice for payment 1C 8.3

Creating an account in 1s 8.3 is possible by entering a new one from the Register of trade documents, as well as entering on the basis, subject to certain conditions

By order of the client, if:

In it, a contract is selected with the order of interaction By orders;

It does not require an agreement, but the agreement specifies the procedure for payment by orders.

An invoice for payment in 1C is created on the basis of the Sale of goods and services if:

The contract is used, which defines the order By waybills;

The contract is not needed, but the agreement contains the rules for settlements by waybills.

An account in 1C 8.3 can be created on the basis of any of the above documents, provided that the rules for mutual settlements with the client are under agreements.

When creating an invoice for payment 1C 8.3, according to the data of any of the specified objects, the workplace "Creating invoices for payment" is intended, it opens in the list by the command Create on the basis.

Two working tabs are presented here: Stages and payments and Invoices for payment. Each assumes its details and performs certain functions.

The first one displays all planned payments provided for by the payment schedule.

Let's explain what chart we are talking about. In an agreement with the client, whether it is individual or standard, you can set a payment schedule, according to which it is necessary to record the receipt of funds in the information system.

For the payment schedule, the name is indicated and the list of stages is filled out. For each stage of the payment schedule, the payment option (advance, prepayment or credit), payment (non-cash or cash), percentage of the total amount (the total of all lines must be equal to 100%), deferral (shift in days from the date of sale) are determined.

Let's take an example. The terms of interaction are established for the client: in order to ship products according to the application, the buyer must make an advance payment in the amount of 50% of the amount of this application, the rest must be paid within 5 days after shipment. All payments are made through the cashier.

The data entry looks like this:

Detailing: By orders;

Form of payment: Cash;

Payment options: prepayment (before shipment) 50% and credit (after shipment) 5 days 50%

According to the schedule set in the agreement, the payment stages are automatically calculated in the document itself (Customer's Order or Sale of Goods and Services). If necessary, they can be manually adjusted using the link in the Payment field and transferred to the document without changing the data in the directory.

The flags in the first column of the tab are set automatically for those lines for which you need to issue an invoice for payment. If the payment for the line has already been made (payment documents have been entered into the database), then the line becomes inactive and the already received amount is displayed in the “Paid” column. An account is created by pressing the button of the same name button. In this case, a new posted invoice will be created, the information in which will be filled in in accordance with the data of the basis document and the amount payable. It will be displayed in the list of accounts on the next tab "Invoices for payment" in the status of Issued.

The new account in 1C contains the following information:

In a hat: on the basis of what it was put up, when, to whom and from whom;

The Payment Stages display the form of payment, bank account and/or cashier and payment schedule;

In Additional, the manager, head, chief accountant are indicated, the purpose of the payment is filled in and, if necessary, additional text is entered for output to the printed form;

You can enter other arbitrary text in the Comment for the convenience of the user.

All created invoices for payment 1C 8.3 are available in the list of accounts in the "Sales" section. You can view all issued invoices for the settlement object using the “Related Documents” report, and open them directly from the report by clicking on the corresponding lines of the report.

You can print out a printable form for a posted account in 1C at any time using the "Print" command, it is also possible to group output of several selected accounts.

Printable form Invoice for payment 1C 8.3

The formation of only the printed form Account for 1C 8.3 without storing it in the database is available from the following system objects:

From a sales order, subject to the following conditions:

It uses a contract with detailed settlements By orders;

The contract is not needed, but in the agreement, the settlement option By orders.

From the sale of goods and services if:

An agreement is used in which mutual settlements are carried out according to invoices;

The contract is not needed, but the agreement specifies the details of invoices.

An account in 1s 8.3 can be generated according to the data of any of the above documents, if they apply the settlement procedure under contracts.

Also, for accounts in 1C, the possibility of withdrawing an invoice with a facsimile is implemented. To do this, facsimile printing must be added to the organization card in the print settings (the method of adding is available at the link "How to create a facsimile?"). A printout of such an invoice for payment in 1C is carried out by selecting the Print command by selecting the appropriate menu item.

Document "Application for payment" is the main tool of the subsystem for managing applications for payments. This document allows you to register in the program the need to transfer cash or non-cash funds to suppliers, employees, tax authorities and other counterparties. In addition, the functionality of the document provides a procedure for agreeing and approving each registered application for payment.

Work with the document is carried out in the journal of applications for payments. The journal is accessed via main menu item "Requests for payments" "Journal of requests for payments", as well as through the items in the control panel of the desktops of the program.

Description of the form of the document "Application for payment"

The document form "Application for payment" contains characteristics (details) that reveal the purpose of the registered payment. At the top of the form there is a block of basic details that define the organization, CFD, type of funds and other mandatory characteristics of the application. The "Purpose of payment" tab contains a list of details that allow you to specify the amount and describe in detail the purpose of the payment. In addition, there are three tabs containing additional information about the planned payment: "Accompanying documents", "Payments" and "Application progress".

Document form "Application for payment"

Basic details

List of basic details:

• Payment term - the deadline by which the application must be paid;
• Transaction - a payment transaction that determines the type of settlements with the counterparty. The requisite is obligatory for filling;
• Article DDS - classifying the registered application for payment in accordance with the classifier of articles adopted in the organization. The requisite is obligatory for filling;
• Organization - the company in which the application is registered. When entering a new document, the attribute automatically takes on the value of the "Main Organization" from the user's personal settings (indicated in the form of the element of the "Users" directory). The requisite is obligatory for filling;
• CFD - a structural unit of the company (department, subdivision, department) responsible for mutual settlements with the counterparty - the recipient of funds;
• Initiator - an individual who is the initiator of a transaction registered for payment. The requisite is an additional characteristic of the application and is used as a selection criterion in the logs and reports of the subsystem;
• Payment method - determines the priority method of payment for the application (cash or non-cash). When entering a new document, the attribute takes on the value "Non-cash";
• Comment - a line of arbitrary comment to the registered application for payment;
• Responsible - the user who registered the application document in the program. The attribute is filled in automatically and is not available for editing.

"Purpose of payment" tab

When registering a document on the "Purpose of payments" tab, you must fill in the following details:

• Counterparty - a legal or natural person who is the recipient of funds, is filled in from the "Counterparties" directory. The requisite is obligatory for filling;
• Agreement - an agreement with a counterparty, under which it is necessary to transfer funds;
• Amount of payment ;
• VAT rate ;
• VAT amountincluded in the payment amount;
• Currency of funds;
• Purpose of payment– payment purpose string that defines the subject of the transaction, i.e. for which you need to transfer money. Purpose of payment can be generated automatically;
• Foundation document number- the number of the document that is the basis for the application (for example, the number of the invoice for payment, the number of the invoice, etc.);
• Date of founding document- date of the document that is the basis for the application;
• A document base- a line of information that characterizes the primary document received from the counterparty and is the basis for the transfer of funds. If the basis for payment is an invoice for payment, the characteristics of the document are filled in manually. This attribute is automatically filled in when entering an application based on the supplier's document (invoice, certificate of completion and other primary documents registered in 1C: Accounting);

"Accompanying documents" tab

The "Accompanying Documents" tab contains a table field intended for attaching all necessary accompanying documents to the application for payment, for example, contracts, additional agreements, invoices for payment, certificates, specifications, etc. Attached documents must be electronic documents of any format. When recording an application, all the documents indicated on the tab are stored in the infobase, which ensures the safety of these documents and the possibility of quick access to them directly from the application form.

Application for payment: tab "Accompanying documents"

List of available props:

• Title of the document- the name of the attached document. When adding a document file, this field is automatically filled with the file name. If necessary, the user can change the specified value;
• Document type - the type of the attached document. This field is not editable and is filled in automatically when a file is selected;

The company can pay the supplier in cash or by transferring funds to the supplier's settlement account (non-cash payment). Payment in cash is made using the document Outgoing cash order.

Non-cash payment (transfer of funds to the supplier's settlement account) is recorded in the document Write-off of non-cash funds.

Documents can be issued on the basis of previously executed documents Receipt of goods and services. The transfer of funds to the supplier's settlement account is executed in two stages: execution and printing of a payment document (outgoing payment order) and registration of the actual transfer of funds from the enterprise's settlement account to the supplier's settlement account (after receiving a bank statement).

This procedure for entering documents can be in the event that the company does not plan receipts and does not control the expenditure of funds. If the enterprise needs to control the expenditure of funds, then the expenditure of funds is made in accordance with the approved application for the expenditure of funds. To implement such a payment option in the program, in the Administration - Organizations and funds section, the Applications for spending funds check box must be checked.

Cash control can only be carried out at certain cash desks or on current accounts. It is possible to define a list of those cash desks and settlement accounts, the expenditure of funds from which will be controlled. This is determined in the card of a particular cash desk or current account.

To control the expenditure of funds, the Applications for the expenditure of funds document is used.

How to plan and coordinate with management the cost of funds.

In order to use the mechanisms for planning and controlling the expenditure of funds, it is necessary that in the section Administration - Organizations and funds the check box for Applications for the expenditure of funds is checked.

There is also a possibility to control the expenditure of funds in accordance with the established limits on the expenditure of funds. To exercise such control, you should set additional checkboxes for limit control in the Administration - Organizations and funds section.

The cash flow limit is set for a month and is detailed to cash flow items (payments to suppliers, salaries, business expenses, etc.). The list of cash flow items can be arbitrarily supplemented by the user (section Finance - Settings and directories - Cash flow items).

It is possible to set limits on the expenditure of funds for each division and for each organization.

It should be noted that if it is not necessary to control the expenditure for any item of cash flow, then it must still be included in the tabular section of the document Expense Limits of the DS, for it the option of control should not be limited. It is possible to automatically fill in the tabular part of the document with all the items of movement on the expenditure of funds or those expenditure limits for the DS that were set in the previous month.

The process of approval and approval of the application consists of the following stages.

• Preparation of the application by the initiator of the payment.
• Approval of applications.
• Approval of applications (preparation of applications for payment).

Preparation of the application by the initiator of the payment.

The application for the expenditure of funds is drawn up by the manager on the basis of the delivery document. An application for spending money can be created from a list or from a document form.

It is also possible to issue one application for several delivery documents or without specifying the settlement document.

In a new application for spending funds, all data from the document on the basis of which the application is made is filled in. The manager controls the correctness of filling in the data in the application, sets the expected date of payment and conducts it. The request is posted in the Not approved status.

The manager can attach printed copies of invoices issued by the supplier, delivery documents or any other documents that confirm the need to spend money to the application. For this, the Attached Files mechanism is used (command on the form navigation panel). If the application must be paid, then the manager can set it to a high priority.

Approval of applications.

The list of uncoordinated applications is submitted for approval to the head of the unit (treasurer, financial director). To approve applications, a separate workplace Applications for Approval is provided (section Finance). Approval of applications will only be possible for those users who have the right (role) Approval of applications for spending funds.

In the list, you can select those inconsistent applications for which the payment deadline is suitable. To do this, in the list, you need to set the selection by the status Not approved and by the date of payment.

You can also separately review applications that have the highest priority and applications for each organization.

When viewing applications, the head of the department (treasurer, financial director) sees in the list all the necessary information about the application: the amount of the application, the recipient, etc. Without opening the list, he can see the justification for the need to spend funds on the application (attached files). To do this, click on the icon.

To approve (reject) several requests for payment, you can select the necessary requests in the list and select the appropriate commands:

• Coordinate applications - if it is necessary to coordinate applications for spending funds;
• Reject requests - if requests for spending money should be rejected.

The request is posted in the Agreed status. When the application is approved, the established limit on the expenditure of funds is controlled. The ability to approve requests over the limit is available to all those users who have the right to approve.

You can organize the approval of the application by several persons. In this case, the application approval process can be organized in the 1C: Document Management program, using the possibilities of joint use of the Trade Management and 1C: Document Management programs.

Approval of applications (preparation of applications for payment).

To approve applications, the user must have an additional role defined - Approval for payment of applications for spending funds. In the application, this role is set for the Treasurer access profile.

Information about approved applications is included in the payment calendar (section Finance).

The amount of agreed payments on applications is displayed in the column All pending.

The financier analyzes the possibility of paying for applications on the specified day in cash or by transferring funds from the current account. The application can be opened directly from the calendar and the date and payment method can be specified for it. That is, in accordance with the available balance of funds in various cash desks and current accounts, the financier determines how best to pay for this application.

Directly from the calendar, you can issue an order to transfer funds (from another cash desk, another current account) or register the expected receipt of funds (receipt of additional loans, credits, etc.).

After specifying the date and method of payment, the financier approves the applications (sets the status For payment for them).

After the final approval of the applications, he checks the possibility of paying for the applications. The amount of approved applications is displayed in the Payable column.

After approval of the application (setting the status For payment), you can draw up a payment document for spending money.

After the application is approved, it is desirable to draw up payment documents indicating the type of payment that was registered in the application. However, other types of payments are also allowed. For example, part of the application can be paid in cash, and part - by transferring funds from the current account.

In the case of cash payments, the Cash Outgoing Order document is drawn up. The application for the expenditure of funds will be shown as a payment order in the list of cash outflow vouchers. To fix the payment, just click on the Pay button. Information in the outgoing cash warrant will be drawn up in accordance with the data of the approved application.

The transfer of funds from the current account is made in two stages:

1. A payment order is drawn up and printed. The payment order is sent to the bank.
2. The actual write-off of funds from the current account is recorded upon receipt of an extract from the bank on the movement of funds on the current account.

How to issue and print a payment document.

In the program, you can issue any type of payment document: Outgoing payment order, transferred letter of credit, transferred collection order, etc. To register all these types of documents, the program uses one document - Write-off of non-cash funds.

Which type of payment document is drawn up for transfer to the bank is determined by the setting of the corresponding type in the Write-off of non-cash funds document.

The list of documents for which payment must be registered is displayed on the For payment page of the list of documents Non-cash payments.

If cash planning is not used (the Requests for spending cash check box in the settings is cleared), then this list will display all those documents for which it is necessary to issue cash expenditures: an order to a supplier, receipt of goods and services, etc.

If mutual settlements with the supplier are carried out as a whole under the contract (without detailing on orders or invoices), then the list will display the amount of debt to the supplier under the contract.

If your enterprise uses cash planning, this list will only display approved cash requests (requests with the status Payable).

To issue a payment document for debiting non-cash funds, click the Pay button. The document Write-off of non-cash DS will be generated. The information in the document will be filled in in accordance with the approved application for spending funds. In the tabular part of the document, the calculation object (Agreement with the supplier, Order for the supplier, Receipt of goods and services) that was specified in the application for spending funds will be filled in.

After posting the document, the amount and currency of mutual settlements are automatically filled in. The currency of mutual settlements is determined by the currency of mutual settlements, which was defined in the settlement object specified in the payment document. In our case, the object of settlements is the receipt document, it indicates the currency of mutual settlements, the ruble, so the amount of mutual settlements will also be fixed in rubles.

The payment document is printed and sent to the bank. For the correct execution of a payment order, you need to carefully check and, if necessary, correct all the details that are presented in the Payment purpose field. To automatically fill in the payment purpose, use the Insert command. Using this command, you can fill in the list of those documents for which you need to register payment (specified in the tabular part of the document as a settlement object).

How to register the fact of transferring funds from the company's current account to the supplier's current account.

After receiving a bank statement with a mark on the transfer of funds from the settlement account of the trade enterprise to the settlement account of the supplier, the check box Posted by the bank is selected in the payment order.

It is possible to set a group mark for the bank to carry out a selected list of payments.

At the time of receipt of the bank statement, the accountant must perform the following steps.

• In the Cashless payments list, set the bank account and period that are specified for payments in the bank statement.
• Click the Unposted by bank button. Only those payments will remain in the list, in which the check mark of the bank is not set.
• Using the Receipt and Withdrawal buttons, register those payments that must be reflected in the bank statement.
• Select the list of all payments and click the Posted by bank button.
• In the dialog box that appears, set the date for making payments by the bank and click OK.

For all marked payments, the Posted by bank checkbox will be selected. To reconcile payments with the received bank statement, the Statement by days report is used, which is called by a hyperlink from the list.

It should be noted that the program provides for the possibility of automatic registration of payments using the "Bank Client" program. The program is launched by clicking the Exchange with a bank button in the Cashless payments list.

Mixed payment is also provided. That is, part of the amount can be paid in cash, and part - by transferring funds to the supplier's settlement account. At the same time, on the basis of an application for spending funds (or a document of receipt), two documents are drawn up: an expense cash warrant and a Write-off of non-cash funds.

Information about payment to a supplier can be obtained from the Accounts payable card report. The report is called from the supplier's card.

How to arrange payment to the supplier in foreign currency by transferring funds to a foreign currency current account.

Registration of such an operation makes sense only if settlements are made with a foreign supplier. The currency in which settlements with the supplier are carried out is determined in the agreement with the supplier. If contracts are not used, then the currency of mutual settlements is determined in the supplier's order or in the receipt document if the order is not placed with the supplier.

Funds must be transferred from the enterprise's foreign currency account to the supplier's foreign currency account.

This operation is executed using the Write-off of non-cash DS document with the subsequent registration of payment (checking the box Posted by the bank) after registering the bank statement. A checking account is selected in the document. It must indicate the currency in which funds must be transferred to the supplier's settlement account. The current account currency may not match the currency in which the documents with the supplier are executed (supplier agreement, supplier order, delivery document). For example, mutual settlements with a supplier are conducted in euros, and funds are transferred in dollars. After registration of such operations, it is necessary to issue a revaluation of foreign exchange funds. A revaluation document is created automatically when you run Month-end closing (Financial section). The program itself determines whether it is necessary to perform revaluation, automatically revaluates settlements with suppliers, calculates the exchange rate difference and allocates it to other income (or expenses).

1. Introduction

Cash planning is one of the main tasks of management accounting, in contrast to accounting.

Of course, there are other significant differences between CM and BU (different requirements for analytics, for valuation and revaluation of assets / liabilities, the need to create reserves, etc.), but the need to solve planning problems is the most difficult of them.
The complexity of planning lies not only in the preparation of a plan (its calculation, formation according to different scenarios), but it is also necessary:

• Perform rescheduling;
• Update plans, transfer adjustments to the next periods;
• Carry out a plan - factual analysis.

It should be recognized that most enterprises (using 1C for automation) do not plan in the program.
"We would have to adjust the accounting .." - so many people argue.

Accounting needs to be adjusted, yes, but not to the detriment of planning.
Of course, planning is still involved (but not in 1C, but in XLS). And the very first, main task (which they are trying to solve) is the planning of funds.

• (1) Strategic (budgeting);
• (2) Operational.

And if budgeting (of course, with a top-down approach to planning) can be done using XLS, then operational planning cannot.
The bottom line is that a minimum of users (1-2 people) most often work with budget tables. For most enterprises, the number of budgeting items, etc. analyst - there are not so many of them. That is, everything can be processed with “handles” in XLS.

But with regard to operational planning for d / s, the situation is different here. That is, there are often a large number of invoices for payment, many regular payments, expected payments for customer orders, etc.

And besides, all this can be "tied" to a large number of primary documents that various users of the program work with, documents are corrected, the situation changes, etc.

Another important difference between operational planning and budgeting is that it often goes “from the bottom up”. That is, from “Applications for consumption d / s”, which are always issued by employees of departments.

And these applications, accordingly, need to be processed in time, accepted / rejected, “put into plan” and paid.

Total: operational planning for d / s is the very first of the planning tasks, which should be automated in "1C" for any enterprise.

And as a result of planning, the finance department / treasury should "see" in the system:

• When, to whom, from which current account / cash desk, for what amount you need to pay;
• What is the d / c balance on “such and such” date, taking into account current balances, planned expenses and d / c receipts. It is necessary to avoid the so-called. "cash gaps".

  That is, there is a need to work with the payment calendar.

• What debt with counterparties will be on the specified dates, taking into account planned payments, receipts and the current balance of mutual settlements.

  That is, there is a need to work with the calendar of calculations.

Purpose of this article - talk about the possibilities of automating operational planning for d / s. At the same time, a comparative analysis of 3 different circulation configurations will be carried out (two are typical from 1C, one is specialized from wiseadvice).

Each of the configurations can be used to solve the tasks of operational planning for c / c, however, a balanced choice should be made based on the scope and scale of your project.

2. Capabilities of SCP 1.3

At the moment, 1C has not yet released the long-awaited, new edition of the SCP (rev. 2). And therefore, we will focus on what is available - the corresponding subsystems of SCP 1.3:

It must be canceled that the subsystem "Applications for the expenditure of funds" was updated in the configuration relatively recently (2011). And as a result, in the managed interface mode, the item "Applications for spending d / s /" appeared in the sections panel.

If you try in a typical configuration, in file mode, open the form of the document "Application for the expense of d / s" (aka, ZRDS), then an error immediately occurs on the variable "GlobalValues" from the general module "Working with CommonVariables".

This kind of error can be corrected, however, as they say: "the sediment remains." That is, there are enough “roughnesses” in the subsystem of the ZRDS UPP.
The ability to issue a WRDS document through a WEB browser is useful, but in practice it will be necessary to think carefully about the simplification and ergonomics of the standard form of the document. This will be especially important for mobile devices.

But as for the payment calendar, then in the thin client mode, remotely via a WEB browser, etc. they won't be able to use it. The reason is that the "Cash Management" subsystem has not been updated for a long time and, in particular, the "Payment calendar" report is not built on a data composition system. And therefore, this report cannot be used in thin clients, there is no possibility to create arbitrary settings for it.

When working with ZRDS, an important place is occupied by the procedure for coordinating and approving applications. Depending on the organizational structure of the enterprise and other business features, the internal procedure for approving applications (approval regulations) can be quite complex (multi-stage, variable, etc.). Thus, for automation, this is not an easy task.

In SCP, the subsystem of coordination and approval is implemented. It provides quite flexible settings.

• Approval is a confirmation of the need to pay for the application. Usually, the approval should go through the heads of departments, managers and other responsible persons of the company.
• The approval is the final confirmation (by the treasurer) that the application will be paid. At the same time, the date of payment must be determined, the current account / cash desk from which payment will be made. Thus, the payment falls into the operational plan (payment calendar).

It must be canceled that a number of points of the typical functionality of the SCP do not provide what is required in the actual implementation of the subsystem.
I will write about these “moments” later, but for now let’s consider what functionality a typical configuration provides.

1. You can enable the use of the application approval mechanism separately, for each organization.

• It is possible to set up the sequence of passing the application along the routes, the hierarchy of routes.

1. At the same time, it should be noted that the hierarchy in the subdivision directory is not taken into account in the application routing mechanisms.
2. It is also necessary to cancel that the coordination and approval is technically built without the use of a business process mechanism.

• At each point, you can specify one / several users, for whom the execution of the application approval will be available. That is, the application can be approved by any of them (who will have time to do it first).

• For each unit, you can assign the corresponding point of the approval route. The bottom line is this: when making an application (ZRDS), the CFD (subdivision) must be indicated. And depending on the specified subdivision, the SCP “finds” the matching point corresponding to it and “sends” a request for approval to this point.

It is also permissible not to specify a department in the coordination route setting. In this case, such an agreement point will be "applied" to all CFDs for which the corresponding route point is not specifically indicated.

1. The coordination itself is carried out using a special processing “Approval of applications”

1. Analysis of the planned availability of funds, payment schedule and tracking of cash gaps is performed in the "Payment Calendar" report.

In addition to the planned consumption of d / s (ZRDS), the planned receipt of d / s can also be taken into account. For these purposes, a special document “Planned receipt of d / s” is provided.

It should be noted that although there are states (prepared, approved, etc.) in the document “Planned receipt of d / s”, but there is no possibility to agree on this document (as well as ZRDS). That is, changing document statuses is possible only in the "manual control" mode.

And yet in the SCP there is an opportunity to take into account the planned receipt of d / s from buyers without issuing documents “Planned receipt of d / s”.

That is, if “Customer Orders” are issued for the buyer, then in a separate report “Payment calendar taking into account orders”, this planned receipt of d / c can be seen.

1. In addition to the "Payment calendar" report, the "Analysis of the availability of funds" report is provided.

At the same time, it is possible to reserve d / c (on applications for expenses) or place applications on account of planned receipts.

There is also the functionality of closing the ZRDS and the planned receipts of d / s. For these purposes, in the "regular client" mode, the documents "Closing applications for spending / receiving d / s" are provided.

However, this functionality is also not supported in thin/web client mode.
Here you need to understand that the "hard reservation" technique is strongly tied to the chronology of entering documents, and this makes adjustments and rescheduling difficult.

Therefore, the functionality is left in the SCP rather as a “legacy of the past”, and a payment calendar should be used to analyze the availability of d / c.

So, the functionality of the SCP was considered and now I will list those moments of a typical configuration that, in practice, on projects, have to be finalized:

1. According to the document "Application for spending d / c":
   1. In the document, you can specify the "Subdivision" (by the way, in the configuration it is designated as the CFR - the center of financial responsibility). But it is quite possible that the application is made from one unit (FSC), and at the same time, the costs will need to be further attributed / distributed to another / other divisions (FSC - financial management centers).

      Possibility to specify DFS, etc. - missing.

      There is no possibility to change the route, redirect the application to other routes.

1. There is no possibility to plan the transfer of cash between settlement accounts, from the account to the cash desk, and so on.
1. Agreement process:
   1. There is an opportunity to coordinate the ZRDS, but there is no possibility to coordinate the planned receipt of d / s.
   2. In practice, it becomes necessary to carry out coordination for other employees. At the same time, the system also needs to record information about “who and for whom completed the coordination”.

      The option of installing several possible executors at one point of agreement is often not suitable, since this executor can be specified at other stages of the agreement. As a result, all this will lead to the fact that in the list of applications for approval, the employee will simultaneously have both main and indirect tasks for approval. Of course, this confuses the user, it is not convenient.

      Summarizing, there is no possibility to coordinate for another performer, the ability to indicate who and for whom has the right to coordinate - is absent.

   3. In the process of approval of applications, when the application moves to the approval of the next one along the route, the functionality of automatic informing (by e-mail) of the next performer, as well as the author of the application, is required.
   4. If the author of the application is already responsible for approval / approval (at any stage of the route!), then it is quite logical that the program would automatically “shorten” the route, redirect the application to the highest available level. However, this is not provided for in the PPP.
   • All of the listed requirements, although not in the typical configuration, nevertheless.

1. Reports, access rights.
   1. The possibility of restricting access to applications only for available authors / performers (coordinators) is in demand; by divisions available to the user.
   2. There is no reporting on control (by days and intervals) of actual and planned debt. This is true for both buyers and suppliers.
   3. Reporting and part of the functionality are not suitable for working in thin / web-client mode.
2. Accounting under regular agreements, contracts.
   1. Often there are situations when it is necessary to regularly pay suppliers. For example, rent payments, etc.

      The UPP does not automate the reflection in the payment calendar, etc. these upcoming expenses. That is, it is necessary to track such payments in the manual control mode and fill out applications for payment, which is inconvenient and time-consuming.

   2. In contracts with buyers, with suppliers, conditions for the percentage of prepayment, payment terms, etc. can be prescribed.

      The UPP does not automatically record all this information and (as a result) automatically reflect it in the payment calendar.

3. Features of UT 11.1

With the release of the new configuration "Trade Management Rev. 11", many new, useful features have appeared for the tasks of operational planning and financial control.
Perhaps the most significant in this part in UT11 (compared to SCP 1.3) is the mechanism for accounting for the payment schedule. This mechanism just "closes" what was sorely lacking - automation of planning / accounting under regular agreements, contracts.

Thus, in UT11 it is possible not to draw up at all (if not necessary, of course) documents for planning expenses and receipts d / c, and at the same time, the payment calendar will be normally formed.

You can cancel that the “typical settings” of the “Payment calendar” report do not really meet expectations (as such, the calendar is not displayed), but in user mode, you can add grouping by “payment date” and the report will be generated in the usual form.

The functionality of the report has been greatly expanded (compared to SCP 1.3) through the use of a data composition system. Now, a report can be generated in a thin / web client, saved in the database and assigned to different users with the settings they need.

In addition to planning the flow and receipt of d / s, UT11 has the functionality of planning the movement of d / s. For these purposes, you can draw up the documents "Order to move d / s".

Compared to UPP 1.3, for the document “Application for spending d / c”, the number of types of business transactions taken into account has increased:

Now it is possible to approve both the documents “Application for spending d/c” and other orders:

To analyze the debt by intervals / terms, the report "Accounts receivable" is provided. If necessary, you can create a debt calendar. To do this, in the user mode, add grouping by payment dates.

Unfortunately, UT11 (as before) does not provide for the possibility of analyzing the debt calendar by supplier. However, finalize UT11 for this task.

To summarize: new methodological solutions "1C" together with the capabilities of the 8.2 platform provide a good basis for automating the tasks of operational planning and control of d / s.

But at the same time, it must be understood that the UT11 configuration is not a complete, ready-made solution for automating the treasury and planning d / s.

• Firstly, in UT11, in a very simplified form, a mechanism for coordinating / approving applications for consumption and other planning documents for d / s is implemented. That is, there are no routing mechanisms, the process of approving applications is reduced to a simple setting of statuses.
• Secondly, in UT11 there is no budgeting subsystem and (as a result) there is no functionality for monitoring requests for planned budgets.

4. WA Opportunities: Financier

Historically, the WA:Financier configuration was developed on the basis of the Treasury Management product.

And at the same time, the new Financier solution from WiseAdvice also includes:

• Budget planning subsystem;
• Contract management subsystem;
• Subsystem for the formation and accounting of actual payments;
• Flexible, customizable mechanism for generating/filling documents based on templates;
• Flexible, customizable subsystem for integration with the client-bank.

Let's consider the main functionality of "WA: Financier" in terms of the treasury - from accounting for the conditions under contracts to the formation of a payment calendar.

1. In the process of approving an application, you can not only approve / reject the document (as is done in the SCP), but other functions are also available: for example, send the document for revision, or request additional information. information.

   This whole process is automated, respectively, reporting on the status of working out the approval of the document is provided.

5. Results

Conclusions:

1. To automate the work of financial departments, treasuries, organizations with complex org. structure the most appropriate solution is "WA: Financier".

   This solution has been developing and evolving for a long time, thus accumulating the specifics and requirements of different Finns. departments and treasuries. The total labor costs for the development of the solution amounted to more than 5000 man/hours.

   The advantage of the WA: Financier solution is its advanced functionality and a large number of program settings mechanisms. Thus, the implementation of this solution is possible in a short time (the so-called "box implementation"), without additional development, programming, etc.

   Since the solution contains mechanisms for two-way exchange with all the main typical configurations, integration into the existing structure (data exchange with the UT, SCP, Complex, Bukh databases) will not be difficult.

2. To automate the financial department / treasury as part of the integrated automation project best fit solution based on SCP.

   At the same time, you need to understand that the functionality of the SCP will require improvements.

   Specificity, requirements fin. departments, treasuries are not embedded in the SCP as deeply as it is done in separate, specialized solutions.

   Thus, the implementation of SCP for these tasks should be performed only as part of an automation project.

3. For large organizations, for automation of the treasury department UT11 does not fit.

   In this decision, firstly, there are no mechanisms for coordination / approval of planning documents.

   Secondly, there is no budgeting subsystem and control over the implementation of budgets during operational planning.

   However, UT11 perfect for automation (including operational planning for d / c) small fin. company departments.

Business process "Coordination and approval of applications for spending funds"

In conditions of a stable financial condition, the company is able to fully and on time fulfill its obligations - in this case, the company does not need to optimize the spending of funds. At the current time, in the conditions of the financial crisis, the mechanism for distributing scarce funds for the obligations of the enterprise is especially relevant.

The process consists of six consecutive steps:

1. The representative of the unit (managers, engineers, etc.) draws up an application for spending money on obligations - advances on contracts and repayment of debts on settlement documents.

2. The head of the department, using convenient tools, checks the applications for correctness and, if necessary, corrects them.

3. The responsible representative of the financial service (financial director, deputy financial director or head of the organization) determines from which current accounts, to whom and in what amount the funds should be transferred.

4. The head of the division distributes the amounts allowed for payment for specific applications (in fact, for obligations - orders, invoices, settlement documents).

5. The accounting department of the enterprise, on the basis of applications approved and allocated for obligations, creates outgoing payment orders.

6. Payment orders are automatically uploaded to the client-bank.

Making applications for spending money

Registration of operations for the expenditure of funds from settlement accounts always begins with the planning of the expenditure of funds - that is, the execution of applications for spending by all departments of the enterprise involved in the process.

Each service of the enterprise draws up an application for the expenditure of funds depending on the purpose of the expense (each purpose of the expense corresponds to a certain type of operation in the document "Application for the expenditure of funds"). As the purpose of the expense, in the case of advance payments, an order to the supplier can be indicated, and in the case of debt repayment, a settlement document.

Thus, the entire planned expenditure of funds for all services must be reflected in the system in the form of applications for the expenditure of funds.

Formation of an application for the expenditure of funds is carried out using the document "Application for the expenditure of funds".

Fig.1.

Checking prepared applications

The head of the department checks the list of applications for spending money issued by subordinates, corrects and sends it to the financial service for approval. To approve the application for spending funds, the document “Approval of applications” is drawn up, in which unfulfilled documents “Application for spending funds” are selected.

Fig.2.

As a result, after verification and adjustment, the head of the department confirms that the completed applications are agreed and ready for consideration by the financial service.

Fig.3.

Approval of applications by the financial service

After each service has prepared - registered in the system - an application for spending funds, the financial director or the responsible person appointed by him makes a decision on their payment (full or partial) on that day. At the same time, a decision can be made both for each individual application, as well as for a combination of them on a certain basis - for example, on payment to a certain counterparty (or under a specific counterparty agreement), or the budget for service applications as a whole is agreed upon.

Fig.4

When deciding on the expenditure of funds, it is necessary to indicate from which current account to send them. When considering applications, the financial director sees the balances of funds on settlement accounts (taking into account planned receipts and previously approved payments) on the “Account balances” tab. By posting the document, the financial director approves the amounts of funds that can be allocated to applications for the expenditure of funds for the service.

Fig.5.

Allocation of approved payments to disbursement requests.

The head of the department, using the document “Distribution of applications”, allocates the amounts approved in general for the service or specifically for counterparties to the applications for spending funds selected by him.

Fig.6

If the approved amount for the application is less than planned, then an application for spending funds is automatically created for the remaining amount, which can be submitted by the head of the unit for approval by the financial service on another day.

Using a set of analytical reports, department employees can analyze the planned, approved and executed amount of payments and the remaining obligations of the department to counterparties.

Registration of operations on the actual expenditure of funds.

After the applications for the expenditure of funds have passed the process of coordination with the financial director, the financial department of the accounting department, on the basis of approved applications, enters the document “Outgoing payment order”. In this case, in the document "Outgoing payment order" all the necessary fields are filled in automatically, the accountant indicates the purpose of the payment (for the printed form of the payment order) and posts the document "Outgoing payment order" without the "Paid" mark.

Created and posted payment orders from 1C are imported into the Client-Bank system.

The next day, upon receipt of an extract from the bank on the transactions performed, the accountant in each payment order indicates the mark “Paid”, and also enters into the system operations for the expenditure of funds that the bank deducted from the current account without acceptance - draws up the documents “Payment order: write-off of funds” and “Payment request received”. In the event that funds are written off without acceptance in favor of counterparties, the relevant services need to select the settlement document of the counterparty for which payment was made and close the application for spending, if it was previously issued.

You can check the executed transactions for the expenditure of funds per day with the statement using the standard processing "Bank statement". In the standard processing "Bank Statement", the specialist can control the balance at the beginning, income, expense, balance at the end of the day for each bank account of the organization in the context of documents. If it is clear from the printout that the document was paid in part, then the user can issue a partial payment directly from processing.

Only after posting the documents on the expenditure of funds with the “Paid” sign, the system writes off funds from the accounts and changes the status of settlements with counterparties.

Configuration options

The solution is intended for software products "1C: Production Enterprise Management 8" and "1C: Trade Management 8".

Cost of work

It is determined individually based on the characteristics of the Customer's configuration.