Debt management device, debt management method, and debt management program

Abstract

To provide a credit management device etc. capable of improving accuracy of managing credit collection.SOLUTION: A credit management device for managing a scheduled collection date of credit to be collected from a transaction destination, can access to transaction destination data including the number of days until accounting corresponding to an accounting basis of the transaction destination, a transaction destination's credit billing closing date, and a transaction destination's credit collection set date, and accounting data including a transaction origin's credit accounting date at a transaction origin. A control unit is configured to: calculate, based on the transaction destination data and the accounting data, an additional accounting date by adding the number of days until accounting to the transaction origin's credit accounting date; determine whether or not the calculated additional accounting date is within the credit billing closing date; and if the calculated additional accounting date is within the credit billing closing date, calculate a collection set date that is set from an accounting month corresponding to the billing closing date as the scheduled collection date of the credit, whereas, if the calculated additional accounting date exceeds the credit billing closing date, calculate a collection set date that is set from an accounting month following the accounting month corresponding to the billing closing date as the scheduled collection date.SELECTED DRAWING: Figure 6

Description

Technical Field

[0001] The present invention relates to a claim management device, a claim management method, and a claim management program.

Background Art

[0002] Conventionally, a claim management device for managing the scheduled collection date of claims has been known (see, for example, Patent Document 1). In the claim management device of Patent Document 1, the scheduled collection date is registered based on the input content of sales.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In Patent Document 1, the scheduled collection date of the claim is registered based on the sales of the transaction source, and it is the scheduled collection date based on the accounting standard of the transaction source. However, since the collection of claims is executed by the payment from the customer, the scheduled collection date often depends on the accounting standard of the customer. Therefore, when the accounting standards of the transaction source and the customer are different, the scheduled collection date registered by the transaction source may be inaccurate, which may hinder the management of claim collection.

[0005] The present invention has been made in view of the above problems, and an object thereof is to provide a claim management device, a claim management method, and a claim management program that can improve the accuracy of claim collection management.

Means for Solving the Problems

[0006] To solve the above-mentioned problems and achieve the objective, the debt management device according to the present invention is a debt management device equipped with a control unit that manages the scheduled collection date of debts to be collected from business partners, and is able to access business partner data including the number of days until recording corresponding to the accounting standards of the business partner, the billing closing date of the business partner's debts, and the collection setting date of the business partner's debts, and accounting data including the trading source's accounting date of the debts at the trading source, and the control unit calculates an added recording date by adding the number of days until recording to the trading source's accounting date of the debts based on the business partner data and the accounting data, determines whether the calculated added recording date is within the billing closing date of the debts, and if the calculated added recording date is within the billing closing date of the debts, calculates the collection setting date set from the accounting month corresponding to the billing closing date as the scheduled collection date of the debts, while if the calculated added recording date exceeds the billing closing date of the debts, calculates the collection setting date set from the accounting month following the month corresponding to the billing closing date as the scheduled collection date.

[0007] In addition, in the debt management device according to the present invention, the control unit may generate collection schedule data that includes the calculated collection schedule date and an accounting flag for the accounting month corresponding to the collection schedule date.

[0008] Furthermore, in the accounts receivable management device according to the present invention, the control unit performs a provisional closing process for the invoice of the accounts receivable, and in the provisional closing process, it determines whether or not it has obtained acceptance data including the date of accounting for the accounts receivable at the trading partner, and if it has obtained the acceptance data, it calculates the collection setting date set from the accounting month corresponding to the date of accounting for the trading partner as the scheduled collection date of the accounts receivable, and if the scheduled collection date calculated from the acceptance data matches the scheduled collection date in the scheduled collection data, it maintains the scheduled collection date in the scheduled collection data and the closing flag, while if the scheduled collection date calculated from the acceptance data differs from the scheduled collection date in the scheduled collection data, it may update the scheduled collection date in the scheduled collection data to the scheduled collection date calculated from the acceptance data and update the closing flag for the accounting month corresponding to the updated scheduled collection date.

