Planned recovery equipment, planned recovery method, and planned recovery program

Abstract

To provide a collection schedule assuming device, a collection schedule assuming method, and a collection schedule assuming program with which it is possible to generate assumed collection schedule data at a contact point of time and thereby grasp a funds collection schedule ahead of recording sales.SOLUTION: The present invention acquires contract data in which a bill-to entity, an order amount, and a scheduled collection date are set in association; acquires assumed collection schedule data at contract data acquisition time, in which a bill-to entity, an assumed collection schedule amount, a scheduled collection date, and an individual accounted classification indicating whether or not sales have been recorded are set in association on the basis of contract data; acquires collection schedule table data in which a collection amount and a sales recorded classification indicating whether or not sales have been recorded are set in association for each collection schedule date and for each bill-to entity, on the basis of the assumed collection schedule data; and causes the collection schedule table data to be displayed.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to an estimated collection schedule device, an estimated collection schedule method, and an estimated collection schedule program.

Background Art

[0002] Patent Document 1 discloses a configuration that calculates an estimated collection amount on the issue date of accounts receivable, which is a sales claim generated by sales accounting, and automatically determines an estimated collection date.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in the invention described in Patent Document 1, there is a problem that cash flow simulation cannot be performed before sales accounting, and future cash flow cannot be predicted.

[0005] The present invention has been made in view of the above problems, and an object thereof is to provide an estimated collection schedule device, an estimated collection schedule method, and an estimated collection schedule program that can grasp the estimated collection schedule of funds prior to sales accounting by generating estimated collection schedule data at the time of contract.

Means for Solving the Problems

[0006] To solve the above-mentioned problems and achieve the objective, the collection schedule estimation device according to the present invention is a collection schedule estimation device comprising a storage unit and a control unit, wherein the control unit comprises: contract acquisition means for acquiring contract data set by linking the billing party, order amount, and collection schedule date; assumed collection schedule acquisition means for acquiring assumed collection schedule data set by linking the billing party, assumed collection schedule amount, collection schedule date, and individual accounted classification indicating whether or not sales have been recorded, based on the contract data when the contract data is acquired; and assumed collection schedule acquisition means for acquiring collection schedule table data set by linking the collection amount and sales accounted classification indicating whether or not sales have been recorded for each collection schedule date and each billing party, based on the assumed collection schedule data; and collection schedule display means for displaying the collection schedule table data.

[0007] Furthermore, in the collection schedule estimation device according to the present invention, the control unit further comprises sales acquisition means for acquiring sales data of sales corresponding to the estimated collection schedule data, and collection schedule acquisition means for updating the individually accounted category set in the estimated collection schedule data to "sales accounted" based on the sales data, and acquiring collection schedule data set by linking the billing address, the sales collection schedule amount, and the collection schedule date.

[0008] Furthermore, the collection schedule estimation device according to the present invention is characterized in that the control unit further comprises a billing acquisition means that acquires billing data linked to the billing recipient, billing amount, and collection schedule date based on the collection schedule data, and sets and updates the billing number in the collection schedule data and the collection schedule table data based on the billing data.

[0009] Furthermore, in the collection schedule estimation device according to the present invention, the storage unit further comprises a billing address master set by linking the billing address, collection period, and closing date group which is a group of billing addresses to be billed in a lump sum, and the billing acquisition means acquires the billing data set by linking the billing address, billing amount, and collection schedule date included in the closing date group based on the collection schedule data and the billing address master, and updates the billing number in the collection schedule data and the collection schedule table data based on the billing data.

[0010] Furthermore, in the recovery schedule estimation device according to the present invention, the recovery schedule acquisition means is further characterized in that, when an instruction to change the recovery schedule date set in the recovery schedule data to a changed recovery schedule date is set, it updates the recovery schedule data based on the change instruction and updates the recovery schedule table data based on the recovery schedule data.

