Claims management device, claims management method, and claims management program

Abstract

To provide a credit management apparatus, credit management method, and credit management program capable of performing credit management and clearing processing for each of invoice transfer and payroll deduction in the same operation.SOLUTION: A credit management apparatus of the present embodiment is configured: if a product is sold to an employee of a group company, to acquire sales data in which a collection method that is payroll deduction, transfer slip, invoice transfer, or cash, a group company, a collection schedule date, a product price, and the purchased employee if the collection method is the payroll deduction are set; to create collection schedule data in which the collection method that is the payroll deduction, transfer slip, or invoice transfer, the group company, the collection schedule date, and the product price are set; and to create deduction data for the purchased employee and transmit it to a payroll system of the group company to which the purchased employee belongs if the collection method set in the collection schedule data is the payroll deduction.SELECTED DRAWING: Figure 1

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 technology that manages sales data for each employee of each company that makes up a corporate group when they purchase products sold by other companies in the group, and deducts the sales data in cooperation with each company's payroll system. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2003-141374 A Summary of the Invention [Problem to be solved by the invention]

[0004] In industries where sales operations include both external sales and sales to employees of the company or employees of the same group companies (hereafter referred to as "internal sales"), such as the food industry, there are two types of receivables from group companies: receivables from invoices for regular business (biller transfers) and receivables from employee sales (transfers of supply deductions), and these are deposited separately. For this reason, the conventional technology required management of receivables by denomination, such as invoice transfers and payroll deductions, which made receivable management and settlement processing (tasks) complicated.

[0005] The present invention has been made in consideration of the above, and aims to provide a claims management device, a claims management method, and a claims management program that can perform claims management and settlement processing for both invoice transfers and salary deductions in the same operation. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, the accounts receivable management device of the present invention is a accounts receivable management device equipped with a memory unit and a control unit, wherein the control unit is characterized in that when a product is sold to an employee of a group company, the control unit is equipped with a sales acquisition means for acquiring sales data setting the collection method which is payroll deduction, transfer slip, invoice transfer, or cash, the group company, the scheduled collection date, the product amount, and the purchasing employee if the collection method is payroll deduction, and creating scheduled collection data setting the collection method which is payroll deduction, transfer slip, or invoice transfer, the group company, the scheduled collection date, and the product amount, a deduction creation means for creating deduction data for the purchasing employee and sending it to the payroll system of the group company to which the purchasing employee belongs, if the collection method set in the scheduled collection data is payroll deduction, a deposit acquisition means for acquiring deposit data setting the group company, deposit date, and deposit amount, and a deposit reconciliation means for creating deposit reconciliation data for the sales data based on the deposit data and the scheduled collection data.

[0007] In addition, the accounts receivable management method of the present invention is a accounts receivable management method executed by an accounts receivable management device having a memory unit and a control unit, and is characterized in that it includes a sales acquisition step, executed by the control unit, of acquiring sales data that sets the collection method, which is payroll deduction, transfer slip, invoice transfer, or cash, the group company, the scheduled collection date, the product amount, and the purchasing employee if the collection method is payroll deduction, when a product is sold to an employee of a group company, and creating scheduled collection data that sets the collection method, which is payroll deduction, transfer slip, or invoice transfer, the group company, the scheduled collection date, and the product amount; a deduction creation step, when the collection method set in the scheduled collection data is payroll deduction, of creating deduction data for the purchasing employee and sending it to the payroll system of the group company to which the purchasing employee belongs; a deposit acquisition step, of acquiring deposit data that sets the group company, deposit date, and deposit amount; and a deposit reconciliation step, of creating deposit reconciliation data for the sales data based on the deposit data and the scheduled collection data.

[0008] In addition, the accounts receivable management program of the present invention is a accounts receivable management method program to be executed by an accounts receivable management device having a memory unit and a control unit, and is characterized in that it includes a sales acquisition step for acquiring sales data that sets the collection method, which is payroll deduction, transfer slip, invoice transfer, or cash, the group company, the scheduled collection date, the product amount, and the purchasing employee when the collection method is payroll deduction, when a product is sold to an employee of a group company, and creating scheduled collection data that sets the collection method, which is payroll deduction, transfer slip, or invoice transfer, the group company, the scheduled collection date, and the product amount; a deduction creation step for creating deduction data for the purchasing employee and sending it to the payroll system of the group company to which the purchasing employee belongs, when the collection method set in the scheduled collection data is payroll deduction; a deposit acquisition step for acquiring deposit data that sets the group company, deposit date, and deposit amount; and a deposit reconciliation step for creating deposit reconciliation data for the sales data based on the deposit data and the scheduled collection data. Effect of the Invention

