Information processing device, information processing method, program, and information processing system

Abstract

To reduce the time and effort required for managing a document form issued in an external system.SOLUTION: An information processing apparatus includes: an input receiving unit which receives an input of external form information in a tabular format formed by associating item names and item values extracted from a document form generated in an external system; and a display control unit which causes a terminal device to display a setting screen for selecting an item value to be associated with a column in which an item value of a certain item name has been deleted, in the external form information, from an item value in another column.SELECTED DRAWING: Figure 18

Description

[Technical Field]

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

[0002] A conventional system for managing deposits from a deposit source is known. For example, a system is known in which a deposit management terminal issues an invoice, sends it to a business partner, and receives a notification of completion of the deposit made in accordance with the invoice, along with the invoice. Summary of the Invention [Problem to be solved by the invention]

[0003] In the conventional systems described above, it is not possible to associate invoices issued by external systems with deposits made in accordance with these invoices, and it is not possible to manage the form information contained in forms issued by external systems. For this reason, in recent years, systems that handle forms have begun to import form information from external systems. However, in the past, depending on the system environment, etc., it was sometimes necessary to make adjustments when importing form information from external systems, which made management time-consuming.

[0004] The present invention has been made in view of the above circumstances, and aims to reduce the effort required to manage forms issued by an external system. [Means for solving the problem]

[0005] The disclosed technology includes an input receiving unit that receives input of external form information in a table format in which item names and item values ​​extracted from a form created in an external system are associated with each other; The external form information includes preview image data of the form created in the external system, a first selection field that accepts selection of a row from which an item value corresponding to an item name has been deleted among item names included in the external form information, a second selection field that accepts selection of another row different from the row selected in the first selection field, and a third selection field that accepts selection of an item name in the other row selected in the second selection field. a display control unit that displays a setting screen on a terminal device; The other row selected in the second selection field The aforementioned a registration unit that generates form information including information that associates an item value corresponding to an item name selected in a third selection field with an item name whose item value has been deleted in the row selected in the first selection field; The information processing device has the following. [Effects of the Invention]

[0006] The disclosed technology can reduce the effort required to manage forms issued by external systems. [Brief explanation of the drawings]

[0007] [Figure 1] FIG. 1 is a diagram illustrating an example of a system configuration of a transaction management system. [Figure 2] FIG. 2 illustrates an example of a hardware configuration of a transaction management device. [Figure 3] FIG. 2 illustrates an example of a hardware configuration of a terminal device. [Figure 4] FIG. 2 illustrates an example of a tenant management database. [Figure 5] FIG. 10 is a diagram illustrating an example of a placement definition database. [Figure 6] FIG. 10 is a diagram illustrating an example of an association definition database. [Figure 7] FIG. 10 is a diagram illustrating an example of a document template database. [Figure 8] FIG. 10 is a diagram illustrating document template information. [Figure 9] 2 is a diagram illustrating the functional configuration of each device of the transaction management device. FIG. [Figure 10] FIG. 10 is a diagram illustrating an example of external form information. [Figure 11] FIG. 10 is a diagram illustrating an example of intermediate data. [Figure 12] This is a first sequence diagram explaining the operation of the transaction management system. [Figure 13] FIG. 10 is a second sequence diagram illustrating the operation of the transaction management device. [Figure 14] 10 is a flowchart illustrating a process of reading external form information. [Figure 15] 10 is a flowchart illustrating the processing of a transaction management device. [Figure 16] FIG. 10 is a first diagram showing an example of a display on a seller terminal. [Figure 17] FIG. 10 is a second diagram showing an example of a display on the seller terminal. [Figure 18] FIG. 10 is a third diagram showing an example of a display on a seller terminal. [Figure 19] FIG. 4 is a fourth diagram showing an example of a display on a seller terminal. [Figure 20] FIG. 5 is a fifth diagram showing an example of a display on a seller terminal. [Figure 21] FIG. 6 is a sixth diagram showing an example of a display on a seller terminal. DETAILED DESCRIPTION OF THE INVENTION

[0008] The following describes an embodiment with reference to the drawings: Fig. 1 is a diagram showing an example of the system configuration of a transaction management system.

[0009] Transaction management system 100 of this embodiment includes transaction management device 200 and terminal device 400, and transaction management device 200 and terminal device 400 are connected via a network or the like.

[0010] The terminal device 400 of this embodiment is a terminal device that is mainly used by a seller in a buying and selling transaction. The terminal device includes various terminal devices such as a PC (Personal Computer), a smart terminal (smartphone), a tablet terminal, etc. (The same applies to the terminal device 300 described later). In the following explanation, for the convenience of explaining this embodiment, the terminal device 400 may be referred to as a seller terminal 400.

[0011] Furthermore, the transaction management system 100 of this embodiment is connected to a terminal device 300 via a network. The terminal device 300 is a terminal device that is primarily used by buyers in sales transactions. In the following description, for the sake of convenience in explaining this embodiment, the terminal device 300 may be referred to as a buyer terminal 300.

[0012] In the following description, a user who uses a service provided by the transaction management system 100 of this embodiment may be referred to as a tenant. In other words, in this embodiment, a tenant is a business operator or an individual who acts as a seller or buyer.

[0013] The external system 500 of this embodiment is, for example, a sales management system independently managed by a seller tenant, and communicates with the seller terminal 400 via a network or the like. The external system 500 of this embodiment creates documents such as invoices in response to operations from the seller terminal 400.

[0014] In this embodiment, the form is, for example, an estimate, an order form, a delivery note, an invoice, etc. Furthermore, the form information in this embodiment is information written on these forms. For example, if the form is an invoice, the form information includes detailed information written on the invoice, such as the billing source, billing destination, billing amount, payment due date, product name, unit price, quantity, amount, etc. of the product to be invoiced.

[0015] In the following description, an invoice will be used as an example of a form, and form information written on the invoice will be referred to as invoice information.

[0016] The transaction management device 200 of this embodiment manages invoices exchanged between businesses and individuals who conduct sales transactions.

[0017] More specifically, the transaction management device 200 of this embodiment manages each item contained in the invoice information (document information) of an invoice (document) created in the external system 500 in association with each item used when creating the invoice (document) in the transaction management device 200.

[0018] The transaction management device 200 of this embodiment includes a tenant management database 210, a placement definition database 220, a correspondence definition database 230, a document template database 240, a form management database 250, and a transaction management unit 260.

[0019] The tenant management database 210 stores information about tenants.

[0020] The placement definition database 220 stores placement definition information generated by the transaction management system 100. The placement definition information is referenced when displaying a form image of a form generated by the external system 500. Details of the placement definition information will be described later.

[0021] The correspondence definition database 230 stores correspondence definition information that associates item names included in a form created by the external system 500 with item names used when creating the form by the transaction management device 200. Details of the correspondence definition information will be described later.

[0022] The document template database 240 stores document template information. The document template information is information that indicates the position at which the item name and item value of each item included in a form are displayed in a preview image for each type of form. In other words, the document template information is information that defines a template image of the form. Details of the document template information will be described later. Note that the item values ​​in this embodiment are information that are entered in association with the item names, and are character string data for the item names, such as alphanumeric characters, kana characters, and various symbols.

[0023] Form management database 250 stores form image data and form information of forms created by transaction management device 200. Form management database 250 also stores form information of forms created by external system 500 and form image data created by transaction management device 200 from this form information.