[0011] Furthermore, in the collection schedule estimation device according to the present invention, the sales acquisition means acquires installment sales data, which is the installment portion of the sales data, when the sales are recorded in installments; the collection schedule acquisition means acquires collection schedule data, which is set by linking the billing address, the planned collection amount for installment sales, and the planned collection date, based on the installment sales data; based on the collection schedule data, the estimated collection schedule data is divided into estimated collection schedule data for installments and estimated collection schedule data for non-installments; and the individually recorded category set in the estimated collection schedule data for installments is updated to "sales recorded".

[0012] Furthermore, in the recovery schedule estimation device according to the present invention, the contract acquisition means is characterized in that, when the billing address, the order amount, and the scheduled accounting date are set, it determines the recovery schedule date based on the scheduled accounting date and acquires the contract data that has been set by linking the billing address, the order amount, and the scheduled recovery date.

[0013] Furthermore, the method for estimating a collection schedule according to the present invention is a method for estimating a collection schedule to be executed by a collection schedule estimation device comprising a storage unit and a control unit, and is characterized by comprising: a contract acquisition step, which is executed in the control unit to acquire contract data set by linking the billing party, order amount, and collection schedule date; an assumed collection schedule acquisition step, which, when acquiring the contract data, acquires assumed collection schedule data set by linking the billing party, assumed collection schedule amount, collection schedule date, and individual accounted classification indicating whether or not sales have been recorded, based on the contract data, and acquires assumed collection schedule table data set by linking the collection amount and the accounted sales classification indicating whether or not sales have been recorded for each collection schedule date and each billing party; and a collection schedule display step, which displays the collection schedule table data.

[0014] Furthermore, the collection schedule estimation program according to the present invention is a collection schedule estimation program to be executed by a collection schedule estimation device comprising a storage unit and a control unit, characterized in that the control unit executes: a contract acquisition step of acquiring contract data set by linking the billing party, order amount, and collection schedule date; an assumed collection schedule acquisition step of acquiring assumed collection schedule data set by linking the billing party, assumed collection schedule amount, collection schedule date, and individual accounted classification indicating whether or not sales have been recorded, based on the contract data acquired at the time of acquiring the contract data, and based on the assumed collection schedule data, acquiring collection schedule table data set by linking the collection amount and the accounted sales classification indicating whether or not sales have been recorded for each collection schedule date and each billing party; and a collection schedule display step of displaying the collection schedule table data. [Effects of the Invention]

[0015] According to the present invention, even for contracts with long construction periods, it is possible to grasp the approximate expected recovery date at the time of contract signing. Furthermore, according to the present invention, by calculating the expected fund recovery date based on contract data and issuing invoices as they occur without waiting for the monthly closing date, it is possible to perform early fund simulations. Furthermore, according to the present invention, for companies with limited cash flow, it is possible to grasp the expected recovery date at the order stage, enabling them to build a more accurate and earlier financial strategy. Furthermore, according to the present invention, it is possible to perform an expected fund simulation at the time of contract signing. Furthermore, according to the present invention, by calculating the expected sales amount from the contract amount, it is possible to grasp the expected collection month and collection amount without waiting for the invoice closing date, enabling early fund simulations and the implementation of fund plans ahead of schedule. Furthermore, according to the present invention, it is appealing to industries that handle long-term contracts and fixed-term contracts, and by grasping the expected recovery date early, it is useful for understanding the financial status and managing funds. Furthermore, while conventional methods required monthly billing to perform cash flow simulations, this invention makes it possible to perform anticipated cash flow simulations at the time of contract signing. As a result, companies with limited cash flow or those handling long-term contracts can grasp expected revenue recovery earlier at the order stage and develop more accurate financial strategies earlier. [Brief explanation of the drawing]