[0009] Furthermore, in the debt management device according to the present invention, if the inspection data has not been acquired, the control unit may update the collection setting date, which is set in the accounting month following the month in which the provisional closing of the invoice is performed, as the collection scheduled date in the collection scheduled data, and update the accounting end flag for the accounting month corresponding to the updated collection scheduled date.

[0010] Furthermore, the debt management method according to the present invention is a debt management device equipped with a control unit that manages the scheduled collection date of a debt to be collected from a business partner, and uses business partner data including the number of days until recording corresponding to the accounting standards of the business partner, the billing closing date of the debt for the business partner, and the collection setting date of the debt for the business partner, and accounting data including the trading source recording date of the debt for the debt at the trading source, and calculates an added recording date by adding the number of days until recording to the trading source recording date of the debt based on the business partner data and the accounting data, determines whether the calculated added recording date is within the billing closing date of the debt, and if the calculated added recording date is within the billing closing date of the debt, calculates the collection setting date set from the accounting month corresponding to the billing closing date as the scheduled collection date of the debt, while if the calculated added recording date exceeds the billing closing date of the debt, calculates the collection setting date set from the accounting month following the month following the accounting month corresponding to the billing closing date as the scheduled collection date.

[0011] Furthermore, the debt management program according to the present invention is a debt management program that causes a debt management device equipped with a control unit to execute a debt management method for managing the scheduled collection date of debts to be collected from a business partner, and uses business partner data including the number of days until recording corresponding to the accounting standards of the business partner, the billing closing date of the business partner's debt, and the collection setting date of the business partner's debt, and accounting data including the trading source recording date of the debt at the trading source, and causes the debt management device to execute the following: Based on the business partner data and the accounting data, calculate an added recording date by adding the number of days until recording to the trading source recording date of the debt, determine whether the calculated added recording date is within the billing closing date of the debt, and if the calculated added recording date is within the billing closing date of the debt, calculate the collection setting date set from the accounting month corresponding to the billing closing date as the scheduled collection date of the debt, while if the calculated added recording date exceeds the billing closing date of the debt, calculate the collection setting date set from the accounting month following the month following the accounting month corresponding to the billing closing date as the scheduled collection date. [Effects of the Invention]

[0012] The present invention has an effect of enhancing the accuracy of the management of debt collection.

Brief Explanation of Drawings

[0013] [Figure 1] FIG. 1 is a diagram showing an example of the configuration of a debt management device. [Figure 2] FIG. 2 is a diagram showing an example of customer data. [Figure 3] FIG. 3 is a diagram showing an example of accounting data. [Figure 4] FIG. 4 is a diagram showing an example of collection schedule data. [Figure 5] FIG. 5 is a diagram showing an example of inspection data. [Figure 6] FIG. 6 is a diagram showing an example of a debt management method. [Figure 7] FIG. 7 is a diagram showing an example of a provisional claim processing screen. [Figure 8] FIG. 8 is a diagram showing an example of the transition of collection schedule data for customer T001. [Figure 9] FIG. 9 is a diagram showing an example of the transition of collection schedule data for customer T002. [Figure 10] FIG. 10 is a diagram showing an example of the transition of collection schedule data for customer T003.

Embodiments for Carrying Out the Invention

[0014] Hereinafter, embodiments of a debt management device, a debt management method, and a debt management program according to the present invention will be described in detail based on the drawings. Note that the present invention is not limited by this embodiment.

[0015] [1. Configuration] An example of the configuration of a debt management device 100 according to this embodiment will be described with reference to FIG. 1 and the like. FIG. 1 is a block diagram showing an example of the configuration of the debt management device 100.

[0016] The claims management device 100 manages claims to be recovered from trading partners. For example, it registers the scheduled recovery dates of claims against trading partners. The claims management device 100 is constructed based on a commercially available desktop personal computer. Note that the claims management device 100 is not limited to being constructed based on a stationary information processing device such as a desktop personal computer, and may also be constructed based on a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistants), smartphone, or tablet personal computer.

[0017] The claims management device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. Each part of the claims management device 100 is communicably connected via an arbitrary communication path.

