JP7330937B2 - Program, information processing device and method - Google Patents

Description

The present disclosure relates to programs, information processing apparatuses, and methods.

When conducting transactions between companies and sole proprietors, send documents such as quotations, purchase orders, and invoices that indicate the content and amount of products and outsourcing related to the transaction to the other party, and indicate the details of the transaction in the document. is being done. Such documents are prepared to ensure that there are no discrepancies in terms of transaction details and amounts, and are exchanged between the orderer and the contractor. However, it takes time and effort to create such a document.

Various techniques are provided to reduce the trouble of creating such documents. In Patent Document 1, in order to efficiently manage the status of predetermined events related to payment operations without omission between parties, it is managed by a distributed ledger using blockchain, and the contents of billing registration, pending payments, payment procedures, etc. I am getting the details of the payment.

JP 2020-091695 A

By the way, when a company and a sole proprietor (so-called freelancer) place an order, especially in the case where the company is the ordering party and the sole proprietor is the contractor, the process itself of the sole proprietor issuing an invoice is a burden. It has become. In addition, there is a demand from the ordering party (company) to control the timing of payment and details of payment without waiting for the arrival of the invoice from the sole proprietor (which is not known when it will come and requires a reminder). The prior art has not been able to sufficiently meet such demands.

Therefore, this disclosure describes a technology that enables the orderer to control the timing and content of payment by reducing the process of issuing an invoice on the orderer side when making a payment for a transaction. .

According to one embodiment of the present disclosure, a program is provided that is executed by a computer that includes a processor and a memory and manages transactions between multiple businesses. Status information relating to transactions is registered in the memory, and the status information includes a transaction start state indicating that the transaction has started, a billing state indicating that the transaction has been billed, and a payment notification regarding the transaction. Status information is registered, including a payment notification status indicating that the The program causes the processor to accept registration of status information for transactions from business operators, and when the status information is a transaction start status, the status information from one of the plurality of business operators is billing status or status information. A step of receiving registration of payment notification status, and a step of transmitting payment notification to another business operator when registration of payment notification status is received as status information are executed.

According to an embodiment of the present disclosure, an information processing device is provided that includes a control unit and a storage unit, and manages transactions between a plurality of business operators. Status information relating to transactions is registered in the storage unit, and the status information includes a transaction start state indicating that the transaction has started, a billing state indicating that the transaction has been billed, and a payment notification regarding the transaction. Status information is registered, including a payment advice status indicating that the payment has been made. The control unit accepts registration of status information for a transaction from a business operator, and when the status information is a transaction start state, a billing state or a payment notification is received from one of the plurality of business operators as the status information. A step of receiving the registration of the status, and a step of transmitting the payment notification to another business operator when the registration of the payment notification status as the status information is received.

Also according to one embodiment of the present disclosure, there is provided a method executed by a computer comprising a processor and a memory for managing transactions conducted between multiple entities. Status information relating to transactions is registered in the memory, and the status information includes a transaction start state indicating that the transaction has started, a billing state indicating that the transaction has been billed, and a payment notification regarding the transaction. Status information is registered, including a payment notification status indicating that the The method is such that the processor receives registration of status information for a transaction from a business operator, and when the status information is a transaction start state, the status information is a billing state or a status information from one business operator out of the plurality of business operators. A step of accepting registration of payment advice status, and a step of transmitting a payment advice to another business operator when registration of payment advice status is accepted as status information are performed.

According to this disclosure, in the transaction start state (settlement possible), registration of billing status or payment notification status is accepted as status information, and if registration of payment notification status is accepted, other business operators send a payment notice to As a result, it becomes possible to reduce the process of issuing invoices on the orderer side and to control the timing and content of payment on the orderer side when settling transactions.

1 is a diagram showing the overall configuration of a transaction management system 1; FIG. 2 is a block diagram showing a functional configuration of terminal device 10 constituting transaction management system 1 of Embodiment 1. FIG. 2 is a diagram showing a functional configuration of server 20 configuring transaction management system 1 of Embodiment 1. FIG. 4 is a sequence diagram showing an example of transaction status information and sub-status information by the transaction management system 1 of Embodiment 1. FIG. It is a figure which shows the example of the data structure of the transaction database 2021 which the server 20 memorize|stores, and the user database 2022. 4 is a flow chart showing an example of a flow of transaction information registration processing by the transaction management system 1 of Embodiment 1. FIG. 4 is a flow chart showing an example of a flow of status information registration processing by the transaction management system 1 of Embodiment 1. FIG. 6 is a diagram showing an example of a screen displaying transaction information displayed on the terminal device 10. FIG. 6 is a diagram showing an example of a screen displaying transaction information displayed on the terminal device 10. FIG. 4 is a diagram showing an example of a screen for inputting transaction information displayed on the terminal device 10. FIG. 4 is a diagram showing an example of a screen displaying a transaction list displayed on the terminal device 10. FIG. FIG. 10 is a diagram showing a functional configuration of server 20 that configures transaction management system 1 of Embodiment 2; 6 is a diagram showing an example of a screen displaying transaction information displayed on the terminal device 10. FIG. 6 is a diagram showing an example of a screen displaying transaction information displayed on the terminal device 10. FIG.

Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In the following description, the same parts are given the same reference numerals. Their names and functions are also the same. Therefore, detailed description thereof will not be repeated.

<Overview>
A transaction management system according to the present disclosure will be described below. This transaction management system is a system for managing transactions between users who are businesses. In general, when placing an order, receiving an order, or purchasing a product or service between companies and sole proprietors, the processes of quotation, ordering, receiving an order, delivery, billing, and payment are often followed. . For example, when placing an order or receiving an order between companies to provide a certain service, the ordering company asks the receiving company to submit a quotation (estimation process), and the amount stated in the quotation, etc. If an agreement is reached on the terms of the above, submit a purchase order (ordering/ordering process), the receiving company provides the service (delivery process), and the receiving company receives an invoice for payment of the service. is submitted (billing process), and the amount stated on the invoice is actually paid (payment process). The transaction management system according to the present disclosure manages information on the state of processes such as quotations, orders, orders, delivery, billing, and payments as status information, and these status information are created, waiting, confirming, approved and other status information is managed as sub-status information. Here, the business operator is a concept that includes not only corporations such as companies but also sole proprietors. Note that the transaction management system according to the present disclosure is not limited to the function of managing transactions as described above, and may be a system that provides overall accounting processing services related to companies and individual businesses that are users. For example, the input transaction information may be used as deposit/withdrawal information, the input of financial information such as owned assets may be accepted, and accounting processing services for the user's company or individual business may be provided.

In addition, the transaction management system according to the present disclosure is a system provided by a so-called SaaS (Software as a Service) as a Web service, for example, by a cloud server or the like, and is configured to be accessible by a user who is a business operator by predetermined authentication. It is This transaction management system enables registration of transaction information and transaction status information regardless of whether it is the ordering side or the receiving side. A system that allows status information to be accessed and updated.