[0024] In the following description, a form created in the external system 500 may be referred to as an external form, and form information of a form created in the external system 500 may be referred to as external form information. The external form information is data in a table format, and may be a CSV file or the like.

[0025] The external form information is information in which item names and item values ​​included in a form created by the external system 500 are associated with each other. Specifically, the external form information of this embodiment includes, for example, rows containing item names extracted from the form and rows containing item values ​​extracted from the form. In addition, in the external form information, in rows containing item values, the item values ​​are associated with the item names according to the position (column) of the item value.

[0026] Furthermore, in the external form information of this embodiment, when duplicate item values ​​are included in multiple rows, the duplicate item values ​​may be deleted.

[0027] If item values ​​are erased from rows of external report information, in order to read the external report information into the transaction management system 100, it was necessary to modify the external report information so that all rows contained item names and corresponding item values.

[0028] However, this adjustment is time-consuming and involves the possibility of human error during the adjustment process.

[0029] Therefore, the transaction management unit 260 of this embodiment displays a setting screen on the seller terminal 400 for associating a row in the external report information in which the item value of a certain item name has been erased with a row in which the item name and the corresponding item value are included.

[0030] More specifically, the transaction management unit 260 causes the seller terminal 400 to display a setting screen that allows the user to select an item value to be associated with a row in which the item value of a certain item name has been deleted from the item values ​​of other rows.

[0031] Therefore, in this embodiment, when importing external form information, there is no need to manually revise the external form information, which can reduce the effort required to manage forms issued by the external system 500. Details of the external form information in this embodiment will be described later.

[0032] In addition, the transaction management unit 260 of this embodiment generates correspondence definition information that associates item names included in external form information created by the external system 500 with item names used when creating forms in the transaction management device 200, and stores the information in the correspondence definition database 230. Furthermore, the transaction management unit 260 generates placement definition information that links the document template information specified when creating the correspondence definition information with the correspondence definition information, and stores the information in the placement definition database 220.

[0033] Furthermore, the transaction management unit 260 of this embodiment creates form image data based on the external form information, based on the external form information and the placement definition database 220, and displays a preview image on the seller terminal 400. Therefore, in this embodiment, the seller can easily understand how the item names included in the external form information are placed on the form image.

[0034] In this embodiment, this allows the report information created in the external system 500 to be replaced with and managed by the report information created in the transaction management device 200. In other words, in this embodiment, the report created in the external system 500 can be managed in the same way as the report created in the transaction management system 100.

[0035] Therefore, in this embodiment, even if a seller tenant uses multiple external systems 500, the documents can be managed in a centralized manner, thereby reducing the effort required to manage the documents.

[0036] In this embodiment, the management of forms includes, for example, checking whether payment has been received from the invoice recipient (buyer) by the payment due date specified on the invoice, urging the invoice recipient (buyer) to make payment if payment has not been confirmed by the payment due date, and clearing accounts receivable by checking the amount of payment against the amount invoiced. In addition, the management of invoices may also include the management of the history of invoices sent to invoice recipients.

[0037] 1, the transaction management device 200 has a tenant management database 210, a placement definition database 220, a correspondence definition database 230, a document template database 240, and a form management database 250, but is not limited to this. Some or all of each database may be provided in an external device. Furthermore, the transaction management device 200 may be realized by multiple information processing devices.

[0038] Next, the hardware configuration of an information processing device that realizes transaction management device 200 will be described with reference to FIG.

[0039] Figure 2 shows an example of the hardware configuration of a transaction management device. Transaction management device 200 is constructed by a computer, and as shown in Figure 2, includes CPU 201, ROM 202, RAM 203, HD 204, HDD (Hard Disk Drive) controller 205, display 206, external device connection I / F (Interface) 208, network I / F 209, bus line B1, keyboard 211, pointing device 212, DVD-RW (Digital Versatile Disk Rewritable) drive 214, and media I / F 216.

[0040] Of these, the CPU 201 controls the overall operation of the transaction management device 200. The ROM 202 stores programs used to drive the CPU 201, such as the IPL. The RAM 203 is used as a work area for the CPU 201. The HD 204 stores various data, such as programs. The HDD controller 205 controls the reading and writing of various data from and to the HD 204 under the control of the CPU 201. The display 206 displays various information, such as a cursor, menu, window, text, or image.

[0041] The external device connection I / F 208 is an interface for connecting various external devices. In this case, the external devices are, for example, USB (Universal Serial Bus) memories, printers, etc. The network I / F 209 is an interface for data communication using a communication network. The bus line B1 is an address bus, a data bus, etc. for electrically connecting each component such as the CPU 201 shown in FIG. 2.

[0042] The keyboard 211 is a type of input means having multiple keys for inputting characters, numbers, various instructions, etc. The pointing device 212 is a type of input means for selecting and executing various instructions, selecting a processing target, moving a cursor, etc. The DVD-RW drive 214 controls reading and writing of various data from and to a DVD-RW 213, which is an example of a removable recording medium. Note that this is not limited to a DVD-RW, and may be a DVD-R, etc. The media I / F 216 controls reading and writing (storing) of data from and to a recording medium 215, such as a flash memory.

[0043] 3 is a diagram showing an example of the hardware configuration of a terminal device (seller terminal) 400. In FIG.

[0044] The terminal device 400 of this embodiment includes a CPU 401 , a ROM 402 , a RAM 403 , an EEPROM 404 , a CMOS sensor 405 , an image sensor I / F 406 , an acceleration / direction sensor 407 , a media I / F 409 , and a GPS receiving unit 411 .

[0045] Of these, the CPU 401 is an arithmetic processing unit that controls the overall operation of the terminal device 400. The ROM 402 stores programs used to drive the CPU 401, such as the CPU 401 and the IPL. The RAM 403 is used as a work area for the CPU 401. The EEPROM 404 reads or writes various data, such as terminal device programs, under the control of the CPU 401. The ROM 402, RAM 403, and EEPROM 404 are examples of storage devices for the terminal device 400. The bus line B2 is an address bus, a data bus, or the like, for electrically connecting the components, such as the CPU 401, shown in FIG. 3.

[0046] The CMOS (Complementary Metal Oxide Semiconductor) sensor 405 is a type of built-in imaging means that captures an image of a subject (mainly a self-portrait) and obtains image data under the control of the CPU 401. Note that instead of a CMOS sensor, an imaging means such as a CCD (Charge Coupled Device) sensor may also be used.

[0047] The imaging element I / F 406 is a circuit that controls the driving of the CMOS sensor 405. The acceleration / azimuth sensor 407 is a variety of sensors, such as an electronic magnetic compass that detects geomagnetism, a gyrocompass, and an acceleration sensor. The media I / F 409 controls the reading and writing (storage) of data from and to a recording medium 408, such as a flash memory. The data bus 410 is an address bus, a data bus, or the like, for electrically connecting the various components, such as the CPU 401, shown in FIG. 3. The GPS receiver 411 receives GPS signals from GPS satellites.

[0048] The terminal device 400 also includes a long-distance communication circuit 412, an antenna 412a of the long-distance communication circuit 412, a CMOS sensor 413, an image sensor I / F 414, a microphone 415, a speaker 416, an audio input / output I / F 417, a display 418, an external device connection I / F (Interface) 419, a short-distance communication circuit 420, an antenna 420a of the short-distance communication circuit 420, and a touch panel 421.

