Information processing device, information processing method, and program

Abstract

To provide a device, a method, and a program that can obtain a money quickly even when no requested amount is transferred by a transfer deadline even after sending a bill to a customer.SOLUTION: In an information processing system, an acquisition part of an information processor (server 100) acquires bill data. A display control part controls so that the acquired bill data is displayed on a screen. The screen includes a first object to which factoring regarding the bill data can be requested. A transmission part transmits bill data related to the first object to a system of factoring to request the factoring when the first object is selected.SELECTED DRAWING: Figure 4

Description

[Technical field]

[0001] The present invention relates to an information processing device, an information processing method, and a program. [Background technology]

[0002] Patent Document 1 discloses a device for automatically creating invoices. [Prior art documents] [Patent documents]

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

[0004] Even if an invoice is sent to a customer, the invoice amount may not be transferred by the due date. [Means for solving the problem]

[0005] According to one aspect of the present invention, there is provided an information processing device. The information processing device has a control unit. The control unit acquires invoice data. The control unit controls so as to display the acquired invoice data on a screen. The screen includes a first object for which factoring can be requested for the invoice data. When the first object is selected, invoice data related to the first object is transmitted to a factoring system to request factoring. [Brief description of the drawings]

[0006] [Figure 1] FIG. 1 is a diagram illustrating an example of a system configuration of an information processing system. [Diagram 2] FIG. 2 is a diagram illustrating an example of a hardware configuration of the server device. [Diagram 3]FIG. 3 is a diagram illustrating an example of a hardware configuration of the client device. [Figure 4] FIG. 4 is a diagram illustrating an example of a functional configuration of the server device. [Diagram 5] FIG. 5 is an activity diagram showing an example of information processing in the server device. [Figure 6] FIG. 6 is a diagram (part 1) showing an example of the display screen. [Figure 7] FIG. 7 is a diagram illustrating an example of a system configuration of an information processing system according to the first modification. [Figure 8] FIG. 8 is a diagram showing an example of a display screen of the first modified example. [Figure 9] FIG. 9 is a diagram illustrating an example of a functional configuration of a server device according to the second modification. [Figure 10] FIG. 10 is a diagram illustrating an example of a functional configuration of a server device according to the third modification. [Figure 11] FIG. 11 is a diagram illustrating an example of a functional configuration of a server device according to the fourth modification. [Figure 12] FIG. 12 is a diagram showing an example of a display screen of the fourth modified example. [Figure 13] FIG. 13 is a diagram illustrating an example of a functional configuration of a server device according to the fifth modification. In FIG. [Figure 14] FIG. 14 is a diagram showing an example of a display screen of the fifth modified example. [Figure 15] FIG. 15 is a diagram illustrating an example of a functional configuration of a server device according to the sixth modification. In FIG. [Figure 16] FIG. 16 is a diagram showing an example of a display screen of the sixth modification. [Figure 17] FIG. 17 is a diagram illustrating an example of a functional configuration of a server device according to the seventh modification. In FIG. [Figure 18] FIG. 18 is a diagram showing an example of a display screen of the seventh modification. [Figure 19] FIG. 19 is a diagram showing an example of a display screen of the eighth modified example. [Figure 20] FIG. 20 is a diagram showing an example of a display screen of the ninth modification. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0007] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, embodiments of the present invention will be described with reference to the drawings. Various characteristic features shown in the following embodiments can be combined with each other.

[0008] In this specification, the term "unit" may include, for example, a combination of hardware resources implemented by a circuit in the broad sense and software information processing that can be specifically realized by these hardware resources. In addition, various information is handled in this embodiment, and this information is represented by high and low signal values ​​as a binary bit collection consisting of 0 or 1, and communication and calculation can be performed on the circuit in the broad sense.

[0009] In addition, a circuit in the broad sense is a circuit realized by at least appropriately combining a circuit, circuitry, a processor, a memory, etc. In other words, it includes an application specific integrated circuit (ASIC), a programmable logic device (e.g., a simple programmable logic device (SPLD), a complex programmable logic device (CPLD), and a field programmable gate array (FPGA)), etc.

[0010] <Embodiment 1> 1. System Configuration FIG. 1 is a diagram showing an example of a system configuration of an information processing system 1000. As shown in FIG. 1, the information processing system 1000 includes, as a system configuration, a server device 100, a client device 110, and a server device 120. The server device 100 is a server device that executes the processing of this embodiment. The client device 110 is a device used by a user, such as a PC (Personal Computer). The server device 120 is a server device of a company that provides factoring services. Here, factoring refers to a service of purchasing accounts receivable and collecting the accounts receivable. The server device 100, the client device 110, and the server device 120 are connected to each other via a network 150 so as to be able to communicate with each other.

[0011] 1, for the sake of simplicity, only one client device 110 is illustrated in the information processing system 1000. However, the information processing system 1000 includes as many client devices 110 as the number of users registered in the information processing system 1000. In addition, the client device 110 is not limited to a PC, and may be a tablet computer, a smartphone, or the like. The server device 100 is an example of an information processing device.

