JP7572918B2 - Claims management device, claims management method, and claims management program - Google Patents

Description

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

Patent Document 1 discloses a technology in which, when a change occurs to the combination pattern of business partners in the business flow of an account transaction, multiple pieces of business partner identification information for identifying each of the multiple business partners that match the extraction conditions of the user operation are extracted from the next-branch management business flow pattern master, displayed on an update required screen, and updated collectively to the changed destination of the user operation.

JP 2021-28787 A

In general accounts receivable management, the common configuration is that there are multiple customers (1:N (N = an integer of 2 or more)) whose sales records are managed for each billing destination that manages accounts receivable.

However, in the hairdressing and beauty industry, such as beauty salons, there are cases where a customer beauty salon is billed for the salon's business, where a wholesale is made to the beauty salon for purposes other than the salon's normal business and then billed to the beauty salon, and where a wholesale is made to an individual employed at the beauty salon for personal use by a clerk (staff member) working at the salon and then billed. For this reason, unlike the general accounts receivable management configuration (1:N), the hairdressing and beauty industry needs to manage multiple billing destinations as a single customer (N:1). However, this is not taken into consideration in the above-mentioned Patent Document 1, which causes the problem of cumbersome input of orders or sales.

The present invention has been made in consideration of the above, and aims to provide a receivables management device, a receivables management method, and a receivables management program that allow easy selection of input of orders or sales, even when managing multiple billing destinations as a single customer.

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 control unit, and is capable of accessing a billing category type master that manages multiple billing category types to which numerical values are assigned in advance in order to link a customer with multiple billing destinations, a billing destination master that manages receivables by linking billing destination information related to the multiple billing destinations and any one of the multiple billing category types to customer information related to the customer, and a customer master that links the customer information and billing destination consolidated information that collectively manages the multiple billing destinations, and the control unit is characterized by having an identification means that refers to the billing category type master, the billing destination master, and the customer master, and identifies the billing destination information linked to the billing category type to which the smallest value is assigned based on the customer information entered on the order input screen of the slip, and a display control means that displays the identified billing destination information on the order input screen.

The method of managing accounts receivable according to the present invention is executed by an accounts receivable management device having a control unit, and is capable of accessing a billing category type master that manages multiple billing category types to which numerical values are assigned in advance in order to link a customer with multiple billing destinations, a billing destination master that manages accounts receivable by linking billing destination information related to the multiple billing destinations and any one of the multiple billing category types to customer information related to the customer, and a customer master that links the customer information and billing destination consolidated information that collectively manages the multiple billing destinations, and is characterized by including a specification step executed by the control unit, which refers to the billing category type master, the billing destination master, and the customer master, and identifies the billing destination information linked to the billing category type to which the smallest value is assigned based on the customer information entered on the order input screen of the slip, and a display control step that displays the identified billing destination information on the order input screen.

The receivables management program according to the present invention is a receivables management program executed by a receivables management device having a control unit, and is capable of accessing a billing category type master that manages multiple billing category types to which numerical values are assigned in advance in order to link a customer with multiple billing destinations, a billing destination master that manages receivables by linking billing destination information related to the multiple billing destinations and any one of the multiple billing category types to customer information related to the customer, and a customer master that links the customer information and billing destination consolidated information that collectively manages the multiple billing destinations, and the control unit includes a specification step of referring to the billing category type master, the billing destination master, and the customer master, and identifying the billing destination information linked to the billing category type to which the smallest value is assigned based on the customer information entered on the order input screen of the slip, and a display control step of displaying the identified billing destination information on the order input screen.

The present invention has the advantage that even when managing multiple billing destinations as one customer, it is easy to select the input of orders or sales.

FIG. 1 is a schematic diagram showing an overview in a block diagram of an example of the configuration of a claim management device according to an embodiment. FIG. 2 is a diagram showing an example of a billing category data table in the billing category master according to the embodiment. FIG. 3 is a diagram showing an example of a billing destination data table in the billing destination master according to the embodiment. FIG. 4 is a diagram illustrating an example of a customer data table in the special customer master according to the embodiment. FIG. 5 is a flowchart showing an outline of the processing executed by the claim management device according to the embodiment. FIG. 6 is a diagram showing an example of an order input screen. FIG. 7 is a diagram showing an example of an order input screen. FIG. 8 is a diagram showing an example of an order input screen. FIG. 9 is a diagram showing an example of an order input screen. FIG. 10 is a diagram showing an example of the billing destination search screen. FIG. 11 is a diagram showing an example of the order input screen.