[0016] [Figure 1] Figure 1 is a block diagram showing an example of the configuration of the device intended for recovery in this embodiment. [Figure 2] Figure 2 shows an example of a billing address master in this embodiment. [Figure 3] Figure 3 is a flowchart showing an example of the processing of the device intended for recovery in this embodiment. [Figure 4] Figure 4 shows an example of the planned recovery process in this embodiment. [Figure 5] Figure 5 shows an example of the planned recovery process in this embodiment. [Figure 6] FIG. 6 is a diagram showing an example of the scheduled recovery assumption process in the present embodiment. [Figure 7] FIG. 7 is a diagram showing an example of the scheduled recovery assumption process in the present embodiment. [Figure 8] FIG. 8 is a diagram showing an example of the scheduled recovery assumption process in the present embodiment. [Figure 9] FIG. 9 is a diagram showing an example of the scheduled recovery assumption process in the present embodiment. [Figure 10] FIG. 10 is a diagram showing an example of the scheduled recovery assumption process in the present embodiment. [Figure 11] FIG. 11 is a diagram showing an example of the scheduled recovery assumption process in the present embodiment. [Figure 12] FIG. 12 is a diagram showing an example of the scheduled recovery assumption process in the present embodiment. [Figure 13] FIG. 13 is a diagram showing an example of the scheduled recovery assumption process in the present embodiment. [Figure 14] FIG. 14 is a diagram showing an example of the scheduled recovery assumption process in the present embodiment. [Figure 15] FIG. 15 is a diagram showing an example of the scheduled recovery assumption process in the present embodiment.

BEST MODE FOR CARRYING OUT THE INVENTION

[0017] Embodiments of the present invention will be described in detail based on the drawings. Note that the present invention is not limited to these embodiments.

[0018] [1. Overview] First, the overview of the present invention will be described.

[0019] In industries that conduct multiple businesses such as product sales, subcontract manufacturing, and metered billing businesses (for example, the IT industry, etc.), there are various cases, large and small, mixed together, and the types of contracts are diverse. At the time of delivery, there are contracts with amount changes depending on sales and subcontracting content, contracts with a metered system and only the unit price determined, etc.

[0020] Therefore, while it was possible to roughly predict sales figures and timing based on contract amounts, it was not possible to determine the expected collection of funds until the end of the month. Furthermore, because cash flow simulations could not be performed until invoices were finalized at the end of the month, it was impossible to foresee future cash flow.

[0021] Therefore, in this embodiment, in order to grasp the approximate recovery schedule at the time of contracting, even for contracts with long construction periods, a mechanism for early financial simulation is provided by achieving two things: calculating the expected fund recovery schedule based on contract data, and issuing invoices each time without waiting for the monthly closing. In this embodiment, the expected fund recovery schedule is calculated based on contract data, and invoices are processed in a batch each time, thereby allowing for the calculation of the confirmed fund recovery schedule early without waiting for the monthly closing.

[0022] [2. Structure] An example of the configuration of the recovery device 100 according to this embodiment will be described with reference to Figures 1 and 2. Figure 1 is a block diagram showing an example of the configuration of the recovery device 100 according to this embodiment.

[0023] As shown in Figure 1, the device 100 intended for collection is a commercially available desktop personal computer. However, the device 100 intended for collection is not limited to stationary information processing devices such as desktop personal computers, but may also be portable information processing devices such as commercially available notebook personal computers, PDAs (Personal Digital Assistants), smartphones, and tablet personal computers.

[0024] The planned recovery device 100 comprises a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. Each part of the planned recovery device 100 is connected to communicate via any communication path.

[0025] The communication interface unit 104 connects the device scheduled for recovery 100 to the network 300 so that it can communicate with the network via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has the function of communicating data with other devices via a communication line. Here, the network 300 has the function of connecting the device scheduled for recovery 100 and the server 200 so that they can communicate with each other, and is, for example, the internet or a LAN (Local Area Network).

[0026] The input / output interface unit 108 is connected to an input device 112 and an output device 114. The output device 114 can be a monitor (including a touch panel), a speaker, or a printer. The input device 112 can be a keyboard, a mouse, a microphone, or a monitor that works in conjunction with a mouse to provide pointing device functionality. In the following, the output device 114 may be referred to as the monitor 114 or printer 114, and the input device 112 may be referred to as the keyboard 112 or mouse 112.

