Program, information processor, and method

The sales management system addresses the complexity of transaction document management by generating workflow and form information based on user transactions, ensuring timely reminders and preventing task omissions, thereby improving user efficiency.

JP2024157014AInactive Publication Date: 2024-11-06FREEE

Patent Information

Application Number
JP2024137549
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2024-08-19
Publication Date
2024-11-06
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

Existing sales management systems face challenges in managing transaction documents and procedures, as they vary by industry and business partner, and require complex internal processes that are cumbersome for users to handle.

Method used

A sales management system that generates workflow and form information based on user transactions, determines necessary steps using stored workflow model information, and notifies users of deadlines and reminders to prevent task omission.

Benefits of technology

Facilitates efficient management of transaction workflows and document creation, preventing task omissions by providing necessary forms and timely reminders, thus enhancing user productivity.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024157014000001_ABST
    Figure 2024157014000001_ABST
Patent Text Reader

Abstract

To provide a program, an information processor, and a method that present a ledger sheet and notifies a user of a reminder in a transaction workflow.SOLUTION: A server of a sales management system executes the steps of: storing workflow model information indicating a business procedure and a ledger sheet for performing a business procedure for each procedure, and receiving input transaction information with another business operator; determining, on the basis of the workflow model information and past transaction information with another business operator, whether a procedure is necessary, and generating workflow information that manages information including the procedure determined to be necessary according to a determination result of the received transaction; generating a ledger sheet format required for transaction related to the transaction information received for each procedure generated on the basis of the ledger sheet; and presenting the workflow information and ledger sheet information. The server further executes the steps of: receiving correction information for the input workflow information; correcting, on the basis of the received correction information, the workflow information; and generating, on the basis of the workflow information, a reminder according to a deadline for the procedure and notifying of it.SELECTED DRAWING: Figure 7
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

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

[0002] 2. Description of the Related Art Sales management services that are used by users who sell products to create various documents such as quotations and delivery notes required for selling products and to understand the status of products are provided, for example, as Web services.

[0003] As a technology for a transaction management system, Patent Document 1 discloses a technology for a transaction management system that is easily accessible by both an orderer and a seller and allows shared use of transaction data. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent Publication No. 2021-009505 Summary of the Invention [Problem to be solved by the invention]

[0005] By the way, the forms required for product sales management usually differ depending on the type of business, the business partner, etc. Also, depending on the business partner and the content of the transaction, detailed statements must be attached, and various forms must be created and managed. Furthermore, the internal procedures within the user company also vary from company to company. The management of such transaction procedures and forms can be cumbersome for the person in charge.

[0006] Therefore, in this disclosure, a technology will be described that presents documents required for business in a transaction workflow and notifies reminders as necessary. [Means for solving the problem]

[0007] According to an embodiment of the present disclosure, there is provided a program to be executed by a computer having a processor and a memory, the memory storing workflow model information indicating each procedure for a user who is a business operator to perform a task, and form format information for performing the task for each procedure, and the program causes the processor to execute the following steps: accepting information regarding the user's transactions with other business operators input by the user; determining whether each procedure is necessary based on the workflow model information and information regarding transactions with other business operators that the user has performed in the past and saved, and generating workflow information for managing information regarding the accepted transaction including each procedure determined to be necessary according to the result of the determination; generating form information required for the transaction related to the information regarding the accepted transaction for each generated step based on the form format information; presenting the workflow information and the form information to the user; accepting correction information for the workflow information input by the user; correcting the workflow information based on the received correction information; and generating reminder information according to the deadline for each procedure based on the workflow information and notifying the user. Effect of the Invention

[0008] According to the present disclosure, by presenting documents necessary for business operations in a transaction workflow and sending reminders as necessary, it is possible to prevent users from missing out on tasks related to a transaction or missing out on taking action toward a business partner. [Brief description of the drawings]

[0009] [Figure 1] 1 is a block diagram showing the overall configuration of a sales management system 1 according to a first embodiment. [Diagram 2] 2 is a block diagram showing the functional configuration of a terminal device 10 constituting the sales management system 1. FIG. [Diagram 3] 2 is a block diagram showing the functional configuration of a server 20 constituting the sales management system 1. FIG. [Figure 4]2 is a diagram showing an example of the data structure of a workflow model database 2021 stored in the server 20 constituting the sales management system 1. FIG. [Diagram 5] 2 is a diagram showing an example of the data structure of a form format database 2022 stored in the server 20 constituting the sales management system 1. FIG. [Figure 6] 2 is a diagram showing an example of a data structure of a workflow database 2023 stored in a server 20 constituting a sales management system 1. FIG. [Figure 7] 13 is a flowchart showing an example of a flow of a workflow generation process performed by the sales management system 1. [Figure 8] 13 is a flowchart showing an example of a flow of a workflow correction process performed by the sales management system 1. [Figure 9] 11 is a flowchart showing an example of a flow of a reminder process performed by the sales management system 1. [Figure 10] 11 is a diagram showing an example of a workflow screen displayed on the terminal device 10. FIG. [Figure 11] 1 is a diagram showing an example of a screen of a form displayed on a terminal device 10. FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Hereinafter, an embodiment of the present disclosure will be described with reference to the drawings. In the following description, the same components are denoted by the same reference numerals. Their names and functions are also the same. Therefore, detailed description thereof will not be repeated.

[0011] <Summary> The sales management system according to the present disclosure will be described below. The sales management system according to the present disclosure is a system for generating and managing workflow information indicating procedures for carrying out business operations for transactions between a corporation or a sole proprietor and another business. The sales management system according to the present disclosure is a system for generating and managing form information for carrying out business operations for each procedure. When transactions are carried out between businesses, such as companies or sole proprietors, there are many cases in which procedures such as quotation, ordering, receiving an order, delivery, and billing are carried out, and it is necessary to issue forms such as quotation and purchase order forms for each of these procedures to carry out the transaction. The sales management system according to the present disclosure is a system for managing procedures such as quotation and ordering as a workflow and providing a service that supports the issuance of forms required for each procedure. The sales management system according to the present disclosure is a system provided as a Web service, for example, by a cloud server or the like, by so-called SaaS (Software as a Service).

