Information processing device, information processing system, and program

Abstract

Automate the generation of legal documents or archiving of data. [Solution] The information processing device includes a processing circuit that identifies a billing destination based on a billing request from a billing source, presents an invoice addressed to the billing destination from the billing source and including necessary information, and, when a request for sending of the generated invoice is received from the billing source, sends the invoice to the billing destination or notifies the billing destination that the invoice has been issued, and stores the invoice in a database.

Description

[Technical field]

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

[0002] Regarding billing at the time of a transaction, the items to be recorded vary greatly depending on the laws applied at the time of the transaction or settlement. For example, as of 2024, the number of required items has increased due to the invoice system introduced in October 2023, and it is also necessary to keep data that can be referenced for those items.

[0003] There are cloud services and other such services that automatically calculate and store invoice items and tax rates, but automated services that correspond to the invoice system, for example, are still in their infancy. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2019-109555 A Summary of the Invention [Problem to be solved by the invention]

[0005] Thus, one of the non-limiting problems that the embodiments of the present disclosure aim to solve is to automatically create legal documents or store data. The problem that the embodiments of the present disclosure aim to solve can be, as some further non-limiting examples, a problem corresponding to the effects described in the embodiments. That is, a problem that corresponds to at least one of the effects described in the description of the embodiments of the present disclosure can be the problem that the present disclosure aims to solve. [Means for solving the problem]

[0006] The information processing device includes a processing circuit that identifies a billing destination based on a request from a billing source, presents an invoice addressed to the billing destination from the billing source and including necessary items, and, when a request for sending the generated invoice is received from the billing source, sends the invoice to the billing destination or notifies the billing destination that the invoice has been issued, and stores the invoice in a database. [Brief description of the drawings]

[0007] [Figure 1] FIG. 1 is a diagram showing an example of a configuration of an information processing system according to an embodiment. [Diagram 2] 1 is a flowchart showing an example of processing of an information processing system according to an embodiment. [Diagram 3] 1 is a flowchart showing an example of processing of an information processing system according to an embodiment. [Figure 4] 1 is a flowchart showing an example of processing of an information processing system according to an embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] Hereinafter, the embodiments of the present disclosure will be described with reference to the drawings. The drawings are used for explanation, and the shape, size, or size ratio of each component in an actual device to other components does not necessarily have to be as shown in the drawings. In addition, since the drawings are simplified, components necessary for implementation other than those shown in the drawings are also appropriately provided.

[0009] <Management of contracts and qualified invoices>

[0010] 1 is a diagram showing a schematic diagram of an information processing system according to an embodiment. The information processing system 1 includes a server 10 provided in a cloud and a client 20 that can access the server 10 in the cloud. The information processing system 1 may be configured as a system that executes various processes in the server 10 on the cloud in response to a request from the client 20.

[0011] The information processing system 1 may be configured to include one or more servers 10. The one or more servers 10 may be configured to include a computation server that executes computations and a file server that stores files.

[0012] The client 20 is a terminal used by a user, and the user can use the services provided by the server 10 via the client 20. The client 20 is, for example, a computer, a smartphone, a tablet terminal, etc. owned by the user, but is not limited to these.

[0013] In this disclosure, the term "information processing device" may refer to a server 10 or a client 20. The information processing device includes at least a storage unit and / or a processing unit. These components may be semiconductor devices formed separately or integrally. The processing unit may include a processing circuit that executes processing in the information processing device.

[0014] The processing circuit may include a general-purpose processor (CPU: Central Processing Unit, GPU: Graphics Processing Unit, etc.) or a dedicated processor (ASIC: Application Specific Integrated Circuit), etc. At least a part of these processors may include analog circuits and / or digital circuits. At least a part of these processors may be formed of rewritable circuits such as FPGAs (Field Programmable Gate Arrays).

[0015] Also, when the term "program" is used, it means that the program is for specifically implementing information processing by software using any of the information processing devices in the information processing system 1, which is a hardware resource. At least a part of the processing circuit can be implemented by referring to an executable file, etc., stored in the storage unit.

[0016] The information processing system 1 can provide the information processing of the present disclosure as a cloud service. The information processing system 1 can provide the service by a method such as SaaS (Software as a Service), and can also provide the service in a form of accessing a server via a browser or the like.

[0017] Fig. 2 is a flowchart showing an example of processing of the information processing system 1 according to an embodiment. The processing in Fig. 2 shows processing between a seller client 20 and the server 10. It is assumed that data on seller users is stored in the server 10 in advance. If user data does not exist in the server 10, the server 10 can obtain and generate the necessary data on a new user in response to a request from the client 20.

