JP7464068B2 - Trade management system and trade management method - Google Patents

Description

The present invention relates to a transaction management system and a transaction management method .

There are known conventional deposit management systems that manage deposits from deposit sources. One example is a system that transmits invoices issued by a deposit management terminal to business partners, and receives a deposit completion notification for deposits made in accordance with the invoice, with the notification associated with the invoice.

In the conventional system described above, if an invoice is issued by the system, it is not possible to match the invoice with the deposit made in accordance with the invoice, and it is not possible to manage payments corresponding to the invoice.

The present invention was made in consideration of the above circumstances, and aims to make it possible to manage forms issued by external systems.

The disclosed technology is a transaction management system that manages form image data of a form issued by an external system, and includes: a first reception unit that receives an import instruction for form image data of a form issued by the external system and form information included in the form; a transmission unit that transmits a display request for an import operation screen for performing an import operation when the first reception unit receives the import instruction ; a display control unit that displays the import operation screen based on the display request sent from the transmission unit; a second reception unit that receives a selection of the form image data and the form information to be imported on the import operation screen displayed by the display control unit; and a registration unit that associates the form image data and the form information whose selection has been received and registers them in an invoice management database .

You can manage reports issued by external systems.

FIG. 2 is a diagram illustrating an example of a system configuration of a transaction management system. FIG. 2 is a diagram illustrating an example of a hardware configuration of a transaction management device. FIG. 2 illustrates an example of a hardware configuration of a terminal device. FIG. 2 illustrates an example of a tenant management database according to the first embodiment; FIG. 2 is a first diagram illustrating an example of an invoice management database according to the first embodiment. A diagram explaining the functional configuration of each device of the transaction management system of the first embodiment. A first sequence diagram explaining the operation of the transaction management system of the first embodiment. FIG. 13 is a diagram showing an example of a CSV file. FIG. 11 is a first diagram showing a display example of a seller terminal according to the first embodiment; FIG. 13 is a second diagram showing an example of a display of the seller terminal in the first embodiment. FIG. 13 is a third diagram showing an example of a display of the seller terminal in the first embodiment. FIG. 4 is a fourth diagram showing a display example of the seller terminal of the first embodiment. A second sequence diagram explaining the operation of the transaction management system of the first embodiment. 1 is a first flowchart illustrating the processing of a transaction management device according to a first embodiment. FIG. 5 is a fifth diagram showing a display example of the seller terminal of the first embodiment. FIG. 6 is a sixth diagram showing an example of a display of the seller terminal according to the first embodiment. A third sequence diagram explaining the operation of the transaction management system of the first embodiment. FIG. 7 is a seventh diagram showing an example of a display of the seller terminal in the first embodiment. 13 is a second flowchart illustrating the processing of the transaction management device of the first embodiment. 13 is a third flowchart illustrating the processing of the transaction management device of the first embodiment. FIG. 13 is an eighth diagram showing a display example of the seller terminal of the first embodiment. FIG. 13 is a second diagram showing an example of the invoice management database of the first embodiment. FIG. 13 is a ninth diagram showing a display example of the seller terminal of the first embodiment. FIG. 13 is a third diagram showing an example of the invoice management database of the first embodiment. FIG. 10 is a tenth diagram showing a display example of the seller terminal of the first embodiment. A diagram explaining the functional configuration of each device of the transaction management system of the second embodiment. FIG. 13 illustrates an example of an invoice management database according to the second embodiment; A first sequence diagram explaining the operation of the transaction management system of the second embodiment. FIG. 13 is a first diagram showing a display example of a seller terminal according to the second embodiment; A second sequence diagram explaining the operation of the transaction management system of the second embodiment. FIG. 13 is a second diagram showing an example of a display of the seller terminal according to the second embodiment. FIG. 13 is a third diagram showing an example of a display of the seller terminal according to the second embodiment. A diagram explaining the functional configuration of each device of the transaction management system of the third embodiment. A sequence diagram explaining the operation of the transaction management system of the third embodiment. A diagram explaining the functional configuration of each device of the transaction management system of the fourth embodiment. A sequence diagram explaining the operation of the transaction management system of the fourth embodiment.

(First embodiment)
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will now be described with reference to the accompanying drawings. Fig. 1 is a diagram showing an example of a system configuration of a transaction management system.

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

The transaction management system 100 of this embodiment is used by businesses and individuals who conduct sales transactions, and the transaction management device 200 mainly manages invoices issued at the time of sales transactions. Invoice management in this embodiment includes, for example, checking whether payment has been received from the billing destination (buyer) by the payment due date stated on the invoice, urging the billing destination (buyer) to make payment if payment has not been confirmed by the payment due date, and clearing accounts receivable by matching the amount received with the amount invoiced. Invoice management may also include managing the history of invoices sent to billing destinations.

In the following explanation, an invoice issued during a sales transaction will be used as an example of a document, but the document may be something other than an invoice. Specifically, for example, the document may be a purchase order, a delivery note, or an estimate.

The terminal device 400 in this embodiment is a terminal device that is mainly used by a seller in a buying and selling transaction. In the following description, the terminal device 400 may be referred to as a seller terminal 400. The terminal device 400 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 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 entity or an individual who acts as a seller or a buyer.
The transaction management system 100 of this embodiment manages invoice image data of an invoice issued by a seller in an external system 500 other than the transaction management system 100 in association with invoice information contained in the invoice.

The transaction management system 100 of this embodiment also transmits invoice image data of an invoice issued by the external system 500 to an e-mail service 700, a printing service 800, etc. The e-mail service 700 may be a server that provides a service of transmitting invoice image data of an invoice issued by a seller using the external system 500 to a buyer by e-mail. The printing service 800 may be a server that provides a service of outputting invoice image data of an invoice issued by a seller using the external system 500 as a printed matter.

The transaction management system 100 of this embodiment also accepts a deposit completion notification, etc., from the accounting system 600. The deposit completion notification may be output to the transaction management device 200, for example, after the accounting system 600 accepts a deposit instruction from the terminal device 300 and performs the deposit process.

The terminal device 300 is a terminal device that is primarily used by the buyer in a buying and selling transaction. Furthermore, a deposit instruction from the terminal device 300 is a deposit instruction in accordance with an invoice issued by the seller using the external system 500.

The transaction management device 200 of this embodiment has a tenant management database 210, an invoice image database 220, an invoice management database 230, and a transaction management section 260.

The tenant management database 210 stores information about tenants. In other words, the tenant management database 210 stores information about the seller. The invoice image database 220 stores form image data. The invoice management database 230 stores invoice management information for managing invoice information. At this time, the invoice management information associates invoice information with invoice image data.

When invoice image data and invoice information for an invoice issued using the external system 500 are uploaded from the seller terminal 400, the transaction management unit 260 stores the invoice image data and invoice information in association with each other. Therefore, in this embodiment, invoices issued by the external system 500 can be managed.

In the example of FIG. 1, the tenant management database 210, the invoice image database 220, and the invoice management database 230 are provided in the transaction management device 200, but this is not limited to the above. Each of these databases may be provided in part or in whole in another device. Furthermore, the transaction management device 200 may be realized by multiple information processing devices.

Next, the hardware configuration of an information processing device that realizes the transaction management device 200 will be described with reference to FIG. 2. FIG. 2 is a diagram showing an example of the hardware configuration of the transaction management device.

The transaction management device 200 is constructed by a computer and includes a CPU 201, a ROM 202, a RAM 203, a HD 204, a HDD (Hard Disk Drive) controller 205, a display 206, an external device connection I/F (Interface) 208, a network I/F 209, a bus line 219, a keyboard 211, a pointing device 212, a DVD-RW (Digital Versatile Disk Rewritable) drive 214, and a media I/F 216.

