Information processing device, information processing method, and program

JP2023036785A5Active Publication Date: 2024-12-06MONEY FORWARD INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2022204244
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2021-05-31
Filing Date
2022-12-21
Publication Date
2024-12-06
Estimated Expiration
2041-12-16

AI Technical Summary

Technical Problem

Existing subscription billing systems do not facilitate easy access to past and future billing information, limiting user reference and management.

Method used

An information processing device generates and displays a set of mutually related invoice data based on item information, allowing users to easily view and manage billing data across multiple transactions.

Benefits of technology

Enables users to quickly refer to related billing information, improving user experience and management efficiency by providing easy access to past and future invoices.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 00000000_0000_ABST
    Figure 00000000_0000_ABST
Patent Text Reader

Abstract

To provide an information processing device, an information processing method, and a program that enable a user to check the invoice of the previous month or the invoice of the next month by referring to the invoice even if the invoice is issued periodically. [Solution] In an information processing system 1000 in which a server device 100 and a client device 110 are connected to each other so that they can communicate with each other via a network 150, the server device, which is an information processing device, acquires one piece of case information including information on one business partner, information on the billing amount related to a transaction with the business partner, and information on the number of payments related to the billing amount, and if the information on the number of payments included in the case information indicates multiple payments, it is equipped with a generation unit that generates a set of invoice data related to each other from the one piece of case information, and a display control unit that controls the first screen of the client to display a first screen including a list of the set of invoice data.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

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

[0002] Subscription-based billing systems are becoming more common. Patent Document 1 discloses a technology for automating billing at predetermined intervals for products or services purchased periodically by customers. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2016-126599 Summary of the Invention [Problem to be solved by the invention]

[0004] Even if the invoice is issued periodically, there is a demand to be able to check the invoice of the previous month or the next month for reference. [Means for solving the problem]