[0049] Of these, the long-distance communication circuit 412 is a circuit that communicates with other devices via a communication network. The CMOS sensor 413 is a type of built-in imaging means that captures an image of a subject and obtains image data under the control of the CPU 401. The image sensor I / F 414 is a circuit that controls the driving of the CMOS sensor 413. The microphone 415 is a built-in circuit that converts sound into an electrical signal. The speaker 416 is a built-in circuit that converts an electrical signal into physical vibrations to generate sound such as music or voice. The sound input / output I / F 417 is a circuit that processes the input and output of sound signals between the microphone 415 and the speaker 416 under the control of the CPU 401.

[0050] The display 418 is a type of display means such as a liquid crystal display or organic electroluminescence (EL) display that displays an image of a subject, various icons, etc. The external device connection I / F 419 is an interface for connecting various external devices. The short-range communication circuit 420 is a communication circuit such as NFC (Near Field Communication) or Bluetooth (registered trademark). The touch panel 421 is a type of input means that allows a user to operate the terminal device 400 by pressing the display 418. The display 418 is an example of a display unit that the terminal device 400 has.

[0051] In addition, buyer terminal 300 and seller terminal 400 of this embodiment may have the same hardware configuration as transaction management device 200.

[0052] Next, each database included in the transaction management device 200 will be described with reference to FIGS.

[0053] 4 is a diagram showing an example of a tenant management database. The tenant management database 210 of this embodiment is provided, for example, for each tenant. The tenant management database 210 of this embodiment includes information items such as name, address, telephone number, email address, and name of person in charge, and these items are associated with tenant IDs and tenant names.

[0054] In this embodiment, information in the tenant management database 210 that includes values ​​for items such as name, address, telephone number, email address, and person in charge name may be referred to as tenant information. The tenant ID and tenant name are information for identifying a tenant. The value of the item "name" indicates the name of the business partner (billing party), and the values ​​of the items "address," "telephone number," "email address," and "person in charge name" indicate the address, telephone number, email address, and name of the person in charge of the transaction of the billing party, respectively.

[0055] Note that the information items included in the tenant information are not limited to the example shown in Fig. 4. The information items included in the tenant information do not need to include all the items shown in Fig. 4, and may include items other than the items shown in Fig. 4.

[0056] 5 is a diagram showing an example of a placement definition database. In this embodiment, a placement definition database 220 is provided for each tenant, and when placement definition information is created in a tenant, the placement definition information is stored in the placement definition database 220 for each tenant.

[0057] FIG. 5 shows the placement definition database 220 of the tenant identified by the tenant ID "0001."

[0058] The document template database 240 of this embodiment includes information items such as a document type, a correspondence definition ID, and a document template ID, each of which is associated with a tenant ID. In this embodiment, information including the value of the item "tenant ID" and the values ​​of the other items in the placement definition database 220 is referred to as placement definition information.

[0059] The value of the item "placement definition name" indicates the name of the placement definition information. In other words, the value of the item "placement definition name" is information for identifying the placement definition information.

[0060] The value of the item "Matching definition ID" indicates identification information for identifying the mapping definition information. The value of the item "Document template ID" indicates identification information for identifying the document template information.

[0061] In the example of Figure 5, the invoice (document) identified by the document type name "Invoice 001" has item names placed in the invoice image based on the correspondence definition information identified by the correspondence definition ID "1" and the document template information identified by the document template ID "1".

[0062] 6 is a diagram showing an example of the association definition database. The association definition database 230 of this embodiment is provided for each tenant, but may be configured such that definition information associated with the identification information (tenant ID) of the tenant is stored in one or more databases together with other tenants.

[0063] The correspondence definition database 230 of this embodiment includes, as information items, a tenant ID, a correspondence definition ID, an item name of form information, and an item name of external form information. In the correspondence definition database 230, the item "item name of form information" and the item "external form information" are associated with the item "tenant ID" and the item "correspondence definition ID."

[0064] In this embodiment, information including the value of the item "tenant ID" and the values ​​of other items in the association definition database 230 is expressed as association definition information.

[0065] The value of the item "Matching definition ID" is identification information for identifying the matching definition information. The value of the item "Item name of report information" is the item name used when creating a report in the transaction management device 200. The value of the item "Item name of external report information" is the item name included in the external report information.

[0066] In the example of Figure 6, in the correspondence definition information identified by the correspondence definition ID "1," the item names "Document Title," "Document Number," and "Destination Name" of the report information are respectively associated with the item names "Title," "Invoice Number," and "Customer Name" contained in the external report information.

[0067] 7 is a diagram showing an example of the document template database 240. The document template database 240 of this embodiment is created in advance for each tenant and stored in the transaction management device 200.

[0068] The document template database 240 of this embodiment includes, as information items, tenant ID, document template ID, document type, document template name, form information item name, coordinates, placement method, font size, etc. In the document template database 240, the item "tenant ID" and the item "document template ID" are associated with other items.

[0069] In this embodiment, information including the value of the item "tenant ID" and the values ​​of other items in the document template database 240 is expressed as document template information.

[0070] The value of the item "Document Type" indicates the type of form. The value of the item "Document Template Name" indicates the name of the document template.

[0071] The value of the "Coordinates" item indicates the coordinates of the reference position of the rectangle that displays the item name of the corresponding form information. The value of the "Layout" item indicates the layout method of the character string within the rectangle. The value of the "Font" item indicates the font of the characters.

[0072] It should be noted that the information items included in document template database 240 are not limited to the example shown in Fig. 7. Document template database 240 may include information items other than those shown in Fig. 7.

[0073] The document template information will be further described below with reference to Fig. 8. Fig. 8 is a diagram illustrating the document template information.

[0074] In this embodiment, the coordinates in the document template information may be absolute coordinates from the top left point P1 of the document 80 on A4 paper, for example.

[0075] Also, for example, if the alignment method for the item name "Document Title" in the report information is centered, the coordinates corresponding to this item name will be the coordinates of the center point P2 of the rectangle 82 in which the value of the item name "Document Title" is displayed.

[0076] Also, for example, if the item name "Document Number" in the report information is aligned left, the coordinates corresponding to this item name will be the coordinates of point P3 at the left end of rectangle 83 in which the value of the item name "Document Number" is displayed.

[0077] Next, the functional configuration of each device included in transaction management system 100 of this embodiment will be described with reference to Fig. 9. Fig. 9 is a diagram illustrating the functional configuration of each device included in the transaction management system.

[0078] First, we will explain the functions of the transaction management device 200. The transaction management unit 260 of the transaction management device 200 of this embodiment has a transmission unit 261, a reception unit 262, an input acceptance unit 263, a display control unit 264, an image generation unit 265, a definition generation unit 266, an association unit 267, and a registration unit 268.

[0079] The transmitter 261 and receiver 262 transmit and receive information between the transaction management device 200 and other devices.

[0080] Specifically, the sending unit 261 sends the invoice image data stored in the form management database 250 to the destination buyer terminal 300, etc. The receiving unit 262 receives the external invoice information created in the external system 500 from the seller terminal 400.

[0081] Input receiving unit 263 receives various inputs to transaction management device 200. Specifically, input receiving unit 263 receives various information inputs and requests from seller terminal 400.

