JP6991179B2 - Transaction management device, transaction management method and transaction management program - Google Patents

Description

The present disclosure relates to a transaction management device, a transaction management method, and a transaction management program for managing transaction data relating to transactions performed between a plurality of businesses.

When conducting transactions between companies and sole proprietors, documents such as quotations, purchase orders, and invoices for the products and business consignment related to the transaction are sent to the other party, and the details of the transaction are shown in the document. Such a document is created so that there is no discrepancy in transaction details and amounts, and is a document exchanged between the orderer and the contractor. However, transactions that occur between companies and sole proprietors are often continuous or have similar content over and over, with similar quotes, purchase orders, and invoices each time. It is necessary to create a document such as an invoice, and the work is time-consuming.

For example, in an accounting processing system that performs accounting processing in a company or an individual business, a system that manages transaction data between an orderer and a contractor is known (see, for example, Patent Document 1). The system disclosed in Patent Document 1 manages estimation data and billing data as transaction data, and clears the billing data registered by the contractor based on the payment schedule data registered by the orderer. Is to do. In such an accounting processing system, work efficiency is improved so that transaction data is generated based on estimation data and billing data is generated.

Japanese Unexamined Patent Publication No. 2018-139042

By the way, as mentioned above, many of the transaction management systems used by companies and the like are managed only within the company, and those shared with business partners are not often used. This is because there is a risk that business partner data within a company may be leaked to other companies, and it is not easy to standardize. For example, in a specific industry, a system called EDI (Electronic Data Interchange) that manages various transaction information among multiple companies is used, but the transaction management system used within the company is different for each company. It often has its own specifications, and it is not easy to use EDI for common use.

Therefore, in this disclosure, a transaction management device, a transaction management method, and a transaction management program, which can be easily accessed by both the orderer and the contractor by being managed for each transaction data and can be shared with the transaction data, will be described. ..

The transaction management device in one aspect of the present disclosure is a transaction management device that manages transaction data related to transactions performed between a plurality of businesses, and is a transaction data from one of the plurality of businesses. A transaction data registration reception unit that accepts registration and registers the work status of one of the multiple work processes set as the transaction work process related to the received transaction data as being in progress, and one business. Invitation notification unit that accepts invitations from multiple businesses to other businesses and notifies other businesses of the invitation, and transaction data for one business and the invited other businesses. The edit input reception unit that accepts the input of edits to the transaction data from one business operator or another invited business operator and reflects the edits to the transaction data, and the changes made by editing the transaction data. , Accepts input of approval for transaction data from one business operator or other invited business operator, and the work status of one work process. When the work status of one work process becomes the approval state, the work status of the subsequent work process set as the next work process of one work process is registered as working. It is equipped with a transaction data process change unit.

The transaction management method in one aspect of the present disclosure is a transaction management method for managing transaction data related to transactions performed between a plurality of business operators, and is performed by the transaction data registration reception unit among a plurality of business operators. Transaction data that accepts the registration of transaction data from one business operator and registers the work status of one of the multiple work processes set as the work process of the transaction related to the received transaction data as working. Registration acceptance step, invitation notification step performed by the invitation notification department to accept invitations from one business to other businesses among multiple businesses and notify other businesses of the invitation, and edit input reception The department presents transaction data to one business operator and other invited business operators, accepts input for editing of transaction data from one business operator or other invited business operators, and conducts transaction data. The edit input acceptance step that reflects the edits to the transaction data, the change part presentation step that presents the changed part due to the edit to the transaction data to the business operator other than the edited business operator, and the approval input The approval input acceptance step and transaction data process performed by the reception department to accept the input of approval for transaction data from one business operator or another invited business operator and change the work status of one work process to the approved state. When the work status of one work process performed by the change department becomes the approved state, the transaction data process change step that registers the work status of the subsequent work process set as the next work process of one work process as working. , Equipped with.

Further, the transaction management program in one aspect of the present disclosure is a transaction management program that manages transaction data related to transactions performed between a plurality of business operators, and is a transaction from one of the plurality of business operators. A transaction data registration acceptance step that accepts data registration and registers the work status of one of a plurality of work processes set as a transaction work process related to the accepted transaction data as working. Invitation notification step to accept invitations from multiple businesses to other businesses and notify other businesses of the invitation, and to one business and the invited other businesses An edit input acceptance step that presents transaction data, accepts edits to the transaction data from one business operator or another invited business operator, and reflects the edits to the transaction data, and edits to the transaction data. The step of presenting the changed part to present the part to the business other than the business that edited it, and the input of approval for the transaction data from one business or another invited business, and one work process When the approval input acceptance step that changes the work status to the approval state and the work status of one work process become the approval state, the work status of the subsequent work process that is set as the next work process of one work process is being worked on. Let the computer execute the transaction data process change step to be registered as.

According to the present disclosure, registration of transaction data is accepted from one of a plurality of businesses, and invitations to other businesses are accepted. Therefore, transaction data can be registered regardless of the orderer or the contractor, and can be easily accessed by being invited by another business operator. This makes it possible to easily and inexpensively construct a system in which transaction data can be shared among traders.

