Accounts receivable management using 1C:Enterprise 8

The main goal of the organization is to generate profit, which is influenced by various factors, one of which is debt to the organization. Accounts receivable are debts owed to an organization from various counterparties (debtors), which are formed in a situation where a product is sold (accepted and this is documented), but payment for it has not been received.

Such debt is a current asset of the enterprise, so it is important to monitor its movement and collect it in a timely manner. The financial stability of the organization depends on the amount of debt, which accordingly increases risks, costs, and, as a result, reduces the profitability and liquidity of working capital. Therefore, it is important to control the debts of counterparties. How to view accounts receivable for 1C users?

General information about accounts receivable

Order No. 34n dated July 29, 1998 regulates the formation of receivables. Such amounts that various counterparties owe our organization (enterprises, individuals, budget, extra-budgetary funds, etc.) can be seen in the organization’s balance sheet in the form of a debit balance for accounts 60, 62, 66, 67, 68, 69 , 70, 73, 75, 76.

Thus, debts can arise as a result of:

  • sale (shipment) of goods subject to deferred payment
  • purchases of products (raw materials) on prepayment
  • when overpaying taxes
  • issuance of accountable amounts to employees

If the taxpayer has a counter-obligation to a counterparty (accounts payable), doubtful debt is recognized as the part of the debt that exceeds the taxpayer's payables to this counterparty.

Expert of the Legal Consulting Service GARANT O. Tkach

Standard reports for analysis of receivables and payables

Subsystem "Reports"

Account balance sheet

The report shows opening and closing balances, as well as turnover for the period for the selected account. We choose account 60 if we want to look at the debt by suppliers, and account 62 if we are interested in balances and turnover of customers.

Subconto Analysis report

For accounts for which analytical accounting is maintained, you can generate a report on analytical accounting objects (sub-accounts). The report is generated both for counterparties as a whole and by groups (buyers, suppliers, founders, etc.). All settings are performed in user mode.

Subsystem “To the Manager”:

This subsystem “1C: Accounting 8” (rev. 3.0) contains analytical reports in a language that any employee can understand – “without debits and credits.”

Report "Debt by suppliers"

The report will show for which counterparty our organization has unpaid obligations or advances (you can group Supplier, Agreement and Document).

Report "Customers' Debt"

Watch video instructions for working with reports >> https://bit-cloud.ru/get/Hj23EjL8ZU

The role of accounts receivable in an organization

Achieving the main goal of the enterprise may not be fully realized due to the growth of accounts receivable. To overcome this problem, each organization must resolve the issue of reducing accounts receivable, primarily related to monitoring its dynamics.

The program used in many enterprises, 1C, allows you to analyze accounts receivable by generating reports for a certain period.

Based on the Chart of Accounts and the Instructions for its use, the debt can be reflected in the following synthetic accounts: 60, 62, 63, 66, 67, 68, 69, 70, 71, 73, 75, 76, etc. At the same time, analytics are carried out for each account for each buyer, supplier, account, etc.

Automatic identification of overdue receivables

Accounting for accounts receivable in the standard functionality of “1C: Accounting 8” depends on a combination of settings such as:

  • keeping records of contracts;
  • setting individual terms for repaying buyers' debts under the contract;
  • formation of reserves for doubtful debts;
  • use of tools for debt adjustment, offset of advances, write-off of debts, etc.;
  • managing deadlines using the document “Invoice for payment to the buyer”, etc.

The program "1C: Accounting 8" (rev. 3.0) implements three ways to indicate the acceptable deadlines for payment of debt by buyers:

Method No. 1. Individual deadlines for fulfilling obligations under the contract

If the company maintains analytical accounting under contracts (Path: subsystem Main >> Functionality menu >> Calculations tab >> the Accounting under contracts flag is selected in the settings), then the repayment period of the debt under the contract can be specified in the contract card with a specific counterparty.

Method No. 2. Single deadline for all buyers

The system allows you to set a single debt repayment period for all buyers.

Path: Administration subsystem >> Accounting parameters >> settings field Deadlines for payment of debt to suppliers, Deadlines for payment of debt by buyers.

Accounts receivable will be considered normal from the moment they arise and as long as they are within the payment period specified in the agreement card. Accounts receivable that are not repaid at the time of payment expiration are considered overdue.