[0012] 2. Hardware Configuration (1) Hardware Configuration of Server Device 100 FIG. 2 is a diagram showing an example of a hardware configuration of the server device 100. The server device 100 includes, as a hardware configuration, a control unit 201, a storage unit 202, and a communication unit 203. The control unit 201 is a CPU (Central Processing Unit) or the like, and controls the entire server device 100. The storage unit 202 is a HDD (Hard Disk Drive), a ROM (Read Only Memory), a RAM (Random Access Memory), an SSD (Solid State Drive), or any combination thereof, and stores a program and data used when the control unit 201 executes processing based on the program. The control unit 201 executes processing based on the program stored in the storage unit 202, thereby realizing functions of the server device 100 as shown in FIG. 4, FIG. 9 to FIG. 11, FIG. 13 to FIG. 14, and FIG. 16 described later, and processing of an activity diagram as shown in FIG. 5 described later, and the like. The communication unit 203 is a NIC (Network Interface Card) or the like, which connects the server device 100 to the network 150 and controls communication with other devices (for example, the client device 110 and the server device 120, etc.) The storage unit 202 is an example of a storage medium. The hardware configuration of server device 120 is also similar to that of server device 100. The control unit of server device 120 executes processes based on programs stored in the storage unit of server device 120, thereby realizing the functions of server device 120.

[0013] (2) Hardware Configuration of the Client Device 110 FIG. 3 is a diagram showing an example of a hardware configuration of the client device 110. The client device 110 includes, as a hardware configuration, a control unit 301, a storage unit 302, an imaging unit 303, an input unit 304, an output unit 305, and a communication unit 306. The control unit 301 is a CPU or the like, and controls the entire client device 110. The storage unit 302 is a ROM, a RAM, an SSD, or any combination thereof, and stores a program and data used when the control unit 301 executes processing based on the program. The control unit 301 executes processing based on the program stored in the storage unit 302, thereby realizing functions of the client device 110. The imaging unit 303 is a camera or the like, and captures an image of a subject. The input unit 304 is a keyboard, a mouse, or the like, and inputs information to the control unit 301 in response to a user operation. The output unit 305 is a display or the like, and outputs the results of processing by the control unit 301. The communication unit 306 is a NIC or the like, which connects the client device 110 to the network 150 and controls communication with other devices (for example, the server device 100).

[0014] 3. Functional configuration 4 is a diagram showing an example of the functional configuration of the server device 100. The server device 100 includes an acquisition unit 401, a display control unit 402, and a transmission unit 403 as its functional configuration.

[0015] (Acquisition section 401) The acquisition unit 401 acquires bill data. The acquisition unit 401 may acquire bill data from the storage unit 202, or may acquire bill data from a data storage server device or the like that can communicate via the network 150. More specifically, when the acquisition unit 401 receives a display request for bill data from the client device 110, it acquires bill data corresponding to the display request. Here, if "all" is included as the display request, the acquisition unit 401 acquires all bill data as bill data corresponding to the display request. Also, if "creation date of bill data" is included as the display request, the acquisition unit 401 acquires bill data created on the creation date specified as the bill data corresponding to the display request. As another example, if "company name" is included as the display request, the first acquisition unit 401 may acquire bill data including the "company name" specified as the bill data corresponding to the display request. Similarly, instead of "company name", "amount" or the like may be used.

[0016] (Display control unit 402) The display control unit 402 controls the display of the acquired invoice data on the output unit 305 of the client device 110 that sent the display request. Examples of screens displayed by the display control unit 402 will be described below with reference to Figs. 6, 8, 12, 15, and 17. For example, as shown in Fig. 6, the screen includes a factoring button 610, a factoring button 620, a factoring button 630, and a factoring button 640 that allow factoring of the invoice data to be requested. The factoring button is an example of a first object. In this embodiment, an example is described in which a factoring button, etc. is displayed on a screen that displays invoice data. However, the display control unit 402 may display a factoring button, etc. in association with an invoice on a screen for managing receivables.

[0017] (Transmitter 403) When the factoring button is selected, the transmission unit 403 transmits invoice data related to the factoring button to the server device 120 and requests factoring. For example, when the factoring button 620 in Fig. 6 is selected, the transmission unit 403 transmits invoice data related to the accelerated examination fee to XX Co., Ltd. as invoice data related to the factoring button 620 to the server device 120 and requests factoring. The server device 120 is an example of a factoring system.

[0018] 4. Information Processing FIG. 5 is an activity diagram showing an example of information processing in the server device 100. As shown in FIG. In A501, the acquisition unit 401 determines whether or not a display request for invoice data has been received from the client device 110. If the acquisition unit 401 determines that a display request has been received, the process proceeds to A502. If the acquisition unit 401 determines that a display request has not been received, the process of A501 is repeated.

[0019] In A502, the acquisition unit 401 acquires bill data. More specifically, the acquisition unit 401 acquires one or more bill data items corresponding to the display request. In A503, the display control unit 402 controls the client device 110 to display the invoice data acquired by the acquisition unit 401 on the screen of the client device 110. FIG. 6 is a diagram (part 1) showing one example of a display screen. The display screen is a screen that is displayed on the client device 110 in response to a request to display invoice data. As shown in FIG. 6, the display screen includes a list of invoices that meet the search criteria included in the display request and an invoice selected from the list of invoices. The display screen also includes a factoring button 610, a factoring button 620, a factoring button 630, and a factoring button 640. The factoring button 610, the factoring button 620, and the factoring button 630 are each buttons for requesting factoring for a corresponding invoice from the list of invoices. The factoring button 640 is a button for requesting factoring for an invoice from an invoice selected from the list of invoices.

