Program, information processing device and method

The sales management system allows users to view, edit, and publish template data for commercial transactions, addressing the need for advanced design integration and improving user satisfaction by facilitating data sharing.

JP2025004439AActive Publication Date: 2025-01-15FREEE
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
JP2023104129
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-06-26
Publication Date
2025-01-15
Estimated Expiration
2043-06-26

AI Technical Summary

Technical Problem

Users who value advanced designs in commercial transactions, such as product designers, need to refer to and select template data created by other users for forms like invoices, but existing systems do not facilitate this functionality.

Method used

A sales management system that allows users to view, edit, and publish template data for commercial transactions, enabling other users to access and utilize the edited template data.

Benefits of technology

Enables users to demonstrate their design abilities and improve convenience and satisfaction by sharing and utilizing template data created by others, enhancing the sales management system's functionality.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2025004439000001_ABST
    Figure 2025004439000001_ABST
Patent Text Reader

Abstract

To provide a technique of allowing other users to browse and use template data necessary for managing commercial transactions.SOLUTION: A server of a sales management system stores template data (2021) necessary for managing commercial transactions, and executes as functions thereof: a step (S121) of receiving, from a user, input of transaction data relating to a commercial transaction of the user; a step (S221) of receiving, from the user, editing input to template data selected from the stored template data and used for managing the commercial transaction relating to the received transaction data; and a step (S222) of storing the template data edited by the user as the template data relating to the received transaction data and disclosing it such that other users can browse it.SELECTED DRAWING: Figure 4
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] ERP (Enterprise Resource Planning) package software (often referred to as integrated core business systems, and many are provided as cloud-based services) includes a sales management system that manages all aspects of sales operations, from prospect and inquiry management to quotations, orders, sales, invoices, and accounts receivable management, and also includes workflow management and document management functions.

[0003] A technique related to the above-mentioned technique is disclosed in Patent Document 1.

[0004] Patent Document 1 discloses an electronic procurement system that holds information on form layouts used in various transactions and enables a user to easily change the form layout. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2012-098878 A Summary of the Invention [Problem to be solved by the invention]

[0006] Incidentally, some users consider forms used in various transactions, such as invoices, to be an opportunity to demonstrate their design skills. This tendency is particularly seen among users who handle product designs and those who place importance on cutting-edge design. These users have a need to be able to refer to template data used in commercial transactions, including form data, created by other users, and select a template with a design that suits their needs.

[0007] Therefore, this disclosure describes a technology that allows other users to view and use template data required for managing commercial transactions. [Means for solving the problem]

[0008] According to one embodiment of the present disclosure, there is provided a program for managing commercial transactions related to a user, when executed by a computer having a processor and a memory, wherein the memory stores template data required for managing the commercial transactions, and the program causes the processor to execute the following steps: accepting from the user an input of transaction data related to the commercial transaction related to the user; accepting from the user an editing input for template data selected from the stored template data to be used for managing the commercial transaction related to the accepted transaction data; and storing the template data edited by the user as template data related to the accepted transaction data and making the template data publicly available for viewing by other users. Effect of the Invention

[0009] According to the present disclosure, template data required for managing commercial transactions is made publicly available for other users to view, thereby satisfying the need to refer to template data used in commercial transactions, such as form data, created by other users. [Brief description of the drawings]

[0010] [Figure 1] FIG. 2 is a diagram showing an example of form data, which is an example of template data used in the present disclosure. [Diagram 2] 1 is a block diagram showing an overall configuration of a sales management system 1 according to a first embodiment. [Diagram 3] 3 is a block diagram showing a functional configuration of the terminal device 10 of FIG. 2. [Figure 4] 3 is a block diagram showing a functional configuration of the server 20 of FIG. 2. [Diagram 5] FIG. 5 is a diagram showing an example of the data structure of a template database 2021 in FIG. 4. [Figure 6] FIG. 5 is a diagram showing an example of a data structure of a transaction database 2022 in FIG. 4. [Figure 7] 13 is a flowchart showing an example of a flow of template data selection processing performed by the sales management system 1. [Figure 8] 13 is a flowchart showing an example of a flow of a template edit data transmission process performed by the sales management system 1. [Figure 9] FIG. 13 is a diagram showing an example of a screen of published template data displayed on the terminal device 10. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Hereinafter, an embodiment of the present disclosure will be described with reference to the drawings. The following description and drawings are examples for explaining the present invention, and are omitted and simplified as appropriate for clarity of explanation. The present invention can be implemented in various other forms. Unless otherwise specified, each component may be singular or plural. In the following description, the same components are denoted by the same reference numerals. Their names and functions are also the same. Therefore, detailed descriptions thereof will not be repeated.