Transactions such as those described above take place not only between companies, but also between companies and sole proprietors (so-called freelancers). For example, it is often done when requesting writing of a predetermined article to be published on a website, or when requesting research, document preparation, auditing, etc. in a predetermined specialized field. When a company places an order for a given work to a sole proprietor, the process itself, in which the sole proprietor, who receives the order, issues an invoice, becomes a burden for the sole proprietor as described above. There are many things. As a result, a period of time has elapsed after a sole proprietor has delivered a given work, and in many cases, the orderer side issues an invoice at the request of the orderer.

In addition, the company on the ordering side needs to wait for the invoice from the sole proprietor on the receiving side to process the actual payment. There is a desire to control the timing of payment and details of payment without waiting for the arrival of the bill. This is because waiting for the arrival of invoices requiring reminders, which do not know when they will come, incurs management costs.

Therefore, the transaction management system according to the present disclosure makes it possible to transmit a payment notification for a transaction for which an order has been placed, for example, after delivery, at a timing at which it is possible to proceed to the billing process described above. In the payment notice, information such as payee information, means of payment, payment due date, etc. is notified. This will reduce the burden of issuing invoices on sole proprietors who receive orders, while allowing companies on the ordering side to control the timing and content of payments without waiting for the arrival of invoices. ing.

<First Embodiment>
The transaction management system 1 will be described below. In the following description, for example, when the terminal device 10 accesses the server 20 , the server 20 responds with information for generating a screen on the terminal device 10 . The terminal device 10 generates and displays a screen based on information received from the server 20 .

<1 Overall Configuration of Transaction Management System 1>
FIG. 1 is a diagram showing the overall configuration of a transaction management system 1. As shown in FIG. As shown in FIG. 1, a transaction management system 1 includes a plurality of terminal devices (terminal device 10A and terminal device 10B are shown in FIG. 1; hereinafter collectively referred to as "terminal device 10"). , and the server 20 . The terminal device 10 and the server 20 are connected via a network 80 so as to be able to communicate with each other. Network 80 is configured by a wired or wireless network.

The terminal device 10 is a device operated by each user. Here, a user is a person who uses the terminal device 10 to register and update transaction information and transaction status information, which are functions of the transaction management system 1. Business owner, etc. The terminal device 10 is implemented by a stationary PC (Personal Computer), a laptop PC, or the like. In addition, the terminal device 10 may be, for example, a mobile terminal such as a tablet compatible with a mobile communication system or a smart phone.

The terminal device 10 is communicably connected to the server 20 via the network 80 . The terminal device 10 is a wireless base station 81 compatible with communication standards such as 4G, 5G, and LTE (Long Term Evolution), and a wireless LAN (Local Area Network) standard such as IEEE (Institute of Electrical and Electronics Engineers) 802.11. It is connected to the network 80 by communicating with a compatible communication device such as a wireless LAN router 82 . As shown as terminal device 10B in FIG.

The communication IF 12 is an interface for inputting and outputting signals so that the terminal device 10 communicates with an external device. The input device 13 is an input device (for example, a keyboard, a touch panel, a touch pad, a pointing device such as a mouse, etc.) for receiving an input operation from a user. The output device 14 is an output device (display, speaker, etc.) for presenting information to the user. The memory 15 temporarily stores programs and data processed by the programs, and is a volatile memory such as a DRAM (Dynamic Random Access Memory). The storage unit 16 is a storage device for storing data, and is, for example, a flash memory or a HDD (Hard Disc Drive). The processor 19 is hardware for executing an instruction set described in a program, and is composed of arithmetic units, registers, peripheral circuits, and the like.

The server 20 is a device that manages transaction information, transaction status information, and user information. The server 20 receives registration of transaction information from a user who is a business operator, receives an invitation from a trading partner, notifies the partner, and receives access from the user who is the partner. When the server 20 receives transaction status information from the user (business operator and transaction partner) and receives payment notification as the status information, the server 20 notifies the transaction partner. Furthermore, the server 20 performs payment processing based on the payment notification.

Server 20 is a computer connected to network 80 . The server 20 includes a communication IF 22 , an input/output IF 23 , a memory 25 , a storage 26 and a processor 29 .

The communication IF 22 is an interface for inputting and outputting signals for the server 20 to communicate with an external device. The input/output IF 23 functions as an interface with an input device for receiving input operations from the user and an output device for presenting information to the user. The memory 25 temporarily stores programs and data processed by the programs, and is a volatile memory such as a DRAM (Dynamic Random Access Memory). The storage 26 is a storage device for storing data, such as a flash memory or HDD (Hard Disc Drive). The processor 29 is hardware for executing an instruction set described in a program, and is composed of arithmetic units, registers, peripheral circuits, and the like.

<1.1 Configuration of terminal device 10>
FIG. 2 is a block diagram showing the functional configuration of the terminal device 10 that constitutes the transaction management system 1 of Embodiment 1. As shown in FIG. As shown in FIG. 2, the terminal device 10 includes a plurality of antennas (antenna 111, antenna 112), wireless communication units (first wireless communication unit 121, second wireless communication unit 122) corresponding to each antenna, and an operation unit. It includes reception unit 130 (including keyboard 131 and display 132 ), audio processing unit 140 , microphone 141 , speaker 142 , camera 150 , storage unit 160 , and control unit 170 . The terminal device 10 also has functions and configurations not particularly shown in FIG. 2 (for example, a battery for retaining power, a power supply circuit for controlling power supply from the battery to each circuit, etc.). As shown in FIG. 2, each block included in the terminal device 10 is electrically connected by a bus or the like.

The antenna 111 radiates a signal emitted by the terminal device 10 as radio waves. Antenna 111 also receives radio waves from space and provides a received signal to first wireless communication section 121 .

The antenna 112 radiates a signal emitted by the terminal device 10 as radio waves. Antenna 112 also receives radio waves from space and provides a received signal to second wireless communication section 122 .

The first wireless communication unit 121 performs modulation/demodulation processing and the like for transmitting and receiving signals via the antenna 111 in order for the terminal device 10 to communicate with other wireless devices. The second wireless communication unit 122 performs modulation/demodulation processing and the like for transmitting and receiving signals via the antenna 112 so that the terminal device 10 communicates with other wireless devices. The first radio communication unit 121 and the second radio communication unit 122 are communication modules including a tuner, an RSSI (Received Signal Strength Indicator) calculation circuit, a CRC (Cyclic Redundancy Check) calculation circuit, a high frequency circuit, and the like. The first radio communication unit 121 and the second radio communication unit 122 perform modulation/demodulation and frequency conversion of radio signals transmitted/received by the terminal device 10 and give received signals to the control unit 170 .

The operation accepting unit 130 has a mechanism for accepting user input operations. Specifically, operation accepting unit 130 includes a keyboard 131 and a display 132 . Note that the operation reception unit 130 may be configured as a touch screen that detects the user's touch position on the touch panel, for example, by using a capacitive touch panel.

The keyboard 131 accepts input operations by the user of the terminal device 10 . The keyboard 131 is a device for inputting characters, and outputs input character information to the control unit 170 as an input signal.

The display 132 displays data such as images, moving images, and text under the control of the control unit 170 . The display 132 is implemented by, for example, an LCD (Liquid Crystal Display) or an organic EL (Electro-Luminescence) display.