[0018] The client 20 transmits a billing request to the server 10 based on input from the user (S100). The client 20 accepts at least a request that specifies the billing destination. The user inputs data required for billing via a UI (User Interface, including GUI: Graphical User Interface) displayed on a browser or software (hereinafter referred to as a browser, etc.) as a cloud service, and the client 20 transmits a bill based on the input data to the server 10.

[0019] As a non-limiting example, the information processing system 1 may be in a form in which an invoice template or the like is provided to the client 20 and the user inputs necessary information such as the invoice destination, billing item name, and billing amount (including quantity). Data such as the invoice destination and billing items can be registered in advance in the server 10 by the user, and can be set in a selection format based on this registered information. The user can also set the billing items, etc., using a template or the like that is prepared in advance by the server 10.

[0020] As a non-limiting example, the information processing system 1 may be configured to receive data of an invoice separately created by a user via an interface of the client 20. In this case, the client 20 may appropriately extract the invoice destination, invoice items, invoice amount, etc. based on OCR or metadata embedded in the document. Alternatively, the client 20 may transmit the invoice data to the server 10, and the server 10 may extract the invoice destination, invoice items, invoice amount, etc.

[0021] The client 20 may present information on other users who are registered as business partners of the user from the user. In other words, the user may use the information processing system 1 to select a billing destination that is registered in advance as a business partner.

[0022] Furthermore, the information processing system 1 can transmit to the server 10 the designation of the contract related to the billing input by the user via the client 20. The input of the contract by the user can also be in a form in which the client 20 can select a contract, memorandum, etc. related to an already concluded contract by referring to a database related to both parties in the server 10. When the billing destination is selected as described above, the server 10 can also be configured to present a contract, etc. related to the business partner selected by the user as the billing destination, based on a request from the client 20.

[0023] The user-related information may be stored in the server 10 or in a storage area within the client 20. In this case, customer information and the like is not released to the outside, and input from the user is accepted within the client 20 and encrypted, thereby achieving safer communication.

[0024] Also, the client 20 may be in a form that allows the user to select billing items, etc. based on past transaction records based on the specified billing information received from the user. The client 20 may be in a form that allows the user to confirm by presenting an invoice that lists billing items, billing amounts, etc. based on past records based on the billing information received from the user.

[0025] In addition, the client 20 can provide the user with various processes based on past transaction records. For example, the client 20 can present candidates for business partners to the user, or can suggest transaction items, transaction amounts, etc. after identifying a business partner. The user can select from among those proposed by the client 20, or can generate a new invoice for the business partner via the client 20.

[0026] The client 20 may be configured to accept input of the transaction date from the user. If the user does not input the transaction date, the client 20 may set the invoice issue date as the transaction date.

[0027] The server 10, which receives a billing request from the client 20, acquires information on the biller and billee related to the bill accepted by the client 20, and checks whether a contract has been concluded between the biller and billee that permits settlement of the billing item (S200).

[0028] The contract does not exclude the inclusion of contracts for transactions other than the billing items. The contract also allows for business in accordance with the items within the scope described. In general, contracts are often concluded according to the actual circumstances of the transaction. The contract in this disclosure may also correspond to the actual circumstances of this general transaction.

[0029] That is, the requesting user can enter into a contract including various services in line with the business with the requestee user via the client 20. In this case, the requesting user can not only make a claim related to the billing items limited to the contents of the contract concluded via the client 20, but can also realize a claim related to the business between the requesting user and the requestee within or outside the scope of the contract.

[0030] In other words, the information processing system 1 is capable of issuing, settling, and managing invoices not only for billing items related to work within the contract concluded between the two users, but also for billing items related to work outside the contract.

[0031] As described above, when the client 20 receives a specification of the contract related to the accepted claim, the server 10 may extract the contract related to the claim from the database in which it is stored. If extraction is not possible, the server 10 may perform a process equivalent to S202: NO shown below.

[0032] If a contract relating to the billing item between the biller and billee exists in the database (S202: YES), the process moves to branch A which indicates processing for the billee.

[0033] The contract is not limited to one stored in the database, but may be a contract already concluded between the requester and the requestee, or some electronic document in lieu of the contract that the requester has sent to the server 10 in the process of S100. In this case, the server 10 also proceeds to the process of branch A.

[0034] 3 is a flowchart showing the process in branch A according to one embodiment. The server 10, which has confirmed the existence of a contract concluded for the billing item, issues an invoice based on the received billing request.