[0012] <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 managing transaction data, which is various information about transactions between corporations or sole proprietors and other business operators. When transactions are made between businesses such as companies and sole proprietors regarding goods, services, etc., procedures such as quotation, ordering, receiving an order, delivery, and billing are often followed, and it is necessary to issue forms such as quotation and purchase order for each of these procedures to process the transaction. The sales management system according to the present disclosure is a system for providing a service that manages procedures such as quotation and ordering, and 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, that is, by so-called SaaS (Software as a Service).

[0013] In addition, the sales management system according to the present disclosure manages user transaction data and provides accounting services. The accounting services provided to users include managing cash transactions such as purchases, sales, and borrowings, recording (entering) transactions in ledgers (journal entries, general ledgers), creating trial balances as settlement processing at the designated accounting period, and creating financial statements such as income statements and balance sheets.

[0014] Furthermore, the sales management system according to the present disclosure stores and manages template data required for managing user transaction data. The template data is a data group that manages various information required for managing transaction data as templates, which are exemplary data according to the user's industry, business scale, etc., and includes, for example, workflow data showing procedures for quotation, ordering, etc., and form layout data for quotation sheets, purchase orders, etc.

[0015] Fig. 1 is a diagram showing an example of form data, which is an example of template data used in the present disclosure. The form data stored in the sales management system according to the present disclosure is image data of invoice P1, as shown in Fig. 1 as an example. Invoice P1 is template data for creating invoices used in user transactions, and includes the invoice issue date, billing destination company name, billing company name, subject, item, quantity, amount, etc.

[0016] As mentioned above, some users may consider forms such as the invoice P1 used in various transactions as an opportunity to demonstrate their own design sense. This tendency is particularly seen in users who handle designs of products and the like, and users who value advanced designs. For example, there was a need to change the layout of the billing destination company name P11 and the billing company name P12 shown in Figure 1, such as by using a different font from the usual one, or by changing the position or color. There was also a need to imitate the data management method of a company with an advanced image, for example. Therefore, there was a need to refer to and select template data, including form data, created by other users.

[0017] In view of this, a sales management system according to the present disclosure stores and manages template data required for managing commercial transactions. The system also accepts input of transaction data related to commercial transactions from a user, and accepts edit input for the template data used to manage the commercial transactions related to the accepted transaction data. The system then stores the template data edited by the user as template data related to the transaction data, and makes the template data available for other users to view.

[0018] With the above-mentioned configuration, template data, such as form data, created by other users can be referenced, selected, and used, thereby satisfying the need to reference and select template data, such as form data, created by other users. In addition, template data edited by a user is made public in a state that can be viewed by other users, allowing the user to demonstrate their design abilities. This makes it possible to improve convenience and satisfaction for customers in the sales management system.

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