The audio processing unit 140 modulates and demodulates an audio signal. Audio processing section 140 modulates the signal supplied from microphone 141 and supplies the modulated signal to control section 170 . Also, the audio processing unit 140 provides an audio signal to the speaker 142 . The audio processing unit 140 is implemented by, for example, a processor for audio processing. Microphone 141 receives a voice input and provides voice signal corresponding to the voice input to voice processing section 140 . The speaker 142 converts the audio signal provided from the audio processing unit 140 into audio and outputs the audio to the outside of the terminal device 10 .

The camera 150 is a device for receiving light with a light receiving element and outputting it as a photographed image. The camera 150 is, for example, a depth camera that can detect the distance from the camera 150 to the subject.

The storage unit 160 is configured by, for example, a flash memory or the like, and stores data and programs used by the terminal device 10 . In one aspect, storage unit 160 stores user information 161 .

The user information 161 is information of a user who uses the terminal device 10 to register and update transaction status information, which is a function of the transaction management system 1 . The user information includes information for identifying the user (user ID), the name of the user, organizational information such as the company to which the user belongs, and the like.

The control unit 170 reads a program stored in the storage unit 160 and executes instructions included in the program to control the operation of the terminal device 10 . The control unit 170 is, for example, an application installed in the terminal device 10 in advance. The control unit 170 functions as an input operation reception unit 171, a transmission/reception unit 172, a data processing unit 173, and a notification control unit 174 by operating according to a program.

The input operation reception unit 171 performs processing for receiving a user's input operation to the input device such as the keyboard 131 .

The transmission/reception unit 172 performs processing for the terminal device 10 to transmit/receive data to/from an external device such as the server 20 according to a communication protocol.

The data processing unit 173 performs processing according to a program to perform computation on data input by the terminal device 10, and outputs the computation result to a memory or the like.

The notification control unit 174 performs processing for presenting information to the user. The notification control unit 174 performs processing for displaying a display image on the display 132, processing for outputting sound to the speaker 142, processing for causing the camera 150 to vibrate, and the like.

<1.2 Functional Configuration of Server 20>
FIG. 3 is a diagram showing a functional configuration of server 20 that constitutes transaction management system 1 of Embodiment 1. As shown in FIG. As shown in FIG. 3 , the server 20 functions as a communication section 201 , a storage section 202 and a control section 203 .

The communication unit 201 performs processing for the server 20 to communicate with an external device.

The storage unit 202 stores data and programs used by the server 20 . The storage unit 202 stores a transaction database 2021, a user database 2022, and the like.

The transaction database 2021 is a database for holding various information related to transactions managed by the transaction management system 1 . Details will be described later.

The user database 2022 is a database for holding various information of users who register and update transaction information and transaction status information in the transaction management system 1 . Details will be described later.

By the processor of the server 20 performing processing according to the program, the control unit 203 includes various modules such as a reception control module 2031, a transmission control module 2032, a transaction information registration reception module 2033, an invitation notification module 2034, a status information registration reception module 2035, The functions shown in the payment notification module 2036 and the payment processing module 2037 are exhibited.

The reception control module 2031 controls processing for the server 20 to receive a signal from an external device according to a communication protocol.

The transmission control module 2032 controls the processing by which the server 20 transmits signals to external devices according to a communication protocol.

The transaction information registration acceptance module 2033 controls the process of accepting registration of information on transactions managed by the transaction management system 1 from business operators who are users of the transaction management system 1 . The information on the transaction received by the transaction information registration reception module 2033 is, for example, information on the parties involved in the transaction, such as the orderer, the contractor, the purchaser, etc., the information on the project, the delivery date, the amount, etc. If the deliverables and deliverables can be managed as electronic information such as reports and design documents, deliverables and deliverables may be included. A business operator who registers transaction information in the transaction information registration reception module 2033 may be an entity related to the transaction, such as an orderer, a contractor, a purchaser, etc., and may be a corporation or an individual. If it is not registered, registration is performed in advance, an ID and password are issued, and predetermined authentication is performed.

The information about the subject related to the transaction received by the transaction information registration reception module 2033 includes information such as company name or personal name, trade name, contact information (telephone number, e-mail address, user registered in the transaction management system 1 account information, etc.). In addition, the business operator who is the entity related to the transaction may be any person related to the transaction such as the ordering party, the contractor, the purchaser, etc. Specifically, two or more business operators There may be three or more companies (three companies) or more, including those who pay the expenses for the transaction, those who receive the payments, but may also include those who are not related to the payment of expenses ( mere advisor, auditor, etc.). The information about the project is the name of the project, such as "Construction of Website for Company ◇△".

The invitation notification module 2034 uses the information on the subject related to the transaction in the transaction information received by the transaction information registration reception module 2033 as the user who uses the transaction management system 1 to identify other businesses as the business partner related to the transaction. controls the process of inviting people as users. The invitation notification module 2034 notifies the contact of the information regarding the subject related to the transaction among the transaction information received by the transaction information registration reception module 2033 that the person is registered as the target of the transaction, and sends the notification to the transaction management system. Invite access to 1. At this time, if the business operator to be notified is not registered as a user of the transaction management system 1, it is registered with the transaction management system 1, a user ID and password are issued, and predetermined authentication is performed. A business operator invited by the invitation notification module 2034 can register new information and update the transaction information received by the transaction information registration reception module 2033, but a predetermined restriction may be set.

The status information registration reception module 2035 receives status information input from the business operator whose transaction information has been received by the transaction information registration reception module 2033 or from the business operator whose invitation has been notified by the invitation notification module 2034, and adds the status information to the transaction information. controls the process of registering settings and registering status information updates. Here, the status information is information indicating the status of the transaction process, and includes, but is not limited to, quotation, order placement, order receipt, delivery, billing (billing status), and payment, as described above. For example, the status information of quotation, order placement, and order receipt may be managed as a transaction start (transaction start state) indicating that the transaction has been started, and the billing and payment status information may be managed as a request related to the transaction. It may be managed as a claim (billing status) indicating that the Also, the status information registration reception module 2035 may receive and register cancellation and change of status information. The status information may be information registered as the state of the entire transaction process, or may be information registered for each business operator. For example, if the status information of the order-placing business operator is "Ordering", the status information of the order-receiving business operator is "Order received".

Furthermore, the status information registration reception module 2035 registers, as status information from the business operator, a payment notification (payment notification status) indicating that a payment notification for the transaction will be made. Payment notification status information is status information that can be selected to be registered instead of billing status information. This is status information that a certain business operator notifies the business operator, who is mainly the contractor, of information such as payment destination information, payment method, and payment date without waiting for the arrival of the invoice (billing data). . Therefore, the status information registration reception module 2035 manages so as to select either billing status information or payment notification status information, and changes status information from billing to payment notification registration or status information to payment notification. Control to prevent registration from transitioning to billing.

In addition, the status information registration reception module 2035 may control to automatically shift to billing status information when registration of payment notification status information is not received from the business operator within a predetermined period. The predetermined period may be a specific period such as one month or less. A predetermined action may occur. Furthermore, the status information registration acceptance module 2035 may accept cancellation or change registration of the payment notice status information from the business operator within a predetermined period after the payment notice status information is registered.