It is a functional block block diagram which shows the transaction management system which concerns on one Embodiment of this disclosure. It is a sequence diagram which shows the example of the work process and work status in the transaction management apparatus 100 of FIG. It is a functional block block diagram which shows the user terminal 200 of FIG. It is a flowchart which shows the operation of the transaction data registration process in the transaction management apparatus 100 of FIG. It is a screen display diagram which shows the example of the login screen W1 displayed on the display part 220 of FIG. It is a screen display diagram which shows the example of the transaction data input screen W2 displayed on the display part 220 of FIG. It is a flowchart which shows the operation of the transaction data editing process in the transaction management apparatus 100 of FIG. It is a screen display diagram which shows the example of the transaction data edit screen W3 displayed on the display part 220 of FIG. It is a screen display diagram which shows the example of the change part presentation screen W4 displayed on the display part 220 of FIG. It is a screen display diagram which shows the example of the form data screen W5 displayed on the display part 220 of FIG. It is a functional block block diagram which shows the transaction management apparatus 100A of the transaction management system which concerns on one Embodiment of this disclosure. It is a screen display diagram which shows the example of the transaction data input screen W6 displayed on the display part 220 of FIG. It is a functional block block diagram which shows the transaction management apparatus 100B of the transaction management system which concerns on one Embodiment of this disclosure. It is a functional block block diagram which shows the computer 700 which concerns on one Embodiment of this disclosure.

Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. The embodiments described below do not unreasonably limit the contents of the present disclosure described in the claims. Also, not all of the components shown in the embodiments are essential components of the present disclosure.

(Embodiment 1)
<Structure>
FIG. 1 is a functional block configuration diagram showing a transaction management system 1 according to the first embodiment of the present disclosure. This transaction management system 1 is not limited, but as an example, in a system that manages transaction data related to transactions performed between users who are business operators, it accepts registration of transaction data regardless of the orderer or the contractor and makes a transaction. It is a system that allows a business operator who is a user who registered data to mutually access and edit transaction data by inviting a business partner.

The service provided by the transaction management system 1 is not limited to the management of transaction data as described above, and may be a service for general accounting processing related to the user's company or individual business. For example, the input transaction data may be used as deposit / withdrawal data, and the input of financial data such as owned assets may be accepted to provide an accounting service for a user's company or individual business.

The transaction management system 1 has a transaction management device 100, a plurality of user terminals 200A, 200B, ..., And a network NW. The transaction management device 100 and the user terminals 200A, 200B, ... Are connected to each other via the network NW. The network NW is a communication network for communication, and is not limited to the Internet, an intranet, a LAN (Local Area Network), a WAN (Wide Area Network), a wireless LAN (Wireless LAN), and a wireless WAN (Wireless LAN). It is composed of a communication network including a wireless WAN (WAN), a virtual private network (VPN), and the like. Note that the user terminals 200A, 200B, ... Each have the same configuration, and when the configuration of the user terminals 200A, 200B, ... Is described, the user terminal 200 is represented as the user terminal 200.

The transaction management device 100 accepts registration of transaction data as a user from one of a plurality of businesses, registers and changes the work process and work status of the transaction data, and registers the transaction data and the user. It is a device that receives and reflects the editing of transaction data from a user who is another business operator invited by the user, and generates form data such as an estimate and a purchase order from the transaction data. The transaction management device 100 is not limited, but is composed of, for example, a computer (desktop, laptop, tablet, etc.) that provides various Web services, a device including a server device, and the like. The server device is not limited to a server device that operates independently, and may be a distributed server system or a cloud server that operates in cooperation by communicating via a network NW.

The user terminal 200 is a device that accepts operations for registering and editing transaction data input by the user and displays transaction data and form data, and is not limited to, as an example, a smartphone, a mobile terminal, or a computer (desktop, wrap). It is composed of tops, tablets, etc.). In this user terminal 200, as an example, not limited to, an application for managing transaction data in the transaction management system 1 is installed, or a URL or the like for accessing the transaction management device 100 is set, and tap or double them. The transaction data management or accounting service is started by starting it by clicking or displaying it on the browser.

FIG. 2 is a sequence diagram showing an example of a work process and a work status in the transaction management device 100 of FIG. The work process and work status managed by the transaction data in this embodiment will be described. Here, the work process is the "estimation stage", the "ordering stage", and the "billing stage" indicating the stage of the transaction in the business operator, and the work status is the "creation stage" indicating the state in the work process of each business operator. It is "medium", "confirming", "waiting", etc., and is registered for each of a plurality of businesses, for example.

First, the business operator who is the orderer or the contractor registers the transaction data. In addition, a business operator who is a business partner is invited, and this business operator can access transaction data. At this time, the orderer or the contractor is not limited to one company, that is, three or more businesses can access the transaction data as the orderer or the contractor.

At this time, as shown in FIG. 2, the work process of the registered transaction data is in the estimation stage, and the work status of the user who is the contractor is in the process of creating the quotation in step S001, and the work status of the user who is the orderer. Is waiting for an estimate in step S002. When the contractor creates a quotation and sends it to the orderer, the work status of the orderer is in the process of confirming the quotation in step S003, and the work status of the contractor is waiting for the quotation confirmation in step S004. When the orderer approves the contents of the quotation, the work status of the contractor becomes the quotation in step S005.

Next, the work process of the transaction data is in the ordering stage, and the work status of the orderer is in the process of creating the order in step S006. When the orderer creates an order and sends it to the contractor, the work status of the contractor is in the order confirmation in step S007, and the work status of the orderer is waiting for the order confirmation in step S008. When the contractor approves the order contents, the work status of the contractor becomes the order completed in step S009, and the work status of the orderer becomes the order completed in step S010. After that, the actual delivery of the product related to the transaction and the business related to outsourcing are performed.

When the actual delivery of goods related to the transaction and the work related to outsourcing are completed, the work process of the transaction data is in the billing stage, the work status of the contractor is in the process of creating the bill in step S011, and the work status of the orderer is step. Waiting for S012 billing. When the contractor creates a bill and sends it to the orderer, the work status of the orderer is in the process of confirming the bill content in step S013, and the work status of the contractor is waiting for the bill confirmation in step S014. When the orderer approves the billing content, the work status of the contractor becomes the billed in step S015, and the work status of the orderer becomes the billed content confirmed in step S016. After this, the payment is actually made and the transaction is completed. In the transaction management system 1, the work process and work status are changed and managed as described above. The above work process and work status are examples, and are not limited to these.

As shown in FIG. 1, the transaction management device 100 includes a communication unit 110, a storage unit 120, and a control unit 130.