[0020] <1 Overall configuration of sales management system 1> FIG. 2 is a block diagram showing the overall configuration of the sales management system 1 according to the first embodiment. As shown in FIG. 2, the sales management system 1 includes a plurality of terminal devices (terminal device 10A and terminal device 10B are shown in FIG. 2. 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 so as to be able to communicate with each other via a network 80. 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. Note that 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 also be installed and configured to be viewable through the dedicated application.

[0021] The terminal device 10 is a device operated by each user. Here, the user is a person who uses the terminal device 10 to manage transaction data, which is a function of the sales management system 1, and to view, select, and edit template data, such as an employee of a business enterprise 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.

[0022] 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. 2, 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.

[0023] 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 a device (e.g., 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.

[0024] Server 20 is a device that stores and manages template data required for managing commercial transactions, which is a function of sales management system 1. Server 20 accepts input of transaction data related to commercial transactions from users, and accepts edit input for the template data. Server 20 also stores template data edited by a user as template data related to that transaction data, and makes it publicly available for other users to view.

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

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

[0027] <1.1 Configuration of the terminal device 10> FIG. 3 is a block diagram showing a functional configuration of the terminal device 10 of FIG. 2. As shown in FIG. 3, 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 camera 160, a storage unit 170, and a control unit 180. The terminal device 10 also has functions and configurations (e.g., a battery for holding 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. 3. As shown in FIG. 3, each block included in the terminal device 10 is electrically connected by a bus or the like. The terminal device 10 shown in FIG. 3 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.

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

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

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

[0031] The operation reception unit 130 has a mechanism for receiving an input operation from a user in response to the control of the control unit 180. 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 position of the user's contact with the touch panel, for example, by using a capacitive touch panel.

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

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

[0034] The audio processing unit 140 modulates and demodulates an audio signal under the control of the control unit 180. The audio processing unit 140 modulates a signal provided from the microphone 141 and provides the modulated signal to the control unit 180. The audio processing unit 140 also provides the audio signal to the speaker 142. The audio processing unit 140 is realized by, for example, 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.

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

[0036] Camera 160 is a device that receives light with a light receiving element and outputs the received light as a captured image in accordance with the control of control unit 180. Camera 160 may be configured, for example, with an imaging device such as a digital camera or a video camera.

[0037] Storage unit 170 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 170 stores user information 171.

[0038] The user information 171 is information about a user who uses the terminal device 10 to manage transaction data, which is a function of the sales management system 1, and to view, select, and edit template data. The user information includes information for identifying the user (user ID) and information such as the name or title of the business operator or person in charge (user attribute data).

[0039] 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 fulfills the functions of an input operation receiving unit 181, a transmission / reception unit 182, a notification control unit 183, and a data processing unit 184 by operating in accordance with a program (not shown) that is an application that is stored in advance in the storage unit 170 of the terminal device 10 and installed, for example.

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

[0041] The transmission / reception unit 182 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.

[0042] The notification control unit 183 performs a process of presenting information to the user. The notification control unit 183 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.

[0043] The data processing unit 184 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.

[0044] <1.2 Functional configuration of server 20> Fig. 4 is a block diagram showing a functional configuration of the server 20 of Fig. 2. As shown in Fig. 4, the server 20 fulfills the functions of a communication unit 201, a storage unit 202, and a control unit 203.

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

[0046] 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 template database 2021, a transaction database 2022, and the like.

[0047] The template database 2021 is a database for holding template data required for managing user transaction data, which is managed by the sales management system 1. Details will be described later.

[0048] Template data is a data group that manages various information required for managing transaction data as templates, with various exemplary data according to the user's industry, business scale, etc., and includes, for example, workflow data showing procedures for quotation, ordering, etc., and form layout data for quotations, purchase orders, etc. There are no particular limitations on the data format of the files that make up the template data, and any known data format that can describe the location of data, such as PDF (Portable Document Format), Word, or XML (eXtensible Markup Language), can be suitably applied.

[0049] The transaction database 2022 is a database for holding data (transaction data) on transactions such as purchases of various goods and the like, sales related to sales, and various payments by users of the sales management system 1, specifically, information on deposits and withdrawals at businesses that are users. Details will be described later.

[0050] The control unit 203 performs functions indicated in various modules, such as a reception control module 2031, a transmission control module 2032, a transaction data reception module 2033, a template extraction module 2034, a user presentation module 2035, a template selection reception module 2036, a template edit reception module 2037, and a template publication module 2038, by the processor 29 of the server 20 performing processing in accordance with a program.

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

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

[0053] The transaction data reception module 2033 controls the process of receiving input of transaction data related to commercial transactions from users who are employees of a business enterprise or individual business owners. The transaction data received by the transaction data reception module 2033 is, for example, various information about transactions conducted with other businesses, specifically, 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. In addition, the transaction data 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.

[0054] For example, terminal device 10 accepts input of transaction data from a user through processing by input operation acceptance unit 181. When the user inputs the transaction data, terminal device 10 transmits information on the template data selected by the user via transmission / reception unit 182. Transaction data acceptance module 2033 receives and accepts the transaction data entered by the user via communication unit 201.

[0055] The transaction data received by the transaction data receiving module 2033 may include information on deadlines for each step in a transaction, specifically, steps such as quotation, ordering, receiving, delivery, and billing.

[0056] The transaction data receiving module 2033 stores the received transaction data in the transaction database 2022 .

[0057] The template extraction module 2034 controls the process of extracting one or more of the template data edited by the user or other users from the template data stored in the template database 2021, based on the transaction data accepted by the transaction data acceptance module 2033. The template data extracted by the template extraction module 2034 is, for example, workflow data indicating procedures for quotation, ordering, etc., and form layout data for quotations, purchase orders, etc., and is used as template data to be used for managing commercial transactions related to the accepted transaction data.

[0058] The template extraction module 2034 searches the template database 2021 based on, for example, information about the entities related to the transaction contained in the transaction data and information about the contents of the case, and extracts template data that the user or other users have used (by editing) in past transactions, or template data that has been edited by a user with a similar industry type, transaction content, corporate size, etc. of the entity of the transaction, as recommended template data to be used for the transaction data.

[0059] User presentation module 2035 controls the process of presenting the template data extracted by template extraction module 2034 to the user associated with the transaction data accepted by transaction data acceptance module 2033. User presentation module 2035 transmits the template data to terminal device 10 via communication unit 201. Terminal device 10 receives the template data via transmission / reception unit 182, and causes the template data to be displayed on display 150 through processing by notification control unit 183, for presenting the template data to the user associated with the transaction data.

[0060] The template selection receiving module 2036 controls the process of receiving an input to select one of the template data presented by the user presentation module 2035 from a user related to the transaction data received by the transaction data receiving module 2033. For example, the terminal device 10 receives an input to select one of the template data from a user related to the transaction data through processing by the input operation receiving unit 181. At this time, the user selects template data to be used in his / her transaction according to the business type, transaction content, corporate size, etc. of the trading partner, or according to preference.

[0061] When the user selects one of the template data, terminal device 10 transmits information about the template data selected by the user via transmission / reception unit 182. Template selection reception module 2036 receives and accepts the information about the template data selected by the user via communication unit 201.

[0062] The template selection receiving module 2036 stores the template data selected by the user in the transaction database 2022 as the template data to be used for the transaction data.

[0063] The template edit receiving module 2037 controls the process of receiving edit input for template data selected by the user that has been received by the template selection receiving module 2036. At this time, the user performs edit input on terminal device 10 with the selected template data displayed on display 150 of terminal device 10, and therefore terminal device 10 receives the edit input for the template data through processing by input operation receiving unit 181. Terminal device 10 transmits information about the edit input for template data by the user via transmission / reception unit 182. The template edit receiving module 2037 receives and accepts information about the edit input for template data by the user via communication unit 201.

[0064] For example, the user edits the template data selected by the user to apply the business partner's company name, address, person in charge name, and transaction details. The template edit reception module 2037 receives such edit input for the template data.

[0065] Furthermore, the user performs editing input for template data selected by the user to change the layout of forms, for example, by changing the font and character size from those of the template data, changing the position and color of each entry item such as company name and item, etc. The template editing reception module 2037 receives such editing input for template data.

[0066] The template edit reception module 2037 also controls the process of storing template data for which edit input has been accepted as template data related to the transaction data accepted by the transaction data reception module 2033. The template edit reception module 2037 stores the template data for which edit input has been accepted in the transaction database 2022. At this time, the template edit reception module 2037 stores the template data in association with the transaction data stored in the transaction database 2022.

[0067] Furthermore, the template edit receiving module 2037 controls the process of storing the template data for which edit input has been accepted as new template data in the template database 2021. At this time, the template edit receiving module 2037 may link the template data for which edit input has been accepted to the attribute data of the user, for example, linking the attribute data of the user as tag data, and storing and storing the new template data in the template database 2021. Note that the attribute data of the user may be obtained from user information 171 of terminal device 10.

[0068] Furthermore, the template edit reception module 2037 may link the template data for which edit input has been received to transaction target data related to the product or service that is the subject of the commercial transaction, and store and memorize it as new template data in the template database 2021. Specifically, the template edit reception module 2037 links the template data to information on the subjects related to the transaction and information on the content of the case, which are included in the transaction data, and stores and memorizes it in the template database 2021 as new template data.

[0069] The template publishing module 2038 controls the process of publishing the template data stored in the template database 2021 by the template edit receiving module 2037 in a state where it can be viewed by other users. For example, the template publishing module 2038 may publish the template so that it can be referenced only by users who are members of the sales management system 1 provided as a Web service, or may publish the template so that it can be referenced only by general users who are not members. Furthermore, the template publishing module 2038 may publish the template so that it can be referenced only by some members of the sales management system 1 who are provided with a specific service, such as paid members or users who are members of a specific course.

[0070] <2 Data Structure> Hereinafter, the data structures referenced by the sales management system 1 will be described with reference to Fig. 5 and Fig. 6. Fig. 5 is a diagram showing an example of the data structure of the template database 2021 in Fig. 4. Fig. 6 is a diagram showing an example of the data structure of the transaction database 2022 in Fig. 4.

[0071] As shown in FIG. 5, each record of the template database 2021 includes an item "user ID", an item "user name", an item "template data details", and the like.

[0072] The item "user ID" is information for identifying each user who manages transaction data, which is a function of the sales management system 1, and who views, selects, and edits template data.

[0073] The item "user name" is the name or information indicating the name of a user of the sales management system 1, and for example, the name of a corporation, the name of a person in charge, or the personal name of a sole proprietor is stored.

[0074] The item "template data details" is management information related to template data managed by the sales management system 1, and specifically includes the item "template data ID", the item "template data", the item "remarks", etc. This item "template data details" is a data group that manages various information required for managing transaction data, and is data that serves as a model for transaction data related to commercial transactions.

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

[0076] The item "template data" is a group of data that manages various information required for managing transaction data managed by the sales management system 1, and is stored in a data format that can describe the data placement position, for example, in XML format.

[0077] The item "Notes" is supplementary information about the template data managed by the sales management system 1. In the example shown in FIG. 5, when the template data is form layout data, information indicating the type of form and the characteristics of the form layout data is stored.

[0078] The template data stored in the template database 2021 includes template data that is stored in advance as initial data of the sales management system 1, and template data that has been edited by a user and accepted by the template edit acceptance module 2037.

[0079] As shown in FIG. 6, each record of the transaction database 2022 includes an item "customer ID", an item "customer name", an item "industry type", an item "detailed transaction information", and the like.

[0080] The item "Customer ID" is information included in the transaction data managed by the sales management system 1 and identifies each business entity that is a customer.

[0081] The item "Customer Name" is information indicating the name of the customer included in the transaction data managed by the sales management system 1, and stores, for example, the corporate name, the name of the person in charge, or the personal name of a sole proprietor.

[0082] The item "Industry" is information that indicates the business type of the trading partner, which is included in the transaction data managed by the sales management system 1. In the example shown in Figure 6, the names of business types such as "wholesale industry" and "sales industry" are stored.

[0083] The item "transaction detail information" is management information regarding transaction data managed by the sales management system 1, and specifically includes the items "date", "summary", "item", and "amount". This item "transaction detail information" is information registered by users such as business operators and personnel in charge regarding daily transactions, and is configured so that the latest information is added as a record in chronological order of the item "date", for example.

[0084] The item “Date” is information on the date on which a transaction related to the transaction data managed by the sales management system 1 occurred.

[0085] The item "Summary" is information indicating whether a transaction related to the transaction data managed by the sales management system 1 is an expenditure (withdrawal) or income (deposit); for example, if it is an expenditure, "expense" information is stored, and if it is income, "income" information is stored.

[0086] The item "item" is information indicating the content of a specific good, service, etc., for a transaction related to the transaction data managed by the sales management system 1.

[0087] The item “amount” is information indicating the amount of deposit and withdrawal for a transaction related to the transaction data managed by the sales management system 1.

[0088] The server 20 adds a record to the item “transaction detail information” of the transaction database 2022 as the server 20 receives information about the transaction from the user.

[0089] <3 operations> Hereinafter, the payment data generation process and the payment data transmission process performed by the sales management system 1 in the first embodiment will be described with reference to FIGS.

[0090] FIG. 7 is a flowchart showing an example of a flow of template data selection processing performed by the sales management system 1.

[0091] In step S111, the input operation receiving unit 181 of the terminal device 10 receives an operation to input transaction data related to a commercial transaction from a user who is an employee of a business enterprise or a sole proprietor, etc. The transmitting / receiving unit 182 transmits the received transaction data and user information 171 to the server 20.

[0092] In step S121, the transaction data receiving module 2033 of the server 20 receives the transaction data and user information 171 transmitted in step S111 via the communication unit 201. The transaction data received in step S121 is, for example, various information about a transaction conducted with other business operators, specifically, information about the parties involved in the transaction such as an orderer, an order recipient, and a purchaser, information about the contents of the case, delivery date, amount, and the like.

[0093] In step S122, based on the transaction data accepted in step S121, the template extraction module 2034 of the server 20 extracts template data recommended for use with the transaction data from the template data stored in the template database 2021. In step S122, the template data is extracted based on, for example, information contained in the transaction data about the entities related to the transaction and information about the contents of the case.

[0094] In step S123, the user presentation module 2035 of the server 20 transmits the template data extracted in step S122 to the terminal device 10 via the communication unit 201 in order to present the template data to the user associated with the transaction data accepted in step S121.

[0095] In step S113, transmitter / receiver unit 182 of terminal device 10 of the user related to the transaction data accepted in step S121 accepts the template data sent from server 20. Notification control unit 183 causes display 150 to display the accepted template data.

[0096] In step S114, input operation acceptance unit 181 of terminal device 10 accepts an input to select one of the template data displayed on display 150 in step S113. At this time, the user selects the template data to be used for his or her transaction according to the business type, transaction content, corporate size, etc. of the trading partner, or according to preference. Transmitting / receiving unit 182 transmits information about the selected template data to server 20.

[0097] In step S124, the template selection receiving module 2036 of the server 20 receives the template data selected by the user and transmitted in step S114 via the communication unit 201. The template selection receiving module 2036 also registers the template data selected by the user by storing it in the transaction database 2022.

[0098] As described above, when the sales management system 1 receives input of transaction data related to commercial transactions from a user, it extracts template data recommended for use with the transaction data based on the transaction data and presents it to the user. Then, when it receives an input from the user to select one of the presented template data, it registers it as the template data to be used with the transaction data. This makes it possible to refer to and select and use template data, including form data, created by other users. This makes it possible for the sales management system to improve convenience and satisfaction for customers.

[0099] FIG. 8 is a flowchart showing an example of a flow of a template edit data transmission process performed by the sales management system 1.

[0100] In step S211, the input operation acceptance unit 181 of the terminal device 10 accepts editing input for the template data displayed on the display 150 in step S113. At this time, with the selected template data displayed on the display 150 of the terminal device 10, the user performs editing input for applying the trading partner's company name, address, name of the person in charge, and transaction details, and editing input for changing the layout of forms, which are examples of template data, to the terminal device 10. The transmitting / receiving unit 182 transmits information on the editing input for the accepted template data to the server 20.

[0101] In step S221, the template edit reception module 2037 of server 20 receives via communication unit 201 information about the edit input for the template data edited by the user that was sent in step S211. The template edit reception module 2037 also stores and stores the template data for which edit input has been accepted in transaction database 2022 as template data related to the transaction data. Furthermore, the template edit reception module 2037 stores and stores the template data for which edit input has been accepted in template database 2021 as new template data.

[0102] In step S222, the template edit receiving module 2037 of the server 20 makes the template data stored in step S221 publicly available to other users so that it can be viewed.

[0103] As described above, the sales management system 1 accepts editing input for template data selected by the user from the user, registers it as template data related to the transaction data, and also registers it as new template data. Then, the template data registered as new template data is made public in a state that other users can view it. Therefore, the template data that demonstrates the user's design sense can be shared with other users. This can lead to improved convenience and satisfaction for customers.

[0104] <4 Screen example> An example of a screen of template data published by the sales management system 1 will be described below with reference to FIG.

[0105] Fig. 9 is a diagram showing an example of a screen displaying published template data on the terminal device 10. The example screen of Fig. 9 shows an example of a screen displaying template data that has been published by the template publishing module 2038 in a state that can be viewed by other users, and is displayed on the display 150. This corresponds to step S222 in Fig. 8.

[0106] As shown in Fig. 9, a window 1031 is displayed on the display 150 of the terminal device 10. This window 1031 displays a template data display screen 1031a that is stored in the template database 2021 and is made publicly available so that other users can view it. In the example shown in Fig. 10, the template data display screen 1031a displays the user's corporate name, etc. in a user display field 1031b, the type of template data edited by the user is displayed in a category display field 1031c, and the template data edited by the user is displayed in a data display field 1031d. In addition, an explanation field 1031e that indicates the contents of the template data, etc. is displayed to the right of the data display field 1031d.

[0107] Other users can understand what the template data in the data display column 1031d is like by referring to the user display column 1031b, category display column 1031c, and explanation column 1031e displayed on the template data display screen 1031a. By opening the data display column 1031d, it is possible to understand the detailed contents of the template data. Based on this, the user can determine whether or not the template data can be used for their own transaction data.

[0108] <Summary> As described above, according to this embodiment, when input of transaction data related to a commercial transaction is accepted from a user, template data recommended for use with the transaction data is extracted based on the transaction data and presented to the user. Then, when an input to select one of the presented template data is accepted from the user, it is registered as the template data to be used with the transaction data. This makes it possible to refer to and select and use template data, including form data, created by other users. This makes it possible to improve convenience and satisfaction for customers in the sales management system.

[0109] Furthermore, according to this embodiment, editing input for template data selected by a user is accepted from the user, and the edited input is registered as template data related to the transaction data, and also registered as new template data. Then, the template data registered as new template data is made public in a state that other users can view. Therefore, template data that demonstrates the user's design sense can be shared with other users. This can lead to improved convenience and satisfaction for customers.

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

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

[0112] (Supplementary Note 1) A program to be executed by a computer having a processor 29 and a memory 25 for managing commercial transactions relating to a user, wherein the memory 25 stores template data (2021) required for managing the commercial transactions, and the program causes the processor 29 to execute the following steps: accepting from the user input of transaction data relating to the commercial transaction relating to the user (S121); accepting from the user editing input for template data selected from the stored template data to be used for managing the commercial transaction relating to the accepted transaction data (S221); and storing the template data edited by the user as template data relating to the accepted transaction data, and making it publicly available for viewing by other users (S222).

[0113] (Appendix 2) The program described in (Appendix 1), in which the memory stores user attribute data and, in a step of storing template data edited by the user, stores the template data required for managing commercial transactions in association with the user attribute data.

[0114] (Appendix 3) A program as described in (Appendix 1), in which in a step of accepting transaction data, transaction target data relating to goods or services that are the subject of a commercial transaction is accepted, and in a step of storing template data edited by a user, the transaction target data is linked as tag data to the template data required for managing the commercial transaction and stored.

[0115] (Supplementary Note 4) The program described in any of (Supplementary Note 1) to (Supplementary Note 3), further executing the steps of: extracting, based on the accepted transaction data, one or more of the template data edited by other users as template data to be used for managing the commercial transaction related to the accepted transaction data (S122); presenting the extracted template data to the user who accepted the transaction data (S123); and accepting, from the user who accepted the transaction data, an input selecting one of the presented template data (S124).

[0116] (Supplementary Note 5) An information processing device comprising a control unit 203 and a memory (storage unit 202), and managing commercial transactions related to a user, wherein the memory (storage unit 202) stores template data (2021) required for managing the commercial transactions, and the control unit 203 executes the following steps: accepting from the user input of transaction data related to the user's commercial transaction (S121); accepting from the user editing input for template data selected from the stored template data to be used for managing the commercial transaction related to the accepted transaction data (S221); and storing the template data edited by the user as template data related to the accepted transaction data, and publishing the template data in a state where it can be viewed by other users (S222).

[0117] (Supplementary Note 6) A method for managing commercial transactions relating to a user, executed by a computer including a processor 29 and a memory 25, wherein the memory 25 stores template data (2021) required for managing the commercial transactions, and the method executes the following steps by the processor 29: accepting from the user input of transaction data relating to the commercial transaction relating to the user (S121); accepting from the user editing input for template data selected from the stored template data to be used for managing the commercial transaction relating to the accepted transaction data (S221); and storing the template data edited by the user as template data relating to the accepted transaction data, and making it publicly available for viewing by other users (S222). [Explanation of symbols]

[0118] 1: Sales management system 10: Terminal device 10A: Terminal device 10B: 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: Camera 170: Storage section 171: User information 180: Control section 181: Input operation reception section 182: Transmitter / receiver 183: Notification control section 184: Data processing section 201: Communications Department 202: Storage section 203: Control section 1031 : Window 1031a: Template data display screen 1031b: User display column 1031c: Category display column 1031d: Data display column 1031e: Description 2021: Template Database 2022: Trade Database 2031: Receiving control module 2032: Transmission control module 2033: Transaction data reception module 2034: Template extraction module 2035: User presentation module 2036: Template selection reception module 2037: Template editing reception module 2038: Template publishing module

Claims

1. A program for managing commercial transactions related to a user when executed by a computer having a processor and a memory, the memory stores template data required for managing the commercial transaction; The program causes the processor to: receiving, from the user, an input of transaction data relating to the commercial transaction pertaining to the user; receiving, from the user, an edit input for template data selected from the stored template data and used for managing the commercial transaction related to the received transaction data; storing the template data edited by the user as template data related to the accepted transaction data, and publishing the template data in a state where it can be viewed by other users.

2. The memory stores attribute data of the user; 2. The program according to claim 1, wherein in the step of storing the template data edited by the user, attribute data of the user is linked to the template data required for managing the commercial transaction and stored.

3. In the step of accepting the transaction data, transaction target data relating to a product or service that is the subject of the commercial transaction is accepted; 2. The program according to claim 1, wherein in the step of storing the template data edited by the user, the transaction object data is linked to the template data required for managing the commercial transaction as tag data and stored.

4. The program further comprises: extracting one or more of the template data edited by other users based on the accepted transaction data as template data to be used for managing the commercial transaction related to the accepted transaction data; presenting the extracted template data to a user who has accepted the transaction data; 4. The program according to claim 1, further comprising: a step of receiving an input from a user who has received the transaction data, for selecting one of the presented template data.

5. An information processing device that includes a control unit and a memory, and manages commercial transactions related to a user, the memory stores template data required for managing the commercial transaction; The control unit is receiving, from the user, an input of transaction data relating to the commercial transaction pertaining to the user; receiving, from the user, an edit input for template data selected from the stored template data and used for managing the commercial transaction related to the received transaction data; and storing the template data edited by the user as template data related to the accepted transaction data, and publishing the template data in a state where it can be viewed by other users.

6. 1. A method for managing a commercial transaction involving a user, the method being executed by a computer having a processor and a memory, the method comprising: the memory stores template data required for managing the commercial transaction; The method further comprises the processor: receiving, from the user, an input of transaction data relating to the commercial transaction pertaining to the user; receiving, from the user, an edit input for template data selected from the stored template data and used for managing the commercial transaction related to the received transaction data; storing the template data edited by the user as template data related to the accepted transaction data, and making the template data publicly available for other users to view.

Citation Information

Patent Citations

  • Document management system

    JP2007072769A

  • Specific business management system, method for controlling specific business management system, and specific business management program

    JP2008004049A

  • Template management device and program

    JP2016170537A

  • Document template sharing system and providing method thereof

    KR1020150096004A

  • Business form creation processing system and business form creation processing method and program

    JP2012098878A