[0027] The storage unit 106 stores various databases, tables, and files. The storage unit 106 also stores computer programs that work in cooperation with the OS (Operating System) to give instructions to the CPU (Central Processing Unit) to perform various processes. The storage unit 106 can be, for example, a memory device such as RAM (Random Access Memory) or ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, or an optical disk. The storage unit 106 includes a billing master 106a and a transaction database 106b.

[0028] The billing address master 106a is a master file where billing addresses are configured. Here, the billing address master 106a may be configured with linked billing addresses, collection dates, and closing date groups, which are groups of billing addresses to be billed in a single batch.

[0029] Now, with reference to Figure 2, an example of the billing address master 106a in this embodiment will be described. Figure 2 is a diagram showing an example of the billing address master 106a in this embodiment.

[0030] As shown in Figure 2, the billing master 106a in this embodiment may have a billing code, billing name, collection month, collection date, and closing date group set.

[0031] Returning to Figure 1, the transaction database 106b stores transaction data. Here, the transaction data may store contract data, projected collection schedule data, collection schedule data, sales data, collection schedule data, invoice data, installment sales data, projected installment collection schedule data, and / or projected non-installment collection schedule data, etc.

[0032] The control unit 102 is a CPU or the like that comprehensively controls the planned collection device 100. The control unit 102 has an internal memory for storing control programs such as the OS, programs that define various processing procedures, and required data, and executes various information processing based on these stored programs. Functionally, the control unit 102 comprises a contract acquisition unit 102a, a planned collection acquisition unit 102b, a collection schedule display unit 102c, a sales acquisition unit 102d, a planned collection acquisition unit 102e, and a billing acquisition unit 102f.

[0033] The contract acquisition unit 102a acquires contract data (order data or recurring contract data). Here, the contract acquisition unit 102a may acquire contract data that is linked to the billing address, order amount, and scheduled collection date. Alternatively, if the billing address, order amount, and scheduled accounting date (scheduled sales date or scheduled billing date) are set, the contract acquisition unit 102a may determine the scheduled collection date based on the scheduled accounting date and acquire contract data that is linked to the billing address, order amount, and scheduled collection date. The contract acquisition unit 102a may also register the contract data in the transaction database 106b. Here, in this embodiment, scheduled date setting data, where the scheduled collection date is a predetermined date after the scheduled accounting date (for example, the end of the following month), may be stored in the storage unit 106.

[0034] The estimated collection schedule acquisition unit 102b acquires estimated collection schedule data, which is set by linking the billing address, estimated collection amount, collection date, and individual accounting classification indicating whether or not the sale has been recorded. Here, the estimated collection schedule acquisition unit 102b may acquire estimated collection schedule data, which is set by linking the billing address, estimated collection amount, collection date, and individual accounting classification indicating whether or not the sale has been recorded, based on the contract data when acquiring contract data, and then acquire collection schedule table data, which is set by linking the collection amount, invoice number, and sales accounting classification indicating whether or not the sale has been recorded, for each collection date and each billing address, based on the estimated collection schedule data.

[0035] The collection schedule display unit 102c displays the collection schedule data.

[0036] The sales acquisition unit 102d acquires sales data. Here, the sales acquisition unit 102d may acquire sales data for sales corresponding to the expected collection data. In addition, if the sales are recorded in installments, the sales acquisition unit 102d may acquire installment sales data, which is the installment portion of the sales data.

[0037] The collection schedule acquisition unit 102e acquires collection schedule data linked to the billing address, sales collection amount, and collection date. Here, the collection schedule acquisition unit 102e may update the individually accounted category set in the assumed collection schedule data to "sales accounted" based on the sales data, and acquire collection schedule data linked to the billing address, sales collection amount, and collection date. Also, if an instruction to change the collection date set in the collection schedule data to a changed collection date is set, the collection schedule acquisition unit 102e may update the collection schedule data based on the change instruction, and update the collection schedule table data based on the collection schedule data. Furthermore, the collection schedule acquisition unit 102e may acquire collection schedule data linked to the billing address, sales collection amount for installments, and collection date based on the installment sales data, split the assumed collection schedule data into assumed collection schedule data for installments and assumed collection schedule data for non-installments based on the collection schedule data, and update the individually accounted category set in the assumed collection schedule data for installments to "sales accounted."