[0012] Incidentally, many of the above-mentioned transaction processes must be completed by a certain deadline. For this reason, it is important to manage the deadline for completing the process. However, such processing deadlines are not necessarily set uniformly, and deadlines for transactions in particular often differ depending on the relationship with the trading partner. Furthermore, the internal procedures within the companies that process transactions also vary from company to company.

[0013] In addition, the documents such as quotations and purchase orders issued in the above-mentioned transaction processes usually differ depending on the industry, business partner, etc. Also, depending on the business partner and transaction content, it may be necessary to attach a detailed statement, and various documents must be created and managed.

[0014] Therefore, the sales management system according to the present disclosure stores workflow model information, and when it receives transaction information from a user, it generates workflow information by determining whether each procedure is necessary based on the workflow model information. For example, if a specific procedure is unnecessary depending on the trading partner, it generates workflow information by omitting that procedure for the transaction with that trading partner.

[0015] In addition, the sales management system according to the present disclosure stores form format information for each procedure, and when transaction information is received from a user, generates form information required for the received transaction for each procedure of the generated workflow information. For example, form information is information such as an estimate, a purchase order, etc.

[0016] Furthermore, the sales management system according to the present disclosure notifies the user of reminder information according to the deadline for each procedure based on the workflow information.

[0017] With the above configuration, workflow information and form information are generated, which makes it easier for users to manage their work regarding transactions and makes it possible to prevent missed tasks. Also, reminder information according to the deadline for each step is notified to the user, which makes it possible to prevent users from missing out on taking action with clients regarding transactions. This makes it easier to manage tasks in sales management and makes it possible to prevent missed tasks.

[0018] <Embodiment 1> The following describes the sales 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.

[0019] <1 Overall configuration of sales management system 1> FIG. 1 is a block diagram showing the overall configuration of a sales management system 1 according to the first embodiment. As shown in FIG. 1, the sales 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 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 on 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.

[0020] The terminal device 10 is a device operated by each user. Here, the user is a person who uses the terminal device 10 to perform transaction processing (workflow management, form creation), which is a function of the sales management system 1, and is, for example, a person in charge of a company that is a business operator, a sole proprietor, etc. The terminal device 10 is realized by a stationary PC (Personal Computer), a laptop PC, etc. Alternatively, the terminal device 10 may be, for example, a tablet compatible with a mobile communication system, a mobile terminal such as a smartphone, etc.

[0021] 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 compatible with communication standards such as 4G, 5G, and LTE (Long Term Evolution), and a wireless LAN router 82 compatible with 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.

[0022] The communication IF 12 is an interface for inputting and outputting signals so that the terminal device 10 can communicate with an external device. 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 an input operation 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 a program and data processed by the program, 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, and is, for example, a flash memory or a HDD (Hard Disc Drive). The processor 19 is hardware for executing an instruction set described in a program, and is composed of an arithmetic unit, a register, a peripheral circuit, etc.

[0023] The server 20 is a device that manages various information related to transaction processing by the user business operator, such as workflow information and form information. The server 20 stores workflow model information indicating each procedure for the user to perform the business, and form format information for performing the business for each procedure. When the server 20 receives information on a transaction with another business operator from the user, it generates workflow information related to the received transaction, generates form information required for the transaction, and receives correction information for the workflow information. The server 20 also generates reminder information according to the deadline for each procedure based on the workflow information, and notifies the user.

[0024] The server 20 is a computer connected to a 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.

[0025] The communication IF 22 is an interface for inputting and outputting signals so that the server 20 can communicate with an external device. The input / output IF 23 functions as an interface with an input device for receiving an input operation 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 an instruction set described in a program, and is composed of an arithmetic unit, a register, a peripheral circuit, etc.

[0026] <1.1 Configuration of the terminal device 10> FIG. 2 is a block diagram showing a functional configuration of the terminal device 10 constituting the sales management system 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 the respective antennas, an operation reception unit 130 (including a keyboard 131 and a mouse 132), a voice processing unit 140, a microphone 141, a speaker 142, a display 150, a storage unit 160, and a control unit 170. 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 terminal device 10 shown in FIG. 2 will be described as a mobile terminal such as a tablet or a smartphone compatible with a mobile communication system, but may be a stationary PC (Personal Computer) or a laptop PC.

[0027] The antenna 111 emits a signal generated by the terminal device 10 as a radio wave. The antenna 111 also receives a radio wave from space and provides the received signal to the first wireless communication unit 121.

[0028] The antenna 112 radiates a signal generated 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 radio communication unit 122.

[0029] The first wireless communication unit 121 performs modulation / 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 / 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, a Received Signal Strength Indicator (RSSI) calculation circuit, a Cyclic Redundancy Check (CRC) 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 the received signals to the control unit 170.

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

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

[0032] 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 an object selected on the screen and information indicating that a button has been pressed to the control unit 170 as input signals.

[0033] The audio processing unit 140 modulates and demodulates an audio signal. The audio processing unit 140 modulates a signal provided from the microphone 141 and provides the modulated signal to the control unit 170. The audio processing unit 140 also provides the audio signal to the speaker 142. The audio processing unit 140 is realized, for example, by a processor for audio processing. The microphone 141 accepts audio input and provides an audio signal corresponding to the audio input to the audio processing unit 140. The speaker 142 converts the audio signal provided from the audio processing unit 140 into audio and outputs the audio to the outside of the terminal device 10.

[0034] Display 150 displays data such as images, videos, and text under the control of control unit 170. Display 150 is realized by, for example, an LCD (Liquid Crystal Display) or an organic EL (Electro-Luminescence) display.

[0035] Storage unit 160 is configured with memory 15, such as a flash memory, and storage unit 16, and stores data and programs used by terminal device 10. In one aspect, storage unit 160 stores user information 161.

[0036] The user information 161 is information about a user who uses the terminal device 10 to perform transaction processing (workflow management, form creation), which is a function of the sales management system 1. The user information includes information for identifying the user (user ID), the name or title of the business operator or person in charge, and the like.