[0035] The server 10 issues an invoice based on the information acquired from the client 20 (S204). The server 10 can create an invoice that includes information required by law. The server 10 can create an invoice that conforms to the invoice system, for example. The server 10 can include, for example, the issuer name (which may be replaced by a trade name), registration number, transaction date, transaction details (transaction items), transaction price, applicable tax rate, consumption tax amount, and recipient's name on the invoice it creates.

[0036] If the server 10 cannot find the registration number associated with the user in the database, it can request the user to input the registration number via the client 20. The user inputs the registration number via the client 20, and the client 20 notifies the server 10 of the registration number input by the user, and the server 10 can associate this registration number with the user and register it in the database.

[0037] Depending on the user's instruction via the client 20, the server 10 may create an invoice that conforms to the legal system, listing the applicable tax rate but not the amount of consumption tax. The server 10 may also create an invoice that does not list the recipient's name. The server 10 may also list invoices for a certain period of time together. In this case, the server 10 may request the user to submit delivery notes, invoices, etc. showing transactions during this certain period of time, and after receiving the documents from the user via the client 20, issue a combined invoice.

[0038] If there is any missing information about the other party (billing destination), the server 10 can notify the client 20 of the other party to request the input of the relevant information. When the information about the other party is complete, the server 10 can finalize the invoice.

[0039] Regarding other missing information, the server 10 can notify the user who is missing the information via the client 20 which can be operated and can view the information, and when all the information is collected, the invoice can be created.

[0040] The server 10 notifies and sends the issued invoice to the billing destination client 20. At this time, the server 10 can also send the client 20 a link for making payment related to the invoice.

[0041] The server 10 can also send information about the contract together with the invoice to the client 20 to which the invoice is to be sent. The server 10 can notify the client 20 to which the invoice is to be sent of information about the concluded contract linked to the invoice to be issued, for example, a link to view the contract.

[0042] The server 10 can also set a billing deadline. The billing deadline may be set by the user via the client 20. If the content is not submitted or the payment is not completed by the billing deadline, the server 10 or the client 20 can send a reminder to the billing destination via the client 20 as appropriate. In addition, the server 10 or the client 20 can also remind the user via the billing destination client 20 at a set timing prior to the set billing deadline.

[0043] The server 10 can store information about issued invoices in a database and store and manage them as invoices whose settlement has not yet been completed.

[0044] The client 20 presents the user with a link (hyperlink) for making payment together with the contents of the invoice (S310). The client 20 may transition to a state in which it is waiting for approval of the payment from the user. In addition, the user can temporarily hold the payment presented to the client 20 and transition to the above-mentioned state in which it is waiting for approval, and execute the payment at any timing.

[0045] The client 20 may record that the contents have been presented. If the contents have not been presented to the user within a predetermined period, the client 20 may notify the user again. The record of the confirmation of the contents may be managed on the server 10 side. The fact that the contents have been presented to the billing destination may be in a form that can be referenced by the client 20 that made the request.

[0046] If the client 20 also notifies information about the contract in S210, the client 20 can present the information about the contract together with the information of the issued invoice. Also, the invoiced client 20 can present the contract in the database selected by the user via the invoice source client 20.

[0047] The user can refer to data such as invoices in the server 10 via the client 20 by following hyperlinks or the like presented on the client 20 on a browser or application.

[0048] The client 20 may present the invoice issued to the user, and may also present information related to the issued invoice in an appropriate data format. For example, the client 20 may provide data to the user in a database format, a file format such as CSV, other text file formats, a format for any application (accounting software, tax software, or other software for referencing and editing data), any other binary file format, or any description language format such as MHT or XML.

[0049] The client 20 accepts whether or not to approve (agree) to the payment related to the invoice issued by the user (S312). If the user does not approve (agree) (S312: NO), the client 20 notifies the server 10 that the payment has not been approved.

[0050] The server 10 notified that the claim was not approved notifies the biller that the claim was not approved (S212). Subsequent processing, for example, the users can resolve the issue between themselves, and reissue the invoice with the consent of the users, etc., according to the processing in Fig. 2. As a non-limiting example, the subsequent flow may be the same as the flow from branch B in Fig. 2.

[0051] In other words, both users may execute the contract conclusion process via information processing system 1, or they may conclude a contract outside of information processing system 1 and notify information processing system 1 of this, thereby enabling re-billing and payment processing.

[0052] If approved (S312: YES), the client 20 accepts the payment method from the user and requests the server 10 to make the payment using that payment method (S314). The server 10 executes the payment based on the request from the client 20 (S214). The details of the payment method will be described later.

[0053] If the payment cannot be executed, the server 10 notifies the user via the client 20 that the payment could not be executed, and can request the user to change the means to enable the payment and to execute the payment again.