[0020] In A504, the display control unit 402 determines whether or not the factoring button has been selected on the display screen. If the display control unit 402 determines that the factoring button has been selected on the display screen, the display control unit 402 advances the process to A505. If the display control unit 402 determines that the factoring button has not been selected on the display screen, the display control unit 402 returns the process to A503. In A505, the sending unit 403 sends the invoice data related to the selected factoring button to the server device 120 and requests factoring. For example, upon receiving the factoring request, the server device 120 requests the corresponding account receivable company to accept the factoring contract. When the account receivable company accepts the factoring contract, the server device 120 makes a payment of the account receivable amount due to factoring to the server device 100.

[0021] As another example, when the factoring button is selected, the display control unit 402 may display a screen on the client device 110 to confirm whether or not the accounts receivable related to the invoice may be sold to a factoring company. Then, when it is selected on the displayed screen that the accounts receivable related to the invoice may be sold to a factoring company, the sending unit 403 may send invoice data related to the selected factoring button to the server device 120 and request factoring. As yet another example, when the factoring button is selected, the sending unit 403 may send an email or the like to the account receivable company regarding the invoice, requesting acceptance of the factoring contract. Then, when the account receivable company accepts the factoring contract, the sending unit 403 may send the invoice data related to the selected factoring button to the server device 120 and request factoring.

[0022] According to the process of this embodiment, a factoring button for requesting factoring is displayed on the screen displaying invoice data, so when a user wants to request factoring, he or she only has to select the factoring button. If the user requests factoring, the fee is deducted, but this saves the time involved in communicating with customers who are slow to remit the invoice amount, and allows the user to receive the money immediately.

[0023] (Variation 1) A modification of the first embodiment will be described. FIG. 7 is a diagram showing an example of a system configuration of an information processing system 1000 of the first embodiment. The information processing system 1000 of the first embodiment further includes a server device 130 in comparison with the information processing system 1000 of the first embodiment. The server device 130 is a server device of a company that provides a billing agency service. Here, the billing agency includes a service of receiving a request for debt collection from a creditor and negotiating with the debtor to collect the debt. The billing agency may include credit screening, invoice issuance, payment collection, and the like. The server device 130 is connected to other devices via a network 150 so as to be able to communicate with them. The hardware configuration of the server device 130 is the same as that of the server device 100. The control unit of the server device 130 executes processing based on a program stored in the storage unit of the server device 130, thereby realizing the functions of the server device 130.

[0024] The display control unit 402 of the first modification performs control so that the acquired invoice data is displayed on the output unit 305 of the client device 110 that has transmitted the display request. FIG. 8 is a diagram showing an example of a display screen of the first modification. As shown in FIG. 8, the screen displayed by the display control unit 402 includes a factoring button 610, a factoring button 620, a factoring button 630, and a factoring button 640, which can be used to request factoring of the invoice data. In addition, the screen displayed by the display control unit 402 includes a billing agency button 710, a billing agency button 720, a billing agency button 730, and a billing agency button 740, which can be used to request the invoice data to a billing agency. The billing agency button is an example of a second object.

[0025] When the factoring button is selected, the transmission unit 403 transmits invoice data related to the selected factoring button to the server device 120 and requests factoring. When the billing agency button is selected, the transmission unit 403 transmits invoice data related to the selected billing agency button to the server device 130 and requests billing agency. Here, the server device 130 is an example of a debt collection system.

[0026] According to the first modification, the user can select whether to have the invoice factored or to have it handled by a billing agency by selecting a button displayed on the screen.

[0027] (Variation 2) A modification of the first embodiment will be described. FIG. 9 is a diagram showing an example of the functional configuration of the server device 100 of the second modification. The server device 100 includes, as functional configurations, a generation unit 901, an acquisition unit 902, a display control unit 903, and a transmission unit 904. The acquisition unit 902 is the same as the acquisition unit 401 of the first embodiment. The display control unit 903 is the same as the display control unit 402 of the first embodiment. The transmission unit 904 is the same as the transmission unit 403 of the first embodiment. The generation unit 901 generates bill data based on a user operation via a predetermined screen displayed on the client device 110. The bill data generated by the generation unit 901 may be stored in the storage unit 202, or may be stored in a data storage server device or the like that can communicate via the network 150. The acquisition unit 902 acquires the bill data generated by the generation unit 901 and stored in the storage unit 202 or the like.

[0028] According to the second modification, the server device 100 can also provide a function for generating billing data.

