Claims management device, claims management method, and claims management program
The credit management device automatically manages transaction suspensions and resumptions based on debt collection status, addressing delays and risks in existing systems by integrating transaction suspension and resumption mechanisms.
Patent Information
- Application Number
- JP2021030111
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2021-02-26
- Publication Date
- 2024-11-13
- Estimated Expiration
- 2041-02-26
AI Technical Summary
Existing systems fail to automatically suspend transactions when a factoring company is unable to collect debts, leading to potential delays and increased risk of non-collection and loss of business opportunities.
A credit management device and method that includes a storage unit to store transaction statuses and receivable data, with a control unit to automatically acquire and update transaction suspension data, determine processing continuation, and output messages when necessary, ensuring timely transaction suspension and resumption based on debt collection status.
Enables automatic control of transactions to prevent further debt collection risks, reduces loss of business opportunities, and ensures timely resumption of transactions upon debt collection, thereby enhancing operational efficiency and reducing non-collection risks.
Smart Images

Figure 0007582880000001 
Figure 0007582880000002 
Figure 0007582880000003
Abstract
Description
[Technical field]
[0001] The present invention relates to a claim management device, a claim management method, and a claim management program. [Background technology]
[0002] Patent Document 1 discloses a configuration for offsetting payables and receivables with the same maturity between a paying company (debtor) and a supplier company (creditor) and executing payment processing for the supplier company according to payment from the paying company. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2019-219933 A Summary of the Invention [Problem to be solved by the invention]
[0004] However, the invention described in the above Patent Document 1 had a problem in that if the factoring company was unable to collect the debt from the debtor, the factoring company could not automatically request the suspension of the transaction.
[0005] The present invention has been made in consideration of the above-mentioned problems, and aims to provide a receivables management device, a receivables management method, and a receivables management program that can share billing data with a factoring company and automatically share transaction suspension data from the factoring company if the factoring company is subsequently unable to collect the receivable. [Means for solving the problem]
[0006] In order to solve the above-mentioned problems and achieve the object, the receivables management device of the present invention is a receivables management device equipped with a memory unit and a control unit, wherein the memory unit comprises a customer memory means for storing a customer master that sets the transaction status for each customer, and a receivables memory means for storing receivables data of receivables factored by a factoring company and for which a maturity date is set, and the control unit comprises a transaction suspension acquisition means for acquiring transaction suspension data for a customer when the factoring company is unable to collect receivables from the customer by the maturity date, an update means for updating the customer master based on the transaction suspension data, and a processing continuation determination means for determining that processing cannot be continued based on the transaction setting data and the customer master when transaction setting data with the customer is input.
[0007] In addition, in the receivables management device of the present invention, the transaction suspension acquisition means further acquires transaction suspension lifting data for a trading partner when the trading partner repays a debt to the factoring company, and the update means further updates the trading partner master based on the transaction suspension lifting data.
[0008] In addition, in the receivable management device of the present invention, the processing continuation determination means is further characterized in that, when the transaction setting data with the trading partner is input, it determines that processing can be continued based on the transaction setting data and the trading partner master.
[0009] In addition, in the debt management device of the present invention, the control unit is further characterized by having a message output means for outputting a processing impossible continuation message when the processing continuation determination means determines that processing cannot be continued.
[0010] In the claim management device according to the present invention, the processing continuation determination means further displays a transaction input screen for inputting the transaction setting data with the business partner.
[0011] In addition, in the debt management device of the present invention, the transaction suspension data is set as a transaction suspension date for the trading partner, and the update means sets the transaction suspension date as the transaction status of the trading partner set in the trading partner master based on the transaction suspension data.
[0012] In addition, in the debt management device of the present invention, the transaction suspension lifting data is set as the transaction suspension lifting date for the supplier, and the update means is further characterized in that, when the transaction suspension lifting date arrives based on the transaction suspension lifting data, it lifts the transaction suspension date set in the supplier master.
[0013] In the claim management device according to the present invention, the transaction setting data is order setting data, shipping setting data, or sales setting data.
[0014] In addition, the receivables management method of the present invention is a receivables management method to be executed by a receivables management device having a memory unit and a control unit, the memory unit comprising a customer memory means for storing a customer master that sets the transaction status for each customer, and a receivables memory means for storing receivables data of receivables factored by a factoring company and having a maturity date set, and is executed by the control unit, the method including a transaction suspension acquisition step for acquiring transaction suspension data for the customer if the factoring company is unable to collect the receivables from the customer by the maturity date, an update step for updating the customer master based on the transaction suspension data, and a processing continuation determination step for determining that processing cannot be continued based on the transaction setting data and the customer master when transaction setting data with the customer is input.
[0015] In addition, the receivables management program of the present invention is a receivables management program to be executed by a receivables management device having a memory unit and a control unit, the memory unit comprising a customer memory means for storing a customer master that sets the transaction status for each customer, and a receivables memory means for storing receivables data of receivables factored by a factoring company and for which a maturity date is set, and the control unit is characterized in that it executes the following steps: a transaction suspension acquisition step for acquiring transaction suspension data for the customer when the factoring company is unable to collect the receivables from the customer by the maturity date; an update step for updating the customer master based on the transaction suspension data; and a processing continuation determination step for determining that processing cannot be continued based on the transaction setting data and the customer master when transaction setting data with the customer is input. Effect of the Invention
[0016] According to the present invention, even if a transaction (order, shipment, sales) occurs with a company that has not been able to collect receivables, the system can control the transaction so that the transaction cannot proceed. In addition, according to the present invention, when the collection of uncollected receivables is completed, a notification from the factoring company can be automatically linked, so that the transaction with the company that has not been able to collect receivables can be resumed. In addition, according to the present invention, the risk of debt collection can be reduced, and the opportunity loss of transactions can be prevented. In addition, according to the present invention, for wholesale businesses that wholesale to restaurants and the like, the risk of debt collection can be reduced. In addition, according to the present invention, when the transaction suspension condition is met, the downstream process of the business can be immediately stopped, and when the suspension condition is avoided, the transaction can be immediately resumed. In addition, according to the present invention, the risk of uncollected receivables that cannot be detected by normal credit management alone can be avoided, and unnecessary business opportunity loss due to delay in transaction suspension can be prevented. In addition, according to the present invention, the risk of bad debts can be mechanically prevented in the debt collection business. [Brief description of the drawings]
[0017] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of a claim management device in this embodiment. [Diagram 2] FIG. 2 is a flowchart showing an example of the process of the claim management device in this embodiment. [Diagram 3] FIG. 3 is a diagram showing an example of a bond management process in this embodiment. [Figure 4] FIG. 4 is a diagram showing an example of a supplier master screen in this embodiment. [Diagram 5] FIG. 5 is a diagram showing an example of a bond management process in this embodiment. [Figure 6] FIG. 6 is a diagram showing an example of an order input screen in this embodiment. [Figure 7] FIG. 7 is a diagram showing an example of a shipping input screen in this embodiment. [Figure 8] FIG. 8 is a diagram showing an example of a sales input screen in this embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0018] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described in detail with reference to the drawings. However, the present invention is not limited to the embodiment.
[0019] [1. Overview] First, an overview of the present invention will be described.
[0020] Previously, the process of transferring receivables to a factoring company was sometimes systemized. In actual operation, if receivables cannot be collected after being transferred to a factoring company, the factoring company notifies the company that transferred the receivables and the transaction with the relevant customer must be stopped. However, this is an analog operation, so there are cases where the notification is missed or the transaction suspension is delayed depending on the timing of the notification. On the other hand, previously, if uncollected receivables are collected, the factoring company notifies the company that transferred the receivables and the transaction with the relevant customer must be started. However, this is also an analog operation, so there are cases where the notification is missed or the transaction start is delayed depending on the timing of the notification.
[0021] Therefore, in this embodiment, a mechanism is provided that can control the system so that, upon receiving transaction suspension information from the factoring company, all transactions including orders, shipments, and sales are automatically suspended, and, upon receiving transaction cancellation information from the factoring company, all transactions including orders, shipments, and sales are automatically resumed.
[0022] [2. Configuration] An example of the configuration of a claim management device 100 according to this embodiment will be described with reference to Fig. 1. Fig. 1 is a block diagram showing an example of the configuration of the claim management device 100 according to this embodiment.
[0023] 1, the claim management device 100 is a commercially available desktop personal computer. Note that the claim management device 100 is not limited to a stationary information processing device such as a desktop personal computer, and may be a portable information processing device such as a commercially available notebook personal computer, a PDA (Personal Digital Assistant), a smartphone, or a tablet personal computer.
[0024] The bond management device 100 comprises a control unit 102, a communication interface unit 104, a memory unit 106, and an input / output interface unit 108. Each unit of the bond management device 100 is connected to each other so as to be able to communicate with each other via any communication path.
[0025] The communication interface unit 104 communicatively connects the claim 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 the communication line. Here, the network 300 has a function of connecting the claim management device 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] An input device 112 and an output device 114 are connected to the input / output interface unit 108. The output device 114 may be a monitor (including a touch panel), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that cooperates with a mouse to realize a pointing device function. In the following, the output device 114 may be referred to as the monitor 114 or the printer 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.
[0027] The storage unit 106 stores various databases, tables, files, etc. The storage unit 106 records computer programs for cooperating with the OS (Operating System) to give instructions to the CPU (Central Processing Unit) to perform various processes. 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 as the storage unit 106. The storage unit 106 includes a customer master 106a and a credit database 106b.
[0028] The supplier master 106a is a master that sets the transaction status for each supplier. Here, the supplier master 106a may be set in association with a supplier identifier (e.g., a supplier code and / or a supplier name, etc.) and a transaction status (e.g., a transaction suspension date, etc.).
[0029] The claim database 106b stores claim data. Here, the claim database 106b may store claim data of claims factored by a factoring company, for which a maturity date is set.
[0030] The control unit 102 is a CPU or the like that performs overall control of the claim management device 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, and required data, and executes various information processing based on these stored programs. In terms of functional concept, the control unit 102 includes a transaction suspension acquisition unit 102a, an update unit 102b, a processing continuation determination unit 102c, and a message output unit 102d.
[0031] The transaction suspension acquisition unit 102a acquires transaction suspension data for a business partner. Here, when the factoring company is unable to collect receivables from the business partner by the maturity date of the receivables, the transaction suspension acquisition unit 102a may acquire transaction suspension data for the business partner. Furthermore, when the business partner repays its debt to the factoring company, the transaction suspension acquisition unit 102a may acquire transaction suspension lift data for the business partner. Furthermore, the transaction suspension data may include a transaction suspension date for the business partner. Furthermore, the transaction suspension lift data may include a transaction suspension lift date for the business partner. Furthermore, the transaction suspension acquisition unit 102a may store the transaction suspension data or the transaction suspension lift data in the receivables database 106b.
[0032] The update unit 102b updates the supplier master 106a. Here, the update unit 102b: The supplier master 106a may be updated based on the transaction suspension data. The update unit 102b may also update the supplier master 106a based on the transaction suspension lift data. The update unit 102b may also set a transaction suspension date as the transaction status of the supplier set in the supplier master 106a based on the transaction suspension data. The update unit 102b may also cancel the transaction suspension date set in the supplier master 106a when the transaction suspension lift date arrives based on the transaction suspension lift data.
[0033] When transaction setting data with a supplier is input, the process continuation determination unit 102c determines whether or not the process can be continued. Here, when transaction setting data with a supplier is input, the process continuation determination unit 102c may determine that the process cannot be continued based on the transaction setting data and the supplier master 106a. When transaction setting data with a supplier is input, the process continuation determination unit 102c may determine that the process can be continued based on the transaction setting data and the supplier master 106a. Furthermore, the process continuation determination unit 102c may display a transaction input screen for inputting transaction setting data with a supplier. Furthermore, the transaction setting data may be order setting data, shipping setting data, or sales setting data.
[0034] The message output unit 102d outputs a message indicating that processing cannot be continued. Here, the message output unit 102d may output a message indicating that processing cannot be continued when the processing continuation determination unit 102c determines that processing cannot be continued.
[0035] [3. Specific Examples] A specific example of this embodiment will be described with reference to FIGS.
[0036] [Accounts Management Processing] An example of a claim management process in this embodiment will now be described with reference to Fig. 2. Fig. 2 is a flow chart showing an example of the process of the claim management device 100 in this embodiment.
[0037] As shown in FIG. 2, when a user inputs transaction setting data with a trading partner into the transaction input screen via the input device 112, the control unit 102 obtains the receivables data corresponding to the transaction setting data and transmits the receivables data to the factoring company (step SA-1).
[0038] Then, the control unit 102 sets the transaction suspension date, which is the transaction status of the supplier set in the transaction setting data, to blank (null) in the supplier master 106a (step SA-2).
[0039] Then, the transaction suspension acquisition unit 102a judges whether or not transaction suspension data for the supplier transmitted from the factoring company has been acquired on the maturity date of the receivable (step SA-3).
[0040] If the transaction suspension acquisition unit 102a determines that transaction suspension data has not been acquired (step SA-3: No), the transaction suspension acquisition unit 102a shifts the process to step SA-10.
[0041] On the other hand, if the transaction suspension acquisition unit 102a determines that transaction suspension data has been acquired (step SA-3: Yes), it shifts the process to step SA-4.
[0042] Then, the update unit 102b sets the maturity date of the bond to the transaction suspension date set in the supplier master 106a based on the transaction suspension data (step SA-4).
[0043] Then, the process continuation determination unit 102c determines whether or not the user has input transaction setting data with the supplier on the transaction input screen via the input device 112 (step SA-5).
[0044] If the process continuation determination unit 102c determines that transaction setting data with the supplier has not been input on the transaction input screen (step SA-5: No), the process proceeds to step SA-8.
[0045] On the other hand, if the process continuation determination unit 102c determines that transaction setting data with the supplier has been input on the transaction input screen (step SA-5: Yes), it shifts the process to step SA-6.
[0046] Then, the processing continuation determination unit 102c determines that processing cannot be continued based on the transaction setting data and the supplier master 106a (step SA-6).
[0047] Then, the message output unit 102d causes the output device 114 to display a message indicating that processing cannot be continued (step SA-7).
[0048] Then, the transaction suspension acquisition unit 102a determines whether or not it has acquired transaction suspension lifting data for the trading partner, which data sets the transaction suspension lifting date for the trading partner and is sent from the factoring company when the trading partner repays its debt to the factoring company (step SA-8).
[0049] If the transaction suspension acquisition unit 102a determines that transaction suspension lift data has not been acquired (step SA-8: No), the transaction suspension acquisition unit 102a shifts the process to step SA-5.
[0050] On the other hand, if the transaction suspension acquisition unit 102a determines that transaction suspension lift data has been acquired (step SA-8: Yes), it shifts the process to step SA-9.
[0051] Then, when the transaction suspension lift date arrives based on the transaction suspension lift data, updating unit 102b cancels (sets to blank (null)) the transaction suspension date set in supplier master 106a (step SA-9).
[0052] Then, the process continuation determination unit 102c determines whether or not the user has input transaction setting data with the supplier to the transaction input screen via the input device 112 (step SA-10).
[0053] If the process continuation determination unit 102c determines that the transaction setting data with the supplier has not been input on the transaction input screen (step SA-10: No), the process ends.
[0054] On the other hand, if the process continuation determination unit 102c determines that transaction setting data with the supplier has been input on the transaction input screen (step SA-10: Yes), it shifts the process to step SA-11.
[0055] Then, the process continuation determination unit 102c determines that the process can be continued based on the transaction setting data and the supplier master 106a, and continues the process based on the transaction setting data (step SA-11), and ends the process.
[0056] Here, an example of the claim management process in this embodiment will be described with reference to Fig. 3 to Fig. 8. Fig. 3 and Fig. 5 are diagrams showing an example of the claim management process in this embodiment. Fig. 4 is a diagram showing an example of a supplier master screen in this embodiment.
[0057] As shown in FIG. 3, in this embodiment, the receivables assigning company ships the goods corresponding to the order entry and the shipment entry to the business partner, and sends the receivables data corresponding to the sales entry to the factoring company. Then, as shown in FIG. 3, in this embodiment, the factoring company issues an invoice and sends it to the business partner, and if the business partner does not make payment on the maturity date of the receivables: January 5, 2020, transaction suspension data is created and sent to the receivables assigning company. Then, as shown in FIG. 3, in this embodiment, the receivables assigning company automatically updates the business partner master 106a based on the received transaction suspension data. Then, as shown in FIG. 3, in this embodiment, when the receivables assigning company inputs transaction setting data with the business partner into each input screen, the transaction suspension date of the business partner master 106a is referenced, and if the reference date of each input screen is after the transaction suspension date + 1 day (January 6, 2020), processing cannot be continued. FIG. 3 shows an example of automatic updating of supplier master data 106a. However, as shown in FIG. 4, in this embodiment, when suspension of trading data is received, the suspension date may be manually registered on the supplier master screen.
[0058] As shown in Fig. 5, in this embodiment, when a client deposits funds into the factoring company, transaction suspension lifting data is created by the factoring company and sent to the receivables transferring company. As shown in Fig. 5, in this embodiment, the client master 106a is automatically updated based on the received transaction suspension lifting data at the receivables transferring company. As shown in Fig. 5, in this embodiment, when transaction setting data with a client is entered into each input screen at the receivables transferring company, the transaction suspension date in the client master 106a is referenced, and if no data has been set, processing can continue.
[0059] Here, an example of a message output indicating that processing cannot be continued in this embodiment will be described with reference to Fig. 6 to Fig. 8. Fig. 6 is a diagram showing an example of an order input screen in this embodiment. Fig. 7 is a diagram showing an example of a shipment input screen in this embodiment. Fig. 8 is a diagram showing an example of a sales input screen in this embodiment.
[0060] As shown in FIG. 6, in this embodiment, when a supplier code and order date are entered on the order input screen, a determination is made as to whether or not trading has been suspended based on the supplier and order date. If trading has been suspended, a message is displayed and processing cannot continue.
[0061] Also, as shown in FIG. 7, in this embodiment, when a supplier code and shipping date are entered on the shipment input screen, it is determined whether or not trading has been suspended based on the supplier and shipping date, and if trading has been suspended, a message is displayed and processing cannot continue.
[0062] Also, as shown in FIG. 8, in this embodiment, when a supplier code and sales date are entered on the sales input screen, whether or not trading is suspended is determined based on the supplier and sales date, and if trading is suspended, a message is displayed and processing cannot continue.
[0063] [4. Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This embodiment can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby contributing to goals 8 and 9 of the SDGs.
[0064] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of SDGs Goals 12, 13, and 15.
[0065] Furthermore, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.
[0066] 5. Other embodiments The present invention may be embodied in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.
[0067] 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 using known methods.
[0068] In addition, the processing procedures, control procedures, specific names, information including parameters such as registered data and search conditions for each process, screen examples, and database configurations shown in this specification and drawings may be changed as desired unless otherwise specified.
[0069] Furthermore, with regard to the claim management device 100, each of the components shown in the figures is a functional concept, and does not necessarily have to be physically configured as shown in the figures.
[0070] For example, the processing functions of the claim management device 100, particularly the processing functions performed by the control unit 102, may be realized in whole or in part by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded on a non-transient computer-readable recording medium that includes programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the claim management device 100 as necessary. That is, a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive). This computer program is executed by being loaded into a RAM, and cooperates with the CPU to form a control unit.
[0071] In addition, this computer program may be stored in an application program server connected to the claim management device 100 via any network, and it is also possible to download all or part of it as necessary.
[0072] In addition, the program for executing the process described in this embodiment may be stored in a non-transient computer-readable recording medium, or may be configured as a program product. Here, the "recording medium" includes any "portable physical medium" such as a memory card, a Universal Serial Bus (USB) memory, a Secure Digital (SD) card, a flexible disk, a magneto-optical disk, a ROM, an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable and Programmable Read Only Memory (EEPROM (registered trademark)), a Compact Disk Read Only Memory (CD-ROM), a Magneto-Optical disk (MO), a Digital Versatile Disk (DVD), and a Blu-ray (registered trademark) Disc.
[0073] Moreover, a "program" is a data processing method written in any language or description method, and may be in any form, such as source code or binary code. Note that a "program" is not necessarily limited to a single configuration, but also includes a configuration that is distributed as a plurality of modules or libraries, and a program that achieves its function by cooperating with a separate program, such as an OS. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in this embodiment, as well as the installation procedure after reading, may use well-known configurations and procedures.
[0074] The various databases etc. stored in the memory unit 106 are storage means such as 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 etc. used for various processes and providing websites.
[0075] The claim management device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the information processing device to which any peripheral device is connected. The claim management device 100 may be realized by installing software (including programs or data, etc.) that causes the device to realize the processing described in this embodiment.
[0076] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be functionally or physically distributed and integrated in any unit according to various additions or functional loads. In other words, the above-mentioned embodiments can be implemented in any combination, or the embodiments can be implemented selectively. [Industrial Applicability]
[0077] INDUSTRIAL APPLICABILITY The present invention is useful in industries such as the food industry, which has many small and medium-sized enterprises as business partners such as food wholesalers, and the financial industry, such as factoring companies. [Explanation of symbols]
[0078] 100 Credit management device 102 Control section 102a Trading Suspension Department 102b Update section 102c Processing continuation decision unit 102d Message output section 104 Communication interface section 106 Storage section 106a Customer Master 106b Bond Database 108 Input / Output Interface Section 112 Input Devices 114 Output Device 200 Servers 300 Network
Claims
1. A claim management device including a memory unit and a control unit, The storage unit is A supplier storage means for storing a supplier master in which a transaction status for each supplier is set; a receivables storage means for storing receivables data of receivables factored by a factoring company, the receivables data having a maturity date set thereon; Equipped with The control unit is a transaction suspension acquisition means for acquiring transaction suspension data for a customer when the factoring company is unable to collect the receivables from the customer by the maturity date; an update means for updating the supplier master based on the transaction suspension data; a processing continuation determination means for determining that processing cannot be continued based on the transaction setting data and the supplier master when the supplier master is updated based on the transaction suspension data and transaction setting data with the supplier is input; Equipped with The transaction suspension acquisition means includes: When the customer repays the debt to the factoring company, data on the lifting of the suspension of transactions with the customer is obtained; The update means includes: updating the customer master based on the transaction suspension lift data; The processing continuation determination means A receivable management device characterized in that, when the customer master is updated based on the transaction suspension lift data and the transaction setting data with the customer is input, it is determined that processing can be continued based on the transaction setting data and the customer master.
2. The control unit is a message output means for outputting a message indicating that the processing cannot be continued when the processing continuation determination means determines that the processing cannot be continued; 2. The claim management device according to claim 1, further comprising:
3. The processing continuation determination means 3. The claim management device according to claim 1, further comprising a transaction input screen for inputting the transaction setting data with the business partner.
4. The transaction suspension data includes: A trading suspension date for the said business partner is set, The update means includes:
2. The claim management device according to claim 1, wherein the transaction suspension date is set as the transaction status of the supplier set in the supplier master based on the transaction suspension data.
5. The transaction suspension lift data is A date for lifting the suspension of transactions with the said business partner is set, The update means includes:
5. The claim management device according to claim 4, further comprising: cancelling the transaction suspension date set in the supplier master when the transaction suspension cancellation date arrives based on the transaction suspension cancellation data.
6. The transaction setup data includes:
6. The claim management device according to claim 1, wherein the data is order setting data, shipping setting data, or sales setting data.
7. A claim management method to be executed by a claim management device having a memory unit and a control unit, The storage unit is A supplier storage means for storing a supplier master in which a transaction status for each supplier is set; a receivables storage means for storing receivables data of receivables factored by a factoring company, the receivables data having a maturity date set thereon; Equipped with The control unit executes a transaction suspension acquisition step of acquiring transaction suspension data for a customer when the factoring company is unable to collect the receivables from the customer by the maturity date; an updating step of updating the supplier master based on the transaction suspension data; a process continuation determination step of determining that the process cannot be continued based on the transaction setting data and the supplier master when the supplier master is updated based on the transaction suspension data and transaction setting data with the supplier is input; a transaction suspension release acquisition step of acquiring transaction suspension release data for the transaction partner when the transaction partner has paid off a debt to the factoring company; a cancellation update step of updating the supplier master based on the transaction suspension cancellation data; a process continuation possibility determination step of determining, when the supplier master is updated based on the transaction suspension lift data and the transaction setting data with the supplier is input, whether or not processing can be continued based on the transaction setting data and the supplier master; A method for managing claims, comprising:
8. A claim management program to be executed by a claim management device having a memory unit and a control unit, The storage unit is A supplier storage means for storing a supplier master in which a transaction status for each supplier is set; a receivables storage means for storing receivables data of receivables factored by a factoring company, the receivables data having a maturity date set thereon; Equipped with In the control unit, a transaction suspension acquisition step of acquiring transaction suspension data for a customer when the factoring company is unable to collect the receivables from the customer by the maturity date; an updating step of updating the supplier master based on the transaction suspension data; a process continuation determination step of determining that the process cannot be continued based on the transaction setting data and the supplier master when the supplier master is updated based on the transaction suspension data and transaction setting data with the supplier is input; a transaction suspension release acquisition step of acquiring transaction suspension release data for the transaction partner when the transaction partner has paid off a debt to the factoring company; a cancellation update step of updating the supplier master based on the transaction suspension cancellation data; a process continuation possibility determination step of determining, when the supplier master is updated based on the transaction suspension lift data and the transaction setting data with the supplier is input, whether or not processing can be continued based on the transaction setting data and the supplier master; A receivables management program to implement the above.
Citation Information
Patent Citations
Vehicle maintenance and management system, computer-based method for maintenance and management of vehicle, and vehicle maintenance and management program
JP2004178346A
Collection agency / recovery guarantee system
JP2004178458A
Demand storage system, demand storage device, method, and computer program
JP2006323519A
Gas station system
JP2010097448A
System and method for managing information on electronic recording credit regarding financial service
JP2015090585A