[0082] The display control unit 264 controls the display on the seller terminal 400. Specifically, for example, the display control unit 264 causes the seller terminal 400 to display a setting screen for allowing the user to select an item value to be associated with a row in which an item value of a certain item name has been deleted from among the items included in the external form information, from the item values ​​of other rows.

[0083] The image generation unit 265 generates preview image data of the form created by the external system 500. In other words, the image generation unit 265 generates external form image data. More specifically, the image generation unit 265 controls the display of the seller terminal 400 via a display control unit 450 of the seller terminal 400, which will be described later, so that the image data is displayed on the display of the seller terminal 400.

[0084] The definition generating unit 266 generates association definition information and placement definition information in response to an operation on the seller terminal 400 , and stores them in the association definition database 230 and placement definition database 220 .

[0085] When a setting is made on the setting screen displayed on the seller terminal 400 to select the item values ​​to be included in a row from which an item value has been erased, the association unit 267 associates the row from which the item value has been erased with the selected item value according to the setting content, and temporarily stores the external report information after the association has been made.

[0086] In the following description, the external form information after association, which is temporarily held by the association unit 267, may be referred to as intermediate data. Therefore, the association unit 267 generates intermediate data in which the item values ​​included in all rows included in the external form information are associated with the item names, according to the settings input from the seller terminal 400.

[0087] The registration unit 268 references the placement definition database 220 , generates form information by replacing the item names included in the external form information with the item names of the form information, and stores the generated form information in the form management database 250 .

[0088] Furthermore, when intermediate data is generated for the external form information by the association unit 267, the registration unit 268 of this embodiment uses the generated intermediate data to generate form information in which the item names included in the external form information are replaced with the item names of the form information. In other words, the registration unit 268 generates the replaced external form information from the external form information or the intermediate data.

[0089] In the following description, form information in which the item names contained in the external form information have been replaced with the item names used when creating a form in the transaction management device 200 may be referred to as replaced form information.

[0090] The registration unit 268 of this embodiment associates the replaced form information with the external form image data created by the image generation unit 265 and stores them in the form management database 250. At this time, the external form image data stored in the form management database 250 may be stored as, for example, PDF data.

[0091] Next, the functions of seller terminal 400 will be described. Seller terminal 400 of this embodiment has a communication control unit 430, an input reception unit 440, and a display control unit 450. Communication control unit 430 transmits and receives information between seller terminal 400 and other devices. Specifically, for example, communication control unit 430 controls communication between seller terminal 400 and external system 500 and communication between seller terminal 400 and transaction management device 200.

[0092] Input receiving unit 440 receives input of various information to seller terminal 400. Display control unit 450 controls the display of information on the display of seller terminal 400.

[0093] Here, the processing of the association unit 267 of this embodiment will be described with reference to Fig. 10 and Fig. 11. Fig. 10 is a diagram showing an example of external form information. The external form information 30 shown in Fig. 10 is data in a table format. In the following description, the first column from the left side of the paper and the first row from the top of the paper will be described.

[0094] In the external form information 30, the first line 31 includes the names of items included in the external form from which the external form information 30 is extracted. Specifically, in the external form information 30, line 31 includes the names of items such as "voucher number," "customer code," "customer name," "consumption tax," "total invoice amount," "product name," "unit price," "quantity," and "amount."

[0095] In the external form information 30, the first column 32 contains information that identifies the item names and corresponding item values ​​included in the external form. Specifically, column 32 contains "header," "total," "details," etc.

[0096] Furthermore, in the external form information 30, the first row 31 includes an item "row type" in addition to the item names included in the external form. The item "row type" is also included in the first column 32. The value of the item "row type" indicates information that identifies the item value that corresponds to the other item name included in row 31. In other words, the value of the item "row type" indicates the name of each row from the second row onwards, and is information that indicates the item name that corresponds to the value included in each row.

[0097] In the example of Figure 10, the line containing the item "line type" and the item name included in the external form is the first line 31, but the line containing the item "line type" and the item name included in the external form does not have to be the first line.

[0098] In the external form information 30, the value of the item "Row Type" in the second line 33 is "Header." The "Header" indicates the bibliographic information of the external form, and in this embodiment, the "Header" includes item names indicating the issue date of the external form, such as "Invoice Date," "Customer Code," and "Customer Name." In other words, line 33 includes item values ​​indicating the bibliographic information of the external form.

[0099] Furthermore, in the external form information 30, the value of the item "Line Type" in the fourth line 34 is "Details." "Details Information" indicates the details of the external form, and includes the item values ​​of the item names "Product Name," "Unit Price," "Quantity," and "Amount." In other words, line 34 includes item values ​​that indicate the details information of the external form.

[0100] Here, in row 34, the field values ​​corresponding to the field names "Invoice Date," "Customer Code," and "Customer Name" have been erased and left blank. This is because the field values ​​corresponding to the field names "Invoice Date," "Customer Code," and "Customer Name" in row 34 overlap with the field values ​​of the field names "Invoice Date," "Customer Code," and "Customer Name" included in row 33.

[0101] In addition, in the external form information 30, the fifth line 35 and the sixth line 36 also contain item values ​​indicating detailed information included in the external form, similar to line 34. In addition, in lines 35 and 36, the item values ​​corresponding to the item names "voucher date," "customer code," and "customer name" have been erased (removed).

[0102] In this way, in the external form information 30, duplicate item values ​​are removed from rows that contain item values ​​that overlap with other rows, depending on the specifications of the external system 500 that outputs the external form information 30.

[0103] Therefore, in this embodiment, if there is a row in the external form information 30 where an item value that overlaps with another row has been deleted, the seller terminal 400 displays a setting screen for allowing the seller to select an item value to be associated with the row where the item value has been deleted from the item values ​​of the other rows. Next, the transaction management device 200 generates intermediate data by the association unit 267 that associates the item value of the selected other row with the row where the item value has been deleted.

[0104] In other words, the association unit 267 generates intermediate data that includes, for all rows included in the external form information 30, item values ​​that correspond to the item names included in the external form.

[0105] Fig. 11 is a diagram showing an example of intermediate data. Intermediate data 30A shown in Fig. 11 is an example of intermediate data generated when, on the setting screen displayed on seller terminal 400, the item values ​​corresponding to the item names "voucher date," "customer code," and "customer name" included in row 33 of external form information 30 are paired with rows 34, 35, and 36.

[0106] In the intermediate data 30A, rows 34, 35, and 36 of the external form information 30 include rows 34A, 35A, and 36A in which the item names "voucher date," "customer code," and "customer name" are associated with corresponding item values.

[0107] Specifically, row 34A includes the item values ​​"Product A," "1000," "10," and "10000" for the item names "Product Name," "Unit Price," "Quantity," and "Amount," and the item values ​​"2021 / 1 / 10," "1001," and "A Trading Company" for the item names "Invoice Date," "Customer Code," and "Customer Name." The item values ​​of the item names "Product Name," "Unit Price," "Quantity," and "Amount" are item values ​​contained only in row 34 of the external document information 30, and the item values ​​of the item names "Invoice Date," "Customer Code," and "Customer Name" are item values ​​contained only in row 33 of the external document information 30.