Method No. 3. Individual deadlines for fulfilling obligations on invoices for payment

It is possible to keep records using the document “Invoice for payment to the buyer.” For this purpose, the “Payment by” detail is used - it sets the deadline by which the buyer needs to make payment. If an invoice is not paid on time, the line with this invoice in the invoice journal for payment will be highlighted in red. Paid bills will be highlighted in green. Also, the status of “Paid”, “Partially paid”, “Not paid” will automatically change in invoices, depending on whether payment documents have been entered based on this invoice. If necessary, based on the document “Invoice for payment to the buyer”, you can generate documents for the sale of goods or services.

These methods can be used at the same time. The payment term specified in the contract card with the counterparty has priority. If the payment period is not specified in the agreement, then receivables that are not repaid within the Customer Payment Deadline specified in the Accounting Parameters settings (method No. 2) are considered overdue.

The procedure for characterizing the status of accounts receivable in 1C

In 1C: Accounting it is possible to check accounts receivable. The section “Accounts receivable and payable” includes reporting for the bank, which is filled out automatically and cannot be edited manually, but only by entering documents into the database in the program.

The section details information on each:

  • to the counterparty indicating the TIN
  • agreement with the counterparty
  • debt from the date of occurrence

Debt is also divided according to terms of execution: long-term (over 12 months) and short-term.

The organization must create reserves for doubtful debts if such debt is considered doubtful, which can be automated in 1C.

For example, let’s take account 60 and 62 based on the 1C: Accounting chart of accounts.

In account 60, analytical accounting is kept for suppliers and contractors (sub-account “Counterparties”) and the basis of calculations (sub-account “Contracts”), and each supplier and contractor is an element of the directory “Counterparties”, and the basis of calculations is “Contracts”. By analogy, analytical accounting is maintained for account 62 - for buyers and customers (sub-account “Counterparties”) and the basis of calculations (sub-account “Agreements”), and each supplier and contractor is an element of the directory “Counterparties”, and the basis of calculations is “Contracts”. This complies with the requirements of the Chart of Accounts.

In the “Agreements” directory, debt is divided into short-term and long-term (according to the details “Date of occurrence of the obligation” and “Date of repayment of the obligation”) and here information is generated on accounts to and from counterparties, as well as existing contracts.

To account for debt, use the “Account balance sheet” report:

report setupscore 62.1
field “Type of subconto 1”"Counterparties"
field “Type of subconto 2”"Treaties"

This reflects the initial balances, turnover and final balances of mutual settlements with customers. If the buyer has a debt, you can see the basis for the formation (invoice or agreement). If there is no need to consider turnover by accounts or contracts, then when setting up the report, the “Type of subaccount 2” field remains blank.

CounterpartyAgreement (account)Amount, rub.
LLC "Firm"Invoice No. 01 dated 10/11/202150000,00
IP Valeeva V.V.main contract5000,00
Total55000,00

Based on the data obtained, a conclusion is made about the existence and amount of debt.

Accounts receivable are a quickly realizable asset and it is necessary to evaluate their conversion into cash and take into account the share of bad debts according to the average statistical data of previous periods. For example, the amount of accounts receivable is 200,000.00 rubles, including the unpaid amount - 20,000.00 rubles. The share of unpaid debt in the total amount is 10%. This means that according to the “Turnover balance sheet for account 62.1” the conclusion will be that 10% of the debt has not been paid and it is advisable to create a reserve for the next period.

To monitor the payment schedule and maintain settlement and payment discipline, the “Turnover between sub-accounts” report is used to track the repayment of debt during the period between all sub-accounts. In report settings:

Type of subconto (main)"Counterparties"
"View of subconto (corresponding)""Flow of funds"
"Subconto""Payment to supplier"

The report will show the amounts of repayment of accounts payable by creditors and the repayment procedure. If, when setting up, instead of “Payment to supplier”, “Receipts from buyers” is indicated, then the report will reflect the receipt of funds from buyers.

Additionally, visualization tools are provided in the form of a “Diagram” report: when setting up the report on the “Data” tab, the account 60.1 is indicated, the type of totals is selected (closing balances, credit, amount), and on the “Diagram” tab the parameters for generating the report are set.