The communication unit 110 is a communication interface for communicating with the user terminal 200 by wire or wirelessly via the network NW, and any communication protocol may be used as long as mutual communication can be executed. The communication unit 110 is not limited, and for example, communication is performed by a communication protocol such as TCP / IP (Transmission Control Protocol / Internet Protocol).

The storage unit 120 stores programs, input data, and the like for executing various control processes and each function in the control unit 130. It is composed of a memory including a memory) and a storage including an HDD (Hard Disk Drive), an SSD (Solid State Drive), a flash memory and the like. Further, the storage unit 120 stores the transaction DB 121, the form F (format) DB 122, and the user DB 123. Further, the storage unit 120 temporarily stores data when communicating with the user terminal 200 and the financial institution server 300, and data generated by each process described later.

The transaction DB 121 stores transaction data registered by a company or a private business that is a user of the transaction management system 1. Specifically, transaction information such as information on the products to be delivered (product number, model number, version number, quantity, etc.) generated in the business of the company, etc., and various payment information such as business consignment fees and purchase of equipment are available. , The information of the customer, the item, the date of occurrence, the transaction amount, etc. are stored. This transaction data is accessible only to the registered user and the user invited by that user.

Further, the transaction DB 121 also stores change history information so that the contents before and after the change can be presented when the contents of the transaction data are edited and changed by the change portion presenting unit 134 described later. When the transaction management system 1 provides an accounting service, the transaction data is aggregated and treated as financial information for a predetermined period such as daily, monthly, and year by the user's company or the like.

The form format DB 122 stores wording information and layout information necessary for the format of form data. Specifically, it is wording information and layout information necessary for creating an estimate, a purchase order, and an invoice, which are forms created for each of the above-mentioned work processes, and is an "estimate" and a "purchase order". , "Invoice" and other titles, fixed phrases, information that defines the position where items and amounts are described on the form, etc. are stored. This form format data is used when creating a form as a product of the above-mentioned work process, and form data is created by applying variable data such as a company name, an item, and an amount to this form format data.

The user DB 123 stores registration information of a company or a sole proprietor who is a user of the transaction management system 1. In the transaction management system 1, at least one of the orderer and the contractor who register the transaction data needs to be registered as a user, and the account information of the user, specifically, the user ID (email address) and password, Information such as the company name, the name of the sole proprietor, and contact information is stored.