[0108] Therefore, it can be seen that in row 34A, the item values ​​corresponding to the item names "voucher date," "customer code," and "customer name" have been selected from the item values ​​in row 33 as the item values ​​to be associated with row 34. In addition, row 34A also shows that the item values ​​corresponding to the item names "voucher date," "customer code," and "customer name" selected from the item values ​​in row 33 have been associated with the item values ​​of the item names "product name," "unit price," "quantity," and "amount" included in row 34.

[0109] Similarly, row 35A includes item values ​​that are included only in row 35 of the external form information 30 and item values ​​that are included only in row 33 of the external form information 30. Similarly, row 36A includes item values ​​that are included only in row 36 of the external form information 30 and item values ​​that are included only in row 33 of the external form information 30.

[0110] Thus, in this embodiment, if the external report information 30 includes a row in which an item value that overlaps with another row has been deleted, the item value selected from the other row is applied as the deleted item value, depending on the settings entered by the user (seller) of the seller terminal 400.

[0111] In the following explanation, matching the item value contained in a row from which the item value of a certain item name has been deleted with the item value selected from another row (the deleted item value) may be expressed as "applying the item value selected from another row to the row from which the item value has been deleted."

[0112] More specifically, associating the item values ​​of the item names "Product Name," "Unit Price," "Quantity," and "Amount" contained in row 34, from which the item values ​​corresponding to the item names "Invoice Date," "Customer Code," and "Customer Name" have been deleted, with the item values ​​corresponding to the item names "Invoice Date," "Customer Code," and "Customer Name" selected from row 33, can be said to "apply the item values ​​selected from row 33 to row 34."

[0113] The above is the process of generating intermediate data by the association unit 267.

[0114] Next, the operation of the transaction management system 100 of this embodiment will be described with reference to Fig. 12. Fig. 12 is a first sequence diagram illustrating the operation of the transaction management system.

[0115] FIG. 12 shows the operation when an instruction to register external form information is received from seller terminal 400 to transaction management device 200, and when new placement definition information corresponding to this external form information is created.

[0116] In this embodiment, registering external report information in the transaction management device 200 includes replacing the item names contained in the external report information with the item names used when creating reports in the transaction management device 200 to create replaced report information, and storing the replaced report information in the report management database 250.

[0117] In addition, in this embodiment, registering external document information in the transaction management device 200 includes storing external document image data created based on the external document information in the document management database 250 in association with the replaced document information.

[0118] In the transaction management system 100 of this embodiment, when the seller terminal 400 receives an operation from a tenant instructing the registration of external report information (step S1201), it sends a request to the transaction management device 200 to display a report registration screen for registering the external report information (step S1202).

[0119] When transaction management device 200 receives the display request, display control unit 264 transmits an instruction to seller terminal 400 to display the form registration screen (step S1203).

[0120] Upon receiving this display instruction, seller terminal 400 causes display control unit 450 to display the form registration screen on display 418 (step S1204).

[0121] The following processing from step S1205 onwards shows the case where placement definition information corresponding to external form information is newly created.

[0122] The case where new placement definition information is created is, for example, when placement definition information corresponding to external form information is not stored in the placement definition database 220.

[0123] When the seller terminal 400 receives an operation from a tenant to select a definition registration screen for registering placement definition information (step S1205), the display control unit 450 causes the display 418 to display the definition registration screen (step S1206).

[0124] Next, the seller terminal 400 accepts the input of a new placement definition name and the selection of external report information through the tenant's operation (step S1207), and then transmits the input placement definition name and the selected external report information to the transaction management device 200 (step S1208).

[0125] In this embodiment, if an existing placement definition name is selected in step S1207, the selected placement definition name may be sent to the transaction management device 200 together with external form information, and the placement definition information identified by the placement definition name may be edited. The operation of the transaction management device 100 when editing the placement definition information is the same as the operation from step S1209 onwards, which will be described later.

[0126] Furthermore, the external form information may be a CSV file, etc. The external form information may be downloaded from the external system 500 to the seller terminal 400 in advance and stored in the seller terminal 400.

[0127] Furthermore, the operations from step S1209 to step S1215 described below show the case where the external form information sent from seller terminal 400 includes a row that is not associated with an item value of the form issued from external system 500. In other words, Figure 10 shows the operation when, when association is performed by association unit 267, external form information is registered in transaction management device 200 using intermediate data temporarily stored in association unit 267.

[0128] In addition, if the external report information sent from the seller terminal 400 corresponds to all rows contained in the external system 500 with the item values ​​of the issued report, the transaction management device 200 simply proceeds to step S1216 after step S1208.

[0129] When the seller terminal 400 receives an operation instructing the setting of item values ​​to be applied to rows in the external report information where the item values ​​have been deleted (step S1209), it sends a request to set the correspondence to the transaction management device 200 (step S1210).

[0130] When transaction management device 200 receives the setting request through input receiving unit 263, it transmits to seller terminal 400 an instruction to display a setting screen for applying the item values ​​(step S1211).

[0131] Seller terminal 400 receives this display instruction and causes display control unit 450 to display the settings (step S1212).

[0132] Next, seller terminal 400 accepts settings on the setting screen for applying item values ​​to the rows from which the item values ​​have been deleted (step S1213), and transmits the settings to transaction management device 200 (step S1214).

[0133] The transaction management device 200 uses the association unit 267 to apply item values ​​selected from other rows to rows where an item name and corresponding item value have been deleted, according to the settings (step S1215). In other words, the transaction management device 200 uses the association unit 267 to generate intermediate data based on the external form information and the association settings.

[0134] Next, when seller terminal 400 accepts the selection of a document template by the tenant's operation (step S1216), it notifies transaction management device 200 of the selected document template (step S1217). Specifically, seller terminal 400 transmits the selected document template ID to transaction management device 200.

[0135] When the transaction management device 200 receives notification of the document template through the definition generating unit 266, the transaction management device 200 acquires template image data indicating a template image corresponding to the document template (step S1218).

[0136] Note that the template image data corresponding to the document template may be stored in association with the document template ID in the document template database 240. The template image data may also be generated by the image generation unit 265 based on the selected document template information.

[0137] Next, transaction management device 200 reads the external form information transmitted from seller terminal 400 in step S1208 by definition generation unit 266 (step S1219). At this time, if intermediate data has been generated, definition generation unit 266 reads the intermediate data instead of the external form information. Details of the processing in step S1219 will be described later.

[0138] Next, transaction management apparatus 200 causes display control unit 264 to send an instruction to seller terminal 400 to display the template image (step S1220).

[0139] Seller terminal 400 receives the display instruction and displays the template image on the registration screen (step S1221).

[0140] Next, when the seller terminal 400 receives an operation on the registration screen to associate the item names included in the external report information with the item names used when creating the report information (step S1222), it highlights the results of the association on the registration screen (step S1223).

[0141] Next, when the seller terminal 400 receives an operation instructing the registration of the matching results (step S1224), it sends a registration request to the transaction management device 200 for the matching definition information indicating the matching results and the placement definition information (step S1225).

[0142] When transaction management device 200 receives the registration request, definition generation unit 266 generates association definition information and placement definition information, and stores them in association definition database 230 and placement definition database 220 (step S1226).