[0037] The control unit 170 is constituted by, for example, the processor 19, and controls the operation of the terminal device 10 by reading a program stored in the storage unit 160 and executing instructions included in the program. The control unit 170 fulfills the functions of an input operation receiving unit 171, a transmission / reception unit 172, a notification control unit 173, and a data processing unit 174 by operating in accordance with a program (not shown) that is an application that is stored in advance in the storage unit 160 of the terminal device 10 and installed, for example.

[0038] The input operation receiving unit 171 performs processing for receiving input operations by a user via an input device such as the keyboard 131 .

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

[0040] The notification control unit 173 performs a process of presenting information to the user. The notification control unit 173 performs a process of causing the display 150 to display a display image, a process of causing the speaker 142 to output a sound, and the like.

[0041] The data processing unit 174 performs calculations on the data that the terminal device 10 accepts as input in accordance with a program, and outputs the calculation results to a memory or the like.

[0042] <1.2 Functional configuration of server 20> 3 is a block diagram showing the functional configuration of the server 20 constituting the sales management system 1. As shown in FIG. 3, the server 20 fulfills the functions of a communication unit 201, a storage unit 202, and a control unit 203.

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

[0044] The storage 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 storage unit 202 stores a workflow model database 2021, a form format database 2022, a workflow database 2023, and the like.

[0045] The workflow model database 2021 is a database for holding model information of a workflow indicating each procedure for a user who is a business operator to carry out a business, which is the basis of the workflow information generated by the sales management system 1. Details will be described later.

[0046] The form format database 2022 is a database for holding form format information for carrying out business procedures on a step-by-step basis, which is the basis for form information generated by the sales management system 1. Details will be described later.

[0047] The workflow database 2023 is a database for holding workflow information indicating procedures for carrying out work regarding transactions that are managed by the sales management system 1. Details will be described later.

[0048] The control unit 203 performs functions indicated in various modules, such as a receiving control module 2031, a transmitting control module 2032, a transaction information reception module 2033, a workflow generation module 2034, a report information generation module 2035, a presentation module 2036, a progress information acquisition module 2037, a workflow correction module 2038, and a reminder notification module 2039, by the processor 29 of the server 20 performing processing according to a program.

[0049] The reception control module 2031 controls the process in which the server 20 receives a signal from an external device in accordance with a communication protocol.

[0050] The transmission control module 2032 controls the process in which the server 20 transmits signals to external devices in accordance with a communication protocol.

[0051] The transaction information receiving module 2033 controls the process of receiving information about transactions between the user and other businesses, input by the user of the sales management system 1 through the operation of the terminal device 10 by the user. The transaction information received by the transaction information receiving module 2033 is, for example, information about the entities related to the transaction, such as the orderer, the orderee, the purchaser, information about the contents of the case, delivery date, amount, etc., and may include the deliverables and the deliverables if they are manageable as electronic information, such as reports and design documents. The entities related to the transaction may be either corporations or individuals, as long as they are entities related to the transaction, such as the orderer, the orderee, the purchaser, etc.

[0052] The transaction information receiving module 2033 may receive information related to a transaction, including information on deadlines for each procedure in the transaction, specifically, procedures such as quotation, ordering, receiving an order, delivery, and billing. The deadlines for procedures are information generated together with the workflow by the workflow generating module 2034, which will be described later, but may also be input by the user. For example, if a specific procedure needs to be completed earlier than the normal deadline, the input of the deadline for that procedure may be received from the user and reflected in the workflow.

[0053] The workflow generation module 2034 controls the process of determining whether each procedure is necessary based on the workflow model information stored in the workflow model database 2021 and information on transactions with other businesses that have been performed by the user in the past and stored. The workflow generation module 2034 determines whether each procedure in a transaction stored in the workflow model information is necessary, for example, based on information on transactions that the user has previously input to the sales management system 1. Specifically, the workflow generation module 2034 refers to the business partner of the transaction, the time of the transaction, the deadline, etc., recognizes patterns such as a procedure being omitted under certain conditions (for example, the creation of a purchase order is omitted and the transaction content is executed), and determines whether each procedure in the transaction is necessary.

[0054] Furthermore, the workflow generation module 2034 controls the process of generating workflow information for managing information including each procedure determined to be necessary according to the result of the above-mentioned determination, regarding the transaction accepted by the transaction information acceptance module 2033. At this time, the workflow generation module 2034 may generate the workflow information based on workflow model information stored in the workflow model database 2021. The workflow generation module 2034 generates workflow information indicating procedures such as quotation, ordering, receiving, delivery, and billing for the accepted transaction, for example.

[0055] The workflow generation module 2034 may generate workflow information including information on deadlines for each procedure in a transaction, specifically, procedures such as quotation, ordering, receiving an order, delivery, and billing. At this time, the workflow generation module 2034 may generate the workflow information based on deadline information (as a model) stored in workflow model information stored in the workflow model database 2021. Furthermore, when the transaction information receiving module 2033 receives a deadline for a procedure, the workflow generation module 2034 reflects the deadline in the workflow.

[0056] The workflow generation module 2034 stores the generated workflow information in the workflow database 2023 .

[0057] The form information generation module 2035 controls the process of generating form information required for a transaction related to information on a transaction accepted by the transaction information acceptance module 2033 for each step in the workflow generated by the workflow generation module 2034. At this time, the form information generation module 2035 generates form information required for the transaction based on form format information stored in the form format database 2022. Specifically, the form information required for the transaction is information on forms such as estimates, purchase orders, and invoices issued for each step. There is no particular limitation on the data format of the file for the form information, and any known data format that can describe the location of data, such as PDF (Portable Document Format), Word, and XML (eXtensible Markup Language), can be suitably applied.

[0058] Specifically, the form information generation module 2035 applies necessary information to each item defined in the form format information stored in the form format database 2022, specifically, items such as the trading partner (e.g., estimate delivery destination), issue date, amount, etc. At this time, the form information generation module 2035 may extract information on the necessary items from the information on the transaction accepted by the transaction information acceptance module 2033 and apply it.

[0059] The form information generation module 2035 stores the generated form information in association with the workflow database 2023 (it may be stored directly or a link to the storage destination may be stored).

[0060] The presentation module 2036 controls the process of presenting to the user the workflow information generated by the workflow generation module 2034 and the form information generated by the form information generation module 2035. The presentation module 2036 transmits the workflow information and the form information to the terminal device 10 and presents them to the user by displaying them on the display 150. The presentation module 2036 may illustrate the workflow information using a line diagram or may display it as a list.