To account for debt, it is necessary to carry out an inventory, usually at the end of the period, and makes it possible to identify debt balances. For this purpose, there is a report “Inventory of settlements with counterparties”: Reports – Specialized – Inventory of settlements with counterparties. The unified form INV-17 or a self-developed form can be used, which is checked with a checkbox on the tab and the relevant inventory information is entered into this form. The debt table is filled in automatically based on the available accounting data entered by clicking the “Fill” button (in this case, both the confirmed and the expired date of obligation are indicated). The “Not confirmed” column must be filled in manually.

Thus, the use of reports in 1C makes it possible to regularly monitor and analyze mutual settlements with buyers and suppliers, assess the status of debt and take measures to optimize it.

Accounts receivable management using 1C:Enterprise 8

I'll tell you my story that happened to me.

After buying my new car for about six months in the fall, closer to winter, I was pleasantly surprised to discover that it, it turns out, has a heated function for the side mirrors. This can greatly make life easier for a car enthusiast in frosty weather. Another six months later, it turned out quite by accident that my modest city hatchback could have a hidden button to open the trunk without simultaneously opening all the locks on the four other doors of the car. This is incredibly convenient when you are poking around in the trunk, practically immersed there headlong, and therefore you can easily not notice an intruder next to the driver's door. I continue to make my discoveries to this day, which greatly amuses my friends and acquaintances - more experienced drivers. Another example. I personally know several people who, when buying a mobile phone, did not have a complete understanding of all the functions available in it, and only then discovered what a huge amount of benefits can be obtained from this wonderful benefit of civilization.

What am I leading to with all this? Many years of experience in the IT field allowed me to compile some statistics regarding how aware software users are of the real capabilities of the software product they are using. The statistics are as follows: The vast majority (namely, more than 80%) of companies, when purchasing this or that software, initially have an idea only of the general concept of the solution; at best, they know individual functional blocks (most often this is the functionality for which, actually, the product is purchased). Everything else “remains behind the scenes.”

Of course, at the stage of choosing software, such an approach is completely justified - after all, you can’t immediately try to grasp the immensity. But the problem is that almost half of the users of licensed software never manage to fully “declassify” the rich functionality of the system throughout its entire lifespan. But how much time and money could this or that function save?

There are plenty of reasons for this - both objective and subjective. Modern ERP systems are not so easy to learn; the price for system flexibility is often its complexity, and key users of the system do not always have the opportunity to devote time to study documentation or attend training.

As a result, there are situations when, having invested the Nth amount of money in a project for implementing an information system, after completion of the project the company uses the system’s capabilities not at one hundred percent, but, let’s say, at sixty percent. What about the other forty? Perhaps, with their help, the company will be able to obtain from the information system the necessary data that influences the adoption (or non-acceptance) of a decision that is strategically important for the company. The price of the issue here is very high.

Without knowing about the heating button, I can easily clear the frost from the side view mirrors of the car with a spatula. If I'm not in a hurry. What if I’m late and don’t have time for unnecessary movements? What if it’s minus 30 degrees outside and I still have gloves at home? So it turns out that, in a state of deep frostbite, I arrive at work an hour late. Although you could just press one button. But you had to know exactly where to click.

Shifting the topic closer to the subject of the article, I will inform you that there are “buttons where to press” in “1C: Enterprise 8.0.” (namely, this system will be discussed today) is an incredible amount. The topic of this article is “Management reporting in 1C:Enterprise 8.0. "enables its author to reveal his knowledge in this area on the scale of an entire book (and possibly in several volumes). But knowing how difficult it is for key users of the system to find time to read literature (the lack of time has already been mentioned above, and therefore we will act consistently), today we will choose for discussion only one narrow topic - “Accounts Receivable”.

Companies that work with their customers and clients exclusively on prepayment basis are in the minority in Russia today, and therefore the issue of accounts receivable management is still relevant. What is the total amount of accounts receivable and what does it consist of? How big or small is this figure compared to last month or the same period last year? What is the structure of “receivables” by date of occurrence? Which buyers and customers do not pay for our products? What specific orders (applications), shipments have not been paid for? What are the reasons for non-payment and when can I expect payments? What actions are taken by company employees to recover accounts receivable and how effective are they? These are, perhaps, the questions that company leaders would like to know the answers to.