The control unit 130 controls the entire operation of the transaction management device 100 by executing a program stored in the storage unit 120, and is not limited, but as an example, a CPU (Central Processing Unit), an MPU ( Devices including Micro Processing Unit (GPU), GPU (Graphics Processing Unit), Microprocessor, Processor core, Multiprocessor, ASIC (Application-Specific Integrated Circuit), FPGA (Field Programmable Gate Array) Etc. As the functions of the control unit 130, the transaction data registration reception unit 131, the invitation notification unit 132, the edit input reception unit 133, the change part presentation unit 134, the form data generation unit 135, the approval input reception unit 136, and the transaction. It is provided with a data process changing unit 137. The transaction data registration reception unit 131, invitation notification unit 132, edit input reception unit 133, change location presentation unit 134, form data generation unit 135, approval input reception unit 136, and transaction data process change unit 137 are stored in the storage unit 120. It is started by the stored program and executed by the transaction management device 100.

The transaction data registration reception unit 131 communicates the transaction data because the user terminal 200 is operated by the operation of the user who is one of the plurality of businesses and the registration information of the transaction data is transmitted. Accepted via unit 110. In addition, the work status of the received transaction data is registered. For example, the work process of the received transaction data is registered as the estimation stage, and if the registered user is the contractor, the work status of the user is registered as being created (working), and if the orderer is the orderer, the user's work status is registered. Register the work status as waiting for quotation. The received transaction data is stored in the transaction DB 121.

The invitation notification unit 132 operates the user terminal 200 by the operation of the user who has registered the transaction data, and the invitation data for inviting another business operator who is a business partner is transmitted. Therefore, the invitation notification unit 132 communicates the invitation data. Accepted via unit 110. In addition, the received invitation data will be notified to the other business operators. The invitation data includes contact information to the other business operator, and if the other business operator is a user of the transaction management system 1, account information and the like are included, and if the other business operator is not a user of the transaction management system 1. Includes e-mail address and the like.

Further, the invitation notification unit 132 registers the work status of the invited business operator as being in the process of making an estimate (working) when the invited business operator is the contractor, and estimates the work status of the business operator when the orderer is the orderer. Register as a wait. Hereinafter, the invited business operator and the business operator who registered the transaction data are collectively referred to as "user".

In the edit input reception unit 133, the user terminal 200 is operated by the operation of another invited business operator, and access information to the transaction management device 100 is transmitted. Therefore, the access information is transmitted via the communication unit 110. The corresponding transaction data received and stored in the transaction DB 121 is transmitted, displayed on the user terminal 200, and presented. Further, since the user terminal 200 is operated by the user to input the edit to the transaction data, the edit input reception unit 133 accepts the edit information via the communication unit 110 and stores it in the transaction DB 121. Reflect the edited contents for the applicable transaction data. Information before and after editing the transaction data is stored in the transaction DB 121 as a change history.

Further, since the user terminal 200 is operated by the user's operation to input the change of the work status for the transaction data, the edit input reception unit 133 accepts the change information via the communication unit 110 and enters the transaction DB 121. Reflect the changes to the corresponding transaction data stored. For example, when the work process of transaction data is in the estimation stage, when the user who is the contractor creates an estimate and sends it to the orderer, the user changes the work status to waiting for the estimate confirmation, so that the user registers it in the transaction DB 121. At this time, the work status of the orderer is registered in the transaction DB 121 as being confirmed for quotation.

When the transaction data is accessed by a user other than the user who has performed the editing received by the edit input reception unit 133, the change location presentation unit 134 has the same edit content reflected by the edit input reception unit 133. It is transmitted to the user terminal 200 of the user, and the changed part is displayed and presented. At this time, since the information before and after the editing of the transaction data is stored in the transaction DB 121 as a change history, the part corresponding to the change is presented. The changed part presenting unit 134 displays the changed part by highlighting displaying it in bold or different colors, highlighting it by shading, or displaying a comment by a balloon or the like. Further, the changed part presenting unit 134 displays the changed part by the change history display in which the state before and after the change can be recognized. By such highlighting and change history display, the changed part can be recognized at a glance.

The form data generation unit 135 generates form data created as a deliverable for each of a plurality of work processes, and in the above-mentioned example, quotation data, purchase order data, and invoice data. In the format data of the form data stored in the form format DB 122, titles and fixed phrases such as "estimate", "purchase order", and "invoice" are already set, and the position where the item and the amount are described on the form. Is defined, the form data is generated by applying variable data such as the item and amount data of the transaction data stored in the transaction DB 121 to the form format data. Further, the form data generation unit 135 transmits to the user terminal 200 and displays it.

The approval input receiving unit 136 operates the user terminal 200 by the user's operation to input the approval for the above-mentioned transaction data work process. Therefore, the approval input receiving unit 136 accepts the approval information via the communication unit 110 and enters the transaction DB 121. Reflect the work status for the corresponding transaction data stored. For example, when the work process of transaction data is in the estimation stage, the user who is the ordering party approves the quotation, so the approval information is accepted via the communication unit 110, and the work status of the contractor has been estimated (approval status). Is registered in the transaction DB 121. Further, for example, when the work process of transaction data is in the ordering stage, the user who is the contractor approves the order, so the approval information is accepted via the communication unit 110, and the work status of the contractor has been ordered (approved). It is registered in the transaction DB 121 as a state), and the work status of the orderer is registered in the transaction DB 121 as an order completed (approved state).

When accepting the input of approval, the approval input receiving unit 136 determines whether or not other work statuses are set in a predetermined state, and if it is in that state, the work status is changed to the approval state. You may. For example, when three or more businesses are accessing transaction data as an orderer or a contractor, approval may not be accepted unless the company is in a state of confirmation or waiting. This makes it possible to prevent unnecessary rework work.

When the work status of the transaction data in the transaction DB 121 is registered as estimated, ordered, and ordered, the transaction data process change unit 137 advances the work process to the next work process (subsequent work process). For example, when the estimation stage is approved in the work process of the transaction data, the work process is registered as the ordering stage, and the work status of the orderer is registered in the transaction DB 121 as the order is being created (working). In addition, when the ordering stage is approved in the work process of transaction data and the work is completed after that, the work process is registered as the billing stage, the work status of the contractor is registered in the transaction DB 121 as billing is being created (working), and the order is placed. The work status of the person is registered in the transaction DB 121 as waiting for billing.

In the transaction data process change unit 137, for example, when the user wants to skip the next work process, the user terminal 200 is operated by the user's operation, and a skip instruction for skipping the above-mentioned transaction data work process is given. Since it is input, the skip instruction may be accepted via the communication unit 110. At this time, the transaction data process change unit 137 may further advance the work process to the next work process (next subsequent work process) with respect to the corresponding transaction data stored in the transaction DB 121. As a result, unnecessary work processes can be skipped, and more flexible work process management becomes possible.

FIG. 3 is a functional block configuration diagram showing the user terminal 200 of FIG. The user terminal 200 includes a communication unit 210, a display unit 220, an operation unit 230, a storage unit 240, and a control unit 250.

The communication unit 210 is a communication interface for communicating with the transaction management device 100 by wire or wirelessly via the network NW, and any communication protocol may be used as long as mutual communication can be executed. The communication unit 210 is not limited, and communication is performed by a communication protocol such as TCP / IP as an example.

The display unit 220 is a user interface used for displaying the operation content input by the user and the transmission content from the transaction management device 100, and is composed of a liquid crystal display or the like. In the display unit 220, the transaction data to be edited is displayed by the edit input reception unit 133, the changed part of the transaction data is displayed by the changed part presentation unit 134, or the form data generated by the form data generation unit 135 is displayed. ..

The operation unit 230 is a user interface used for a user to input an operation instruction, and is composed of a keyboard, a mouse, a touch panel, and the like. The operation unit 230 can input transaction data in the transaction data registration reception unit 131, input invitations of other businesses in the invitation notification unit 132, edit input of transaction data in the edit input reception unit 133, or in the approval input reception unit 136. Used to enter approval for a work process.

The storage unit 240 stores programs for executing various control processes and functions in the control unit 250, input data, and the like. The storage unit 240 is not limited, and as an example, a memory including RAM, ROM, etc., an HDD, It is composed of storage including SSD, flash memory and the like. Further, the storage unit 240 temporarily stores the data that has communicated with the transaction management device 100.

The control unit 250 controls the entire operation of the user terminal 200 by executing a program stored in the storage unit 240, and is not limited to, as an example, a CPU, an MPU, a GPU, a microprocessor, and a processor. It is composed of a core, a multiprocessor, an ASIC, a device including an FPGA, and the like.

<Processing flow>
The processing flow of an example of the transaction management method executed by the transaction management device 100 of the transaction management system 1 will be described. First, with reference to FIG. 4, the flow of the transaction data registration process, which is a part of the transaction management method, executed by the transaction management device 100 will be described. FIG. 4 is a flowchart showing the operation of the transaction data registration process in the transaction management device 100 of FIG.

As the process of step S101, the transaction management device 100 performs user authentication in order to provide the user with the transaction data itself by the transaction management system 1, the work process and work status of the transaction data, and the accounting service including them. Therefore, the user is requested to input the account information and the password, and the user authentication is performed by collating with the registered information based on the input information. If they match, the user is logged in to the transaction management device 100.

FIG. 5 is a screen display diagram showing an example of the login screen W1 displayed on the display unit 220 of FIG. In step S101, since the user operates the user terminal 200 to access the transaction management device 100, the URL of the login screen is transmitted according to the instruction of the transaction management device 100, and the login screen is displayed. Alternatively, the login screen is displayed according to the instruction of the application installed in the user terminal 200 in advance. By these operations, the login screen W1 as shown in FIG. 5 is displayed on the display unit 220 of the user terminal 200.

When the login screen W1 as shown in FIG. 5 is displayed on the display unit 220 of the user terminal 200, the user operates the operation unit 230 to input the account input field IN1 provided on the login screen W1 and the password. Enter your account information (email address in this embodiment) and password in the field IN2. After that, by pressing the login button B1, the user authentication in step S101 is performed, and the user is logged in to the transaction management device 100.

As the process of step S102, the transaction data registration information is transmitted by the operation of the operation unit 230 of the user terminal 200. Therefore, in the transaction data registration reception unit 131 of the transaction management device 100, the transaction data is transmitted via the communication unit 110. Will be accepted. The received transaction data is stored in the transaction DB 121.

FIG. 6 is a screen display diagram showing an example of the transaction data input screen W2 displayed on the display unit 220 of FIG. When user authentication is performed in step S101, the user is logged in to the transaction management device 100 and input of transaction data is selected by selecting a menu or a tab, the transaction data input screen W2 shown in FIG. 6 is displayed on the display unit 220 of the user terminal 200. Then, the input becomes possible by the operation of the operation unit 230.

When the transaction data input screen W2 as shown in FIG. 6 is displayed on the display unit 220 of the user terminal 200, the user can operate the operation unit 230 to display the amount field IN3 provided on the transaction data input screen W2. , In various input fields such as supplier input field IN4, input information such as supplier information (company name and individual business owner's name), item, account item, date of occurrence, amount, etc. related to transaction data. After that, by pressing the registration button B2, the transaction data in step S102 is registered.

As the process of step S103, the transaction data registration receiving unit 131 registers the work status of the transaction data registered in step S102. For example, the work process of transaction data is registered as an estimation stage, and if the registered user is a contractor, the work status of the user is registered as being created (working), and if the orderer is the orderer, the work status of the user is registered. Is stored in the transaction DB 121 while waiting for an estimate.

As the process of step S104, the invitation data for inviting another business operator who is a business partner is transmitted by the operation of the operation unit 230 of the user terminal 200. Therefore, the invitation notification unit 132 of the transaction management device 100 sends the invitation data. Is accepted via the communication unit 110. The accepted invitation data is notified to the other business operator by the account information, e-mail address, etc. of the other business operator included in the invitation data.

Next, with reference to FIG. 7, the flow of the transaction data editing process, which is a part of the transaction management method, executed by the transaction management device 100 will be described. FIG. 7 is a flowchart showing the operation of the transaction data editing process in the transaction management device 100 of FIG.

As the process of step S201, the access information to the transaction management device 100 is transmitted by the operation of the operation unit 230 of the user terminal 200 by the other business operator notified of the invitation data in step S104. Therefore, the edit input reception unit 133 receives the access information via the communication unit 110. Further, the edit input receiving unit 133 transmits the corresponding transaction data stored in the transaction DB 121 and displays it on the user terminal 200 of the other business operator.

As the process of step S202, the editing information for the transaction data is transmitted by the operation of the operation unit 230 of the user terminal 200, so that the editing input receiving unit 133 receives the editing information via the communication unit 110. The received editing information is reflected in the corresponding transaction data stored in the transaction DB 121. At this time, the transaction DB 121 stores information before and after editing the transaction data as a change history.

FIG. 8 is a screen display diagram showing an example of the transaction data editing screen W3 displayed on the display unit 220 of FIG. When the transaction management device 100 is accessed by the operation of another business operator in step S201, the transaction data is transmitted, and the transaction data editing screen W3 as shown in FIG. 8 is displayed on the user terminal 200. Further, when the transaction data is similarly accessed by the operation of the user who registered the transaction data, the transaction data editing screen W3 is similarly displayed on the user terminal 200.

When the transaction data editing screen W3 as shown in FIG. 8 is displayed on the display unit 220 of the user terminal 200, the user is provided on the transaction data editing screen W3 by operating the operation unit 230, if necessary. Enter information for changing transaction data in various input fields such as item input field IN5 and amount input field IN6. Further, by pressing the work status display T1, the change of the work status is input. After that, by pressing the registration button (not shown), the edit input in step S202 is performed, and the edit information for the transaction data is transmitted to the transaction management device 100. Is accepted via the communication unit 110.

As the process of step S203, when the transaction data is accessed by a user other than the user who performed the editing accepted in step S202 in the changed part presenting unit 134, the edited content reflected in step S202 is the other. It is transmitted to the user terminal 200 of the user of the above, and the changed part is displayed. This changed part is displayed by the information before and after editing the transaction data stored in the transaction DB 121. At this time, in the changed part presenting unit 134, the changed part is displayed by, for example, highlighting displayed in bold or a different color, highlighting display by shading, or comment display by a balloon or the like. In addition, the changed part is displayed by the change history display in which the state before and after the change can be recognized.

FIG. 9 is a screen display diagram showing an example of the changed portion presentation screen W4 displayed on the display unit 220 of FIG. The edited part of the transaction data performed in step S202 is shown as the highlight display H1 of the changed part presenting screen W4 shown in FIG. The highlight display H1 shows the information before and after the editing of the transaction data stored in the transaction DB 121 in a shaded manner, and the edited portion can be recognized at a glance. Although it is difficult to understand in the highlight display H1 of FIG. 9, the display is such that the contents of the changed transaction data can also be read.

As the process of step S204, in the form data generation unit 135, the data of the item and the amount of the transaction data stored in the transaction DB 121 is applied to the format data of the form data stored in the form format DB 122, and the form data is applied. Is generated. The generated form data is, for example, a quote, purchase order, or invoice.

FIG. 10 is a screen display diagram showing an example of the form data screen W5 displayed on the display unit 220 of FIG. In the format data of the form data stored in the form format DB 122, the form title T2 which is the form name provided on the form data screen W5 and the frame L1 for inputting the item and the amount are set in advance. There is. Therefore, the form data is generated by applying the data of the item and the amount of the transaction data stored in the transaction DB 121 to the places such as the address field IN7 and the amount field IN8. This form data may be printed and mailed, or may be delivered to the other party as electronic data in the transaction management device 100.

As the process of step S205, the approval for the work process of the transaction data is transmitted by the operation of the operation unit 230 of the user terminal 200, so that the approval input reception unit 136 accepts the approval information via the communication unit 110. .. For example, when the work process of transaction data is in the estimation stage, the estimation is approved by the user who is the ordering party, and the work status of the contractor is registered in the transaction DB 121 as estimated (approved state). Further, for example, when the work process of the transaction data is in the ordering stage, the order is approved by the user who is the contractor, the work status of the contractor is registered in the transaction DB 121 as ordered (approved status), and the work status of the orderer. Is registered in the transaction DB 121 as ordered (approved state).

In step S205, although not shown, an approval button (approval input means) is provided in the transaction data editing screen W3 shown in FIG. 8 and the changed part presentation screen W4 shown in FIG. 9, and the approval button is pressed. Approval input may be made.

As the process of step S206, the transaction data process change unit 137 advances the work process to the next work process (subsequent work process) when the approval input is performed in step S205. For example, if the estimation stage is approved in the work process of transaction data, the work process is registered in the transaction DB 121 as an ordering stage. Further, when the ordering stage is approved in the work process of the transaction data and the business is completed thereafter, the work process is registered in the transaction DB 121 as the billing stage.

As the process of step S207, when the work process is advanced in step S206, the transaction data process change unit 137 registers the work status of the advanced work process. For example, when the work process is registered as the ordering stage, the work status of the ordering party is registered in the transaction DB 121 as ordering being created (working). When the work process is registered as the billing stage, the work status of the contractor is registered in the transaction DB 121 as billing is being created (working), and the work status of the orderer is registered in the transaction DB 121 as waiting for billing. As a result, the work process and work status are automatically updated, so that appropriate transaction data can be managed.

<Effect>
As described above, when the transaction management device and the transaction management method according to the present embodiment receive the registration of transaction data from the business operator who is the user regardless of the orderer or the contractor, the transaction management device and the transaction management method accept invitations to other business operators. The business operator will be notified. In addition, transaction data can be edited regardless of the orderer or contractor. Therefore, it can be easily accessed by the invited business operator, and transaction data can be registered, edited, and used regardless of the orderer or the contractor. This makes it possible to easily and inexpensively construct a system in which transaction data can be shared among traders.

Further, when the input of approval for the transaction data is received, the work status of the subsequent work process is registered as working. At this time, since the common transaction data is used even if the work process progresses, for example, the transaction data registered in the process of the estimation stage can be used even in the ordering stage. Furthermore, since both the orderer and the contractor can access the transaction data, the transaction data can be shared between different work processes. This makes it possible to construct a transaction data management system that facilitates process control.

Further, when the transaction data is accessed by a user other than the user who edited the changed part by the changed part presenting unit, the changed part is displayed by highlighting or the like for the edited content. As a result, it is possible to share data updates when transaction data is shared among traders.

(Embodiment 2)
FIG. 11 is a functional block configuration diagram showing the transaction management device 100A of the transaction management system 1 according to the second embodiment of the present disclosure. The transaction management device 100A accepts the registration of transaction data as a user from one of a plurality of businesses, registers and changes the work process and work status, and from the user who registered the transaction data and the user. Similar to the transaction management device 100 according to the first embodiment, the storage unit 120 is an input item in that the transaction data is edited and reflected from the user who is another invited business operator to generate the form data. It differs from the transaction management device 100 according to the first embodiment in that it stores a DB (input item model data) 124 and has a recommendation unit 138 as a function of the control unit 130.

The present embodiment has a function of recommending input candidates from past input items when registering transaction data in the transaction data registration receiving unit 131 and editing transaction data in the edit input receiving unit 133. Therefore, the input item DB 124, which is the model information based on the input contents to the past input items, is stored.

The input item DB 124 stores model data constructed by machine learning from the contents input to the input items of the transaction data in the past by the company or the sole proprietor who is the user of the transaction management system 1. This model data is constructed from the relationship between the input items stored in the transaction DB 121 and the input contents, for example, and the recommendation unit 138, which will be described later, recommends the optimum input contents for the predetermined input items. It is the model data of.

The recommendation unit 138 is optimal for a predetermined input item when registering transaction data in the transaction data registration reception unit 131 or editing transaction data in the edit input reception unit 133 based on the model data stored in the input item DB 124. Recommend various input candidates. For example, when there are a plurality of candidates, recommendations may be made in descending order of priority, and when some characters or numbers are input, those that apply to the input contents may be recommended. Further, the recommendation unit 138 may give a warning to the input items stored in the transaction DB 121 and the input contents deviating from the input contents based on the model data stored in the input item DB 124. .. Other configurations and processing flows are the same as those in the first embodiment.

FIG. 12 is a screen display diagram showing an example of the transaction data input screen W6 displayed on the display unit 220 of FIG. The transaction data input screen W6 shown in FIG. 12 is provided with a customer input field IN9. When trying to enter the business name of a business partner in this business partner input field IN9, for example, if some characters are entered, the recommendation unit 138 recommends input candidates that apply to the part of the input contents. The recommendation column R1 is displayed. For example, the name of a company that is a business partner should be entered in the official name, but it is troublesome to enter the exact official name, such as the difference between the previous stock and the latter stock. As a result, the labor can be reduced.

According to the present embodiment, in addition to the effect of the first embodiment, by providing the recommendation unit, the optimum input candidate for the input item is recommended, so that it is possible to reduce the time and effort for inputting.

(Embodiment 3)
FIG. 13 is a functional block configuration diagram showing the transaction management device 100B of the transaction management system 1 according to the third embodiment of the present disclosure. The transaction management device 100B accepts the registration of transaction data as a user from one of a plurality of businesses, registers and changes the work process and work status, and from the user who registered the transaction data and the user. Similar to the transaction management device 100A according to the second embodiment, in that the transaction data is edited and reflected from the user who is another invited business operator to generate the form data, but as a function of the control unit 130. Further, it is different from the transaction management device 100A according to the second embodiment in that it is provided with a machine learning unit 139.

In the present embodiment, as in the second embodiment, there is a function of recommending input candidates from past input items when registering transaction data in the transaction data registration reception unit 131 and editing transaction data in the edit input reception unit 133. Although it is equipped, it is equipped with a machine learning unit for constructing model information for that purpose.

The machine learning unit 139 performs machine learning from the contents input in the input items of the transaction data in the past by the company or the sole proprietor who is the user of the transaction management system 1. At this time, the transaction data or input item to be machine learning may be only the transaction data of the user, or may be the transaction data of a business operator of a similar scale or industry. As the machine learning method by the machine learning unit 139, machine learning may be performed by any method such as supervised machine learning and reinforcement learning. The machine learning unit 139 performs machine learning at a predetermined timing, reflects it in the input item DB 124, and updates it.

According to the present embodiment, in addition to the effect of the second embodiment, the provision of the machine learning unit makes it possible to improve the accuracy of the recommendation of the input item.

(Embodiment 4 (program))
FIG. 14 is a functional block configuration diagram showing an example of the configuration of the computer (electronic computer) 700. The computer 700 includes a CPU 701, a main storage device 702, an auxiliary storage device 703, and an interface 704.

Here, the transaction data registration reception unit 131, the invitation notification unit 132, the edit input reception unit 133, the change part presentation unit 134, the form data generation unit 135, and the approval input reception unit 136 according to the first to third embodiments. The details of the control program (transaction management program) for realizing each function constituting the transaction data process change unit 137, the recommendation unit 138, and the machine learning unit 139 will be described. These functional blocks are implemented in the computer 700. The operation of each of these components is stored in the auxiliary storage device 703 in the form of a program. The CPU 701 reads a program from the auxiliary storage device 703, expands it to the main storage device 702, and executes the above processing according to the program. Further, the CPU 701 secures a storage area corresponding to the above-mentioned storage unit in the main storage device 702 according to the program.

Specifically, the program accepts registration of transaction data from one of a plurality of businesses on the computer 700, and is set as a transaction work process related to the received transaction data. A transaction data registration acceptance step that registers the work status of one of the work processes as being worked, and an invitation from one business operator to another business operator among multiple business operators, and other businesses. Invitation notification step to notify a person of an invitation and present transaction data to one business operator and other invited business operators, and edit the transaction data from one business operator or another invited business operator. The edit input acceptance step that accepts the input of and reflects the edit to the transaction data, and the change part presentation step that presents the changed part due to the edit to the transaction data to the business operator other than the business operator who edited it. The approval input acceptance step that accepts the input of approval for the transaction data from the business operator or other invited business operator and changes the work status of one work process to the approval status, and the work status of one work process is the approval status. Then, it is a control program that realizes a transaction data process change step of registering the work status of the subsequent work process set as the next work process of one work process as being worked by a computer.

The auxiliary storage device 703 is an example of a tangible medium that is not temporary. Other examples of non-temporary tangible media include magnetic disks, magneto-optical disks, CD-ROMs, DVD-ROMs, semiconductor memories and the like connected via the interface 704. Further, when this program is distributed to the computer 700 via the network, the distributed computer 700 may expand the program to the main storage device 702 and execute the above processing.

Further, the program may be for realizing a part of the above-mentioned functions. Further, the program may be a so-called difference file (difference program) that realizes the above-mentioned function in combination with another program already stored in the auxiliary storage device 703.

Although the embodiments related to the disclosure have been described above, these can be implemented in various other embodiments, and can be implemented by making various omissions, substitutions, and changes. These embodiments and modifications, as well as those omitted, replaced or modified, are included in the technical scope of the claims and the equivalent scope thereof.

1,1A transaction management system, 100, 100A, 100B transaction management device, 110 communication unit, 120 storage unit, 121 transaction DB, 122 form F (format) DB, 123 user DB, 124 input item DB (input item model data) , 130 Control unit, 131 Withdrawal information reception unit, 132 Invitation notification unit, 133 Edit input reception unit, 134 Change location presentation unit, 135 Form data generation unit, 136 Approval input reception unit, 137 Transaction data process change unit, 138 Recommendation Unit, 139 Machine learning unit, 200A, 200B, ... (200) User terminal, 210 communication unit, 220 display unit, 230 operation unit, 240 storage unit, 250 control unit, NW network

Claims (13)

A transaction management device that manages transaction data related to transactions performed between multiple businesses.
A work process of one of a plurality of work processes set as a work process of the transaction related to the transaction data received by receiving registration of the transaction data from one of the plurality of businesses. Transaction data registration reception department that registers the work status of
The one business operator accepts an invitation from the other business operator among the plurality of business operators to access and edit the transaction data, and invites the other business operator to the other business operator. Invitation notification section to notify and
The transaction data is presented to the one business operator and the other business operator, and the input of editing for the transaction data is accepted from the one business operator and the other business operator, respectively, and the transaction data is received. The edit input reception unit that reflects the above edits,
The changed part presenting unit that presents the changed part of the transaction data by the editing to the business operator other than the business operator who performed the editing, and the changed part presenting unit.
Approval input that accepts the input of approval for the transaction data from the one business operator or the other business operator and changes the work status of the one work process registered for each of the plurality of business operators to the approval state. With the reception department
When the work status of the one work process becomes the approved state, the work status of the subsequent work process set as the next work process of the one work process and registered for each of the plurality of business operators is registered as working. Transaction data process change department and
When inputting edits to the transaction data by the one business operator or the other business operator, input candidates for the input items of the transaction data are based on the input item model data constructed from the input items of the transaction data in the past. The recommendation section that recommends
A transaction management device including a machine learning unit that performs machine learning based on input contents for input items of the past transaction data and generates the input item model data . The transaction management device according to claim 1, further comprising a form data generation unit for generating different form data, which is set for each of the plurality of work processes based on the transaction data. The second aspect of claim 2, wherein the form data generation unit generates one or more form data of the quotation data, the purchase order data, and the invoice data for the transaction data for each of the plurality of work processes. Transaction management device. The transaction management according to claim 2 or 3, wherein the form data generation unit generates the form data set in the subsequent work process when the work status of the subsequent work process is registered as being in progress. Device. Upon receiving the input of approval for the transaction data, the approval input receiving unit determines whether or not the transaction data and the work status of the one work process are in the set predetermined state, and the predetermined predetermined state. The transaction management device according to any one of claims 1 to 4, wherein the work status of the one work process is changed to the approval state when the state is in the state. When the transaction data process change unit receives a skip instruction for skipping the subsequent work process from the one business operator or the other business operator, the next work process set as the next work process of the subsequent work process is next. The transaction management device according to any one of claims 1 to 5, which registers the work status of the subsequent work process as being worked. The approval input receiving unit presents the approval input means for inputting the approval for the transaction data to the one business operator and the other business operator, and the input of the approval input means is used to input the approval input means. The transaction management device according to any one of claims 1 to 6, wherein the work status of the above is changed to the approval state. The transaction management device according to any one of claims 1 to 7, wherein the changed part presenting unit presents the changed part by the editing by highlighting, highlighting, or commenting. The changed part presenting unit presents the changed part by the edit by the change history display which can recognize the state before the change by the edit and the state after the change, any one of claims 1 to 8. The transaction management device described in. The transaction management device according to any one of claims 1 to 9 , wherein the recommendation unit presents a warning for an input item of the input transaction data based on the input item model data. The transaction management device according to any one of claims 1 to 10 , wherein the plurality of businesses are the orderer or the contractor of the transaction related to the transaction data. It is a transaction management method that manages transaction data related to transactions performed between multiple businesses.
A plurality of operations set as a work process of the transaction related to the transaction data, which is performed by the transaction data registration reception unit and receives registration of the transaction data from one of the plurality of businesses. A transaction data registration acceptance step that registers the work status of one of the processes as being in progress,
The invitation notification unit accepts an invitation from the one business operator to another business operator among the plurality of business operators to access and edit the transaction data, and the other business operator. Invitation notification step to notify the business operator of the invitation, and
The transaction data is presented to the one business operator and the other business operator performed by the edit input reception unit, and the one business operator and the other business operator input edits to the transaction data, respectively. Acceptance, edit input acceptance step that reflects the edit on the transaction data,
The change part presentation step of presenting the changed part by the edit to the transaction data to the business operator other than the edited business operator, which is performed by the changed part presenting unit.
The approval input reception unit accepts the input of approval for the transaction data from the one business operator or the other business operator, and determines the work status of the one work process registered for each of the plurality of business operators. Approval input acceptance step to change to approval status,
When the work status of the one work process performed by the transaction data process change unit is in the approved state, the subsequent work process is set as the next work process of the one work process and is registered for each of the plurality of business operators. Transaction data process change step to register the work status of
When the recommendation department inputs edits to the transaction data by the one business operator or the other business operator, the transaction data is based on the input item model data constructed from the input items of the transaction data in the past. A recommendation step that recommends input candidates for input items, and
A transaction management method comprising a machine learning step of performing machine learning based on input contents for input items of the past transaction data performed by the machine learning unit and generating the input item model data . A transaction management program that manages transaction data related to transactions conducted between multiple businesses.
A work process of one of a plurality of work processes set as a work process of the transaction related to the transaction data received by receiving registration of the transaction data from one of the plurality of businesses. Transaction data registration acceptance step to register the work status of
The one business operator accepts an invitation from the other business operator among the plurality of business operators to access and edit the transaction data, and invites the other business operator to the other business operator. Invitation notification step to notify and
The transaction data is presented to the one business operator and the other business operator, and the input of editing for the transaction data is accepted from the one business operator and the other business operator, respectively, and the transaction data is received. And the edit input acceptance step that reflects the above edits,
A change part presentation step for presenting the changed part of the transaction data by the editing to the business operator other than the business operator who performed the editing, and a step of presenting the changed part.
Approval input that accepts the input of approval for the transaction data from the one business operator or the other business operator and changes the work status of the one work process registered for each of the plurality of business operators to the approval state. Reception step and
When the work status of the one work process becomes the approved state, the work status of the subsequent work process set as the next work process of the one work process and registered for each of the plurality of business operators is registered as working. Transaction data process change steps and
When inputting edits to the transaction data by the one business operator or the other business operator, input candidates for the input items of the transaction data are based on the input item model data constructed from the input items of the transaction data in the past. The recommendation step to recommend, and
A transaction management program for causing a computer to perform machine learning based on input contents for input items of the past transaction data and generate machine learning steps to generate the input item model data .

Images