[0054] After the settlement is completed, the server 10 can link the information indicating that the settlement has been completed and manage the invoice related to the claim (S216). The server 10 can present the invoice, linked with the information indicating that the settlement has been completed, at any timing based on a request from the user (the biller and / or the billee) via the client 20 or an agent who is legally permitted to view invoices, etc. and can refer to the information of the user (for example, a tax accountant or a certified public accountant delegated by the user).

[0055] As described above, the information processing system 1 makes it possible to smoothly and electronically process invoices, settlements, and other processes based on billing requests. These processes can be completed on the cloud, improving user convenience. In addition, document management can be automatically performed electronically, making it possible to perform annual processing, settlement of accounts, and the like with high efficiency and precision.

[0056] Next, a case where the contract cannot be confirmed in S202 will be described.

[0057] 4 is a flow chart illustrating a non-limiting example of processing related to branch B according to an embodiment. If the server 10 is unable to confirm the existence of a contract concluded for a billing item, it can notify both users of the processing related to the contract required to bill the received billing request.

[0058] The server 10 requests the contract related to the claim from the client 20 that made the claim (S220). Although not shown in the flowchart, if a concluded contract that already exists in the database can be used or invoked at this stage, the client 20 accepts the user's selection of the contract to be used or invoked and notifies the server 10, and the server 10 can execute the process of branch A shown in Fig. 3 based on the contract.

[0059] Although not shown in the flowchart, a contract is not a required component of the process. The billing client 20 can also request the issuance of an invoice for work outside the contract that has been concluded. The client 20 may obtain a flag for billing items related to work outside the contract and notify the server 10 of the flag. Conversely, the client 20 may obtain a flag for billing items related to a contract that has been concluded and notify the server 10 of the flag.

[0060] Based on information that the requested claim can be processed outside the contract, the information processing system 1 can skip the processes from S220 to S222 and move to branch A. In this case, upon request from the claimant user, the information processing system 1 can automatically execute the process of branch A even in the absence of a contract.

[0061] For example, the information processing system 1 can continue the invoice issuing process without checking for ongoing contracts from the biller to the billee, contracts for related items, or contracts for different items to the same billee.

[0062] In addition, it is also possible to process additional charges from the billing source, additional invoices, etc. By omitting the processing of these contract requests, etc., it becomes possible to more smoothly realize, for example, transactions related to continuous business.

[0063] When the client 20 receives the request for the contract from the server 10, it notifies the user accordingly. After this notification, the client 20 accepts input related to the contract from the user and transmits the contract to the server 10 (S120). The client 20 can have the user select whether or not the contract has been concluded between the billing party and the billed party, and transmit the selection result together with the contract to the server 10.

[0064] The client 20 may notify the user that a contract is to be uploaded. The contract to be uploaded may be a contract (such as a memorandum of understanding) for an already concluded contract.

[0065] The client 20 may also display a contract template to the user to assist in creating the contract. In this case, the client 20 may transmit the contract created based on the template to the server 10.

[0066] When the client 20 receives an unsigned contract from a user, the client 20 may also obtain information related to the electronic signature. By obtaining information related to the certificate of the electronic signature, etc., it becomes possible to proceed with the contract signing process in the cloud service. In addition, a user who has used an electronic signature in the information processing system 1 in the past can store information related to the electronic signature in the server 10 or the client 20 and reuse it.

[0067] The server 10 that has received the contract stores the contract in association with both parties, and checks whether the contract has already been concluded between the billing party and the billed party (S222). If the contract has already been concluded between the billing party and the billed party (S222: YES), the server 10 can execute the process from branch A.

[0068] If the received contract is an unsigned contract (S222: NO), the server 10 transmits information related to this contract to the client 20 to which the contract is to be billed (S224). The server 10 transmits information related to the contract to, for example, the client 20 to which the contract is to be billed. As above, the information related to the contract may be information such as a hyperlink for accessing the contract in the server 10. The server 10 may also notify the user to which the contract is to be billed to encourage the user to conclude the contract.

[0069] The billing destination client 20 can present a contract to the user based on the received information (S320).

[0070] After presenting the information, the client 20 receives a decision from the user as to whether or not to conclude the contract (S322). In other words, the user can confirm the information of the presented contract document, and then decide whether or not to conclude the contract, and notify the server 10 of this decision via the client 20.

[0071] When the billed client 20 receives input from the user that the contract can be concluded, it can also obtain a certificate of an electronic signature, etc., related to the billed user and transmit it to the server 10. The server 10 or the client 20 can also manage information related to an electronic signature, etc., related to the billed user, in the same way as the information of the requester.