So, let's see how a company using the 1C:Enterprise 8 software system can get answers to these questions.

Who are our debtors and how much do they owe us?

The figure shows a report that provides information on the amounts of debt of counterparties to the company on a certain date (in our example, at the end of the day on July 31), in the selected currency (in our example, it is USD).

The report is detailed by counterparties - buyers and customers of the company.

As can be seen from the report, the total amount of accounts receivable as of July 31, 2005. is 93,310.83 USD. The list of debtors includes 13 counterparties, and two organizations especially “distinguished themselves” - Zarya and Iskra, whose debt to the company is significantly greater than that of other counterparties. This means that it is these two counterparties that you need to pay special attention to first.

In cases where the list of debtors does not fit on one page, the “Accounts Receivable - Chart” report will help you visually select the counterparties with the largest debt.

In this case, we chose the chart type - “pie volume”, and the data labels - “percentage”. The diagram clearly shows that the debts of the two organizations Zarya and Iskra together actually account for more than 80% (40.81% + 40.93%) of the total amount of receivables, while all other debtors of the company account for only 20%. (The above example seems to correspond to the well-known Pareto principle: 20% of buyers - 80% of receivables).

However, in reality everything is much more interesting. In particular, one of the features is that many companies have several legal entities, and our debtors are no exception. Let's imagine a small holding (let's call it Glavtorg), consisting of a trading house (Trading House LLC), a chain of retail stores (Set Stores LLC) and a manager). Let's assume that each of the holding's legal entities is a buyer of our products and has receivables. The amount of debt of each of Glavtorg's legal entities is not so large as to attract our attention. However, for the holding as a whole, there may be a fairly impressive figure that deserves to be worked on.

In “1C:Enterprise 8.0” it is possible to indicate the parent organization for each counterparty (thus indicating that the counterparty belongs to the holding), and then generate the necessary analytical reporting in the context of holdings. This capability is shown in Figures 3 and 4.

Thus, having received a report on accounts receivable, grouped by the main counterparties, we saw that debtors Zarya and Iskra actually provide 80% of the amount, but the remaining part of the debt is not at all “spread out” among the other counterparties, but falls mainly on the Shopping Center Snowflake. Trade, represented by several legal entities, accounts for 13.45% of “receivables”.

Note that grouping information in reports by parent counterparties is precisely one of those features of 1C:Enterprise 8.0 that not all users of the system are aware of.

Is this a lot or a little? They did the math and shed a few tears...

Having received the amounts of receivables (in general and for each debtor), we will try to draw conclusions regarding these figures. The first thing we need is a comparison with previous periods. Only by analyzing the dynamics of changes in accounts receivable over a certain (preferably long) period of time will we be able to assess how good or bad the situation is today.

The Figure shows a report that compares accounts receivable amounts as of three different dates—August 1, 2005, February 1, 2005 (six months ago), and February 1, 2004 (one and a half years ago). The earliest of the three dates, February 1, 2004, was chosen as the reference time period (the one with which the other two will be compared). The other two periods are compared with the reference.

The report is generated in the management accounting currency (in our example - USD) and is detailed by counterparties. Such detailing makes it possible to look at the dynamics of changes in the volume of “receivables” over a period of time for each debtor we are interested in separately. In our case, the debtor “Zarya” is alarming, the amount of debt has increased sharply over the past six months. A slight increase in debt (by 21.056% compared to February last year) was observed by individual entrepreneur A.P. Bobrov. Neva TD repaid its debt almost completely (99.983%). The bottom eight lines of the report are counterparties whose debt arose relatively recently - in the period from February to July of the current year, because neither as of February 1 of this year, nor as of February 1 of last year, there were no “receivables” for them. This is a relatively “fresh” debt.