Of these, the CPU 201 controls the operation of the entire transaction management device 200. The ROM 202 stores programs used to drive the CPU 201, such as 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 or writing of various data from the HD 204 according to the control of the CPU 201. The display 206 displays various information such as a cursor, menu, window, character, or image.

The external device connection I/F 208 is an interface for connecting various external devices. In this case, the external devices are, for example, a USB (Universal Serial Bus) memory or a printer. The network I/F 209 is an interface for data communication using a communication network. The bus line 219 is an address bus, a data bus, etc. for electrically connecting each component such as the CPU 201.

The keyboard 211 is a type of input means equipped with 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 the cursor, etc. The DVD-RW drive 214 controls the reading and writing of various data from the 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 the reading and writing (storing) of data from the recording medium 215, such as a flash memory.

Figure 3 is a diagram showing an example of the hardware configuration of a terminal device. In Figure 3, the hardware configuration of the terminal device 400 is explained.

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/orientation sensor 407, a media I/F 409, and a GPS receiver 411.

Of these, CPU 401 is an arithmetic processing device that controls the operation of the entire terminal device 400. ROM 402 stores the CPU 401 and programs used to drive CPU 401, such as IPL. RAM 403 is used as a work area for CPU 401. EEPROM 404 reads or writes various data, such as programs for the terminal device, under the control of CPU 401. ROM 402, RAM 403, and EEPROM 404 are examples of storage devices for terminal device 400. Bus line 422 is an address bus, data bus, etc., for electrically connecting each component such as CPU 401.

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) under the control of the CPU 401 to obtain image data. Note that instead of a CMOS sensor, an imaging means such as a CCD (Charge Coupled Device) sensor may also be used.

The imaging element I/F 406 is a circuit that controls the driving of the CMOS sensor 405. The acceleration/direction 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 GPS receiver 411 receives GPS signals from GPS satellites.

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.

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 drive 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 electrical signals into physical vibrations to produce sounds such as music and voice. The audio input/output I/F 417 is a circuit that processes the input and output of audio signals between the microphone 415 and the speaker 416 under the control of the CPU 401.

The display 418 is a type of display means such as liquid crystal or organic EL (Electro Luminescence) 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.

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

Next, we will explain each database that the transaction management device 200 has, with reference to Figures 4 and 5.

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

In this embodiment, information including values of items such as name, address, telephone number, email address, and person in charge in the tenant management database 210 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" respectively indicate the address, telephone number, email address, and name of the person in charge of the transaction of the billing party.

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.

Figure 5 is a first diagram showing an example of an invoice management database in the first embodiment. The invoice management database 230 in this embodiment may be provided for each tenant.

In this embodiment, the invoice management database 230 includes the following information items: invoice information number, customer ID, customer name, invoice amount, payment due date, creation date, delivery date, payment status, payment date, deposit account, settlement status, import, external invoice ID, file path, etc.

In the invoice management database 230, the items "invoice number" and tenant name correspond to other items. In the following explanation, information including the value of the item "invoice number", the tenant name, and the values of other items is referred to as invoice management information.

In addition, the invoice management database 230 stores both invoice management information for managing invoice information for invoices issued by the external system 500 and invoice management information for managing invoice information for invoices issued by the transaction management system 100.

In this embodiment, invoice information includes, for example, items such as "invoice number," "client ID," "client name," "billing amount," "payment due date," and "creation date." In addition, items such as "sent date," "deposit status," "deposit date," "deposit account," "clearance status," "import," "external invoice ID," and "file path" are information items for managing invoice information. Therefore, in this embodiment, invoice management information includes invoice information.

The value of the item "invoice number" is identification information for identifying an invoice. In other words, the value of the item "invoice number" is identification information for identifying invoice management information.
The value of the item "Customer ID" is identification information for identifying a customer. Specifically, the value of the item "Customer ID" is the tenant ID of the tenant (buyer) to which the invoice identified by the invoice number is to be sent (transmitted).

The value of the field "Customer Name" indicates the name of the buyer. The value of the field "Invoice Amount" indicates the invoice amount, and the value of the field "Payment Due Date" indicates the date by which the invoice amount is due. The value of the field "Created Date" indicates the date the invoice was created, and the value of the field "Sent Date" indicates the date the seller sent the invoice to the buyer.

The value of the item "Payment Status" indicates whether the invoice amount has been paid or not. For example, if the value of the item "Payment Status" is "Not Paid", it indicates that the payment corresponding to the invoice amount has not been made, and if the value of the item "Payment Status" is "Payed", it indicates that the invoice amount has been paid.

The value of the "Deposit Date" field indicates the date on which the deposit was made, and the value of the "Deposit Account" field indicates the account to which the deposit was made.

The value of the "Settlement Status" item indicates whether the invoice amount for which payment has been confirmed has been erased. Specifically, when the value of the "Settlement Status" item is "Unsettlement", this indicates that the payment has been confirmed, but the invoice amount has not been erased. When the value of the "Settlement Status" item is "Settlement Completed", this indicates that the amount for which payment has been confirmed has been erased from the invoice amount.

The value of the item "Import" indicates whether the invoice information identified by the invoice number is invoice information for an invoice created using the external system 500. Specifically, if the value of the item "Import" is "No", this invoice information is invoice information created in the transaction management system 100. Also, if the value of the item "Import" is "Yes", this invoice information is invoice information created in the external system 500.

The value of the item "External Invoice ID" is invoice identification information for identifying an invoice issued by the external system 500. The value of the item "File Path" indicates the storage location of the invoice image data of the invoice identified by the invoice number.

In the example of Figure 5, the value of the item "Import" for invoice numbers 1056 and 1057 is Yes, and the invoice management information identified by invoice numbers 1056 and 1057 includes invoice information created in the external system 500.

In addition, in the invoice management database 230, the invoice information with invoice numbers 1056 and 1057 is invoice information contained in the invoice identified by the invoice ID "Invoice01234" in the external system 500.

Furthermore, the invoice image data for invoice numbers 1056 and 1057 are stored in the storage locations specified by the file paths. In this manner, in this embodiment, invoice information and invoice image data are associated with each other and stored (registered) in the invoice management database 230.

Next, the functional configuration of each device of the transaction management system 100 will be described with reference to FIG. 6. FIG. 6 is a diagram illustrating the functional configuration of each device of the transaction management system of the first embodiment.

First, the functions of the transaction management device 200 will be described. 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, a registration unit 265, an information acquisition unit 266, and an information management unit 267.

The transmitting unit 261 and the receiving unit 262 transmit and receive information between the transaction management device 200 and other devices.

Specifically, the sending unit 261 sends the invoice image data stored in the invoice image database 220 to the destination email service 700 or print service 800. The receiving unit 262 receives the invoice image data and invoice information created in the external system 500 from the seller terminal 400.

The input reception unit 263 receives various inputs to the transaction management device 200. Specifically, the input reception unit 263 receives various information inputs and requests from the seller terminal 400, the accounting system 600, the buyer terminal 300, etc. Examples of various information include form image data (invoice image data), form information (invoice information), payment completion notifications, etc.

The display control unit 264 controls the display on the seller terminal 400. The registration unit 265 registers the invoice image data and invoice information of the invoice created in the external system 500 in the transaction management system 100. Specifically, when the invoice image data and invoice information are imported from the seller terminal 400, the registration unit 265 associates the invoice image data with the invoice information and stores them in the invoice management database 230.

The information acquisition unit 266 acquires various types of information. Specifically, the information acquisition unit 266 acquires information transmitted from the seller terminal 400. The information acquisition unit 266 also acquires various types of information stored in the invoice management database 230, etc.

The information management unit 267 manages invoice image data and invoice management information. Specifically, the information management unit 267 updates the invoice management database 230, etc.

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