In addition, the status information registration reception module 2035 registers the setting of the sub-status information linked to the above status information, and registers the update of the sub-status information. Sub-status information is information indicating the work status in each transaction process status, and includes, for example, creating, waiting, confirming (approval waiting status), and approved (approved status) as described above. , but not limited to this. A detailed example of migration of status information and sub-status information will be described later.

The payment notification module 2036 controls the process of transmitting the payment notification to the target business operator when the status information registration reception module 2035 receives the registration of the payment notification status information from the business operator. Payment notice means that the business operator, who is the main orderer of the transaction, notifies the business operator, who is the main contractor, of information, payment method, payment date, etc. This payment notice may be sent to only some of the merchants involved in the transaction.

The payment notification module 2036, for example, transmits the information on the payee and the information on the means of payment as a notice of payment based on the information on the payee and the information on the means of payment registered in the user database 2022 as the user information about the business operator of the payee. Alternatively, if the user is not registered, the user may be prompted to register. In addition, in the payment notice, information on the payee and information on the means of payment may be notified to the business operator of the payment source. Furthermore, it may be configured such that a payment notice cannot be sent to a business operator whose information on the payee and the information on the means of payment are not registered in the user database 2022 . Furthermore, if the business to which the payment is to be made is registered in the user database 2022 so as to send a payment notice, the status information registration reception module 2035 automatically shifts to the payment notice status and sends the payment notice. It may be configured as

The payment processing module 2037 controls processing for performing payment processing based on information on the payee, payment means, and payment due date included in the payment notice notified by the payment notice module 2036 . The payment processing module 2037, for example, generates accounting information (journal information, settlement information, etc.) that can be processed by the accounting system or the settlement system from the payee information, payment method, and payment date, and performs payment processing. The payment processing module 2037 may perform payment processing related to the payment notification using the accounting processing service provided by the transaction management system 1 as described above, or may perform payment processing by transmitting to an external payment system or the like. good.

<1.3 Specific examples of transaction status information and sub-status information>
FIG. 4 is a sequence diagram showing an example of transaction status information and sub-status information by the transaction management system 1 of the first embodiment. The sequence diagram shown in FIG. 4 is a diagram showing transition of status information and sub-status information for a transaction between an orderer who is one business operator and a contractor who is one business operator. Hereinafter, transition of status information and sub-status information will be described with reference to FIG. "Quotation", "Order", "Invoicing", and "Payment Notice" indicated by the thick dashed frame in FIG. , 'Waiting', and 'Approved' indicate sub-status information.

First, a business operator who is an orderer or a contractor registers transaction information. It also invites a business partner to do business with, allowing this business to access transaction information. At this time, the orderer or contractor is not limited to one company, that is, three or more companies can access the transaction data as the orderer or contractor.

At this time, as shown in FIG. 4, the registered transaction information process becomes the estimate process, and the status information becomes "estimate". The sub-status information of the business operator who is the contractor becomes "creating" in step S001, and the sub-status information of the business operator who is the orderer becomes "waiting" in step S002. When the contractor prepares an estimate and sends it to the orderer, the orderer's sub-status information becomes "confirming" in step S003, and the contractor's sub-status information becomes "waiting for confirmation" in step S004. When the orderer approves the content of the estimate, the contractor's sub-status information becomes "estimated" in step S005.

Then the transaction information process becomes the order process and the status information becomes "order placed". The orderer's sub-status information becomes "creating" in step S006. When the orderer creates an order and sends it to the contractor, the contractor's sub-status information becomes "confirming" in step S007, and the orderer's sub-status information becomes "waiting for confirmation" in step S008. When the contractor approves the contents of the order, the contractor's sub-status information becomes "approved" in step S009, and the orderer's sub-status information becomes "approved" in step S010. After that, the delivery of the actual product related to the transaction and the work related to the outsourcing are performed.

When the actual delivery of the goods related to the transaction and the work related to the outsourcing are completed, the transaction information process will be the billing process or the payment notification process depending on the orderer's choice, and the status information will be "billing" or "payment notification". . When the orderer registers billing status information in the status information registration reception module 2035, the status information becomes "billing". The sub-status information of the contractor becomes "creating" in step S011, and the sub-status information of the orderer becomes "waiting" in step S012. When the contractor creates a bill and sends it to the orderer, the orderer's sub-status information becomes "confirming" in step S013, and the contractor's sub-status information becomes "waiting for confirmation" in step S014. When the orderer approves the billing details, the contractor's sub-status information becomes "approved" in step S015, and the orderer's sub-status information becomes "approved" in step S016. After this, the actual payment is made and the transaction is completed.

When the orderer registers payment notice instead of billing status information in the status information registration reception module 2035, the status information becomes "payment notice". The orderer's sub-status information becomes "payment notice" in step S021. After this, the actual payment is made and the transaction is completed. In the transaction management system 1, the status information and sub-status information as described above are updated to manage the transaction status. Note that the above status information and sub-status information are examples, and the present invention is not limited to this.

<2 Data structure>
FIG. 5 is a diagram showing an example of the data structure of the transaction database 2021 and user database 2022 stored by the server 20. As shown in FIG.

As shown in FIG. 5, each record in the transaction database 2021 includes an item "transaction ID", an item "project name", an item "orderer/contractor", an item "transaction history information", and the like.

The item “transaction ID” is information for identifying each piece of transaction information to be managed by the transaction management system 1 .

The item "project name" is a name indicating a transaction project to be managed by the transaction management system 1, for example, "○△ article writing", "◇△ company (web) site construction". name is stored.

The item "orderer/contractor" is information for identifying each subject related to a transaction, which is managed by the transaction management system 1. For example, it is registered as information for identifying each of the orderer and the contractor. Identifier information is stored.

The item "transaction history information" is history information of information indicating the state of the transaction process, which is managed by the transaction management system 1. Specifically, the item "transaction history ID" and the item " date”, item “status”, item “sub-status”, and the like. This item "transaction history information" is, for example, transition history information of the item "status" and the item "sub-status", the item "transaction history ID" is numbered in chronological order, and the latest information is added as a record. configured to be

The item "transaction history ID" is information that identifies each piece of information indicating the status of the transaction process. is configured so that

The item "date" is information on the date when the status of the transaction process was updated.

The item "status" is status information indicating the state of the transaction process, and stores, for example, "quotation", "order placement", "billing", or "payment notice" as described above.

The item "sub-status" is sub-status information indicating the work status in each status of the transaction process. It is

Although illustration is omitted, in the transaction database 2021, if the deliverables and deliverables of transactions managed by the transaction management system 1 can be managed as electronic information such as reports and design documents, , deliverables and deliverables may be stored.

The transaction information registration reception module 2033 of the server 20 updates the transaction database 2021 upon reception of the registration of the information on the transaction. In addition, the status information registration reception module 2035 receives registration of update of status information indicating the state of the transaction process or sub-status information indicating the work status in each state of the transaction process. Add a record to the item "Transaction history information".

Each record of the user database 2022 includes an item “user ID”, an item “user detailed information”, and the like.

The item "user ID" is information that identifies each entity related to a transaction, which is a management target managed by the transaction management system 1. For example, it is registered as information that identifies each business operator (orderer, contractor). This is the identification information that is provided. It corresponds to the item “orderer/contractor” of transaction database 2021 .