In general, it follows from the report that over the past year and a half, the volume of receivables from buyers and customers to the company has grown from 13,421.65 USD to 93,310.83 USD. In percentage terms, the growth is 595% (that is, the debt has increased almost 7 times). Is this situation normal? Yes, this situation can be considered normal if during the analyzed period the company’s revenue also increased 7 times. Generally speaking, it is much more interesting to evaluate the volume of accounts receivable not in itself, but in relation to the company’s revenue. This indicator is calculated by dividing the amount of accounts receivable at the end of the period by the amount of revenue for the period, and is expressed as a percentage. Let's see what the value of the indicator is in our case. The calculation of the indicator is presented in Figure 6. The value of the indicator is more than 70%. Many companies consider the norm to be within 10%. From this point of view, our 71.55% is a catastrophic value, and, of course, the company must take some action aimed at reducing the volume of accounts receivable. And for this it is necessary to understand the reasons for this volume, and then we will form in “1C: Enterprise 8.0.” a number of analytical reports that will help us with this.

But before we go any further, let's go back to Figures 5 and 6 and look at how we were able to get 1C:Enterprise 8.0. reports of exactly this type (I suspect that this is not obvious to all 1C:Enterprise 8.0 users).

How we got the right numbers in the right form or a few words about the “Budgeting” subsystem

The reports presented in Figures 5 and 6 are actually obtained from the Budgeting subsystem. The subsystem is part of the main solution on the 1C:Enterprise 8.0 platform - “Manufacturing Enterprise Management” (abbreviated as “UPP”). The integrated solution "UPP" contains several subsystems: production management, sales management, purchasing management, cash management, budgeting, personnel management, equipment management, accounting, IFRS. It is not always advisable to implement absolutely all subsystems, and therefore the decision about which SCP capabilities will be used by the company is made individually in each specific case, depending on the specifics of the company’s activities and the goals of implementing an information system based on SCP. The decision to implement the “Budgeting” subsystem, as a rule, is made based on the fact that the main capability of the subsystem is the preparation of budgets. However, let’s see what else the “Budgeting” subsystem can do in terms of generating management reporting. Using the “Budgeting” subsystem it is possible to:

  1. Create a forecast balance and a number of other forecast forms, taking into account various options (scenarios) for the future financial condition of the company, analyze forecast data (Figure 7),
  2. Obtain a management balance sheet and other financial reports based on actual data for the selected period, conduct a financial analysis of the data and compare profits with another period (Figure 7),
  3. Compare two or more budgets (in general and item by item) for different periods of time, compare different options (scenarios) of budgets for the same period,
  4. Conduct plan-fact analysis, identify deviations of fact from plan (in absolute values ​​and percentages),
  5. Compare actual data from several periods,
  6. Calculate indicators of any type (using formulas specified by the system user), based on planned (budget) or actual data.

To obtain data on the amounts of receivables for three different dates and compare the amounts with each other (Figure 5), we used the report of the “Budgeting” subsystem, which is called “Comparative analysis of balances on budgeting accounts.” In the report generation parameters settings (called by clicking the “settings” button located in the top panel of the report), we indicate the type of data and dates on the “general” tab as shown in Figure 8.

Next, on the “Selection” tab, you must indicate “Account”, “equals”, then select from the proposed list the account with the name “Customers’ debt, current”.

To get detailed information about debtor counterparties in the report, add the “Counterparty” grouping on the “Groups” tab. Having made all the settings described above and clicking the “Generate” button, we will receive a report exactly as in Figure 5. Of course, in the operational circuit of the 1C:Enterprise 8.0 system (in particular, in the “sales management” subsystem) you can also get information on accounts receivable, and in a variety of analytical aspects. But for a beautiful comparison of data from several periods “with one button,” the capabilities provided by the “Budgeting” subsystem are better suited.

Now let’s return to Figure 6. The form presented in the figure was also obtained through the “Budgeting” subsystem, and specifically using the so-called “financial calculations”. Financial calculations are a flexible tool in the 1C:Enterprise 8.0 system that allows the system user to build financial reports of any type. The user of the system independently sets the structure of the financial calculation - indicates which lines and indicators will be present in the report, and by what formulas the values ​​of these indicators will be calculated (Figure 9). At the same time, you can “pull” data into financial calculations both from the “budgeting” subsystem and from other subsystems - for example, “production management” or “personnel management”. The main thing here is to know where to get the necessary data, and actually writing the formulas itself is not at all difficult. In our example, we took data from the “budgeting” subsystem, since all actual data (including data on revenue for the period and accounts receivable at the end of the period) in our case are reflected in this subsystem.

Let's dive into analytics