Below, an embodiment 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 drawings. Note that the present invention is not limited to this embodiment.

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

The receivables management device 100 shown in FIG. 1 is a commercially available desktop personal computer. Note that the receivables 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, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.

The claim management device 100 includes a control unit 102, a communication interface unit 104, a memory unit 106, and an input/output interface unit 108. Each unit of the claim management device 100 is connected to each other so as to be able to communicate with each other via any communication path.

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.

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 works with a mouse to provide 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.

The memory unit 106 stores various databases, tables, files, and the like. The memory unit 106 records computer programs that work with the OS (Operating System) to give instructions to the CPU (Central Processing Unit) to perform various processes. The memory unit 106 can be, for example, a memory device such as a RAM (Random Access Memory) or a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, or an optical disk. The memory unit 106 stores a billing category type master 106a, a billing destination master 106b, and a customer master 106c.

The billing category type master 106a manages multiple billing category types to which numerical values are assigned in advance in order to link a customer with multiple billing recipients.

Figure 2 is a diagram showing an example of a billing category data table in the billing category master 106a. In the category data table T1 shown in Figure 2, billing category information (billing section type code) indicating a billing category type to which a numerical value is assigned in advance and a billing section type name are stored in a corresponding state. For example, as shown in Figure 2, the first column of the category data table T1 holds the billing category type code "1" as the billing category type information and the billing category type name "business" in a corresponding state. Furthermore, as shown in Figure 2, the second column of the category data table T1 holds the billing category type code "2" as the billing category type information and the billing category type name "separate account" in a corresponding state. Furthermore, the third column of the category data table T1 holds the billing category type code "9" as the billing category type information and the billing category type name "individual" in a corresponding state. Here, business refers to major transactions, for example, regular business. Specifically, a business basically refers to one beauty salon with one billing destination. A separate account refers to transactions other than the main business, such as esthetics, nails, miscellaneous items, and equipment. Specifically, a separate account refers to a case where multiple billing destinations are linked to one beauty salon. Furthermore, an individual refers to a transaction with a hairdresser who belongs to a beauty salon. Specifically, an individual refers to a case where multiple billing destinations are linked to each of multiple beauty salons that belong to one beauty salon.

The billing destination master 106b manages accounts receivable by linking billing destination information for multiple billing destinations and one of multiple billing classification types to customer information for customers.

Figure 3 is a diagram showing an example of a billing destination data table in the billing destination master 106b. The billing destination data table T2 shown in Figure 3 stores billing destination information (billing destination codes) for multiple billing destinations, billing destination names, one of multiple billing category types (billing category type codes), and customer information (customer codes) for customers in a linked state. For example, as shown in Figure 3, the first column of the billing destination data table T2 stores the billing destination code "45210-101" as billing destination information, the billing destination name "business", the billing category type code "1" as billing category type information, and the customer code "45210" as customer information in a linked state.

Customer master 106c manages sales performance by linking customer information with billing destination consolidated information that collectively manages multiple billing destinations.

Figure 4 is a diagram showing an example of a customer data table in the customer master 106c. In the first column of the customer data table T3 shown in Figure 4, the customer code "45210" as customer information, the customer name "Salon XXX", and the billing collective code "45210" as billing collective information are stored in a linked state.

Returning to FIG. 1, the description of the configuration of the claim management device 100 will continue.
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 an identification unit 102a, a determination unit 102b, and a display control unit 102c.

The identification unit 102a refers to the billing category type master 106a, billing destination master 106b, and customer master 106c, and identifies the billing destination information (billing destination code) linked to the billing category type to which the smallest value is assigned, based on the customer information (customer code) entered on the order input screen of the invoice.

When the billing category type displayed on the order entry screen is changed, the determination unit 102b refers to the billing destination master 106b and determines whether there are multiple billing category types.

The display control unit 102c displays the billing information identified by the identification unit 102a on the order input screen on the output device 114. When the billing category type displayed on the order input screen is changed and the determination unit 102b determines that there are multiple billing category types, the display control unit 102c refers to the billing master 106b and displays a billing search screen including multiple billing information linked to customer information on the output device 114. When one of the multiple billing information on the billing search screen is selected, the display control unit 102c switches from the billing search screen to the order input screen and displays it, and displays the billing information selected by the user on the order input screen. The display control unit 102c also displays the billing category type name related to the billing category type linked to the billing information identified by the identification unit 102a and the customer name related to the customer on the order input screen.

