JP2024056997A - PROGRAM, INFORMATION PROCESSING APPARATUS, AND METHOD - Google Patents

Abstract

[Problem] To provide a program, information processing device, and method for customizing a workflow in response to changes in workflow management when a transaction amount is changed. [Solution] The method includes a step of accepting input of transaction data from a user relating to a commercial transaction between the user and a second business that is the user's business partner, a step of generating and presenting workflow information relating to the commercial transaction with the second business 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, a step of presenting the changed workflow information to the user if it is determined that the workflow information needs to be changed based on the information related to the change, and a step of accepting an instruction from the user to approve the change to the workflow information and changing the workflow information. [Selected Figure] Figure 10

Description

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

ERP (Enterprise Resource Planning) package software (often referred to as integrated core business systems, and often provided as cloud-based services) includes a sales management system that manages the entire sales process, from prospect and lead management to quotations, orders, sales, invoices, and accounts receivable management, and also includes a workflow management function.

A technology related to the above-mentioned technology is disclosed in Patent Document 1.

Patent Document 1 relates to a transaction management system, and the transaction management device of this transaction management system includes a transaction data registration acceptance unit that accepts registration information for transaction data through the operation of one of multiple businesses, an invitation notification unit that accepts invitation data to invite other businesses, an edit input acceptance unit that accepts edit input for the transaction data, a change presentation unit that presents changes to the edited content to users other than the user who performed the edit, a form data generation unit that generates form data such as quotations, an approval input acceptance unit that accepts approval input for the work process of the transaction data, and a transaction data process change unit that advances the work process to the next work process.

JP 2021-9505 A

When managing transactions (workflow), for example, if the amount being handled changes, the workflow may change. Specifically, if the amount being handled exceeds 100,000 yen, the approval flow (approver, attached vouchers, etc.) may change. The perspective for checking may also change. For this reason, there is currently a situation where cumbersome management is carried out, such as requesting business partners to issue separate invoices so that the amount does not exceed a specified amount.

Therefore, this disclosure describes a technology that can customize workflow management to accommodate changes in workflow when the transaction amount changes.

According to an embodiment of the present disclosure, a program is provided for a computer having a processor and a memory to execute the program. The memory stores format information of forms necessary for a user, who is a first business operator, to perform a business, and model information of a workflow indicating a work process for creating forms. The program causes the processor to execute the following steps: a first step of accepting input of transaction data related to a business transaction between the user and a second business operator, who is a business partner of the user, from the user; a second step of generating workflow information related to a business transaction with the second business operator by referring to the model information based on the transaction data accepted in the first step, and presenting the information; 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; a fourth step of determining whether or not the workflow information generated in the second step needs to be changed based on the information related to the change accepted in the third step, and if it is determined that the change is necessary, presenting the changed workflow information to the user; and a fifth step of accepting an instruction to approve the change 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 change.

According to the present disclosure, in workflow management, when the amount of transactions changes, it becomes possible to customize the workflow accordingly.

A diagram showing the overall configuration of a transaction management system 1 of embodiment 1. A block diagram showing the functional configuration of a terminal device 10 that constitutes the transaction management system 1 of embodiment 1. A diagram showing the functional configuration of a server 20 that constitutes a transaction management system 1 of embodiment 1. A figure showing an example of the data structure of a transaction database 2021 stored in a server 20 constituting a transaction management system 1 of embodiment 1. A figure showing an example of the data structure of a report format database 2022 stored in the server 20 constituting the transaction management system 1 of embodiment 1. A figure showing an example of the data structure of a workflow model information database 2025 stored in the server 20 constituting the transaction management system 1 of embodiment 1. A diagram showing an example of the data structure of a client information database 2027 stored in the server 20 constituting the transaction management system 1 of embodiment 1. A figure showing an example of the data structure of a user information database 2028 stored in the server 20 constituting the transaction management system 1 of embodiment 1. A sequence diagram showing an example of work processes and work statuses in the transaction management system 1 of embodiment 1. 1 is a flowchart showing an example of the flow of workflow processing by the transaction management system 1 of embodiment 1. 11 is a flowchart showing an example of the flow of workflow processing by the transaction management system 1 of embodiment 1, and is a flowchart showing an example of the flow of processing following the processing shown in FIG. 10. 10A and 10B are diagrams illustrating examples of screens displayed on a terminal device 10. 10A and 10B are diagrams illustrating examples of screens displayed on a terminal device 10. FIG. 2 is a diagram showing an example of a folder tree screen displayed on the terminal device 10. FIG. 2 is a diagram showing an example of a folder tree screen displayed on the terminal device 10. FIG. 2 is a diagram showing an example of a folder tree screen displayed on the terminal device 10.

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 some parts have been omitted or simplified as appropriate for clarity of explanation. The present invention can also be implemented in various other forms. Unless otherwise specified, each component may be singular or plural.

In addition, in the figures explaining the embodiments, parts having the same functions are given the same reference numerals, and repeated explanations are 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 explanation, various information may be explained using expressions such as "table," "list," and "queue," but the various information may be expressed in other data structures. To indicate independence from data structure, "XX table," "XX list," and the like may be referred to as "XX information." When explaining identification information, expressions such as "identification information," "identifier," "name," "ID," and "number" are used, but these are interchangeable.

In addition, in the following description, 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.

When there are multiple components with the same or similar functions, they may be described using the same reference numerals with different subscripts. However, when there is no need to distinguish between these multiple components, the subscripts may be omitted.

In addition, the following description may describe processing performed by executing a program, but the program is executed by a processor (e.g., a CPU or a GPU) to perform a defined process using storage resources (e.g., a memory) and/or an interface device (e.g., a communication port) as appropriate, so the subject of the processing may be the processor. Similarly, the subject of the processing performed by executing a program may be a controller, device, system, computer, or node having a processor. The subject of the processing performed by executing a program may be any computing unit, and may include a dedicated circuit (e.g., an FPGA or an ASIC) that performs a specific process.