The input reception unit 440 receives various information input to the seller terminal 400. The communication unit 430 displays the information on the display of the seller terminal 400.

Next, the operation of the transaction management system 100 of this embodiment will be described with reference to FIG. 7. FIG. 7 is a first sequence diagram explaining the operation of the transaction management system of the first embodiment. FIG. 7 shows the operation of registering invoice image data and invoice information of an invoice created by the external system 500 in the transaction management device 200.

In the transaction management system 100 of this embodiment, the seller terminal 400 receives an instruction from a tenant such as a seller to import invoice image data and invoice information of an invoice created in the external system 500 (step S701).

At this time, the seller terminal 400 holds invoice image data and invoice information for the invoice that was previously created in the external system 500.

Next, when the seller terminal 400 receives the import instruction, it sends a request to the transaction management device 200 to display a screen for performing the import operation (step S702).

The transaction management device 200 accepts this display request and sends an instruction to the seller terminal 400 to display the import operation screen (step S703).

The seller terminal 400 accepts this display instruction and displays the import operation screen on the display unit 450 (step S704).

Next, the seller terminal 400 accepts the selection of invoice image data and invoice information to be imported on the import operation screen (step S705).

Note that the invoice image data of an invoice created by the external system 500 may be, for example, image data in PDF format. In the following description, the invoice image data created by the external system 500 may be referred to as a PDF file.

In addition, the invoice information of an invoice created in the external system 500 may be, for example, data in CSV format. In the following description, the invoice information of an invoice created in the external system 500 may be expressed as a CSV file. The CSV file may include invoice information for multiple invoices.

When the PDF file and the CSV file are selected, the seller terminal 400 transmits an import request for the two selected files to the transaction management device 200 (step S706). At this time, the selected PDF file and the CSV file are also transmitted to the transaction management device 200.

When the transaction management device 200 receives input of a PDF file and a CSV file via the input receiving unit 263, the information acquisition unit 266 acquires the two files, and the registration unit 265 stores the PDF file in the invoice image database 220 (step S707).

In other words, the transaction management device 200 accepts import operations from the seller terminal 400 via the input acceptance unit 263.

Next, the transaction management device 200 associates the CSV file with the PDF file and registers them in the invoice management database 230 via the registration unit 265 (step S708).

In other words, the transaction management device 200, through the registration unit 265, associates the invoice image data of the invoice created in the external system 500 with the invoice information and stores it in the invoice management database 230 of the transaction management system 100.

The operation shown in FIG. 7 is further explained below. FIG. 8 shows an example of a CSV file.

It can be seen that the CSV file 81 shown in Figure 8 contains invoice information for an invoice whose invoice ID assigned in the external system 500 is "Invoice01234" and invoice information for an invoice whose invoice ID is "Invoice01235".

Next, a display example of the seller terminal 400 will be described with reference to Figs. 9 to 12. Fig. 9 is a first diagram showing a display example of the seller terminal of the first embodiment. Screen 91 shown in Fig. 9 shows an example of an import operation screen displayed on the seller terminal 400 in step S704 of Fig. 7.

Screen 91 includes a selection field 92. In this embodiment, when selection field 92 is selected, a list of CSV files held by seller terminal 400 may be displayed. Seller terminal 400 sets the CSV file selected in the list as the CSV file to be imported. When a CSV file is selected, screen 91 transitions to screen 91A shown in FIG. 10. Here, it is assumed that CSV file 81 has been selected.

Figure 10 is a second diagram showing an example of the display of the seller terminal of the first embodiment. The screen 91A shown in Figure 10 includes a selection field 92, a display area 93, and an operation button 94.

Display area 93 displays invoice information 95, 96 contained in CSV file 81 selected in selection field 92. In addition, in display area 93, for invoice information 95, "invoice1.pdf" is selected as the corresponding PDF file, and for invoice information 96, a PDF file is about to be selected.

In the display area 93, an operation button 95a is associated with the invoice information 95 and displayed. The operation button 95a is an operation button for displaying a preview image of a PDF file associated with the invoice information 95. When the seller terminal 400 receives an operation on the operation button 95a, the seller terminal 400 may transition the screen 91A to a display screen for a preview image of Invoice1.pdf.

An operation button 96a is associated with and displayed on the invoice information 96. The operation button 96a is an operation button for displaying a list of PDF files. When the operation button 96a is operated in the display area 93, a list of PDF files may be displayed on the screen 91A.

Operation button 94 is an operation button for sending an import request for the selected CSV file and PDF file to the transaction management device 200. When operation button 94 is operated, the seller terminal 400 sends the selected CSV file and PDF file to the transaction management device 200.

Figure 11 is a third diagram showing an example of the display of the seller terminal of the first embodiment. Screen 111 shown in Figure 11 shows another example of the import operation screen displayed on the seller terminal 400 in step S704 of Figure 7.

Screen 111 includes selection fields 92 and 112. In this embodiment, when selection field 112 is selected, a list of PDF files held by seller terminal 400 may be displayed. In other words, on screen 111, each of a CSV file and a PDF file is selected.

When a CSV file and a PDF file are selected, screen 111 transitions to screen 111A.

Figure 12 is a fourth diagram showing an example of the display of the seller terminal of the first embodiment. The screen 111A shown in Figure 12 includes selection fields 92, 112, a display area 113, and an operation button 94.

In the display area 113, invoice information 95 and 96 are displayed. In addition, in the display area 113, each of the invoice information 95 and 96 is automatically associated with the PDF file selected in the selection field 112, and the PDF file name is displayed.

In FIG. 12, when a PDF file is selected, the seller terminal 400 may perform character recognition processing on the selected PDF file and extract information such as the invoice ID and customer ID contained in the invoice image. The seller terminal 400 may then identify the invoice information contained in the CSV file from the extracted information and display the PDF file and the CSV file in association with each other.

This way, when importing a large amount of invoice information, you can avoid the trouble of having to select the PDF files that correspond to each invoice information one by one.

Operation buttons 95a and 96b displayed in display area 113 are operation buttons for displaying a preview image of a PDF file associated with the invoice information.

Next, we will explain how the transaction management device 200 of this embodiment manages deposits, etc.

Figure 13 is a second sequence diagram explaining the operation of the transaction management system of the first embodiment. Figure 13 shows the operation of the transaction management system 100 when displaying a list of invoices issued by the seller that have not yet been sent to the buyer.

In the transaction management system 100 of this embodiment, when the seller terminal 400 receives an instruction to display a list screen of unsent invoice information (step S1301), it transmits a display request for the list screen to the transaction management device 200 (step S1302). Note that this display request may include a tenant ID for identifying the seller, etc.

When the transaction management device 200 receives the display request, the display control unit 264 generates screen data for displaying a list screen of unsent invoices (step S1303), and transmits an instruction to display the list screen to the seller terminal 400 (step S1304). Details of the processing in step S1303 will be described later.

When the seller terminal 400 receives an instruction to display the list screen, the display unit 450 displays a list screen of unsent invoices on the display (step S1305).

In this embodiment, invoice information created in the external system 500 and registered in the transaction management system 100 is prohibited from being edited. Also, in this embodiment, invoice information created in the transaction management system 100 is permitted to be edited.

The processing from step S1306 onwards shows the operation when editing invoice information for which editing is permitted.

When the seller terminal 400 receives an instruction to edit invoice information that is permitted to be edited on the list screen of unsent invoices (step S1306), it sends a request to display the edit screen to the transaction management device 200 (step S1307).

When the transaction management device 200 receives this display request, the display control unit 264 sends an instruction to display the editing screen to the seller terminal 400 (step S1308).

The seller terminal 400 accepts the display instruction and causes the display unit 450 to display the editing screen on the display (step S1309).