2. Processing Executed by the Claim Management Device 100
Next, a description will be given of the processing executed by the claim management device 100. FIG.

As shown in FIG. 5, first, the display control unit 102c displays the order input screen on the output device 114 by outputting the order input screen on the output device 114 in response to the user's operation of the input device 112 (step S101).

Figure 6 is a diagram showing an example of an order input screen. The order input screen P1 shown in Figure 6 includes an order number input area m1 that can accept input of an order number, an order date input area m2 that can accept input of an order date, a shipping date input area m3 that can accept input of a shipping date, a customer input area m4 that can accept input of customer information, a billing category type area m5 that can accept input of a billing category type, and a billing information display area m6 that displays billing information. Furthermore, the order input screen P1 includes a customer display area m11 where the customer name is displayed according to the customer information, and a billing display area m12 where the billing name is displayed. Furthermore, the order input screen P1 includes a product area m21 that includes the product name, sales volume, unit price, and amount of the ordered product.

Returning to FIG. 5, the description of step S102 and subsequent steps will be continued.
In step S102, the judgment unit 102b judges whether or not customer information has been input into the customer input area m4 by the user operating the input device 112. If the judgment unit 102b judges that customer information has been input into the customer input area m4 (step S102: Yes), the claim management device 100 proceeds to step S103, which will be described later. On the other hand, if the judgment unit 102b judges that customer information has not been input into the customer input area m4 (step S102: No), the claim management device 100 proceeds to step S111, which will be described later.

Then, the identification unit 102a acquires the customer information entered in the customer input area m4 (step S103), and refers to the billing category type master 106a, the billing destination master 106b, and the customer master 106c to identify the billing destination information linked to the billing category type to which the smallest value is assigned (step S104). Specifically, as shown in FIG. 7, when the customer information entered in the customer input area m4 is "45210", the identification unit 102a refers to the billing destination master 106b and identifies the business "45210-101" in the billing destination master 106b as the billing destination information linked to the billing category type to which the smallest value is assigned (see the billing destination data table T2 in FIG. 3).

Then, the display control unit 102c displays the billing information to which the minimum value specified by the specification unit 102a is assigned on the order input screen P1 (step S105). Specifically, as shown in FIG. 8, the display control unit 102c displays "1" in the billing category type area m5 of the order input screen P1 as the billing category type to which the minimum value specified by the specification unit 102a is assigned. In this case, the display control unit 102c initially sets the billing information that uniquely determines the billing information holding the billing category type information, specifically "45210-101", to be displayed in the billing information display area m6 of the order input screen P1. Furthermore, the display control unit 102c displays the customer name "Salon A" related to the customer in the customer display area m11, and the billing name "Business" in the billing display area m12. This allows the user to easily select input of orders or sales, even when managing multiple billing destinations as one customer.

Then, the judgment unit 102b judges whether the billing category type has been changed by the user operating the input device 112 (step S106). Specifically, as shown in FIG. 9, the judgment unit 102b judges whether the billing category type has been changed from "1" to "2" by the user operating the input device 112. If the judgment unit 102b judges that the billing category type has been changed by the user operating the input device 112 (step S106: Yes), the receivables management device 100 proceeds to step S107, which will be described later. On the other hand, if the judgment unit 102b judges that the billing category type has not been changed by the user operating the input device 112 (step S106: No), the receivables management device 100 proceeds to step S111, which will be described later.

In step S107, the judgment unit 102b refers to the billing destination master 106b and judges whether or not there are multiple billing category types input by the user by operating the input device 112. If the judgment unit 102b judges that there are multiple billing category types input by the user by operating the input device 112 (step S107: Yes), the receivables management device 100 proceeds to step S108, which will be described later. On the other hand, if the judgment unit 102b judges that there are not multiple billing category types input by the user by operating the input device 112 (step S107: No), the receivables management device 100 proceeds to step S110, which will be described later.

In step S108, the display control unit 102c refers to the billing destination master 106b and the customer master 106c, and outputs a billing destination search screen including multiple billing destinations linked to the customer information to the output device 114, thereby displaying the billing destination search screen on the output device 114.