So, it's time to start looking into the causes of accounts receivable. In order to make assumptions regarding the reasons for the “receivables”, we will try to “twist” these figures in various analytical sections. Only by analyzing the same situation (number, problem) from several different angles can relatively correct conclusions be drawn. From what angles can we look at “receivables” in the information system “1C:Enterprise 8.0”? It can be viewed, at a minimum, in the following analytical sections:

  1. For counterparties-debtors (we already did this at the very beginning).
  2. By intervals of debt occurrence.
  3. Under agreements concluded with counterparties-debtors.
  4. By types of contracts.
  5. By orders (applications).
  6. By types of orders (applications).
  7. By types of counterparties (in terms of the types of classifications accepted by the company), for example, by geographic regions of the counterparties’ location.
  8. For managers who shipped products (goods, services) to counterparties-debtors.
  9. For the main managers of counterparties-debtors.
  10. By company divisions.

The Figure shows a report providing information on accounts receivable by occurrence interval. Please note that the interval values ​​(number of days) by which the amounts in the report are grouped are not strictly specified by the program, but are entered directly by the system user. Moreover, you can enter and store several options in the system at the same time, and when generating a report, select the desired option.

This opportunity is clearly illustrated in Figure 11 - when generating the report, we introduced a new option for intervals (month, quarter, year, more than a year) and immediately received data on accounts receivable in the context of these periods.

As practice shows, the shorter the period for which the debt arose, the greater the likelihood of the debtor repaying the debt. Of course, there may be exceptions, but in any case, with equal efforts expended by the company to repay the debt, “fresh” debts are usually repaid with much greater success.

Let's do a little calculation based on this assumption. Let’s estimate the chances of receiving a debt for a period of no more than 30 days at 90%, from 31 to 90 days at 80%, from 90 days to 1 year at 60%, and over 1 year at only 20%. The calculation results are presented in Figure 12. From them it follows that first of all it is advisable to work with the counterparty “Iskra”, and secondly with “Zarya” and “Fresh Wind”. And it makes sense to simply write off the debt of such organizations as World of Light, Glavspetsstroy and Neva TD. Prioritization is necessary, because the resources that a company can allocate to work with debtors are not endless. (In fact, all employees of the company cannot deal only with this issue from morning to evening).

The calculation described above and the conclusions that we drew from it are just one example of how you can use the reporting generated in 1C:Enterprise 8.0 for analysis and decision-making.

The next issue we will consider is the analysis of accounts receivable in the context of contracts and orders.

Analysis of accounts receivable in the context of contracts and orders (applications) of buyers

Generally speaking, information about accounts receivable in the context of contracts and customer orders in “1C: Enterprise 8.0” can be obtained from several types of reports, namely: “Mutual settlements with counterparties”, “Debt by counterparties”, “Accounts receivable-diagram”, except In addition, some universal shapes will also work. However, we will deliberately continue to use only one report “Debt by counterparties”, thanks to which we will study the capabilities of the system in terms of various groupings and data selections. In other words, we will see how, based on the same report template, you can get several different forms.

Let's start with the fact that not all information can be included in any report, but only information that satisfies a certain criterion (or several criteria). What we will do now is to select in the contract report only those contracts that were concluded with four specific debtor organizations - “Zarya”, “Snezhinka Trade Center”, “Fresh Wind” and “Morozko”. To do this, in the selection conditions for the counterparty at the top of the report, we will indicate the type of condition - “In the list” and then add to the list those counterparties that interest us.

Data grouping in reports can be done both vertically (by rows) and horizontally (by columns).

In our case, the horizontal grouping is done by counterparties, and the vertical grouping is by counterparties’ agreements.

Thus, we received a beautiful report on accounts receivable in the context of contracts concluded with buyers and customers.

Now suppose that the company has several types of contracts that differ from each other in terms of payment by the buyer for shipped products. It would be logical to analyze under what types of contracts debt arises more often?

There is such a possibility in the system. Agreements in “1C:Enterprise 8.0” can be divided by type, using, for example, the analytical attribute “Type of mutual settlements”.

Further in the “Debt by Contractors” report, it is enough to group the data according to this analytical criterion, and we will immediately receive an answer to our question.

The report on accounts receivable, grouped by type of agreement, is presented in Figure 17.