[0029] (Variation 3) A modification of the first embodiment will be described. FIG. 10 is a diagram showing an example of the functional configuration of the server device 100 of the third modification. The server device 100 includes, as its functional configuration, an extraction unit 1001, an acquisition unit 1002, a display control unit 1003, and a transmission unit 1004. The acquisition unit 1002 is the same as the acquisition unit 401 of the first embodiment. The display control unit 1003 is the same as the display control unit 402 of the first embodiment. The transmission unit 1004 is the same as the transmission unit 403 of the first embodiment. The extraction unit 1001 extracts invoice data from an invoice in a predetermined electronic document file format that has been received. The predetermined electronic document file format is, for example, PDF (Portable Document Format). However, this does not limit the present embodiment, and other electronic document file formats may be used. The extraction unit 1001 may also extract invoice data from mail information of the client device 110. Here, the method of acquiring the invoice data from the mail information related to the client device 110 is not particularly limited. For example, the extraction unit 1001 may access a mail server of the mail used by a specific user of the client device 110 via the communication unit 203 and acquire an e-mail sent to the email address of the specific user. The specific user is, for example, an accounting user. Here, the mail server may store the e-mail sent to the specific user's email address, or may manage and designate the e-mail stored in another server. More specifically, in a state where the server device 100 has obtained access rights to the e-mail from the specific user, the extraction unit 1001 directly accesses the mail server and acquires the e-mail stored in the mail server. The invoice data extracted by the extraction unit 1001 may be stored in the storage unit 202, or may be stored in a data storage server device or the like that can communicate via the network 150. The acquisition unit 1002 acquires the invoice data extracted by the extraction unit 1001 and stored in the storage unit 202 or the like.

[0030] According to the third variant, the server device 100 can also process invoice data in a specified electronic document file format read by a scanner or the like, or invoice data in a specified electronic document file format attached to an e-mail, thereby achieving the same effects as those of the above-described embodiment.

[0031] (Variation 4) A modification of the first embodiment will be described. FIG. 11 is a diagram showing an example of the functional configuration of the server device 100 of the fourth modification. The server device 100 includes, as functional configurations, a first acquisition unit 1101, a second acquisition unit 1102, a selection unit 1103, a display control unit 1104, and a transmission unit 1105. The first acquisition unit 1101 is the same as the acquisition unit 401 of the first embodiment. The transmission unit 1105 is the same as the transmission unit 403 of the first embodiment. The second acquisition unit 1102 acquires the past payment history of the customer. Here, the past payment history of the customer includes information such as the payment amount for each payment, whether or not the payment was made, whether or not the payment was made by the payment due date stated on the invoice, and when the payment was made. The past payment history of the customer may be stored in the storage unit 202, may be stored in a data storage server device that can communicate via the network 150, or may be acquired from another system.

[0032] The selection unit 1103 selects a target customer for which the factoring button is to be displayed based on the payment history acquired by the second acquisition unit 1102. For example, the selection unit 1103 selects a target customer for which the factoring button is to be displayed based on the first criteria information and the payment history. Here, the first criteria information is information in which conditions are set for selecting a target customer for which the factoring button is to be displayed when certain information in the payment history has a certain value. A specific example of the first criteria information is information indicating that payment was not made by the payment due date stated on the invoice.

[0033] The display control unit 1104 controls to display a factoring button in association with the customer selected by the selection unit 1103. Fig. 12 is a diagram showing an example of a display screen of Modification Example 4. In the example of Fig. 12, AA Co., Ltd. is selected from the list of invoices as the customer for which the factoring button is to be displayed, and a factoring button 610 is displayed.

[0034] According to the fourth variant example, the server device 100 can suggest customers who are eligible for factoring by selecting a customer for whom the factoring button is to be displayed based on the payment history and displaying the factoring button in association with that customer.

[0035] (Variation 5) A modification of the first embodiment will be described. FIG. 13 is a diagram showing an example of the functional configuration of the server device 100 of the fifth modification. The server device 100 includes, as functional configurations, a first acquisition unit 1201, a second acquisition unit 1202, a selection unit 1203, a display control unit 1204, and a transmission unit 1205. The first acquisition unit 1201 is similar to the acquisition unit 401 of the first embodiment. The second acquisition unit 1202 is similar to the second acquisition unit 1102 of the fourth modification. The selection unit 1203 selects a first customer for which the factoring button is to be displayed and a second customer for which the billing agency button is to be displayed based on the acquired payment history. For example, the selection unit 1203 selects a customer for which the factoring button is to be displayed and a customer for which the billing agency button is to be displayed based on the second reference information and the payment history. Here, the second reference information is information that sets conditions for selecting a customer as a target customer for displaying the factoring button when what information in the payment history has what value, and selecting a customer as a target customer for displaying the billing agency button when what information in the payment history has what value. Specific examples of the second reference information include reference information for the factoring button such as having made payments past the due date twice or more in the past, and reference information for the billing agency button such as having made a payment past the due date once in the past. This is because factoring has a higher fee than billing agency.

[0036] The display control unit 1204 controls to display the factoring button in association with the first customer selected by the selection unit 1203, and to display the billing agency button in association with the second customer selected by the selection unit 1203. FIG. 14 is a diagram showing an example of a display screen of the fifth modified example. In the example of FIG. 14, the factoring button 610 and the factoring button 620 are displayed on the invoice of ZZ Co., Ltd., and the billing agency button 710 is displayed on the invoice of XX Co., Ltd. For example, when the billing agency button 710 is selected, the transmission unit 1205 transmits invoice data related to the billing agency button 710 (invoice data of the invoice of XX Co., Ltd. in the example of FIG. 14) to the server device 130 and requests billing agency.