Figure 10 is a diagram showing an example of a billing destination search screen. The billing destination search screen P2 shown in Figure 10 includes a search result screen K1 that includes multiple billing destinations linked to customer information. This search result screen K1 includes billing destination codes "45210-201," "45210-202," and "45210-203" as multiple billing destination information for multiple billing destinations linked to customer code "45210" as customer information. This allows the user to select the desired billing destination by operating the input device 112 while viewing the billing destination search screen P2 displayed by the output device 114.

Returning to FIG. 5, the description of step S109 onward will be continued.
In step S109, the judgment unit 102b judges whether or not the user has selected one of the multiple billing destinations by operating the input device 112. If the judgment unit 102b judges that the user has selected one of the multiple billing destinations by operating the input device 112 (step S109: Yes), the claim management device 100 proceeds to step S110, which will be described later. On the other hand, if the judgment unit 102b judges that the user has not selected one of the multiple billing destinations by operating the input device 112 (step S109: No), the claim management device 100 returns to step S108, which has been described above.

In step S110, the display control unit 102c displays the billing information selected by the user by operating the input device 112 on the order entry screen P1. For example, as shown in FIG. 11, when the user operates the input device 112 to select the billing code "45210-201" and the billing name "Esthetic" as billing information from the search result screen K1 in FIG. 10, the display control unit 102c displays the order entry screen P3 according to the selection result. This allows the user to easily select input of orders or sales, even when managing multiple billing destinations as a single customer.

Then, the determination unit 102b determines whether or not the user has performed an end operation by operating the input device 112 (step S111). If the determination unit 102b determines that the user has performed an end operation by operating the input device 112 (step S111: Yes), the receivable management device 100 ends this process. On the other hand, if the determination unit 102b determines that the user has not performed an end operation by operating the input device 112 (step S111: No), the receivable management device 100 returns to the above-mentioned step S106.

According to the embodiment described above, the identification unit 102a refers to the billing category type master 106a, billing destination master 106b, and customer master 106c, and identifies the billing destination information (billing destination code) linked to the billing category type to which the smallest value is assigned based on the customer information (customer code) entered on the order input screen P1 of the invoice, and the display control unit 102c displays the billing destination information identified by the identification unit 102a on the order input screen P1 (see Figure 8) on the output device 114. Therefore, even when multiple billing destinations are managed as one customer, it is easy to select the input of orders or sales.

Furthermore, according to the embodiment, when the billing category type displayed on the order input screen P1 is changed and the determination unit 102b determines that there are multiple billing category types, the display control unit 102c refers to the billing destination master 106b and displays the billing destination search screen P2, which includes multiple billing destination information linked to the customer information, on the output device 114. This allows the user to intuitively grasp multiple billing destinations.

Furthermore, according to the embodiment, when one of the multiple billing destination information is selected on the billing destination search screen P2, the display control unit 102c switches the display from the billing destination search screen P2 (see FIG. 10) to the order entry screen P3 (see FIG. 11), and displays the billing destination information selected by the user on the order entry screen P3. This allows the user to easily enter orders or sales for the selected billing destination.

In addition, according to the embodiment, the display control unit 102c displays the billing category type name related to the billing category type and the customer name related to the customer linked to the billing destination information identified by the identification unit 102a on the order input screen P1 (see FIG. 8), so that the user can intuitively grasp the billing category type and customer name of the selected billing destination.

[3. 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 making it possible to contribute to goals 8 and 9 of the SDGs.

In addition, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, which can contribute to the achievement of SDGs goals 12, 13, and 15.

In addition, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.

4. 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.

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 a known method.

In addition, the processing procedures, control procedures, specific names, registered data for each process, information including search conditions and other parameters, screen examples, and database configurations shown in this specification and drawings may be changed as desired unless otherwise specified.

Furthermore, with regard to the debt management device 100, each component shown in the figure is a functional concept and does not necessarily have to be physically configured as shown in the figure.

For example, the processing functions of the receivable 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 receivable management device 100 as necessary. That is, a computer program is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive) for working with the OS to give instructions to the CPU and perform various processes. This computer program is executed by being loaded into RAM, and works with the CPU to form the control unit.

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 needed.