[0018] The communication interface unit 104 communicably connects the claims management device 100 to the network 300 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 a function of communicating data with other devices via a communication line. Here, the network 300 has a function of communicably connecting the claims management device 100 and the server 200 to each other, and is, for example, the Internet or a LAN (Local Area Network). Note that the data stored in the storage unit 106 may be stored in the server 200, for example.

[0019] An input device 112 and an output device 114 are connected to the input / output interface unit 108. As the output device 114, in addition to a monitor (including a home television), a speaker or a printer can be used. As the input device 112, in addition to a keyboard, a mouse, and a microphone, a monitor that cooperates with the mouse to realize a pointing device function can be used. In the following, the output device 114 may be described as the monitor 114, and the input device 112 may be described as the keyboard 112 or the mouse 112.

[0020] The memory unit 106 stores various databases, tables, and files. The memory 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. As the memory unit 106, for example, memory devices such as RAM (Random Access Memory) and ROM (Read Only Memory), fixed disk devices such as hard disks, flexible disks, and optical disks can be used.

[0021] The memory unit 106 stores customer data 106a, accounting data 106b, collection schedule data 106c, and acceptance data 106d, etc.

[0022] Figure 2 shows an example of customer data. Customer data 106a is, for example, information for managing customers. As shown in Figure 2, customer data 106a includes items such as customer code, customer name, closing date (invoice closing date), collection date (collection setting date), customer sales basis, and number of days until recognition, and this information is associated with each other. The customer code is the customer identification code. The customer name is the name of the customer. The closing date is the closing date for invoicing receivables set by the customer, for example, the end of the month. The collection date is the setting date for collection of receivables, for example, the end of the month following the closing date. The customer sales basis is the basis for receivables to be recognized by the customer, for example, the shipment basis, the acceptance basis, etc. The number of days until recognition is the number of days set in association with the customer sales basis, and is set based on the customer sales basis, for example, 0 days, 5 days, 15 days, etc.

[0023] Figure 3 shows an example of accounting data. Accounting data 106b is, for example, sales data that manages the sales of goods from a trading partner. As shown in Figure 3, accounting data 106b includes the fields of sales number, customer, shipping date (internal accounting date), customer order number, and sales amount, and this information is associated with each other. The sales number is a number that identifies the sale of a product. The customer is the same as the customer code in Figure 2 and is a customer identification code. The shipping date is the date the goods were shipped by the trading partner and is the date the account receivable is recorded by the trading partner (trading partner accounting date). The customer order number is a number that identifies the order for goods from the trading partner and is a number assigned to each order. The sales amount is the amount sold in the order.

[0024] Figure 4 shows an example of collection schedule data. Collection schedule data 106c is data that manages the scheduled collection date of accounts receivable. As shown in Figure 4, collection schedule data 106c includes the following fields: sales number, customer order number, customer, company accounting date, scheduled collection date, scheduled collection amount, account end flag, and invoice number, and this information is associated with each other. The sales number, customer order number, customer, and company accounting date are the same as in accounting data 106b in Figure 3. The scheduled collection date is the date on which the accounts receivable is collected, set based on the collection setting date in customer data 106a. The scheduled collection amount is the scheduled collection amount of the accounts receivable corresponding to the sales amount. The account end flag is a flag assigned to the accounting month corresponding to the scheduled collection date. For example, the account end flag has values ​​of "0", "1", and "2", with "0" being for the current month's billing, "1" for the next month's billing, and "2" for the month after next's billing. The invoice number is a number that identifies the accounts receivable to be billed.

[0025] Figure 5 shows an example of acceptance data. Acceptance data 106d is data provided by the customer and indicates that the customer has received the goods. As shown in Figure 5, acceptance data 106d includes the customer, customer order number, accounting date (customer accounting date), and payment amount, and this information is associated with each other. The customer and customer order number are the same as in accounting data 106b and collection schedule data 106c in Figure 3. The accounting date (customer accounting date) is the date the goods were received by the customer and is the date the customer records the liability (customer accounting date). The payment amount is the amount paid to the supplier corresponding to the sales amount.