[0143] Specifically, the definition generation unit 266 assigns an association definition ID to the information indicating the association result between items in response to the tenant's operation, stores the information as association definition information in the association definition database 230. Furthermore, the definition generation unit 266 associates the document template ID transmitted from the seller terminal 400 in step S1210 with the association definition ID assigned to the information indicating the association result. Then, the definition generation unit 266 associates the placement definition name, document template ID, and association definition ID received from the seller terminal 400 in step S1208, and stores them in the placement definition database 220.

[0144] By the above operation, new placement definition information is stored.

[0145] Next, with reference to FIG. 13, an operation for registering external form information in transaction management device 200 using placement definition information stored in placement definition database 220 will be described.

[0146] FIG. 13 is a second sequence diagram illustrating the operation of the transaction management device.

[0147] The processing from step S1301 to step S1304 in FIG. 13 is the same as the processing from step S1201 to step S1204 in FIG. 12, and therefore a description thereof will be omitted.

[0148] When the seller terminal 400 accepts an operation to select the placement definition name and external form information on the form registration screen displayed in step S1304 (step S1305), it sends a registration request for the placement definition name and external form information to the transaction management device 200 (step S1306).

[0149] The transaction management device 200 accepts this registration request, and associates the external form information with the external form image data and registers them in the form management database 250 (step S1307).

[0150] Next, the reading of external form information by the definition generating unit 266 of this embodiment will be described with reference to Fig. 14. Fig. 14 is a flowchart illustrating the processing for reading external form information. Fig. 14 shows details of step S1219 in Fig. 12.

[0151] When the definition generation unit 266 of the transaction management device 200 of this embodiment receives notification of a document template, it acquires template image data indicating a template image corresponding to the document template, and then determines whether or not the association unit 267 has associated the external form information (step S1401). If association has not been performed in step S1201, the definition generation unit 266 reads the external form information sent from the seller terminal 400 in step S1208 (step S1402), and ends the process.

[0152] In step S1401, if association with external form information has been performed, the definition generating unit 266 reads the intermediate data held by the association unit 267 instead of the external form information (step S1403), and ends the process.

[0153] Next, the registration process of external form information and external form image data in transaction management device 200 will be described with reference to Fig. 15. Fig. 15 is a flowchart illustrating the process of transaction management device 200. Fig. 15 shows details of step S1307 in Fig. 13.

[0154] In the transaction management device 200 of this embodiment, the definition generating unit 266 reads the first line of data from the CSV file acquired as external form information (step S1501).

[0155] Next, the transaction management device 200, through the registration unit 268, refers to the placement definition database 220 and identifies the correspondence definition information and document template information from the correspondence definition ID and document template ID linked to the selected placement definition name (step S1502).

[0156] Next, the registration unit 268 generates rewritten form information in which the item names included in the external form information are replaced with the item names of the form information based on the identified association definition information (step S1503).

[0157] Next, the transaction management device 200 causes the image generating unit 265 to specify the layout of the item names included in the replaced form information based on the document template information specified in step S1502 (step S1504).

[0158] Next, the image generating unit 265 generates preview image data (external form image data) based on the identified layout (step S1505).

[0159] The external form image data created here is image data that displays the item names used when creating a form using transaction management device 200.

[0160] Next, the transaction management device 200 causes the image generation unit 265 to associate the replaced form information with the external form image data and store them in the form management database 250 (step S1506).

[0161] In this embodiment, for example, if the CSV file contains external form information for external forms issued to multiple different buyers, the process of Fig. 15 can be repeated until the registration of all the external form information contained in the CSV file is completed. Therefore, in this embodiment, the seller can collectively register the external invoice information for multiple buyers created in the external system 500 in the transaction management device 200.

[0162] Below, examples of displays on seller terminal 400 will be described with reference to FIGS.

[0163] Fig. 16 is a first diagram showing a display example of the seller terminal. Screen 131 shown in Fig. 16 is an example of a form registration screen displayed on seller terminal 400 in step S1204 of Fig. 12 (step S1304 of Fig. 13).

[0164] Screen 131 includes tabs 132 and 133. Fig. 16 shows an example in which tab 132 is selected on screen 131. Tab 132 is selected when external form information is to be registered by referring to placement definition information already stored in the correspondence definition database 230.

[0165] When a tab 133 is selected, the screen 131 transitions to a definition registration screen for newly registering placement definition information.

[0166] The screen 131 includes a display area 134, selection fields 135 and 136, and an operation button 137. The display area 134 displays the placement definition name and a message prompting the user to select a CSV file (external form information).

[0167] An icon image 135a is associated and displayed in the selection field 135. When the icon image 135a is selected on the screen 131, a list of placement definition names stored in the placement definition database 220 is displayed. The placement definition name displayed from the list is displayed in the selection field 135.

[0168] Selection field 136 displays the file name of a CSV file selected from the CSV files downloaded to seller terminal 400. Operation button 137 is an operation button for issuing a registration instruction to register the CSV file selected in selection field 136 in transaction management device 200.

[0169] Next, the definition registration screen will be described with reference to Fig. 17. Fig. 17 is a second diagram showing an example of a display on the seller terminal.

[0170] Screen 141 shown in FIG. 17 is an example of a definition registration screen displayed on seller terminal 400 in step S1206 of FIG.

[0171] The screen 141 includes display areas 142 , 143 , 144 , and 145 and an operation button 146 .

[0172] A preview of the external form image is displayed in display area 142. On screen 141, the item names included in the CSV file are being associated with the item names of the form information, so a template image corresponding to the document template information is displayed in display area 142.

[0173] Specifically, the display area 142 displays a template image corresponding to document template information with a document type of "invoice" and a document template name of "professional."

[0174] In the display area 143, a definition registration screen is displayed with options for selecting whether to register new placement definition information or edit placement definition information.

[0175] The display area 144 includes a selection field 144-1, an input field 144-2, a selection field 144-3, an operation button 144-4, and display fields 144-5 and 144-6. The selection field 144-1 is used to select the placement definition name of the placement definition information to be edited. The input field 144-2 is used to input the placement definition name of the placement definition information to be newly added.

[0176] In the selection field 144-3, the name of the CSV file that is the external form information to be registered is selected.

[0177] Operation button 144-4 is an operation button for sending a setting request to transaction management device 200 to apply an item value selected from another row to the row whose item value has been deleted. In other words, operation button 144-4 is an operation button for displaying a setting screen for applying an item value selected from another row to the row whose item value has been deleted.

[0178] Display field 144-5 displays the document type of the referenced document template information, and display field 144-6 displays the name of the referenced document template information.

[0179] The example in FIG. 17 shows a case where new placement definition information named "Invoice 001" is registered, and it can be seen that document template information with a document type of "Invoice" and a document template name of "Professional" is used.

[0180] Display area 145 displays a correspondence field for associating the item names included in the CSV file with the item names of the form information.

[0181] Specifically, for example, display area 145 displays a list of item names of form information included in document template information with document type "invoice" and document template name "professional" from document template database 240.

[0182] Also displayed in the display area 145 are a selection field for associating the item names of the displayed list of form information with the item names included in the CSV file, and an operation button for confirming the association.

[0183] Specifically, a selection field 145-1 is displayed in the display area 145 for selecting the item name of the CSV file to be associated with the item name "document number" of the form information. The selection field 145-1 is displayed in association with the item name "document number." Furthermore, an operation button 145-1a is displayed in association with the selection field 145-1.