[0037] According to the fifth modification, the server device 100 can select, based on the payment history, customers for whom the factoring button is to be displayed and customers for whom billing agency is to be displayed, and can suggest customers for whom factoring and billing agency are to be displayed by displaying the factoring button and billing agency button in association with each customer. For example, the server device 100 suggests billing agency by displaying the billing agency button for level A customers who tend to be late in making payments. The server device 100 can also suggest factoring by displaying the factoring button for level B customers who tend to be even more late in making payments than level A customers.

[0038] (Variation 6) A modification of the first embodiment will be described. FIG. 15 is a diagram showing an example of the functional configuration of the server device 100 of the sixth modification. The server device 100 includes, as functional configurations, a first acquisition unit 1501, a second acquisition unit 1502, a selection unit 1503, a display control unit 1504, and a transmission unit 1505. The first acquisition unit 1501 is the same as the acquisition unit 401 of the first embodiment. The transmission unit 1505 is the same as the transmission unit 403 of the first embodiment. The second acquisition unit 1502 acquires credit information of the customer. Here, the credit information of the customer is a value indicating the creditworthiness of the company calculated from the company's history, size, profit and loss, current capital situation, etc. In this modification example, the closer the value of the creditworthiness is to 1, the lower the creditworthiness is. The credit information of the customer may be stored in the storage unit 202, may be stored in a data storage server device that can communicate via the network 150, or may be acquired from another system.

[0039] The selection unit 1503 selects a target customer for which the factoring button is to be displayed based on the acquired credit information. For example, the selection unit 1503 selects a target customer for which the factoring button is to be displayed based on the third criteria information and the customer's credit information. Here, the third criteria information is information in which a condition is set for selecting a customer as a target customer for which the factoring button is to be displayed, based on a certain value of the customer's credit information. A specific example of the third criteria information is a value indicating a credit rating of 5 or less.

[0040] The display control unit 1504 controls to display a factoring button in association with the selected customer. Fig. 16 is a diagram showing an example of a display screen of Modification Example 6. In the example of Fig. 16, a factoring button 610 and a factoring button 620 are displayed on the invoice of XX Co., Ltd.

[0041] According to variant example 6, the server device 100 can suggest customers who are eligible for factoring by selecting a customer for which a factoring button is to be displayed based on the customer's credit information and displaying the factoring button in correspondence with that customer. As another example, the server device 100 may acquire accounting information of a customer and determine the customer's credit information based on the accounting information. The server device 100 may acquire financial information of a customer and determine the customer's credit information based on the financial information. The server device 100 may acquire payment status information indicating the past payment status of an account receivable (billing destination) and determine the customer's credit information based on the payment status information. The server device 100 may calculate the amount that the customer will pay in the future based on contract information indicating the contents of the contract with the customer, estimate the customer's financial status, and determine the customer's credit information based on the estimated financial status. If there is rule information that defines rules for each customer, the server device 100 may also take the rule information into consideration when determining whether or not to display a factoring button on the customer. The server device 100 may also determine whether or not to display a factoring button on the customer based on any combination of these multiple pieces of information.

[0042] (Variation 7) A modification of the first embodiment will be described. FIG. 17 is a diagram showing an example of the functional configuration of the server device 100 of the seventh modification. The server device 100 includes, as functional configurations, a first acquisition unit 1701, a second acquisition unit 1702, a selection unit 1703, a display control unit 1704, and a transmission unit 1705. The first acquisition unit 1701 is similar to the acquisition unit 401 of the first embodiment. The second acquisition unit 1702 is similar to the second acquisition unit 1502 of the sixth modification. The selection unit 1703 selects a first customer for which the factoring button is to be displayed and a second customer for which the billing agency button is to be displayed based on the acquired credit information. For example, the selection unit 1703 selects a customer for which the factoring button is to be displayed and a customer for which the billing agency button is to be displayed based on the fourth standard information and the credit information of the customer. Here, the fourth standard information sets a condition for what value of a customer's credit information must be for the customer to be selected as a target customer for displaying the factoring button. The fourth standard information also sets a condition for what value of a customer's credit information must be for the customer to be selected as a target customer for displaying the billing agency button. Specific examples of the fourth standard information include a value indicating the creditworthiness of 5 or less as standard information for the factoring button, and a value indicating the creditworthiness of 6 or more and 10 or less as standard information for the billing agency button. Here, the smaller the value indicating the creditworthiness (the closer to 1), the lower the creditworthiness.

[0043] The display control unit 1704 controls to display the factoring button in association with the first customer selected by the selection unit 1703, and to display the billing agency button in association with the second customer selected by the selection unit 1703. FIG. 18 is a diagram showing an example of a display screen of the seventh modification. In the example of FIG. 18, the factoring button 610 and the factoring button 620 are displayed on the invoice of ZZ Co., Ltd., and the billing agency button 710 is displayed on the invoice of XX Co., Ltd. For example, when the billing agency button 710 is selected, the transmission unit 1705 transmits invoice data related to the billing agency button (invoice data of the invoice of XX Co., Ltd. in the example of FIG. 18) to the server device 130 and requests billing agency.

