Program, information processing device and method

Abstract

To provide a program for acquiring a history of transactions, situation changes, etc., by linking a plurality of pieces of form information (information of sales, invoices, etc.,) relating to a same transaction, and transitioning the form information between related forms.SOLUTION: A program for operating a computer including a processor 29 and memories 25 and 26, causes the processor 29 to execute: a first step of accepting registration of data relating to transactions; a second step of acquiring form data relating to the transactions registered in the first step; a third step of registering the form data in the memory in association with the transactions; a fourth step of acquiring updated data of the form data for the transactions relating to transaction data; a fifth step of registering the updated data of the form data in the memory in association with the transactions; and a sixth step of presenting the form data and the updated data as a list based on predetermined order in association with the transactions.SELECTED DRAWING: Figure 1

Description

[Technical field]

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

[0002] A transaction management system that manages supporting data such as vouchers in business-to-business transactions and links them to transaction data has already been disclosed that has the following configuration: acquires or accepts registration of information regarding transactions such as product sales, accepts registration of information on various vouchers (quotations, contracts, delivery notes, invoices, etc.), and presents information on the various accepted vouchers to users (see Patent Document 1).

[0003] Also, a configuration has already been disclosed in which supporting data is read by OCR, acquired as text data, and used to infer the target transaction (see Patent Document 2). [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2018-169944 A [Patent Document 2] JP 2022-62458 A Summary of the Invention [Problem to be solved by the invention]

[0005] In sales management operations, depending on the type of product, the quantity and price of the product may change between the time of order and actual delivery due to negotiations between the parties, inventory status, various accidents, etc. There was a need for a sales management system that could visualize the series of such transactions and grasp the situation.

[0006] The purpose of the present disclosure is to provide a system in a sales management system that links multiple document information (sales, invoice, etc.) related to the same transaction, transitions between related documents, and enables understanding of transaction history, changes in status, etc. [Means for solving the problem]

[0007] According to one embodiment of the present disclosure, a program for operating a computer including a processor and a memory is provided. The program causes the processor to execute a first step of accepting, from a user who is a first business operator, registration of data regarding a transaction between the user and a second business operator who is a trading partner of the user; a second step of acquiring report data regarding the transaction registered in the first step; a third step of registering the report data acquired in the second step in memory, linking it to the transaction registered in the first step; a fourth step of acquiring updated data of the report data acquired in the second step for the transaction related to the data registered in the first step; a fifth step of registering the updated data of the report data acquired in the fourth step in memory, linking it to the transaction registered in the first step; and a sixth step of presenting the report data acquired in the second step and the updated data of the report data acquired in the fourth step as a list in a predetermined order, linked to the transaction registered in the first step. Effect of the Invention

[0008] According to the present disclosure, in a sales management system, it is possible to link multiple document information (sales, invoice, etc.) related to the same transaction, transition between related documents, and understand transaction history, changes in status, etc. [Brief description of the drawings]

[0009] [Figure 1] 1 is a diagram showing an overall configuration of a sales management system 1 according to a first embodiment. [Diagram 2] 1 is a block diagram showing a functional configuration of a terminal device 10 constituting a sales management system 1 according to a first embodiment. [Diagram 3] FIG. 2 is a diagram showing a functional configuration of a server 20 constituting a sales management system 1 according to the first embodiment. [Figure 4] FIG. 2 is a diagram showing an example of a data structure of a transaction database 2022 stored in the server 20 constituting the sales management system 1 according to the first embodiment. [Diagram 5] 1 is a diagram showing an example of a data structure of a form database 2023 stored in the server 20 constituting the sales management system 1 according to the first embodiment. FIG. [Figure 6] FIG. 2 is a diagram showing an example of a data structure of a client information database 2025 stored in the server 20 constituting the sales management system 1 according to the first embodiment. [Figure 7] 1 is a flowchart showing an example of a flow of workflow processing by the sales management system 1 of the first embodiment. [Figure 8] 11 is a flowchart showing an example of a flow of workflow processing by the sales management system 1 of the first embodiment, and is a flowchart showing an example of a flow of processing subsequent to the processing shown in FIG. [Figure 9] FIG. 1 is a diagram showing an overview of a sales management operation performed by a sales management system 1 according to a first embodiment. [Figure 10] 1 is a diagram showing an example of a screen displayed on the terminal device 10. FIG. [Figure 11] 1 is a diagram showing an example of a screen displayed on the terminal device 10. FIG. [Figure 12] 1 is a diagram showing an example of a screen displayed on the terminal device 10. FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. The following description and drawings are examples for explaining the present invention, and appropriate omissions and simplifications have been made for clarity of explanation. The present invention can be implemented in various other forms. Unless otherwise specified, each component may be singular or plural.

[0011] In the drawings explaining the embodiments, the same reference numerals are used to designate parts having the same functions, and repeated explanations thereof will be omitted.

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

[0013] 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 of 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.

[0014] Furthermore, 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.

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

[0016] In addition, in the following description, the processing performed by executing a program may be described, but the program is executed by a processor (e.g., CPU, GPU) to perform a defined process using storage resources (e.g., memory) and / or interface devices (e.g., communication ports) 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 a calculation unit, and may include a dedicated circuit (e.g., FPGA or ASIC) that performs a specific process.

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

[0018] Furthermore, the at least one processor may be a processor in the broad sense, such as a hardware circuit (for example, a field-programmable gate array (FPGA) or an application specific integrated circuit (ASIC)) that performs part or all of the processing.

[0019] 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.

[0020] A 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 for storing a program to be distributed, and the processor of the program distribution server may distribute the program to be distributed to other computers. 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.

[0021] 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 an HDD, it may include, for example, a SAS (Serial Attached SCSI) HDD or a NL-SAS (Nearline SAS) HDD.

[0022] In the following description, identification numbers are used as identification information for various objects, but other types of identification information (for example, identifiers including alphabetic characters or symbols) may be used instead.

[0023] In addition, in the following description, when describing elements of the same type without distinguishing between them, reference signs (or common signs among the reference signs) may be used, and when describing elements of the same type with distinction between them, the identification numbers (or reference signs) of the elements may be used.

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

[0025] <0 System Overview> The sales management system according to the present disclosure will be described below.

[0026] A sales management system according to the present disclosure, as an example and not a limitation, in a system that manages transaction data related to a transaction conducted between a user who is a first business operator and a second business operator who is another business operator, accepts registration of at least the transaction data from the user, acquires the transaction data and report data related to the transaction data, and registers the transaction data and report data in association with each other. Next, the sales management system acquires update data of the report data related to the transaction data that has already been registered, and registers the acquired update data in association with the transaction data. The sales management system then presents the report data and update data related to the associated transaction data as a list based on a predetermined order, for example, based on a time series.

[0027] The services provided by the sales 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 owned assets may be accepted to provide accounting services for the user's company or personal business.

[0028] In the sales 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 (product 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 contracts 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 the information entered into the sales 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 sales management system as a file created in a certain format, and uploaded to a server constituting the sales management system and registered as a system.

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

[0030] <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.

[0031] <1 Overall configuration of sales management system 1> FIG. 1 is a 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 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.

[0032] 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 entity that causes the server 20 to generate various forms data in association with the commercial transactions and exchanges the generated forms data with the second business entity, 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.

[0033] 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.

[0034] 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.

[0035] The server 20 generates workflow information in response to instructions from a 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 a user. The server 20 then generates workflow information based on the transaction data and the model information, and generates form data based on this workflow information.

[0036] 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.

[0037] 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.

[0038] <1.1 Configuration of the terminal device 10> 2 is a block diagram showing a functional configuration of the terminal device 10 constituting the sales 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.

[0039] 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.

[0040] 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.

[0041] 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 180.

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

[0043] 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 180 as an input signal.

[0044] 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 180 as input signals.

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

[0046] The storage unit 170 is configured with 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.

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

[0048] The control unit 180 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 170 and executing instructions included in the program. The control unit 180 performs the functions of an input operation receiving 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).

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

[0050] The transmitting / receiving unit 1802 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.

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

[0052] 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, processing to output sound to a speaker (not shown), and the like.

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

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

[0055] 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 transaction database (DB) 2022, a form DB 2023, form data 2024, a client information DB 2025, and the like.

[0056] The transaction DB 2022 is a database for managing transaction data relating to commercial transactions between a user and a second business operator. Preferably, multiple pieces of transaction data are stored in the transaction DB 2022. Details will be described later.

[0057] The form DB 2023 is a database for managing form data related to commercial transactions between a user and a second business operator, which is linked to the transaction data stored in the transaction DB 2022. Details will be described later.

[0058] The form data 2024 is form data related to a commercial transaction between a user and a second business operator, linked to the transaction data stored in the transaction DB 2022. The form data 2024 stored in the storage unit 202 may be generated by an information processing device other than the server 20, such as the terminal device 10, or may be generated by a module (not shown in FIG. 3) of the control unit 203 of the server 20.

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

[0060] The control unit 203 performs functions indicated by various modules, such as a receiving control module 2031, a transmitting control module 2032, a transaction data registration module 2033, a report data acquisition module 2034, a report data association module 2035, a report data update module 2036, a presentation control module 2037, and an accounting / payment data generation module 2038, by the processor 29 of the server 20 performing processing in accordance with the application program 2021 stored in the memory unit 202.

[0061] 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.

[0062] The transmission control module 2032 controls the process in which the server 20 transmits signals to external devices in accordance with 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 accesses the server 20 via the network 80.

[0063] When a user, who is the first business operator, operates terminal device 10 and transmits registration information for the transaction data, transaction data registration module 2033 receives the transaction data via communication unit 201. Transaction data registration module 2033 stores the received transaction data in transaction DB 2022. Preferably, transaction data registration module 2033 also stores the registration date of the transaction data in transaction DB 2022. The registration date may be obtained from a timer not shown in FIG. 3, or may be input by the user when the user transmits the transaction data registration information via terminal device 10.

[0064] The form data acquisition module 2034 acquires form data related to transaction data that has been registered or is to be registered by the transaction data registration module 2033, and stores the acquired form data in the form data 2024 of the storage unit 202. The form data acquisition module 2034 also stores the registration date of the form data in a form DB 2023 (to be described later). The registration date may be acquired from a timer not shown in FIG. 3, or may be input by the user when the user transmits the transaction data registration information via the terminal device 10.

[0065] The registration of transaction data by the transaction data registration module 2033 and the acquisition of form data by the form data acquisition module 2034 do not need to be performed at the same time, and either operation may be performed first. This is because, as described below, the form data association module 2035 performs an operation to associate the transaction data stored in the transaction DB 2022 with the form data stored in the form DB 2023, so as long as both exist when the transaction data and the form data are associated, it does not matter which is registered first.

[0066] The method by which the form data acquisition module 2034 acquires the form data is arbitrary. As an example, the terminal device 10 is operated by the operation of a user who is a first business operator, and the form data stored in the storage unit 170 of the terminal device 10 is sent to the server 20 by the transmission / reception unit 1802 of the control unit 180, so that the form data acquisition module 2034 accepts the sent form data and stores the accepted form data in the storage unit 202. Alternatively, the terminal device 10 is operated by the operation of a user who is a first business operator, and the form data stored in the storage unit 170 of the terminal device 10 is specified, so that the form data acquisition module 2034 cooperates with the reception control module 2031 and the transmission control module 2032 to acquire the form data stored in the storage unit 170 and specified by the user of the terminal device 10 from the storage unit 170 and stores it in the storage unit 202.

[0067] The form data to be acquired is not limited to that stored in the storage unit 170 of the terminal device 10. As an example, the form data to be acquired may be stored in an external server not shown in FIG. 1. In this case, the user of the terminal device 10 may specify the form data to be acquired, and the transmission / reception unit 1802 of the terminal device 10 may send the specified form data to the server 20, or the form data acquisition module 2034 may acquire the specified form data in cooperation with the reception control module 2031 and the transmission control module 2032. There is no particular restriction on the external server, and it may be a so-called document server, or an online storage service such as Dropbox (registered trademark) or Microsoft (registered trademark) Onebox. In the case of an online storage service, authentication information is required, so when the subscriber of the online storage service is the user of the terminal device 10 and the report data acquisition module 2034 acquires report data from the online storage service, it is preferable that the user of the terminal device 10 grants the administrator of system 1 access rights for the report data to be acquired, or performs pre-processing such as moving the report data to a shared space provided in the online storage service.

[0068] Here, when the form data acquisition module 2034 acquires the form data and stores it as the form data 2024 in the storage unit 202, it is preferable to classify and store the form data by type (e.g., estimate, contract, delivery note, invoice). Here, as an example of a mode in which the form data acquisition module 2034 classifies and stores the form data, a mode in which a folder for each type of form is created in the storage unit 202, and the corresponding form data is stored in the corresponding folder for each type of form may be mentioned. Alternatively, a mode in which a tag is given to each type of form and assigned to the form data 2024 may be mentioned.

[0069] One example of a method for the form data acquisition module 2034 to know the type of form data acquired by the form data acquisition module is a method in which the user specifies the type of transmitted form data when operating the terminal device 10 to transmit the form data to the server 20. Alternatively, when the form data acquisition module 2034 acquires form data, the form data acquisition module 2034 may analyze text data contained in the form data, and if the text data contains text data such as "invoice", the form data acquisition module 2034 may determine that the form data is an invoice and store the data in a folder related to invoices.

[0070] Alternatively, when acquiring the form data and storing it in the storage unit 202 as the form data 2024, the form data acquisition module 2034 preferably classifies and stores the form data according to the status of the transaction related to the form data (details of the status will be described later). Alternatively, the form data acquisition module 2034 may tag the form data with a status.

[0071] The form data association module 2035 associates the transaction data stored in the transaction DB 2022 with the form data stored in the form DB 2023, and stores the associated information in the form DB 2023. The transaction data and form data to be associated are preferably designated by a user, who is the first business operator, operating the terminal device 10 and inputting the designation of the transaction data and form data to be associated. For example, the file name of the file related to the form data includes a name and an identifier for identifying the transaction data, and the form data association module 2035 can associate the transaction data and form data based on this name and identifier, but it is more reliable to have the user operate the terminal device 10 to associate the transaction data and form data while checking them one by one, and this can reduce malfunctions.

[0072] Information regarding the association between transaction data and report data can be managed by establishing a database that manages only this information, but in this embodiment, the association information between transaction data and report data is equivalent to associating in report DB2023 a report ID for identifying individual report data in report DB2023 with a transaction ID for identifying individual transaction data (see Figure 5).

[0073] The report data update module 2036 acquires update data of the report data related to the transaction data registered in the transaction DB 2022 by the transaction data registration module 2033, and stores the acquired update data in the storage unit 202 as the report data 2024. There are no limitations on the method of acquiring the update data by the report data update module 2036, and one example is a method in which the user, who is the first business operator, operates the terminal device 10 and acquires the update data by specifying and inputting the update data in association with the transaction data.

[0074] In addition, if the transaction data registration module 2033 is configured to register and update the transaction status for the transaction data registered in the transaction DB 2022, the report data update module 2036 can check with the user of the terminal device 10 whether the report data has been updated when updating this status, and wait for the user to specify the updated data. Here, the transaction status can be set arbitrarily, but as an example, the transaction status is divided into a work process and a work status, and the work process can be "quote," "order," "sales," and "billing," and the work status can be "creating," "checking," "waiting," and the like, which indicate the state of the work process. Hereinafter, when the status is referred to, it is an expression that combines the work process and the work status, for example, "creating an estimate."

[0075] Furthermore, it is preferable that when the transaction data registration module 2033 updates the transaction status for the transaction data registered in the transaction DB 2022, the report data update module 2036 moves the folder for each status in which the report data is stored to the folder for the updated status.

[0076] In addition, when the form data update module 2036 acquires update data for form data classified into the same type, if this update data matches a predetermined condition, it is preferable that the form data update module 2036 transmits notification information to the terminal device 10 to notify the user. One example of the predetermined condition is when the delivery date of the transaction related to the update data is brought forward.

[0077] Furthermore, if the form data update module 2036 holds a rule-based DB (not shown), and if a change from a specified status to another specified status is registered in the transaction data registration module 2033 and this status change falls under a specified rule, the form data update module 2036 can confirm with the user of the terminal device 10 whether the form data has been updated and wait for the user to specify the updated data. As an example, if a status of "re-created estimate" is registered, it is presumed that the terms of the estimate, such as the amount, have been changed, so it is assumed that the estimate data, which is form data, has been changed, and the user of the terminal device 10 is confirmed as to whether the form data has been updated.

[0078] The presentation control module 2037 cooperates with the reception control module 2031 and the transmission control module 2032 to present the form data acquired by the form data acquisition module 2034 and the update data acquired by the form data update module 2036, which are related to the same transaction data, in a list based on a predetermined order. There is no particular limit to the destination of the presentation of the presentation control module 2037, but in the present system 1, it is preferably a user who is a first business operator who operates the terminal device 10. There is no particular limit to the manner of presentation to the user, but as an example, a manner in which display control data for displaying a predetermined screen on the display 150 of the terminal device 10 is transmitted to the terminal device 10. The terminal device 10 displays a predetermined screen on the display 150 of the terminal device 10 based on this display control data. There is also no particular limit to the predetermined order in which the form data and the update data are presented, but as an example, the presentation control module 2037 presents the form data and the update data in chronological order based on the registration date.

[0079] There are no particular limitations on the manner in which the presentation control module 2037 presents the form data and update data, and the form data and update data may be displayed as images, or only the titles of the form data and update data may be displayed as text. However, it is preferable that the presentation control module 2037 presents the form data and update data in a manner in which the form data and update data relate to the same transaction and can be distinguished from each other. One example of such a manner is a manner in which the form data and update data classified in the same type for the same transaction are displayed as a group (for example, in a predetermined area on the screen of the display 150 and arranged vertically and horizontally).

[0080] Furthermore, when the presentation control module 2037 acquires update data of form data classified into the same type, if the update data meets a predetermined condition, it is preferable to present the update data in a display mode different from other form data and update data. Here, the predetermined condition is a case where the amount described in the form related to the form data is different from the amount described in the form related to the update data. As an example of a mode of differentiating the display modes, a mode in which the display color of the corresponding update data is set to red and the other form data and update data is displayed in black is exemplified.

[0081] When the presentation control module 2037 presents the form data and update data, in addition to displaying images and titles of the form data and update data, it is preferable to display a link that allows direct access to the form data 2024 stored in the storage unit 202, superimposed on these images or titles. In other words, it is preferable to display the form data 2024 itself in the storage unit 202 on the display 150 of the terminal device 10 by clicking on the image or title.

[0082] When the transaction status for transaction data registered in the transaction DB 2022 by the transaction data registration module 2033 is updated to "settlement", that is, when a payment occurs in the transaction related to the transaction data, the accounting / payment data generation module 2038 generates accounting data related to the payment and stores it in the memory unit 202. Then, the accounting / payment data generation module 2038 generates payment data related to the payment, for example, financial institution payment data and credit card payment data, and stores it in the memory unit 202. After that, preferably, the accounting / payment data generation module 2038 transmits the generated payment data to an external server, for example, a financial institution payment server or a credit card payment server, and performs payment processing.

[0083] <2 Data Structure> Fig. 4 is a diagram showing an example of the data structure of a transaction DB 2022 stored by the server 20 in Fig. 3. Fig. 5 is a diagram showing an example of the data structure of a form DB 2023 stored by the server 20 in Fig. 3. Fig. 6 is a diagram showing an example of the data structure of a client information DB 2025 stored by the server 20 in Fig. 3.

[0084] As shown in FIG. 4, each record in transaction DB2022 includes an item "Transaction ID", an item "Client ID", an item "Order subject", an item "Order number", an item "Customer order number", an item "Registration date", an item "Amount", an item "Status", etc.

[0085] The item “transaction ID” is information for identifying transaction data managed by the sales management system 1.

[0086] The item "client ID" is information for identifying a second business (client) that is a trading partner of a user (first business) who is the administrator of the sales management system 1.

[0087] The item "order subject" is information that indicates the subject of the commercial transaction related to the transaction data identified by the item "transaction ID".

[0088] The item "order number" is information indicating an order number that is assigned by the sales management system 1 so that the sales management system 1 can identify the transaction data identified by the item "transaction ID".

[0089] The item "customer order number" is information indicating the order number assigned by the second business to the transaction related to the transaction data identified by the item "transaction ID".

[0090] The item "registration date" is information indicating the date on which the transaction data registration module 2033 registered the transaction data identified by the item "transaction ID" in the transaction DB 2022.

[0091] The item "amount" is information indicating the amount of goods or services traded in a transaction related to the transaction data identified by the item "transaction ID".

[0092] The item "status" is information indicating the status of the transaction related to the transaction data identified by the item "transaction ID".

[0093] As shown in Figure 5, each record in the report DB2023 includes an item "transaction ID", an item "report ID", an item "report type", an item "report data acquisition date", an item "amount", an item "status", etc.

[0094] The item “transaction ID” is information for identifying transaction data managed by the sales management system 1, and is the same as the item “transaction ID” of the transaction DB 2022.

[0095] The item “document ID” is information for identifying the document data managed by the sales management system 1.

[0096] The item "document type" is information indicating the name of the document related to the document data identified by the item "document ID".

[0097] The item “document data acquisition date” is information indicating the date on which the document data identified by the item “document ID” was acquired by the document data acquisition module 2034 and registered in the document DB 2023 .

[0098] The item "amount" is information indicating the amount of a product or service written on a form related to the form data identified by the item "form ID".

[0099] The item "status" is information indicating the status of the form related to the form data identified by the item "form ID".

[0100] As shown in FIG. 6, each record of the client information DB 2025 includes an item "client ID", an item "company name", an item "corporate number", an item "address", an item "contact information", an item "industry", and the like.

[0101] The item “client ID” is information for identifying a second business that is a trading partner of a user (first business) who is the administrator of the sales management system 1, and is the same as the item “client ID” in the transaction DB2022.

[0102] The item "name" is information indicating the corporate name or individual name of the second business identified by the item "client ID".

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

[0104] The item "address" is information that indicates the address of the second business identified by the item "client ID".

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

[0106] <3 operations> Hereinafter, the workflow process by the sales management system 1 in the first embodiment will be described with reference to FIGS.

[0107] Fig. 9 is a diagram showing an example of a transaction process and a transaction status managed by the sales management system 1 according to the present disclosure. Using Fig. 9, the transaction process and the transaction status managed by the transaction data in the present disclosure will be described. Note that here, the transaction process is "quote", "order", "inspection / sales", and "billing" which indicate the stage of the transaction at the business operator, and the transaction status is "creating", "checking", "waiting", etc. which indicate the state in the work process of each business operator, and is registered for each of multiple business operators, for example.

[0108] The block labeled "case management" corresponds to the function of the sales management system 1 in the present embodiment 1. "Case management" grasps the progress of transaction cases throughout the entire transaction process and manages documents, including slips, received during the transaction process.

[0109] 9, the scope indicated as "accounting" is managed by an accounting system which may be a system separate from the sales management system 1 in the present embodiment 1. Naturally, the sales management system 1 may realize such a function.

[0110] 7 and 8 are flowcharts showing an example of a flow of workflow processing performed by the sales management system 1 according to the present disclosure.

[0111] In step S700, the server 20 performs user authentication to provide the user with transaction data generated by the sales 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 input information is verified to match the registered information for user authentication. If the information matches, the user is logged into the server 20.

[0112] In the process of step S701, registration information for transaction data is sent by operating the operation reception unit 130 of the terminal device 10, and the transaction data registration module 2033 of the server 20 accepts the transaction data via the communication unit 201. The accepted transaction data is stored in the transaction DB 2022. Note that, 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, thereby registering the transaction data in the server 20.

[0113] In step S702, the form data acquisition module 2034 of the server 20 acquires the form data related to the transaction data registered in step S701.

[0114] Next, in step S703, the form data acquisition module 2034 of the server 20 classifies the form data acquired in step S702 based on the type of form, etc., and stores the classified form data in the storage unit 202. As an example, the form data acquisition module 2034 stores the form data in a folder for each classification.

[0115] In step S704, the form data association module 2035 of the server 20 associates the transaction data registered in step S701 with the form data acquired in step S702 for the transaction related to the transaction data. More specifically, the form data association module 2035 links the form data acquired in step S702 to the transaction data for the transaction related to the form data.

[0116] In step S705, the report data update module 2036 of the server 20 waits for the report data to be updated, and if notified that the report data has been updated (YES in step S705), in step S706, the report data update module 2036 acquires the update data notified in step S705.

[0117] Next, in step S707, the form data update module 2036 of the server 20 classifies the update data acquired in step S706 based on the type of form, etc., and stores the classified data in the storage unit 202. As an example, the form data update module 2036 stores the update data in a folder for each classification.

[0118] 8, in step S800, the form data association module 2035 of the server 20 associates the transaction data registered in step S701 with the update data for the transaction related to the transaction data acquired in step S706. More specifically, the form data association module 2035 links the update data acquired in step S706 to the transaction data for the transaction related to the update data.

[0119] When the user, who is the first business operator, operates the terminal device 10 to input an instruction to display the form data, and the server 20 receives this input signal (YES in step S801), the program proceeds to step S802. On the other hand, if the server 20 has not received the input signal at this point (NO in step S801), the program ends.

[0120] In step S802, the presentation control module 2037 of the server 20 determines whether the update data acquired in step S806 has been updated according to a predetermined condition. If it is determined that the update data has been updated according to the predetermined condition (YES in step S802), the program proceeds to step S803, and if it is determined that the update data has not been updated according to the predetermined condition (NO in step S802), the program proceeds to step S805.

[0121] In step S803, the presentation control module 2037 of the server 20 generates display control data for changing the display mode to display the corresponding update data on the display 150 of the terminal device 10, and sends it to the terminal device 10, and the terminal device 10 displays the form data and update data for which display instructions were given in step S801 on the screen of the display 150 based on this display control data. Next, in step S804, notification information is transmitted to the terminal device 10 to notify the user operating the terminal device 10 that update data updated according to predetermined conditions exists. The terminal device 10 that has received the notification information notifies the user based on this notification information.

[0122] In step S805, the presentation control module 2037 of the server 20 generates display control data for displaying the report data and update data for which display was instructed in step S801 on the display 150 of the terminal device 10, and sends it to the terminal device 10. Based on this display control data, the terminal device 10 displays the report data and update data for which display was instructed in step S801 on the screen of the display 150.

[0123] <4 Screen example> Examples of screens for workflow processing by the sales management system 1 will be described below with reference to FIGS.

[0124] 10 is a diagram showing an example of a login screen 1000 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 transmitted 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 is installed in the terminal device 10 in advance. Through these operations, the login screen 1000 as shown in FIG. 10 is displayed on the display 150 of the terminal device 10.

[0125] 10 is displayed on the display 150 of the terminal device 10, the user operates the operation reception unit 130 to input his / her own account information (email address in this embodiment) and password into an account input field 1001 and a password input field 1002 provided on the login screen 1000. After that, by pressing a login button 1003, user authentication is performed and the user is logged in to the server 20.

[0126] Fig. 11 is a diagram showing an example of a transaction data display screen 1100 displayed on the display 150 of the terminal device 10. After the user is authenticated by the server 20 and logs in to the server 20, when the user selects to display transaction data by selecting a menu or tab, the transaction data display screen 1100 shown in Fig. 11 is displayed on the display 150 of the terminal device 10 and becomes available for input by operating the operation reception unit 130.

[0127] The transaction data display screen 1100 displays the transaction data managed by the sales management system 1 of the present embodiment 1 described with reference to Fig. 9, more specifically, details of transactions related to the transaction data registered in the transaction DB 2022. In particular, the transaction data display screen 1100 displays transaction data for each transaction process of the transaction related to the transaction data.

[0128] Fig. 12 is a diagram showing another example of a transaction data display screen 1200 displayed on the display 150 of the terminal device 10. When the user selects and inputs data by clicking, for example, on an area displaying "Sales" using the operation reception unit 130 of the terminal device 10 on the transaction data display screen 1100 shown in Fig. 11, a transaction data display screen 1200 shown in Fig. 12 is displayed on the display 150 of the terminal device 10, and becomes available for input by operating the operation reception unit 130.

[0129] The transaction data display screen 1200 has an area 1201 in which the titles of the form data and update data linked to the selected transaction data are displayed in a list. The titles of the form data and update data are displayed in chronological order in this area 1201. When the user selects and inputs a title via the operation reception unit 130, the selected form data or update data is displayed on the display 150 of the terminal device 10. In other words, the titles of the form data and update data displayed in the area 1201 also function as links to the form data and update data.

[0130] <5.Summary> As described above, the server 20 of this embodiment can present the form data and update data linked to the transaction data on the display 150 of the terminal device 10 in a list in a predetermined order, more specifically, based on a time series, and can transition between the form data and update data related to the transaction. This makes it possible to visualize the series of transaction flows and to easily grasp the transaction status. It also makes it possible to handle slip management for annual contracts, subscription contracts, etc.

[0131] <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.

[0132] In addition, 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 included in 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 storing it 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, ROMs, etc.

[0133] Furthermore, the program code for realizing 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), and the like.