[0072] Also, the billed client 20 may store information on the electronic signature of the billed user, in which case, when the billed client 20 receives an input from the user that the contract can be concluded, the server 10 may automatically transmit a certificate for the electronic signature, etc. to the server 10. As another example, when the server 10 receives a notification from the billed client 20 that the contract can be concluded, the server 10 may refer to a database to search for information on the certificate for the electronic signature, etc. of the billed user, and if it exists, automatically conclude the contract based on the information on the certificate.

[0073] The server 10 that has received the notification from the client 20 judges whether or not a contract can be concluded based on the response from the client 20 to which the request is made (S226). If the server 10 judges that the contract can be concluded (S226: YES), for example, if both parties' electronic signatures, etc. have been obtained, the server 10 can conclude the contract on the memorandum, that is, complete the electronic contract.

[0074] As described above, the electronic signature, etc. may be automatically extracted by the server 10 or automatically transmitted to the server 10 by the client 20, and the server 10 can conclude an electronic contract based on the obtained certificate.

[0075] According to the information processing system 1 in this embodiment, it is possible to make an electronic contract using a digital signature or the like, but the embodiment of the present disclosure does not exclude other methods. For example, the information processing system 1 can receive a contract with a signature other than a digital signature from a requesting user, and prompt the requesting user to sign a signature other than a digital signature to conclude the contract. For example, the requesting client 20 can notify the user to print out the acquired contract, sign it, digitize it, and upload it. Also, only one of the parties can use a digital signature.

[0076] If the contract cannot be concluded (S226: NO), the server 10 notifies the requesting client 20 of that fact and can repeat the process of branch B. When the client 20 receives the notification, it presents that fact to the user (S122). The server 10 and the client 20 can also notify the user that the contract could not be concluded in conjunction with the process of branch B.

[0077] Also, although not shown in the flowchart, if the billing destination client 20 accepts input indicating that the billing will be concluded, but the conclusion cannot be realized using the means selected by the user, the server 10 can notify the user via the billing destination client 20 that the billing method should be reviewed or corrected.

[0078] The server 10 stores the contract for the concluded contract, linking it to both parties. It can also link the items related to the invoice received in S100 to the contract and store them. As a result, from the next time onwards, the user can select the invoice item to the invoice recipient via the client 20 and request invoice, and the server 10 will automatically refer to the contract.

[0079] In addition, the billed user can complete settlement of bills related to the same billing item from the same biller received via client 20 on the cloud service of information processing system 1.

[0080] Furthermore, the user can refer to and receive the contract document stored in the server 10 at any time as necessary.

[0081] As described above, the information processing system 1 makes it possible to realize not only settlement of invoices but also the conclusion of contracts for cloud services.

[0082] The notification to both users can be sent to accounts registered by both users, for example, by email, SNS, SMS, or push notification to the device on which the software is installed.

[0083] When a user who is registered as a qualified invoice issuing business issues a qualified invoice following the above procedure, the other user can properly receive the input tax credit. Qualified invoices issued in the information processing system 1 are properly stored in the server 10. Therefore, transactions related to the qualified invoice can be subject to the input tax credit.

[0084] Furthermore, by issuing the above-mentioned qualified invoice, the user who issues the invoice can avoid being victimized by the other user negotiating a price reduction for the consumption tax.

[0085] As described above, according to this embodiment, the information processing system 1 can properly manage contracts and qualified invoices. As a result, users can carry out proper transactions while eliminating concerns about invoices.

[0086] The above is not particularly limited to the billing method. For example, the server 10 or the client 20 can create a bill for the same amount more quickly based on a fixed amount bill created by the user. The server 10 or the client 20 can also set the number of payments for a bill at the request of the user. The server 10 or the client 20 can also issue a simple bill that does not fall under the category of a qualified bill.

[0087] The user may set a deadline for a claim via the information processing system 1. In this case, the information processing system 1 may notify the billing destination and the biller of a claim that is overdue. Also, a reminder may be automatically sent to the billing destination a predetermined number of days before the billing deadline expires.

[0088] <About payment>

[0089] The information processing system 1 can adopt, as a payment method, a method of using a credit card, a method of transferring or withdrawing funds from a designated bank account, or a method of trading with virtual currency implemented by a blockchain or the like. The information processing system 1 may also have a wallet function. A user indicates his / her intention to make a payment by selecting any method presented by the information processing system 1 via the client 20, and the client 20 can notify the server 10 of the accepted payment method.

[0090] The server 10, which has received the approval of the payment and the notification of the payment method, executes the payment based on the payment method received from the client 20 (S214). If the payment cannot be completed, the server 10 can return the payment to the client 20 for selection of a payment method or approval of the payment. If the payment is returned, the client 20 can notify the user of this and notify the user to select an appropriate payment method again or to approve the payment again.