In the following description, a "processor (part)" 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). The at least one processor may be a single-core or multi-core.

In addition, at least one processor may be a processor in the broad sense, such as a hardware circuit (e.g., an FPGA (Field-Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit)) that performs some or all of the processing.

In the following description, a "memory unit" refers to one or more memories, typically a primary storage device. At least one memory in the memory unit may be a volatile memory or a non-volatile memory.

The program may be installed in 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 may include a processor and a storage resource that stores the program to be distributed, and the processor of the program distribution server may distribute the program to be distributed to other computers. Also, in the following description, two or more programs may be realized as one program, and one program may be realized as two or more programs.

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

In addition, in the following description, identification numbers are used as identification information for various objects, but other types of identification information (e.g., identifiers including letters or codes) may also be used.

In the following description, when elements of the same type are described without distinction, reference signs (or common signs among reference signs) are used, and when elements of the same type are described with distinction, the identification numbers (or reference signs) of the elements are used.

In addition, in the following explanation, the control lines and information lines are those that are considered necessary for the explanation, and not all control lines and information lines in the product are necessarily shown. All components may be connected to each other.

＜0 System Overview＞
The transaction management system according to the present disclosure will be described below.

The transaction management system according to the present disclosure is, by way of example and not limitation, a system for managing transaction data relating to transactions conducted between a user, who is a first business operator, and a second business operator, who is another business operator, and at least accepts registration of transaction data from the user, and generates workflow information suitable for the transaction data based on this transaction data, pre-registered form format data, and workflow model information. Next, when there is a change in the transaction data, the transaction management system accepts the change instruction and change details from the user, determines whether to make changes to the workflow information, and if it determines that changes are necessary, changes the workflow information and presents it to the user, and obtains approval of the changes from the user. Then, once approval of the changes is obtained from the user, the workflow information is changed.

The services provided by the transaction management system 1 are not limited to the management of transaction data as described above, but may be general accounting services related to the user's company or personal business. For example, the input transaction data may be used as deposit and withdrawal data, and the input of financial data such as assets may be accepted to provide accounting services for the user's company or personal business.
In the following description, the instruction to change the transaction data is accepted from a user who is a first business operator, but the second business operator may also be invited to the transaction management system and accept the instruction to change the transaction data in the same way as the first business operator.

In the transaction management system according to the present disclosure, transaction data refers to data related to a commercial transaction between a user and a second business. As an example, the transaction data is transaction information such as information on delivered goods (item number, model number, version number, quantity, etc.) generated in the business of the user (or the first business company if the user is an employee of the first business company), various payment information such as 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) of this information entered into the transaction management system by the user when actually conducting a commercial transaction with the second business company, arranged in chronological order. The transaction data may also be created in a terminal device constituting the transaction management system as a file created in a certain format, and uploaded to a server constituting the transaction management system and registered as a system.

In addition, in the transaction management system according to the present disclosure, the documents are documents necessary for the user to carry out business operations based on the transaction data. Such documents are well known, and examples include quotations, orders (purchase orders), delivery notes, receipts, inspection slips, and invoices. As long as the documents are necessary for the user to carry out business operations based on the transaction data, there are no particular limitations on their names or contents, and documents of various names and contents can be managed and created in the transaction management system according to the present disclosure.

In addition, 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 required when creating the forms. Specifically, the format information is wording information and layout information required to create estimates, purchase orders, and invoices, which are forms created for each work process, which is a workflow, as described below, and includes information defining the titles and standard phrases such as "estimate," "purchase order," and "invoice," as well as the positions for writing items and amounts on the forms. This form format data is used when creating forms as deliverables of work processes, and form data is created by applying transaction data such as company names, items, and amounts to this form format data.

Furthermore, in the transaction management system according to the present disclosure, the workflow refers to the work process for creating documents. A specific workflow will be described in detail using a diagram, but as an example, when a second business entity places an order for a deliverable with a user, a quote for the cost of creating the deliverable is created, the quote is approved by a superior and then sent to the second business entity, the second business entity issues an instruction to create a deliverable including the quote, the deliverable is created and delivered together with a delivery note, and an invoice for the cost of creating the deliverable is issued. In the transaction management system according to the present disclosure, the workflow model information is information indicating the type of workflow for each of the workflows assumed in advance. The user refers to the workflow model information, selects one of the workflow model information, 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 user's selection. The workflow information is information indicating a specific workflow suitable for the selected transaction data.

After the workflow information is generated, the transaction data may be changed. For example, after a detailed review of the procedure for creating the deliverable, it is determined that a quote that exceeds the initial estimated amount needs to be created. The workflow needs to be created based on the company's internal regulations, etc., and the approver and attached vouchers may change depending on the estimated amount. For example, if there is an internal regulation that the section manager must approve an estimate of 100,000 yen or less, but if the estimate exceeds 100,000 yen and is up to 10 million yen, the department manager must approve it, then if the estimated amount is changed, the approval route (i.e., the workflow) must also be changed. Therefore, when the transaction data is changed, the transaction management system according to the present disclosure accepts instructions to change the transaction data and information related to the change, and determines whether or not the workflow information should be changed based on the information related to the change in the transaction data.

Then, when the transaction management system according to the present disclosure determines that the workflow information needs to be changed, it presents the changed workflow information to the user and accepts approval for the change to the workflow information from the user. When approval for the change is accepted, the transaction management system according to the present disclosure changes the workflow information.

<First embodiment>
The following describes the transaction management system 1. 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 a first embodiment. As shown in FIG. 1, the transaction management system 1 includes a plurality of terminal devices (terminal device 10A and terminal device 10B are shown in FIG. 1. Hereinafter, they may be collectively referred to as "terminal device 10") and a server 20. The terminal devices 10 and the server 20 are connected to each other via a network 80 so as to be able to communicate with each other. The network 80 is configured as a wired or wireless network. In this embodiment, the server 20 is a server having a function as a web server (including a cloud server), and exchanges information with the terminal device 10 through web pages. In addition, a web page browser for viewing web pages is installed in the terminal device 10, but a dedicated application for providing the services of the server 20 may be installed and configured to be viewable through 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, the user is an entity that conducts commercial transactions with the second business, and is a person in charge of a company that is a business that generates various forms of data in the server 20 in association with the commercial transactions and exchanges the generated forms of data with the second business, or a sole proprietor. 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, a mobile terminal such as a smartphone, or the like.