The item "user detailed information" is information related to a transaction-related user that is managed by the transaction management system 1. Specifically, the item "enterprise name" and the item "corporation/individual". , the item “contact”, the item “payment method”, the item “payment notice”, and the like.

The item "company name" is information indicating the company name or individual name of the company (orderer, contractor) involved in the transaction.

The item “corporation/individual” is information indicating whether a business operator (orderer, contractor) related to the transaction is a corporation or an individual.

The item "contact information" is information indicating the contact information of a business operator (orderer, contractor) related to the transaction, and stores, for example, a telephone number, an e-mail address, and the like.

The item "payment method" is information registered as payment method information for business operators (orderers, contractors) involved in the transaction. "Payment" is stored if it is acceptable. In addition, transfer destination account information at the time of payment is also stored.

The item "payment notice" is information indicating whether or not payment notices have been received in the past from business operators (orderers, contractors) involved in the transaction. "None" is stored.

Although illustration is omitted, the user database 2022 may store information to be registered as a person receiving a payment notice for a business operator (orderer, contractor) related to the transaction.

The transaction information registration reception module 2033 of the server 20 adds a record to the user database 2022 along with prompting the person to register the transaction information if the person is not registered. The invitation notification module 2034 adds a record to the user database 2022 along with prompting registration when inviting another business operator as a user as a trading partner for a transaction if the business operator is not registered.

<3 Operation>
Transaction information registration processing and status information registration processing by the transaction management system 1 according to the first embodiment will be described below with reference to FIGS. 6 and 7. FIG.

FIG. 6 is a flow chart showing an example of the flow of transaction information registration processing by the transaction management system 1 of the first embodiment.

In step S111, the input operation reception unit 171 of the terminal device 10A receives a user ID and password for performing authentication necessary for using the service of the transaction management system 1 from the business operator who is the user who registers the transaction information. accepts the operation of inputting The transmission/reception unit 172 transmits the received user ID and password and user information to the server 20 . The transmitting/receiving unit 172 of the terminal device 10A receives the authentication completion information transmitted from the server 20 . The notification control unit 174 causes the display 132 to display the received authentication completion information.

In step S<b>121 , server 20 receives the user ID and password via communication unit 201 . The server 20 confirms that the received user ID and password of the user are correct, and performs predetermined authentication. If it is valid, the server 20 transmits information of completion of authentication to the terminal device 10A via the communication unit 201 .

In step S112, the input operation accepting unit 171 of the terminal device 10A accepts an input for registering transaction information, which is a management target of the transaction management system 1, from the user. The information received as transaction information is, for example, information on the matter, delivery date, amount of money, and the like. The transmitting/receiving unit 172 transmits the received transaction information to the server 20 .

In step S<b>122 , the transaction information registration reception module 2033 of the server 20 receives the transaction information transmitted from the terminal device 10</b>A via the communication unit 201 . The transaction information registration reception module 2033 registers the received transaction information in the transaction database 2021 .

In step S113, the input operation accepting unit 171 of the terminal device 10A accepts an input for registering the information of the trading partner from the user. The information received as the information on the transaction partner is, for example, the information on the entity related to the transaction, such as the orderer, the contractor, the purchaser, and the like. The transmitting/receiving unit 172 transmits the received transaction information to the server 20 .

In step S123, the transaction information registration reception module 2033 of the server 20 receives, via the communication unit 201, the information of the trading partner transmitted from the terminal device 10A. The transaction information registration acceptance module 2033 registers the accepted transaction counterparty information in the transaction database 2021 .

In step S124, the invitation notification module 2034 of the server 20 invites the business operator as a user as a trading partner for the transaction based on the trading partner information received in step S123. If the business operator to be notified is not registered as a user of the transaction management system 1, it is registered with the transaction management system 1 and a user ID and password are issued. The invitation notification module 2034 transmits the information of the invitation as a trading partner, and the user ID and password when the registration to the transaction management system 1 is performed, to the terminal device 10B that transmits the invitation via the communication unit 201. . The access information transmitted from the terminal device 10B is received via the communication unit 201, and the authentication completion information is transmitted.

In step S<b>134 , the transmitting/receiving unit 172 of the terminal device 10</b>B receives the invitation information, the user ID, and the password as the business partner transmitted from the server 20 . The notification control unit 174 causes the display 132 to display the received invitation information. The input operation accepting unit 171 accepts an input operation for accessing the server 20 from a user who is an invited business operator. The transmitter/receiver 172 transmits the received access information to the server 20 .

In step S<b>125 , the transaction information registration reception module 2033 of the server 20 registers the information of the business operator invited in step S<b>124 in the transaction database 2021 and user database 2022 .

As described above, the user of the transaction management system 1 receives registration of transaction information from a business operator related to a transaction, and receives registration of information of a business partner related to the transaction. An invitation as a business partner is transmitted to the accepted business partner, and if the business partner is not registered as a user, user registration is performed. This enables mutual registration of transaction information and update information of status information set in the transaction information.

FIG. 7 is a flow chart showing an example of the flow of status information registration processing by the transaction management system 1 of the first embodiment.

In step S211, the input operation reception unit 171 of the terminal device 10A registers the setting of the status information and sub-status information in the transaction information from the user who registered the transaction information, and registers the update of the status information and sub-status information. accepts input to The transmitting/receiving unit 172 transmits the registration information of the received status information to the server 20 .

In step S231, the input operation receiving unit 171 of the terminal device 10B receives an input from the invited user to register the settings of the status information and sub-status information in the transaction information and to register the update of the status information and sub-status information. . The transmitting/receiving unit 172 transmits the registration information of the received status information to the server 20 .

In step S221, the status information registration reception module 2035 of the server 20 registers the settings of the status information and sub-status information transmitted from the terminal device 10A or 10B, and registers the update of the status information and sub-status information. Information is received via the communication unit 201 . The status information registration reception module 2035 registers the received status information and sub-status information in the transaction database 2021 .

In step S212, when the delivery of the actual product related to the transaction and the work related to the outsourcing are completed, the input operation reception unit 171 of the terminal device 10A receives the request status as status information from the user who registered the transaction information. Accepts an input to register a payment notice indicating that a payment notice for the transaction will be made instead of the information. The transmitting/receiving unit 172 transmits the received payment notification status information to the server 20 . Note that this operation may be performed by the invited user on the terminal device 10B.

In step S222, the status information registration reception module 2035 of the server 20 receives, via the communication unit 201, the information for registering the payment notification status information transmitted from the terminal device 10A. The status information registration reception module 2035 registers the received payment notification status information in the transaction database 2021 .

In step S223, the payment notification module 2036 of the server 20 transmits a payment notification to the target business operator via the communication unit 201 for the transaction of the payment notification status information received in step S222.

In step S<b>233 , the transmission/reception unit 172 of the terminal device 10</b>B receives the payment notice transmitted from the server 20 . The notification control unit 174 causes the display 132 to display the received payment notification. Note that this notification may be sent to the terminal device 10A to the user who registered the transaction information.

In step S224, the payment processing module 2037 of the server 20 performs payment processing based on the payee information, payment method, and payment date included in the payment notice transmitted in step S223.

In step S225, the payment processing module 2037 of the server 20 registers in the transaction database 2021 the result of the payment processing performed in step S224.