[0091] When the server 10 is notified by the client 20 that payment is to be made by credit card, the server 10 may inquire with the credit card company and immediately determine whether or not the payment can be made. In this case, if the payment cannot be made, the server 10 may immediately notify the user that the payment could not be made via the client 20. If the credit card of the target user is not registered, the server 10 may prompt the user to notify the credit card information via the client 20.

[0092] When the server 10 is notified by the client 20 of a payment request by depositing money from a bank account, it can inquire about the matter to the bank and determine whether the payment has been completed based on whether the deposit has been made. When the server 10 is notified by the client 20 of a payment by transfer from a bank account, it can notify the user of the transfer destination of the account related to the information processing system 1 and determine whether the transfer has been made at the appropriate time. Also, the server 10 may be configured to accept transfers from a bank account by any means such as Pay-easy (registered trademark).

[0093] This implementation may be implemented using the functionality of a virtual bank, which allows the server 10 to automatically realize processes such as depositing and clearing.

[0094] As another example, the server 10 may have an interface that allows the client 20 to directly transfer funds to the bank account of the biller. In this case, a direct transfer is made from the billing recipient to the biller, and the information processing system 1 may determine that the settlement has been made when a transfer confirmation is notified from the biller or the transfer recipient.

[0095] As another non-limiting example, funds can be deposited by debiting a bank account designated by the user.

[0096] If bank withdrawal is selected and the user's bank account is not registered, the server 10 may request the client 20 to obtain information relating to the user's bank account, and the client 20 may obtain the bank account information from the user by presenting this request to the user.

[0097] Alternatively, payments may be made using any electronic currency, or payments may be made using virtual currency using blockchain.

[0098] Information related to IDs such as credit cards, bank accounts, or electronic currency from billing destinations may be registered in the server 10 at the user's discretion (by opting in or out). In this case, from the next payment opportunity onwards, a quick payment can be achieved by a method linked to the user.

[0099] As another non-limiting example, when funds or equivalent information are transferred to the biller due to settlement from the billing destination, the information processing system 1 can store the user's funds in its own account and present an amount indicating the transfer amount in the user's wallet. In other words, the information processing system 1 may virtually set up a user's account.

[0100] A user can withdraw the amount registered in the wallet to his / her own bank account, etc., at any time. As another example, a user can use the amount registered in the wallet to settle another invoice to which the user is designated as the billing recipient. A user can also charge the wallet at any time. As another example, a shortage of money, etc., may be automatically charged to the wallet from a bank account, credit card, etc. designated by the user, either manually or automatically from a registered account, etc.

[0101] That is, when the invoice is received, the client 20 presents the user with the option of settling the invoice from the wallet, and can execute the settlement based on the wallet balance at the user's request. At this time, it may be possible to select whether to settle the entire invoice amount from the wallet, or to settle only a portion of the invoice amount from the wallet.

[0102] <Presentation of written request documents>

[0103] The information processing system 1 can present documents and information that have been appropriately stored and managed by the above-mentioned processing to a user or the user's representative (a qualified tax accountant, certified public accountant, etc.) at any time.

[0104] By using this system, a user can store and check data related to electronic transactions. The information processing system 1 may also have functions as an analysis tool, an accounting tool, and a tax tool.

[0105] The information processing system 1 can, for example, analyze claims and present various statistics upon request from a user.

[0106] For example, the information processing system 1 can calculate legally required accounting details for a claim upon request from a user and present them to the user.

[0107] The information processing system 1 can, for example, execute tax-related processing for a claim upon request from a user, and present the calculated results to the user.

[0108] If necessary, the information processing system 1 can issue a receipt to both or one of the users. This receipt can also be sent automatically after the settlement is completed. For example, the information processing system 1 can provide a receipt to the user via the billing destination client 20. The information processing system 1 can also provide a copy of the receipt to the user via the billing source client 20.

[0109] <Modification>

[0110] The information processing system 1 can also accept requests based on purchase orders etc., rather than from billing requests. A user may initiate processing of billing and / or contract conclusion based on purchase orders etc., to the information processing system 1 via the client 20.

[0111] In S100, the client 20 can execute a request for an order from an ordering party to the server 10, instead of a request for a bill from a billing party. After that, the flow for concluding a contract is similar.

[0112] The server 10 can realize the above-mentioned processing based on requests and / or processing related to the ordering source and / or the ordering recipient via the client 20. In this case, the user can decide whether to settle the account. For example, if a prepayment fee is included at the time of ordering, an invoice for the prepayment fee can be issued and processing between both parties can be performed according to the contract.