[0038] The billing retrieval unit 102f retrieves billing data for the billing recipient. Here, the billing retrieval unit 102f may retrieve billing data that links the billing recipient, billing amount, and scheduled collection date based on the collection schedule data, and update the billing number in the collection schedule data and collection schedule data based on the billing data. Alternatively, the billing retrieval unit 102f may retrieve billing data that links the billing recipient, billing amount, and scheduled collection date included in the closing date group based on the collection schedule data and the billing recipient master 106a, and update the billing number in the collection schedule data and collection schedule data based on the billing data.

[0039] [3. Specific examples] A specific example of this embodiment will be described with reference to Figures 3 to 15.

[0040] [Expected recovery process] Now, with reference to Figure 3, an example of the planned recovery process in this embodiment will be described. Figure 3 is a flowchart showing an example of the process of the planned recovery device 100 in this embodiment.

[0041] As shown in Figure 3, the contract acquisition unit 102a acquires contract data linked to the billing address, order amount, and scheduled collection date, and registers the contract data in the transaction database 106b (step SA-1).

[0042] Then, the estimated collection schedule acquisition unit 102b acquires estimated collection schedule data, which is set by linking the billing party, estimated collection amount, collection date, and individual recorded sales classification indicating whether or not sales have been recorded, based on the contract data registered in the transaction database 106b when acquiring contract data. Based on the estimated collection schedule data, it acquires collection schedule table data, which is set by linking the collection amount, invoice number, and sales recorded sales classification indicating whether or not sales have been recorded, for each collection date and each billing party (Step SA-2).

[0043] Then, the collection schedule display unit 102c displays the collection schedule data on the output device 114 (step SA-3).

[0044] Then, the sales acquisition unit 102d acquires sales data corresponding to the expected collection data (step SA-4).

[0045] Then, the collection schedule acquisition unit 102e updates the individually accounted category set in the assumed collection schedule data to "accounted for sale" based on the sales data, acquires collection schedule data linked to the billing address, sales collection schedule amount, and collection schedule date, and updates the collection schedule table data based on the collection schedule data (step SA-5).

[0046] Then, the collection schedule display unit 102c displays the collection schedule data on the output device 114 (step SA-6).

[0047] Then, the billing acquisition unit 102f acquires billing data that links the billing recipient, billing amount, and scheduled collection date based on the collection schedule data, and updates the billing number in the collection schedule data and collection schedule data based on the billing data (step SA-7).

[0048] Then, the collection schedule display unit 102c displays the collection schedule data on the output device 114 (step SA-8), and the process ends.

[0049] Here, an example of the planned recovery process in this embodiment will be described with reference to Figures 4 to 15. Figures 4 to 15 are diagrams showing an example of the planned recovery process in this embodiment.

[0050] As shown in Figure 4, in this embodiment, contract data, which is order data for both product sales and contract work, is registered when the user enters an order.

[0051] As shown in Figure 5, in this embodiment, contract data, which is a recurring contract data for usage-based billing, is registered based on the user's input of a recurring contract.

[0052] As shown in Figure 6, in this embodiment, projected collection schedule data is created when the user enters an order and a recurring contract, and the collection schedule data is displayed. Normally, the collection schedule can only be viewed after the sales have been recorded, but as shown in Figure 6, in this embodiment, projected collection schedule data is created from the contract stage, making it possible to plan cash flow for several months in advance.

[0053] As shown in Figure 7, in this embodiment, when the user enters sales data, collection schedule data for the order is generated, the "accounted" checkbox for the estimated collection schedule data is checked, and the collection schedule data is considered correct.