What follows from the report? What follows is that accounts receivable in the company exist only under two types of contracts. The first is contracts that require payment by the buyer directly upon shipment of products. The second type is contracts for which payment is made by the buyer once a month on the last day, for products shipped during the month.

At the same time, the debt under the first type of agreement is significantly greater than under the second. Perhaps the company should reconsider the terms of contracts with payment upon shipment, since it is precisely for them that debt arises in significant amounts? Or, perhaps, it makes sense not to enter into such agreements at all, but to work with your counterparties on some other terms, thus reducing the likelihood of “receivables” arising in the future. Although, frankly speaking, looking at our report, it is not at all obvious that the cause of all the troubles lies precisely in the contracts.

In this regard, it makes sense that you can “dig” even deeper and see for which orders (applications) the debt arose. I would like to note that such a possibility in the system exists only if in the contracts the attribute of conducting mutual settlements “for orders” is selected, and not “for the contract as a whole.”

To obtain information about the “receivable”, we will use the same report “Debt of counterparties”, but this time in the report settings we will set two groupings by rows - “Counterparty” and “Transaction”. “Transactions” in this case simply mean customer orders.

The counterparty “Morozko” did not pay us for two orders, “Snezhinka” and “Fresh Wind” each have one unpaid order. Unfortunately, we will not be able to detail the debt of the counterparty Iskra by order. It is for the above reason - in the agreement with Iskra, under which the debt arose, the sign of conducting mutual settlements “under the agreement as a whole” is established.

Next, you can conduct an even more in-depth analysis of orders according to various criteria, grouping orders by company divisions, responsible employees and any other information that is present in customer requests. Or isn't even present. For example, let's set our task to find out whether delays in customer payments are in any way related to the quality of the company's products. To accomplish this task, we propose to do the following: based on a customer survey, indicate directly in the orders how the buyer evaluates the quality of the products shipped according to the order, and then group all orders for which there is a “receivable” according to these estimates. And then correlate the information received with the amounts of receivables for orders.

However, when we open the “Buyer’s Order” document in “1C:Enterprise 8.0”, we will not find in it such a field (details) in which we could enter information about the buyer’s assessment of the quality of the products under the order. Does this mean that our task is impossible? Not at all. In “1C:Enterprise 8.0” it is possible to add any additional details called “properties” to documents (and not only documents). Taking advantage of this wonderful opportunity, we came up with a new property, which we called “Customer assessment of product quality by order” and even set possible values ​​for it: “Satisfactory”, “Unsatisfactory”.

After we indicated in the orders how the buyer evaluates the quality of the shipped products, it became possible to obtain a report on receivables of the following type - see Figure 20 (the figure shows both the report itself and its configuration in terms of data groupings):

As follows from the report, non-payments by customers are unlikely to be caused by complaints about the quality of the company's products. Only in one case (an order in the amount of 1,625.00 USD from the buyer “Morozko”) the buyer is clearly not satisfied with the quality of the product, which, of course, may be the reason for the buyer’s non-payment of this order. For other orders, such a conclusion cannot be made.

So why don't they pay?

So why don't they pay? You can, of course, survey the debtors themselves, reflect the survey results in 1C:Enterprise 8.0, and then build a report on orders, grouped by reasons for late payments. For example, in this form (Figure 21):

Of course, it is not always possible to obtain objective data through a survey, but in our example (Figure 21), there is something to think about. In almost half of the cases, debtors cited the reason for non-payment as an agreement on a deferred payment with the sales manager, while the terms of contracts with buyers did not seem to provide for deferrals. A report grouped by the “Responsible” attribute of the “Buyer’s Order” document will help you figure out which employees are showing inappropriate initiative (it is assumed that the employee who is listed as responsible worked with this buyer’s request).