[0113] In addition, upon request from one or both users, the information processing system 1 can also execute a prepayment process. This prepayment process can be realized in any process of the information processing system 1 that is initiated by a purchase order or an invoice.

[0114] As described above, the information processing system 1 can also start processing related to billing and / or settlement by accepting a purchase order instead of an invoice. For example, when a user wants to perform simple processing, a simpler system can be provided that can perform everything from ordering to billing and management by executing processing that starts from this purchase order.

[0115] As described above, according to the present disclosure, it is possible to realize an information processing system 1 that executes processes such as issuing contracts, issuing invoices (including qualified invoices), issuing receipts, customer management, product management, analysis and reporting, document management and presentation, settlement, and wallet functions. By using this information processing system 1, customers can centrally manage necessary information related to electronic settlement, and settlement companies can use a system that automatically supports various functions and a system that realizes easy-to-understand settlement not only for BtoB but also for BtoC.

[0116] The present disclosure can also be in the following form.

[0117] (1) processing circuitry; The processing circuitry includes: Identifying the billing recipient based on a billing request from the billing source; The billing source presents an invoice to the billing destination, including necessary information; When a request for sending the generated invoice is received from the billing source, the billing destination is sent the invoice or a notice is given that the invoice has been issued; storing said invoice in a database; Information processing device.

[0118] (2) The above-mentioned necessary matters are at least: The invoice registration number of the requester, Information indicating the date of the transaction; Transaction items, Transaction amount, and Consumption tax amount, The information processing device according to (1) ,

[0119] (3) The processing circuitry includes: Referencing information on a contract concluded between the requester and the requestee from a database, or referring to information on a contract transmitted from the requester together with the request for the claim; An information processing device according to (1) or (2).

[0120] (4) The processing circuitry includes: If there is no information related to the contract, notify the requester that the contract has not been concluded; An information processing device according to (3).

[0121] (5) The processing circuitry includes: If a contract relating to the claim has not been concluded, notify the claimant that no contract has been concluded; An information processing device according to (3).

[0122] (6) The processing circuitry includes: If no contract has been concluded, the conclusion of the contract relating to said invoice is effected electronically; An information processing device according to (3).

[0123] (7) The processing circuitry includes: When the payment for the invoice is completed, the invoice is associated with the payment and stored in a database. An information processing device according to any one of (1) to (6).

[0124] (8) The processing circuitry includes: Providing the user with information relating to at least one of the settled invoice, the contract relating to the invoice, or the receipt relating to the invoice; An information processing device according to (7).

[0125] (9) processing circuitry; The processing circuitry includes: Identify a supplier based on the request from the customer, The order source presents an invoice to the order recipient, containing necessary information; When a request for sending the generated invoice is received from the order source, the invoice is sent to the order destination, or a notice is given that the invoice has been issued; storing said invoice in a database; Information processing device.

[0126] (10) The processing circuitry includes: Providing a wallet function for carrying out payments; An information processing device according to any one of (1) to (9).

[0127] (11) The information processing device according to any one of (1) to (10), which is a server.

[0128] (12) The processing circuitry Identify the billing recipient based on the billing source's request; The billing source presents an invoice to the billing destination, including necessary information; When a request for sending the generated invoice is received from the billing source, the billing destination is sent the invoice or a notice is given that the invoice has been issued; storing said invoice in a database; Information processing methods.

[0129] (13) The processing circuitry Identify a supplier based on the request from the customer, The order source presents an invoice to the order recipient, containing necessary information; When a request for sending the generated invoice is received from the order source, the invoice is sent to the order destination, or a notice is given that the invoice has been issued; storing said invoice in a database; Information processing methods.

[0130] (14) A processing circuit is caused to execute a method relating to information processing according to any one of (1) to (11). program.

[0131] (15) A client and a server, The client, A billing request including at least a billing destination is transmitted from a billing source to the server; The server, Present an invoice containing necessary information from the billing source to the billing destination via the client; When a request for sending the generated invoice is received from the billing source via the client, the invoice is sent to the billing destination via the client, or a notice that the invoice has been issued is given; storing said invoice in a database; Information processing system.

[0132] (16) In the information processing system according to (15), causing the client to perform an action on the client; program.

[0133] (17) In the information processing system according to (15), causing the server to perform an operation on the server; program.

[0134] In the above, the program may be recorded in a non-transitory computer-readable medium, and the program may be distributed by the computer-readable medium or via a network.