[0044] According to the seventh modification, the server device 100 can select customers for whom the factoring button is to be displayed and customers for whom billing agency is to be displayed based on the credit information of the customers, and can suggest customers for whom factoring and billing agency are to be displayed by displaying the factoring button and billing agency button in association with each customer. For example, the server device 100 suggests billing agency by displaying the billing agency button for a customer with credit rating A based on the customer's financial situation, etc. Then, the server device 100 can suggest factoring by displaying the factoring button for a customer with credit rating B, whose financial situation is worse than that of the customer with credit rating A.

[0045] (Variation 8) A modified example of the first embodiment will be described. The display control unit 402 of the eighth modified example controls so that a deposit confirmation request button capable of requesting a process for confirming deposit is displayed on the display screen together with the factoring button. The deposit confirmation request button is an example of a third object. FIG. 19 is a diagram showing an example of a display screen of the eighth modified example. In the example of FIG. 19, the factoring button 610 and the deposit confirmation request button 1910 are displayed on the invoice of ZZ Co., Ltd. in the invoice list. In addition, the factoring button 620 and the deposit confirmation request button 1920 are displayed on the invoice of ZZ Co., Ltd. For example, when the factoring button 620 and the deposit confirmation request button 1920 are selected, the transmission unit 403 of the eighth modified example transmits invoice data related to the factoring button 620 and the deposit confirmation request button 1920 (in the example of FIG. 19, the invoice data of ZZ Co., Ltd.) to the server device 120, requests factoring, and requests a deposit confirmation process for the invoice amount related to the invoice data. Here, the payment confirmation process refers to, for example, a process of confirming whether the amount stated on an issued invoice has been paid by the corresponding customer, and changing the status of the invoice from a waiting for payment state to a paid state when the payment has been confirmed. For example, when requested to perform payment confirmation process, server device 120 manages its own account information and confirms whether the invoice amount stated on the invoice has been transferred to a specified account by the due date stated on the invoice from the account payable company related to the invoice. When the invoice amount stated on the invoice has been transferred to a specified account by the due date stated on the invoice from the account payable company related to the invoice, server device 120 considers that the payment has been confirmed. Then, server device 120 changes the status of the invoice from a waiting for payment state to a paid state, and transmits to server device 100 information indicating that the invoice has been paid, together with identification information for identifying the corresponding invoice.

[0046] According to variant example 8, a factoring button and a payment confirmation request button for requesting payment confirmation processing are displayed on the screen displaying invoice data, so that when a user wishes to make a payment confirmation request, the user need only select the payment confirmation request button.

[0047] (Variation 9) A modification of the first embodiment will be described. The display control unit 402 of the ninth modification controls so that a billing agent button and a payment confirmation request button that can request a process to confirm the payment are displayed on the display screen. The payment confirmation request button is an example of a third object. FIG. 20 is a diagram showing an example of a display screen of the ninth modification. In the example of FIG. 20, the billing agent button 710 and the payment confirmation request button 2010 are displayed on the invoice of XX Corporation in the invoice list. In addition, the billing agent button 720 and the payment confirmation request button 2020 are displayed on the invoice of XX Corporation. For example, when the billing agent button 720 and the payment confirmation request button 2020 are selected, the transmission unit 403 of the ninth modification transmits invoice data related to the billing agent button 720 and the payment confirmation request button 2020 (in the example of FIG. 20, the invoice data of the invoice of XX Corporation) to the server device 130, requests billing agent and requests payment confirmation processing of the invoice amount related to the invoice data.

[0048] According to variant example 9, a billing agency button and a payment confirmation request button for requesting payment confirmation processing are displayed on the screen displaying the invoice data, so that when a user wishes to make a payment confirmation request, the user need only select the payment confirmation request button.

[0049] (Variation 10) In the above-mentioned embodiment and modified example, an example has been described in which factoring or billing agency can be requested on an invoice basis. However, the server device 100 may also be able to request factoring or billing agency for all invoices of a customer on a customer-by-customer basis. For example, when a factoring button for a certain customer is selected on the screen, the server device 100 may display an inquiry window such as "Do you want to request factoring of other invoices of this customer as well?", and when "Yes" is selected in the inquiry window, the server device 100 may request factoring of other invoices of the customer of the selected invoice as well. The same applies to billing agency.

[0050] According to the tenth modification, it is possible to request factoring and billing services all at once.