In addition, the program for executing the processing described in this embodiment may be stored on a non-transitory computer-readable recording medium, or may be configured as a program product. Here, the term "recording medium" refers to a memory card, a USB (Universal Serial Bus) memory, a SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), an EEPROM (registered trademark) (Electrically Erasable and Programmable Read Only Memory), a CD-ROM (Compact Disk Read Only Memory), an MO (Magneto-Optical disk), a DVD (Digital Versatile This includes any "portable physical media" such as a Blu-ray (registered trademark) Disc, and a Blu-ray (registered trademark) Disc.

A "program" is a data processing method written in any language or description method, and may be in any format, 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 consisting of multiple modules or libraries, and a program that works in conjunction 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, can use well-known configurations and procedures.

The various databases stored in the memory unit are storage devices such as RAM, ROM, etc., 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 providing websites.

The receivables 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 receivables management device 100 may also be realized by implementing software (including programs or data, etc.) that causes the device to realize the processing described in this embodiment.

Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the figures, and all or part of them can be functionally or physically distributed and integrated in any unit depending on 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.

This invention is useful in industries such as hairdressing and beauty, and cosmetics, where multiple billing destinations are managed by a single customer.

REFERENCE SIGNS LIST 100 Debt management device 102 Control unit 102a Identification unit 102b Determination unit 102c Display control unit 104 Communication interface unit 106 Storage unit 106a Billing category type master 106b Billing destination master 106c Customer master 108 Input/output interface unit 112 Input device 114 Output device 200 Server 300 Network

Claims (6)

A claim management device including a control unit,
A billing category master that manages multiple billing category types to which numerical values are assigned in advance in order to link a customer with multiple billing destinations;
a billing destination master for managing claims by linking billing destination information related to the plurality of billing destinations and any one of the plurality of billing classification types to customer information related to the customer;
A customer master that links the customer information with billing destination collective information that collectively manages the multiple billing destinations;
is accessible to
The control unit is
a specifying means for referring to the billing category type master, the billing destination master, and the customer master, and specifying the billing destination information linked to the billing category type to which a minimum value is assigned based on the customer information entered on the order entry screen of the slip;
a display control means for displaying the specified billing information on the order entry screen;
To have
A debt management device comprising: a determination means for determining whether or not there are a plurality of billing classification types by referring to the billing destination master when the billing classification type displayed on the order input screen is changed;
The display control means
When the billing category type displayed on the order input screen is changed and the determination means determines that there are a plurality of billing category types, the billing master is referenced and a billing destination search screen including the plurality of billing destination information linked to the customer information is displayed.
2. The claim management device according to claim 1. The display control means
when any one of the plurality of billing information is selected on the billing search screen, switching from the billing search screen to the order entry screen and displaying the selected billing information on the order entry screen;
3. The claim management device according to claim 2. The display control means
a billing category name related to the billing category type and a customer name related to the customer linked to the specified billing destination information are displayed on the order entry screen.
4. The claim management device according to claim 1, wherein the claim management device is a device for managing claims. A claim management method executed by a claim management device having a control unit,
A billing category master that manages multiple billing category types to which numerical values are assigned in advance in order to link a customer with multiple billing destinations;
a billing destination master for managing claims by linking billing destination information related to the plurality of billing destinations and any one of the plurality of billing classification types to customer information related to the customer;
A customer master that links the customer information with billing destination collective information that collectively manages the multiple billing destinations;
is accessible to
Executed by the control unit,
a step of referring to the billing category type master, the billing destination master, and the customer master, and identifying the billing destination information associated with the billing category type to which a minimum value is assigned, based on the customer information entered on the order entry screen of the slip;
a display control step of displaying the specified billing information on the order entry screen;
That includes
A receivables management method comprising: A claim management program executed by a claim management device having a control unit,
A billing category master that manages multiple billing category types to which numerical values are assigned in advance in order to link a customer with multiple billing destinations;
a billing destination master for managing claims by linking billing destination information related to the plurality of billing destinations and any one of the plurality of billing classification types to customer information related to the customer;
A customer master that links the customer information with billing destination collective information that collectively manages the multiple billing destinations;
is accessible to
The control unit is
a step of referring to the billing category type master, the billing destination master, and the customer master, and identifying the billing destination information associated with the billing category type to which a minimum value is assigned, based on the customer information entered on the order entry screen of the slip;
a display control step of displaying the specified billing information on the order entry screen;
containing,
A receivables management program featuring:

Images