When the seller terminal 400 receives an editing operation and an operation to save the edits (step S1310), it sends a request to save the edited content to the transaction management device 200 (step S1311).

When the transaction management device 200 receives a request to save the edited content, the information management unit 267 registers the edited content in the invoice management database 230 (step S1312).

Next, the process of generating a list screen of unsent invoices will be described with reference to FIG. 14. FIG. 14 is a first flowchart illustrating the process of the transaction management device of the first embodiment. FIG. 14 shows the details of the process of step S1303 in FIG. 13.

The transaction management device 200 uses the information acquisition unit 266 to refer to the invoice management database 230 to acquire invoice information for which a value has not been entered for the item "sending date" (step S1401).

Then, the transaction management device 200 executes processing up to step S1405 for the acquired invoice information (step S1402).

The transaction management device 200, through the information management unit 267, refers to the invoice management information including the acquired invoice information, and determines whether the acquired invoice information has been imported from an external source (step S1403). Specifically, the information management unit 267 refers to the invoice management information including the acquired invoice information, and determines whether the value of the item "Import" is "Yes."

If in step S1403 the invoice information was imported from an external source, the transaction management device 200 proceeds to step S1405, which will be described later.

In step S1403, if the invoice information has not been imported from outside, that is, if the acquired invoice information has been created in the transaction management system 100, the information acquisition unit 266 determines that this invoice information is invoice information that is permitted to be edited (step S1404). In other words, the information acquisition unit 266 displays an operation button for this invoice information to transition to an editing screen for the invoice information.

When the transaction management device 200 has performed the processes of steps S1403 and S1404 for all the invoice information acquired in step S1401 (step S1405), it proceeds to step S1406.

The transaction management device 200 generates screen data for displaying a list screen of unsent invoices including the result of the determination as to whether editing of the invoice information is permitted (step S1406), and ends the process.

The list screen of unsent invoices will be described below with reference to Figure 15. Figure 15 is a fifth diagram showing an example of the display on the seller terminal in the first embodiment.

Screen 151 shown in FIG. 15 is an example of a list screen of unsent invoices displayed on the seller terminal 400 in step S1305 of FIG. 13.

The screen 151 has a display area 152. In the display area 152, a list 153 of invoice information acquired in step S1401 of FIG. 14 is displayed.

In addition, the display area 152 displays operation buttons 154 associated with each invoice information, and operation buttons 155 associated with a portion of the invoice information displayed in the display area 152.

Operation button 154 is an operation button for instructing the seller terminal 400 to send an invoice including the corresponding invoice information to the buyer. When the seller terminal 400 receives this instruction to send, it may send an invoice sending request to the transaction management device 200. Also, in this embodiment, when operation button 154 is operated on screen 151, screen 151 transitions to a sending settings screen, which will be described later.

In this case, the transaction management device 200 may send the invoice according to the invoice delivery method. Specifically, for example, if the invoice delivery method is email, the transaction management device 200 may send the invoice information instructed to be sent to the email service 700.

Also, for example, if the invoice is to be sent by mail, the invoice information instructed to be sent may be sent to the printing service 800.

The operation button 155 is only displayed for invoice information that is permitted to be edited. In the example of FIG. 15, the operation button 155 is displayed for invoice information whose client name is B4 Co., Ltd., but is not displayed for invoice information whose client name is B1 Co., Ltd. and invoice information whose client name is B2 Co., Ltd.

Therefore, it can be seen that, of the invoice information displayed on screen 151, only the invoice information with the client name B4 Co., Ltd. was created in the transaction management system 100, and the other invoice information was created in the external system 500.

In this embodiment, when operation button 155 is operated on screen 151, screen 151 transitions to an invoice information editing screen.

Figure 16 is a sixth diagram showing an example of the display of the seller terminal of the first embodiment. Screen 161 shown in Figure 16 is an example of an invoice information editing screen displayed on the seller terminal 400 in step S1309 of Figure 13.

Screen 161 includes a display field 162 and operation buttons 163. Display field 162 displays the item names and item values of information included in the invoice information for which Honshu is permitted, in correspondence with each other. Display field 162 also accepts re-input of each item name and the corresponding item value.

Operation button 163 is an operation button for storing the item values displayed in display field 162 in the invoice management database 230.

When the operation button 163 on the screen 161 is operated, the transaction management device 200 stores the item value entered in the display field 162 in the invoice management database 230.

Next, referring to FIG. 17, we will explain how the transaction management system 100 sends an invoice and manages deposits after sending the invoice. FIG. 17 is a third sequence diagram that explains the operation of the transaction management system of the first embodiment.

In Figure 17 below, steps S1701 to S1703 show the process of sending an unsent invoice to the buyer, and steps S1704 to S1711 show the process of managing the payment status after the invoice has been sent.

In this embodiment, the process of sending an invoice to a buyer and the process of managing the payment status do not have to be performed consecutively, but may be performed at separate, independent times.

The seller terminal 400 accepts an instruction to send an invoice (step S1701). Specifically, the seller terminal 400 accepts an operation to select one of the operation buttons 154 on the screen 151 of FIG. 15.

Next, the seller terminal 400 transmits an invoice delivery request to the transaction management device 200 (step S1702). The invoice delivery request includes the invoice number, delivery setting information, etc. Delivery setting information is information that indicates the invoice delivery method, etc.

When the transaction management device 200 receives the sending request, the information management unit 267 executes sending of the invoice (step S1703). The details of the processing of step S1703 will be described later.

When the seller terminal 400 receives an instruction to display the invoice management screen for a specified period (step S1704), the seller terminal 400 transmits a display request for the invoice management screen to the transaction management device 200 (step S1705). Note that this display request may include information specifying the period.

The transaction management device 200 receives a request to display the invoice management screen, and the display control unit 264 generates screen data for displaying the invoice management screen (step S1706). Details of step S1706 will be described later.

Next, the transaction management device 200 sends an instruction to display the invoice management screen to the seller terminal 400 (step S1707).

The seller terminal 400 accepts this display instruction and causes the display unit 450 to display the invoice management screen on the display (step S1708).

Next, when the seller terminal 400 receives an operation to instruct invoice management, such as a payment reminder (step S1709), it sends an invoice management request to the transaction management device 200 (step S1710).

The transaction management device 200 receives the invoice management request and manages the invoice information using the information management unit 267 (step S1711). The details of the processing in step S1711 will be described later.

Next, referring to FIG. 18, a description will be given of the sending settings screen for making sending settings when sending an invoice. FIG. 18 is a seventh diagram showing an example of a display on a seller terminal in the first embodiment. Screen 181 shown in FIG. 18 is an example of a sending settings screen for making settings related to sending an invoice. Screen 181 is displayed on seller terminal 400, for example, when a tenant instructs sending of an invoice in step S1701 of FIG. 17.

Screen 181 includes display fields 182, 183, selection fields 184, 185, input field 186, and operation button 187.

Display field 182 displays an invoice number for identifying the invoice to be sent. Display field 182 may also display the amount due on the invoice identified by the invoice number.

Display field 183 displays an icon image for displaying a list of unsent invoices. In this embodiment, when the icon image in display field 183 is selected, window 181A may be displayed on screen 181. Window 181A displays a list of unsent invoices. In this embodiment, the invoice number of an invoice selected from the list displayed in window 181A may be displayed in display field 182.

Selection fields 184 and 185 are selection fields for selecting the method of sending the invoice. Specifically, selection field 184 is a selection field for selecting the method of sending the invoice by email, and selection field 185 is a selection field for selecting the method of sending the invoice by mail.

In the example of Figure 18, invoice number "1056" is displayed in display field 182, and selection field 184 is selected, so it can be seen that the invoice information identified by invoice number "1056" and invoice image data are set to be sent by email.

