Information processing system, information processing method and program
The information processing system addresses the inefficiency of manual invoice checking by automating the calculation and output of total amounts for combined invoices, enhancing the efficiency of billing operations.
Patent Information
- Application Number
- JP2023075915
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-02
- Publication Date
- 2024-11-15
AI Technical Summary
Conventional systems require manual checking of invoice lists or combined invoice lists, making billing operations inconvenient and time-consuming.
An information processing system that acquires multiple bill information, calculates total amounts based on defined common conditions, and outputs bill data for each total amount, reducing the time and effort involved in billing operations.
The system efficiently reduces the time and effort required for billing-related tasks by automating the process of identifying and combining invoices that meet specific criteria, thereby streamlining the billing workflow.
Smart Images

Figure 2024160717000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to an information processing system, an information processing method, and a program. [Background technology]
[0002] Patent Document 1 discloses a technology for receiving electronic invoices from each biller information terminal, consolidating electronic invoices for the same billee, calculating a total amount, and transmitting the consolidated information to each billee information terminal. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2002-259900 A Summary of the Invention [Problem to be solved by the invention]
[0004] When processing many invoices, it is necessary to know which invoices require action and take appropriate action accordingly, but with the previous system, this was inconvenient as it required checking a page listing invoices or a page listing combined invoices.
[0005] In view of the above circumstances, the present invention provides an information processing system and the like that can reduce the labor involved in invoice-related tasks. [Means for solving the problem]
[0006] According to one aspect of the present invention, there is provided an information processing system. The information processing system includes a processor, and in an acquisition step, the processor acquires a plurality of pieces of invoice information, each of which indicates the contents of a respective invoice. In a calculation step, the processor calculates a total amount of invoices whose contents satisfy a common condition based on the acquired plurality of pieces of invoice information, and a plurality of common conditions are defined. In an output step, for each of the plurality of total amounts calculated for the plurality of common conditions, the processor outputs invoice data indicating the invoice for that total amount.
[0007] According to this embodiment, the work involved in invoices can be reduced. [Brief description of the drawings]
[0008] [Figure 1] 1 is a diagram showing the overall configuration of a request management system 1. FIG. [Diagram 2] FIG. 2 is a diagram illustrating a hardware configuration of a server device 10. [Diagram 3] FIG. 2 is a diagram showing a hardware configuration of a user terminal 20. [Figure 4] FIG. 2 illustrates an example of a functional configuration of a control unit of each device. [Diagram 5] FIG. 11 is an activity diagram showing an example of a business support process. [Figure 6] FIG. 13 is a diagram illustrating an example of a billing database. [Figure 7] FIG. 4 illustrates an example of a case database. [Figure 8] FIG. 13 is a diagram showing an example of a displayed invoice list. [Figure 9] FIG. 13 is a diagram showing an example of a list of displayed combined invoices. [Figure 10] FIG. 13 is a diagram showing an example of a displayed preview. [Figure 11] FIG. 13 is a diagram showing an example of displayed billing information for each invoice before being added up. [Figure 12] FIG. 13 is a diagram showing an example of billing information of a displayed invoice that can be added. [Figure 13]FIG. 13 is a diagram showing an example of edited billing information for each invoice before being added up. [Figure 14] FIG. 13 is a diagram showing another example of edited billing information of each invoice before being added up. [Figure 15] FIG. 13 is a diagram showing an example of a display when an operation is performed to exclude an item from the target of collective summation. [Figure 16] FIG. 13 is a diagram showing an example of a display when an operation to exclude items from the target of collective summation is confirmed. [Figure 17] FIG. 13 is a diagram showing an example of a list of combined invoices after editing has been completed. [Figure 18] FIG. 13 is a diagram showing an example of information regarding a generated claim. [Figure 19] FIG. 13 is a diagram showing an example of a display of the number of combined invoices. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0009] Hereinafter, embodiments of the present invention will be described with reference to the drawings. Various features shown in the following embodiments can be combined with each other.
[0010] Incidentally, the program for realizing the software appearing in this embodiment may be provided as a non-transitory computer-readable recording medium, or may be provided so as to be downloadable from an external server, or may be provided so that the program is started on an external computer and its functions are realized on a client terminal (so-called cloud computing).
[0011] In addition, in this embodiment, the term "unit" may include, for example, a combination of hardware resources implemented by a circuit in the broad sense and software information processing that can be specifically realized by these hardware resources. In addition, in this embodiment, various information is handled, and this information is represented, for example, by physical values of signal values representing voltage and current, high and low signal values as a binary bit group consisting of 0 or 1, or quantum superposition (so-called quantum bits), and communication and calculation can be performed on the circuit in the broad sense.
[0012] In addition, a circuit in the broad sense is a circuit realized by at least appropriately combining a circuit, circuitry, a processor, a memory, etc. In other words, it includes an application specific integrated circuit (ASIC), a programmable logic device (e.g., a simple programmable logic device (SPLD), a complex programmable logic device (CPLD), and a field programmable gate array (FPGA)), etc.
[0013] 1. Hardware Configuration In this section, the hardware configuration of the recruitment operation support system according to this embodiment will be described.
[0014] FIG. 1 is a diagram showing the overall configuration of the billing management system 1. FIG. 1 shows an overview of each device provided in the billing management system 1 and users who use those devices. Each overview will be explained from time to time with reference to other figures. The billing management system 1 is an information processing system that executes business support processing, which is information processing for supporting billing operations. Billing operations are operations in which, when a transaction such as a product or service is carried out with a customer, the customer is charged for the transaction. Billing operations include, for example, creating and sending invoices, confirming payments, managing deposits, and collecting debts.
[0015] The billing management system 1 comprises a communication line 2, a server device 10, and a user terminal 20. The communication line 2 is not particularly limited, but may be configured, for example, by the Internet network. The communication line 2 may also include a local area network, a mobile communication network, and a VPN (Virtual Private Network), etc. The communication line 2 mediates data exchange between devices connected to the line. In the example of FIG. 1, the server device 10 is connected to the communication line 2 by wire, and the user terminal 20 is connected wirelessly. The connection of each device to the communication line 2 may be wired or wireless.
[0016] The server device 10 is an information processing device that executes business support processing while exchanging data with the user terminal 20 via the communication line 2. The user terminal 20 is a terminal used by a user, and executes display of information generated by the server device 10, acceptance of operations by the user, etc. The user terminal 20 is, for example, a smartphone, a tablet terminal, a personal computer, etc.
[0017] 2 is a diagram showing a hardware configuration of server device 10. Server device 10 includes a control unit 11, a storage unit 12, a communication unit 13, and a bus 14. Bus 14 electrically connects each unit included in server device 10.
[0018] (Control unit 11) The control unit 11 includes at least one processor. The at least one processor may be configured, for example, by a central processing unit (CPU), a micro processing unit (MPU), a graphics processing unit (GPU), one or more integrated circuits, one or more discrete circuits, or a combination of these (not shown).
[0019] The control unit 11 is a computer that realizes various functions related to the billing management system 1 by reading out a predetermined program stored in the memory unit 12. In other words, information processing by software stored in the memory unit 12 is specifically realized by the control unit 11, which is an example of hardware, and can be executed as each functional unit included in the control unit 11. These will be described in more detail in the next section. Note that the control unit 11 is not limited to being single, and it may be implemented by having multiple control units 11 for each function. It may also be a combination of these.
[0020] (Storage unit 12) The storage unit 12 stores various information defined by the above description. This can be implemented, for example, as a storage device such as a solid state drive (SSD) or a hard disk drive (HDD) that stores various programs and the like related to the billing management system 1 executed by the control unit 11, or as a memory such as a random access memory (RAM) that stores temporarily required information (arguments, arrays, etc.) related to the program calculations. The storage unit 12 stores various programs, variables, etc. related to the billing management system 1 executed by the control unit 11.
[0021] (Communications Department 13) The communication unit 13 is configured by a communication module. The communication module may be a wireless communication module conforming to standards such as IEEE802.11a / b / g / n / ac / ax, LTE, 5G, and 6G, or may be a wired communication module conforming to standards such as IEEE802.3. The communication unit 13 is configured to be capable of transmitting various electrical signals from the server device 10 to external components. The communication unit 13 is also configured to be capable of receiving various electrical signals from the external components to the server device 10. More preferably, the communication unit 13 has a network communication function, and may be implemented so that various information can be communicated between the server device 10 and an external device via the communication line 2.
[0022] Fig. 3 is a diagram showing a hardware configuration of the user terminal 20. The user terminal 20 includes a control unit 21, a storage unit 22, a communication unit 23, an input unit 24, an output unit 25, and a bus 26. The bus 26 electrically connects the various units included in the user terminal 20. The control unit 21, the storage unit 22, and the communication unit 23 are similar hardware to the control unit 11, the storage unit 12, and the communication unit 13 shown in Fig. 2, although the specifications, model, etc. may be different.
[0023] (Input section 24) The input unit 24 has keys, buttons, a touch screen, a mouse, etc., and receives input from the user. The input unit 24 may also have a microphone and receive voice input from the user.
[0024] (Output section 25) The output unit 25 has a display, a speaker, and the like, and displays visual information generated in a manner that is visible to the user, such as screens, images, icons, text, and the like, on the display surface of the display, and outputs sounds including voice.
[0025] 2. Functional configuration In this section, the functional configuration of the present embodiment will be described. As described above, information processing by software stored in the storage unit of each device is specifically realized by a control unit, which is an example of hardware, so that each functional unit included in the control unit can be executed.
[0026] 4 is a diagram showing an example of the functional configuration of the control unit of each device. The control unit 11 of the server device 10 includes a server display unit 111, a storage control unit 112, an information acquisition unit 113, an amount calculation unit 115, and a bill output unit 116. The control unit 21 of the user terminal 20 includes a user display unit 211 and an operation reception unit 212.
[0027] The server display unit 111 executes processing for displaying on each terminal a system screen related to the billing management system 1. In this embodiment, the server display unit 111 performs processing such as generating and transmitting an HTML (Hyper Text Markup Language) file, and displays a web page showing the system screen on the user terminal 20. The server display unit 111 may also perform processing such as generating and transmitting display data for an application for using the billing management system 1.
[0028] The memory control unit 112 controls the memory unit 12 of its own device, and writes and reads data to and from the memory unit 12. The information acquisition unit 113 acquires information used in the business support processing. The information acquisition unit 113 acquires, for example, invoice information indicating the contents of the invoice. The information counting unit 114 counts the information (invoice information and case information) described below. The amount calculation unit 115 calculates the amount related to the invoice. The amount calculation unit 115 calculates, for example, the invoice amount for each transaction. The invoice output unit 116 outputs data generated by the business support processing. The invoice output unit 116 outputs, for example, invoice data indicating the contents of the invoice.
[0029] The user display unit 211 of the user terminal 20 displays a system screen relating to the billing management system 1 indicated by the screen data transmitted from the server device 10. The operation accepting unit 212 accepts operations by the user who uses the user terminal 20.
[0030] When a user operates the user terminal 20 to use the billing management system 1, the user enters a user ID (Identification) and a password to log in. This associates the user ID with information generated in the user terminal 20, making it possible to identify which user the information pertains to.
[0031] 3. Information Processing This section describes information processing (business support processing) in this embodiment, which causes a computer that controls the claim management system 1 to execute a program. The claim management system 1 includes a processor that can execute a program to perform each step shown in the following FIG. 5 and the like.
[0032] FIG. 5 is an activity diagram showing an example of business support processing. The business support processing shown in FIG. 5 is initiated when a person in charge of billing at a company or the like performs an operation to display a list of invoices in order to perform billing-related tasks. First, the user terminal 20 receives an operation to display the invoice list via the operation reception unit 212 (A11). The invoice list is a list that displays multiple pieces of billing information. The billing information is information that indicates the content of the bill (such as the billing destination and the billing amount). The operation reception unit 212 transmits operation data indicating the received operation and the user who performed the operation to the server device 10.
[0033] When the server device 10 receives the transmitted operation data by the storage control unit 112, it reads out the invoice information that the user indicated by the received operation data has the viewing authority (A12). The invoice information is information used to issue an invoice, and includes billing information. The server device 10 stores a billing database that stores the invoice information.
[0034] Figure 6 is a diagram showing an example of a billing database. The billing database DB1 shown in Figure 6 stores invoice information such as invoice number, billing destination, item, delivery date, creation date, invoice date, expected payment date, invoice amount, billing balance, and status, each associated with the other. The invoice number is a number issued to identify each invoice. The invoice destination is the destination of the invoice. The item is a classification or category used to identify the goods and services that are the subject of the invoice.
[0035] The delivery date indicates the date on which the product to be billed was delivered or the service was provided. The creation date indicates the date on which the invoice was created (issued). The billing date indicates the date on which the invoice was issued, and in this embodiment, it is the same as the creation date. Note that the method of setting the billing date is not limited to this. For example, it may be arbitrarily set based on the invoice creation date, or it may be arbitrarily set based on the delivery date. Furthermore, when the lump sum processing described later is performed, it may be arbitrarily set based on the closing date, or it may be arbitrarily set based on the invoice creation date. Furthermore, examples of the arbitrary settings include the invoice creation date, the day after the invoice creation date, the last day of the month of invoice creation, the 1st day of the month following invoice creation, the delivery date, the day after the delivery date, the last day of the month of delivery, or the 1st day of the month following delivery, but other settings may also be possible.
[0036] The expected payment date is the expected date when payment is made for an issued invoice. The billing amount is the amount billed according to the invoice, and the billing balance is the billing amount minus the amount already paid. The status refers to the state of the invoice, and indicates, for example, whether it has been sent, not been sent, or is waiting for approval. Note that these items are merely examples, and items not shown in FIG. 6 may be included in the invoice database DB1 if necessary for invoicing.
[0037] In this embodiment, the memory control unit 112 reads out invoice information for which the billing date is for the current month. Next, the server device 10, via the memory control unit 112, reads out case information for which the user indicated by the received operation data has viewing authority (A13). Case information is information on a case in which a transaction occurs between the user or the business entity to which the user belongs and a customer. Case information indicates the contents of the transaction, and therefore includes billing information indicating the contents of the bill arising from the transaction. The server device 10 stores a case database in which case information is stored.
[0038] Figure 7 is a diagram showing an example of a case database. The case database DB2 shown in Figure 7 stores case numbers, businesses, transaction IDs, departments, service names, billing destinations, contract start dates, contract end dates, billing amounts, and number of payments, each associated with the other. The case number is a number issued to identify each case. The businesses are businesses that are business partners for each case. The transaction ID is an ID issued to identify each transaction. The contract start date and contract end date are the dates on which the contract for each transaction starts and ends.
[0039] The invoice amount is the amount that the creditor invoices the debtor for each transaction. The number of payments is the number of payments agreed upon with the business partner. The contract start date, contract end date, and number of payments indicate the timing of payment, i.e., the timing of invoice. For example, if the contract start date is April, the contract end date is March, and the number of payments is 12, invoices will be generated every month. 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 the invoice amount for each item included in the case information indicates multiple payments, it is possible to generate a set of invoice data related to each other from one case information. Note that the items shown in FIG. 7 are only an example, and items not shown in FIG. 7 may be included in the case database DB2 if necessary for case management.
[0040] In this embodiment, the storage control unit 112 reads out the case information whose billing date falls in the current month. Next, the server device 10, through the server display unit 111, generates screen data showing a list of invoices based on the read invoice information and case information, and transmits the generated screen data to the user terminal 20 (A13). The user terminal 20, through the user display unit 211, displays the invoice list indicated by the transmitted screen data (A14). The displayed invoice list and the contents of the billing indicated by the case information in the invoice list will be described with reference to FIG. 8.
[0041] Fig. 8 is a diagram showing an example of a displayed invoice list. In the example of Fig. 8, the user display unit 211 displays a system screen G1 of the invoice management system 1. The system screen G1 displays tabs TB11, TB12, and TB13, a reset button B11, a filter button B12, a lump sum button B13, an input field C11 for filtering conditions, a list of invoices D11, and the number of filtered items D12.
[0042] Tab TB11 is an image for operation to display a page containing a list of invoices for all claims. Tab TB12 is an image for operation to display a page containing a list of invoices for unsent claims, and tab TB13 is an image for operation to display a page containing a list of invoices for claims that have been sent. The term "claim" here includes both claims indicated by invoice information and claims indicated by case information.
[0043] When a user performs an operation to select a tab, the operation receiving unit 212 receives the operation, and the user display unit 211 communicates with the server display unit 111 and displays a page including a list of invoices for the claim corresponding to the selected tab. In the example of Fig. 8, the tab TB11 is selected, and the user display unit 211 displays a page including a list of invoices for all claims.
[0044] The input field C11 is an area for inputting conditions for narrowing down the invoices to be displayed. The invoice number, status, invoice recipient, delivery date, creation date, invoice date, expected payment date, and invoice amount, or a range of values, can each be input into the input field C11. The number of narrowed down items D12 indicates the number of invoices that have been narrowed down by input into the input field C11, from among the invoices selected by the tab. Note that in the example of FIG. 8, no input has been made into the input field C11, so the number of items before narrowing down (1,232 items) is shown.
[0045] The invoice list D11 is a list of invoices selected by the tabs, narrowed down by inputting information into the input field C11. The invoice list D11 shows each item of invoice information, such as the invoice number, status, invoice destination, delivery date, creation date, invoice date, expected payment date, invoice amount, and invoice balance.
[0046] The invoice information shown in Fig. 6 includes all of the information of the items displayed in the invoice list as billing information. On the other hand, the case information shown in Fig. 7 does not include some of the items in the invoice list (invoice number, status, item, creation date, invoice date, expected payment date, billing balance). Therefore, the server display unit 111 converts the information included in the case information that indicates the contents of the invoice (i.e., the billing information) into information of the items displayed in the invoice list, and includes it in the invoice list together with the billing information included in the invoice information.
[0047] For example, the server display unit 111 uses the case number in the case information as a temporary invoice number (an official invoice number will be issued later), the service name as the item, the scheduled invoice issue date determined from the contract start date, contract end date and number of payments as the creation date and invoice date, and the day a specified period has passed since the scheduled issue date as the scheduled payment date, and includes these in the invoice list.
[0048] As mentioned above, the items of the invoice information shown in Fig. 6 and the case information shown in Fig. 7 are examples and are not limited to these. For example, the case information may include "item", "delivery date (or scheduled delivery date)", and "billing date (or scheduled billing date)". In this way, the case information may include information on items that directly indicate the contents of the bill as billing information, or may include information from which the contents of the bill can be derived as billing information.
[0049] The reset button B11 is an image for operation that accepts an operation to reset the input to the input field C11. The narrow down button B12 is an image for operation that accepts an operation to reflect the narrowing down based on the narrowing down condition input to the input field C11.
[0050] The Lump Sum button B13 is an operation image for accepting an addition operation to add together all of the claims included in the invoice list (both the claims indicated by the invoice information and the claims indicated by the case information) whose contents satisfy a common condition (hereinafter referred to as the "addition condition"). The user terminal 20 accepts the operation on the Lump Sum button B13 as an addition operation via the operation acceptance unit 212, and transmits operation data indicating that the addition operation has been accepted to the server device 10 (A21). On receiving the transmitted operation data, the server device 10 extracts, via the memory control unit 112, claims that satisfy the addition condition from the claims included in the invoice list (A22).
[0051] The aggregation condition is a condition for determining whether or not each invoice included in the invoice list is subject to aggregation of invoice amounts. In this embodiment, the initial aggregation condition is set to be a condition that is met when the invoice recipient is the same and the invoice date is the current month. Note that in the example of FIG. 8, the invoice dates for all invoices are the current month, so the memory control unit 112 extracts invoices included in the invoice list (both invoices indicated by invoice information and invoices indicated by case information) that are the same invoice recipient and that satisfy the aggregation condition (which may include both invoices indicated by invoice information and invoices indicated by case information).
[0052] Next, the server device 10 counts the number of claims extracted in A22 using the information counting unit 114 (A23). Next, the server device 10 calculates the total amount of claims indicated by the claims extracted in A22 using the amount calculation unit 115 (A24). The server device 10 then determines whether or not all claims included in the invoice list have been extracted (A25), and if it determines that there are claims that have not been extracted (NO), it returns to A22, changes the billing destination used in the summation conditions, and extracts claims again.
[0053] If the server device 10 determines in A25 that there are no unextracted bills and that all bills have been extracted (YES), it generates screen data showing a list of all combined bills whose total amounts were calculated in A24 using the server display unit 111, and transmits the generated screen data to the user terminal 20 (A26). Hereinafter, the process of combining bills collectively from A22 to A26 will be referred to as the "lump sum processing." The user terminal 20 displays the list of combined bills shown in the transmitted screen data using the user display unit 211 (A27).
[0054] Fig. 9 is a diagram showing an example of a list of displayed combined invoices. In the example of Fig. 9, the user display unit 211 displays the system screen G2 of the invoice management system 1. The system screen G2 displays a preview button B21, an edit button B22, a tally button B23, a create button B24, an input field C21 for inputting combining conditions, a list D21 of combined invoices, and the number of items after combining D22.
[0055] The number of items after combining D22 indicates the number of invoices after the combined combining process has been performed. In the example of FIG. 9, the combined combining process has reduced the number of invoices from 1,232 in the example of FIG. 8 to 200. The list of combined invoices D21 is a list of combined invoices that add up the invoice amounts of invoices that meet the combining conditions. Each combined invoice may include both invoices indicated by invoice information and invoices indicated by case information. The list of combined invoices D21 shows information on each item of invoice, such as invoice destination, invoice date, total number D23, item, and invoice amount, as invoice information. The total number D23 shows the number of original invoices whose invoice amounts have been added together for the combined invoice. For example, an invoice with a total number of "10 items" is an invoice in which the invoice amounts of 10 invoices have been added together.
[0056] A preview button B21 and an edit button B22 are associated with each combined invoice. The preview button B21 is an operation image for accepting an operation to display the combined invoice. The edit button B22 is an operation image for accepting an operation to edit the combined invoice. The input field C21 for combination conditions is an area for inputting the combination conditions. The tally button B23 is an operation image for accepting an operation to execute the lump sum process again with the combination conditions input in the input field C21. The create button B24 is an operation image for accepting an operation to create an invoice with the contents of the combined invoice list D21.
[0057] When the user enters information into the input field C21 and operates the tally button B23, the user terminal 20 accepts these operations through the operation acceptance unit 212 as operations to change the summation conditions, and transmits request data to the server device 10 requesting that the lump sum processing be performed again with the input summation conditions (A31). Upon receiving the transmitted request data, the server device 10 re-executes the lump sum processing from A22 using the summation conditions indicated in the received request data. The server device 10 updates the list of combined invoices by re-executing the lump sum processing.
[0058] When the user operates the preview button B21, the user terminal 20 accepts the operation as a preview display operation via the operation acceptance unit 212, and displays an image (preview) of the invoice corresponding to the operated preview button B21 via the user display unit 211 (A32).
[0059] Fig. 10 is a diagram showing an example of a displayed preview. In the example of Fig. 10, a preview E21 of the combined invoice for billing destination C, out of the combined invoices shown in Fig. 9, is displayed on the system screen G2. In the example of Fig. 10, only the upper part of the combined invoice is displayed in the preview E21, but the entire invoice can be displayed by scrolling or reducing it. The user can check whether there are any problems with the billing details by looking at the preview of the displayed combined invoice.
[0060] The user display unit 211 displays the preview E21 below the operated preview button B21, thereby simultaneously displaying the preview E21 and the edit button B22 corresponding to the previewed combined invoice. When the user determines from the preview E21 that the combined invoice needs to be edited, the user operates the edit button B22 corresponding to that combined invoice. The user terminal 20 accepts the operation on the edit button B22 via the operation acceptance unit 212, and transmits request data indicating the combined invoice to be edited and a request to edit the combined invoice to the server device 10 (A33).
[0061] When the server device 10 receives the request data, the storage control unit 112 reads out the billing information of each invoice before the combination, which is included in the combined invoice indicated in the received request data, and transmits it to the user terminal 20 (A34). The user terminal 20 displays the transmitted billing information of each invoice before the combination on the user display unit 211 (A35).
[0062] Fig. 11 is a diagram showing an example of billing information for each invoice before being combined that is displayed. In the example of Fig. 11, billing information D31 for each invoice before being combined that is included in the combined invoice of the preview E21 shown in Fig. 10 is displayed on the system screen G3. The billing information D31 may include both billing information indicated by the invoice information and billing information indicated by the case information. The system screen G3 displays the preview E21, billing information D31, an add button B31, an exclude button B32, a save button B33, a cancel button B34, and an exclude from bulk summation button B35.
[0063] The Add button B31 is an operation image that accepts an operation to add other invoices to the combined invoice. The Exclude button B32 is an operation image that accepts an operation to exclude some invoices from the combined invoice. The Save button B33 is an operation image that accepts an operation to save an edited combined invoice. The Cancel button B34 is an operation image that accepts an operation to cancel editing of a combined invoice. The Exclude from lump sum combination button B35 is an operation image that accepts an operation to exclude the entire combined invoice from lump sum combination.
[0064] On the system screen G3, the operations on the above buttons are performed as editing operations for the combined invoice. The user terminal 20 receives these editing operations through the operation reception unit 212 (A36). On receiving the editing operations, the operation reception unit 212 transmits operation data indicating the content of the received editing operations to the server device 10. The server device 10 executes a reflection process for reflecting the editing by the editing operations indicated by the transmitted operation data (A37).
[0065] For example, when adding another invoice to the combined invoice, the operation reception unit 212 receives an operation on the Add button B31 as an editing operation. In this case, the server device 10 executes a process of reading out billing information of an invoice that can be added to the combined invoice as a reflection process by the memory control unit 112. For example, the memory control unit 112 reads out billing information of an invoice that has not been combined because it has the same billing destination as the combined invoice and the billing date is not the same month and therefore does not meet the combination conditions. The memory control unit 112 transmits the billing information of the read invoice to the user terminal 20. The user terminal 20 displays the billing information of the invoice that was transmitted by the user display unit 211.
[0066] Fig. 12 is a diagram showing an example of displayed billing information of an invoice that can be added. In the example of Fig. 12, billing information D41 of an invoice that can be added is displayed on a system screen G4. On the system screen G4, the billing information D41, the number of invoices that can be added D42, an input field C41 for invoice filtering conditions, an Uncreated button B41, a Created button B42, a Clear button B43, a Filter button B44, a Select button B45, and an Add button B46 are displayed.
[0067] The billing information D41 indicates the billing date, item, billing amount, case ID, invoice number, data source, and delivery date of the invoices that can be added to the combined invoice. The billing information D41, like other billing information, can include both billing information indicated by the invoice information and billing information indicated by the case information. The number of items D42 indicates the number of invoices that can be added to the combined invoice (34 in the example of FIG. 12).
[0068] The input field C41 is an area for inputting the delivery date, billing date, billing destination, and data source. The data source is the information source of the billing information for the invoice, which in this embodiment is invoice information or case information. The Not Created button B41 is an operation image for accepting an operation to narrow down the invoices to invoices that have not been created (not issued). The Created button B42 is an operation image for accepting an operation to narrow down the invoices to invoices that have been created (issued).
[0069] The clear button B43 is an operation image for accepting an operation to clear the input in the input field C41 and return to the state before narrowing down. The narrow down button B44 is an operation image for accepting an operation to narrow down the invoices by the content entered in the input field C41. The select button B45 is displayed alongside the invoice information of each displayed invoice, and is an operation image for accepting an operation to select which of those invoices to add to the combined invoice. The add button B46 is an operation image for accepting an operation to decide to add the selected invoice to the combined invoice.
[0070] For example, when the user finds an invoice to add while narrowing down the invoices to be displayed, the user operates the selection button B45 corresponding to that invoice, and then operates the add button B46. The user terminal 20 accepts these operations as editing operations for the combined invoice via the operation acceptance unit 212 (A36). When the editing operation is accepted, the user terminal 20 displays, via the user display unit 211, the billing information of each invoice before it was combined into the edited combined invoice.
[0071] Fig. 13 is a diagram showing an example of edited billing information for each invoice before addition. In the example of Fig. 13, billing information D33 for each invoice before addition, to which invoice D32 has been added from billing information D31 for each invoice before addition shown in Fig. 11, is displayed on the system screen G3. The user display unit 211 displays a notification image C31 including the character string "One invoice to be added has been added." The notification image C31 is an image indicating that an invoice to be added to the combined invoice has been added through editing.
[0072] The operation reception unit 212 also receives, as an editing operation, an operation to exclude an invoice to be added up, that is, an operation on the exclude button B32 on the system screen G3 shown in Fig. 11 (A36). In this case, the server device 10 executes, as a reflection process, a process in which the storage control unit 112 excludes the invoice information corresponding to the operated exclude button B32 from the combined invoice and stores it in the invoice database DB1 as invoice information indicating a separate invoice (A37). In the user terminal 20, the user display unit 211 displays according to the editing operation.
[0073] Fig. 14 is a diagram showing another example of edited billing information for each invoice before addition. In the example of Fig. 14, billing information D34 for each invoice before addition, in which one invoice has been deleted from billing information D31 for each invoice before addition shown in Fig. 11, is displayed on the system screen G3. The user display unit 211 displays a notification image C32 including the character string "Billing data has been excluded." The notification image C32 is an image indicating that an invoice to be added up has been excluded by editing.
[0074] The operation reception unit 212 also receives, as an editing operation (A36), an operation to exclude all invoices to be added from the lump sum addition, that is, an operation on the Exclude from Lump Sum Addition button B35 on the system screen G3 shown in Fig. 11. When the Exclude from Lump Sum Addition button B35 is operated, the user display unit 211 displays the screen shown in Fig. 15.
[0075] FIG. 15 is a diagram showing an example of a display when an operation to exclude invoices from the lump sum is performed. For example, suppose that the user looks at the billing information D31 of each invoice before the summation shown in FIG. 11, decides that the invoice should be excluded from the lump sum, and operates the exclude button B35. In that case, the user display unit 211 displays a notification image C33 including the character string "Do you want to exclude the invoice from the lump sum? If you exclude it, this invoice will not be created in this lump sum creation." as shown in FIG. The notification image C33 is an image for confirming whether it is OK to exclude all displayed invoices to be added from the lump sum.
[0076] The user display unit 211 displays a cancel button B37 and a enter button B38 superimposed on the notification image C33. When the cancel button B37 is operated, the user display unit 211 stops displaying the notification image C33 and returns to the display before the exclude button B35 was operated. When the enter button B38 is operated, the user terminal 20 accepts, via the operation acceptance unit 212, an editing operation to exclude all displayed invoices to be added up from lump-sum addition.
[0077] In this case, the server device 10 executes a process of storing all of the displayed invoices to be added together as invoice information indicating individual invoices in the billing database DB1 as a reflection process by the memory control unit 112 (A37). For example, when the Exclude from Bulk Addition button B35 is pressed for a combined invoice that includes three invoices, the memory control unit 112 executes a process of storing invoice information representing each of the three invoices as an individual invoice in the billing database DB1 as a reflection process.
[0078] Furthermore, in the user terminal 20, the user display unit 211 performs display according to the editing operation. Fig. 16 is a diagram showing an example of the display when the operation to exclude from lump sum addition has been confirmed. In the example of Fig. 16, the user display unit 211 displays the system screen G2 shown in Fig. 9 again, and displays a notification image C34 including the character string "The invoice to billing destination C has been excluded from lump sum addition." The notification image C34 is an image for notifying that the exclusion from lump sum addition has been confirmed.
[0079] The user display unit 211 also displays a list D51 of combined invoices in which the number of invoices to be consolidated has been reduced by one, and the number of invoices after consolidation D52. The number of invoices after consolidation D22 shown in Fig. 9 was "200", but the number of invoices after consolidation D52 is "199" because one invoice has been reduced by the operation to exclude it from the consolidated consolidation.
[0080] The user performs various editing operations as described above to finalize the contents of the combined invoice that is to be the subject of the lump sum addition. Fig. 17 is a diagram showing an example of a list of combined invoices after editing has been completed. In the example of Fig. 17, an invoice list D61 in which several combined invoices have been edited from the combined invoice list D21 shown in Fig. 9 is displayed.
[0081] For example, the number of invoices to be combined for invoice recipients A and E has increased from 2 to 3 and from 1 to 2, respectively. Additionally, the number of invoices to be combined for invoice recipient F has decreased from 30 to 28. In addition, invoice recipient C, which was included in the list of combined invoices D21, is no longer included in the lump-sum combination. Therefore, while the number of items after combination D22 shown in Figure 9 was 200, the number of items after combination D62 shown in Figure 17 is 199.
[0082] When the user has completed the necessary editing operations on the list of combined invoices, they operate the Create button B24. The user terminal 20 receives the operation on the Create button B24 via the operation reception unit 212 as an instruction operation to create the combined invoices all at once (A41). Note that the operation reception unit 212 may receive this instruction operation immediately after the list of combined invoices is displayed in A27. When the user terminal 20 receives this instruction operation, it transmits to the server device 10 creation instruction data indicating the billing information of each combined invoice included in the invoice list and an instruction to create those combined invoices.
[0083] When the server device 10 receives the transmitted creation instruction data, the storage control unit 112 executes a lump sum processing to reflect the billing information of each combined invoice indicated by the received creation instruction data in the billing database DB1 (A42). Here, the area in which the information on billing generated in the lump sum processing (such as the invoice list D11 shown in FIG. 8 and the combined invoice list D21 shown in FIG. 9) is stored will be described with reference to FIG.
[0084] Fig. 18 is a diagram showing an example of information related to a bill that is generated. Fig. 18 shows a first memory area and a second memory area secured in the memory unit 12 in the lump sum processing. These first memory area and second memory area are areas for temporarily storing information related to a bill when the lump sum processing is executed. The first memory area stores information to be reflected in the billing database DB1. The second memory area is an area for temporarily storing necessary information that is not reflected in the billing database DB1 but is used while the lump sum processing is being executed.
[0085] In Fig. 18(a), in the lump sum processing, first, billing information indicated by the invoice information read from the invoice database DB1 and billing information indicated by the case information read from the case database DB2 are shown. Each of these billing information includes an invoice number (including a case number that is set as a temporary invoice number). In the example of Fig. 18, the invoice numbers are consecutive numbers for ease of explanation, but in reality this does not have to be the case, and it is sufficient that unique invoice numbers are assigned.
[0086] The storage control unit 112 stores the billing information of each invoice to be included in the lump sum shown in Fig. 18(a) in the first storage area. When an instruction to create a combined invoice is given, the storage control unit 112 generates billing information indicating each combined invoice and stores it in the first storage area, as shown in Fig. 18(b), and moves and stores the billing information of each invoice to be added to the second storage area. In addition, when, for example, some invoices are excluded from the combined invoice or the entire combined invoice is excluded from the lump sum, the storage control unit 112 deletes the corresponding billing information (billing information excluded from the addition) stored in the first storage area and stores the billing information in the second storage area.
[0087] When the storage control unit 112 executes the lump sum processing, it transmits count data indicating the number of combined invoices created by the lump sum processing to the user terminal 20. The user terminal 20 displays the number of combined invoices indicated by the transmitted count data on the user display unit 211 (A43). Fig. 19 is a diagram showing an example of the display of the number of combined invoices. In the example of Fig. 19, the user display unit 211 displays a notification image C71 including the character string "199 invoices have been created" on a system screen G7 including an invoice list D71 of the collectively combined invoices. The notification image C71 is an image showing the number of combined invoices created by the collectively combined process.
[0088] Once the server device 10 has created the combined invoice as described above, the billing output unit 116 outputs billing data showing the created combined invoice (A44). The billing output unit 116 outputs the billing data to a printer, for example, and issues the invoice on paper. The billing output unit 116 also outputs the billing data to the business system of the billing destination, which then processes the payment based on the output billing data. In this way, the billing output unit 116 outputs the billing data to the output destination according to the invoice processing method.
[0089] As described above, in the billing management system 1, the information acquisition unit 113 is an example of an acquisition unit that acquires multiple pieces of invoice information. Each of the multiple pieces of invoice information is information indicating the content of the respective bill. Furthermore, the amount calculation unit 115 is an example of a calculation unit that calculates the total amount of bills whose content satisfies a common condition (aggregation condition) based on the multiple pieces of invoice information acquired by the information acquisition unit 113. Multiple common conditions are defined. For example, in the example of FIG. 9, the common condition is that the billing destination and closing date are the same.
[0090] Moreover, the billing output unit 116 is an example of an output unit that outputs billing data. Specifically, the billing output unit 116 outputs billing data indicating a bill for each of a plurality of total amounts calculated for a plurality of common conditions. According to this embodiment, the number of processes can be reduced by consolidating bills compared to when all bills are processed individually in billing operations, and the effort required for operations related to billing can be reduced.
[0091] Furthermore, the information acquisition unit 113 acquires one or more pieces of invoice information and one or more pieces of case information. The invoice information is information indicating the content of each invoice. The case information is information regarding the case in which a transaction occurs, and indicates the content of the invoice arising in the transaction (such as the invoice destination and invoice amount). Furthermore, based on the invoice information and case information acquired by the information acquisition unit 113, the amount calculation unit 115 calculates the total amount of invoices whose invoice content satisfies a common condition (aggregation condition).
[0092] Then, the bill output unit 116 outputs bill data indicating a bill for the total amount calculated by the amount calculation unit 115. According to this embodiment, it is possible to reduce the amount of work related to bills even for cases at a stage before the invoice information is generated, compared to a case where the case information is not used to calculate the total amount.
[0093] The common conditions (combined conditions) are not limited to the billing destination and closing date described above. The common conditions may be a condition that one of the billing destination, billing date, closing date, or payment deadline is common, or a condition that two or more of them are common. Regardless of the conditions used, tasks related to multiple bills can be performed together.
[0094] Furthermore, the amount calculation unit 115 calculates the total amount of claims that have the same billing destination among claims that satisfy the common conditions for the contents of the claims. According to this embodiment, claims that have the same billing destination are issued as a combined invoice, so that multiple invoice data are not output to the same billing destination.
[0095] The server display unit 111 is an example of a first display unit that executes a process to display the number of items for which the total amount has been calculated. For example, the server display unit 111 executes a process to display the number of combined invoices, i.e., the number of items for which the total amount has been calculated, is 199, in the notification image C71 shown in Fig. 19. According to this embodiment, the displayed number can be understood as the number of invoices after the addition.
[0096] The server display unit 111 is also an example of a second display unit that executes a process for displaying the number of claims included in the calculated total amount in association with the calculated total amount. For example, in the total number D22 shown in Fig. 9, the server display unit 111 indicates that the total amount of two claims has been calculated for the claim destination A, and the total amount of ten claims has been calculated for the claim destination B. According to this embodiment, it is possible to grasp the number of claims included in each total amount.
[0097] The server display unit 111 is also an example of a third display unit that executes a process for displaying a list of billing details included in the calculated total amount in association with the calculated total amount. For example, the server display unit 111 displays billing information D31 of the invoice shown in Fig. 11 as a list of billing details included in the total amount of the invoice for invoice destination C. According to this embodiment, the combined billing details can be understood.
[0098] Furthermore, when a bill to be separated is selected from the displayed list, the bill output unit 116 outputs bill data indicating the separated bill and bill data indicating the bills included in the list excluding the separated bill. For example, in the example of FIG. 14, one of the three bills to billing destination C is excluded from the combined bill. In this case, the bill output unit 116 outputs bill data for the excluded bill and bill data indicating the remaining bills on the combined bill. According to this embodiment, the combined bill can be separated as necessary.
[0099] Furthermore, when an instruction is given to add another bill to the total amount calculated by the amount calculation unit 115, the bill output unit 116 outputs bill data indicating a bill for the total amount plus the amount of the other bill. For example, in the example of Fig. 13, the amount of another bill, bill D32, is added to the total amount of three bills to bill recipient C. According to this embodiment, bills can be further added up as necessary.
[0100] <Other embodiments> In the embodiment, the billing output unit 116 outputs the billing data to a printing device or a business system of the billing destination, but the output destination of the billing data is not limited to this. For example, the billing output unit 116 may display the billing contents on a display connected to the server device 10, or may output the billing data to a storage device and store the billing contents.
[0101] <Setting whether or not to combine> In the billing management system 1, it may be possible to set whether or not each bill should be added to the total amount (i.e., whether or not it should be included in the combined invoice). In this case, the amount calculation unit 115 calculates the total amount of bills that are set to be added to the total amount among bills whose contents satisfy a common condition (combination condition).
[0102] For example, information indicating whether or not a bill can be included in a combined invoice is stored in the billing database DB1 shown in Fig. 6. Then, the amount calculation unit 115 calculates the total amount by adding bills that are set as being eligible for a combined invoice to the total amount, but not adding bills that are set as not eligible for a combined invoice to the total amount. According to this embodiment, if a bill is set as not eligible for a combined invoice, it will not be included in the combined invoice, so that individual billing can be done as necessary.
[0103] In addition, in the billing destination master that stores billing destinations, it may be possible to set automatic summation for each billing destination. For billing destinations for which automatic summation is set to "ON", the lump sum processing described above is automatically performed every time an invoice is created. This makes it easier to create invoices in a more appropriate format for each billing destination.
[0104] <Configuration variations> The configuration shown in FIG. 1 etc. is an example, and other configurations may be used as long as there is no inconvenience in implementation. For example, one device may be distributed to two or more devices, or may be replaced by a cloud computing system. Furthermore, the functions of one device may be distributed and realized to two or more devices, or the functions of two or more devices may be concentrated and realized in one device. Furthermore, the operation performed by one function may be distributed to two or more functions, or two or more functions may be integrated into one function. In short, as long as each function required for the entire billing management system 1 is realized, the devices that realize those functions may have any configuration.
[0105] The above-described aspects of the embodiment are an information processing device such as the server device 10, and an information processing system such as the billing management system 1 including the server device 10, but may also be an information processing method. The information processing method includes each step of the information processing system. The above-described aspects of the embodiment may also be a program. The program causes a computer to execute each step of the information processing system.
[0106] <Other variations> The output destination of information or data (hereinafter referred to as "information, etc.") may be another device, a display, a memory unit (including a built-in memory unit and an external memory unit), etc. Acquisition of information, etc. includes acquiring information, etc. generated by the device itself, in addition to acquiring information, etc. transmitted from another device. The table in which parameters are associated is not limited to the table shown in the figure, and the number of parameters may be reduced or increased. Furthermore, information, etc. corresponding to parameters may be obtained by a formula, a conditional formula, a macro, etc., without using a table.
[0107] <Additional Notes> Furthermore, it may be provided in the following aspects:
[0108] (1) An information processing system comprising a processor, wherein in an acquisition step, the processor acquires a plurality of invoice information, each of the plurality of invoice information being information indicating the contents of a respective invoice, and in a calculation step, calculates a total amount of invoices whose contents satisfy a common condition based on the acquired plurality of invoice information, a plurality of the common conditions being defined, and in an output step, outputs invoice data indicating a invoice for each of the plurality of total amounts calculated for the plurality of common conditions.
[0109] According to this embodiment, the work involved in invoices can be reduced.
[0110] (2) An information processing system comprising a processor, wherein in an acquisition step, the processor acquires one or more pieces of invoice information and one or more pieces of case information, the invoice information being information indicating the content of each invoice, the case information being information regarding a case in which a transaction occurs and indicating the content of the invoice arising in the transaction, in a calculation step, based on the acquired invoice information and case information, calculates a total amount of invoices whose content satisfies a common condition, and in an output step, outputs invoice data indicating the calculated total amount of invoices.
[0111] According to this embodiment, it is possible to reduce the workload of invoice-related tasks even for cases at a stage before invoice information is generated.
[0112] (3) In the information processing system described in (1) or (2) above, the common condition is that the billing destination, billing date, closing date, or payment deadline is the same.
[0113] According to this embodiment, tasks related to multiple claims can be carried out all at once.
[0114] (4) In the information processing system described in any one of (1) to (3) above, in the calculation step, the processor calculates a total amount of claims that have a common billing destination among claims whose content satisfies the common condition.
[0115] According to this aspect, it is possible to prevent multiple invoice data from being output to the same invoice destination.
[0116] (5) An information processing system according to any one of (1) to (4) above, wherein the claim can be set as to whether or not to add it to the total amount, and in the calculation step, the processor calculates the total amount of claims whose content satisfies the common condition and which are set to be added to the total amount.
[0117] According to this embodiment, individual claims can be made as necessary.
[0118] (6) In the information processing system according to any one of (1) to (5) above, in the first display step, the processor executes a process for displaying the number of items for which the total amount has been calculated.
[0119] According to this embodiment, it is possible to grasp the number of invoices after the total amount is added up.
[0120] (7) In the information processing system described in any one of (1) to (6) above, in a second display step, the processor executes a process for displaying the number of claims included in the calculated total amount in correspondence with the calculated total amount.
[0121] According to this embodiment, it is possible to grasp the number of claims included in the total amount.
[0122] (8) In the information processing system described in any one of (1) to (7) above, in a third display step, the processor executes processing to display a list of billing details included in the calculated total amount in correspondence with the calculated total amount.
[0123] According to this embodiment, it is possible to grasp the contents of the combined bill.
[0124] (9) In the information processing system described in (8) above, in the output step, when a claim to be separated is selected from the displayed list, the processor outputs invoice data indicating the separated claim and invoice data indicating the claims included in the list excluding the separated claim.
[0125] In this manner, the combined claims can be separated as necessary.
[0126] (10) In the information processing system described in any one of (1) to (9) above, in the output step, when an instruction is given to add another bill to the calculated total amount, the processor outputs invoice data indicating a bill for the amount of the other bill added to the total amount.
[0127] In this manner, claims can be further aggregated as necessary.
[0128] (11) An information processing method comprising the steps of the information processing system according to any one of (1) to (10) above.
[0129] According to this embodiment, the work involved in invoices can be reduced.
[0130] (12) A program for causing a computer to execute each step of the information processing system according to any one of (1) to (10) above.
[0131] According to this embodiment, the work involved in invoices can be reduced. Of course, this is not the case. Furthermore, the above-described embodiments and modifications may be combined in any desired manner.
[0132] Finally, although various embodiments of the present invention have been described, these are presented as examples and are not intended to limit the scope of the invention. The new embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. The embodiments and their modifications are within the scope and spirit of the invention, and are included in the scope of the invention and its equivalents described in the claims. [Explanation of symbols]
[0133] 1: Billing management system 10: Server device 11: Control section 20: User terminal 21: Control section 111: Server display section 112: Memory control unit 113: Information acquisition department 114: Information and Counting Department 115: Amount Calculation Department 116: Billing output section 211: User display section 212: Operation reception section
Claims
1. An information processing system, a processor, the processor comprising: In the acquisition step, a plurality of pieces of invoice information are acquired, each of the plurality of pieces of invoice information being information indicating the contents of a respective invoice; In the calculation step, a total amount of invoices whose contents satisfy a common condition is calculated based on the plurality of invoice information acquired, and the common condition is defined in a plurality of ways, In the output step, for each of the total amounts calculated for the common conditions, invoice data indicating an invoice for the total amount is output. Information processing system.
2. An information processing system, a processor, the processor comprising: In the acquisition step, one or more pieces of invoice information and one or more pieces of case information are acquired, the invoice information being information indicating the contents of each invoice, the case information being information regarding a case in which a transaction occurs, indicating the contents of the invoice arising in the transaction, In the calculation step, a total amount of claims whose contents satisfy a common condition is calculated based on the acquired invoice information and case information; In the output step, invoice data showing the calculated total amount is output. Information processing system.
3. 2. The information processing system according to claim 1, The common condition is that the billing destination, billing date, closing date, or payment deadline is the same. Information processing system.
4. 2. The information processing system according to claim 1, The processor, In the calculation step, a total amount of claims having a common billing destination is calculated among claims whose contents satisfy the common condition. Information processing system.
5. 2. The information processing system according to claim 1, The charge can be set to be added to the total amount or not, The processor, In the calculation step, a total amount of claims that satisfy the common condition and are set to be added to the total amount is calculated. Information processing system.
6. 2. The information processing system according to claim 1, The processor, In the first display step, a process for displaying the number of items for which the total amount has been calculated is executed. Information processing system.
7. 2. The information processing system according to claim 1, The processor, In the second display step, a process is executed for displaying the number of claims included in the calculated total amount in association with the calculated total amount. Information processing system.
8. 2. The information processing system according to claim 1, The processor, In a third display step, a process is executed to display a list of billing contents included in the calculated total amount in association with the calculated total amount. Information processing system.
9. 9. The information processing system according to claim 8, The processor, In the output step, when a claim to be separated is selected from the displayed list, bill data showing the separated claim and bill data showing claims included in the list excluding the separated claim are output. Information processing system.
10. 2. The information processing system according to claim 1, The processor, In the output step, when an instruction is given to add another bill to the calculated total amount, bill data indicating a bill for the amount obtained by adding the amount of the other bill to the calculated total amount is output. Information processing system.
11. 1. An information processing method, comprising: The information processing system according to any one of claims 1 to 10, Information processing methods.
12. A program, A computer is caused to execute each step of the information processing system according to any one of claims 1 to 10. program.
Citation Information
Patent Citations
Electronic bill management system
JP2002259900A