[0054] As shown in Figure 8, in this embodiment, the collection schedule data for the confirmed periodic contract inputs is generated in the batch processing of periodic contract billing, the "accounted" checkbox for the assumed collection schedule data is checked, and the collection schedule data is considered correct. Here, as shown in Figure 8, in this embodiment, the confirmed amount according to the usage amount for metered billing is reflected in the collection schedule data.

[0055] As shown in Figure 9, in this embodiment, the recorded sales data is displayed in the collection schedule from the collection schedule data. Here, as shown in Figure 9, in this embodiment, the usage-based charges are reflected in the confirmed data. In this way, in the collection schedule of this embodiment, the recorded category indicates that acceptance has been completed and that collection is highly likely, making it possible to use this information for cash flow management.

[0056] As shown in Figure 10, in this embodiment, by grouping business partners by closing date group held in the billing master 106a, business partners who perform the initial closing on the 10th of each month are closed all at once, and by performing batch billing processing each time, the billing number in the collection schedule data is updated, making it possible to determine that the transaction has been finalized. In other words, in this embodiment, although the industry operates on a per-transaction closing basis, the collection schedule is finalized by closing bills in the order that have been determined.

[0057] As shown in Figure 11, in this embodiment, the invoice number is displayed in the collection schedule based on the estimated collection data processed for billing. This allows for a more accurate assessment of the collection schedule than at the time of sales recognition, and can be used for cash flow management.

[0058] As shown in Figure 12, in this embodiment, the scheduled collection date is delayed by one month due to the billing party's circumstances. Therefore, the scheduled collection date is changed by the user's input of a change in the scheduled collection date, and the scheduled collection date in the scheduled collection data is changed, but the assumed scheduled collection data remains unchanged.

[0059] Furthermore, as shown in Figure 13, in this embodiment, the results of the changes to the collection schedule are reflected in the collection schedule table, making it possible to use the latest information in the cash flow plan.

[0060] As shown in Figure 14, in this embodiment, the installment payments are recorded as sales when the user enters sales data, and collection data is generated only for the installment payments.

[0061] As shown in Figure 15, in this embodiment, since payments are made in installments, only the installment payments are recorded in the collection schedule, making it possible to use this information for cash flow planning.