As described above, the transaction management system 1 mutually accepts and registers the update information of the status information set in the transaction information from the orderer and the contractor. When the actual delivery of the product related to the transaction or the work related to the outsourcing is completed, instead of the billing status information, the payment notification status information indicating that the payment notification related to the transaction will be made is accepted from the orderer. A payment notice is sent to the contractor, and payment processing is performed based on the information contained in the payment notice. This reduces the burden of issuing invoices on the contractor, and allows the ordering party to control the timing of payment and details of payment without waiting for the arrival of the invoice.

<4 Screen example>
An example of a screen for display processing of transaction information and a transaction list by the transaction management system 1 will be described below with reference to FIGS. 8 to 10. FIG.

FIG. 8 is a diagram showing an example of a screen displaying transaction information displayed on the terminal device 10. As shown in FIG. The screen example of FIG. 8 shows a screen example in which a transaction name (project name) and details of expenses are displayed as transaction information registered in the transaction database 2021 . This corresponds to step S212 in FIG.

As shown in FIG. 8, the display 132 of the terminal device 10 displays a status display column 1031a indicating status information and sub-status information, and a transaction name indicating the item name as detailed information on transactions stored in the transaction database 2021. A display field 1031b and a detail display field 1031c showing details of expenses are displayed, and a payment notification selection button (payment notification state selection means) 1031d for selecting payment notification as status information is provided. The payment notice selection button 1031d is a button for registering a payment notice as status information from the business operator, and confirms the status information and sub-status information displayed in the status display column 1031a, the delivery status of the item, etc. , is a button for selecting payment notification by pressing it when approving the delivery and selecting payment notification instead of billing for the status information. This payment notice selection button 1031d simplifies the procedure for selecting a payment notice.

On the screen shown in FIG. 8, the payment notification selection button 1031d is displayed when the status information and sub-status information are ready to move to the billing process or payment notification process (for example, when the ordering process is approved). If the contractor of the transaction is a sole proprietor, and if the contractor of the transaction has received a payment notice in the past, the contractor of the transaction is registered as a business operator that receives the payment notice. It may be controlled so that it is displayed only when it is set.

FIG. 9 is a diagram showing an example of a screen displaying transaction information displayed on the terminal device 10. As shown in FIG. The screen example of FIG. 9 shows a screen example in which a transaction name (case name) and details of expenses are displayed as transaction information registered in the transaction database 2021 . This corresponds to step S212 in FIG.

As shown in FIG. 9, the display 132 of the terminal device 10 includes a status display field 1031a, a transaction name display field 1031b, a detail display field 1031c, and a status display field 1032a similar to the payment notification selection button 1031d shown in FIG. A transaction name display field 1032b, a detail display field 1032c, and a payment notice selection button 1032d are displayed. Further, the display 132 of the terminal device 10 is provided with a billing selection button (billing state selection means) 1032e for selecting billing as status information. The request selection button 1032e is a button for registering a request from the business as status information. This is a button for selecting billing by pressing when approving a product and selecting payment notification instead of billing for status information.

In the screen shown in FIG. 9, the payment notification selection button 1032d and the billing selection button 1032e may be controlled so that when either one is selected, the other cannot be selected. It may be controlled so that the other cannot be selected when the period elapses.

FIG. 10 is a diagram showing an example of a screen for inputting transaction information displayed on the terminal device 10. As shown in FIG. The example screen of FIG. 10 shows an example of a screen in which a transaction name (issue name) or the like is input as transaction information to be registered in the transaction database 2021 . This corresponds to step S112 in FIG.

As shown in FIG. 10, the display 132 of the terminal device 10 has a status display field 1033a indicating status information and a transaction name input field 1033b indicating the project name as detailed information of the transaction to be registered in the transaction database 2021. Further, a payment notification selection button (payment notification state selection means) 1033c for selecting payment notification as status information is provided. The payment notice selection button 1033c has the same function as the payment notice selection button 1031d shown in FIG. 8, but differs in that it is at the stage of accepting registration of transaction information. As shown in FIG. 10, a payment notification selection button (payment notification state selection means) 1033c may accept a payment notification if it is in a transaction start state in which a transaction has been started. It may be displayed as "payment notice reservation".

FIG. 11 is a diagram showing an example of a screen displaying a transaction list displayed on the terminal device 10. As shown in FIG. The screen example of FIG. 11 shows a screen example in which a list of transaction information registered in the transaction database 2021 is displayed. This corresponds to step S212 in FIG.

As shown in FIG. 11, the display 132 of the terminal device 10 displays a list display column 1034a of transaction information stored in the transaction database 2021. As shown in FIG. In the list display column 1034a, as the transaction information, only the orderer and the orderer related to the transaction (in the case of the diagram shown in FIG. 11, it is an example of the screen of the orderer, so only the orderer (supplier) is displayed. ), a status display column 1034c showing status information and sub-status information, and a payment notice selection button (payment notice state selection means) 1034d for selecting payment notice as status information are displayed. there is This payment notice selection button 1034d facilitates collective selection of payment notices.

<Summary>
As described above, according to the present embodiment, for example, when the delivery of the actual product related to the transaction or the work related to outsourcing has been completed, the orderer sends the payment notification related to the transaction instead of the billing status information. Upon receipt of the payment notification status information indicating that the payment notification will be made, the payment notification is transmitted to the contractor, and payment processing is performed based on the information included in the payment notification. Therefore, it becomes possible for the contractor to reduce the load of issuing the invoice, and for the orderer, it becomes possible to control the timing and details of payment without waiting for the arrival of the invoice. This allows a smooth transition from transaction information to the payment process.

In addition, a payment notice selection button (billing state selection means) for selecting payment notice as status information is provided on a screen displaying detailed information on transactions or a screen displaying a list of transactions. This makes it possible to simplify the procedure for selecting a payment notice.

<Second Embodiment>
Other embodiments of the transaction management system 1 will be described below.

<1 Overall Configuration of Transaction Management System 1>
FIG. 12 is a diagram showing a functional configuration of server 20 that constitutes transaction management system 1 of Embodiment 2. As shown in FIG. The overall configuration of the transaction management system 1 and the configuration of the terminal device 10 according to the second embodiment are the same as those of the first embodiment, and will not be described repeatedly. The configuration of the server 20 is the same as that of the first embodiment, except that the function of the recommendation module 2038 is newly provided as shown in FIG. The functions of the recommendation module 2038 in the second embodiment will be described below.

The recommendation module 2038 controls the process of recommending registration of a payment notice as status information of transaction information. For example, the recommendation module 2038, for a transaction with the same business as a transaction for which a payment notification was registered as status information in the past, completes the delivery of the actual product related to the transaction and the work related to outsourcing, and the billing process is completed. Alternatively, when the payment notification process can be selected, register the payment notification as status information and recommend to send the payment notification to the business operator. In addition, the recommendation module 2038, when the attribute of the business operator (contractor) of the transaction partner matches a predetermined condition, for example, when the contractor of the transaction is a sole proprietor, or when the contractor of the transaction sends a payment notification If you are registered as a business operator that receives payment, when the actual delivery of the product related to the transaction or the work related to outsourcing is completed and you can select the billing process or the payment notification process, register the payment notification as status information and Recommend sending a payment notice to the merchant. In other words, the recommendation module 2038 recommends that the payment notice be registered as the status information for the transaction for which there is a high probability that the contractor of the transaction will select the payment notice.