[0061] The progress information acquisition module 2037 controls the process of acquiring transaction progress information for deadline information included in the workflow information generated by the workflow generation module 2034 (modified by the workflow modification module 2038 described below). The progress information acquisition module 2037 acquires transaction progress information based on actual results for a transaction accepted by the transaction information acceptance module 2033, for example.

[0062] Furthermore, the progress information acquisition module 2037 may update the deadline of each procedure based on the acquired transaction progress information. At this time, the progress information acquisition module 2037 may update each procedure to complete if it is completed based on the acquired transaction progress information. The progress information acquisition module 2037 may, for example, update the status information of each procedure stored in the workflow database 2023 and set the status information of a completed procedure to complete. Furthermore, the progress information acquisition module 2037 may update the deadline of each procedure to a predetermined date and time in the future (for example, one week later) if it is not completed based on the acquired transaction progress information.

[0063] Specifically, the progress information acquisition module 2037 may accept input of transaction progress information from a user through the user's operation of the terminal device 10. The progress information acquisition module 2037 accepts input of the actual completion date for procedures such as quotation, ordering, receiving, delivery, and billing.

[0064] Furthermore, specifically, the progress information acquisition module 2037 may acquire transaction progress information from information about a user transmitted from an external server that manages information about the user. The external server that manages information about the user is, for example, a server that provides a service that manages external schedule information, attendance information, and the like, and may be a server that manages various information used in a schedule management application and attendance management application used by the user on the terminal device 10. The progress information acquisition module 2037 may acquire transaction progress information by linking information from such an external server.

[0065] The workflow modification module 2038 controls the process of accepting modification information for the workflow information input by the user of the sales management system 1 through the operation of the terminal device 10 by the user. The workflow information transmitted by the presentation module 2036 is presented in the terminal device 10, and input of modifications to this workflow information is accepted from the user and transmitted to the server 20. The workflow modification module 2038 accepts input information for modifications to the workflow information input by the user.

[0066] Furthermore, the workflow modification module 2038 controls the process of modifying the workflow information based on the modification information for the received workflow information. The workflow modification module 2038 reflects the modification content for the workflow information input by the user in the workflow information stored in the workflow database 2023.

[0067] Modifications to workflow information accepted by the workflow modification module 2038 include modifications to add, change, delete, etc., procedures to the workflow information generated by the workflow generation module 2034. Modifications to workflow information also include modifications to change deadline information for each procedure included in the workflow information generated by the workflow generation module 2034.

[0068] The reminder notification module 2039 controls the process of generating reminder information according to the deadline of each procedure based on the workflow information generated by the workflow generation module 2034 (modified by the workflow modification module 2038) and notifying the user of the deadline. Specifically, the reminder notification module 2039 generates reminder information for deadlines of procedures such as quotation, ordering, receiving an order, delivery, and billing, transmits the information to the terminal device 10, and notifies the user by displaying the information on the display 150. The reminder information may be, for example, information notifying that the deadline of each procedure is approaching, information notifying the deadline by which work should be started in order to complete each procedure by the deadline, or information notifying the deadline by which a business partner should be contacted for each procedure.

[0069] The reminder notification module 2039 may generate reminder information and notify the user based on deadline information of a procedure accepted by the transaction information acceptance module 2033. The reminder notification module 2039 may also generate reminder information based on deadline information of a procedure generated by the workflow generation module 2034 and notify the user.

[0070] Furthermore, the reminder notification module 2039 may generate reminder information and notify the user before a predetermined date and time of the deadline related to the deadline information, or after the deadline has passed. Specifically, the reminder notification module 2039 may notify the user of the reminder information before a predetermined date and time of the deadline (e.g., three days before), or may notify the user of the reminder information after the deadline has passed (e.g., one day after the deadline).

[0071] Also, for example, the workflow database 2023 may store (record) man-month information required to execute each procedure, which is included in the workflow information, and the reminder notification module 2039 may notify the user of reminder information including information on the deadline for starting each procedure in the workflow information, based on the deadline information and the man-month information. Specifically, based on man-month information that a certain procedure requires 0.1 man-months (2 days), the reminder notification module 2039 may notify the user of the reminder information 0.1 man-months (2 days) before the deadline, or may notify the user of the reminder information including a certain grace period.

[0072] In addition, in a certain aspect, the control unit 203 may generate workflow model information associated with a user based on information related to the user's past transactions. Specifically, the workflow model information stored in the workflow model database 2021 is stored (stored) in association with each user. The control unit 203 reflects information related to the user's past transactions in this workflow model information. At this time, the control unit 203 may generate workflow model information associated with a user based on information including the user's attribute information.

[0073] At this time, a machine learning model generated from information on past transactions of the user may be generated as the model information of the workflow. This machine learning model may be generated by machine learning performed as a function of the control unit 203, or a machine learning model generated as a result of machine learning performed by another device may be acquired. The machine learning performed to generate the machine learning model may be supervised machine learning using predetermined teacher data, unsupervised machine learning, or deep learning. Furthermore, the evaluation result by the machine learning model may be later compared with the result by the user's input, and a process of merging the learning result by further machine learning may be performed.

[0074] <2 Data Structure> Fig. 4 is a diagram showing an example of the data structure of a workflow model database 2021 stored by the server 20 constituting the sales management system 1. Fig. 5 is a diagram showing an example of the data structure of a form format database 2022 stored by the server 20 constituting the sales management system 1. Fig. 6 is a diagram showing an example of the data structure of a workflow database 2023 stored by the server 20 constituting the sales management system 1.

[0075] As shown in FIG. 4, each record of the workflow model database 2021 includes an item "model ID", an item "model pattern name", an item "business type of use", an item "procedure information", and the like.

[0076] The item "Model ID" is information for identifying each piece of workflow model information that is the basis of workflow information. Since there are multiple pieces of workflow model information depending on, for example, model patterns and business types (user attributes) as described below, the item "Model ID" is used to identify them.