[0184] In this embodiment, when operation button 144-4 is operated on screen 141, screen 141 transitions to screen 141A, which will be described later.

[0185] 18 is a third diagram showing an example of a display on the seller terminal 400. Screen 141A shown in FIG. 18 is an example of a setting screen displayed on seller terminal 400 in step S1212 of FIG.

[0186] Screen 141 includes display areas 142, 143, 144A, and 147, and operation button 146. Although not shown in Fig. 18, display area 144A includes display area 145 below display area 147. On screen 141A, display area 145 is displayed within display area 144A by scrolling scroll bar 148.

[0187] The display area 147 includes selection fields 147a, 147b, and 147c, and operation buttons 147d and 147e. The display area 147 also includes a selection field 147f and an operation button 147g.

[0188] The selection column 147a is a selection column for selecting a column indicating the name of each row included in the external form information.

[0189] In this embodiment, the column showing the name of each row included in the external form information is the first column 32 containing the item name "Row Type" (see FIG. 10). Therefore, on screen 141A, "Row Type" is selected in selection field 147a.

[0190] Selection field 147b is a selection field for selecting the row to which the item value is to be applied. In other words, selection field 147b is a selection field for selecting the name of the row to which the item value is to be associated in the external form information. The row to which the item value is to be applied is a row from which the item value corresponding to some item name has been deleted from the item names included in the external form.

[0191] On the screen 141A, “Details” is selected as the name of the row to which the item values ​​are to be applied. Note that the row selected here to which the item values ​​are to be applied may be row 34 of the external form information 30.

[0192] Row 34 is a row in which the field values ​​corresponding to the field names "Document Number," "Customer Code," and "Customer Name" contained in the external report have been deleted, and as will be described later, this is the row to which the field values ​​of row 33 are applied.

[0193] Selection field 147c is a selection field for selecting the row to which the item value is to be applied. On screen 141A, "Header" is selected as the name of the row to which the item value is to be applied.

[0194] Each of the selection columns 147b and 147c may display a list of the names of the rows included in the external form information 30. In this case, the name of the row selected in the selection column 147a, "row type," is not included in the list.

[0195] Operation button 147d is an operation button for adding selection field 147b in display area 147, and operation button 147e is an operation button for adding selection field 147c.

[0196] When operation button 147d is operated, selection field 147b is added, allowing multiple rows to be selected as destinations for the item value. When operation button 147e is operated, selection field 147c is added, allowing multiple rows to be selected as destinations for the item value.

[0197] Selection column 147f is a selection column for selecting an item name to which the item value is to be applied in the row selected in selection column 147c. Operation button 147g is an operation button for adding selection column 147f.

[0198] On screen 141A, "Header" is selected in selection field 147c. Therefore, in selection field 147f, an item name is selected from the item names whose item value is included in the row named "Header."

[0199] In the external form information 30, the row named "Header" is row 33 (see FIG. 10). Therefore, on the screen 141A, the item names "Voucher Number," "Customer Code," and "Customer Name," whose item values ​​are included in row 33, are selected in the selection field 147f.

[0200] In this embodiment, by entering information into the setting screen in this manner, the item values ​​of the item names "voucher number," "customer code," and "customer name" contained in row 33 of external document information 30 are associated with the item values ​​of the item names "voucher number," "customer code," and "customer name" in row 34 selected in selection field 147b.

[0201] In this embodiment, when the setting contents indicating this association are transmitted to the transaction management device 200, the association unit 267 generates a row 34A in the intermediate data 30A.

[0202] In this embodiment, this association is set for all rows in the external form information 30 that contain item names whose item values ​​have been deleted, thereby generating intermediate data 30A.

[0203] In this embodiment, the row containing the item name whose item value has been deleted is selected as the destination to which the item value will be applied, and the row containing the deleted item value is selected as the row to which the item value will be applied, thereby making it possible to associate each row with the item value of the item name contained in the external report.

[0204] Therefore, in this embodiment, the user (seller) of the seller terminal 400 does not need to directly edit the tabular external form information 30, and can easily associate the item names with the item values ​​in each row. Therefore, in this embodiment, the transaction management system 100 can easily read the external form information 30, reducing the effort required to manage forms issued by an external system.

[0205] In this embodiment, once the association in the display area 147 of the screen 141A is completed, the item names included in the external form information 30 (CSV file) are associated with the item names of the form information in the display area 145.

[0206] In this embodiment, for example, the display area 145 may be displayed by moving the scroll bar 148.

[0207] In this embodiment, an operation button for ending the setting of the association between the item name and the item value in each row may be displayed in the display area 147. In this case, when this operation button is operated, the screen 141A may transition to the screen 141 including the display area 145.

[0208] Fig. 19 is a fourth diagram showing a display example of the seller terminal. Screen 141B shown in Fig. 19 shows the process of associating the item names included in external form information 30 (CSV file) with the item names of the form information.

[0209] On screen 141B, the item name "invoice number" included in the CSV file is selected in selection field 145-1. In this embodiment, when operation button 145-1a is operated in this state, the item name "invoice number" included in the CSV file (external form information) is associated with the item name "document number" of the form information.

[0210] Also displayed in display area 145 is a selection field 145-2 for selecting the item name of the CSV file to be associated with the item name "destination name" of the form information. Selection field 145-2 is displayed in association with the item name "destination name." Furthermore, an operation button 145-2a associated with selection field 145-2 is displayed.

[0211] On screen 141B, the item name "Customer Name" included in the CSV file is selected in selection field 145-2. In this embodiment, when operation button 145-2a is operated in this state, the item name "Customer Name" included in the CSV file (external form information) is associated with the item name "Destination Name" of the form information.

[0212] In this embodiment, the item names included in the external form information are associated with the item names of the form information in this way. Therefore, the display area 145 of this embodiment can also be said to be a correspondence field for associating the item names of the form information with the item names included in the external form information.

[0213] On screen 141B, after the operation of associating the item names included in the external report information with the item names of the report information is completed, when operation button 146 is operated, the seller terminal 400 sends a request to register placement definition information to the transaction management device 200.

[0214] 20 is a fifth diagram showing an example of a display on a seller terminal. Screen 141C shown in FIG. 20 shows a state in which item names are associated with each other in display area 144.

[0215] In FIG. 20, a list 149 of item names included in the CSV file is displayed in a selection field 145-3 corresponding to the item name "Destination Address" of the form information, and "Customer Address" is selected in this list 149.

[0216] In this embodiment, when operation button 145-3a is operated in this state, the item name "client address" included in the CSV file is associated with the item name "recipient address" in the form information.

[0217] Fig. 21 is a sixth diagram showing a display example of a seller terminal. On screen 141D shown in Fig. 21, when an item name of external form information 30 (CSV file) is selected in display area 145, the item value of the form information associated with the item name of the selected CSV file is highlighted in the preview image displayed in display area 142.

[0218] On screen 141D, pointer 150 is used to select the item name "invoice number" of the CSV file selected in selection field 145-1 of display area 145. In this embodiment, the item name selected by pointer 150 is displayed highlighted.

[0219] Additionally, in the preview image displayed in the display area 142, an area 142a displaying the item value corresponding to the item name "invoice number" of the CSV file is highlighted. Note that the item name "invoice number" may also be displayed together with the item value in the area 142a.

[0220] That is, in this embodiment, the display mode of the item name of the external form information selected in the display area 145 and the selected item name and item value in the preview image is made different from that of other item names.

