Information processing device, information processing method, and program

Abstract

To provide an information processing device, method and program capable of saving time related to communication about billing with a customer who are slow to transfer his / her bills and acquiring money soon.SOLUTION: In an information processing system 1000 in which a server device 100, a client device 110, and a server device 120 are connected communicably through a network 150, the server device 100 being an information processing device causes an acquisition part to acquire bill data, and a display control part to display the acquired bill data on a screen. The screen includes a first object that can request factoring about the bill data. If the first object is selected, a transmission part transmits the bill data related to the first object to the server device 120 being a factoring system to request factoring.SELECTED DRAWING: Figure 1

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] Japanese Patent Publication No. 2020-194603 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 the acquired invoice data to be displayed on a screen. The screen includes a first object for which factoring related to the invoice data can be requested. When the first object is selected, the invoice data related to the first object is sent to a factoring system, and a factoring request is made. [Brief explanation of the drawings]

[0006] [Figure 1] FIG. 1 is a diagram illustrating an example of a system configuration of an information processing system. [Figure 2] FIG. 2 is a diagram illustrating an example of a hardware configuration of the server device. [Figure 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. [Figure 5] FIG. 5 is an activity diagram illustrating 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 modification. [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 modification. [Figure 13] FIG. 13 is a diagram illustrating an example of a functional configuration of a server device according to the fifth modification. [Figure 14] FIG. 14 is a diagram showing an example of a display screen of the fifth modification. [Figure 15] FIG. 15 is a diagram illustrating an example of a functional configuration of a server device according to the sixth modification. [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. [Figure 18] FIG. 18 is a diagram showing an example of a display screen according to the seventh modification. [Figure 19] FIG. 19 is a diagram showing an example of a display screen of the eighth modification. [Figure 20] FIG. 20 is a diagram showing an example of a display screen of the ninth modification. DETAILED DESCRIPTION OF THE INVENTION

[0007] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The present invention will be described below with reference to the accompanying drawings. Various 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. Also, in this embodiment, various information is handled, and this information is represented by high or low signal values ​​as a binary bit collection consisting of 0 or 1, and communication and calculation can be performed on a 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. That is, 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 illustrating an example of the 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 so as to be able to communicate with each other via a network 150.

[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 there are users registered in the information processing system 1000. Furthermore, 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 illustrating an example of the hardware configuration of the server device 100. The server device 100 includes, as its hardware configuration, a control unit 201, a storage unit 202, and a communication unit 203. The control unit 201 is a central processing unit (CPU) or the like, and controls the entire server device 100. The storage unit 202 is a hard disk drive (HDD), read-only memory (ROM), random access memory (RAM), solid state drive (SSD), or any combination thereof, and stores programs and data used when the control unit 201 executes processing based on the programs. The control unit 201 executes processing based on the programs stored in the storage unit 202, thereby realizing functions of the server device 100 as shown in FIGS. 4, 9-11, 13-14, and 16, which will be described later, and processing of an activity diagram as shown in FIG. 5, which will be described later, and the like. The communication unit 203 is a NIC (Network Interface Card) or the like, and 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). The storage unit 202 is an example of a storage medium. The hardware configuration of server device 120 is also the same as that of server device 100. The control unit of server device 120 executes processing based on a program 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 illustrating an example of the hardware configuration of the client device 110. The client device 110 includes, as its 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, RAM, SSD, or any combination thereof, and stores programs and data used when the control unit 301 executes processing based on the programs. The control unit 301 executes processing based on the programs 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 user operations. The output unit 305 is a display or the like, and outputs 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 invoice data. The acquisition unit 401 may acquire the invoice data from the storage unit 202, or may acquire the invoice 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 request to display invoice data from the client device 110, it acquires invoice data corresponding to the display request. Here, if the display request includes "all," the acquisition unit 401 acquires all invoice data as invoice data corresponding to the display request. Furthermore, if the display request includes "invoice data creation date," the acquisition unit 401 acquires invoice data created on the specified creation date as invoice data corresponding to the display request. As another example, if the display request includes "company name," the first acquisition unit 401 may acquire invoice data including the specified "company name" as invoice data corresponding to the display request. Similarly, "amount" or the like may be used instead of "company name."

[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 Figures 6, 8, 12, 15, and 17. For example, as shown in Figure 6, the screen includes a factoring button 610, a factoring button 620, a factoring button 630, and a factoring button 640, which allow the user to request factoring related to the invoice data. The factoring button is an example of a first object. In this embodiment, an example in which a factoring button or the like is displayed on a screen displaying invoice data will be described. However, the display control unit 402 may also display a factoring button or the like in association with an invoice on a screen for managing receivables.

[0017] (Transmitter 403) When the factoring button is selected, the sending unit 403 sends 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 sending unit 403 sends 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 request to display invoice data has been received from the client device 110. If the acquisition unit 401 determines that a request to display invoice data has been received, the process proceeds to A502. If the acquisition unit 401 determines that a request to display invoice data 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 bill data acquired by the acquisition unit 401 on the screen. FIG. 6 is a diagram (part 1) showing an example of a display screen. The display screen is a screen 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 match 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 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 selected from the list of invoices.

[0020] At A504, the display control unit 402 determines whether 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 process proceeds to A505. If the display control unit 402 determines that the factoring button has not been selected on the display screen, the process returns 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 via 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 it is OK to sell the accounts receivable related to the invoice to a factoring company. If it is selected on the displayed screen that it is OK to sell the accounts receivable related to the invoice to a factoring company, the sending unit 403 may send the 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 related to 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 processing 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, they simply select the factoring button. By requesting factoring, a fee is deducted, but this saves the time involved in communicating with customers who are slow to remit invoice amounts, 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 the 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, as compared with the information processing system 1000 of the first embodiment. The server device 130 is a server device of a company that provides billing agency services. Here, billing agency includes a service of receiving a request for debt collection from a creditor and negotiating with the debtor to collect the debt. Note that the billing agency service may also include credit screening, invoice issuance, payment collection, etc. The server device 130 is communicably connected to other devices via a network 150. The hardware configuration of the server device 130 is similar to that of the server device 100. The functions of the server device 130 are realized by a control unit of the server device 130 executing processing based on a program stored in a memory unit of the server device 130.

[0024] The display control unit 402 of Modification 1 controls the display of the acquired invoice data on the output unit 305 of the client device 110 that sent the display request. FIG. 8 is a diagram showing an example of a display screen of Modification 1. 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 allow a user to request factoring for the invoice data. The screen displayed by the display control unit 402 also includes a billing agency button 710, a billing agency button 720, a billing agency button 730, and a billing agency button 740, which allow a user to request a billing agency for the invoice data. The billing agency button is an example of a second object.

[0025] When the factoring button is selected, the transmission unit 403 transmits the invoice data associated with the selected factoring button to the server device 120 and requests factoring. When the billing agency button is selected, the transmission unit 403 transmits the invoice data associated with 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 request factoring or billing agency for the invoice 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 its functional configuration, a generation unit 901, an acquisition unit 902, a display control unit 903, and a transmission unit 904. The acquisition unit 902 is similar to the acquisition unit 401 of the first embodiment. The display control unit 903 is similar to the display control unit 402 of the first embodiment. The transmission unit 904 is similar to the transmission unit 403 of the first embodiment. The generation unit 901 generates invoice data based on a user operation via a predetermined screen displayed on the client device 110. The invoice 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 invoice 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 similar to the acquisition unit 401 of the first embodiment. The display control unit 1003 is similar to the display control unit 402 of the first embodiment. The transmission unit 1004 is similar to the transmission unit 403 of the first embodiment. The extraction unit 1001 extracts invoice data from a received invoice in a predetermined electronic document file format. 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 also be used. The extraction unit 1001 may also extract invoice data from email information of the client device 110. Here, the method for acquiring invoice data from email information related to the client device 110 is not particularly limited. For example, the extraction unit 1001 may access an email server for an email used by a specific user of the client device 110 via the communication unit 203 and acquire emails sent to the specific user's email address. The specific user may be, for example, an accounting user. Here, the email server may store emails sent to the specific user's email address, or may manage emails stored on another server. More specifically, after the server device 100 has obtained access rights to emails from the specific user, the extraction unit 1001 directly accesses the email server and acquires the emails stored on the email server. The invoice data extracted by the extraction unit 1001 may be stored in the storage unit 202 or 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 variant example 3, the server device 100 can also process invoice data in a specified electronic document file format that has been read by a scanner or the like, or invoice data in a specified electronic document file format that has been attached to an email, 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 illustrating an example of the functional configuration of the server device 100 of the fourth modification. The server device 100 includes, as its functional configuration, 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 similar to the acquisition unit 401 of the first embodiment. The transmission unit 1105 is similar to the transmission unit 403 of the first embodiment. The second acquisition unit 1102 acquires the customer's past payment history. Here, the customer's past payment history 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 due date stated on the invoice, and when the payment was made. The customer's past payment history 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, or may be acquired from another system.

[0032] The selection unit 1103 selects a target customer for which a 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 a factoring button is to be displayed based on first criteria information and payment history. Here, the first criteria information is information that sets conditions for selecting a customer as a target customer for which a factoring button is to be displayed, based on what information in the payment history and what value it takes. A specific example of the first criteria information is information indicating that payment was not made by the due date stated on the invoice.

[0033] The display control unit 1104 controls the display of 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 variant example 4, the server device 100 can suggest customers eligible for factoring by selecting a customer for whom a factoring button is to be displayed based on payment history and displaying a factoring button associated with that customer.

[0035] (Variation 5) A modification of the first embodiment will be described. FIG. 13 is a diagram illustrating an example of the functional configuration of the server device 100 of the fifth modification. The server device 100 includes, as its functional configuration, 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, based on the acquired payment history, a first customer for whom a factoring button is to be displayed and a second customer for whom a billing agency button is to be displayed. For example, the selection unit 1203 selects, based on the second criteria information and the payment history, a customer for whom a factoring button is to be displayed and a customer for whom a billing agency button is to be displayed. Here, the second criteria information is information that sets conditions for what information in the payment history must have a value to select a customer as a target for displaying the factoring button, and what information in the payment history must have a value to select a customer as a target for displaying the billing agency button.Specific examples of the second criteria information include criteria information for the factoring button that indicates two or more instances of past due payments in the past, and criteria information for the billing agency button that indicates one instance of past due payments in the past.This is because factoring has higher fees than billing agency services.

[0036] The display control unit 1204 controls to display a factoring button in association with the first customer selected by the selection unit 1203, and to display a 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 Modification Example 5. 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 the invoice data related to the billing agency button 710 (in the example of FIG. 14, the invoice data of XX Co., Ltd.) 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 its functional configuration, 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 similar to the acquisition unit 401 of the first embodiment. The transmission unit 1505 is similar to the transmission unit 403 of the first embodiment. The second acquisition unit 1502 acquires customer credit information. Here, the customer credit information is a value indicating the creditworthiness of a company determined from the company's history, size, profit and loss, current financial situation, etc. In this modification, the closer the value indicated by the creditworthiness is to 1, the lower the creditworthiness. The customer credit information 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, or may be acquired from another system.

[0039] The selection unit 1503 selects a target customer for which a factoring button is to be displayed based on the acquired credit information. For example, the selection unit 1503 selects a target customer for which a factoring button is to be displayed based on third criteria information and the customer's credit information. Here, the third criteria information is information that sets conditions for selecting a customer as a target customer for which a 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 eligible for factoring by selecting a target customer for which a factoring button is to be displayed based on the customer's credit information and displaying a factoring button corresponding to that customer. As another example, the server device 100 may acquire a customer's accounting information and determine the customer's credit information based on the accounting information. The server device 100 may also acquire a customer's financial information and determine the customer's credit information based on the financial information. The server device 100 may also acquire payment status information indicating the past payment status of accounts receivable (billing destinations) and determine the customer's credit information based on the payment status information. The server device 100 may also calculate the amount the customer will pay in the future based on contract information indicating the details 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 defining rules for each customer, the server device 100 may also take the rule information into account when determining whether or not to display a factoring button for the customer. The server device 100 may also determine whether or not to display a factoring button for a 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 illustrating an example of the functional configuration of the server device 100 of the seventh modification. The server device 100 includes, as its functional configuration, 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, based on the acquired credit information, a first customer for whom a factoring button is to be displayed and a second customer for whom a billing agency button is to be displayed. For example, the selection unit 1703 selects, based on the fourth criteria information and the customer's credit information, a customer for whom a factoring button is to be displayed and a customer for whom a billing agency button is to be displayed. Here, the fourth standard information sets the condition for selecting a customer as a target customer for displaying the factoring button when a certain value of the customer's credit information is reached. The fourth standard information also sets the condition for selecting a customer as a target customer for displaying the billing agency button when a certain value of the customer's credit information is reached. Specific examples of the fourth standard information include the standard information for the factoring button being a value indicating the credit rating of 5 or less, and the standard information for the billing agency button being a value indicating the credit rating of 6 or more and 10 or less. Here, the smaller the value indicating the credit rating (the closer to 1), the lower the credit rating.

[0043] The display control unit 1704 controls to display a factoring button in association with the first customer selected by the selection unit 1703, and to display a 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 Modification Example 7. 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 (in the example of FIG. 18, the invoice data of XX Co., Ltd.) to the server device 130 and requests billing agency.

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

[0045] (Variation 8) A modification of the first embodiment will be described. The display control unit 402 of the eighth modification performs control so that a factoring button and a deposit confirmation request button that can request a deposit confirmation process are displayed on the display screen. 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 modification. In the example of FIG. 19, the factoring button 610 and the deposit confirmation request button 1910 are displayed for an invoice for ZZ Co., Ltd. in the invoice list. Furthermore, the factoring button 620 and the deposit confirmation request button 1920 are displayed for an invoice for 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 modification transmits invoice data associated with the factoring button 620 and the deposit confirmation request button 1920 (in the example of FIG. 19, the invoice data for the invoice for ZZ Co., Ltd.) to the server device 120, requesting factoring and requesting 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 checking whether the amount stated on an issued invoice has been paid by the corresponding customer, and if the payment has been confirmed, changing the status of the invoice from a waiting for payment state to a paid state. For example, when requested to perform payment confirmation processing, server device 120 manages its own account information and checks 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. Server device 120 considers the payment to be confirmed 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. Then, server device 120 changes the status of the invoice from a waiting for payment state to a paid state and sends to server device 100 identification information identifying the corresponding invoice, along with information indicating that the invoice has been transferred.

[0046] According to variant 8, the screen displaying the invoice data displays a factoring button and a payment confirmation request button for requesting payment confirmation processing, so if the user wishes to make a payment confirmation request, they simply need to 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 performs control so that a billing agency button and a payment confirmation request button that can request payment confirmation processing 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, a billing agency button 710 and a payment confirmation request button 2010 are displayed for an invoice for XX Corporation in the invoice list. Furthermore, a billing agency button 720 and a payment confirmation request button 2020 are displayed for an invoice for XX Corporation. For example, when the billing agency button 720 and the payment confirmation request button 2020 are selected, the transmission unit 403 of the ninth modification transmits invoice data associated with the billing agency button 720 and the payment confirmation request button 2020 (in the example of FIG. 20, the invoice data for the invoice for XX Corporation) to the server device 130, requesting billing agency and payment confirmation processing for the invoice amount related to the invoice data.

[0048] According to variant example 9, the screen displaying the invoice data displays a billing agency button and a payment confirmation request button for requesting payment confirmation processing, so if the user wishes to make a payment confirmation request, they simply need to select the payment confirmation request button.

[0049] (Variation 10) In the above-described embodiment and modified example, an example was given in which factoring or billing agency services can be requested on an invoice-by-invoice basis. However, the server device 100 may also be configured to allow factoring or billing agency services to be requested 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 a query window such as, "Do you want to request factoring for this customer's other invoices as well?", and when "Yes" is selected in the query window, request factoring for other invoices of the selected customer's customer as well. The same applies to billing agency services.

[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 the following aspects: In the information processing device, the control unit generates bill data based on a user operation and acquires the generated bill data. In the information processing device, the control unit extracts invoice data from the received invoice in a predetermined electronic document file format, and acquires the extracted invoice data. In the information processing device, the control unit acquires the customer's past payment history, selects the customer for whom 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 that can request billing data from a billing agent, and the control unit acquires the customer's past payment history, 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 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 customer credit information, selects a target customer for displaying the first object 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 that can request billing data from a billing agent, and the control unit acquires customer credit information, and based on the acquired credit information, 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 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 that can request invoice data from a billing agent, 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 process a payment confirmation, 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 payment confirmation process for 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 process a payment confirmation, and when the second object and the third object are selected, the control unit sends invoice data related to the second object and the third object to a billing agency system, requests billing agency, and also requests a payment confirmation process 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 related to the invoice data can be requested, and when the first object is selected, the invoice data related to the first object is sent to a factoring system and a factoring request is made. 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 medium, or may be provided so that it can be downloaded from an external server, or may be provided so that the program is started 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 generates a screen and transmits 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-described modified examples 8 and 9, a deposit confirmation request button for requesting deposit confirmation processing 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 deposit confirmation processing. Similarly, when the billing agency button is selected, the server device 100 may request billing agency and also request deposit confirmation processing. 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 invoice display screen 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 invoice display screen 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 invoice display screen when requested by the client device 110.

[0054] Furthermore, the functions provided by the above-mentioned server device may be provided by a system made up of a plurality of server devices. As mentioned 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 data collection method.

[0055] Finally, while various embodiments of the present invention have been described, these are presented by way of example only and are not intended to limit the scope of the invention. The novel embodiments may be embodied in various other forms, and various omissions, substitutions, and modifications may be made without departing from the spirit of the invention. The embodiments and their modifications are intended to be included within the scope and spirit of the invention, as well as within the scope of the inventions and their equivalents as defined in the appended claims. [Explanation of symbols]

[0056] 100: Server device 110: Client device 120: Server device 130: Server equipment 150: Network 201: Control unit 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: Sending department 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: Transmitter 1000: Information Processing Systems 1001:Extraction part 1002: Acquisition Department 1003: Display control unit 1004: Transmitter 1101: First acquisition unit 1102: Second acquisition unit 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 unit 1502: Second acquisition unit 1503: Selection section 1504: Display control unit 1505: Transmitter 1701: First acquisition unit 1702: Second acquisition section 1703: Selection section 1704: Display control unit 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 Get invoice data, Controlling the display of the acquired billing data on a screen; The screen includes a billing request object that can request billing data from a billing agent, Obtain a customer's past payment history, selecting a second customer for which the billing request object is to be displayed based on the acquired payment history and history condition information; The history condition information is used to determine whether a customer who has made a past payment indicated by the payment history is a customer of the target item. The information is information that sets conditions for being selected as a customer of the second type, An information processing device controls to display the billing request object in association with the selected second customer.

2. 2. The information processing device according to claim 1, When the billing request object is selected, the control unit transmits bill data related to the billing request object to a billing agent system and requests billing agent service.

3. An information processing device, A control unit is provided. The control unit Get invoice data, Controlling the display of the acquired billing data on a screen; The screen includes a billing request object that can request billing data from a billing agent, Obtaining customer credit information selecting a second customer for whom the billing request 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 second customer; An information processing device controls to display the billing request object in association with the selected second customer.

4. 4. The information processing device according to claim 3, When the billing request object is selected, the control unit transmits bill data related to the billing request object to a billing agent system and requests billing agent service.

5. An information processing device, A control unit is provided. The control unit Get invoice data, Controlling the display of the acquired billing data on a screen; The screen includes a deposit confirmation request object that can request a process to confirm the deposit, When the payment confirmation request object is selected, the control unit sends invoice data related to the payment confirmation request object to a factoring system, requests factoring, and requests payment confirmation processing for the invoice amount related to the invoice data.

6. 5. The information processing device according to claim 1, The screen further includes a deposit confirmation request object that can request a process to confirm the deposit, When the billing request object and the payment confirmation request object are selected, the control unit sends invoice data related to the billing request object and the payment confirmation request object to a billing agency system, requests billing agency and requests payment confirmation processing for the billing amount related to the invoice data.

7. An information processing method executed by an information processing device, An information processing method, wherein the information processing device executes the operation according to any one of claims 1 to 5.

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

Images