[0077] The item "Model Pattern Name" is a name for explaining the model pattern of a workflow model information that is classified into multiple model patterns. For example, the item "Model Pattern Name" stores information such as "Order - Invoice 2 months", which indicates that it takes two months from ordering a transaction to invoicing.

[0078] The item "Business Type" is a name for explaining the business type of the workflow model information, which is classified into multiple business types (user attributes). For example, the item "Business Type" stores information such as the business type of the user who is the transaction subject (e.g., retail, wholesale, manufacturing).

[0079] The item "Procedure information" is information on procedures stored as model information of a workflow, and specifically includes the items "Action", "Required procedures", "Required man-hours", "Format ID used", "Deadline", etc. The item "Procedure information" stores model information on actions from business partners and procedures required to respond to those actions, for example in chronological order, linked to the model information of a workflow identified by the item "Model ID".

[0080] The item "action" is a name indicating an action from a business partner that is managed as workflow model information. For example, the item "action" stores information such as "quote request" indicating that a request for a quote has been received from a business partner.

[0081] The item "Required Procedure" is a name indicating a procedure required to respond to an action from a business partner, which is managed as workflow model information. For example, the item "Required Procedure" stores information such as "Create Estimate", which indicates the creation of an estimate.

[0082] The item "required man-hours" is information indicating man-month information required to execute a procedure for responding to an action from a business partner, which is managed as workflow model information.

[0083] The item "Used report format ID" is information for identifying format information for generating a report required for a transaction for each procedure required to respond to an action from a business partner, which is managed as workflow model information.

[0084] The item "deadline" is information that indicates a deadline for responding to an action from a business partner, which is managed as workflow model information.

[0085] As shown in FIG. 5, each record of the form format database 2022 includes an item "form format ID", an item "form name", an item "form layout data", and the like.

[0086] The item "Report Format ID" is information that identifies format information for generating a report required for a transaction for each procedure required to respond to an action from a business partner, and corresponds to the item "Report Format ID Used" in the Workflow Model Database 2021.

[0087] The item "Report Name" is the name of the report required for the transaction for each procedure required to respond to an action from a business partner. For example, the item "Report Name" stores information such as "Quote Pattern 1," which is the name of the report.

[0088] The item "Form Layout Data" is layout data of forms required for a transaction for each procedure required to respond to an action from a business partner. The item "Form Layout Data" may store file data directly or a link to the storage destination. There are no particular limitations on the data format of the file data, and any data format that can describe the position of data, such as PDF (Portable Document Format), Word, or XML (eXtensible Markup Language), may be used.

[0089] As shown in FIG. 6, each record of the workflow database 2023 includes an item "user ID", an item "user name", an item "transaction name", an item "workflow information", and the like.

[0090] The item “user ID” is information for identifying each user of the sales management system 1.

[0091] The item “user name” is the name or title of a user of the sales management system 1.

[0092] The item “transaction name” is the name of a transaction related to a workflow that is managed by the sales management system 1.

[0093] The item "Workflow information" is information on the workflow of a transaction that is managed by the sales management system 1, and specifically includes an item "action", an item "occurrence date", an item "response procedure", an item "response date", etc. The item "workflow information" stores information on actions from business partners and procedures required to respond to those actions, for example in chronological order, linked to a user identified by the item "user ID".

[0094] The item “action” is a name indicating an action from a business partner that is managed as a workflow, and corresponds to the item “action” in the workflow model database 2021.

[0095] The item "Occurrence Date" is the date on which an action from a business partner, which is managed as a workflow, actually occurred.

[0096] The item “Response Procedure” is a name indicating a procedure required to respond to an action from a business partner, which is managed as a workflow, and corresponds to the item “Required Procedure” in the Workflow Model Database 2021.

[0097] The item "Response Date" is the date on which an action from a business partner, which is managed as a workflow, was actually responded to.

[0098] 6, when a date is stored in the item "Response Date", it indicates that the response to the action has been completed, and when no date is stored, it indicates that the response to the action has not been completed. In this way, the item "Response Date" also serves as status information for each step, but the status information for each step may be configured to be stored separately in the workflow database 2023.

[0099] The workflow generation module 2034 of the server 20 adds a record to the workflow database 2023 in association with generating the workflow information. The form information generation module 2035 updates the item "workflow information" in the workflow database 2023 in association with generating the form information.

[0100] <3 operations> Hereinafter, the workflow generation process, workflow correction process, and remind process performed by the sales management system 1 in the first embodiment will be described with reference to FIGS.

[0101] FIG. 7 is a flowchart showing an example of a flow of a workflow generation process performed by the sales management system 1.

[0102] In step S111, the input operation receiving unit 171 of the terminal device 10 receives from the user an operation to input a user ID and password for authentication required to use the services of the sales management system 1. The transmitting / receiving unit 172 transmits the received user ID and password, and the user information 161 to the server 20. The transmitting / receiving unit 172 of the terminal device 10 receives authentication completion information and service screen display information transmitted from the server 20. The notification control unit 173 causes the display 150 to display the received service screen display information.

[0103] In step S121, the server 20 receives the user ID and password via the communication unit 201, confirms that the user ID and password of the user are valid, and performs a predetermined authentication. If the user ID and password are valid, the server 20 transmits authentication completion information and the transaction information receiving module 2033 of the server 20 transmits display information of the service screen to the terminal device 10 via the communication unit 201.

[0104] In step S112, the input operation receiving unit 171 of the terminal device 10 receives an input of information related to a transaction between the user and another business through an operation by the user. The transmitting / receiving unit 172 transmits the input information related to the transaction to the server 20.

[0105] In step S122, the transaction information receiving module 2033 of the server 20 receives information on transactions with other businesses transmitted from the terminal device 10 via the communication unit 201. The information on the transaction is, for example, information on the parties involved in the transaction, such as the orderer, the order recipient, the purchaser, etc., information on the contents of the case, the delivery date, the amount, etc., but may also include information on the deadline for each step in the transaction.

[0106] In step S123, the workflow generation module 2034 of the server 20 judges whether each procedure is necessary based on the workflow model information and information on transactions with other businesses that have been saved by the user in the past. In addition, in step S123, the workflow generation module 2034 generates workflow information that manages information including each procedure that has been judged to be necessary according to the result of the judgment. In step S123, for example, based on the workflow model information stored in the workflow model database 2021 and information on the user's past transactions with other businesses, the necessity of each procedure in the transaction, specifically, procedures such as estimate, order, receipt, delivery, and billing, is judged, the procedures judged to be unnecessary are omitted, and workflow information is generated for each procedure that has been judged to be necessary.