[0051] <Additional Notes> The invention may be provided in each of the following aspects: In the information processing device, the control unit generates invoice data based on a user operation and acquires the generated invoice data. In the information processing device, the control unit extracts invoice data from a received invoice in a predetermined electronic document file format, and acquires the extracted invoice data. In the information processing device, the control unit acquires a customer's past payment history, selects a customer for which the first object is to be displayed based on the acquired payment history, and controls the information processing device to display the first object in association with the selected customer. In the information processing device, the screen includes the first object and a second object for which invoice data can be requested to a billing agency, and the control unit acquires past payment history of customers, and based on the acquired payment history, selects a first customer for whom the first object is to be displayed and a second customer for whom the second object is to be displayed, and controls the information processing device to display the first object in association with the selected first customer and to display the second object in association with the selected second customer. In the information processing device, when the second object is selected, the control unit transmits invoice data related to the second object to a billing agency system and requests billing agency. In the information processing device, the control unit acquires credit information of a customer, selects a customer for which the first object is to be displayed based on the acquired credit information, and controls the information processing device to display the first object in association with the selected customer. In the information processing device, the screen includes the first object and a second object for which invoice data can be requested to a billing agency, and the control unit acquires customer credit information, and based on the acquired credit information, selects a first customer for which the first object is to be displayed and a second customer for which the second object is to be displayed, and controls the information processing device to display the first object in association with the selected first customer and to display the second object in association with the selected second customer. In the information processing device, when the second object is selected, the control unit transmits invoice data related to the second object to a billing agency system and requests billing agency. In the information processing device, the screen includes the first object and a second object for which invoice data can be requested to be handled by a billing agency, and when the first object is selected, the control unit sends the invoice data related to the first object to a factoring system and requests factoring, and when the second object is selected, sends the invoice data related to the second object to a debt collection system and requests billing agency. In the information processing device, the screen further includes a third object that can be requested to perform a process to confirm receipt of payment, and when the first object and the third object are selected, the control unit sends invoice data related to the first object and the third object to a factoring system, requests factoring, and also requests a process to confirm receipt of the invoice amount related to the invoice data. In the information processing device, the screen further includes a third object that can be requested to perform a process to confirm payment, and when the second object and the third object are selected, the control unit transmits invoice data related to the second object and the third object to a billing agency system, requests billing agency, and also requests payment confirmation processing for the billing amount related to the invoice data. An information processing method executed by an information processing device, which acquires invoice data and controls the display of the acquired invoice data on a screen, the screen including a first object for which factoring can be requested related to the invoice data, and when the first object is selected, the invoice data related to the first object is sent to a factoring system to request factoring. A program for causing a computer to function as the control unit. Of course, this is not the case.

[0052] For example, the program for realizing the above-mentioned software may be provided as a non-transitory computer-readable recording medium, or may be provided so as to be downloadable from an external server, or may be provided so that the program is launched on an external computer and its functions are realized on a client terminal (so-called cloud computing). Furthermore, the above-described embodiments and modifications may be combined in any desired manner. In the above-described embodiment, the server device 100 is assumed to generate a screen and transmit it to the client device 110. However, the server device 100 may transmit data for generating a screen to the client device 110. The client device 110 may then generate and display a screen based on the data received from the server device 100.

[0053] For example, in the above-mentioned modified examples 8 and 9, a deposit confirmation request button for requesting a deposit confirmation process is provided separately from the factoring button and billing agency button, but when the factoring button is selected, the server device 100 may request factoring and also request a deposit confirmation process. Similarly, when the billing agency button is selected, the server device 100 may request a billing agency and also request a deposit confirmation process. Furthermore, the server device 100 may change whether or not to display a factoring button in association with an invoice in response to a request from the client device 110. That is, the server device 100 displays the factoring button on the display screen of the invoice when requested by the client device 110. Similarly, the server device 100 may change whether or not to display a billing agency button in association with an invoice in response to a request from the client device 110. That is, the server device 100 displays the billing agency button on the display screen of the invoice when requested by the client device 110. Similarly, the server device 100 may change whether or not to display a payment confirmation request button in association with an invoice in response to a request from the client device 110. That is, the server device 100 displays the payment confirmation request button on the display screen of the invoice when requested by the client device 110.

[0054] Furthermore, the functions provided by the above-mentioned server device may be provided by a system consisting of a plurality of server devices. As described above, the invoice data may be invoice data created on the cloud, invoice data received by email, or invoice data imported in bulk from a CSV (Comma Separated Value) file, etc. There are no limitations on the type of receivables or the method of collecting the data.

[0055] Finally, although various embodiments of the present invention have been described, these are presented as examples and are not intended to limit the scope of the invention. The new embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. The embodiments and their modifications are within the scope and spirit of the invention, and are included in the scope of the invention and its equivalents described in the claims. [Explanation of symbols]

[0056] 100: Server device 110: Client device 120: Server device 130: Server device 150: Network 201: Control section 202: Storage section 203: Communications Department 301: Control section 302: Storage section 303: Imaging unit 304: Input section 305: Output section 306: Communications Department 401: Acquisition Department 402: Display control unit 403: Sender 610: Factoring button 620: Factoring button 630: Factoring button 640: Factoring button 710: Billing agent button 720: Billing Agent Button 730: Billing Agent Button 740: Billing Agent Button 901 :Generation part 902: Acquisition Department 903: Display control unit 904: Transmission unit 1000: Information processing systems 1001:Extraction part 1002: Acquisition department 1003: Display control unit 1004: Transmitter 1101: First acquisition unit 1102: Second acquisition section 1103: Selection section 1104: Display control unit 1105: Transmission unit 1201: First acquisition section 1202: Second acquisition section 1203: Selection section 1204: Display control unit 1205: Transmission unit 1501: First acquisition section 1502: Second acquisition section 1503: Selection section 1504: Display control unit 1505: Transmission unit 1701: First acquisition section 1702: Second acquisition section 1703: Selection section 1704: Display control section 1705: Transmission unit 1910: Payment confirmation request button 1920: Payment confirmation request button 2010: Payment confirmation request button 2020: Payment confirmation request button

