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

Abstract

[Problem] In workflow management, when the handling amount changes, customization is performed in response to the change in the workflow. A program for operating a computer 20 including a processor 29 and memories 25 and 26, wherein the program sends information to the processor 29 from a user to a second business partner of the user and the user. a step of accepting input of transaction data regarding a commercial transaction with a second business operator; and a step of generating and presenting workflow information regarding a commercial transaction with a second business operator based on the transaction data by referring to model information; a step of accepting an instruction to change the transaction data and information related to the change from the user; and a step of presenting the changed workflow information to the user when it is determined that it is necessary to change the workflow information based on the information related to the change; A step of accepting an instruction for approving a change in workflow information from a user and changing the workflow information is executed. [Selection diagram] Figure 1

Description

The present disclosure relates to a program, an information processing device, and a method.

As an ERP (Enterprise Resource Planning) package software (often called an integrated core business system, often provided as a cloud-based service), it can be used to manage sales operations, from prospect and inquiry management to quotation, order, sales, billing, and receivables management. There is a sales management system that manages the entire business, and it also has a workflow management function.

As a technology related to the above-mentioned technology, there is a technology disclosed in Patent Document 1.

Patent Document 1 relates to a transaction management system, and a transaction management device of this transaction management system includes a transaction data registration reception unit that receives registration information of transaction data by operation of one of a plurality of business operators; An invitation notification unit that accepts invitation data to invite other businesses; an edit input reception unit that accepts editing input for transaction data; and a change part presentation unit that shows changes in edited content to users other than the user who made the edits. a form data generation unit that generates form data such as estimates, an approval input reception unit that receives approval input for work processes of transaction data, and a transaction data process change unit that advances the work process to the next work process; Equipped with

JP 2021-9505 Publication

When managing transactions (workflow), for example, when the amount of money to be handled changes, the workflow may be changed. Specifically, if the transaction amount exceeds 100,000 yen, the process for approval (approver, attached documents, etc.) may change. Also, the perspective of checking may change. Therefore, the current situation is that troublesome management procedures are required, such as requesting business partners to separate invoices so that the amount does not exceed a predetermined amount.

Therefore, in the present disclosure, a technology that can perform customization corresponding to the change in the workflow when the handling amount changes in workflow management will be described.

According to one embodiment of the present disclosure, a program to be executed by a computer including a processor and a memory is provided. The memory stores format information of forms necessary for the user, who is the first business operator, to carry out business, and workflow model information indicating a work process for creating forms. The program causes the processor to receive, from a user, transaction data relating to a business transaction between the user and a second business partner with which the user does business, and based on the transaction data accepted in the first step. The second step is to generate workflow information related to a commercial transaction with a second business entity by referring to the model information, and present this information. A third step of accepting data change instructions and information related to the change, and determining whether or not it is necessary to change the workflow information generated in the second step based on the information related to the change accepted in the third step. , if it is determined that a change is necessary, a fourth step of presenting the changed workflow information to the user; and accepting an instruction to approve the change of the workflow information from the user who presented the changed workflow information in the fourth step; A fifth step of changing workflow information is executed based on the accepted change approval instruction.

According to the present disclosure, in workflow management, when the handling amount changes, it becomes possible to perform customization corresponding to the change in the workflow.

1 is a diagram showing the overall configuration of a transaction management system 1 according to a first embodiment. FIG. 1 is a block diagram showing a functional configuration of a terminal device 10 that constitutes a transaction management system 1 according to a first embodiment. FIG. 2 is a diagram showing a functional configuration of a server 20 that constitutes the transaction management system 1 of the first embodiment. FIG. 3 is a diagram illustrating an example of a data structure of a transaction database 2021 stored in the server 20 that constitutes the transaction management system 1 of the first embodiment. FIG. 3 is a diagram illustrating an example of a data structure of a form format database 2022 stored in the server 20 that constitutes the transaction management system 1 of the first embodiment. FIG. 3 is a diagram illustrating an example of a data structure of a workflow model information database 2025 stored in the server 20 that constitutes the transaction management system 1 of the first embodiment. FIG. 3 is a diagram illustrating an example of a data structure of a client information database 2027 stored in the server 20 that constitutes the transaction management system 1 of the first embodiment. FIG. 3 is a diagram illustrating an example of a data structure of a user information database 2028 stored in the server 20 that constitutes the transaction management system 1 of the first embodiment. FIG. FIG. 2 is a sequence diagram showing an example of a work process and work status in the transaction management system 1 according to the first embodiment. 2 is a flowchart illustrating an example of a workflow process performed by the transaction management system 1 according to the first embodiment. 11 is a flowchart showing an example of the flow of workflow processing by the transaction management system 1 of the first embodiment, and is a flowchart showing an example of the flow of processing subsequent to the processing shown in FIG. 10. 3 is a diagram showing an example of a screen displayed on the terminal device 10. FIG. 3 is a diagram showing an example of a screen displayed on the terminal device 10. FIG. 3 is a diagram showing an example of a screen of a folder tree displayed on the terminal device 10. FIG. 3 is a diagram showing an example of a screen of a folder tree displayed on the terminal device 10. FIG. 3 is a diagram showing an example of a screen of a folder tree displayed on the terminal device 10. FIG.

Embodiments of the present invention will be described below with reference to the drawings. The following description and drawings are examples for explaining the present invention, and are omitted and simplified as appropriate for clarity of explanation. The present invention can also be implemented in various other forms. Unless specifically limited, each component may be singular or plural.

In the drawings explaining the embodiments, parts having the same functions are denoted by the same reference numerals, and repeated explanations thereof will be omitted.

The position, size, shape, range, etc. of each component shown in the drawings may not represent the actual position, size, shape, range, etc. in order to facilitate understanding of the invention. Therefore, the present invention is not necessarily limited to the position, size, shape, range, etc. disclosed in the drawings.

In the following description, various information may be described using expressions such as "table," "list," and "queue," but various information may be expressed using data structures other than these. "XX table", "XX list", etc. are sometimes referred to as "XX information" to indicate that they do not depend on the data structure. When describing identification information, expressions such as "identification information", "identifier", "name", "ID", and "number" are used, but these expressions can be replaced with each other.

In addition, in the following explanation, the configuration of each table is an example, and one table may be divided into two or more tables, or all or part of two or more tables may be one table. good.

When there are multiple components having the same or similar functions, the same reference numerals may be given different suffixes for explanation. However, if there is no need to distinguish between these multiple components, the subscripts may be omitted in the description.