When the recommendation module 2038 receives an instruction from the business operator to register the payment notice as status information, the status information registration reception module 2035 receives and registers the payment notice.

<2 Data structure>
The data structure in the second embodiment is the same as in the first embodiment, so it will not be described repeatedly.

<3 Operation>
Since the operation in the second embodiment is the same as that in the first embodiment, it will not be described repeatedly.

<4 Screen example>
An example of a screen for display processing of transaction information by the transaction management system 1 will be described below with reference to FIGS. 13 and 14. FIG.

FIG. 13 is a diagram showing an example of a screen displaying transaction information displayed on the terminal device 10. As shown in FIG. The screen example of FIG. 13 shows a screen example in which recommended information is displayed as a pop-up display on a screen displaying transaction information registered in the transaction database 2021 . This corresponds to step S212 in FIG.

As shown in FIG. 13, the display 132 of the terminal device 10 includes a status display column 1031a, a transaction name display column 1031b, and a status display column 1035a similar to the details display column 1031c shown in FIG. 8, a transaction name display column 1035b, and a detail display field 1035c are displayed. Furthermore, the display 132 of the terminal device 10 displays a recommendation information display field 1035d as a pop-up display. The recommendation information display column 1035d is provided with a permission button 1035e for accepting the recommendation content displayed in the recommendation information display column 1035d and a rejection button 1035f for not accepting the recommendation content.

On the screen shown in FIG. 13, the recommendation information display column 1035d recommends that payment notice be selected for transactions with the same business operator as the transaction for which payment notice was registered as status information in the past. With this recommendation information display field 1035d, it is possible to recognize that payment notice can be selected, and with the permission button 1035e and the rejection button 1035f, the procedure for selecting payment notice or not selecting payment notice Procedures become easier.

FIG. 14 is a diagram showing an example of a screen displaying transaction information displayed on the terminal device 10. As shown in FIG. The screen example of FIG. 14 shows a screen example in which recommended information is displayed as a pop-up display on a screen displaying transaction information registered in the transaction database 2021 . This corresponds to step S212 in FIG.

As shown in FIG. 14, the display 132 of the terminal device 10 includes a status display column 1035a, a transaction name display column 1035b, a detailed display column 1035c, a recommendation information display column 1035d, an accept button 1035e, and a reject button 1035f shown in FIG. A status display field 1036a, a transaction name display field 1036b, a detailed display field 1036c, a recommendation information display field 1036d, an allow button 1036e, and a reject button 1036f are displayed.

On the screen shown in FIG. 14, in the recommendation information display column 1036d, as an example of the case where the attributes of the business partner (contractor) of the transaction match the predetermined conditions, the case where the contractor of the transaction is a sole proprietor , recommending that payment advice be selected for the transaction. With this recommendation information display field 1036d, it is possible to recognize that payment notice can be selected, and with the permission button 1036e and the rejection button 1036f, the procedure for selecting payment notice or not selecting payment notice Procedures become easier.

<Summary>
As described above, according to the present embodiment, in the case of a transaction for which there is a high probability that the contractor of the transaction will select payment notice, specifically, the same business operator who registered payment notice as status information in the past , If the contractor of the transaction is a sole proprietor, or if the contractor of the transaction is registered as a business that receives payment notices, it is recommended to register payment notices as status information. This makes it possible for the orderer to grasp the transactions for which payment advice can be selected.

Although the disclosed embodiments have been described above, they can be implemented in various other forms, and can be implemented with various omissions, substitutions, and modifications. These embodiments, modifications, omissions, substitutions and changes are included within the technical scope of the claims and their equivalents.

<Appendix>
The items described in each of the above embodiments will be added below.

(Appendix 1) A program for executing a computer comprising a processor 29 and a memory 25 to manage transactions between a plurality of business operators, wherein the memory 25 stores status information (2021 ) is registered, and as status information, the transaction start state indicating that the transaction has been started, the billing state indicating that the transaction has been billed, and the payment notification state that indicates that the payment notification regarding the transaction has been made; is registered, and the program causes the processor 29 to accept registration of status information for a transaction from a business operator, and when the status information is a transaction start state, one of a plurality of business operators a step of accepting registration of a billing state or a payment notification state as status information from a business operator (S221, S222); A program for executing a step of transmitting (S223).

(Appendix 2) In the memory, sub-status information linked to the status information is registered, and as the sub-status information, status information including an approval waiting status for the status information status and an approved status for the status information status is stored. The program according to (Appendix 1), which receives registration of billing status or payment notification status as status information when registration of approved status is accepted as substatus information when status information is transaction start status. .

(Appendix 3) Payment notification status selection means is provided on a screen for accepting registration of billing status or payment notification status as status information, and payment notification status is provided as status information in response to selection of the payment notification status selection means. The program according to (Appendix 1) or (Appendix 2), which accepts registration of

(Appendix 4) In the screen for accepting registration of billing status or payment notification status as status information, billing status selection means is further provided, and only either billing status selection means or payment notification status selection means can be selected. The program according to (Appendix 3), which is set.

(Appendix 5) When the status information is in the transaction start state, if the registration of the payment notification state is not accepted as the status information by the predetermined period, the billing state is registered as the status information, from (Appendix 1) The program according to any one of (Appendix 4).

(Appendix 6) In addition, if the program accepts registration of payment notification status as status information in past transactions, the status information is transaction start status for transactions with the same business operator as the past transactions. The program according to any one of (Appendix 1) to (Appendix 5), causing a step of recommending registration of the payment notification state as the status information to be executed when the payment notification state is registered.

(Appendix 7) The program further registers payment notification status as status information when the status information is transaction start status for transactions with the business operator when the business operator's attributes match predetermined conditions. The program according to any one of (Appendix 1) to (Appendix 6), causing the step of recommending to be executed.

(Appendix 8) When the status information is the payment notice state, the program further executes a step of accepting registration of cancellation of the payment notice state as the status information by a predetermined period of time. (Appendix 1) to (Appendix 7 ).

(Appendix 9) On the screen that displays a list of transactions whose status information is in the transaction start state and that displays the status information of each of the displayed transactions, payment notification state selection means is provided for each displayed transaction, and the transaction is The program according to any one of (Appendix 1) to (Appendix 8), receiving registration of payment advice status as status information in response to selection of the payment advice status selection means.

(Appendix 10) Information on any one or more of the payee, payment method, and payment date related to the transaction is registered in the memory, and any one or more of the payee, payment method, and payment date related to the transaction is registered as a payment notice. The program according to any one of (Appendix 1) to (Appendix 9), which notifies the information of

(Supplementary Note 11) The program according to (Supplementary Note 10), which prompts registration of a payment destination or payment method related to a transaction if it is not registered.

(Appendix 12) Further, when the payment notice is sent to another business operator, the program causes the other business operator to perform payment processing by a predetermined date. (Appendix 1) (Appendix 11).