[0005] According to one aspect of the present invention, an information processing device is provided. The information processing device has a control unit. The control unit acquires one piece of case information. The case information includes information on one business partner, information on the invoice amount related to a transaction with the business partner, and information on the number of payments related to the invoice amount. If the information on the number of payments included in the case information indicates multiple payments, a set of mutually related invoice data is generated from the one piece of case information. Control is performed to display a first screen based on a request. The first screen includes a list of the set of invoice data. [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 a diagram illustrating an example of case information. [Figure 6] FIG. 6 is a diagram showing an example of the list display screen. [Figure 7] FIG. 7 is an activity diagram showing an example of information processing related to bill data generation in the server device. [Figure 8] FIG. 8 is an activity diagram showing an example of information processing related to bill display in the server device. [Figure 9] FIG. 9 is a diagram showing an example of the invoice screen. [Figure 10] FIG. 10 is a diagram showing an example of the invoice screen. [Figure 11] FIG. 11 is a diagram showing an example of the list display screen of the second modification. [Figure 12] FIG. 12 is a diagram showing an example of the invoice screen of the second modification. [Figure 13] FIG. 13 is a diagram for explaining GUI components of the invoice screen. [Figure 14] FIG. 14 is a diagram showing an example of management of unpaid balances and the like in the third 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 showing 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 and a client device 110. 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 100 and the client device 110 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 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 illustrates 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 by the control unit 201 when executing processes based on the programs. The control unit 201 executes processes based on the programs stored in the storage unit 202, thereby realizing the functions of the server device 100 illustrated in FIG. 4 (described later) and the processes of activity diagrams illustrated in FIGS. 7 and 8 (described later). The communication unit 203 is a network interface card (NIC) or the like, and connects the server device 100 to the network 150 and manages communication with other devices (e.g., the client device 110). The storage unit 202 is an example of a storage medium.

[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 a generation unit 401 and a display control unit 402 as its functional configuration.

[0015] (Generation unit 401) The generation unit 401 generates a set of mutually related invoice data. More specifically, the generation unit 401 receives project information. Here, the project information includes information on the business partner and information on the billing amount related to the transaction. The generation unit 401 generates a set of invoice data based on the project information. FIG. 5 is a diagram illustrating an example of project information. As shown in FIG. 5, the project information includes information on one business partner, the billing destination, the contract period, the item, the billing amount related to the item, and the number of payments related to the billing amount. The project information includes information on the contract with the customer (business partner), such as contract information and item information. In this embodiment, invoice data is generated based on the project information. The project information may be created for each client project or for each client. The project information is obtained from another system (e.g., a sales management system such as Salesforce (registered trademark) or a customer management system) affiliated with the server device 100 or the information processing system 1000 that can communicate with the server device 100 via the network 150, and is temporarily stored in the storage unit 202, etc. The other system is an example of an external system.

[0016] (Display control unit 402) The display control unit 402 controls the display of a list display screen on the output unit 305 of the requesting client device 110 based on the request. The list display screen is an example of a first screen. FIG. 6 is a diagram showing an example of the list display screen. As shown in FIG. 6, the list display screen 700 includes a list 710 of a set of invoice data.

[0017] 4. Information Processing (1) Invoice data generation Fig. 7 is an activity diagram showing an example of information processing related to invoice data generation in the server device 100. The information processing shown in Fig. 7 may be executed periodically, or may be executed in response to the receipt of a request or the like. In A1001, the generation unit 401 acquires case information from the storage unit 202 or the like. In A1002, the generation unit 401 determines whether the number of payments is multiple or not based on the information on the number of payments in the acquired case information. If the generation unit 401 determines that the number of payments is multiple, it proceeds to A1003. If the generation unit 401 determines that the number of payments is not multiple, it proceeds to A1004. More specifically, the generation unit 401 determines whether, among the number of payments for the invoice amount for each item included in the case information, the number of payments for the invoice amount for at least one item indicates multiple times. If the generation unit 401 determines that the number of payments for the invoice amount for at least one item indicates multiple times, it proceeds to A1003. If the generation unit 401 determines that the number of payments for the invoice amounts for all items included in the case information is one, it proceeds to A1004. Using FIG. 5 as an example, the case information shown in FIG. 5 includes items such as an advisory contract and a patent application. The number of payments for the item "patent application" is one, but the number of payments for the item "advisory contract" is 12. Therefore, when the case information is as shown in FIG. 5, the generation unit 401 determines that the number of payments is multiple, and proceeds to A1003. Here, an advisory contract is an example of a subscription. Other examples of subscriptions include services provided by software, cloud services, etc.

[0018] In A1003, the generation unit 401 generates a set of mutually related invoice data from the project information. For example, the generation unit 401 generates a set of invoice data for consecutive months, the number of payments from the contract month, based on the project information. Using FIG. 5 as an example, the generation unit 401 generates invoice data for 1,000,000 yen per month as the consulting contract fee, as a set of mutually related invoice data, because the consulting contract has 12 payments for 1,200,000 yen. In the example of FIG. 5, the contract period is from May 1, 2021 to April 30, 2022, so the generation unit 401 generates invoice data for May 2021 to April 2022. Therefore, each invoice data includes information on the amount of at least 1,000,000 yen. In other words, a set of invoice data is a collection of invoice data for the number of payments (in the example of Figure 5, multiple invoice data from the invoice data for May 2021 to the invoice data for April 2022) that includes the amount (1,00,000 yen in the example of Figure 5) obtained by dividing the invoice amount included in the project information (1,200,000 yen for the advisory contract in the example of Figure 5) by the number of payments (12 times in the example of Figure 5). In A1004, the generation unit 401 generates one invoice data from the project information. For example, if the number of payments for an advisory contract of 1,200,000 yen is one, invoice data of 1,200,000 yen is generated as the advisory contract fee for the first month of the contract period (May 2021 in the above example).

[0019] For simplicity's sake, the following description will be given assuming that invoice data for the same client for the same month is displayed together. For example, if consulting fees and individual invoice amounts other than consulting fees (e.g., filing fees, examination request fees, and interim response fees such as amendments) are incurred in May 2021, the server device 100 will display the invoice data as a consolidated invoice for May that combines these amounts. However, this does not limit the present embodiment. Depending on the settings or display request, a consolidated invoice for one month may be displayed, or individual invoices, such as an invoice for the consulting contract and an invoice for filing fees, may be displayed. (2) Display control

[0020] Fig. 8 is an activity diagram showing an example of information processing related to the display of an invoice in the server device 100. When a predetermined operation is received from the client device 110, etc., the processing shown in Fig. 8 is executed. Note that the processing in Fig. 8 shows only the processing necessary for explaining this embodiment. In A501, the display control unit 402 controls the display of a list display screen on the output unit 305 or the like of the client device 110 that has made the display request. In A502, the display control unit 402 determines whether or not a request to display the invoice screen has been received from the client device 110. If the display control unit 402 determines that a request to display the invoice screen has been received, the process proceeds to A503. If the display control unit 402 determines that a request to display the invoice screen has not been received, the process of A501 is repeated. A request to display the invoice screen may be made, for example, by clicking on one piece of invoice data in the list 710, by selecting one piece of invoice data in the list 710 and double-clicking it, or by selecting one piece of invoice data and right-clicking it and selecting "Display invoice screen" from the menu that appears. Examples of predetermined operations include selecting one piece of invoice data and clicking it, double-clicking one piece of invoice data, selecting one piece of invoice data and right-clicking it and selecting "Display invoice screen" from the menu that appears.

[0021] In A503, the display control unit 402 controls the display of an invoice screen including the invoice data for which a predetermined operation has been performed on the output unit 305 of the client device 110. The invoice screen is an example of a second screen. FIG. 9 is a diagram showing an example of an invoice screen 800. The invoice screen 800 in FIG. 9 is an example of a screen displayed when the first invoice data item 720 in the list 710 on the list display screen 700 of FIG. 6 is selected and a predetermined operation is performed. In the example of FIG. 9, the invoice for May includes consulting fees and patent application fees. Note that, as shown in FIG. 9, the invoice screen 800 does not include a list of a set of invoice data.

[0022] The invoice screen 800 includes a pull-down menu 810. The pull-down menu 810 is an example of a first object. The pull-down menu 810 is an object that instructs the display of one piece of invoice data out of a set of invoice data related to the invoice data for which a predetermined operation has been performed. The invoice screen 800 also includes a back button 830 and a forward button 840. If there is no previous invoice data, the display control unit 402 may not display the back button 830 on the invoice screen 800. Similarly, if there is no next invoice data, the display control unit 402 may not display the forward button 840 on the invoice screen 800. When the go back button 830 is selected, the display control unit 402 displays the invoice data immediately preceding the invoice data displayed on the invoice screen 800, out of the set of invoice data. The go back button 830 is also an example of a first object. For example, in the above example, when the invoice data for June 2021 is displayed on the invoice screen 800, if the go back button 830 is selected, the display control unit 402 displays the invoice data for May 2021 on the invoice screen 800. When the next button 840 is selected, the display control unit 402 displays the invoice data that comes next in the set of invoice data that is displayed on the invoice screen 800. The next button 840 is also an example of a first object. For example, in the above example, when the invoice data for June 2021 is displayed on the invoice screen 800, if the next button 840 is selected, the display control unit 402 displays the invoice data for June 2021 on the invoice screen 800.

[0023] In A504, the display control unit 402 determines whether a switching request has been made. When other invoice data is selected in the pull-down menu 810, the display control unit 402 determines that a switching request has been made. Furthermore, the display control unit 402 determines that a switching request has been made when the go back button 830 is selected. Furthermore, the display control unit 402 determines that a switching request has been made when the go forward button 840 is selected. When the display control unit 402 determines that a switching request has been made, the process proceeds to A505. When the display control unit 402 determines that a switching request has not been made, the process proceeds to A506. The selection of other invoice data in the pull-down menu 810 is an example of an instruction to display one invoice data in the first object. Furthermore, the selection of the go back button 830 is also an example of an instruction to display one invoice data in the first object. Furthermore, selecting the next button 840 is also an example of an instruction to display one piece of bill data in the first object.

[0024] In A505, the display control unit 402 controls the invoice screen to display the invoice data for which switching is instructed. For example, when the fourth invoice data is selected from 12 mutually related invoice data in the pull-down menu 810, the display control unit 402 controls the fourth invoice data (in the above-mentioned example of the consulting fee for the consulting contract from May 1, 2021 to April 30, 2022, the invoice data for August) to be displayed on the output unit 305 of the client device 110. FIG. 10 is a diagram showing an example of an invoice screen 900. As described above, the invoice screen 900 in FIG. 10 is a screen displayed when the fourth invoice data is selected from 12 invoice data in the pull-down menu 810.

[0025] The invoice screen 900 includes a list button 820. The list button 820 is an example of a second object. In A506, the display control unit 402 determines whether or not the list button 820 has been selected. If the display control unit 402 determines that the list button 820 has been selected, the process returns to A501. If the display control unit 402 determines that the list button 820 has not been selected, the process proceeds to A507. When the list button 820 is selected, the display control unit 402 controls the display of the list display screen 700 in A501. The list display screen 700 is a screen in which one piece of invoice data has been selected from a list 710 of a set of invoice data. That is, when invoice data (e.g., invoice data 720) is selected from the list 710 of a set of invoice data on the list display screen 700 as shown in FIG. 6, the display control unit 402 controls the display of the invoice screen 800 of the selected invoice data. Then, when one piece of invoice data from the set of invoice data is selected in the pull-down menu 810 of the invoice screen 800, the display control unit 402 controls the display of the invoice screen 900 of the selected invoice data. When the list button 820 is selected on the invoice screen 900, the display control unit 402 controls the display of the list display screen 700 including the list 710 of invoice data in which the original invoice data for May was selected, rather than the list display screen including the list 710 of invoice data in which the invoice data for August has been selected. For example, in the case of a list screen including a list 710 of invoice data in which August invoice data has been selected, the August invoice data is at the top of the list, and even if the UI (User Interface) is such that invoice data prior to August is displayed by scrolling using a scroll button or the like, the display control unit 402 controls the display so that the original May invoice data is at the top of the list. By controlling the display in this way, it is possible to provide an easy-to-understand screen transition.

[0026] In A507, the display control unit 402 determines whether or not to end the display control processing. If the display control unit 402 determines to end the display control processing, it ends the information processing shown in Fig. 8. If the display control unit 402 determines not to end the display control processing, it returns the processing to A503.

[0027] The process of this embodiment makes it possible to generate and display a set of related invoice data, so that when a user wants to view related invoices for reference, the user can quickly select and display the invoices. As another example, an edit button or the like may be provided on the invoice screen, and when the edit button is selected, the server device 100 may make the invoice editable in accordance with the editing operation. With this configuration, other invoices can be displayed for reference, and if there are any parts that need to be corrected, the invoice data can be edited immediately. As another example, even when six-month installment payments and twelve-month installment payments coexist, the server device 100 may process and display invoice data for the same month for the same client together. For example, if the six-month installment payment item is X and the twelve-month installment payment item is Y, the server device 100 may generate and display invoice data for item X+Y for the first six months, and generate and display invoice data for item Y for the last six months. In the case of installment payments, if the amount is not divisible by 6 or 12 months, the server device 100 may generate and display invoice data for the first or last month by adding the amount that is not divisible by the first or last month. The server device 100 may perform processing based on a preset rule to determine whether to add the amount to the first month, the last month, or a specific month, or may perform processing based on a setting file stored in the storage unit 202 or the like. The server device 100 can change the settings in the setting file based on a request from the client device 110.

[0028] (Variation 1) A modification of the first embodiment will be described. The control unit 201 of Modification 1 may generate a set of mutually related invoice data based on the case information acquired from the cloud contract service. Here, the cloud contract service is a system that provides services that enable various contract-related tasks to be performed online on the cloud, such as creating and concluding contracts, managing contracts, and managing tasks related to contracts. The control unit 201 may also extract case information from the email information of the client device 110 and generate a set of mutually related invoice data based on the extracted case information. Here, the method of acquiring case information from the email information related to the client device 110 is not particularly limited. For example, the control unit 201 may access a mail 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 mail server may store emails sent to the specific user's email address, or may manage or specify emails stored on another server. More specifically, when the server device 100 has obtained access rights to emails from the specific user, the control unit 201 directly accesses the mail server and acquires the emails stored on the mail server. The control unit 201 may also generate a set of mutually related invoice data based on case information in a predetermined electronic document file format that has been registered, etc. The predetermined electronic document file format is, for example, PDF (Portable Document Format). However, it is not limited to PDF and may be another electronic document file format. Furthermore, the control unit 201 may analyze a captured image that has been registered, extract information relating to the invoice from the captured image, and generate a set of mutually related invoice data based on the extracted information. By carrying out the process shown in the modified example, the server device 100 can also generate a set of mutually related bill data.

[0029] (Variation 2) A modification of the first embodiment will be described. FIG. 11 is a diagram showing an example of a list display screen for Modification 2. In FIG. 11, the invoice number, invoice destination, invoice date, expected payment date, invoice amount including tax, invoice balance, etc. are provisionally entered. FIG. 12 is a diagram showing an example of an invoice screen for Modification 2. FIG. 13 is a diagram for explaining GUI components of the invoice screen. As shown in FIG. 13, the upper part of the invoice screen includes a navigation GUI component and a tool GUI component. The navigation GUI component is a GUI component for recognizing and operating your location. "← Invoice" in FIG. 13 is a button equivalent to the list button 820 in Embodiment 1. The current location switching picker in FIG. 13 corresponds to the pull-down menu 810, the back one button 830, and the forward one button 840 in Embodiment 1.

[0030] (Variation 3) A modification of the first embodiment will be described. FIG. 14 is a diagram showing an example of management of unpaid balances, etc. in Variation 3. The example in FIG. 14 shows a case where a transaction generates sales of 1 million yen per month and the initial deposit is for five months. The control unit 201 generates a set of invoice data based on the project information. The control unit 201 then attaches identification information, etc. that identifies the project information to the set of invoice data and manages them in association with each other. If the project information shows a contract of 1 million yen per month for five months, the control unit 201 records 1 million yen as sales and 1 million yen as receivables in the first month. The control unit 201 sets the receivables balance to 1 million yen. For example, if a customer deposits 5 million yen at the end of the following month, the control unit 201 clears the receivables of 1 million yen and records 4 million yen as an advance. The control unit 201 sets the unpaid balance to 4 million yen. The control unit 201 then records 1 million yen as sales and 1 million yen as a reversal of the advance. The control unit 201 sets the unpaid balance to 3 million yen. The following month, the control unit 201 records 1 million yen as sales and 1 million yen as a reversal of the advance payment. The control unit 201 sets the unpaid balance to 2 million yen. In this way, the control unit 201 manages the unpaid balance for a set of invoice data for each project information. Furthermore, upon request, the control unit 201 controls the output unit 305 of the client device 110 to display the history of the unpaid balance for a set of invoice data for each project information. Furthermore, as shown in FIG. 14, the control unit 201 automatically creates the correct accounting based on the receivables and unpaid balance. In other words, because the control unit 201 manages a set of invoice data based on project information, it can automatically create appropriate accounting even when accounting processing differs in relation to monthly sales, such as when the contract is for an annual contract but the payment is made in a lump sum at the beginning.

[0031] <Additional Notes> The invention may be provided in the following aspects: In the information processing device, the control unit acquires the case information from an external system that can communicate with the information processing device via a network. In the information processing device, the control unit determines whether the information on the number of payments included in the case information indicates multiple payments, and if the information on the number of payments indicates multiple payments, generates a set of mutually related invoice data from the case information. In the information processing device, the case information includes information on one business partner, information on the invoice amount for each item in a transaction with the business partner, and information on the number of payments for the invoice amount for each item in a transaction with the business partner, and if the information on the number of payments for the invoice amount for at least one item among the information on the number of payments for each item included in the case information indicates multiple payments, a set of mutually related invoice data is generated from the one piece of case information. In the information processing device, the set of bill data is a collection of bill data for a number of payments, each of which includes an amount obtained by dividing the billing amount by the number of payments. In the information processing device, the set of billing data is billing data relating to a subscription. In the information processing device, when a predetermined operation is performed on one of the invoice data in the list, the control unit displays a second screen including the invoice data on which the predetermined operation was performed, the second screen does not include the list, and the second screen includes a first object, the first object being an object that instructs the display of one of the set of invoice data related to the invoice data on which the predetermined operation was performed, and when the display of the one invoice data is instructed in the first object, the control unit controls the second screen to display the one invoice data. In the information processing device, the second screen includes a second object, and when the second object is selected, the control unit controls to display the first screen, and the first screen is a screen in which the one invoice data of the set of invoice data is selected from the list on the first screen, even if the first object instructs to display the one invoice data of the set of invoice data. In the information processing device, the control unit manages the unpaid balance related to the set of invoice data for each of the case information. In the information processing device, the control unit displays a history of the unpaid balance related to the set of invoice data for each of the case information. An information processing method executed by an information processing device, which generates a set of invoice data related to each other, controls to display a first screen based on a request, and includes a list of the set of invoice data on the first screen. A program for causing a computer to function as the control unit. Of course, this is not the case.

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

[0033] 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) format file, etc.

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

[0035] 100: Server device 110: Client device 150: Network 200: Advisory contract 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 :Generation part 402: Display control unit 700: List display screen 710: List 720: Invoice data 800: Invoice screen 810: Pull-down menu 820: List button 830: Back button 840: Next button 900: Invoice screen 1000: Information Processing Systems

Claims

1. An information processing device, A control unit is provided. The control unit is Obtain information on one project, The case information includes information on one business partner, information on the invoice amount for each item of a transaction with the business partner, and information on the number of payments for the invoice amount for each item of a transaction with the business partner, When the information on the number of payments for the invoice amount for at least one item among the information on the number of payments for each item included in the case information indicates a plurality of payments, a set of invoice data related to each other is generated from the one case information; Controlling display of the first screen based on the request; the first screen includes a list of the set of bill data; The set of billing data includes billing date or billing destination information. Information processing device.

2. An information processing device, A control unit is provided. The control unit is Obtain information on one project, The case information includes information on one business partner, information on the invoice amount for each item of a transaction with the business partner, and information on the number of payments for the invoice amount for each item of a transaction with the business partner, When the information on the number of payments for the invoice amount for at least one item among the information on the number of payments for each item included in the case information indicates a plurality of payments, a set of invoice data related to each other is generated from the one case information; Controlling display of the first screen based on the request; the first screen includes a list of the set of bill data; When a predetermined operation is performed on one of the bill data in the list, the control unit displays a second screen including the bill data on which the predetermined operation has been performed; the second screen includes a bill indicated by the one billing data and a bill having the same billing month as the bill but for different items; Information processing device.

3. An information processing device, A control unit is provided. The control unit is Obtain information on one project, The case information includes information on one business partner, information on the invoice amount for each item of a transaction with the business partner, and information on the number of payments for the invoice amount for each item of a transaction with the business partner, When the information on the number of payments for the invoice amount for at least one item among the information on the number of payments for each item included in the case information indicates a plurality of payments, a set of invoice data related to each other is generated from the one case information; Controlling display of the first screen based on the request; the first screen includes a list of the set of bill data; When a predetermined operation is performed on one of the bill data in the list, the control unit displays a second screen including the bill data on which the predetermined operation has been performed; the second screen includes a claim indicated by the one claim data, and does not include a claim having a different item from the claim, Information processing device.

4. An information processing device, A control unit is provided. The control unit is Obtain information on one project, The case information includes information on one business partner, information on the invoice amount for each item of a transaction with the business partner, and information on the number of payments for the invoice amount for each item of a transaction with the business partner, generating two sets of invoice data each relating to a different item from the single item information, when the information on the number of payments for the invoice amount for a first item indicates a first number of payments and the information on the number of payments for the invoice amount for a second item indicates a second number of payments, Controlling display of the first screen based on the request; the first screen includes a list of at least one of the two sets of bill data; When a predetermined operation is performed on one of the bill data in the list, the control unit displays a second screen including the bill data on which the predetermined operation has been performed; The second screen includes a first billing indicated by the one billing data, and, if there is a second billing in a billing data set different from the billing data and having the same billing month as the first billing, the second billing is included. Information processing device.

5. An information processing device, A control unit is provided. The control unit is Obtain information on one project, The case information includes information on one business partner, information on the invoice amount for each item of a transaction with the business partner, and information on the number of payments for the invoice amount for each item of a transaction with the business partner, When the information on the number of payments for the invoice amount for at least one item among the information on the number of payments for each item included in the case information indicates a plurality of payments, a set of invoice data related to each other is generated from the one case information; Controlling display of the first screen based on the request; the first screen includes a list of the set of bill data; Manage the receivable balance and the unpaid balance for each set of bill data for each item of information; generating journal entries according to the receivable balance and the unpaid balance; Information processing device.

6. An information processing device, A control unit is provided. The control unit is Extract information about a case from an email, The case information includes information on one business partner, information on the invoice amount for each item of a transaction with the business partner, and information on the number of payments for the invoice amount for each item of a transaction with the business partner, When the information on the number of payments for the invoice amount for at least one item among the information on the number of payments for each item included in the case information indicates a plurality of payments, a set of invoice data related to each other is generated from the one case information; Controlling display of the first screen based on the request; the first screen includes a list of the set of billing data; Information processing device.

7. 1. An information processing method, comprising: The method includes a step of causing a control unit of an information processing device to execute the process according to any one of claims 1 to 6. Information processing methods.

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