In addition, in the following explanation, processing performed by executing a program may be explained, but the program is executed by a processor (e.g., CPU, GPU) to perform a predetermined process using storage resources ( Since the processing is performed using a memory (for example, memory) and/or an interface device (for example, a communication port), the main body of the processing may be a processor. Similarly, the subject of processing performed by executing a program may be a controller, device, system, computer, or node having a processor. The main body of the processing performed by executing the program may be an arithmetic unit, and may include a dedicated circuit (for example, FPGA or ASIC) that performs specific processing.

Furthermore, in the following description, a "processor (unit)" refers to one or more processors. The at least one processor is typically a microprocessor such as a CPU (Central Processing Unit), but may be another type of processor such as a GPU (Graphics Processing Unit). At least one processor may be single-core or multi-core.

Furthermore, at least one processor may be a broadly defined processor such as a hardware circuit (for example, an FPGA (Field-Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit)) that performs part or all of the processing.

Furthermore, in the following description, a "memory section" refers to one or more memories, and typically may be a main storage device. At least one memory in the memory section may be a volatile memory or a nonvolatile memory.

A program may be installed on a device, such as a computer, from a program source. The program source may be, for example, a program distribution server or a computer-readable storage medium. When the program source is a program distribution server, the program distribution server includes a processor and a storage resource for storing the program to be distributed, and the processor of the program distribution server may distribute the program to be distributed to other computers. Furthermore, in the following description, two or more programs may be realized as one program, or one program may be realized as two or more programs.

In the present disclosure, a storage device includes one storage drive such as one HDD (Hard Disk Drive) or SSD (Solid State Drive), a RAID device including multiple storage drives, and multiple RAID devices. Furthermore, when the drive is an HDD, it may include, for example, a SAS (Serial Attached SCSI) HDD or an NL-SAS (Nearline SAS) HDD.

Furthermore, in the following description, identification numbers are used as identification information for various objects, but other types of identification information than identification numbers (for example, identifiers containing alphabetic characters or codes) may be employed.

In addition, in the following explanation, when the same type of elements are explained without distinguishing them, reference numerals (or common numerals among the reference numerals) are used, and when the same kind of elements are explained separately, the element An identification number (or reference number) may be used.

In addition, in the following description, control lines and information lines are shown to be necessary for the explanation, and not all control lines and information lines are necessarily shown in the product. All configurations may be interconnected.

<0 System overview>
The transaction management system according to the present disclosure will be described below.

By way of example and not limitation, the transaction management system according to the present disclosure is a system that manages transaction data related to transactions conducted between a user who is a first business operator and a second business operator who is another business operator. , receives at least registration of transaction data from a user, and generates workflow information suitable for the transaction data based on this transaction data, format data of forms and workflow model information registered in advance. Next, if there is a change in the transaction data, the transaction management system accepts the change instruction and change details from the user, determines whether or not to make changes to the workflow information, and if it determines that changes are necessary, changes the workflow information. Make the changes, present them to the user, and get user approval for the changes. Then, when approval for the change is obtained from the user, the workflow information is changed.

Note that the services provided by the transaction management system 1 are not limited to the management of transaction data as described above, but may also be services for general accounting processing related to the user's company or individual business. For example, input transaction data may be used as deposit/withdrawal data, and input of financial data such as owned assets may be accepted to provide accounting processing services for the user's company or individual business.
In the following explanation, an instruction to change transaction data is accepted from the user who is the first business operator, but after inviting the second business operator to the transaction management system, the transaction data will be changed in the same manner as the first business operator. You may accept any change instructions.

In the transaction management system according to the present disclosure, transaction data refers to data regarding commercial transactions between the user and the second business operator. As an example, transaction data may include information on delivered products (product number, model number, , version number, quantity, etc.), transaction information such as various payment information such as business outsourcing fees and purchase of equipment, information on the business partner, item, date of occurrence, transaction amount, etc. The transaction data may be acquired as a history (log) in which the information inputted into the transaction management system by the user when actually conducting a commercial transaction with the second business entity is arranged in chronological order. Further, the transaction data may be created as a file in a certain format on a terminal device that constitutes the transaction management system, and similarly uploaded to a server that constitutes the transaction management system and registered as a system.

Further, in the transaction management system according to the present disclosure, the documents are necessary for the user to perform business based on transaction data. Such documents are well known, and include, for example, an estimate, an order form, a statement of delivery, a receipt, an acceptance statement, and an invoice. There are no particular restrictions on the name or content of documents that are necessary for users to carry out their business based on transaction data, and documents with various names and contents may be managed in the transaction management system related to this disclosure. and can be created.

Further, in the transaction management system according to the present disclosure, the format information of the forms indicates the format of the forms when the forms are created based on the transaction data. As an example, the format information of the form data includes wording information and layout information necessary when creating forms. Specifically, the format information is wording information and layout information necessary to create estimates, purchase orders, and invoices, which are documents created for each work process in the workflow described below. It includes titles such as "Book", "Purchase Order", and "Invoice", fixed phrases, and information that defines the position where items and amounts are written on the form. The format data of this form is used when creating a form as a product of the work process, and the form data is created by applying transaction data such as company name, item, amount, etc. to the format data of this form. .

Furthermore, in the transaction management system according to the present disclosure, a workflow indicates a work process for creating forms. The specific workflow will be explained in detail using diagrams, but as an example, when a user receives an order for a deliverable from a second business, an estimate of the cost of creating the deliverable is created and the estimate is sent to the user. After obtaining approval from the superior, the second business operator instructs the second business operator to create deliverables, including a quotation, and then creates the deliverables and delivers them along with the delivery note. , and issuing an invoice for the costs associated with creating the deliverables. In the transaction management system according to the present disclosure, workflow model information is information indicating what kind of workflow each of the workflows assumed in advance is. The user refers to the model information of the workflows, selects the model information of one of the workflows, and further selects transaction data. The transaction management system according to the present disclosure generates workflow information based on the selected transaction data based on the selection by the user. The workflow information is information indicating a specific workflow suitable for the selected transaction data.

Changes to transaction data may occur after the workflow information is generated. An example is a case where, as a result of careful consideration of the procedure for creating a deliverable, it is necessary to create an estimate that exceeds the initial estimate. The workflow needs to be created based on the first company's internal regulations, and the approver, attached evidence, etc. may change depending on the estimated amount. For example, if there is a company policy that says that if the estimated amount is 100,000 yen or less, it will be approved by the manager, but if the estimated amount exceeds 100,000 yen, it will be approved by the manager up to 10 million yen.The estimated amount will not be changed. In other words, the approval route (i.e. workflow) also needs to be changed. Therefore, when the transaction data is changed, the transaction management system according to the present disclosure accepts the instruction to change the transaction data and the information regarding the change, and changes the workflow information based on the information regarding the change in the transaction data. Determine whether or not.

Then, when the transaction management system according to the present disclosure determines that it is necessary to change the workflow information, it presents the changed workflow information to the user and receives approval from the user for changing the workflow information. Upon accepting the change approval, the transaction management system according to the present disclosure changes the workflow information.

<Embodiment 1>
The transaction management system 1 will be explained 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 the 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 according to the first embodiment. As shown in FIG. 1, the transaction management system 1 includes a plurality of terminal devices (in FIG. 1, a terminal device 10A and a terminal device 10B are shown. Hereinafter, they may be collectively referred to as "terminal devices 10"). , server 20. The terminal device 10 and the server 20 are connected via a network 80 so that they can communicate with each other. The network 80 is configured by a wired or wireless network. In this embodiment, the server 20 is a server that functions as a web server (including a cloud server), and exchanges information with the terminal device 10 via web pages. Further, although a web page browser for viewing web pages is installed in the terminal device 10, a dedicated application for providing the services of the server 20 may be installed and configured to be viewable by the dedicated application. .

The terminal device 10 is a device operated by a user and a person in charge of the second business. In this embodiment, a user is a subject who conducts a commercial transaction with a second business operator, and causes the server 20 to generate various forms of data in connection with the commercial transaction, and the generated form data is transmitted to the second business. This person is a person in charge of a company or a sole proprietor, etc., who communicates with the person. The terminal device 10 is realized by a stationary PC (Personal Computer), a laptop PC, or the like. In addition, the terminal device 10 may be, for example, a tablet compatible with a mobile communication system or a mobile terminal such as a smartphone.

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 corresponding communication device such as a wireless LAN router 82. As shown as a terminal device 10B in FIG. 1, the terminal device 10 includes a communication IF (Interface) 12, an input device 13, an output device 14, a memory 15, a storage section 16, and a processor 19.

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 input operations from a user. The output device 14 is an output device (display, speaker, etc.) for presenting information to the user. The memory 15 is for temporarily storing programs and data processed by the programs, and is a volatile memory such as DRAM (Dynamic Random Access Memory). The storage unit 16 is a storage device for storing data, and is, for example, a flash memory or an HDD (Hard Disc Drive). The processor 19 is hardware for executing a set of instructions written in a program, and is composed of an arithmetic unit, registers, peripheral circuits, and the like.

The server 20 generates workflow information based on instructions from the user who is the owner of the terminal device 10 , generates form data based on this workflow information, and provides the data to the terminal device 10 . The server 20 stores format information of forms and workflow model information. The server 20 also accepts input of transaction data from the user. Then, the server 20 generates workflow information based on the transaction data and model information, and generates form data based on this workflow information.

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 so that the server 20 communicates with external devices. The input/output IF 23 functions as an interface with an input device for receiving input operations from a user and an output device for presenting information to the user. The memory 25 is for temporarily storing programs and data processed by the programs, and is a volatile memory such as DRAM (Dynamic Random Access Memory). The storage 26 is a storage device for storing data, and is, for example, a flash memory or an HDD (Hard Disc Drive). The processor 29 is hardware for executing a set of instructions written in a program, and is composed of an arithmetic unit, 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 FIG. 1. As shown in FIG. 2, the terminal device 10 includes a plurality of antennas (an antenna 111, an antenna 112), a wireless communication section (a first wireless communication section 121, a second wireless communication section 122) corresponding to each antenna, and an operation It includes a reception section 130 (including a keyboard 131 and a mouse 132), a display 150, a storage section 170, and a control section 180. The terminal device 10 also has functions and configurations that are not particularly illustrated in FIG. 2 (for example, a battery for holding power, a power supply circuit that controls the supply of power 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 a radio wave. Further, the antenna 111 receives radio waves from space and provides a received signal to the first wireless communication unit 121.

The antenna 112 radiates a signal emitted by the terminal device 10 as a radio wave. Further, the antenna 112 receives radio waves from space and provides a received signal to the second wireless communication unit 122.

The first wireless communication unit 121 performs modulation and demodulation processing for transmitting and receiving signals via the antenna 111 so that the terminal device 10 communicates with other wireless devices. The second wireless communication unit 122 performs modulation and demodulation processing for transmitting and receiving signals via the antenna 112 so that the terminal device 10 communicates with other wireless devices. The first wireless communication unit 121 and the second wireless 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 wireless communication unit 121 and the second wireless communication unit 122 perform modulation/demodulation and frequency conversion of wireless signals transmitted and received by the terminal device 10 and provide received signals to the control unit 180.

The operation reception unit 130 has a mechanism for accepting user input operations. Specifically, the operation reception unit 130 includes a keyboard 131 and a mouse 132.

The keyboard 131 receives input operations from 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 180 as an input signal.

The mouse 132 receives input operations from the user of the terminal device 10 . The mouse 132 is a pointing device for selecting an object displayed on the display 150, and uses the position information selected on the screen and information indicating that a button is pressed as input signals to the control unit. Output to 180.

The display 150 displays data such as images, videos, and text under the control of the control unit 180. The display 150 is realized by, for example, an LCD (Liquid Crystal Display) or an organic EL (Electro-Luminescence) display. Note that the display 150 is a touch screen that detects the position of the user's touch on the touch panel by using, for example, a capacitive touch panel, and may be configured to include functions such as the above-mentioned keyboard.

The storage unit 170 includes a memory 15 such as a flash memory, and a storage unit 16, and stores data and programs used by the terminal device 10. In one aspect, storage unit 170 stores transaction data 1701.

Transaction data 1701, as described above, is data regarding commercial transactions between the user and the second business operator. Details of the transaction data will be described later.

The control unit 180 is configured by the processor 19, for example, and controls the operation of the terminal device 10 by reading a program stored in the storage unit 170 and executing instructions included in the program. The control unit 180 operates according to a program, which is an application installed in the terminal device 10 in advance (stored in the storage unit 170), for example, to control the input operation reception unit 1801, the transmission/reception unit 1802, and the data processing unit. 1803 and functions as a notification control unit 1804.

The input operation reception unit 1801 performs a process of accepting a user's input operation on an input device such as the keyboard 131.

The transmitting/receiving unit 1802 performs processing for the terminal device 10 to transmit and receive data with an external device such as the server 20 according to a communication protocol.

The data processing unit 1803 performs calculations on the data input by the terminal device 10 according to a program, and outputs the calculation results to a memory or the like.

The notification control unit 1804 performs a process of presenting information to the user. The notification control unit 1804 performs processes such as displaying a display image on the display 150 and outputting audio to a speaker (not shown).

<1.2 Functional configuration of server 20>
FIG. 3 is a diagram showing the functional configuration of the server 20 that constitutes the transaction management system 1 of FIG. 1. 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 external devices.

The storage unit 202 includes, for example, a memory 25 and a storage 26, and stores data and programs used by the server 20. The storage unit 202 stores a transaction database (DB) 2021, a form format DB 2022, fixed text data 2023, form layout data 2024, a workflow (WF) model information DB 2025, a WF model data 2026, a client information DB 2027, a user information DB 2028, etc. Remember.

The transaction DB 2021 is a database for managing transaction data regarding commercial transactions between the user and the second business operator. The transaction DB 2021 preferably stores a plurality of transaction data. Details will be described later.

The form format DB 2022 is a database for managing format information of forms necessary for the user to perform business. The form format DB 2022 preferably stores format information of a plurality of forms. Details will be described later.

The fixed text data 2023 is text data that forms part of the format information and serves as a template for sentences written on forms. In the server 20 according to the present disclosure, a plurality of fixed phrase data 2023 may be stored in the storage unit 202. Note that there is no particular limitation on the data format of the files that constitute the fixed phrase data 2023, and the data format may be a text format or another data format.

Form layout data 2024 is data that defines a position in which text data included in the above-described fixed text data 2023, data included in transaction data, etc. are written on a form, which forms part of the format information. In the server 20 according to the present disclosure, a plurality of form layout data 2024 may be stored in the storage unit 202. Note that there is no particular limitation on the data format of the files that constitute the form layout data 2024, and any known data format that can describe the location of data, such as XML (eXtensible Markup Language) format, can be suitably applied. It is.

The WF model information DB 2025 is a database for managing workflow model information. The WF model information DB 2025 preferably stores model information of a plurality of workflows. Details will be described later.

The WF model data 2026 is workflow model data that constitutes workflow model information. Workflow model data is data that describes the individual work steps that make up the workflow and the chronological context of these work steps. In the server 20 according to the present disclosure, a plurality of WF model data 2026 may be stored in the storage unit 202. Note that there are no particular limitations on the data format of the files that make up the WF model data 2026, and any known data format that can describe the order of data, such as JSON (JavaScript Object Notation) (JavaScript is a registered trademark) format, may be used. is suitably applicable.

The client information DB 2027 contains information on the second business operator, specifically information such as information for identifying the second business operator (client ID), name (company name) of the second business operator, and second corporate number. It is a database for holding the. The client information DB 2027 is created in advance by the user and stored in the storage unit 202. Details will be described later.

The user information DB 2028 is data for holding information on users who use the transaction management system, specifically information for identifying the user (user ID), user's name, affiliation, and other information. The user information DB 2028 is created in advance by the user and stored in the storage unit 202. Details will be described later.

The control unit 203 has a reception control module 2031, a transmission control module 2032, a transaction data acquisition module 2033, a workflow information generation module 2034, a change part acceptance module 2035, It performs the functions shown in the workflow information change module 2036, the form data generation module 2037, and the transaction data process change module 2038.

The reception control module 2031 controls the process by which the server 20 receives signals from an external device according to a communication protocol.

The transmission control module 2032 controls the process by which the server 20 transmits a signal to an external device according to a communication protocol. These reception control module 2031 and transmission control module 2032 provide a function for the server 20 to operate as a Web server for external devices including the terminal device 10 accessed via the network 80.

The transaction data acquisition module 2033 receives the transaction data via the communication unit 201 because the terminal device 10 is operated by the user who is the first business operator and registration information of the transaction data is transmitted. The transaction data acquisition module 2033 stores the received transaction data in the transaction DB 2021.

The workflow information generation module 2034 identifies the transaction data acquired by the transaction data acquisition module 2033 and stored in the transaction DB 2021 (selects any one transaction data if there is a plurality of transaction data in the transaction DB 2021), and selects one of the transaction data. Identify the model information of the workflow that should be applied to the data from the WF model information DB 2025 (select the model information of one workflow if there is model information of multiple workflows), and use the model information of the identified workflow. , to generate workflow information. Then, the workflow information generation module 2034 temporarily stores the generated workflow information in the storage unit 202 and presents the workflow information to the user.

The method by which the workflow information generation module 2034 selects the workflow model information stored in the WF model information DB 2025 is arbitrary, and may be appropriately selected from known methods. One example is a method in which the workflow information generation module 2034 refers to information regarding the second business entity included in the transaction data and selects workflow model information specific to the second business entity. Furthermore, if the transaction data includes item data related to commercial transactions, the workflow information generation module 2034 may select workflow model information specific to this item. Furthermore, the storage unit 202 is provided with training data that describes the relationship between various information included in the transaction data and workflow model information, and this training data is used to generate a learning model, and the workflow information generation module 2034 However, one example is a method of inputting transaction data into this learning model and acquiring workflow model information as an inference result of the learning model.

Further, there is no particular limitation on the method of presenting the workflow information generated by the workflow information generation module 2034 to the user. As an example, the workflow information generation module 2034 generates data for generating a screen on the display 150 of the terminal device 10 used by the user, including a diagram of the workflow using a technique such as a sequence diagram or a state transition diagram. , a method of displaying this data on the display 150 of the terminal device 10 can be cited. Alternatively, there is a method in which the work steps constituting the workflow are shown as boxes, data for generating a screen showing the connection state of the boxes is generated, and this data is displayed on the display 150 of the terminal device 10.

The change part acceptance module 2035 allows a user who has confirmed the workflow information presented by the workflow information generation module 2034 to input an instruction to change transaction data and information related to the change via the terminal device 10 owned by this user. Once done, accept instructions to change this transaction data and information regarding the change.

As an example, in the workflow information generated by the workflow information generation module 2034, the transaction data was a commercial transaction of 100,000 yen, but after examining the estimated amount, it was found that it had been changed to a commercial transaction of 110,000 yen. Here are some cases. Assume that for a company that is a user and a user belonging to this company, commercial transactions over 100,000 yen are approved by the general manager rather than the section manager. Due to the change in the estimated amount, a work process for department manager approval will be added after the section manager approval in the workflow. Therefore, the user inputs into the server 20 via the terminal device 10 that the estimated amount will be changed from 100,000 yen to 110,000 yen (the amount change is also information) in the transaction data, and the changed part acceptance module 2035 Changes to this transaction data and information related to the changes (such as that the estimated amount has become 110,000 yen) are accepted.

Other examples of changes in transaction data include changing the person in charge of the second business partner, changing the position of the person in charge, and changing item data.

Then, the change part acceptance module 2035 stores the accepted and changed transaction data in the transaction DB 2021, and notifies the workflow information change module 2036 that it should consider changing the workflow information in accordance with the change in the transaction data. do.

When the change part acceptance module 2035 accepts the change in transaction data, the workflow information change module 2036 updates the workflow information generated by the workflow information generation module 2034 based on the contents of the changed transaction data (information related to the change). Determine whether changes are necessary. If the workflow information change module 2036 determines that the workflow information needs to be changed, it presents the changed workflow information to the user.

As a method for the workflow information change module 2036 to determine whether or not the workflow information has been changed, a well-known technique can be suitably applied. One example is a method in which the workflow information change module 2036 has a rule-based DB, and the determination is made based on this rule-based DB. Specifically, in the rule-based DB, a rule is registered that if the estimated amount exceeds 100,000 yen, the approval route will be changed from section manager approval to general manager approval, and in the above example, the estimated amount exceeded 100,000 yen, it was determined that it was necessary to change the workflow information according to this rule, and the changed workflow information (in this case, the information related to the change in workflow from section manager approval to general manager approval) was determined to be necessary. Present to the user. At this time, the workflow information change module 2036 refers to various information of the second business operator and/or user stored in the client information DB 2027 and/or user information DB 2028 to determine whether or not the workflow information has been changed. You may.

In addition, training data describing the relationship between changed transaction data and changed workflow information is prepared in the storage unit 202, a learning model is generated using this training data, and the workflow information change module 2036 One example is a method in which, by inputting changed transaction data into this learning model, information on the changed workflow is obtained as an inference result of the learning model and presented to the user.

Furthermore, there is no particular limitation on the method of presenting the workflow information modified by the workflow information modification module 2036 to the user. As an example, the workflow information change module 2036 generates data for generating a screen on the display 150 of the terminal device 10 used by the user, including a diagram of the workflow using a technique such as a sequence diagram or a state transition diagram. , a method of displaying this data on the display 150 of the terminal device 10 can be cited. Alternatively, there is a method in which the work steps constituting the workflow are shown as boxes, data for generating a screen showing the connection state of the boxes is generated, and this data is displayed on the display 150 of the terminal device 10.

In this way, it is preferable that the workflow information change module 2036 presents the changed workflow information to the user in a visually recognizable manner. At this time, it is preferable that the workflow information change module 2036 allows the user to easily understand the changed part by highlighting the changed part, displaying it in a pop-up display, displaying it blinking, or the like. Furthermore, it is preferable that the workflow information change module 2036 similarly allows the user to easily understand the changed portion by displaying the changed portion in a balloon.

Next, the workflow information change module 2036 accepts an instruction to approve changes to workflow information from the user who presented the changed workflow information, and changes the workflow information based on the accepted approval instruction. At this time, it is preferable to present the changed workflow information to the user as the final change result.

At this time, if you accept an instruction from the user that you do not approve (non-approve) at least part of the changes to the workflow information, the workflow model information itself will be changed based on the accepted non-approval instruction. change.

Specifically, the user approves changes to workflow information and workflow model information for a specific second business operator, but for a second business operator other than this specific second business operator. may accept instructions to disapprove changes to workflow information. In this case, the changed workflow model information becomes workflow model information that is applicable only to the specific second business operator.

Similarly, the user approves the change of the workflow model information as well as the change of the workflow information, but the workflow model information can only be changed during a specific period (for example, in the closing months such as March and September). It may be possible to accept instructions that apply only to In this case, the changed workflow model information becomes workflow model information that is applicable only at a specific time.

Note that the workflow information changing module 2036 is not limited to the example described above, and may change the workflow model information as well as the workflow information.

The form data generation module 2037 generates form data, such as estimate data, purchase order data, and invoice data, which are created as deliverables for each of a plurality of work processes. In the format data of the form data stored in the form format DB 2022, titles and fixed phrases such as "estimate," "purchase order," and "invoice" are already set, and the positions where items and amounts are written on the form are already set. is defined, variable data such as item and amount data of transaction data stored in the transaction DB 2021 is applied to this form format data to generate form data. Further, the form data generation module 2037 transmits the generated form data to the terminal device 10 for display.

<2 Data structure>
FIG. 4 is a diagram showing an example of the data structure of the transaction DB 2021 stored in the server 20 of FIG. FIG. 5 is a diagram showing an example of the data structure of the form format DB 2022 stored in the server 20 of FIG. FIG. 6 is a diagram showing an example of the data structure of the WF model information DB 2025 stored in the server 20 of FIG. FIG. 7 is a diagram showing an example of the data structure of the client information DB 2027 stored by the server 20 in FIG. FIG. 8 is a diagram showing an example of the data structure of the user information DB 2028 stored by the server 20 in FIG.

As shown in Figure 4, each record in the transaction DB 2021 includes an item "transaction ID", an item "supplier ID", an item "item", an item "occurrence date", and an item "product number". , the item "Quantity", the item "Amount", the item "Status", the item "Date of change", etc.

The item “transaction ID” is information that identifies transaction data managed by the transaction management system 1.

The item “Business Partner ID” is information that identifies the second business entity that is the business partner of the user (first business entity) who is the administrator of the transaction management system 1.

The item "item" is information indicating the item of goods and services traded in the commercial transaction related to the transaction data identified by the item "transaction ID."

The item "date of occurrence" is information indicating the date of occurrence of the commercial transaction related to the transaction data identified by the item "transaction ID."

The item "product number" is information indicating the product number of the product or service traded in the commercial transaction related to the transaction data identified by the item "transaction ID." Note that if the transaction object is a service, there is no concept of product number, so the item "Product number" will be blank.

The item "Quantity" is information indicating the quantity of goods and services traded in the commercial transaction related to the transaction data identified by the item "Transaction ID." Note that if the transaction object is a service, there is no concept of quantity, so the item "Quantity" will be blank.

The item "amount" is information indicating the amount of goods and services traded in the commercial transaction related to the transaction data identified by the item "transaction ID."

The item "Status" is information indicating the status of the commercial transaction related to the transaction data identified by the item "Transaction ID."

The item "change date" is information indicating the change date of the transaction data identified by the item "transaction ID." As seen in the item "amount", the transaction DB 2021 can record the change history of transaction data.

As shown in FIG. 5, each record in the form format DB 2022 includes an item "form ID", an item "form name", an item "format text data", an item "form format data", and so on.

The item “form ID” is information that identifies the form format managed by the transaction management system 1.

The item "form name" is information indicating the name of the form related to the form format identified by the item "form ID."

The item "Standard text data" is information indicating the file name of the fixed text data 2023 related to the form format identified by the item "Form ID."

The item "Format data" is information indicating the file name of the form layout data 2024 related to the form format identified by the item "Format ID."

In FIG. 5, the extension of the fixed text data 2023 is shown as text, and the extension of the form layout data 2024 is shown as XML, but the formats of these data are not limited to the illustrated example.

As shown in FIG. 6, each record of the WF model information DB 2025 includes an item "WF model ID", an item "WF model data", and the like.

The item “WF model ID” is information that identifies model information of a workflow managed by the transaction management system 1.

The item "WF model data" is information indicating the name of the WF model data 2026 related to the model information of the workflow identified by the item "WF model ID."

Note that although the extension of the WF model data 2026 is shown in the JSON format in FIG. 6, the format of these data is not limited to the illustrated example.

As shown in FIG. 7, each record in the client information DB 2027 includes the item "client ID", the item "company name", the item "corporate number", the item "address", the item "contact information", and the item Including "industry" etc.

The item “Client ID” is information that identifies the second business entity that is the business partner of the user (first business entity) who is the administrator of the transaction management system 1, and This is common to "ID".

The item "Name" is information indicating the corporate name or individual name of the second business entity identified by the item "Client ID."

The item “Corporate Number” is information indicating the corporate number of the second business operator identified by the item “Client ID”.

The item "address" is information indicating the address of the second business entity identified by the item "client ID."

The item "contact information" is information indicating the contact information of the person in charge of the transaction in the second business entity identified by the item "client ID."

The item “industry” is information indicating the industry of the corporation that is the second business entity identified by the item “client ID”.

As shown in FIG. 8, each record in the user information DB 2028 includes the item "user ID", the item "name", the item "affiliation", the item "post", the item "approval authority", and the item " ``Approval authority amount'', item ``email address'', item ``password'', etc. In the user information DB 2028 shown in FIG. 8, it is assumed that the first business entity that uses the transaction management system 1 has a plurality of users (individual units). In this specification, a "user" as a company (corporation) and a "user" as an employee of a company are not particularly distinguished, and both are described as a "user."

The item “user ID” is information for identifying individual users who are administrators and users of the transaction management system 1.

The item "Name" is information indicating the name of the user identified by the item "User ID."

The item "Affiliation" is information indicating the name of the organization to which the user identified by the item "User ID" belongs.

The item "post" is information indicating a post such as a position in the organization name of the organization to which the user identified by the item "user ID" belongs. Note that the item "post" may store not only information indicating a specific post name, but also more abstract information such as position, rank, and title.

The item "approval authority" is information indicating the user's approval authority in the company to which the user identified in the item "user ID" is assigned in the transaction management system 1 according to the present disclosure or to which the user belongs. Note that in FIG. 8, "applicant" is not information indicating decision-making authority, but information "applicant" is stored as information indicating the applicant who is the starting point of the workflow.

The item “approval authority” is information indicating the upper limit amount for the approval authority assigned to the user identified by the item “user ID”.

The item "email address" is information indicating the in-house email address of the user identified by the item "user ID."

The item "password" is information indicating a password (pre-registered) used when logging into the transaction management system 1 according to the present disclosure, of the user identified by the item "user ID." The user logs in to the transaction management system 1 (more specifically, to the server 20) according to the present disclosure using the items "email address" and "password".

<3 Operation>
Hereinafter, workflow processing by the transaction management system 1 in the first embodiment will be described with reference to FIGS. 9 to 11.

FIG. 9 is a sequence diagram illustrating an example of work steps and work status in the transaction management system 1 according to the present disclosure. The work process and work status managed by transaction data in the present disclosure will be described using FIG. 9 . Note that the work process here refers to the "estimate stage," "ordering stage," and "billing stage," which indicate the stages of a transaction in a business operator, and the work status indicates the "creation stage," which indicates the status of each business operator's work process. "Confirming", "Confirming", "Waiting", etc., and are registered for each of a plurality of businesses, for example.

First, the first business operator, which is the orderer, registers transaction data. At this time, the number of the second business entity that is the order recipient is not limited to one company.

At this time, as shown in FIG. 9, the work process of the registered transaction data is in the estimation stage, the work status of the user who is the order taker is in the process of creating an estimate in step S901, and the work status of the user who is the orderer is in the estimation stage. waits for an estimate in step S902. When the order taker creates an estimate and sends it to the orderer, the orderer's work status changes to confirming the estimate in step S903, and the order taker's work status changes to waiting for estimate confirmation in step S904. When the orderer approves the contents of the quotation, the work status of the contractor becomes "estimated" in step S905.

Next, the transaction data work process becomes an ordering stage, and the work status of the orderer becomes in the process of creating an order in step S906. When the orderer creates an order and sends it to the orderer, the orderer's work status becomes order confirmation in step S907, and the orderer's work status becomes waiting for order confirmation in step S908. When the order taker approves the order contents, the order taker's work status changes to "order completed" in step S909, and the orderer's work status changes to "order completed" in step S910. After this, the actual product delivery and outsourcing operations related to the transaction are performed.

When the actual product delivery and work related to outsourcing related to the transaction are completed, the work process of the transaction data changes to the billing stage, the work status of the contractor becomes invoice creation in step S911, and the work status of the orderer changes to step S911. Waiting for billing in S912. When the orderer creates a bill and sends it to the orderer, the orderer's work status changes to confirming the billing details in step S913, and the orderer's work status changes to waiting for billing confirmation in step S914. When the orderer approves the billing details, the ordering party's work status changes to billed in step S915, and the ordering party's work status changes to billing confirmed in step S916. After this, the actual payment is made and the transaction is completed. In the transaction management system 1, changes and management of work processes and work statuses as described above are performed. Note that the above work processes and work statuses are merely examples, and are not limited thereto.

FIG. 10 is a flowchart illustrating an example of a workflow process performed by the transaction management system 1 according to the present disclosure.

As the process in step S1000, the server 20 performs user authentication in order to provide the user with the transaction data itself, the work process and work status of the transaction data, and accounting services including these by the transaction management system 1. Therefore, a request is made to the user to input account information and a password, and user authentication is performed by checking whether the input information matches registered information. If they match, you are logged into the server 20.

As the process in step S1001, the transaction data registration information is transmitted by the operation of the operation reception unit 130 of the terminal device 10, so the transaction data acquisition module 2033 of the server 20 receives the transaction data via the communication unit 201. It will be done. The accepted transaction data is stored in the transaction DB 2021. In addition to (individual) input of transaction data via the terminal device 10, the user can operate the terminal device 10 to generate a transaction data file in advance and send this transaction data file to the server 20. Transaction data may be registered in 20.

In step S1002, the workflow information generation module 2034 of the server 20 generates workflow information based on the transaction data registered in step S1001, and in step S1003, the workflow information generation module 2034 generates the workflow information generated in step S1002. is presented to the user. Preferably, the workflow information generation module 2034 transmits information for displaying the generated workflow information on the display 150 of the user's terminal device 10 to the terminal device 10, and based on this information, displays the workflow information on the display 150. Display such a screen.

As processing in step S1004, the control unit 203 of the server 20 registers a work status for the transaction data registered in step S1001. For example, if the work process of transaction data is registered as the quotation stage, and the registered user is the order taker, the work status of the user is registered as being in the process of creating an estimate (work in progress), and if the user is the orderer, the work status of the user is is stored in the transaction DB 2021 as waiting for an estimate.

In step S1005, the change part acceptance module 2035 of the server 20 allows the user who has confirmed the workflow information presented by the workflow information generation module 2034 in step S1003 to transfer transaction data via the terminal device 10 owned by this user. It waits for the change instruction and information related to the change to be input (YES in step S1005), and when the change instruction is accepted, the transaction data change instruction and information related to the change are accepted. In the flowchart shown in Figure 10, it is supposed to wait for an instruction to change the transaction data before moving to the next step, but if there is an instruction for no change (this can also be called an instruction to change the transaction data) ) before moving to the next step.

In step S1006, the workflow information change module 2036 of the server 20 updates the workflow information generated by the workflow information generation module 2034 in step S1002 based on the change in transaction data and the information related to the change accepted by the change part acceptance module 2035 in step S1005. Determine whether it is necessary to change the information. If it is determined that the workflow information needs to be changed (YES in step S1006), the program proceeds to step S1007, and if it is determined that the workflow information is not necessary to be changed (NO in step S1006), the program proceeds to step S1102. Proceed to.

In step S1007, the workflow information change module 2036 of the server 20 determines that the workflow information needs to be changed, and therefore presents the changed workflow information to the user. Preferably, the workflow information change module 2036 transmits information for displaying the changed workflow information on the display 150 of the user's terminal device 10 to the terminal device 10, and based on this information, the workflow information is displayed on the display 150. Display the screen related to the change.

In step S1100, the workflow information change module 2036 of the server 20 allows the user who has confirmed the change in the workflow information presented by the workflow information change module 2036 in step S1006 to make a transaction via the terminal device 10 owned by this user. The input of information related to whether or not the data change is approved is accepted, and if the accepted information is information related to the approval of the change (YES in step S1100), the program proceeds to step S1101, and the accepted information does not approve the change. If the information is (NO in step S1100), the program proceeds to step S1102.

In step S1101, the workflow information change module 2036 changes the workflow information based on the accepted approval instruction. At this time, the workflow information change module 2036 presents the changed workflow information to the user as the final change result.

As the process of step S1102, the form data generation module 2037 applies the item and amount data of the transaction data stored in the transaction DB 2021 to the format data of the form data stored in the form format DB 2022, and generates the form data. is generated. The generated form data is, for example, an estimate, a purchase order, or an invoice.

As processing in step S1103, the control unit 203 of the server 20 registers the work status of the progressed work process. For example, when the work process is registered as an ordering stage, the work status of the orderer is registered in the transaction DB 2021 as being in the process of creating an order (work in progress). Further, when the work process is registered as a billing stage, the work status of the contractor is registered in the transaction DB 2021 as billing creation (in progress), and the orderer's work status is registered in the transaction DB 2021 as waiting for billing. This automatically updates the work process and work status, making it possible to manage transaction data appropriately.

<4 Screen example>
Hereinafter, examples of screens for workflow processing by the transaction management system 1 will be described with reference to FIGS. 12 to 16.

FIG. 12 is a diagram showing an example of a login screen 1200 displayed on the display 150 of the terminal device 10. Since the user operates the terminal device 10 to access the server 20, the URL of the login screen is transmitted according to an instruction from the server 20, and the login screen is displayed. Alternatively, a login screen is displayed according to an instruction from an application installed on the terminal device 10 in advance. Through these operations, a login screen 1200 as shown in FIG. 12 is displayed on the display 150 of the terminal device 10.

When a login screen 1200 as shown in FIG. 12 is displayed on the display 150 of the terminal device 10, the user operates the operation reception unit 130 to fill in the account input field 1201 and the password input field provided on the login screen 1200. In 1202, the user inputs his/her own account information (email address in this embodiment) and password. Thereafter, by pressing the login button 1203, user authentication is performed and the user is logged into the server 20.

FIG. 13 is a diagram showing an example of a transaction data input screen 1300 displayed on the display 150 of the terminal device 10. After user authentication is performed by the server 20 and the user logs in to the server 20, when inputting transaction data is selected by selecting a menu or a tab, a transaction data input screen 1300 shown in FIG. 13 is displayed on the display 150 of the terminal device 10. The information is then entered into a state where it can be input by operating the operation reception unit 130.

When the transaction data input screen 1300 as shown in FIG. , business partner input field 1302, etc., information such as business partner information (company name and name of sole proprietor), item, account item, date of occurrence, amount, etc., related to the transaction data is input into various input fields such as business partner input field 1302. Thereafter, by pressing the registration button 1303, transaction data is registered in step S1001.

FIG. 14 is a diagram showing an example of a screen of workflow information displayed on the terminal device 10. The screen example in FIG. 14 shows a screen example in which workflow information generated by the workflow information generation module 2034 of the server 20 and transmitted to the terminal device 10 is displayed. This corresponds to step S1003 in FIG.

As shown in FIG. 14, a window 1400 is displayed on the display 150 of the terminal device 10, and this window 1400 displays workflow information 1401 generated by the workflow information generation module 2034 and sent to the terminal device 10. ing. In the example shown in FIG. 14, each work process (for example, creating an estimate) making up the workflow is displayed as a box 1402, and the flow of each work process is displayed as an arrow 1403.

FIG. 15 is a diagram showing an example of a screen displayed on the terminal device 10 with information about workflows that are determined to need to be changed due to changes in transaction data. The example screen in FIG. 15 shows an example of a screen in which information about a workflow requesting consent for change, which is generated by the workflow information change module 2036 of the server 20 and sent to the terminal device 10, is displayed. This corresponds to step S1007 in FIG.

As shown in FIG. 15, a window 1500 is displayed on the display 150 of the terminal device 10, and this window 1500 includes a message requesting approval for the change generated by the workflow information change module 2036 and sent to the terminal device 10. Workflow information 1501 is displayed. In the example shown in FIG. 15, a speech bubble 1502 is displayed at a change location where approval for the change should be obtained, superimposed on the workflow information 1501 shown in FIG. This balloon 1502 displays an area 1503 in which the reason for obtaining approval for the change is written, and buttons 1504 and 1505 that the user operates to input whether or not to approve the change. The user operates the operation reception unit 130 of the terminal device 10 and inputs an operation by pressing down on one of the buttons 1504 and 1505, thereby instructing the server 20 whether or not to approve the change.

FIG. 16 is a diagram showing an example of a screen of workflow information that is changed due to a change in transaction data, which is displayed on the terminal device 10. The screen example in FIG. 16 shows a screen example in which changed workflow information generated by the workflow information change module 2036 of the server 20 and transmitted to the terminal device 10 is displayed. This corresponds to step S1101 in FIG.

As shown in FIG. 16, a window 1600 is displayed on the display 150 of the terminal device 10, and this window 1600 contains information on the changed workflow generated by the workflow information change module 2036 and sent to the terminal device 10. 1601 is displayed. In the example shown in FIG. 16, a changed portion 1602 is displayed as a dotted line superimposed on the workflow information 1401 shown in FIG.

<5. Summary＞
As described above, according to the present embodiment, when there is a change in transaction data, when the change in transaction data is input to the server 20, the workflow information change module 2036 of the server 20 determines whether or not the workflow information has changed. If it is determined that a change is necessary, the user is asked to consent to the change, and if the user consents to the change, the workflow information is changed. As a result, in workflow management, when the handling amount changes, it becomes possible to customize the workflow in accordance with the change.

<6. Additional notes>
Note that the configurations of the embodiments described above are explained in detail in order to explain the present disclosure in an easy-to-understand manner, and the embodiments are not necessarily limited to those having all of the configurations described. Furthermore, it is possible to add, delete, or replace a part of the configuration of each embodiment with other configurations.

Further, each of the above-mentioned configurations, functions, processing units, processing means, etc. may be partially or entirely realized in hardware by designing, for example, an integrated circuit. Further, the present invention can also be realized by software program codes that realize the functions of the embodiments. In this case, a storage medium on which a program code is recorded is provided to a computer, and a processor included in the computer reads the program code stored on the storage medium. In this case, the program code itself read from the storage medium realizes the functions of the embodiments described above, and the program code itself and the storage medium storing it constitute the present invention. Storage media for supplying such program codes include, for example, flexible disks, CD-ROMs, DVD-ROMs, hard disks, SSDs, optical disks, magneto-optical disks, CD-Rs, magnetic tapes, and non-volatile memory cards. , ROM, etc. are used.

Furthermore, the program code that implements the functions described in this embodiment can be implemented using a wide range of program or script languages, such as assembler, C/C++, Perl, Shell, PHP, and Java (registered trademark).

Furthermore, by distributing the software program code that realizes the functions of the embodiment via a network, it can be stored in a storage means such as a computer's hard disk or memory, or a storage medium such as a CD-RW or CD-R. Alternatively, a processor included in the computer may read and execute the program code stored in the storage means or the storage medium.

The matters described in each of the above embodiments are additionally described below.

(Additional note 1)
A program for operating a computer (20) comprising a processor (29) and a memory (25, 26), wherein the memory (25, 26) contains a program for a user who is a first business operator to carry out business. Format information (2022) of forms necessary for this purpose, and workflow model information (2025, 2026) indicating the work process for creating forms are stored, and the program sends information from the user to the processor (29). , a first step (S1001) that accepts the input of transaction data (2021) regarding a commercial transaction between the user and a second business entity that is a business partner of the user; 2021), a second step (S1002, S1003) of generating workflow information related to the commercial transaction with the second business operator by referring to the model information (2025, 2026) and presenting this information; A third step (S1005) that accepts an instruction to change transaction data (2021) and information related to the change from the user who presented the workflow information in the second step (S1002, S1003); Based on the information related to the change, it is determined whether or not the workflow information generated in the second step (S1002, S1003) needs to be changed, and if it is determined that the change is necessary, the changed workflow information is presented to the user. Step 4 (S1006, S1007) to accept an instruction to approve the change in workflow information from the user who presented the workflow information changed in the fourth step (S1006, S1007), and receive an instruction to approve the accepted change. A program that executes a fifth step (S1100, S1101) of changing workflow information based on.
(Additional note 2)
In the fifth step (S1100, S1101), from the user who presented the workflow information changed in the fourth step (S1006, S1007), an unapproved instruction regarding at least part of the change in the workflow information is accepted, and the accepted change The program according to supplementary note 1, which changes model information (2025, 2026) based on an unauthorized instruction.
(Additional note 3)
There are multiple second business operators, and in the fifth step (S1100, S1101), the user who presented the workflow information changed in the fourth step (S1006, S1007) requests that at least part of the changes in the workflow information be made. The program according to supplementary note 2, which accepts an unapproved instruction and changes the model information (2025, 2026) about a specific second business operator based on the unapproved instruction of the accepted change.
(Additional note 4)
In the fifth step (S1100, S1101), from the user who presented the workflow information changed in the fourth step (S1006, S1007), an unapproved instruction regarding at least part of the change in the workflow information is accepted, and the accepted change The program according to appendix 2 or 3, which changes model information (2025, 2026) related to commercial transactions for a specific period based on an unauthorized instruction of.
(Appendix 5)
In the fourth step (S1006, S1007), the information on the changed workflow is presented in a visible state to the user, and at this time, the part of the information related to the workflow that is related to the change is highlighted. The program described in Crab.
(Appendix 6)
In the fourth step (S1006, S1007), the information on the changed workflow is presented in a visible state to the user, and at this time, the part of the information related to the workflow that is related to the change is displayed in a balloon. The program described in Crab.
(Appendix 7)
The program according to any one of appendices 1 to 6, further causes the program to execute a sixth step of presenting the user with information on the workflow changed in the fifth step (S1100, S1101).
(Appendix 8)
An information processing device (20) comprising a processor (29) and a memory (25, 26), the memory (25, 26) containing information necessary for a user who is a first business operator to carry out business. Format information (2022) of various forms and workflow model information (2025, 2026) indicating the work process of creating forms are stored, and the processor (29) receives information from the user from the user's business partner. A first step (S1001) of accepting input of transaction data (2021) regarding a commercial transaction between a second business operator and a user, and based on the transaction data (2021) accepted in the first step (S1001), A second step (S1002, S1003) of generating workflow information related to a commercial transaction with a second business operator by referring to model information (2025, 2026) and presenting this information; A third step (S1005) in which an instruction to change the transaction data (2021) and information related to the change are accepted from the user who presented the workflow information in S1003), and information related to the change accepted in the third step (S1005). Based on this, it is determined whether or not it is necessary to change the workflow information generated in the second step (S1002, S1003), and if it is determined that a change is necessary, a fourth step (S1006) is to present the changed workflow information to the user. , S1007) and the user who presented the workflow information changed in the fourth step (S1006, S1007). An information processing device (20) that executes a fifth step (S1100, S1101) of changing information.
(Appendix 9)
A method carried out by a computer (20) comprising a processor (29) and a memory (25, 26), the memory (25, 26) containing information for a user who is a first business operator to carry out business. Format information (2022) of forms necessary for this purpose and workflow model information (2025, 2026) indicating the work process for creating forms are stored, and the processor (29) receives information from the user from the user. A first step (S1001) that accepts the input of transaction data (2021) regarding a commercial transaction between a second business partner, which is a business partner of the user, and the transaction data (2021) accepted in the first step (S1001). a second step (S1002, S1003) of generating workflow information related to a commercial transaction with a second business operator based on the model information (2025, 2026) and presenting this information; A third step (S1005) that accepts an instruction to change the transaction data (2021) and information related to the change from the user who presented the workflow information in (S1002, S1003); Based on the information, it is determined whether or not it is necessary to change the workflow information generated in the second step (S1002, S1003), and if it is determined that the change is necessary, a fourth step is to present the changed workflow information to the user. Steps (S1006, S1007) and the user who presented the workflow information changed in the fourth step (S1006, S1007) accept an instruction to approve the change in workflow information, and based on the accepted instruction to approve the change, , a fifth step (S1100, S1101) of changing workflow information.