[0026] Next, referring again to Figure 1, the control unit 102 will be described. The control unit 102 is a CPU, etc., that comprehensively controls the debt management device 100. The control unit 102 has an internal memory for storing control programs such as the OS, programs that define various processing procedures, required data, etc., and executes various information processing based on these stored programs.

[0027] The control unit 102 performs information processing, specifically managing debts based on various data stored in the storage unit 106. As part of its debt management process, the control unit 102 performs tasks such as automatically calculating the scheduled collection date for debts and updating the calculated collection date.

[0028] The following section, [2. Specific Examples of Processing], will provide a detailed explanation of specific examples of processing performed by the control unit 102.

[0029] [2. Specific examples of processing] Here, specific examples of processes performed by the accounts receivable management device 100 will be explained with reference to Figures 2 to 7. Figure 6 is a diagram showing an example of an accounts receivable management method, and Figure 7 is a diagram showing an example of a provisional billing closing processing screen. As shown in Figure 6, the accounts receivable management device 100 performs a process to automatically calculate the scheduled collection date of the accounts receivable. The calculation of the scheduled collection date uses customer data 106a and accounting data 106b.

[0030] In calculating the scheduled collection date, the control unit 102 calculates the added accounting date by adding the number of days until the company's accounting date for the receivable, based on the customer data 106a and accounting data 106b. Note that the calculation process for the scheduled collection date described below is a process that is executed as of November 2022, and is executed, for example, when registering the scheduled collection date. Specifically, in Figure 6, the customer associated with sales numbers "U001" and "U002" in accounting data 106b is "T001". Therefore, the control unit 102 adds "0 days", which is the number of days until accounting in customer data 106a as shown in Figure 2, to the shipping date of sales number "U001" (22 / 11 / 25) and the shipping date of "U002" (22 / 11 / 29) in accounting data 106b. As a result, the control unit 102 calculates "22 / 11 / 25" as the date for adding "U001" and "22 / 11 / 29" as the date for adding "U002". Similarly, in Figure 6, the control unit 102 determines that the customer associated with sales numbers "U003", "U004", and "U005" in the accounting data 106b is "T002". Therefore, the control unit 102 adds "5 days", which is the number of days until accounting in the customer data 106a shown in Figure 2, to the shipping date of sales number "U003" (22 / 11 / 24), the shipping date of "U004" (22 / 11 / 25), and the shipping date of "U005" (22 / 11 / 26) in the accounting data 106b. As a result, the control unit 102 calculates "22 / 11 / 29" as the date for adding "U003", "22 / 11 / 30" as the date for adding "U004", and "22 / 12 / 1" as the date for adding "U005". Similarly, in Figure 6, the control unit 102 identifies "T003" as the customer associated with sales number "U006" in accounting data 106b. Therefore, the control unit 102 adds "15 days", which is the number of days until accounting in customer data 106a shown in Figure 2, to the shipping date (22 / 11 / 20) of sales number "U006" in accounting data 106b. As a result, the control unit 102 calculates "22 / 12 / 5" as the date for adding "U006".

[0031] Next, the control unit 102 determines whether the calculated addition date falls within the closing date of the receivable. Specifically, since the closing date of the customer data 106a shown in Figure 2 is the end of the month, the control unit 102 determines whether the addition date falls within "22 / 11 / 30". For sales numbers "U001" to "U004", the control unit 102 determines that the accounting month corresponding to the closing date is "the current month" because it falls within the closing date (22 / 11 / 30). Then, since the collection setting date set from "the current month" is the end of the following month, the control unit 102 calculates "22 / 12 / 31" as the scheduled collection date for the receivable. On the other hand, for sales numbers "U005" to "U006", the control unit 102 determines that the accounting month corresponding to the closing date is "the next month" because it falls beyond the closing date (22 / 11 / 30). Then, the control unit 102 calculates "23 / 1 / 31" as the scheduled collection date for the debt, since the collection setting date set from "next month" is the end of the following month.

[0032] The control unit 102 then generates the collection schedule data 106c shown in Figures 4 and 6 based on the calculated collection schedule date. At this time, the control unit 102 assigns an accounting end flag to the accounting month corresponding to the collection schedule date. Specifically, as shown in the collection schedule data 106c in Figures 4 and 6, the control unit 102 assigns an accounting end flag of "0" to sales numbers "U001" to "U004" and an accounting end flag of "1" to sales numbers "U005" to "U006".