[0134] Furthermore, the program code of the software that realizes the functions of the embodiments 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 out and execute the program code stored in the storage means or storage medium.

[0135] The matters described in the above embodiments will be supplemented below.

[0136] (Appendix 1) A program (2021) for operating a computer having a processor (29) and a memory (25, 26), the program (2021) causes the processor (29) to perform a first step (S701) of accepting, from a user who is a first business, registration of data relating to a transaction between the user and a second business that is a business partner of the user; a second step (S702) of acquiring form data (2024) relating to the transaction registered in the first step (S701); a third step (S704) of registering the form data (2024) acquired in the second step (S702) in the memory (25, 26) in association with the transaction registered in the first step (S701); a fourth step (S706) of acquiring updated data of the report data (2024) acquired in the second step (S702) for the transaction related to the recorded data; a fifth step (S800) of registering the updated data of the report data (2024) acquired in the fourth step (S706) in the memory (25, 26) in association with the transaction registered in the first step (S701); and a sixth step (S805) of presenting the report data (2024) acquired in the second step (S702) and the updated data of the report data (2024) acquired in the fourth step (S706) in a list in a predetermined order in association with the transaction registered in the first step (S701). (Appendix 2) The program (2021) further executes a seventh step (S703) of classifying the report data (2024) acquired in the second step (S702) based on the type of report related to the report data (2024) and registering the classified data in the memory (25, 26). The program (2021) described in Appendix 1. (Appendix 3) In a sixth step (S805), the program (2021) described in Appendix 2 presents report data (2024) classified into the same type and update data of the report data (2024) based on a time series. (Appendix 4) In a fourth step (S706), if update data that meets a specified condition is obtained from update data of report data (2024) classified into the same type, in a sixth step (S805), the presentation mode of the update data that meets the specified condition is presented in a different manner from the other report data (2024) and the update data of the report data (2024), the program (2021) described in Appendix 3. (Appendix 5) A program (2021) described in Appendix 3, which executes an eighth step (S804) of sending notification information to a user when update data that meets specified conditions is obtained from update data of report data (2024) classified into the same type in a fourth step (S706). (Appendix 6) In a sixth step (S805), a program (2021) described in Appendix 1 presents a link to report data (2024) registered in a memory (25, 26) and update data of the report data (2024). (Appendix 7) The program (2021) further executes a ninth step of accepting that a payment has occurred for the transaction related to the data registered in the first step (S701), and a tenth step of generating accounting data related to the payment and registering it in the memory (25, 26) if the payment has occurred in the ninth step, the program (2021) described in Appendix 1. (Appendix 8) The program (2021) further executes an 11th step of generating payment data relating to the payment when the occurrence of the payment is accepted in the 9th step, the program (2021) being described in Appendix 7. (Appendix 9) The information processing device includes a processor (29) and a memory (25, 26), the processor (29) includes a first step (S701) of accepting registration of data relating to a transaction between a user and a second business entity that is a business partner of the user from the user who is a first business entity; a second step (S702) of acquiring form data (2024) relating to the transaction registered in the first step (S701); a third step (S704) of registering the form data (2024) acquired in the second step (S702) in the memory (25, 26) in association with the transaction registered in the first step (S701); and a sixth step (S805) of presenting, as a list in a predetermined order, the report data (2024) acquired in the second step (S702) and the update data of the report data (2024) acquired in the fourth step (S706), the update data of the report data (2024) acquired in the fourth step (S706), the update data of the report data (2024) acquired in the fourth step (S706), the update data of the report data (2024) acquired in the fourth step (S706), the update data of the report data (2024) acquired in the second step (S702), and the update data of the report data (2024) acquired in the fourth step (S706), the update data of the report data (2024) acquired in the fourth step (S706), the update data of the report data (2024) acquired in the first step (S701), the update data of the report data (2024) acquired in the fourth step (S706), the update data of the report data (2024) acquired in the second step (S702), the update data of the report data (2024) acquired in the fourth step (S706), the update data of the report data (2024) acquired in the first step (S701), the update data of the report data (2024) acquired in the fourth step (S706 ... (Appendix 10) A method executed by a computer having a processor (29) and a memory (25, 26), the processor (29) includes a first step (S701) of accepting, from a user who is a first business, registration of data relating to a transaction between the user and a second business that is a business partner of the user, a second step (S702) of acquiring form data (2024) relating to the transaction registered in the first step (S701), a third step (S704) of linking the form data (2024) acquired in the second step (S702) to the transaction registered in the first step (S701) and registering it in the memory (25, 26), and a fourth step (S706) of acquiring updated data of the report data (2024) acquired in the second step (S702) for the transaction related to the transaction; a fifth step (S800) of registering the updated data of the report data (2024) acquired in the fourth step (S706) in a memory (25, 26) in association with the transaction registered in the first step (S701); and a sixth step (S805) of presenting the report data (2024) acquired in the second step (S702) and the updated data of the report data (2024) acquired in the fourth step (S706) in a list in a predetermined order in association with the transaction registered in the first step (S701). [Explanation of symbols]

[0137] 1 Sales management system 10 10A, 10B Terminal device, 20 Server, 25 Memory, 29 Processor, 80 Network, 150 Display, 170 Storage unit, 180 Control unit, 202 Storage unit, 203 Control unit, 2021 Application program, 2022 Transaction DB, 2023 Report DB, 2024 Report data, 2025 Client information DB, 2032 Transmission control module, 2033 Transaction data registration module, 2034 Report data acquisition module, 2035 Report data association module, 2036 Report data update module, 2037 Presentation control module, 2038 Payment data generation module

Claims

1. A program for operating a computer having a processor and a memory, The program causes the processor to: A first step of accepting registration of data relating to a transaction between a user, which is a first business entity, and a second business entity that is a business partner of the user; a second step of acquiring document data relating to the transaction registered in the first step; a third step of registering the document data acquired in the second step in the memory in association with the transaction registered in the first step; a fourth step of acquiring update data of the form data acquired in the second step for the transaction related to the data registered in the first step; a fifth step of registering the update data of the form data acquired in the fourth step in the memory in association with the transaction registered in the first step; a sixth step of presenting the form data acquired in the second step and the update data of the form data acquired in the fourth step as a list in a predetermined order, in association with the transaction registered in the first step; A program to execute.

2. 2. The program according to claim 1, further comprising a seventh step of classifying the form data acquired in the second step based on the type of form related to the form data and registering the classified form data in the memory.

3. 3. The program according to claim 2, wherein in the sixth step, the form data and the update data of the form data classified into the same type are presented in chronological order.

4. 4. The program according to claim 3, wherein in the fourth step, if update data that meets a specified condition is obtained from among the update data of the report data classified into the same type, in the sixth step, the presentation mode of the update data that meets the specified condition is presented in a different manner from that of the other report data and the update data of the report data.

5. 4. The program according to claim 3, further comprising: an eighth step of transmitting notification information to the user when, in the fourth step, update data that meets a predetermined condition is obtained from among the update data of the report data classified into the same type.

6. 2. The program according to claim 1, wherein in the sixth step, links to the form data and the update data of the form data registered in the memory are presented.

7. The program further comprises: a ninth step of accepting that a settlement has occurred for the transaction related to the data registered in the first step; a tenth step of generating accounting data relating to the payment and registering the data in the memory when the payment is accepted in the ninth step; The program according to claim 1 .

8. The program according to claim 7 , further comprising an eleventh step of generating payment data relating to the payment when the occurrence of the payment is accepted in the ninth step.

9. An information processing device including a processor and a memory, The processor, A first step of accepting registration of data relating to a transaction between a user, which is a first business entity, and a second business entity that is a business partner of the user; a second step of acquiring document data relating to the transaction registered in the first step; a third step of registering the document data acquired in the second step in the memory in association with the transaction registered in the first step; a fourth step of acquiring update data of the form data acquired in the second step for the transaction related to the data registered in the first step; a fifth step of registering the update data of the form data acquired in the fourth step in the memory in association with the transaction registered in the first step; a sixth step of presenting the form data acquired in the second step and the update data of the form data acquired in the fourth step as a list in a predetermined order, in association with the transaction registered in the first step; An information processing device that executes the above.

10. 1. A method implemented by a computer having a processor and a memory, comprising: The processor, A first step of accepting registration of data relating to a transaction between a user, which is a first business entity, and a second business entity that is a business partner of the user; a second step of acquiring document data relating to the transaction registered in the first step; a third step of registering the document data acquired in the second step in the memory in association with the transaction registered in the first step; a fourth step of acquiring update data of the form data acquired in the second step for the transaction related to the data registered in the first step; a fifth step of registering the update data of the form data acquired in the fourth step in the memory in association with the transaction registered in the first step; a sixth step of presenting the form data acquired in the second step and the update data of the form data acquired in the fourth step as a list in a predetermined order, in association with the transaction registered in the first step; A method for performing.

Images