1 transaction management system, 10 10A 10B terminal device, 20 server, 25 memory, 29 processor, 30 storage device, 80 network, 150 display, 170 storage section, 180 control section, 202 storage section, 203 control section, 2021 transaction DB, 2022 Form format DB, 2023 Fixed text data, 2024 Form layout data, 2025 WF model information DB, 2026 WF model data, 2027 Client information DB, 2028 User information DB, 2031 Reception control module, 2032 Transmission control module, 2033 Transaction data acquisition Module, 2034 Workflow information generation module, 2035 Change part acceptance module, 2036 Workflow information change module, 2037 Form data generation module, 2038 Transaction data process change module

Claims (9)

A program for operating a computer equipped with a processor and a memory,
The memory stores format information of forms necessary for a user who is a first business operator to carry out business, and workflow model information indicating a work process for creating the forms;
The program causes the processor to:
a first step of accepting input from the user of transaction data regarding a commercial transaction between the user and a second business entity that is a business partner of the user;
A second step of generating information on the workflow related to the commercial transaction with the second business operator by referring to the model information based on the transaction data accepted in the first step, and presenting this information. and,
a third step of accepting an instruction to change the transaction data and information related to the change from the user who presented the workflow information in the second step;
Based on the information related to the change accepted in the third step, it is determined whether or not it is necessary to change the information of the workflow generated in the second step, and if it is determined that the change is necessary, the changed workflow information is changed. a fourth step of presenting information to the user;
A step of accepting an instruction to approve changes to the workflow information from the user who presented the workflow information changed in the fourth step, and changing the workflow information based on the accepted instruction to approve the changes. A program that executes 5 steps. In the fifth step, an instruction to disapprove at least part of the change in the workflow information is accepted from the user who presented the workflow information changed in the fourth step, and an instruction to disapprove the accepted change. The program according to claim 1, which changes the model information based on. There are multiple second business operators,
In the fifth step, an instruction to disapprove at least part of the change in the workflow information is accepted from the user who presented the workflow information changed in the fourth step, and an instruction to disapprove the accepted change. The program according to claim 2, which changes the model information about the specific second business operator based on. In the fifth step, an instruction to disapprove at least part of the change in the workflow information is accepted from the user who presented the workflow information changed in the fourth step, and an instruction to disapprove the accepted change. The program according to claim 2, which changes the model information related to the commercial transaction for a specific period based on. 2. The program according to claim 1, wherein in the fourth step, information on the workflow that has been changed is presented to the user in a visible state, and at this time, a portion of the information on the workflow that is related to the change is highlighted. . 2. The program according to claim 1, wherein in the fourth step, information on the workflow that has been changed is presented to the user in a visible state, and at this time, a portion of the information on the workflow that is related to the change is displayed in a balloon. . 2. The program according to claim 1, further causing the program to execute a sixth step of presenting the workflow information changed in the fifth step to the user. An information processing device comprising a processor and a memory,
The memory stores format information of forms necessary for a user who is a first business operator to carry out business, and workflow model information indicating a work process for creating the forms;
The processor includes:
a first step of accepting input from the user of transaction data regarding a commercial transaction between the user and a second business entity that is a business partner of the user;
A second step of generating information on the workflow related to the commercial transaction with the second business operator by referring to the model information based on the transaction data accepted in the first step, and presenting this information. and,
a third step of accepting an instruction to change the transaction data and information related to the change from the user who presented the workflow information in the second step;
Based on the information related to the change accepted in the third step, it is determined whether or not it is necessary to change the information of the workflow generated in the second step, and if it is determined that the change is necessary, the changed workflow information is changed. a fourth step of presenting information to the user;
A step of accepting an instruction to approve changes to the workflow information from the user who presented the workflow information changed in the fourth step, and changing the workflow information based on the accepted instruction to approve the changes. An information processing device that executes 5 steps. A method performed by a computer comprising a processor and a memory, the method comprising:
The memory stores format information of forms necessary for a user who is a first business operator to carry out business, and workflow model information indicating a work process for creating the forms;
The processor includes:
a first step of accepting input from the user of transaction data regarding a commercial transaction between the user and a second business entity that is a business partner of the user;
A second step of generating information on the workflow related to the commercial transaction with the second business operator by referring to the model information based on the transaction data accepted in the first step, and presenting this information. and,
a third step of accepting an instruction to change the transaction data and information related to the change from the user who presented the workflow information in the second step;
Based on the information related to the change accepted in the third step, it is determined whether or not it is necessary to change the information of the workflow generated in the second step, and if it is determined that the change is necessary, the changed workflow information is changed. a fourth step of presenting information to the user;
A step of accepting an instruction to approve changes to the workflow information from the user who presented the workflow information changed in the fourth step, and changing the workflow information based on the accepted instruction to approve the changes. How to do it in 5 steps.