[0033] Next, referring to Figures 7 to 10, the process for updating the scheduled collection date will be explained. The process for updating the scheduled collection date uses the scheduled collection data 106c and the acceptance data 106d. The process for updating the scheduled collection date described below is executed, for example, at the end of November 2022, in the provisional closing process for claiming receivables.

[0034] When acceptance data 106d is obtained from a business partner, the provisional billing process may require correction of billing information, including the scheduled collection date. Correcting billing information is a high-priority task and should be handled by an experienced person, but manual input is inefficient. Therefore, in the process of updating the scheduled collection date in the provisional billing process, the control unit 102 performs the following process to automatically calculate the scheduled collection date.

[0035] In this provisional billing closing process, the control unit 102 displays the provisional billing closing screen M shown in Figure 7 on the monitor 114. The provisional billing closing screen M is a screen for inputting the information necessary for the provisional billing closing process, and in Figure 7, it is a screen for extracting order numbers that are subject to provisional billing. The provisional billing closing screen M shown in Figure 7 includes fields for creation category, billing closing date, closing date, and customer. The creation category displays checkboxes for selecting "Create" to create an invoice for the accounts receivable of the extracted order numbers, and "Delete" to delete the extracted order numbers. The billing closing date is the date of the billing closing. The closing date and customer are the same as the customer data 106a in Figure 2.

[0036] The control unit 102 extracts the order numbers subject to provisional billing from the collection schedule data 106c based on the extraction conditions entered on the provisional billing processing screen M.

[0037] The control unit 102 determines whether or not it has obtained acceptance data 106d from the customer during the process of updating the scheduled collection date. If the control unit 102 has obtained acceptance data 106d, it calculates the scheduled collection date for the receivable, which is set from the accounting month corresponding to the accounting date of the customer in the acceptance data 106d. Specifically, in the acceptance data 106d shown in Figure 5, the control unit 102 calculates "22 / 12 / 31" as the scheduled collection date because the accounting date for order number "TOK001" is "22 / 11 / 25". Similarly, "22 / 12 / 31" is calculated as the scheduled collection date for order numbers "TOK002", "TOK003", and "TOK005".

[0038] The control unit 102 compares the scheduled collection date calculated from the acceptance data 106d with the scheduled collection date in the scheduled collection data 106c. If the scheduled collection dates match, it maintains the scheduled collection date and settlement flag in the scheduled collection data 106c. Specifically, as shown in Figure 8, the control unit 102 finds that the scheduled collection date for order number "TOK001" in the acceptance data 106d is "22 / 12 / 31," and the scheduled collection date for order number "TOK001" in the scheduled collection data 106c is also "22 / 12 / 31." Since they match, the scheduled collection date in the scheduled collection data 106c is maintained as "22 / 12 / 31," and the settlement flag is also maintained as "0." The same applies to order number "TOK002" and order number "TOK003" in Figure 9.

[0039] Then, when the control unit 102 performs the provisional billing process based on the acquired acceptance data 106d, a number is assigned to the billing number field in the collection schedule data 106c. As shown in Figure 8, the billing number is a number associated with the customer, for example, "S001" is assigned. The same applies to the order number "TOK002", and "S002" is also assigned to the order number "TOK003" in Figure 9.

[0040] On the other hand, the control unit 102 compares the scheduled collection date calculated from the acceptance data 106d with the scheduled collection date in the scheduled collection data 106c. If the scheduled collection dates are different, it updates the scheduled collection date in the scheduled collection data 106c to the scheduled collection date calculated from the acceptance data 106d, and also updates the settlement flag of the scheduled collection data 106c to the settlement flag of the accounting month corresponding to the updated scheduled collection date. Specifically, as shown in Figure 9, the control unit 102 finds that the scheduled collection date for order number "TOK005" in the acceptance data 106d is "22 / 12 / 31", and the scheduled collection date for order number "TOK005" in the scheduled collection data 106c is "23 / 1 / 31", which are different. Therefore, it updates the scheduled collection date in the scheduled collection data 106c to "22 / 12 / 31" and also updates the settlement flag to "0". Then, the control unit 102 assigns the invoice number "S002" to the order number "TOK005".