[0135] The aspects of the present disclosure are not limited to the above-described embodiments, but include various conceivable modifications, and the effects of the present disclosure are not limited to the above-described contents. The components in each embodiment may be appropriately combined and applied. In other words, various additions, modifications, and partial deletions are possible within the scope of the conceptual idea and intent of the present disclosure derived from the contents defined in the claims and their equivalents. [Explanation of symbols]

[0136] 1: Information processing system, 10: Server, 20: Client

Claims

1. A processing circuit and a memory circuit are included, The processing circuitry includes: Identifying the billing recipient based on a billing request from the billing source; It is determined whether or not there is a contract relating to the billing concluded between the billing source and the billing destination in the memory circuit, and if there is no such contract, Present to the claimee any outstanding contracts relating to the claim; transitioning to a state in which a request as to whether or not to conclude a contract related to the contract is received from the billing destination; When a request to enter into a contract is received, enter into the contract related to said contract, When the contract is stored in the memory circuit or when a contract related to the contract is concluded, The billing source presents an invoice to the billing destination, including necessary information; transitioning to a state in which a request as to whether or not to approve the settlement related to the invoice is received from the invoice destination; When you receive a request to approve a payment, Execute a payment process for the invoice; storing the invoice in the storage circuit in association with a flag indicating that the payment has been completed; Information processing device.

2. The processing circuit, When a contract related to the contract is concluded, the contract is stored in the memory circuit in association with the fact that the contract is concluded between the billing source and the billing recipient. The information processing device according to claim 1.

3. The contract, A contract uploaded by the billing address, or Contracts prepared with assistance from templates provided; The information processing device according to claim 1 .

4. The processing circuit, When the memory circuit contains a contract between the billing source and the billing destination, transition to a process of presenting the invoice without presenting the contract to the billing recipient and accepting a contract related to the contract; The information processing device according to claim 1.

5. The contract relating to the concluded contract is: An uploaded copy of the contract in force relating to said claim; A contract has previously been concluded via said processing circuit; or any signed contracts uploaded for other claims or previously signed contracts via said processing circuitry for other claims that can be used in connection with said claim; The information processing device according to claim 4 .

6. The processing circuit, When processing a payment, issue a receipt for that payment; The information processing device according to claim 1.

7. The above-mentioned necessary matters are at least: The invoice registration number of the requester, Information indicating the date of the transaction; Transaction items, Transaction amount, and Consumption tax amount, The information processing device according to claim 1 .

8. The processing circuitry includes: the conclusion of the contract relating to said invoice is effected electronically; The information processing device according to claim 1.

9. The processing circuitry includes: Providing a wallet function for carrying out payments; 9. An information processing device according to claim 1.

10. 9. The information processing device according to claim 1, which is a server.

11. The processing circuitry Identifying the billing recipient based on a billing request from the billing source; A determination is made in a memory circuit as to whether or not there is a contract relating to the billing concluded between the billing source and the billing destination, and if there is no such contract, Present to the claimee any outstanding contracts relating to the claim; transitioning to a state in which a request as to whether or not to conclude a contract related to the contract is received from the billing destination; When a request to enter into a contract is received, enter into the contract related to said contract, When the contract is stored in the memory circuit or when a contract related to the contract is concluded, The billing source presents an invoice to the billing destination, including necessary information; transitioning to a state in which a request as to whether or not to approve the settlement related to the invoice is received from the invoice destination; When you receive a request to approve a payment, Execute a payment process for the invoice; storing the invoice in the storage circuit in association with a flag indicating that the payment has been completed; storing said invoice in a database; Information processing methods.

12. A system including a plurality of clients and a server, A first client related to the billing source among the plurality of clients, sending a billing request including at least a billing destination from the billing source to the server; The server, determining whether or not a contract relating to the billing that has been concluded between the billing source and the billing destination is stored in a memory circuit; If the contract is not stored in the memory circuit, The server presents an unsigned contract related to the billing to the billing destination via a second client related to the billing destination among the multiple clients, The second client transitions to a state in which it receives a request as to whether or not to conclude a contract related to the contract; When the server receives a request to conclude a contract via the second client, the server concludes a contract related to the contract; When the contract is stored in the memory circuit or when a contract related to the contract is concluded, The server presents an invoice containing necessary information from the billing source to the billing destination via the second client; The second client transitions to a state in which it receives a request as to whether or not to approve the settlement related to the invoice; When the server receives a request to approve the payment via the second client, Execute a payment process for the invoice; storing the invoice in the storage circuit in association with a flag indicating that the payment has been completed; Information processing system.

13. 13. The information processing system according to claim 12, causing the client to perform an action on the client; program.

14. 13. The information processing system according to claim 12, causing the server to perform an operation on the server; program.

Images