The terminal device 10 is communicatively connected to the server 20 via a network 80. The terminal device 10 is connected to the network 80 by communicating with communication devices such as a wireless base station 81 that supports communication standards such as 4G, 5G, and LTE (Long Term Evolution), and a wireless LAN router 82 that supports wireless LAN (Local Area Network) standards such as IEEE (Institute of Electrical and Electronics Engineers) 802.11. As shown as the 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 unit 16, and a processor 19.

The communication IF 12 is an interface for inputting and outputting signals so that the terminal device 10 can communicate with external devices. The input device 13 is an input device (e.g., 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 (a display, a speaker, etc.) for presenting information to a user. The memory 15 is for temporarily storing programs and data processed by the programs, etc., and is a volatile memory such as a DRAM (Dynamic Random Access Memory). The storage unit 16 is a storage device for saving data, such as a flash memory or a HDD (Hard Disc Drive). The processor 19 is hardware for executing an instruction set described in a program, and is composed of an arithmetic unit, a register, peripheral circuits, etc.

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

The server 20 is a computer connected to the 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 can communicate with external devices. The input/output IF 23 functions as an interface with an input device for accepting input operations from a user and an output device for presenting information to a user. The memory 25 is for temporarily storing programs and data processed by the programs, etc., and is a volatile memory such as a DRAM (Dynamic Random Access Memory). The storage 26 is a storage device for saving data, such as a flash memory or a 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, etc.

<1.1 Configuration of terminal device 10>
Fig. 2 is a block diagram showing the functional configuration of the terminal device 10 constituting the transaction management system 1 of Fig. 1. As shown in Fig. 2, the terminal device 10 includes a plurality of antennas (antenna 111, antenna 112), wireless communication units (first wireless communication unit 121, second wireless communication unit 122) corresponding to each antenna, an operation reception unit 130 (including a keyboard 131 and a mouse 132), a display 150, a storage unit 170, and a control unit 180. The terminal device 10 also has functions and configurations (e.g., a battery for storing power, a power supply circuit for controlling the supply of power from the battery to each circuit, etc.) that are not particularly shown in Fig. 2. 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 emits the signal emitted by the terminal device 10 as a radio wave. The antenna 111 also receives the radio wave from space and provides the received signal to the first wireless communication unit 121.

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

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

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

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

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

The display 150 displays data such as images, videos, and text in response to the control of the control unit 180. The display 150 is realized, for example, by 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 contact with the touch panel, for example, by using a capacitive touch panel, and may be configured to include the functions of the keyboard and the like described above.

The storage unit 170 is composed of 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, the storage unit 170 stores transaction data 1701.

As described above, transaction data 1701 is data related to a commercial transaction between the user and the second business. Details of the transaction data will be described later.

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

The input operation reception unit 1801 performs processing to receive user input operations on an input device such as the keyboard 131.

The transmission/reception unit 1802 performs processing for the terminal device 10 to transmit and receive data to and from external devices such as the server 20 in accordance with a communication protocol.

The data processing unit 1803 performs calculations on the data received 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 processing to present information to the user. The notification control unit 1804 performs processing to display a display image on the display 150, to output sound to a speaker (not shown), etc.

<1.2 Functional configuration of server 20>
Fig. 3 is a diagram showing the functional configuration of the server 20 constituting the transaction management system 1 of Fig. 1. As shown in Fig. 3, the server 20 performs the functions of a communication unit 201, a storage unit 202, and a control unit 203.

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

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

Transaction DB2021 is a database for managing transaction data related to commercial transactions between a user and a second business. Transaction DB2021 preferably stores multiple transaction data. Details will be described later.

The report format DB2022 is a database for managing the format information of reports that are necessary for users to carry out their work. The report format DB2022 preferably stores format information for multiple reports. Details will be described later.

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

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

The WF model information DB2025 is a database for managing workflow model information. The WF model information DB2025 preferably stores model information for multiple workflows. Details will be described later.

The WF model data 2026 is workflow model data that constitutes model information of a workflow. The workflow model data is data that describes the individual work steps that make up the workflow and the chronological order 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 memory 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, can be suitably applied.

The client information DB2027 is a database for storing information on the second business operator, specifically, information identifying the second business operator (client ID), the name of the second business operator (company name), the second corporate number, etc. The client information DB2027 is created in advance by the user and stored in the memory unit 202. Details will be described later.

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

The control unit 203 performs the functions shown in various modules, such as a receiving control module 2031, a sending control module 2032, a transaction data acquisition module 2033, a workflow information generation module 2034, a change part acceptance module 2035, a workflow information change module 2036, a report data generation module 2037, and a transaction data process change module 2038, by the processor 29 of the server 20 performing processing according to a program.

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

The transmission control module 2032 controls the process in which the server 20 transmits signals to external devices according to a communication protocol. The reception control module 2031 and the transmission control module 2032 provide the server 20 with the function of operating as a web server for external devices, including the terminal device 10, that access the server 20 via the network 80.

When the user, who is the first business operator, operates the terminal device 10 and transmits registration information for the transaction data, the transaction data acquisition module 2033 receives the transaction data via the communication unit 201. 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 (if there is multiple transaction data in the transaction DB 2021, it selects one of the transaction data), identifies workflow model information to be applied to this transaction data from the WF model information DB 2025 (if there is multiple workflow model information, it selects one of the workflow model information), and generates workflow information using the identified workflow model information.The workflow information generation module 2034 then temporarily stores the generated workflow information in the memory unit 202, and presents the workflow information to the user.

The workflow information generation module 2034 may select the workflow model information stored in the WF model information DB 2025 by any method, and may be appropriately selected from known methods. One example is a method in which the workflow information generation module 2034 refers to information about the second business included in the transaction data and selects workflow model information specific to the second business. Another example is a method in which, when the transaction data includes data on an item related to a commercial transaction, the workflow information generation module 2034 selects workflow model information specific to this item. Another example is a method in which training data describing the relationship between various information included in the transaction data and the workflow model information is prepared in the storage unit 202, a learning model is generated using this training data, and the workflow information generation module 2034 inputs the transaction data into this learning model to obtain workflow model information as an inference result of the learning model.

The method of presenting the workflow information generated by the workflow information generation module 2034 to the user is not particularly limited. As an example, the workflow information generation module 2034 may generate data for generating a screen including a line diagram of the workflow using techniques such as a sequence diagram or a state transition diagram on the display 150 of the terminal device 10 used by the user, and display this data on the display 150 of the terminal device 10. Alternatively, the workflow information generation module 2034 may generate data for generating a screen showing the connection status of the boxes, which represents the work steps that make up the workflow, and display this data on the display 150 of the terminal device 10.

When a user who has confirmed the workflow information presented by the workflow information generation module 2034 inputs instructions to change the transaction data and information related to the changes via the terminal device 10 owned by the user, the change acceptance module 2035 accepts the instructions to change the transaction data and information related to the changes.

As an example, in the workflow information generated by the workflow information generation module 2034, the transaction data was for a transaction of 100,000 yen, but after a detailed examination of the estimated amount, it was found that the transaction was changed to 110,000 yen. For a company that is a user and users belonging to this company, transactions over 100,000 yen were approved by the department manager rather than the section manager. With the change in the estimated amount, a work step for the department manager's approval is added after the section manager's approval in the workflow. Therefore, the user inputs to the server 20 via the terminal device 10 that the estimated amount in the transaction data will be changed from 100,000 yen to 110,000 yen (the amount change is also information), and the change acceptance module 2035 accepts the input of the change in the transaction data and information related to the change (such as the estimated amount becoming 110,000 yen).

Other examples of changes to transaction data include changing the person in charge at the second business that is the trading partner, changing the person in charge's job title, and changing item data.

Then, the change acceptance module 2035 stores the accepted and changed transaction data in the transaction DB 2021, and notifies the workflow information change module 2036 that changes to the workflow information should be considered in conjunction with the change in the transaction data.

When the change acceptance module 2035 accepts the changes to the transaction data, the workflow information change module 2036 determines whether or not the workflow information generated by the workflow information generation module 2034 needs to be changed based on the contents of the changed transaction data (information related to the changes). Then, 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, well-known techniques can be suitably applied. As an example, the workflow information change module 2036 may have a rule-based DB and make a determination based on this rule-based DB. Specifically, the rule-based DB has a registered rule such that when the estimated amount exceeds 100,000 yen, the approval route is changed from section manager approval to department manager approval. In the above example, since the estimated amount exceeds 100,000 yen, it is determined that the workflow information needs to be changed according to this rule, and the changed workflow information (in this case, information related to the change in the workflow from section manager approval to department manager approval) is presented to the user. At this time, the workflow information change module 2036 may determine whether or not the workflow information has been changed by referring to various information of the second business operator and/or user stored in the client information DB 2027 and/or user information DB 2028.

Another example is a method in which training data describing the relationship between the changed transaction data and the changed workflow information is prepared in the memory unit 202, this training data is used to generate a learning model, and the workflow information change module 2036 inputs the changed transaction data into this learning model, thereby obtaining the changed workflow information as an inference result of the learning model and presenting it to the user.

The method of presenting the workflow information changed by the workflow information change module 2036 to the user is not particularly limited. As an example, the workflow information change module 2036 may generate data for generating a screen including a line diagram of the workflow using techniques such as a sequence diagram or a state transition diagram on the display 150 of the terminal device 10 used by the user, and display this data on the display 150 of the terminal device 10. Alternatively, the workflow information change module 2036 may generate data for generating a screen showing the connection status of the boxes, which represents the work processes that make up the workflow, and display this data 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 in a state that is visible to the user. At this time, it is preferable that the workflow information change module 2036 enables the user to easily grasp the changed parts by using techniques such as highlighting the parts related to the changes, displaying them as a pop-up, or displaying them with a blinking display. Furthermore, it is preferable that the workflow information change module 2036 enables the user to easily grasp the changed parts by displaying the parts related to the changes in a speech bubble.

Then, the workflow information change module 2036 accepts an instruction to approve the changes to the 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 an instruction is received from the user that at least some of the changes to the workflow information are not approved (not approved), the workflow model information itself is changed based on the accepted instruction of not approving.

Specifically, a user may give an instruction to approve the change to the workflow model information as well as the change to the workflow information for a specific second business operator, but not to approve the change to the workflow information for second business operators other than the specific second business operator. In this case, the changed workflow model information becomes workflow model information that is applicable only to the specific second business operator.

Similarly, a user may approve a change to the workflow model information along with a change to the workflow information, but may specify that the change to the workflow model information should only be applied at a specific time (for example, change the workflow model information only in accounting months such as March and September). In this case, the changed workflow model information becomes workflow model information that is only applicable at a specific time.

In addition to the above example, the workflow information change module 2036 may change the workflow model information along with the workflow information.

The form data generation module 2037 generates form data, such as quotation data, purchase order data, and invoice data, that are created as deliverables for each of multiple work processes. The format data for the form data stored in the form format DB 2022 already has titles and standard phrases, such as "quote," "purchase order," and "invoice," set, and the positions for writing items and amounts on the form are defined. Therefore, variable data, such as item and amount data of the transaction data stored in the transaction DB 2021, is applied to this form format data to generate form data. The form data generation module 2037 also 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 a transaction DB 2021 stored by the server 20 of Fig. 3. Fig. 5 is a diagram showing an example of the data structure of a form format DB 2022 stored by the server 20 of Fig. 3. Fig. 6 is a diagram showing an example of the data structure of a WF model information DB 2025 stored by the server 20 of Fig. 3. Fig. 7 is a diagram showing an example of the data structure of a client information DB 2027 stored by the server 20 of Fig. 3. Fig. 8 is a diagram showing an example of the data structure of a user information DB 2028 stored by the server 20 of Fig. 3.

As shown in FIG. 4, each record in transaction DB2021 includes an item "transaction ID," an item "customer ID," an item "item," an item "date of occurrence," an item "product number," an item "quantity," an item "amount," an item "status," an item "change date," etc.

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

The item "Customer ID" is information that identifies a second business that is a trading partner of a user (first business) who is the administrator of the transaction management system 1.

The "item" field is information that indicates the type of product or service traded in a commercial transaction related to the transaction data identified by the "transaction ID" field.

The "Date of occurrence" item is information that indicates the date of occurrence of the commercial transaction related to the transaction data identified by the "Transaction ID" item.

The "Item Number" item is information that indicates the item number of the product or service traded in the commercial transaction related to the transaction data identified by the "Transaction ID" item. Note that if the subject of the transaction is a service, there is no concept of an item number, so the "Item Number" item will be left blank.

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

The "Amount" item is information that indicates the amount of goods or services traded in a commercial transaction related to the transaction data identified by the "Transaction ID" item.

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

The "Change Date" item is information indicating the date on which the transaction data identified by the "Transaction ID" item was changed. As can be seen in the "Amount" item, transaction DB2021 can record the change history of transaction data.

As shown in FIG. 5, each record in the report format DB 2022 includes an item "Report ID", an item "Report name", an item "Template data", an item "Report format data", etc.

The item "Report ID" is information that identifies the report format managed by the transaction management system 1.

The "Report Name" item is information that indicates the name of the report related to the report format identified by the "Report ID" item.

The item "Fixed phrase data" is information that indicates the file name of the fixed phrase data 2023 related to the form format identified by the item "Form ID".

The item "Report format data" is information that indicates the file name of the report layout data 2024 related to the report format identified by the item "Report ID".

Note that in FIG. 5, the extension of the template data 2023 is shown as text format, and the extension of the form layout data 2024 is shown as XML, but the format of these data is not limited to the illustrated example.

As shown in FIG. 6, each record in the WF model information DB2025 includes an item "WF model ID" and an item "WF model data", etc.

The item "WF model ID" is information that identifies the workflow model information managed by the transaction management system 1.

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

Note that in Figure 6, the extension of the WF model data 2026 is illustrated as JSON format, but the format of these data is not limited to the illustrated example.

As shown in FIG. 7, each record in the client information DB2027 includes the items "client ID", "company name", "corporate number", "address", "contact information", and "industry type", etc.

The item "Client ID" is information that identifies a second business that is a trading partner of a commercial transaction with a user (first business) who is the administrator of the transaction management system 1, and is the same as the item "Trading Partner ID" in transaction DB2021.

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

The "Corporate Number" item is information that indicates the corporate number of the second business identified by the "Client ID" item.

The "Address" item is information that indicates the address of the second business identified by the "Client ID" item.

The "Contact" item is information that indicates the contact information of the person in charge of the transaction at the second business identified by the "Client ID" item.

The "Industry" item is information that indicates the industry of the corporation that is the second business operator identified by the "Client ID" item.

As shown in FIG. 8, each record in user information DB2028 includes the items "User ID", "Name", "Affiliation", "Post", "Approval Authority", "Approval Authority Amount", "Email Address", and "Password". In user information DB2028 shown in FIG. 8, it is assumed that the first business using the transaction management system 1 has multiple (individual) users. In this specification, no distinction is made between a "user" as a company (corporation) and a "user" as an employee of a company, and both are described as "users".

The "User ID" item is information that identifies an individual user who is an administrator or user of the transaction management system 1.

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

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

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

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

The "approval authority" field is information that indicates the maximum amount of approval authority assigned to the user identified by the "user ID" field.

The "Email address" item is information that indicates the in-company email address of the user identified by the "User ID" item.

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

<3 Operation>
The workflow processing by the transaction management system 1 in the first embodiment will be described below with reference to FIGS.

Figure 9 is a sequence diagram showing an example of work processes and work statuses in the transaction management system 1 according to the present disclosure. Using Figure 9, the work processes and work statuses managed by transaction data in the present disclosure will be described. Note that here, the work processes are "quotation stage", "ordering stage", and "billing stage" which indicate the stages of a transaction at a business, and the work statuses are "creating", "checking", "waiting", etc. which indicate the state of each business in the work process, and are registered for multiple business operators, for example.

First, the first business entity that places the order registers the transaction data. At this time, the second business entity that receives the order is not necessarily a single company.

At this time, as shown in FIG. 9, the work process of the registered transaction data becomes the quotation stage, the work status of the user who is the contractor becomes Estimate preparation in step S901, and the work status of the user who is the orderer becomes Awaiting quotation in step S902. When the contractor prepares a quotation and sends it to the orderer, the work status of the orderer becomes Estimate confirmation in step S903, and the work status of the contractor becomes Awaiting quotation confirmation in step S904. When the orderer approves the contents of the quotation, the work status of the contractor becomes Estimate completed in step S905.

Next, the work process for the transaction data enters the ordering stage, and the orderer's work status becomes "Order creation" in step S906. When the orderer creates an order and sends it to the contractor, the contractor's work status becomes "Order confirmation" in step S907, and the orderer's work status becomes "Awaiting order confirmation" in step S908. When the contractor approves the order contents, the contractor's work status becomes "Order accepted" in step S909, and the orderer's work status becomes "Order completed" in step S910. After this, the actual goods related to the transaction are handed over and work related to the outsourcing is carried out.

When the actual delivery of the goods in the transaction and the work related to the outsourcing are completed, the work process of the transaction data enters the billing stage, the contractor's work status becomes "preparing bill" in step S911, and the orderer's work status becomes "waiting for billing" in step S912. When the contractor creates a bill and sends it to the orderer, the orderer's work status becomes "confirming billing details" in step S913, and the contractor's work status becomes "waiting for billing confirmation" in step S914. When the orderer approves the billing details, the contractor's work status becomes "invoiced" in step S915, and the orderer's work status becomes "confirmed billing details" in step S916. After this, 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. Note that the work process and work status described above are only examples and are not limited to these.

Figure 10 is a flowchart showing an example of the flow of workflow processing performed by the transaction management system 1 according to the present disclosure.

In step S1000, the server 20 performs user authentication to provide the user with the transaction data itself from the transaction management system 1, the work process and work status of the transaction data, and accounting services including these. For this purpose, the user is requested to input account information and a password, and the user is authenticated by checking whether the input information matches the registered information. If there is a match, the user is logged in to the server 20.

In the process of step S1001, registration information for transaction data is sent by operating the operation reception unit 130 of the terminal device 10, and the transaction data acquisition module 2033 of the server 20 receives the transaction data via the communication unit 201. The received transaction data is stored in the transaction DB 2021. In addition to (individually) inputting transaction data via the terminal device 10, the user may operate the terminal device 10 to generate a transaction data file in advance, and then transmit this transaction data file to the server 20 to register the transaction data in the server 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 presents the workflow information generated in step S1002 to the user. Preferably, the workflow information generation module 2034 transmits information to the terminal device 10 for displaying the generated workflow information on the display 150 of the user's terminal device 10, and causes the display 150 to display a screen related to the workflow information based on this information.

In step S1004, the control unit 203 of the server 20 registers the work status for the transaction data registered in step S1001. For example, if the work process of the transaction data is registered as the estimate stage, and if the registered user is a contractor, the work status of the user is registered as estimate creation in progress (work in progress), and if the user is an orderer, the work status of the user is registered as awaiting estimate, and these are stored in the transaction DB 2021.

In step S1005, the change acceptance module 2035 of the server 20 waits for the user, who has confirmed the workflow information presented by the workflow information generation module 2034 in step S1003, to input an instruction to change the transaction data and information related to the change via the terminal device 10 owned by the user (YES in step S1005), and if the instruction to change is accepted, accepts the instruction to change the transaction data and information related to the change. Note that in the flowchart shown in FIG. 10, the process moves to the next step after waiting for an instruction to change the transaction data, but it may also move to the next step after accepting an instruction that there is no instruction to change (which can also be considered an instruction to change the transaction data).

In step S1006, the workflow information change module 2036 of the server 20 determines whether or not the workflow information generated by the workflow information generation module 2034 in step S1002 needs to be changed, based on the changes to the transaction data and the information related to the changes accepted by the change part acceptance module 2035 in step S1005. 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 does not need to be changed (NO in step S1006), the program proceeds to step S1102.

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 to the terminal device 10 for displaying the changed workflow information on the display 150 of the user's terminal device 10, and causes the display 150 to display a screen related to the change in the workflow information based on this information.

In step S1100, the workflow information change module 2036 of the server 20 accepts input of information regarding whether or not the change to the transaction data is approved by the user who confirmed the change to the workflow information presented by the workflow information change module 2036 in step S1006, via the terminal device 10 owned by this user. If the accepted information is information regarding approval of the change (YES in step S1100), the program proceeds to step S1101, and if the accepted information is information regarding not approving the change (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 instructions. At this time, the workflow information change module 2036 presents the changed workflow information to the user as the final change result.

In step S1102, the report 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 report data stored in the report format DB 2022 to generate report data. The generated report data is, for example, a quotation, a purchase order, or an invoice.

In the process of step S1103, the control unit 203 of the server 20 registers the work status of the progressed work process. For example, if the work process is registered as the ordering stage, the work status of the client is registered in the transaction DB 2021 as order creation in progress (work in progress). Also, if the work process is registered as the billing stage, the work status of the contractor is registered in the transaction DB 2021 as billing creation in progress (work in progress), and the work status of the client 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>
Below, examples of screens for workflow processing by the transaction management system 1 will be described with reference to Figures 12 to 16.

Figure 12 is a diagram showing an example of a login screen 1200 displayed on the display 150 of the terminal device 10. When a user operates the terminal device 10 to access the server 20, the URL of the login screen is sent at the instruction of the server 20, and the login screen is displayed. Alternatively, the login screen is displayed at the instruction of an app that has been installed in the terminal device 10 in advance. Through these operations, the login screen 1200 as shown in Figure 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 input his/her account information (email address in this embodiment) and password into the account input field 1201 and password input field 1202 provided on the login screen 1200, respectively. After that, the user presses the login button 1203 to be authenticated as the user and to log in to the server 20.

Figure 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 the user selects to input transaction data by selecting a menu or tab, the transaction data input screen 1300 shown in Figure 13 is displayed on the display 150 of the terminal device 10 and becomes available for input by operating the operation reception unit 130.

When a transaction data input screen 1300 such as that shown in FIG. 13 appears on the display 150 of the terminal device 10, the user operates the operation reception unit 130 to input information such as the business partner information (company name or sole proprietor's name), item, account title, date of occurrence, and amount related to the transaction data into various input fields such as the amount field 1301 and business partner input field 1302 on the transaction data input screen 1300. After that, the user presses the register button 1303 to register the transaction data in step S1001.

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

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

Figure 15 is a diagram showing an example screen displayed on the terminal device 10 showing workflow information that has been determined to require change in conjunction with a change to transaction data. The example screen in Figure 15 shows an example screen showing workflow information that has been generated by the workflow information change module 2036 of the server 20 and sent to the terminal device 10, and that requests approval of the change. This corresponds to step S1007 in Figure 10.

As shown in FIG. 15, a window 1500 is displayed on the display 150 of the terminal device 10, and the window 1500 displays workflow information 1501 for which approval of the change is to be requested, which was generated by the workflow information change module 2036 and sent to the terminal device 10. In the example shown in FIG. 15, a speech bubble 1502 is displayed at the change location for which approval of the change is to be obtained, superimposed on the workflow information 1501 shown in FIG. 14. The speech bubble 1502 displays an area 1503 in which the reason for needing approval of the change is described, and buttons 1504 and 1505 that the user operates to input whether or not the change is approved. The user operates the operation reception unit 130 of the terminal device 10 to input an operation input of pressing down one of the buttons 1504 and 1505, thereby instructing the server 20 whether or not the change is approved.

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

As shown in FIG. 16, a window 1600 is displayed on the display 150 of the terminal device 10, and this window 1600 displays changed workflow information 1601 that has been generated by the workflow information change module 2036 and sent to the terminal device 10. In the example shown in FIG. 16, the changes 1602 are displayed by dotted lines, superimposed on the workflow information 1401 shown in FIG. 14.

<5. Summary >
As described above, according to this embodiment, when a change is made to transaction data, the change to the transaction data is input to the server 20, and the workflow information change module 2036 of the server 20 determines whether or not the workflow information has been changed. If it is determined that a change is necessary, the user is asked to approve the change, and if the user approves the change, the workflow information is changed. This makes it possible to customize the system to accommodate changes in workflow.

<6. Notes>
In addition, the above-described embodiments are described in detail to clearly explain the present disclosure, and are not necessarily limited to those including all of the described configurations. In addition, some of the configurations of each embodiment can be added to, deleted from, or replaced with other configurations.

The above-mentioned configurations, functions, processing units, processing means, etc. may be realized in part or in whole by hardware, for example by designing them as integrated circuits. The present invention can also be realized by software program code that realizes the functions of the embodiments. In this case, a storage medium on which the program code is recorded is provided to a computer, and a processor of the computer reads the program code stored in the storage medium. In this case, the program code itself read from the storage medium realizes the functions of the above-mentioned embodiments, and the program code itself and the storage medium on which it is stored constitute the present invention. Examples of storage media for supplying such program code include flexible disks, CD-ROMs, DVD-ROMs, hard disks, SSDs, optical disks, magneto-optical disks, CD-Rs, magnetic tapes, non-volatile memory cards, and ROMs.

In addition, the program code that realizes the functions described in this embodiment can be implemented in a wide range of program or script languages, such as assembler, C/C++, perl, Shell, PHP, Java (registered trademark), etc.

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

The matters explained in each of the above embodiments are noted below.

(Appendix 1)
A program for operating a computer (20) having a processor (29) and memories (25, 26), the memories (25, 26) storing format information (2022) of forms necessary for a user, who is a first business operator, to carry out a business, and model information (2025, 2026) of a workflow indicating a work process for creating the forms, the program causing the processor (29) to perform a first step (S1001) of accepting, from the user, input of transaction data (2021) relating to a commercial transaction between the user and a second business operator, who is a business partner of the user, and a second step (S1002) of generating information of a workflow relating to a commercial transaction with the second business operator by referring to the model information (2025, 2026) based on the transaction data (2021) accepted in the first step (S1001), and presenting the information. 2, S1003), a third step (S1005) of accepting instructions to change the transaction data (2021) and information related to the changes from the user who presented the workflow information in the second step (S1002, S1003), a fourth step (S1006, S1007) of determining whether or not the workflow information generated in the second step (S1002, S1003) needs to be changed based on the information related to the changes accepted in the third step (S1005), and if it is determined that a change is necessary, presenting the changed workflow information to the user, and a fifth step (S1100, S1101) of accepting an instruction to approve the change to the workflow information from the user who presented the workflow information changed in the fourth step (S1006, S1007) and changing the workflow information based on the accepted instruction to approve the changes.
(Appendix 2)
A program as described in Appendix 1, which in a fifth step (S1100, S1101) accepts an indication of non-approval of at least some of the changes to the workflow information from a user who presented the workflow information changed in the fourth step (S1006, S1007), and changes the model information (2025, 2026) based on the accepted indication of non-approval of the changes.
(Appendix 3)
The program described in Appendix 2, in which there are multiple second businesses, and in a fifth step (S1100, S1101), an instruction to not approve at least some of the changes to the workflow information is accepted from a user who presented the workflow information changed in the fourth step (S1006, S1007), and model information (2025, 2026) for a specific second business is changed based on the accepted instruction to not approve the changes.
(Appendix 4)
A program as described in Appendix 2 or 3, which in a fifth step (S1100, S1101) accepts an instruction of non-approval of at least some of the changes to the workflow information from a user who presented the workflow information changed in the fourth step (S1006, S1007), and changes model information (2025, 2026) relating to commercial transactions for a specific period based on the accepted instruction of non-approval of the changes.
(Appendix 5)
A program described in any one of appendices 1 to 4, in which in a fourth step (S1006, S1007), information about the changed workflow is presented to the user in a visible state, and at this time, the part of the information about the workflow that is related to the change is highlighted.
(Appendix 6)
A program described in any one of appendices 1 to 5, in which in a fourth step (S1006, S1007), information on the changed workflow is presented to the user in a visible state, and at this time, the part of the information on the workflow that is related to the change is displayed in a balloon.
(Appendix 7)
The program according to any one of appendices 1 to 6, further comprising a sixth step of presenting to the user information on the workflow changed in the fifth step (S1100, S1101).
(Appendix 8)
The information processing device (20) includes a processor (29) and a memory (25, 26), in which format information (2022) of forms necessary for a user, who is a first business operator, to carry out a business, and model information (2025, 2026) of a workflow indicating a work process for creating the forms are stored. The processor (29) performs the following steps: a first step (S1001) of accepting input of transaction data (2021) from the user regarding a commercial transaction between the user and a second business operator, who is a business partner of the user; a second step (S1002, S1003) of generating workflow information related to a commercial transaction with the second business operator by referring to the model information (2025, 2026) based on the transaction data (2021) accepted in the first step (S1001) and presenting the information; An information processing device (20) executes a third step (S1005) of accepting instructions to change transaction data (2021) and information related to the changes from a user who presented workflow information in steps (S1002, S1003), a fourth step (S1006, S1007) of determining whether or not the workflow information generated in the second step (S1002, S1003) needs to be changed based on the information related to the changes accepted in the third step (S1005), and if it is determined that a change is necessary, presenting the changed workflow information to the user, and a fifth step (S1100, S1101) of accepting instructions to approve the changes to the workflow information from the user who presented the workflow information changed in the fourth step (S1006, S1007), and changing the workflow information based on the accepted instruction to approve the changes.
(Appendix 9)
The method is executed by a computer (20) having a processor (29) and memories (25, 26), in which format information (2022) of forms necessary for a user, who is a first business operator, to carry out a business, and model information (2025, 2026) of a workflow indicating a work process for creating the forms are stored in the memory (25, 26), and the processor (29) performs a first step (S1001) of accepting, from the user, input of transaction data (2021) relating to a commercial transaction between the user and a second business operator, who is a business partner of the user, and a second step (S1002, S1003) of generating information of a workflow relating to a commercial transaction with the second business operator by referring to the model information (2025, 2026) based on the transaction data (2021) accepted in the first step (S1001) and presenting the information. a third step (S1005) of accepting an instruction to change the transaction data (2021) and information related to the change from the user who presented the workflow information in the second step (S1002, S1003); a fourth step (S1006, S1007) of determining whether or not the workflow information generated in the second step (S1002, S1003) needs to be changed based on the information related to the change accepted in the third step (S1005), and if it is determined that a change is necessary, presenting the changed workflow information to the user; and a fifth step (S1100, S1101) of accepting an instruction to approve the change to the workflow information from the user who presented the workflow information changed in the fourth step (S1006, S1007), and changing the workflow information based on the accepted instruction to approve the change.

1 Transaction management system, 10 10A 10B Terminal device, 20 Server, 25 Memory, 29 Processor, 30 Storage device, 80 Network, 150 Display, 170 Memory unit, 180 Control unit, 202 Memory unit, 203 Control unit, 2021 Transaction DB, 2022 Report format DB, 2023 Fixed phrase data, 2024 Report 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 Report data generation module, 2038 Transaction data process change module

Claims (9)

A program for operating a computer having 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 a business operation, and model information of a workflow indicating a work process for creating the forms,
The program causes the processor to:
A first step of accepting input of transaction data from the user regarding a commercial transaction between the user and a second business that is a business partner of the user;
a second step of generating information of the workflow related to the commercial transaction with the second business operator by referring to the model information based on the transaction data received in the first step, and presenting the information;
a third step of receiving an instruction to change the transaction data and information related to the change from the user who has presented the workflow information in the second step;
a fourth step of determining whether or not the information of the workflow generated in the second step needs to be changed based on the information related to the change received in the third step, and if it is determined that the change is necessary, presenting the changed information of the workflow to the user;
a fifth step of accepting an instruction to approve the change 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 change. The program according to claim 1, wherein in the fifth step, an instruction to not approve at least a part of the changes to the workflow information is accepted from the user who presented the workflow information changed in the fourth step, and the model information is changed based on the accepted instruction to not approve the changes. There are a plurality of second businesses,
3. The program according to claim 2, wherein in the fifth step, an instruction of non-approval of at least a portion of the changes to the workflow information is accepted from the user who presented the workflow information changed in the fourth step, and the model information for a specific second business operator is changed based on the accepted instruction of non-approval of the changes. The program according to claim 2, wherein in the fifth step, an instruction to not approve at least a part of the changes to the workflow information is accepted from the user who presented the workflow information changed in the fourth step, and the model information related to the commercial transaction for a specific period is changed based on the accepted instruction to not approve the changes. The program according to claim 1, wherein in the fourth step, the changed workflow information is presented to the user in a visible state, and at this time, the part of the workflow information related to the change is highlighted. The program according to claim 1, wherein in the fourth step, the changed workflow information is presented to the user in a visible state, and at this time, the part of the workflow information related to the change is displayed in a balloon. The program according to claim 1, further comprising a sixth step of presenting the workflow information changed in the fifth step to the user. An information processing device including 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 a business operation, and model information of a workflow indicating a work process for creating the forms,
The processor,
A first step of accepting input of transaction data from the user regarding a commercial transaction between the user and a second business that is a business partner of the user;
a second step of generating information of the workflow related to the commercial transaction with the second business operator by referring to the model information based on the transaction data received in the first step, and presenting the information;
a third step of receiving an instruction to change the transaction data and information related to the change from the user who has presented the workflow information in the second step;
a fourth step of determining whether or not the information of the workflow generated in the second step needs to be changed based on the information related to the change received in the third step, and if it is determined that the change is necessary, presenting the changed information of the workflow to the user;
an information processing device that executes a fifth step of accepting an instruction to approve the change 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 change. 1. A method implemented by a computer having a processor and a memory, comprising:
The memory stores format information of forms necessary for a user, who is a first business operator, to carry out a business operation, and model information of a workflow indicating a work process for creating the forms,
The processor,
A first step of accepting input of transaction data from the user regarding a commercial transaction between the user and a second business that is a business partner of the user;
a second step of generating information of the workflow related to the commercial transaction with the second business operator by referring to the model information based on the transaction data received in the first step, and presenting the information;
a third step of receiving an instruction to change the transaction data and information related to the change from the user who has presented the workflow information in the second step;
a fourth step of determining whether or not the information of the workflow generated in the second step needs to be changed based on the information related to the change received in the third step, and if it is determined that the change is necessary, presenting the changed information of the workflow to the user;
a fifth step of accepting an instruction for approval of the change 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 for approval of the change.