To summarize the above, we note that there are extremely many options for constructing analytical reporting in 1C:Enterprise 8.0. In our example, we worked almost all the time with one single type of report, “Debt of counterparties,” and even then we had not exhausted all its capabilities. In “1C:Enterprise 8.0” (if we talk about the complex solution “Manufacturing Enterprise Management”) there are more than a hundred types of forms of management analytical reporting, in addition there are several universal forms (“balances and turnover”, “list\cross-table”, “diagram universal"), as well as a special tool "report console", which allows you to make a random selection of data from the system. Thanks to this, companies using 1C:Enterprise 8.0 have at their disposal a powerful analytical tool that is useful for all departments of the company. If you learn to use it correctly. And this is not at all as difficult as it might seem at first glance.

Returning to our example on the topic of “accounts receivable”, in conclusion we will consider one more small issue. I really want to know when our debtors plan to repay their debts?

How in “1C:Enterprise 8.0” you can obtain data on planned cash receipts from customers

The Cash Management subsystem, which is part of the 1C:Enterprise 8.0 solution. Managing a Manufacturing Enterprise” makes it possible to plan cash receipts from customers, reflect actual payments and correlate facts with plans.

The Figure shows an example of the “Planned Cash Receipts” report. The report is structured by counterparties. In fact, the presented form is a plan-actual analysis of the receipt of funds from customers. The “receipt” column contains information about how much we plan to receive from the buyer in a given period (in our example, this is the 3rd quarter of 2005). The “expense” column reflects the actual cash receipts from customers for the same period. In the columns “beginning balance” and “final balance” we can see how much of the planned receipts remains to be paid to the buyer (at the beginning and at the end of the period, respectively, in our example - 07/01/2005 and 09/30/2005). If the columns “beginning balance” and “final balance” contain an amount with a minus sign, then it shows how much the buyer’s actual payment exceeded the planned one.

The “planned cash receipts” report can be detailed by customer orders, contracts, departments, specific dates of planned and actual payments, currencies, payment types, etc. — the minimum list of possible options is presented in the Figure.

Thus, having generated the “Planned cash receipts” report, with the necessary analytics and for the required time interval (or at the current moment in time), we will be able to see from whom and for what we expected (or are currently expecting) cash receipts. Of course, we will receive all this information provided that the planned payments are registered in the information system.

In addition to registering planned payments from buyers in the system, we can also strongly recommend registering events (negotiations) with buyers about the return of receivables. Storing such data in the system will allow, based on it, to regularly analyze what efforts the company’s employees make to return receivables (and by comparing the volume of negotiations and the amount of debt returned to the company, also to evaluate what the result of these efforts is). An example of how you can register negotiations with a debtor in 1C:Enterprise 8.0 is shown in Figure 25.

Let's sum it up

So, using the example of working with accounts receivable, we became familiar with some of the capabilities of the 1C:Enterprise 8 software system in terms of generating management reporting.

It is obvious that this system can indeed become a real assistant in the daily work of analysts and managers at all levels in a modern Russian company. The construction of management reporting in 1C:Enterprise 8.0 is based on more than a hundred types of report templates covering several areas - production management, equipment, procurement, logistics, inventory management, sales and CRM, personnel management, financial management: budgeting, management accounting , Russian accounting and IFRS. Each of the templates can, in turn, be flexibly customized by the report user for specific tasks. However, one cannot help but notice that such a powerful tool also requires adequate effort to study it, since not all the capabilities of the system are simple and understandable at first glance. To dive into the topic “Management reporting in 1C:Enterprise 8”, we can recommend visiting the CT center office to familiarize yourself with 1C.

The result of the training will be noticeable - the company will discover new opportunities for analyzing its activities, helping to make the necessary management decisions in a timely manner. In addition, having thoroughly studied the software system, the company provides itself with relative independence from consultants.

Answers to common questions

Question No. 1 : Under the assignment agreement, the organization acquired receivables at nominal value. The debtor is an individual entrepreneur who has ceased business activities (excluded from the Unified State Register of Individual Entrepreneurs). Does the assignee have the right to recognize this debt as bad and include it in non-operating expenses?

Answer : It is important to take into account that the extract from the Unified State Register of Individual Entrepreneurs about the termination of the individual entrepreneur does not apply to the basis for recognizing this debt as bad and writing it off as expenses.

Question No. 2 : The organization switched from UTII to OSNO. In the course of activities on UTII, accounts receivable were formed. Under the new regime, does the organization have the right to create a reserve for debt incurred?

Answer : When switching to OSNO, an organization cannot create a reserve for doubtful debts for previously existing debt.

Rating
( 2 ratings, average 5 out of 5 )
Did you like the article? Share with friends:
For any suggestions regarding the site: [email protected]
Для любых предложений по сайту: [email protected]