Input field 186 is where information about the destination of the invoice is entered. On screen 181, the name of the business partner to which the invoice with invoice number "1056" is to be sent is entered.

Operation button 187 is an operation button for instructing the execution of sending an invoice. When operation button 187 is operated, the seller terminal 400 sends a request to send an invoice to the transaction management device 200.

Next, the process of sending an invoice by the transaction management device 200 will be described with reference to FIG. 19. FIG. 19 is a second flowchart illustrating the process of the transaction management device of the first embodiment. The process of FIG. 19 shows details of the process of step S1703 in FIG. 17.

The transaction management device 200 acquires information indicating the delivery method from the delivery setting information via the information acquisition unit 266 (step S1901).

If the delivery method is by e-mail, the transaction management device 200 causes the information management unit 267 to attach the invoice image data to an e-mail, send the e-mail to the delivery destination included in the delivery destination setting information (step S1902), and proceeds to step S1904, which will be described later.

If the delivery method is mailing, the transaction management device 200 sends the invoice image data and a print request to the print service 800 via the information management unit 267 (step S1903).

Next, the transaction management device 200 uses the information management unit 267 to update the sending date and payment status in the invoice management information in the invoice management database 230 (step S1904), and terminates the process.

Specifically, the information management unit 267 inputs a value for the item "Sent date" in the invoice management information, which includes the invoice number of the sent invoice, and sets the value of the item "Payment status" to "Unpaid." In this embodiment, when an invoice is sent and a value for the item "Sent date" is input, the value of the item "Payment status" becomes "Unpaid." In this embodiment, by doing this, it is possible to prevent situations from occurring in which the buyer is urged to make payment even though the invoice has not been sent.

Next, referring to FIG. 20, the display of the invoice management screen by the transaction management device 200 of this embodiment will be described. FIG. 20 is a third flowchart that explains the processing of the transaction management device of the first embodiment. The processing of FIG. 20 shows details of the processing of step S1708 of FIG. 17.

When the input receiving unit 263 receives a period specification, the transaction management device 200 of this embodiment uses the information acquisition unit 266 to acquire invoice information for the specified period from the invoice management database 230 (step S2001). Specifically, the information acquisition unit 266 acquires invoice information whose payment due date falls within the specified period. Note that in this embodiment, the date included in the specified period may be a date other than the payment due date.

Next, the transaction management device 200 performs the processing from step S2003 onwards for all the acquired invoice information (step S2002).

The transaction management device 200, through the information management unit 267, determines whether the invoice corresponding to the acquired invoice information has been sent (step S2003). Specifically, the information management unit 267 determines whether a value has been entered in the "sent date" field corresponding to the invoice information in the invoice management database 230.

If the payment has not been sent in step S2003, the transaction management device 200 proceeds to step S2007, which will be described later.

If it is determined in step S2003 that the invoice has already been sent, the transaction management device 200 displays this invoice information (step S2004).

Next, the transaction management device 200 determines whether the invoice information to be displayed was created by the external system 500 (step S2005). Specifically, the transaction management device 200 determines whether the value of the item "Import" corresponding to the invoice information to be displayed in the invoice management database 230 is "No."

In step S2005, if the invoice information was not created by the external system 500, i.e., the invoice information was created by the transaction management system 100, the transaction management device 200 proceeds to step S2007.

In step S2005, if the invoice information was created by the external system 500, the transaction management device 200 determines that this invoice information is the invoice information to which a mark should be added (step S2006).

The transaction management device 200 executes the processes from step S2003 to step S2006 for the invoice information acquired in step S2001 (step S2007).

After processing all the invoice information in step S2007, the transaction management device 200 causes the display control unit 264 to generate screen data for displaying an invoice management screen including the invoice information to be displayed (step S2008), and ends the processing.

The invoice management screen displayed on the seller terminal 400 will be described below with reference to FIG. 21. FIG. 21 is an eighth diagram showing an example of the display on the seller terminal in the first embodiment.

Screen 190 shown in FIG. 21 is an example of an invoice management screen displayed in step S1708 of FIG. 17. In FIG. 21, among the invoices issued by Company A1, invoice number 1056 and invoice number 1057 are in an unsent state (see FIG. 5).

Screen 190 includes display areas 191 and 192. Display area 191 displays, for example, the deposit status of a tenant named "A1 Co., Ltd."

Display area 192 displays a list of invoice information to be displayed. Specifically, display area 192 displays invoice information 192-1 for invoices issued to B2 Corporation, and invoice information 192-2 for invoices issued to B3.

In this case, invoice number 1056 and invoice number 1057 are not displayed because they have not been sent yet. Therefore, the invoice information for invoice number 1056 and invoice information for invoice number 1057 are not displayed in display area 192.

The display area 192 also includes operation buttons 192a and 192b that are displayed in association with the invoice information. The operation buttons 192a and 192b are operation buttons for requesting payment from the recipient of the corresponding invoice information.

The operation button 192a is associated with invoice information 192-1, and the operation button 192b is associated with invoice information 192-2.
In this embodiment, when operation button 192a is operated on screen 190 of seller terminal 400, a request for payment to the delivery destination of invoice information 192-1 is sent to transaction management device 200. In response to this request, transaction management device 200 may send a notice or the like to the buyer, who is the delivery destination of invoice information 192-1, to remind him or her to make payment.

Next, referring to Figures 22 and 23, we will explain the case where the invoice identified by invoice number 1056 has been determined to have been sent.

Figure 22 is a second diagram showing an example of an invoice management database in the first embodiment. In the invoice management database 230-1 shown in Figure 22, in the invoice management information where the value of the item "Invoice number" is "1056", a value has been entered for the item "Sent date", and the value of the item "Payment status" is "Unpaid". At this time, no value has been entered for the item "Settlement status" in the invoice management database 230-1.

Figure 23 is a ninth diagram showing an example of the display of the seller terminal of the first embodiment. Screen 190A shown in Figure 23 is an example of an invoice management screen when the state of the invoice management database 230 is as shown in Figure 22.

Here, the invoice information for invoice number "1056" is to be displayed. Also, in the invoice management database 230, the value of the "Import" item for the invoice management information corresponding to invoice number "1056" is "Yes."

Therefore, the invoice information with invoice number "1056" is subject to being marked to indicate that it was created in the external system 500.

Screen 190A includes display areas 191 and 192A. Display area 192A displays a list of invoice information for which invoices have already been sent. Specifically, display area 192A displays invoice information 192-1, 192-2, and 192-3, and operation buttons 192a, 192b, and 192c are displayed corresponding to each piece of invoice information. The value of the item "Payment Status" corresponding to the invoice information displayed here is all "Not entered."

Here, in comparison with display area 192 in FIG. 21, invoice information 192-3 has been added to display area 192A, and it can be seen that invoice information for invoice number "1056" has been sent.

In addition, since the invoice information for invoice number "1056" is invoice information imported from the external system 500, mark 194 is displayed.

In this embodiment, invoice information imported from the external system 500 and invoice information created in the transaction management system 100 are displayed in different display formats so that they can be visually distinguished.

Next, referring to Figures 24 and 25, we will explain the case where a deposit is made in accordance with the invoice identified by invoice number 1056.

Figure 24 is a third diagram showing an example of an invoice management database in the first embodiment. In the invoice management database 230-2 shown in Figure 24, in the invoice management information where the value of the item "Invoice number" is "1056", the value of the item "Payment status" is "Entered".

In addition, in the invoice management database 230-2, in the invoice management information where the value of the item "Invoice number" is "1056", a value is entered for the item "Clearance status", and the value is "Uncleared".

Figure 25 is a tenth diagram showing an example of the display of a seller terminal in the first embodiment. Screen 190B shown in Figure 25 is an example of an invoice management screen when the state of the invoice management database 230 is as shown in Figure 24.