[0107] In step S124, the form information generation module 2035 of the server 20 generates form information required for the transaction related to the transaction-related information accepted in step S122 for each step in the workflow generated in step S123. In step S124, the form information required for the transaction is generated based on, for example, form format information stored in the form format database 2022.

[0108] In step S125, the presentation module 2036 of the server 20 transmits the workflow information generated in step S123 and the form information generated in step S124 to the terminal device 10 via the communication unit 201.

[0109] In step S115, the transmitting / receiving unit 172 of the terminal device 10 accepts the workflow information and the form information transmitted from the server 20. The notification control unit 173 causes the display 150 to display the accepted workflow information and the form information.

[0110] As described above, the sales management system 1 stores workflow model information, and when it receives transaction-related information from a user, it determines whether each step is necessary based on the workflow model information and generates workflow information. For example, if a specific step is not necessary depending on the trading partner, it omits that step and generates workflow information for the transaction with that trading partner. In addition, it stores form format information for each step, and when it receives transaction-related information from a user, it generates form information required for the received transaction for each step of the generated workflow information. The generated workflow information and form information are sent to the terminal device 10 and presented to the user. As a result, since the workflow information and form information are generated, it becomes easier for the user to manage work related to the transaction and it becomes possible to prevent omissions of work.

[0111] FIG. 8 is a flowchart showing an example of a flow of a workflow correction process performed by the sales management system 1.

[0112] In step S211, the input operation receiving unit 171 of the terminal device 10 receives input of correction information for the workflow information through an operation by the user. The transmitting / receiving unit 172 transmits the input correction information for the workflow information to the server 20.

[0113] In step S221, the workflow correction module 2038 of the server 20 accepts, via the communication unit 201, correction information for the workflow information transmitted from the terminal device 10.

[0114] In step S222, the workflow modification module 2038 of the server 20 modifies the workflow information based on the modification information for the workflow information received in step S221. Modifications to the workflow information include modifications to add, change, delete, etc., a procedure to the workflow information, or modifications to change information on the deadline for each procedure included in the workflow information.

[0115] In step S223, the presentation module 2036 of the server 20 transmits the workflow information corrected in step S222 to the terminal device 10 via the communication unit 201.

[0116] In step S213, the transmitting / receiving unit 172 of the terminal device 10 accepts the corrected workflow information transmitted from the server 20. The notification control unit 173 causes the display 150 to display the accepted corrected workflow information.

[0117] As described above, the sales management system 1 accepts input for correction of the presented workflow information and corrects the workflow information based on the input content. This makes it easy to correct the workflow information, facilitating the user's work management regarding transactions and making it possible to prevent omissions in work.

[0118] FIG. 9 is a flowchart showing an example of a flow of the reminding process performed by the sales management system 1.

[0119] In step S321, the progress information acquisition module 2037 of the server 20 acquires transaction progress information for the deadline information included in the workflow information generated in step S123 or modified in step S222.

[0120] In step S322, the reminder notification module 2039 of the server 20 determines whether or not a reminder is necessary according to the deadline of each procedure, based on the workflow information generated in step S123 or corrected in step S222.

[0121] In step S323, if it is determined in step S322 that a reminder is necessary, the reminder notification module 2039 of the server 20 generates reminder information according to the deadline for each procedure, and transmits the reminder information to the terminal device 10 via the communication unit 201. Specifically, the reminder information is a reminder about the deadline for procedures such as quotation, ordering, receiving an order, delivery, and billing.

[0122] In step S313, the transmitting / receiving unit 172 of the terminal device 10 receives the reminding information transmitted from the server 20. The notification control unit 173 causes the display 150 to display the received reminding information.

[0123] As described above, the sales management system 1 generates reminder information according to the deadline of a procedure and notifies the user of the reminder information. This makes it possible to prevent the user from missing out on taking action regarding a transaction with a business partner.

[0124] <4 Screen example> Hereinafter, examples of a workflow screen and a form screen according to the sales management system 1 will be described with reference to FIGS.

[0125] Fig. 10 is a diagram showing an example of a workflow screen displayed on the terminal device 10. The example of the screen in Fig. 10 shows an example of a screen in a state where the workflow information generated by the workflow generation module 2034 is transmitted to the terminal device 10 by the presentation module 2036 and displayed on the display 150. This corresponds to step S115 in Fig. 7.

[0126] As shown in Fig. 10, a window 1031 is displayed on the display 150 of the terminal device 10. This window 1031 displays workflow information 1031a that is generated by the workflow generation module 2034 and transmitted to the terminal device 10. In the example shown in Fig. 10, each procedure constituting the workflow (e.g., creating an estimate) is displayed in a procedure display field 1031b, and the flow of each procedure is displayed by an arrow 1031c.

[0127] In the workflow information 1031a, steps such as "Create an estimate" and "Create an invoice" are displayed as examples in the step display field 1031b, and the flow of each step is displayed with arrows 1031c. This makes it possible to grasp the transaction steps in sales management at a glance.

[0128] Fig. 11 is a diagram showing an example of a form screen displayed on the terminal device 10. The example of the screen in Fig. 11 shows an example of a screen in a state where the form information generated by the form information generation module 2035 is transmitted to the terminal device 10 by the presentation module 2036 and displayed on the display 150. This corresponds to step S115 in Fig. 7.

[0129] As shown in Fig. 11, a window 1031 is displayed on the display 150 of the terminal device 10. This window 1031 displays form information 1032a that has been generated by the form information generation module 2035 and transmitted to the terminal device 10. In the example shown in Fig. 11, an invoice is displayed as the form information 1032a, and each item of the invoice is displayed as item 1032b.