[0041] Here, if the control unit 102 has not obtained the acceptance data 106d, in the provisional closing process for invoices, it updates the scheduled collection date in the scheduled collection data 106c to the collection setting date set from the accounting month following the accounting month in which the provisional closing is performed, and also updates the settlement flag of the scheduled collection data 106c to match the settlement flag of the accounting month corresponding to the updated scheduled collection date. Specifically, as shown in Figures 5 and 9, the control unit 102 has not obtained the acceptance data 106d for order number "TOK004". In this case, the control unit 102 uses the month following the accounting month in which the provisional closing is performed (November) (December) as the accounting month, and calculates the scheduled collection date (end of the following month) set from the accounting month (December) as the scheduled collection date (23 / 1 / 31). Then, the control unit 102 updates the scheduled collection date in the scheduled collection data 106c to "23 / 1 / 31" and also updates the settlement flag to "1". Furthermore, since the control unit 102 did not acquire the acceptance data 106d for order number "TOK004", the invoice number remains blank.

[0042] Regarding order number "TOK006" shown in Figure 10, acceptance data 106d has not been obtained. However, since the calculated scheduled collection date (23 / 1 / 31) matches the scheduled collection date (23 / 1 / 31) in scheduled collection data 106c, the scheduled collection date in scheduled collection data 106c remains "23 / 1 / 31," and the settlement flag also remains "1."

[0043] As described above, this embodiment allows for the automatic calculation of the expected collection date using the number of days until accounting based on the accounting standards of the trading partner, thereby improving the accuracy of debt collection management.

[0044] Furthermore, this embodiment enables accurate debt collection management based on data by generating collection schedule data that includes the calculated collection date.

[0045] Furthermore, this embodiment allows for the automatic updating of the recall schedule data 106c based on the acceptance data 106d, thereby reducing the workload of correction work and improving work efficiency.

[0046] Furthermore, according to this embodiment, even if the acceptance data 106d cannot be obtained, an appropriate recall date can be determined.