[0062] [4. Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This embodiment can contribute to improving operational efficiency and promoting appropriate management decisions by companies, thereby contributing to SDGs Goals 8 and 9.

[0063] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and digital processes, thereby contributing to SDGs Goals 12, 13, and 15.

[0064] Furthermore, this embodiment can contribute to strengthening control and governance, thereby enabling contributions to SDG Goal 16.

[0065] [5. Other Embodiments] In addition to the embodiments described above, the present invention may be implemented in various different embodiments within the scope of the technical idea described in the claims.

[0066] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically by known methods.

[0067] Furthermore, the processing procedures, control procedures, specific names, information including parameters such as registration data and search conditions for each process, screen examples, and database configuration shown in this specification and in the drawings may be changed at will unless otherwise specified.

[0068] Furthermore, with respect to the planned recovery device 100, each component shown in the illustration is a functional concept and does not necessarily have to be physically configured as shown.

[0069] For example, the processing functions of the planned recovery device 100, particularly those performed by the control unit 102, may be implemented in whole or in part by a CPU and a program interpreted and executed by the CPU, or they may be implemented as wired logic hardware. The program is recorded on a non-temporary computer-readable recording medium containing programmed instructions for the information processing device to execute the processing described in this embodiment, and is mechanically read by the planned recovery device 100 as needed. That is, a storage unit such as ROM or HDD (Hard Disk Drive) contains a computer program that works in cooperation with the OS to give instructions to the CPU and perform various processing. This computer program is executed by being loaded into RAM and works in cooperation with the CPU to constitute the control unit.

[0070] Furthermore, this computer program may be stored on an application program server connected to the planned recovery device 100 via any network, and all or part of it can be downloaded as needed.

[0071] Furthermore, the program for executing the processing described in this embodiment may be stored on a non-temporary computer-readable recording medium, or it may be configured as a program product. Here, "recording medium" includes any "portable physical medium" such as memory cards, USB (Universal Serial Bus) memory, SD (Secure Digital) cards, flexible disks, magneto-optical disks, ROMs, EPROMs (Erasable Programmable Read Only Memory), EEPROMs (Registered Trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROMs (Compact Disk Read Only Memory), MOs (Magneto-Optical disks), DVDs (Digital Versatile Disks), and Blu-ray (Registered Trademark) Discs.

[0072] Furthermore, "program" refers to a data processing method described in any language or writing method, regardless of its format, such as source code or binary code. Note that "program" is not necessarily limited to a single, monolithic structure; it also includes distributed structures consisting of multiple modules or libraries, and those that work in cooperation with other programs, such as an operating system, to achieve their functions. Regarding the specific configuration and reading procedures for reading the recording medium in each device shown in this embodiment, as well as the installation procedures after reading, well-known configurations and procedures can be used.

[0073] The various databases stored in the memory unit 106 include memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and website provision.

[0074] Furthermore, the device 100 intended for recovery may be configured as a known personal computer or workstation or other information processing device, or as an information processing device to which any peripheral devices are connected. Alternatively, the device 100 intended for recovery may be implemented by installing software (including programs or data, etc.) on the device that enables the processing described in this embodiment.

[0075] Furthermore, the specific forms of distribution and integration of the devices are not limited to those shown in the figures, and all or part of them can be configured by functionally or physically distributing and integrating them in any unit according to various additions or functional loads. In other words, the embodiments described above may be implemented in any combination, or the embodiments may be implemented selectively. [Industrial applicability]

[0076] This invention is useful in industries such as the IT industry, which often involves long-term contracts; the media industry, which frequently handles contracts lasting from several months to several years; the construction industry, which handles long-term construction and maintenance work; the building maintenance industry, which handles periodic maintenance; and advertising agencies, which handle advertising space. [Explanation of Symbols]

[0077] 100 devices expected to be recovered 102 Control Unit 102a Contract Acquisition Department 102b Estimated Recovery Plan Acquisition Section 102c Collection Schedule Display Unit 102d Sales Acquisition Department 102e Retrieval Schedule Acquisition Section 102f Billing Acquisition Department 104 Communication Interface Section 106 Storage section 106a Billing Address Master 106b Transaction Database 108 Input / Output Interface Section 112 Input device 114 Output device 200 servers 300 Networks

Claims

1. A device for simulating planned retrieval, comprising a memory unit and a control unit, The control unit, A contract acquisition method that creates contract data by linking the billing address, order amount, and scheduled collection date using data entered through contract input, An estimated collection schedule acquisition means creates estimated collection schedule data by linking the billing address extracted from the contract data, the estimated collection amount which is the order amount extracted from the contract data, the estimated collection date extracted from the contract data, and an individual accounted category indicating whether or not the estimated collection amount has been recorded as sales, with the initial setting being "no sales recorded". An estimated collection schedule acquisition means creates an estimated collection schedule table data by linking the collection amount, which is the sum of the estimated collection amounts for each collection date and each billing address extracted from the estimated collection schedule data, and an accounted category indicating whether or not the collection amount has been recorded as sales, with the initial setting being "no sales recorded". A collection schedule display means for displaying the aforementioned collection schedule data, A recovery device characterized by being equipped with the following features.

2. The control unit, A means of acquiring sales data to create sales data for sales that have been recorded, A collection schedule acquisition means that updates the individually accounted category set in the assumed collection schedule data corresponding to the sales data to "sales accounted," and generates collection schedule data that associates the billing address extracted from the assumed collection schedule data, the sales collection amount which is the amount of sales accounted for extracted from the sales data, and the collection schedule date extracted from the assumed collection schedule data, The recovery device according to claim 1, further comprising the following:

3. The control unit, A billing acquisition means creates billing data by linking an automatically assigned slip number, the billing address extracted from the collection schedule data, the billing amount obtained by summing the sales collection schedule amounts for each collection schedule date and each billing address extracted from the collection schedule data, and the collection schedule date extracted from the collection schedule data, and sets and updates the billing number, which is the slip number extracted from the billing data, in the collection schedule data and the collection schedule table data. The recovery device according to claim 2, further comprising the above.

4. The aforementioned storage unit is The billing address master, which is set up by linking the aforementioned billing address, collection period, and closing date group which is the group of billing addresses to be billed in a lump sum, Furthermore, The aforementioned means for obtaining the claim is, The collection schedule estimation device according to claim 3, characterized in that it creates invoice data by linking the automatically assigned slip number, the billing customers included in the closing date group extracted from the billing customer master, the invoice amount obtained by summing the sales collection amount for each collection date and each billing customer extracted from the collection schedule data, and the collection schedule date extracted from the collection schedule data, and sets and updates the collection schedule data and the collection schedule table data with the invoice number, which is the slip number extracted from the invoice data.

5. The aforementioned means for obtaining the planned recovery is, Furthermore, the recovery schedule estimation device according to claim 2, characterized in that, when an instruction to change the recovery schedule date set in the recovery schedule data to a modified recovery schedule date is set, the recovery schedule date in the recovery schedule data is updated with the modified recovery schedule date extracted from the modification instruction, and the recovery schedule table data is updated with the modified recovery schedule date extracted from the updated recovery schedule data.

6. The aforementioned means of obtaining sales is, If the aforementioned sales are recorded as installments, installment sales data, which represents the installment portion of the aforementioned sales data, will be created. The aforementioned means for obtaining the planned recovery is, The collection schedule estimation device according to claim 2, characterized in that it generates collection schedule data set by linking the billing address extracted from the estimated collection schedule data corresponding to the installment sales data, the installment sales collection amount which is the amount recorded for the installment extracted from the installment sales data, and the collection schedule date extracted from the estimated collection schedule data; it divides the estimated collection schedule data into installment

7. The means of obtaining the contract is, The collection schedule estimation device according to any one of 1 to 6, characterized in that, when the billing address, order amount, and scheduled accounting date are set by the contract input, a predetermined date after the scheduled accounting date is determined as the scheduled collection date, and contract data is created that links the billing address, order amount, and scheduled collection date.

8. A recovery schedule simulation method performed by a recovery schedule simulation device comprising a memory unit and a control unit, The control unit is executed as follows: A contract acquisition step creates contract data by linking the billing address, order amount, and scheduled collection date using data entered through contract input. The steps include: creating estimated collection schedule data by linking the billing address extracted from the contract data, the estimated collection amount which is the order amount extracted from the contract data, the estimated collection date extracted from the contract data, and an individual accounted category indicating whether or not the estimated collection amount is recorded as sales, with the initial setting being "no sales recorded"; and creating an estimated collection schedule table data by linking the collection amount, which is the sum of the estimated collection amounts for each collection date and each billing address extracted from the estimated collection schedule data, and an accounted category indicating whether or not the collection amount is recorded as sales, with the initial setting being "no sales recorded". A collection schedule display step that displays the collection schedule data, A method for estimating recovery plans, characterized by including the following:

9. A recovery plan program to be executed by a recovery plan device comprising a memory unit and a control unit, In the control unit, A contract acquisition step creates contract data by linking the billing address, order amount, and scheduled collection date using data entered through contract input. The steps include: creating estimated collection schedule data by linking the billing address extracted from the contract data, the estimated collection amount which is the order amount extracted from the contract data, the estimated collection date extracted from the contract data, and an individual accounted category indicating whether or not the estimated collection amount is recorded as sales, with the initial setting being "no sales recorded"; and creating an estimated collection schedule table data by linking the collection amount, which is the sum of the estimated collection amounts for each collection date and each billing address extracted from the estimated collection schedule data, and an accounted category indicating whether or not the collection amount is recorded as sales, with the initial setting being "no sales recorded". A collection schedule display step that displays the collection schedule data, A program designed to execute the planned recovery process.

Images