Screen 190B includes display areas 191 and 192B. Display area 192B displays a list of invoice information to be displayed. In other words, display area 192B displays a list of invoice information for which invoice information has already been sent.

Specifically, display area 192B displays invoice information 192-1, 192-2, 192-3, and 192-4, and operation buttons 192a, 192b, 192c1, and 192d are displayed corresponding to each invoice information.

Compared to display area 192A in FIG. 23, invoice information 192-4 has been added to display area 192B, and it can be seen that invoice information with invoice number "1057" has been sent. In addition, since invoice information 192-4 with invoice number "1057" is invoice information imported from external system 500, mark 195 is displayed.

In addition, in display area 192B, the payment status corresponding to invoice information 192-3 is set to "paid," indicating that a payment has been made for the invoice corresponding to invoice information 193-3.

Furthermore, an operation button 192c1 is displayed in association with the invoice information 192-3. The operation button 192c1 is an operation button for canceling the invoice information 192-3.

In this way, on the invoice management screen of this embodiment, when a payment is made according to the invoice information, an operation button for clearing the invoice information is displayed. Therefore, according to this embodiment, the seller can visually grasp the status of the invoice information.

In this embodiment, in this way, invoice information imported from the external system 500 can be managed in the same way as invoice information created in the transaction management system 100. Specifically, in this embodiment, management of the sending of invoices created in the external system 500 and management of payments for these invoices can be performed in the same way as management of invoices created in the transaction management system 100.

Therefore, in this embodiment, even if the invoice is created by a sales system or the like that is used independently by the seller tenant, the invoice can be managed simply by importing the invoice image data and invoice information into the transaction management device 200.

In addition, even if a seller uses multiple sales management systems, for example, they can manage invoices collectively by simply importing invoice image data and invoice information into the transaction management device 200, thereby reducing the burden of management work.

Second Embodiment
The second embodiment will be described below with reference to the drawings. The second embodiment differs from the first embodiment in that the file name of the invoice image data stored in the transaction management device 200 is specified. Therefore, in the following description of the second embodiment, the differences from the first embodiment will be described, and components having the same functional configuration as the first embodiment will be given the same reference numerals as those used in the description of the first embodiment, and their description will be omitted.

Figure 26 is a diagram explaining the functional configuration of each device in the transaction management system of the second embodiment.

The transaction management system 100A of this embodiment includes a transaction management device 200A and a seller terminal 400. The transaction management device 200A has a tenant management database 210, an invoice image database 220, an invoice management database 230A, and a transaction management section 260A.

The transaction management unit 260A has a transmission unit 261, a reception unit 262, an input acceptance unit 263, a display control unit 264, a registration unit 265A, an information acquisition unit 266, an information management unit 267, and a file name determination unit 268.

In this embodiment, the file name determination unit 268 determines whether the file name of the invoice image data sent from the seller terminal 400 is in a predefined format.

The registration unit 265A registers the invoice image data and invoice information in the transaction management system 100 when the file name of the invoice image data of an invoice created in the external system 500 is in a file name format that is specified in advance.

The invoice management database 230A of this embodiment stores invoice management information including, for example, the file name of invoice image data in a predefined format and information identifying the external system 500.

Here, the file name of the invoice image data in this embodiment will be explained. In recent years, the Electronic Bookkeeping Act requires that tenants (corporations) store documents for a certain period of time. The Electronic Bookkeeping Act also requires that when storing documents, it is possible to check the relationship between related documents, it is possible to quickly output them to a screen or paper, and it is possible to search using search keys such as dates, business partners, and transaction details. In this embodiment, information including items that can be used as search keys for documents may be referred to as bibliographic information of the invoice.

In this embodiment, when the file name of the invoice image data is given a file name that includes part of the bibliographic information of the invoice, this invoice image data is registered in the invoice management database 230A as invoice image data given a file name in a predefined format.

In addition, at this time, in this embodiment, information identifying the external system 500 from which the invoice image data is output is associated with the file name of the invoice image data and registered in the invoice management database 230A.

In this embodiment, by managing invoice image data obtained from the external system 500 in this manner, it is possible to manage forms issued by the external system 500 while satisfying the requirements for form management.

Figure 27 is a diagram showing an example of an invoice management database of the second embodiment. The invoice management database 230A of this embodiment includes information items such as invoice information number, supplier ID, supplier name, invoice amount, payment due date, creation date, delivery date, payment status, payment date, deposit account, settlement status, import, external invoice ID, external system name, file path, etc. In other words, in addition to the information items held by the invoice management database 230 of the first embodiment, the invoice management database 230A includes the item "external system name."

The value of the item "External system name" is the name of the external system 500 that is the issuer of the invoice identified by the corresponding external invoice ID, and is information that identifies the external system 500. Note that in the example of FIG. 27, the information that identifies the external system 500 is the name of the external system 500, but is not limited to this. In this embodiment, identification information that identifies the external system 500, etc. may be used as the information that identifies the external system 500.

In addition, in the invoice management database 230A of this embodiment, the value of the item "file path" indicates the storage location of the invoice image data of the invoice identified by the invoice number and the file name of the invoice image data.

In the example of Figure 27, the invoice management information containing invoice numbers "1056" and "1057" has the value of the item "Import" as "Yes", and contains external invoice IDs "Invoice01234" and "Invoice01235", and external system name "External system 500".

Therefore, the file path included in the invoice management information, including the invoice numbers "1056" and "1057", stores the invoice image data output from the external system 500.

The file name of the invoice image data included in the file path corresponding to invoice number "1056" is "(X0001)(20201023)(880000).pdf". In other words, this file name includes the client ID, creation date, and invoice amount. In other words, this file name is in a predefined format.

The file name of the invoice image data included in the file path corresponding to invoice number "1057" is "(X0002)(20201023)(100000).pdf." In other words, this file name includes the client ID, creation date, and invoice amount. In other words, this file name is in a predefined format.

Thus, in this embodiment, invoice image data is stored in the invoice management database 230A if it is given a file name that includes bibliographic information about the invoice.

Below, the operation of the transaction management system 100A of this embodiment will be described with reference to FIG. 28. FIG. 28 is a first sequence diagram explaining the operation of the transaction management system of the second embodiment. The processing from step S2801 to step S2806 in FIG. 28 is similar to the processing from step S701 to step S706 in FIG. 7, and therefore the explanation will be omitted.

In step S2806, when the selected PDF file and CSV file are sent from the seller terminal 400, the transaction management device 200A accepts the input of the PDF file and CSV file via the input acceptance unit 263, and determines via the file name determination unit 268 whether the file name of the PDF file is in a predefined format (step S2807).

In step S2807, if the file name of the PDF file is in a predefined format, the transaction management device 200A proceeds to step S2808.

The processing of steps S2808 and S2809 in FIG. 28 is similar to the processing of steps S707 and S708 in FIG. 7, so the description is omitted.

In addition, in step S2807, if the file name of the PDF file is not in a predefined format, the transaction management device 200A may cause the seller terminal 400 to display a notification indicating that the PDF file cannot be registered. At that time, the transaction management device 200A may cause the seller terminal 400 to display a message requesting a change of the file name.

Next, a display example of the seller terminal 400 will be described with reference to FIG. 29. FIG. 29 is a first diagram showing a display example of the seller terminal of the second embodiment. Screen 290 shown in FIG. 29 is an example of an import operation screen displayed on the seller terminal 400 in step S2804 of FIG. 28. Note that screen 290 may be displayed on the seller terminal 400 as a screen for selecting a PDF file after a CSV file has been selected on screen 91 of FIG. 9, for example.