[0009] According to the present invention, it is possible to carry out the credit management and settlement processing for both bill transfers and payroll deductions in the same operation. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 is a schematic diagram showing an overview in a block diagram of an example of the configuration of a loan management device according to an embodiment. [Diagram 2] FIG. 2 is an overall view including the sales channels of the claim management device. [Diagram 3] FIG. 3 is a diagram showing a process flow of the bond management device. [Figure 4] FIG. 4 is a diagram illustrating an example of the sales data table. [Diagram 5] FIG. 5 is a diagram illustrating an example of the collection schedule data table. [Figure 6]FIG. 6 is a diagram illustrating an example of a deduction data table. [Figure 7] FIG. 7 is a diagram showing an example of the deposit data table. [Figure 8] FIG. 8 is a diagram showing an example of the deposit reconciliation data table. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, preferred embodiments of a claim management device, a claim management method, and a claim management program according to the present invention will be described in detail with reference to the accompanying drawings. Note that the present invention is not limited to the preferred embodiments.

[0012] [1. Configuration] An example of the configuration of the claim management according to this embodiment will be described with reference to Fig. 1 etc. Fig. 1 is a block diagram showing an example of the configuration of the claim management.

[0013] The claim management device 100 shown in Fig. 1 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, but 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.

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

[0015] 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). The data stored in the memory unit 106 may be stored in the server 200, for example.

[0016] 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 home television), 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, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.

[0017] The storage unit 106 stores various databases, tables, files, etc. The storage unit 106 records computer programs for cooperating with an OS (Operating System) to give instructions to a 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 stores sales data 106a, scheduled collection data 106b, deduction data 106c, deposit data 106d, and deposit reconciliation data 106e.

[0018] The sales data 106a stores, for each item, the sales date, the customer, the collection method, the scheduled collection date, the amount, and a summary of the item (employee number and / or employee name).

[0019] The collection schedule data 106b stores the customer, collection method, scheduled collection date, and amount.

[0020] The deduction data 106c stores the customer, employee number, expected collection date, and amount.

[0021] The deposit data 106d stores the customer, the deposit date, and the deposit amount.

[0022] The deposit reconciliation data 106e stores the customer, the collection method, and the reconciliation amount.

[0023] 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. The control unit 102 includes a sales acquisition unit 102a, a deduction creation unit 102b, a deposit acquisition unit 102c, and a deposit reconciliation unit 102d.

[0024] When a product is sold to an employee of a group company, the sales acquisition unit 102a acquires sales data that sets the collection method (payroll deduction, transfer slip, invoice transfer, or cash), the group company, the scheduled collection date, the product amount, and the purchasing employee if the collection method is payroll deduction.The sales acquisition unit 102a then creates collection schedule data that sets the collection method (payroll deduction, transfer slip, or invoice transfer), the group company, the scheduled collection date, and the product amount.

[0025] If the collection method set in the collection schedule data is payroll deduction, the deduction creation unit 102b creates deduction data for the purchasing employee and transmits it to the payroll system of the group company to which the purchasing employee belongs.

[0026] The deposit acquiring unit 102c acquires deposit data that includes the group company, the deposit date, and the deposit amount.

[0027] The deposit reconciliation unit 102d creates deposit reconciliation data for the sales data based on the deposit data and the collection schedule data.

[0028] [2. Overall view of the sales channel for the credit management device] FIG. 2 is an overall view including the sales channels of the claim management device 100.

[0029] As shown in FIG. 2, the sales channels of the claim management device 100 include Web sales E1, store sales E2, and regular sales E3.

[0030] Web sales E1 includes (1) sales (internal sales) by retired employees and employees of group companies on the website provided by group companies, and (2) sales by general corporations on the website. Therefore, Web sales E1 includes deductions F1, payment slips F2, and invoice transfers F3.