[0047] [3. Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This embodiment can contribute to improving operational efficiency and promoting appropriate management decisions within companies, thereby enabling contributions to SDGs Goals 8 and 9.

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

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

[0050] [4. 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.

[0051] 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.

[0052] 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.

[0053] Furthermore, with respect to the debt management device 100, each component shown in the diagram is a functional concept and does not necessarily need to be physically configured as shown.

[0054] For example, the processing functions of the debt management device 100, particularly those performed in the control unit, 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 debt management 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 tasks. This computer program is executed by being loaded into RAM and works in cooperation with the CPU to constitute the control unit.

[0055] Furthermore, this computer program may be stored on an application program server connected to the debt management device 100 via any network, and it is possible to download all or part of it as needed.

[0056] 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.

[0057] 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 the embodiments, as well as the installation procedures after reading, well-known configurations and procedures can be used.

[0058] The various databases stored in the memory unit are 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.

[0059] Furthermore, the debt management device 100 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 debt management device 100 may be implemented by installing software (including programs or data, etc.) on the device that enables the processing described in this embodiment.

[0060] 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]

[0061] This invention is useful in a wide range of industries, including wholesalers and trading companies, regardless of the type of product. [Explanation of symbols]

[0062] 100 Debt Management System 102 Control Unit 104 Communication Interface Section 106 Storage section 106a Customer Data 106b Accounting Data 106c Data to be recovered 106d Acceptance Data 108 Input / Output Interface Section 112 Input device 114 Output device 200 servers 300 Networks

Claims

1. A debt management device equipped with a control unit that manages the scheduled collection date of receivables to be collected from business partners, Access is available to customer data including the number of days until accounting corresponding to the accounting standards of the aforementioned customer, the billing closing date of the aforementioned customer's receivables, and the collection setting date of the aforementioned customer's receivables, and accounting data including the date of accounting for the aforementioned receivables at the source of the transaction. The control unit, Based on the aforementioned customer data and accounting data, the number of days until the aforementioned accounting date for the receivable is added to calculate the additional accounting date. Determine whether the calculated date of the additional payment falls within the billing deadline for the said claim. If the calculated addition date falls within the billing closing date of the receivable, the collection setting date set from the accounting month corresponding to the billing closing date is calculated as the scheduled collection date of the receivable, If the calculated additional accounting date exceeds the billing closing date for the receivable, the receivable management device calculates the collection setting date, which is set from the accounting month following the accounting month corresponding to the billing closing date, as the scheduled collection date.

2. The control unit, The debt management device according to claim 1, which generates collection schedule data including the calculated collection schedule date and the accounting month corresponding to the collection schedule date.

3. The control unit, The provisional closing process for the claim is being performed to provisionally close the aforementioned claim. In the aforementioned provisional billing process, Determine whether or not the acceptance data, including the date of accounting for the receivables at the aforementioned trading partner, has been obtained. When the aforementioned acceptance data is obtained, the aforementioned collection setting date, which is set from the accounting month corresponding to the aforementioned trading partner accounting date, is calculated as the aforementioned collection scheduled date for the aforementioned receivable. If the scheduled collection date calculated from the acceptance data matches the scheduled collection date in the scheduled collection data, the scheduled collection date and the settlement flag in the scheduled collection data are maintained, The accounts receivable management device according to claim 2, wherein if the scheduled collection date calculated from the acceptance data differs from the scheduled collection date in the scheduled collection data, the scheduled collection date in the scheduled collection data is updated to the scheduled collection date calculated from the acceptance data, and the settlement flag in the scheduled collection data is updated to the settlement flag for the accounting month corresponding to the updated scheduled collection date.

4. The control unit, If the aforementioned acceptance data has not been obtained, the debt management device according to claim 3 updates the collection date of the collection schedule data to the collection setting date set in the accounting month following the month in which the accounting month is provisionally closed in the provisional closing process, and updates the settlement flag of the collection schedule data to the settlement flag of the collection schedule data for the accounting month corresponding to the updated collection date.

5. A debt management method for managing the scheduled collection dates for receivables to be collected from business partners, The following are used: customer data including the number of days until accounting corresponding to the accounting standards of the aforementioned customer, the billing closing date of the aforementioned customer's receivables, and the collection setting date of the aforementioned customer's receivables; and accounting data including the date of accounting for the aforementioned receivables at the trading source. Based on the aforementioned customer data and accounting data, the number of days until the aforementioned accounting date for the receivable is added to calculate the additional accounting date. Determine whether the calculated date of the additional payment falls within the billing deadline for the said claim. If the calculated addition date falls within the billing closing date of the receivable, the collection setting date set from the accounting month corresponding to the billing closing date is calculated as the scheduled collection date of the receivable, A debt management method in which a debt management device equipped with a control unit calculates the collection setting date, which is set from the accounting month following the accounting month corresponding to the accounting month, as the scheduled collection date, if the calculated additional accounting date exceeds the billing closing date of the debt.

6. A debt management program that causes a debt management device equipped with a control unit to execute a debt management method for managing the scheduled collection dates of receivables to be collected from business partners, The following are used: customer data including the number of days until accounting corresponding to the accounting standards of the aforementioned customer, the billing closing date of the aforementioned customer's receivables, and the collection setting date of the aforementioned customer's receivables; and accounting data including the date of accounting for the aforementioned receivables at the trading source. Based on the aforementioned customer data and accounting data, the number of days until the aforementioned accounting date for the receivable is added to calculate the additional accounting date. Determine whether the calculated date of the additional payment falls within the billing deadline for the said claim. If the calculated addition date falls within the billing closing date of the receivable, the collection setting date set from the accounting month corresponding to the billing closing date is calculated as the scheduled collection date of the receivable, A debt management program that causes the debt management device to calculate the collection setting date, which is set from the accounting month following the accounting month corresponding to the accounting month, as the scheduled collection date, if the calculated additional accounting date exceeds the billing closing date of the debt.

Images