Screen 290 includes input field 291, selection fields 292 and 293, operation button 294, selection field 295, display fields 296 and 297, and selection field 298.

The input field 291 is an input field for specifying the destination of the PDF file. In the input field 291 of the screen 290, the transaction management device 200 is specified.

Selection field 292 is a selection field for selecting the format of the file name of the PDF file. In this embodiment, the predefined formats for the file name of the PDF file are a format in which each item included in the bibliographic information is marked with a delimiter, and a format in which each item included in the bibliographic information is marked with a bracketing character.

Enclosed text is selected on screen 290. Therefore, the file name determination unit 268 of the transaction management device 200 determines that the file name, in which each item included in the bibliographic information is enclosed in text, is a file name of a predefined format.

Selection field 293 is a selection field for selecting a PDF file to be sent to transaction management device 200. On screen 290, a PDF file with the file name (X0001)(20201023)(8800000).pdf is selected in selection field 293. In other words, on screen 290, a PDF file with a file name in which each item included in the bibliographic information is enclosed in text is selected.

Operation button 294 is an operation button for sending the PDF file selected in selection field 293 to the transaction management device 200.

Selection field 295 is a selection field for selecting whether or not to use the storage method stipulated in the Electronic Bookkeeping Act. Display field 296 displays the file from which bibliographic information is to be obtained (the file from which the bibliographic information is to be obtained). Display field 297 displays the specified item as the bibliographic information item to be included in the file name.

On screen 290, in selection field 295, the use of the storage method stipulated in the Electronic Bookkeeping Act is selected, and in display field 296, it is displayed that the file from which bibliographic information is to be obtained is a PDF file. In addition, in display field 297, it is displayed that the items of bibliographic information to be extracted are the business partner ID, creation date, and invoice amount.

Selection field 298 is a selection field for selecting the type of form. On screen 290, invoice is selected as the type of form.

Therefore, in this embodiment, among the PDF files output from the external system 500, a PDF file is saved with a file name in which the items extracted from the PDF file, "Customer ID," "Date of Creation," and "Amount Invoiced," are enclosed in brackets.

In this embodiment, by saving a PDF file with such a file name, for example, when a user of the seller terminal 400 searches for a PDF file, the user can perform a search using the business partner ID, creation date, and billing amount as search keys.

Below, the search for invoice image data in the transaction management system 100A of this embodiment will be described with reference to Figure 30. Figure 30 is a second sequence diagram that explains the operation of the transaction management system of the second embodiment.

In the transaction management system 100A of this embodiment, the seller terminal 400 accepts input of a search key and a search instruction from the user (step S3001). At this time, the seller terminal 400 displays a list screen of the PDF files sent to the transaction management device 200, and the input of the search key and the search instruction is accepted on this list screen.

When the seller terminal 400 receives the input of the search key and search instruction, it sends a search request using the search key to the transaction management device 200A (step S3002).

When the transaction management device 200A receives the search request, it executes a search of the invoice management database 230A (step S3003), and the transaction management device 200A transmits the search results to the seller terminal 400 (step S3004).

The seller terminal 400 accepts the search results and displays the search results on the display unit 450 (step S3005).

Below, the search for PDF files will be explained with reference to Figures 31 and 32. Figure 31 is a second diagram showing an example of the display of the seller terminal in the second embodiment.

The screen 310 shown in FIG. 31 is an example of a PDF file list screen displayed on the seller terminal 400 in step S3001 of FIG. 30.

Screen 310 includes display field 311, input field 312, and operation buttons 313 and 314. Display field 311 displays a list of PDF files sent from seller terminal 400 to transaction management device 200A. Input field 312 is an input field for inputting a search key. For example, a trading partner name, etc. may be input into input field 312.

Operation button 313 is an operation button for displaying an input field 315 for specifying a search range. Operation button 314 is an operation button for sending a search request to the transaction management device 200A.

In this embodiment, when operation button 313 is selected, input field 315 is displayed. Bibliographic information items included in the file name of the PDF file are displayed in input field 315. In the example of screen 310, input field 315 includes an input field for specifying the range of the creation date of the PDF file and an input field for specifying the range of the billing amount. Note that input field 315 may include items other than the creation date and the billing amount. Input field 315 may also include an input field for an external form ID, etc.

In addition, an operation button 316 is displayed for each PDF file displayed in the list in the display field 311. In this embodiment, when an operation button 316 is selected, details of the corresponding PDF file may be displayed on the seller terminal 400.

Figure 32 is a third diagram showing an example of a display on a seller terminal in the second embodiment. Screen 320 shown in Figure 32 is an example of a screen that is displayed when operation button 316 in Figure 31 is selected.

Screen 320 includes display fields 321 and 322. Display field 321 displays the bibliographic information of the PDF file corresponding to operation button 316, such as the creation date, business partner name, and billed amount. Display field 322 displays information identifying the external system 500 that is the output source of the PDF file for which the bibliographic information is displayed, and an external invoice ID that identifies this PDF file.

The display field 321 also includes an operation button 321a. In this embodiment, when the operation button 321a is operated, a PDF file in which the bibliographic information is displayed on the screen 320 is displayed on the seller terminal 400.

In this manner, in this embodiment, the seller terminal 400 allows the user to view a list of PDF files sent to the transaction management device 200A. Furthermore, in this embodiment, PDF files can be easily searched for, and the bibliographic information of the searched PDF file and the invoice image data indicated by the PDF file can be easily displayed on the seller terminal 400. Furthermore, in this embodiment, information identifying the external system 500 that is the issuer of the PDF file is displayed on the seller terminal 400, so that the user of the seller terminal 400 can easily understand the relationship between the transaction management device 200A and the issuer of the PDF file.

Third Embodiment
The third embodiment will be described below with reference to the drawings. The third embodiment differs from the second embodiment in that the transaction management device assigns a file name to the PDF file received from the external system 500. Therefore, in the following description of the third embodiment, the differences from the second embodiment will be described, and the same reference numerals as those used in the description of the second embodiment will be used to designate components having the same functional configuration as the second embodiment, and the description thereof will be omitted.

Figure 33 is a diagram explaining the functional configuration of each device in the transaction management system of the third embodiment.

The transaction management system 100B of this embodiment includes a transaction management device 200B and a seller terminal 400. The transaction management device 200B has a tenant management database 210, an invoice image database 220, an invoice management database 230A, and a transaction management section 260B.

The transaction management unit 260B has a transmission unit 261, a reception unit 262, an input acceptance unit 263, a display control unit 264, a registration unit 265, an information acquisition unit 266, an information management unit 267, and a file name creation unit 269.

The file name creation unit 269 of this embodiment causes the seller terminal 400 to display a setting screen that allows the user to set the items of bibliographic information to be included in the file name, creates a file name according to the set items, and makes the PDF file a PDF file of the created file.

Below, the operation of the transaction management system 100B of this embodiment will be described with reference to FIG. 34. FIG. 34 is a sequence diagram that explains the operation of the transaction management system of the third embodiment.

The processing from step S3401 to step S3404 in FIG. 34 is similar to the processing from step S701 to step S704 in FIG. 7, so the description will be omitted.

The seller terminal 400 accepts the selection of the bibliographic information items to be included in the file name on the import operation screen (step S3405). In other words, the seller terminal 400 accepts the setting of the bibliographic information items to be included in the file name on the import operation screen.

The seller terminal 400 then accepts the selection of a PDF file and a CSV file (step S3406).

Next, when the PDF file and the CSV file are selected, the seller terminal 400 transmits an import request for the two selected files to the transaction management device 200 (step S3407). At this time, the selected PDF file and the CSV file are also transmitted to the transaction management device 200. In addition, in this embodiment, the import request may include information indicating the items of the bibliographic information set in step S3405.