[0031] Store sales E2 includes (1) sales (internal sales) by employees of group companies at stores (shops) and other outlets belonging to group companies, and (2) sales by the general public at stores. Therefore, store sales E2 includes deductions F1 and cash F4.

[0032] Regular sales E3 includes sales to general corporations (corporate transactions). Therefore, regular sales E3 includes invoice transfer F3.

[0033] In this way, the sales data handled by the claim management device 100 includes deductions, payment slips, claimant payments, and cash. In addition, the claim data handled by the claim management device 100 includes various accounts of each parent group company and each group company by transfer, collection result data of individuals by transfer via a bank (e.g. S Bank), and various accounts by general corporations by transfer.

[0034] 3. Processing by the credit management device 100 Next, a description will be given of the processing by the claim management device 100. Fig. 3 is a diagram showing the processing flow by the claim management device 100. In Fig. 3, from the top, the processing flow of withholding, payment slip, invoice payment, and cash is shown.

[0035] As shown in FIG. 3, first, when a product is sold to an employee of a group company, the sales acquisition unit 102a performs sales import to acquire sales data from the store and the Web system, which includes the collection method (payroll deduction, transfer slip, invoice transfer, or cash), the group company, the scheduled collection date, the product amount, and the purchasing employee when the collection method is payroll deduction (step S101). Specifically, as shown in FIG. 4, the sales acquisition unit 102a acquires a sales data table T1 from the store and the Web system. The sales data table T1 shown in FIG. 4 stores the sales date, customer, collection method, scheduled collection date, amount, and statement summary (employee number and employee name) for each statement. For example, when a product is sold to an employee of a group company, the statement K1 stores the sales date as "11 / 1", the customer as "Company A", the collection method as "deduction", the scheduled collection date as "12 / 20", the amount as "1,000 yen", and the statement summary (employee number and employee name) as "1001 Suzuki". On the other hand, if the product is not sold to an employee of a group company (for example, in the case of a bank transfer), the details K2 will show the sales date as "11 / 3", the customer as "Company C", the collection method as "bank transfer", the planned collection date as "12 / 20", and the amount as "3,000 yen". In other words, the details summary for details K2 is blank.

[0036] The sales acquisition unit 102a then creates collection schedule data that sets the collection method (payroll deduction, transfer slip, or invoice transfer), group company, scheduled collection date, and product amount (step S102). Specifically, as shown in Fig. 5, the sales acquisition unit 102a creates a collection schedule data table T2. The collection schedule data table T2 shown in Fig. 5 stores the scheduled collection dates and amounts for each of deduction, invoice transfer, and transfer slip.

[0037] Then, when the collection method set in the scheduled collection data is payroll deduction, the deduction creation unit 102b creates the purchasing employee's deduction data (step S103). Specifically, as shown in Fig. 6, the deduction creation unit 102b creates the purchasing employee's deduction data table T3 by extracting data whose collection method is payroll deduction from among the data included in the scheduled collection data. In this case, the deduction creation unit 102b creates the deduction data table T3 by associating the payroll deduction data extracted from the scheduled collection data with the purchasing employee's employee number, name, etc., by referring to the sales data table T1.

[0038] Then, the deduction creation unit 102b transmits the deduction data created in step S103 to the payroll system of the group company to which the purchasing employee belongs (step S104). Specifically, the deduction creation unit 102b transmits the deduction data table T3 shown in FIG. 6 to the payroll system (e.g., server 200) of the group company to which the purchasing employee belongs via the communication interface unit 104 and the network 300.

[0039] Then, the deposit reconciliation unit 102d creates deposit reconciliation data for the sales data based on the deposit data and the collection schedule data (step S105). Specifically, as shown in Fig. 7 and Fig. 8, the deposit reconciliation unit 102d creates a deposit reconciliation data table T5 for the sales data based on the deposit data table T4 and the collection schedule data table T2 shown in Fig. 2.

[0040] According to the embodiment described above, claims management and settlement processing can be performed for both invoice transfers and payroll deductions in the same operation.

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

[0042] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of goals 12, 13, and 15 of the SDGs.