[0221] In this way, in this embodiment, when an item name contained in external form information is associated with an item name in the form information, if an item name in the external form information is selected, the area in the preview image of the external form image where the value of the selected item name is displayed is highlighted.

[0222] Therefore, in this embodiment, when a preview image is created by replacing the item names of external report information with the item names of report information, the viewer can easily understand where in the report image the item values ​​corresponding to the item names of the external report information are displayed.

[0223] Each function of the above-described embodiments can be realized by one or more processing circuits. Here, the term "processing circuit" in this specification includes a processor programmed to perform each function by software, such as a processor implemented by an electronic circuit, as well as devices such as an ASIC (Application Specific Integrated Circuit), a DSP (Digital Signal Processor), an FPGA (Field Programmable Gate Array), or a conventional circuit module designed to perform each function described above.

[0224] Additionally, the devices described in the embodiments are merely representative of one of several computing environments for implementing the embodiments disclosed herein.

[0225] In one embodiment, transaction manager 200 includes multiple computing devices, such as a server cluster, configured to communicate with each other over any type of communication link, including a network, shared memory, etc., to perform the processing disclosed herein. Similarly, transaction manager 200 may include multiple computing devices configured to communicate with each other.

[0226] Furthermore, transaction management device 200 can be configured to share the disclosed processing steps in various combinations. For example, the processes performed by transaction management device 200 can be performed by other server devices. Similarly, the functions of transaction management device 200 can be performed by other server devices. Also, each element of the server device and the other server devices can be implemented by a single server device. The server devices may be integrated into one server device, or may be separated into multiple devices.

[0227] The correspondence table in the statement may be generated by the learning effect of machine learning. Also, by using machine learning to classify keywords that may be included in the description of transaction details and account items, it is not necessary to use a correspondence table.

[0228] Here, machine learning is a technology that allows a computer to acquire human-like learning capabilities, in which the computer autonomously generates algorithms necessary for judgments such as data classification from learning data that is input in advance, and applies these to new data to make predictions. The learning method for machine learning may be any of supervised learning, unsupervised learning, semi-supervised learning, reinforcement learning, and deep learning, or may be a combination of these learning methods; any learning method for machine learning is acceptable.

[0229] Although the present invention has been described above based on the embodiments, the present invention is not limited to the requirements shown in the above embodiments. These requirements can be changed without departing from the spirit of the present invention, and can be appropriately determined depending on the application form. [Explanation of symbols]

[0230] 100 Transaction Management System 200 Transaction Management Device 210 Tenant Management Database 220 Placement Definition Database 230 Mapping definition database 240 document template database 250 Report Management Database 260 Transaction Management Department 264 Display Control Unit 265 Image Generation Unit 266 Definition generator 267 Mapping Section 268 Registration Department 300 Terminal device (buyer terminal) 400 Terminal Device (Seller Terminal) 500 External Systems [Prior art documents] [Patent documents]

[0231] [Patent Document 1] Japanese Patent Application Laid-Open No. 2002-183640

Claims

1. an input receiving unit that receives input of external form information in a table format in which item names and item values ​​extracted from a form created in an external system are associated with each other; a display control unit that displays on a terminal device a setting screen including preview image data of the form created in the external system, a first selection field that accepts the selection of a row from among the item names included in the external form information, where the item value corresponding to the item name has been deleted, a second selection field that accepts the selection of another row different from the row selected in the first selection field, and a third selection field that accepts the selection of the item name in the other row selected in the second selection field; an information processing device having a registration unit that generates report information including information that associates an item value corresponding to an item name selected in the third selection column of the other row selected in the second selection column with an item name whose item value has been deleted in the row selected in the first selection column.

2. An information processing device as described in claim 1, having a matching unit that generates intermediate data in which an item value corresponding to an item name selected in the third selection column of the other row selected in the second selection column is matched with an item name whose item value has been deleted in the row selected in the first selection column.

3. The display control unit When the external form information includes a line in which an item value of a certain item name has been deleted, the setting screen is displayed on the terminal device; The information processing apparatus according to claim 2 , wherein the intermediate data is generated when the setting screen is displayed on the terminal device.

4. a definition generating unit that generates correspondence definition information that defines correspondence between item names included in the external form information and item names used when creating a form in the information processing device; The definition generation unit An information processing device as described in claim 2 or 3, wherein when the intermediate data is generated based on the external report information, the correspondence definition information is generated based on the result of correspondence on a registration screen for correlating item names included in the intermediate data with item names used when creating the report.

5. An information processing method by an information processing device, the information processing device comprising: Accepts input of external form information in a table format that associates item names and item values ​​extracted from forms created in an external system, displaying on the terminal device a setting screen including preview image data of the form created in the external system, a first selection field for accepting selection of a row from among item names included in the external form information, where an item value corresponding to the item name has been deleted, a second selection field for accepting selection of another row different from the row selected in the first selection field, and a third selection field for accepting selection of an item name in the other row selected in the second selection field; An information processing method that generates report information including information that associates an item value corresponding to an item name selected in the third selection column of the other row selected in the second selection column with an item name whose item value has been deleted in the row selected in the first selection column.

6. The information processing device, 6. An information processing method according to claim 5, further comprising generating intermediate data in which an item value corresponding to an item name selected in the third selection column of the other row selected in the second selection column is associated with an item name whose item value has been deleted in the row selected in the first selection column.

7. The information processing device, When the external form information includes a line in which an item value of a certain item name has been deleted, the setting screen is displayed on the terminal device; The information processing method according to claim 6 , wherein the intermediate data is generated when the setting screen is displayed on the terminal device.

8. generating correspondence definition information that defines correspondence between item names included in the external form information and item names used when creating a form in the information processing device; The correspondence definition information is An information processing method as described in claim 6 or 7, wherein when the intermediate data is generated based on the external report information, the intermediate data is generated based on the result of correspondence on a registration screen for correlating the item names contained in the intermediate data with the item names used when creating the report.

9. Accepts input of external form information in a table format that associates item names and item values ​​extracted from forms created in an external system, displaying on the terminal device a setting screen including preview image data of the form created in the external system, a first selection field for accepting selection of a row from among item names included in the external form information, where an item value corresponding to the item name has been deleted, a second selection field for accepting selection of another row different from the row selected in the first selection field, and a third selection field for accepting selection of an item name in the other row selected in the second selection field; A program that generates report information including information that associates the item value corresponding to the item name selected in the third selection column of the other row selected in the second selection column with the item name whose item value has been deleted in the row selected in the first selection column.

10. An information processing system in which an information processing device and a terminal device are connected via a network, The information processing device includes: an input receiving unit that receives input of external form information in a table format in which item names and item values ​​extracted from a form created in an external system are associated with each other; a display control unit that displays on a terminal device a setting screen including preview image data of the form created in the external system, a first selection field that accepts the selection of a row from among the item names included in the external form information, where the item value corresponding to the item name has been deleted, a second selection field that accepts the selection of another row different from the row selected in the first selection field, and a third selection field that accepts the selection of the item name in the other row selected in the second selection field; an information processing system having a registration unit that generates report information including information that associates an item value corresponding to an item name selected in the third selection column of the other row selected in the second selection column with an item name whose item value has been deleted in the row selected in the first selection column.

Images