When the transaction management device 200B receives input of a PDF file and a CSV file via the input receiving unit 263, the file name creation unit 269 changes the file name of the PDF file (step S3408).

Specifically, the file name creation unit 269 extracts the values of the items set from the PDF file based on the items of the bibliographic information set in step S3405. Then, the file name creation unit 269 creates a file name including the values of the extracted items, and rewrites the file name of the PDF file to the created file name.

The processing in steps S3409 and S3410 in FIG. 34 is similar to the processing in steps S707 and S708 in FIG. 7, so the description is omitted.

In the example of FIG. 34, the items of bibliographic information to be included in the file name are set when an import instruction is received from the seller terminal 400, but this is not limited to the above. Setting the items of bibliographic information to be included in the file name may be performed at a timing separate from the import instruction.

Here, the import operation screen of this embodiment will be described. The import operation screen of this embodiment may be, for example, a screen in which the items of bibliographic information displayed in the display field 297 of the screen 290 shown in FIG. 29 can be selected.

By displaying such a screen on the seller terminal 400, in this embodiment, the user of the seller terminal 400 can set the file name format of the PDF file.

In addition, in this embodiment, the file name of the PDF file received from the seller terminal 400 is rewritten to a file name that includes pre-set bibliographic information items, eliminating the need to manipulate the file name of the PDF file in the external system 500, thereby improving versatility.

(Fourth embodiment)
The fourth embodiment will be described below with reference to the drawings. The fourth embodiment differs from the third embodiment in that a PDF file is imported from a specified external system 500 by rewriting the file name to a file name in a predetermined format. Therefore, in the following description of the fourth embodiment, differences from the third embodiment will be described, and components having the same functional configuration as the third embodiment will be given the same reference numerals as those used in the description of the third embodiment, and descriptions thereof will be omitted.

Figure 35 is a diagram explaining the functional configuration of each device in the transaction management system of the fourth embodiment.

The transaction management system 100C of this embodiment includes a transaction management device 200C and a seller terminal 400. The transaction management device 200C has a tenant management database 210, an invoice image database 220, an invoice management database 230A, and a transaction management section 260C.

The transaction management unit 260C has a transmission unit 261, a reception unit 262, an input acceptance unit 263, a display control unit 264, a registration unit 265, an information acquisition unit 266A, an information management unit 267, and a file name creation unit 269.

When an external system 500 is specified on the seller terminal 400, the information acquisition unit 266A in this embodiment acquires the PDF file and CSV file managed in the specified external system 500.

Below, the operation of the transaction management system 100C of this embodiment will be described with reference to FIG. 36. FIG. 36 is a sequence diagram that explains the operation of the transaction management system of the fourth embodiment.

The processing from step S3601 to step S3605 in FIG. 36 is similar to the processing from step S3401 to step S3405 in FIG. 34, so the description will be omitted.

The seller terminal 400 accepts the designation of the external system 500 on the import operation screen (step S3606).

Next, the seller terminal 400 accepts the selection of a PDF file and a CSV file (step S3606).

Next, when the PDF file and the CSV file are selected, the seller terminal 400 transmits an import request for the two selected files to the transaction management device 200C (step S3607). At this time, the import request may include information indicating the external system 500 specified in step S3606.

When the transaction management device 200C receives the import request, the information acquisition unit 266A sends an information acquisition request to the specified external system 500 (step S3608).

Then, the information acquisition unit 266A acquires the PDF file and the CSV file from the external system 500 (step S3609).

Next, the file name creation unit 269 of the transaction management device 200C changes the file name of the acquired PDF file (step S3610). The details of the processing of step S3610 are the same as those of step S3408 in FIG. 34.

The processing of steps S3611 and S3612 in FIG. 36 is similar to the processing of steps S707 and S708 in FIG. 7, so the description is omitted.

Here, the import operation screen of this embodiment will be described. The import operation screen of this embodiment may be, for example, a screen in which the items of bibliographic information displayed in the display field 297 of the screen 290 shown in FIG. 29 can be selected.

In addition, on the import operation screen of this embodiment, instead of selecting the PDF file to be sent to the transaction management device 200 in the selection field 293 on the screen 290, the external system 500 from which the PDF file and CSV file are to be obtained may be selected.

In this embodiment, by simply specifying the external system 500 from which the PDF file and CSV file are to be obtained and setting the file name format of the PDF file, the PDF file with the file name in the set format can be automatically imported. Therefore, in this embodiment, there is no need to individually select the files to be imported on the seller terminal 400, improving convenience.

Each function of the above-described embodiments can be realized by one or more processing circuits. In this specification, the term "processing circuit" includes a processor programmed to execute each function by software, such as a processor implemented by an electronic circuit, and devices such as an ASIC (Application Specific Integrated Circuit), DSP (digital signal processor), FPGA (field programmable gate array), and conventional circuit modules designed to execute each function described above.

Furthermore, the devices described in the embodiments represent only one of multiple computing environments for implementing the embodiments disclosed herein.

In one embodiment, transaction manager 200 includes multiple computing devices, such as a server cluster. The multiple computing devices are 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.

Further, transaction management apparatus 200 can be configured to share the disclosed processing steps in various combinations. For example, the processes performed by transaction management apparatus 200 can be performed by other server apparatuses. Similarly, the functions of transaction management apparatus 200 can be performed by other server apparatuses. Also, the server apparatus and the elements of the other server apparatuses can be combined into one server apparatus or separated into multiple apparatuses.

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

Here, machine learning refers to 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 identification from training data that is previously loaded, 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.

The present invention has been described above based on each embodiment, but the present invention is not limited to the requirements shown in the above embodiments. These points can be changed without departing from the spirit of the present invention, and can be appropriately determined according to the application form.

100, 100A, 100B, 100C Transaction management system 200, 200A, 200B, 200C Transaction management device 210 Tenant management database 220 Invoice image database 230, 230A Invoice management database 260, 260A, 260B, 260C Transaction management section 264 Display control section 265 Registration section 266 Information acquisition section 267 Information management section 268 File name determination section 269 File name creation section 400 Terminal device (seller terminal)
500 External System

JP 2002-183640 A

Claims (5)

A transaction management system for managing form image data of a form issued by an external system,
a first reception unit that receives an import instruction for importing form image data of a form issued by the external system and form information included in the form;
a transmission unit that transmits a display request for an import operation screen for performing an import operation when the first reception unit receives the import instruction;
a display control unit that displays the import operation screen based on the display request transmitted from the transmission unit;
a second reception unit that receives a selection of the form image data and the form information to be imported on the import operation screen displayed by the display control unit;
a registration unit that registers the form image data that has been selected and the form information in a corresponding relationship with each other in an invoice management database . The transaction management system according to claim 1 , wherein the import operation screen includes a selection field for selecting a file indicating the form information and the form image data. a determination unit that determines whether or not a file name in a predetermined format is assigned to the form image data;
The registration unit is
A transaction management system as described in claim 1 or 2, wherein when the document image data determined to have been assigned a file name of the predetermined format is imported, document management information that corresponds the document image data to the document information is registered . 4. The transaction management system according to claim 3 , wherein the file name includes a part of the bibliographic information of the form image data. A transaction management method by a transaction management system that manages form image data of a form issued by an external system, comprising:
A first reception unit receives an import instruction for importing form image data of a form issued by the external system and form information included in the form;
When the first reception unit receives the import instruction, a transmission unit transmits a display request for an import operation screen for performing an import operation ;
displaying the import operation screen on a display control unit based on the display request transmitted from the transmission unit;
When a selection of the form image data and the form information to be imported is accepted by a second accepting unit on the import operation screen displayed by the display control unit,
A transaction management method in which a registration unit associates the form image data that has been selected with the form information and registers them in an invoice management database.

Images