[0043] Furthermore, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.

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

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

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

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

[0048] For example, the processing functions of the claim management device 100, particularly the processing functions performed by the control unit, 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 contains 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 the control unit.

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

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

[0051] 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 distributed configuration as multiple modules or libraries, and a program that works with a separate program, such as an OS, to achieve its function. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in the embodiments, as well as the installation procedure after reading, may use well-known configurations and procedures.

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

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

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

[0055] The present invention is useful in industries where sales operations include sales to employees of the same company or employees of the same group companies (for example, the food industry). [Explanation of symbols]

[0056] 100 Credit management device 102 Control section 102a Sales Acquisition Department 102b Tax Deduction Creation Department 102c Deposit Collection Section 102d Payment Clearing Department 104 Communication interface section 106 Storage section 106a Sales Data 106b Data to be collected 106c Withholding data 106d Deposit data 106e Receipt reconciliation data 108 Input / Output Interface Section 112 Input Devices 114 Output Device 200 Server device 300 Network

Claims

1. A claim management device including a memory unit and a control unit, The control unit is a sales acquisition means for acquiring from the store and the Web system sales data including external sales and internal sales when a product that can be sold internally to employees of the company or employees of the company's group companies is sold to employees of the company or the group companies, the sales data setting the collection method being payroll deduction, transfer slip, invoice transfer or cash, the group company, the scheduled collection date, the product amount, and the purchasing employee in the case where the collection method is payroll deduction, and creating scheduled collection data setting the collection method being payroll deduction, transfer slip or invoice transfer, the group company, the scheduled collection date, and the product amount; a deduction creation means for creating deduction data for the purchasing employee and transmitting the deduction data to a payroll system of the group company to which the purchasing employee belongs, when the collection method set in the collection schedule data is payroll deduction; a deposit acquisition means for acquiring deposit data that includes the group company, the deposit date, and the deposit amount; a deposit reconciliation means for creating deposit reconciliation data for the sales data based on the deposit data and the collection schedule data; A claim management device comprising:

2. The sales data is stored in association with the employee number and / or name of the purchasing employee.

2. The claim management device according to claim 1.

3. A claim management method executed by a claim management device having a memory unit and a control unit, Executed by the control unit, a sales acquisition step of acquiring sales data including external sales and internal sales when a product that can be sold internally to employees of the company or group companies of the company is sold to employees of the company or group companies from the store and the Web system, the sales data setting the collection method which is payroll deduction, transfer slip, invoice transfer or cash, the group company, the scheduled collection date, the product amount, and the purchasing employee if the collection method is payroll deduction, and creating scheduled collection data setting the collection method which is payroll deduction, transfer slip or invoice transfer, the group company, the scheduled collection date, and the product amount; a deduction creation step of creating deduction data for the purchasing employee and transmitting it to a payroll system of the group company to which the purchasing employee belongs, when the collection method set in the collection schedule data is payroll deduction; a deposit acquisition step of acquiring deposit data that includes the group company, the deposit date, and the deposit amount; a deposit reconciliation step of creating deposit reconciliation data for the sales data based on the deposit data and the collection schedule data; A method for managing claims, comprising:

4. A claim management program to be executed by a claim management device having a memory unit and a control unit, To be executed by the control unit, a sales acquisition step of acquiring sales data including external sales and internal sales when a product that can be sold internally to employees of the company or group companies of the company is sold to employees of the company or group companies from the store and the Web system, the sales data setting the collection method which is payroll deduction, transfer slip, invoice transfer or cash, the group company, the scheduled collection date, the product amount, and the purchasing employee if the collection method is payroll deduction, and creating scheduled collection data setting the collection method which is payroll deduction, transfer slip or invoice transfer, the group company, the scheduled collection date, and the product amount; a deduction creation step of creating deduction data for the purchasing employee and transmitting it to a payroll system of the group company to which the purchasing employee belongs, when the collection method set in the collection schedule data is payroll deduction; a deposit acquisition step of acquiring deposit data that includes the group company, the deposit date, and the deposit amount; a deposit reconciliation step of creating deposit reconciliation data for the sales data based on the deposit data and the collection schedule data; A receivables management program comprising:

Images