Claims

1. An information processing device, A control unit is provided. The control unit is Get invoice data, Controlling the display of the acquired invoice data on a screen; the screen includes a first object capable of requesting factoring related to invoice data; If the first object is selected, transmitting invoice data related to the first object to a factoring system and requesting factoring; the screen includes the first object and a second object capable of requesting billing data to a billing agent; When the first object is selected, the control unit transmits invoice data related to the first object to a factoring system and requests factoring; When the second object is selected, invoice data related to the second object is transmitted to a debt collection system to request for billing on behalf of the debtor. Information processing device.

2. An information processing device, A control unit is provided. The control unit is Get invoice data, Controlling the display of the acquired invoice data on a screen; the screen includes a first object capable of requesting factoring related to invoice data; If the first object is selected, transmitting invoice data related to the first object to a factoring system and requesting factoring; Get the customer's past payment history, selecting a target customer for which the first object is to be displayed based on the acquired payment history and history condition information; The history condition information is information that sets conditions for a customer who has made a past payment indicated by the payment history to be selected as the target customer, Controlling display of the first object in association with a selected customer; Information processing device.

3. An information processing device, A control unit is provided. The control unit is Get invoice data, Controlling the display of the acquired invoice data on a screen; the screen includes a first object capable of requesting factoring related to invoice data; If the first object is selected, transmitting invoice data related to the first object to a factoring system and requesting factoring; the screen includes the first object and a second object capable of requesting billing data to a billing agent; Get the customer's past payment history, selecting a first customer for whom the first object is to be displayed and a second customer for whom the second object is to be displayed based on the acquired payment history and history condition information; The history condition information is information that sets conditions for a customer who has made a past payment indicated by the payment history to be selected as the first target customer and conditions for a customer who has made a past payment indicated by the payment history to be selected as the second target customer, Controlling display of the first object in association with a selected first customer and display of the second object in association with a selected second customer; Information processing device.

4. 4. The information processing device according to claim 3, When the second object is selected, the control unit Send the relevant invoice data to the billing agent's system for billing purposes; Information processing device.

5. An information processing device, A control unit is provided. The control unit is Get invoice data, Controlling the display of the acquired invoice data on a screen; the screen includes a first object capable of requesting factoring related to invoice data; If the first object is selected, transmitting invoice data related to the first object to a factoring system and requesting factoring; Obtaining customer credit information selecting a target customer for which the first object is to be displayed based on the acquired credit information and credit condition information; the credit condition information is information that sets conditions for a customer whose creditworthiness is indicated by the credit information to be selected as the target customer; Controlling display of the first object in association with a selected customer; Information processing device.

6. An information processing device, A control unit is provided. The control unit is Get invoice data, Controlling the display of the acquired invoice data on a screen; the screen includes a first object capable of requesting factoring related to invoice data; If the first object is selected, transmitting invoice data related to the first object to a factoring system and requesting factoring; the screen includes the first object and a second object capable of requesting billing data to a billing agent; Obtaining customer credit information selecting a first customer for whom the first object is to be displayed and a second customer for whom the second object is to be displayed based on the acquired credit information and credit condition information; the credit condition information is information that sets conditions for a customer whose creditworthiness is indicated by the credit information to be selected as the first customer of the target and conditions for a customer to be selected as the second customer of the target, Controlling display of the first object in association with a selected first customer and display of the second object in association with a selected second customer; Information processing device.

7. 7. The information processing device according to claim 6, When the second object is selected, the control unit transmits bill data related to the second object to a billing agent system and requests billing agent. Information processing device.

8. An information processing device, A control unit is provided. The control unit is Get invoice data, Controlling the display of the acquired invoice data on a screen; the screen includes a first object capable of requesting factoring related to invoice data; If the first object is selected, transmitting invoice data related to the first object to a factoring system and requesting factoring; The screen further includes a third object capable of requesting a process for confirming a deposit, When the first object and the third object are selected, the control unit transmits invoice data related to the first object and the third object to a factoring system, requests factoring, and requests a payment confirmation process for the invoice amount related to the invoice data. Information processing device.

9. In the information processing device according to claim 1, claim 3, claim 4, claim 6, or claim 7, The screen further includes a third object capable of requesting a process for confirming a deposit, When the second object and the third object are selected, the control unit transmits billing data related to the second object and the third object to a billing agent system, requests billing agent, and requests a payment confirmation process for the billing amount related to the billing data. Information processing device.

10. An information processing method executed by an information processing device, An information processing method, comprising the steps of: executing the operation according to any one of claims 1 to 9, wherein the information processing device executes the operation according to any one of claims 1 to 9.

11. A program, A program for causing a computer to function as the control unit according to any one of claims 1 to 9.

Images