[0130] An invoice, which is an example of form information 1032a, displays "billing name," "billing address," "amount," and the like as examples of items 1032b. These items are items originally written in the form format stored in the form format database 2022, or information about the transaction accepted by the transaction information acceptance module 2033, or information acquired from other information (for example, today's date), etc. This makes it possible for the user to reduce the effort required to create forms.

[0131] <Summary> As described above, according to this embodiment, workflow model information is stored, and when transaction-related information is received from a user, the necessity of each step is determined based on the workflow model information to generate workflow information. In addition, form format information is stored for each step, and when transaction-related information is received from a user, form information required for the received transaction is generated for each step of the generated workflow information. The generated workflow information and form information are presented to the user. Therefore, since the workflow information and form information are generated, it becomes easier for the user to manage work related to transactions and create forms, and it becomes possible to prevent work omissions. This makes it easier to manage tasks in sales management and makes it possible to prevent task omissions.

[0132] Furthermore, according to this embodiment, input for correction of the presented workflow information is accepted, and the workflow information is corrected based on the input content. Therefore, since the workflow information can be easily corrected, it becomes easier for the user to manage the work related to the transaction, and it becomes possible to prevent the omission of the work. This makes it easier to manage the tasks in the sales management, and makes it possible to prevent the omission of the tasks.

[0133] Furthermore, according to this embodiment, reminder information according to the deadline for each step is notified to the user based on the workflow information. This makes it possible to prevent the user from missing out on necessary work for the transaction steps. This makes it possible to prevent the user from missing out on taking action regarding the transaction with the trading partner.

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

[0135] <Additional Notes> The matters described in the above embodiments will be supplemented below.

[0136] (Supplementary Note 1) A program to be executed by a computer having a processor 29 and a memory 25, the memory 25 storing workflow model information (2021) indicating each procedure for a user who is a business operator to carry out a business, and form format information (2022) for carrying out the business for each procedure, the program causing the processor 29 to receive information input by the user regarding transactions with other business operators by the user (S122), determine whether each procedure is necessary based on the workflow model information and information regarding transactions with other business operators that the user has carried out in the past and stored, and determine whether each procedure is necessary based on the result of the determination regarding the received transaction. a step (S123) of generating workflow information for managing information including each of the generated procedures; a step (S124) of generating, for each of the generated procedures, based on the format information of the procedure, form information required for a transaction related to information relating to the accepted transaction; a step (S125) of presenting the workflow information and form information to a user; a step (S221) of accepting correction information for the workflow information input by the user; a step (S222) of correcting the workflow information based on the accepted correction information; and a step (S323) of generating reminder information according to the deadline for each procedure based on the workflow information and notifying the user.

[0137] (Appendix 2) A program as described in (Appendix 1), in which, in a step of accepting information regarding the transaction, information regarding the transaction including information on the deadlines of each step in the transaction is accepted, and in a step of notifying reminder information, reminder information based on the accepted deadline information is generated and notified to the user.

[0138] (Appendix 3) A program as described in (Appendix 1), in which, in a step of generating workflow information, workflow information including information on deadlines for each step in a transaction is generated, and, in a step of notifying reminder information, reminder information based on the generated deadline information is generated and notified to a user.

[0139] (Appendix 4) A program described in (Appendix 2) or (Appendix 3), in which, in the step of notifying the reminder information, reminder information is generated and notified to the user before a specified date and time of the deadline related to the deadline information, or after the deadline related to the deadline information has passed.

[0140] (Appendix 5) The program described in (Appendix 1), wherein the memory stores man-month information required to carry out each procedure, and in a step of notifying the reminder information, notifies the reminder information including information on the deadline for starting each procedure in the workflow information based on the deadline information and the man-month information.

[0141] (Appendix 6) The program described in (Appendix 1) further executes a step (S321) of acquiring transaction progress information for the deadline information, and a step of updating the deadline information based on the acquired transaction progress information.

[0142] (Appendix 7) The program described in (Appendix 6), wherein in the step of acquiring transaction progress information, transaction progress information is acquired by accepting input from a user.

[0143] (Appendix 8) A program described in (Appendix 6), in which, in a step of acquiring transaction progress information, information about a user sent from an external server that manages information about users is accepted, and transaction progress information is acquired from the accepted information about the user.

[0144] (Appendix 9) A program as described in (Appendix 6), which, in the step of updating deadline information, updates each step to be completed if the step is completed based on the acquired transaction progress information.

[0145] (Appendix 10) A program as described in (Appendix 6), in which in the step of updating deadline information, if each step has not been completed, the deadline for each step is updated to a specified date and time in the future based on the acquired transaction progress information.

[0146] (Appendix 11) The program according to (Appendix 1), further comprising the step of generating model information of a workflow associated with a user based on information regarding the user's past transactions.

[0147] (Appendix 12) The program described in (Appendix 11), wherein the memory stores user attribute information, and in a step of generating workflow model information, generates workflow model information associated with the user based on information including the user attribute information.

[0148] (Supplementary Note 13) An information processing device including a control unit 203 and a storage unit 202, the storage unit 202 storing workflow model information (2021) indicating each procedure for a user who is a business operator to carry out a business, and form format information (2022) for carrying out the business for each procedure, the control unit 203 receiving information input by the user regarding transactions with other business operators of the user (S122), determining whether each procedure is necessary based on the workflow model information and information regarding transactions with other business operators that have been saved by the user in the past, and storing information including each procedure determined to be necessary according to the result of the determination regarding the received transaction. a step (S123) of generating workflow information for managing information relating to the accepted transaction, for each generated procedure based on form format information, a step (S124) of generating form information required for a transaction related to the accepted transaction information, a step (S125) of presenting the workflow information and the form information to a user, a step (S221) of accepting correction information for the workflow information input by the user, a step (S222) of correcting the workflow information based on the accepted correction information, and a step (S323) of generating reminder information according to the deadline for each procedure based on the workflow information and notifying the user.

[0149] (Appendix 14) A method to be executed by a computer including a processor 29 and a memory 25, the memory 25 storing workflow model information (2021) indicating each procedure for a user who is a business operator to carry out a business, and form format information (2022) for carrying out the business for each procedure, the method including a step (S122) in which the processor 29 receives information input by the user regarding transactions between the user and other business operators, determines whether each procedure is necessary based on the workflow model information and information regarding transactions between the user and other business operators that have been saved by the user in the past, and determines whether each procedure is necessary based on the result of the determination regarding the accepted transaction. a step (S123) of generating workflow information for managing information including each of the generated procedures; a step (S124) of generating, for each of the generated procedures, based on form format information, form information required for a transaction related to information relating to the accepted transaction; a step (S125) of presenting the workflow information and form information to a user; a step (S221) of accepting correction information for the workflow information input by the user; a step (S222) of correcting the workflow information based on the accepted correction information; and a step (S323) of generating reminder information according to the deadline for each procedure based on the workflow information and notifying the user. [Explanation of symbols]

[0150] 1: Sales management system 10: Terminal device 13: Input device 14: Output device 15: Memory 16: Storage section 19: Processor 20: Server 25: Memory 26: Storage 29: Processor 80: Network 81: Wireless base station 82: Wireless LAN router 111: Antenna 112: Antenna 121: First wireless communication unit 122: Second wireless communication unit 130: Operation reception section 131: Keyboard 132: Mouse 140: Audio processing unit 141: Mike 142: Speaker 150: Display 160: Storage section 161: User information 170: Control section 171: Input operation reception section 172: Transmitter / receiver 173: Notification control section 174: Data processing section 201: Communications Department 202: Storage section 203: Control section 2021: Workflow Model Database 2022: Report format database 2023: Workflow Database 2031: Receiving control module 2032: Transmission control module 2033: Transaction information reception module 2034: Workflow generation module 2035: Report information generation module 2036: Presentation module 2037 : Progress information acquisition module 2038: Workflow modification module 2039: Remind notification module

Claims

1. A program to be executed by a computer having a processor and a memory, the memory stores workflow model information indicating each procedure for a user who is a business operator to carry out a business, and format information of a form for carrying out the business for each of the procedures; The program causes the processor to: receiving information input by the user regarding transactions between the user and other businesses; determining whether each of the steps is necessary based on the workflow model information and information on transactions with other business operators that have been performed by the user in the past and stored, and generating workflow information for managing information related to the accepted transaction, including each of the steps that have been determined to be necessary based on the result of the determination; generating, for each of the generated procedures, form information required for a transaction related to the received transaction information based on the form format information; presenting the workflow information and the form information to the user; receiving correction information for the workflow information input by the user; modifying the workflow information based on the received modification information; generating reminder information according to the deadline of each step based on the workflow information and notifying the user of the reminder information,

2. In the step of receiving information about the transaction, information about the transaction including information about a deadline for each step in the transaction is received; 2. The program according to claim 1, wherein in the step of notifying the user of the reminder information, the reminder information is generated based on the received information on the deadline and notified to the user.

3. In the step of generating workflow information, the workflow information is generated including information on a deadline for each step in the transaction; 2. The program according to claim 1, wherein in the step of notifying the user of the reminder information, the reminder information is generated based on the generated information on the deadline and notified to the user.

4. The program according to claim 2 or claim 3, wherein in the step of notifying the reminder information, the reminder information is generated and notified to the user before a specified date and time of the deadline related to the deadline information, or after the deadline related to the deadline information has elapsed.

5. The memory stores man-month information required to perform each of the procedures; 2. The program according to claim 1, wherein in the step of notifying the reminder information, the reminder information includes information on a deadline for starting each procedure in the workflow information based on the deadline information and the man-month information.

6. The program further comprises: acquiring progress information of the transaction with respect to the deadline information; 2. The program according to claim 1, further comprising: updating information about the deadline based on the acquired progress information of the transaction.

7. 7. The program according to claim 6, wherein in the step of acquiring the transaction progress information, the transaction progress information is acquired by accepting an input from the user.

8. 7. The program according to claim 6, wherein in the step of acquiring the transaction progress information, information about the user transmitted from an external server that manages information about the user is accepted, and the transaction progress information is acquired from the accepted information about the user.

9. 7. The program according to claim 6, wherein in the step of updating the deadline information, an update is performed to indicate that each step is complete if the each step is completed based on the acquired transaction progress information.

10. 7. The program according to claim 6, wherein in the step of updating the deadline information, the deadline of each step is updated to a predetermined date and time in the future if each step has not been completed based on the acquired transaction progress information.

11. The program further comprises: The program product according to claim 1 , further comprising: generating model information of the workflow associated with the user based on information relating to past transactions of the user.

12. The memory stores attribute information of the user; 12. The program according to claim 11, wherein in the step of generating the workflow model information, the workflow model information associated with the user is generated based on information including attribute information of the user.

13. An information processing device including a control unit and a storage unit, the storage unit stores workflow model information indicating each procedure for a user who is a business operator to perform a task, and format information of a form for performing the task for each procedure; The control unit is receiving information input by the user regarding transactions between the user and other businesses; determining whether each of the steps is necessary based on the workflow model information and information on transactions with other business operators that have been performed by the user in the past and stored, and generating workflow information for managing information related to the accepted transaction, including each of the steps that have been determined to be necessary based on the result of the determination; generating, for each of the generated procedures, form information required for a transaction related to the received transaction information based on the form format information; presenting the workflow information and the form information to the user; receiving correction information for the workflow information input by the user; modifying the workflow information based on the received modification information; generating reminder information corresponding to a deadline for each of the steps based on the workflow information and notifying the user of the reminder information.

14. 1. A method for performing a process on a computer having a processor and a memory, comprising: the memory stores workflow model information indicating each procedure for a user who is a business operator to carry out a business, and format information of a form for carrying out the business for each of the procedures; The method further comprises the processor: receiving information input by the user regarding transactions between the user and other businesses; determining whether each of the steps is necessary based on the workflow model information and information on transactions with other business operators that have been performed by the user in the past and stored, and generating workflow information for managing information related to the accepted transaction, including each of the steps that have been determined to be necessary based on the result of the determination; generating, for each of the generated procedures, form information required for a transaction related to the received transaction information based on the form format information; presenting the workflow information and the form information to the user; receiving correction information for the workflow information input by the user; modifying the workflow information based on the received modification information; generating reminder information according to the deadline of each procedure based on the workflow information and notifying the user of the reminder information,

Citation Information

Patent Citations

  • Transaction management device, transaction management method and transaction management program

    JP2021009505A

Cited By

  • Program, method, information processing device, and system

    JP7792666B1