(Appendix 13) An information processing device comprising a control unit and a storage unit and managing transactions between a plurality of business operators, wherein status information (2021) relating to transactions is registered in the storage unit. , as status information, a transaction start state indicating that the transaction has been started, a billing state indicating that the transaction has been billed, and a payment notification state that indicates that the payment notification regarding the transaction has been made. When the information is registered, the control unit receives registration of status information for a transaction from a business operator (2035), and when the status information is in a transaction start state, a step of receiving registration of a billing state or a payment notification state as status information; a step of transmitting a payment notification to another business operator (2037) when registration of a payment notification state is received as status information (2036); information processing device.

(Appendix 14) A method for managing transactions between a plurality of business operators, executed by a computer comprising a processor 29 and a memory 25, wherein the memory 25 stores status information (2021 ) is registered, and as status information, a transaction start state indicating that the transaction has been started, a billing state indicating that the transaction has been billed, and a payment notification state that indicates that the payment notification regarding the transaction has been made; and the method is such that the processor 29 accepts registration of status information for a transaction from a merchant, and when the status information is a transaction opening status, one of the plurality of merchants a step of accepting registration of a billing state or a payment notification state as status information from a business operator (S221, S222); transmitting (S223) the method.

10 terminal device, 20 server, 80 network, 130 operation reception unit, 161 user information, 22 communication IF, 23 input/output IF, 25 memory, 26 storage, 29 processor, 201 communication unit, 202 storage unit, 2021 transaction database, 2022 user database, 203 control unit

Claims (15)

A program executed by a computer comprising a processor and a memory for managing transactions between a plurality of business operators,
Status information relating to the transaction is registered in the memory,
As the status information, a transaction start state indicating that the transaction has been started, a billing state indicating that the transaction has been billed, and a payment notification state that indicates that the payment notification regarding the transaction has been made. State information is registered, including
The transaction start state is from the registration of transaction information related to the transaction from the business operator to the actual delivery of the product related to the transaction and the end of the business related to outsourcing, and the billing state is the end of the business related to the transaction. It is a state in which the transaction is billed after the actual delivery of the product or the work related to the outsourcing is completed, and the payment notification status is the end of the actual delivery of the product or the work related to the outsourcing related to the transaction. later notified of information about payment for the transaction in lieu of the bill,
The program causes the processor to:
When the registration of the status information for the transaction is received from the business operator, and when the status information is the transaction start status, the status information is the billing status or the status information from one of the plurality of business operators. accepting registration for any of the payment advice states;
and transmitting a payment notice to another business operator when registration of payment notice status as the status information is accepted. The program further causes the processor to:
a step of not accepting registration to shift the status information from the billing state to the payment notification state after accepting the registration of the billing state as the status information;
2. The program according to claim 1, causing execution of a step of not accepting registration of shifting said status information from payment notification state to billing state after accepting registration of payment notification state as said status information. Sub-status information linked to the status information is registered in the memory,
as the sub-status information, state information including an approval waiting state for the state of the status information and an approved state for the state of the status information is registered;
Claim 1 or Claim 2, wherein when the status information is a transaction start state and registration of an approved state is received as the sub-status information, registration of a billing state or a payment notification state is received as the status information. program as described. Payment notification status selection means is provided on the screen for accepting registration of billing status or payment notification status as the status information,
4. The program according to any one of claims 1 to 3, wherein, in response to said payment advice status selection means being selected, registration of payment advice status as said status information is accepted. Billing state selection means is further provided on the screen for accepting registration of billing state or payment notification state as the status information,
5. The program according to claim 4 , wherein only one of said billing status selection means and said payment notification status selection means is set to be selectable. Claims 1 to 1, wherein, when the status information is a transaction start state, if registration of a payment notification state as the status information is not accepted within a predetermined period of time, a billing state is registered as the status information. 6. The program according to any one of 5 . The program further
In the past transaction, when registration of payment notification status is accepted as the status information, and for a transaction with the same business operator as the past transaction, when the status information is a transaction start status, the status 7. The program according to any one of claims 1 to 6 , causing execution of a step of recommending registration of payment advice status as information. The program further
executing a step of recommending registration of a payment notification state as the status information when the status information is a transaction start state for a transaction with the business operator when the attribute of the business operator matches a predetermined condition; 8. The program according to any one of claims 1 to 7 , which causes The program further
9. The method according to any one of claims 1 to 8 , wherein when the status information is the payment notification state, a step of accepting registration of cancellation of the payment notification state as the status information is executed within a predetermined period of time. program. a payment notification state selection means is provided for each of the displayed transactions on a screen displaying a list of the transactions whose status information is a transaction start state and displaying the status information of each of the displayed transactions;
10. The program according to any one of claims 1 to 9 , which accepts registration of a payment advice status as said status information in response to said payment advice status selection means for said transaction being selected. In the memory, one or more of the payment destination, payment means, and payment date related to the transaction are registered,
11. The program according to any one of claims 1 to 10, wherein as the payment notification, one or more of information regarding the payment destination, payment method, and payment date related to the transaction is notified. 12. The program according to claim 11 , prompting registration if the payee or payment means related to the transaction is not registered. The program further
13. The method according to any one of claims 1 to 12 , wherein when a payment notice is sent to another business operator, the other business operator executes a step of performing payment processing by a predetermined date. program as described. An information processing device comprising a control unit and a storage unit and managing transactions between a plurality of business operators,
Status information relating to the transaction is registered in the storage unit,
As the status information, a transaction start state indicating that the transaction has been started, a billing state indicating that the transaction has been billed, and a payment notification state that indicates that the payment notification regarding the transaction has been made. State information is registered, including
The transaction start state is from the registration of transaction information related to the transaction from the business operator to the actual delivery of the product related to the transaction and the end of the business related to outsourcing, and the billing state is the end of the business related to the transaction. It is a state in which the transaction is billed after the actual delivery of the product or the work related to the outsourcing is completed, and the payment notification status is the end of the actual delivery of the product or the work related to the outsourcing related to the transaction. later notified of information about payment for the transaction in lieu of the bill,
The control unit
When the registration of the status information for the transaction is received from the business operator, and when the status information is the transaction start status, the status information is the billing status or the status information from one of the plurality of business operators. accepting registration for any of the payment advice states;
and transmitting a payment notification to another business operator when registration of a payment notification state is received as the status information. A method executed by a computer comprising a processor and a memory for managing transactions between multiple entities, comprising:
Status information relating to the transaction is registered in the memory,
As the status information, a transaction start state indicating that the transaction has been started, a billing state indicating that the transaction has been billed, and a payment notification state that indicates that the payment notification regarding the transaction has been made. State information is registered, including
The transaction start state is from the registration of transaction information related to the transaction from the business operator to the actual delivery of the product related to the transaction and the end of the business related to outsourcing, and the billing state is the end of the business related to the transaction. It is a state in which the transaction is billed after the actual delivery of the product or the work related to the outsourcing is completed, and the payment notification status is the end of the actual delivery of the product or the work related to the outsourcing related to the transaction. later notified of information about payment for the transaction in lieu of the bill,
The method comprises: the processor;
When the registration of the status information for the transaction is received from the business operator, and when the status information is the transaction start status, the status information is the billing status or the status information from one of the plurality of business operators. accepting registration for any of the payment advice states;
and sending a payment advice to another business operator if registration of a payment advice status as the status information is accepted.