Information processing apparatus, information processing system, information processing method, information processing program

Abstract

To improve work convenience.SOLUTION: An information processing device is provided, comprising: a registration unit configured to register multiple business documents issued to a specific issue destination and an address for displaying a list of the multiple business documents in association with each other; and a display control unit configured to make a display unit display the list of the multiple business documents upon access to the address by operation of a user at the specific issue destination.SELECTED DRAWING: Figure 16

Description

Technical Field

[0001] The present invention relates to an information processing apparatus, an information processing system, an information processing method, and an information processing program.

Background Art

[0002] Conventionally, in commercial transactions, a technology is known in which a party providing goods or services (seller) creates image data (such as a PDF file) of an invoice, attaches it to an e-mail, and sends it to the e-mail address of a party purchasing the goods or services (buyer).

Summary of the Invention

Problems to be Solved by the Invention

[0003] A party purchasing goods or services often performs various processes on the received invoices collectively at a specific time such as the end of the month. However, in the conventional technology, since individual invoices are attached to and sent by e-mail, the work of collecting the invoices received during a certain period becomes complicated. Further, the same problems occur not only with invoices but also with documents such as estimates, orders, and delivery notes.

[0004] The present invention has been made in view of the above circumstances, and aims to improve the convenience of work.

Means for Solving the Problems

[0005] The disclosed technology includes a registration unit that registers by associating a plurality of documents issued to a specific recipient with an address for displaying a list of the plurality of documents, and a display control unit that causes a display unit to display a list of the plurality of documents based on access to the address by an operation of a user of the specific recipient. In a storage unit storing form information indicating a form, it has a specifying unit that specifies form information satisfying preset conditions. The registration unit determines whether the address corresponding to the form information specified by the specifying unit can be obtained when a form for a specific recipient is issued. If the address can be obtained, the obtained address is associated with the issued form and registered. It is an information processing apparatus. .

Effects of the Invention

[0006] The convenience of work can be improved.

Brief Description of the Drawings

[0007]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Mode for Carrying Out the Invention

[0008] (First Embodiment) Hereinafter, embodiments will be described with reference to the drawings. FIG. 1 is a diagram showing an example of the system configuration of a form management system.

[0009] The form management system 100 of the present embodiment is an example of an information processing system including a form management device 200, a first terminal device 300, and a second terminal device 400. In the form management system 100, the form management device 200, the first terminal device 300, and the second terminal device 400 are connected via a network or the like.

[0010] The form management system 100 of the present embodiment manages form information transferred between the first terminal device 300 and the second terminal device 400 used by business operators, individuals, etc. who conduct sales transactions, by the form management device 200.

[0011] The first terminal device 300 of the present embodiment is mainly a terminal device used by a buyer in a sales transaction. The second terminal device 400 of the present embodiment is mainly a terminal device used by a seller in a sales transaction. In the following description, the first terminal device 300 is expressed as a buyer terminal 300, and the second terminal device 400 is expressed as a seller terminal 400.

[0012] In the following description, a user who uses the services provided by the invoice management system 100 of the present embodiment may be referred to as a tenant. That is, in the present embodiment, a tenant is a business operator or an individual who becomes a seller or a buyer.

[0013] In the following description, the tenant who is the buyer is described as Company A, and the tenant who is the seller is described as Company B. Therefore, the buyer terminal 300 is managed by Company A, and the seller terminal 400 is managed by Company B.

[0014] The invoice management device 200 of the present embodiment includes a storage unit 210 and an invoice management unit 220. The storage unit 210 of the present embodiment includes a tenant database 230, a business partner management database 240, an invoice database 250, and a viewing management database 260.

[0015] The tenant database 230 stores information about tenants. The business partner management database 240 stores information about business partners of each tenant.

[0016] The invoice database 250 stores invoice information indicating invoices. In the following description, an invoice is described as an example of a form. Therefore, the invoice information of the present embodiment is an example of form information. The viewing management database 260 stores information for allowing each tenant to view a list of forms (invoices) issued from business partners. Note that the form may be a quotation, an order form, a delivery note, or the like.

[0017] The invoice management unit 220 associates a plurality of invoices (forms) issued to a specific issuer with an address for displaying a list of each invoice and stores them in the storage unit 210. In addition, the invoice management unit 220 displays a list of invoices issued within a certain period to the buyer in response to a request from the tenant who is the buyer.

[0018] Therefore, according to the present embodiment, it is not necessary for the buyer to summarize the invoices received during a certain period, and the convenience of the work can be improved.

[0019] In addition, in the example of FIG. 1, it is assumed that the tenant database 230, the business partner management database 240, the invoice database 250, and the viewing management database 260 are provided in the form management device 200, but it is not limited thereto. Each of these databases may be partially or entirely provided outside the form management device 200. Further, the form management unit 220 may be realized by a plurality of information processing devices.

[0020] Next, with reference to FIGS. 2 and 3, the hardware configuration of the information processing device that realizes the form management device 200 and the hardware configuration of the first terminal device 300 will be described.

[0021] FIG. 2 is a diagram showing an example of the hardware configuration of the form management device according to the first embodiment.

[0022] The form management device 200 is constructed by a computer, and as shown in FIG. 2, it includes a CPU 201, a ROM 202, a RAM 203, an HD 204, an 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 B1, a keyboard 211, a pointing device 212, a DVD-RW (Digital Versatile Disk Rewritable) drive 214, and a media I / F 216.

[0023] Among these, the CPU 201 controls the operations of the entire form management device 200. The ROM 202 stores programs used for driving 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 to and from the HD 204 according to the control of the CPU 201. The display 206 displays various information such as a cursor, menu, window, characters, or images. The external device connection I / F 208 is an interface for connecting various external devices. The external devices in this case are, for example, a USB (Universal Serial Bus) memory, a printer, etc. The network I / F 209 is an interface for performing 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.

[0024] Also, the keyboard 211 is a type of input means having a plurality of keys for inputting characters, numerical values, 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 the reading or writing of various data to and from the DVD-RW 213 as an example of a removable recording medium. Note that it is not limited to DVD-RW, and it may be DVD-R or the like. The media I / F 216 controls the reading or writing (storage) of data to and from the recording medium 215 such as a flash memory.

[0025] FIG. 3 is a diagram showing an example of the hardware configuration of the terminal device according to the first embodiment. Since the hardware configurations of the first terminal device 300 and the second terminal device 400 in this embodiment may be the same, in FIG. 3, as an example, the hardware configuration of the first terminal device 300 will be described.

[0026] The first terminal device 300 of this embodiment includes a CPU 301, a ROM 302, a RAM 303, an EEPROM 404, a CMOS sensor 405, an imaging device I / F 406, an acceleration / azimuth sensor 307, a media I / F 309, and a GPS receiver 311.

[0027] Among these, the CPU 301 is an arithmetic processing unit that controls the operation of the entire first terminal device 300. The ROM 302 stores programs used for driving the CPU 301 such as the CPU 301 and IPL. The RAM 303 is used as a work area for the CPU 301. The EEPROM 304 reads or writes (stores) various data such as smartphone programs according to the control of the CPU 301. The ROM 302, the RAM 303, and the EEPROM 304 are an example of the storage device of the first terminal device 300.

[0028] The CMOS (Complementary Metal Oxide Semiconductor) sensor 305 is a type of built-in imaging means that captures a subject (mainly a self-image) according to the control of the CPU 301 to obtain image data. Note that an imaging means such as a CCD (Charge Coupled Device) sensor may be used instead of the CMOS sensor.

[0029] The imaging device I / F 306 is a circuit that controls the driving of the CMOS sensor 305. The acceleration / azimuth sensor 307 is various sensors such as an electronic magnetic compass that detects geomagnetism, a gyrocompass, and an acceleration sensor. The media I / F 309 controls the reading or writing (storage) of data to / from a recording medium 308 such as a flash memory. The GPS receiver 311 receives GPS signals from GPS satellites.

[0030] In addition, the first terminal device 300 includes a long-distance communication circuit 312, an antenna 312a of the long-distance communication circuit 312, a CMOS sensor 313, an imaging device I / F 314, a microphone 315, a speaker 316, an audio input / output I / F 317, a display 318, an external device connection I / F (Interface) 319, a short-distance communication circuit 320, an antenna 320a of the short-distance communication circuit 320, and a touch panel 321.

[0031] Among these, the long-distance communication circuit 312 is a circuit that communicates with other devices via a communication network. The CMOS sensor 313 is a type of built-in imaging means that captures a subject according to the control of the CPU 301 to obtain image data. The imaging device I / F 314 is a circuit that controls the driving of the CMOS sensor 313. The microphone 315 is a built-in circuit that converts sound into an electrical signal. The speaker 316 is a built-in circuit that converts an electrical signal into physical vibration to generate sounds such as music and voices. The audio input / output I / F 317 is a circuit that processes the input / output of audio signals between the microphone 315 and the speaker 316 according to the control of the CPU 301.

[0032] The display 318 is a type of display means such as a liquid crystal or an organic EL (Electro Luminescence) that displays an image of a subject, various icons, etc. The external device connection I / F 319 is an interface for connecting various external devices. The short-distance communication circuit 430 is a communication circuit such as NFC (Near Field Communication) or Bluetooth (registered trademark). The touch panel 321 is a type of input means for operating the first terminal device 300 when a user presses the display 318. The display 318 is an example of the display unit of the first terminal device 400.

[0033] Note that the buyer terminal 300 and the seller terminal 400 of the present embodiment may have the same hardware configuration as the form management device 200.

[0034] Next, with reference to FIGS. 4 to 7, each database included in the storage unit 210 will be described.

[0035] FIG. 4 is a diagram showing an example of the tenant database of the first embodiment. The tenant database 230 of the present embodiment includes, as items of information, a tenant name, a user ID, a password, an email address, etc., and the item "tenant name" is associated with other items. In the tenant database 230, information including the value of the item "tenant name" and the values of other items may be expressed as tenant information.

[0036] The value of the item "tenant name" indicates the name of the tenant and is information for identifying the tenant. The values of the items "user ID" and "password" are used when the tenant logs in to the document management system 100. In the present embodiment, the value of the item "user ID" may be different depending on whether the tenant is a buyer or a seller.

[0037] The value of the item "email address" is information indicating the contact information of the tenant, and specifically, it is the destination for sending order document information, invoice information, etc.

[0038] FIG. 5 is a diagram showing an example of the trading partner management database of the first embodiment. The trading partner management database 240 of the present embodiment may be provided for each tenant. The trading partner management database 240 includes, as items of information, a company name, an email address, a person in charge, etc.

[0039] The value of the item "company name" indicates the tenant name (company name) of the trading partner, and the values of the items "email address" and "person in charge" indicate the email address and the name of the person in charge of the trading partner.

[0040] In the example of FIG. 5, it can be seen that the trading partners of the tenant "B Co., Ltd." are Company A, C Store, etc.

[0041] FIG. 6 is a diagram showing an example of the invoice database of the first embodiment. The invoice database 250 is provided for each tenant, and in FIG. 6, an example of the invoice database 250 of the tenant name "B Co., Ltd." is shown.

[0042] The invoice database 250 of the present embodiment includes, as information items, the billing destination, invoice number, status, total amount, consumption tax, issue date, payment due date, form image path, detailed information, etc., and the items "billing destination" and "invoice number" are associated with other items. In the following description, the information including the values of the items "billing destination" and "invoice number" in the invoice database 250 and other items is referred to as invoice information.

[0043] When the invoice information is created by the seller terminal 400 and transmitted to the form management device 200, the invoice information is stored in the invoice database 250.

[0044] The value of the item "billing destination" indicates the name of the tenant to which the invoice information is to be transmitted. The value of the item "invoice number" is identification information for specifying the invoice information.

[0045] The value of the item "status" indicates the status of the invoice information. When the invoice information is created and stored in the browsing management database 260, the value of the item "status" becomes "temporarily saved", and when the transmission of the invoice information from the form management device 200 to the buyer terminal 300 is completed, the value becomes "sent".

[0046] The value of the item "total amount" is the total amount in the invoice information, the value of the item "consumption tax" is the consumption tax amount for the total amount, and the value of the item "issue date" indicates the creation date (invoice issue date) of the invoice information. The value of the item "form image path" indicates the storage destination of the image data showing the created invoice information. In other words, the value of the item "form image path" indicates the storage destination of the form image data.

[0047] The value of the item "detailed information" indicates the details included in the invoice information. In the example of FIG. 6, items such as "detailed information 1" and "detailed information 2" are associated with the item "detailed information". The item "detailed information 1" includes a product code, product name, quantity, unit price, amount, etc.

[0048] FIG. 7 is a diagram showing an example of the browsing management database according to the first embodiment. The browsing management database 260 of the present embodiment includes a browsing management table 260-1 and an expiration date management table 260-2.

[0049] The browsing management table 260-1 includes, as information items, a list screen address, a status, a billing destination, a billing source, and an invoice number.

[0050] In the browsing management table 260-1, the value of the item "list screen address" is a URL (Uniform Resource Identifier) indicating the storage destination of the list screen data showing the list of invoices for each tenant. The list screen address may be generated, for example, by the document management unit 220. The value of the item "status" indicates whether the value of the item "list screen address" is valid or not. The value of the item "billing destination" indicates the tenant (buyer) to whom the invoice is sent, and the value of the item "billing source" indicates the tenant (seller) who issues the invoice. The value of the item "invoice number" indicates the invoice number of the invoice issued to the tenant who is the billing destination.

[0051] In the expiration date management table 260-2, information indicating the valid period of the list screen address is stored.

[0052] In the example of FIG. 7, the valid period of the list screen address is set to the end of the month two months after the list screen address is generated.

[0053] In the browsing management table 260-1 of the present embodiment, when the period elapsed since the generation of the URL, which is the value of the item "list screen address", is within the valid period, the value of the item "status" becomes "valid", and when the valid period is exceeded, the value of the item "status" becomes "invalid".

[0054] Next, with reference to FIG. 8, the functions of the document management unit 220 of the document management apparatus 200 of the present embodiment will be described. FIG. 8 is a diagram for explaining the functions of the document management unit.

[0055] The form management unit 220 of this embodiment includes an input reception unit 221, a form image generation unit 222, a specification unit 223, a registration unit 224, a screen generation unit 225, a display control unit 226, and an output unit 227.

[0056] The input reception unit 221 receives various inputs to the form management device 200. Specifically, the input reception unit 221 receives the input of invoice information. In addition, the input reception unit 221 receives various operations and requests from the buyer terminal 300 and the seller terminal 400.

[0057] Based on the invoice information received by the input reception unit 221, the form image generation unit 222 generates form image data indicating an invoice image.

[0058] The specification unit 223 specifies invoice information that satisfies a predetermined condition among the invoice information stored in the invoice database 250.

[0059] The predetermined condition is, for example, invoice information whose issue date is within a certain period. In other words, the predetermined condition is invoice information indicating an invoice issued within a certain period (one month, one week, etc.). Also, the predetermined condition is, for example, invoice information with the same billing destination.

[0060] The registration unit 224 stores the invoice information received by the input reception unit 221 in the invoice database 250. Also, the registration unit 224 associates the invoice number included in the input invoice information with the URL, which is the list screen address in the browsing management database 260, and stores it in the browsing management database 260. The details of the processing of the registration unit 224 will be described later.

[0061] The screen generation unit 225 generates screen data for various screens to be displayed on the buyer terminal 300 and the seller terminal 400.

[0062] The display control unit 226 causes the buyer terminal 300 and the seller terminal 400 to display the screen data generated by the screen generation unit 225.

[0063] The output unit 227 transmits (outputs) various types of information to the buyer terminal 300 and the seller terminal 400. Specifically, for example, the output unit 227 transmits to the buyer terminal 300 a list screen address for displaying a list of invoices.

[0064] Next, with reference to FIG. 9, the functions of the buyer terminal 300 and the seller terminal 400 will be described. FIG. 9 is a diagram for explaining the functions of the terminal devices according to the first embodiment. Each of the buyer terminal 300 and the seller terminal 400 in the present embodiment has an input reception unit 330, 430, a display unit 340, 440, and a communication unit 350, 450.

[0065] The input reception units 330, 430 receive operations and information input to the buyer terminal 300 and the seller terminal 400. The display units 340, 440 display various screens on the buyer terminal 300 and the seller terminal 400. The communication units 350, 450 communicate between the buyer terminal 300 and the seller terminal 400 and the form management device 200.

[0066] Next, with reference to FIG. 10, the operation of the form management system 100 according to the present embodiment will be described. FIG. 10 is a first sequence diagram for explaining the operation of the form management system according to the first embodiment. FIG. 10 shows the operation of the form management system 100 when the seller issues an invoice to the buyer and the buyer displays a list of the issued invoices. In FIG. 10, Corporation A is described as the buyer and Corporation B is described as the seller.

[0067] In the form management system 100, the seller terminal 400 receives the input of invoice information and an instruction to create an invoice (step S1001), and transmits the input invoice information to the form management device 200 (step S1002).

[0068] The form management device 200 stores, by the registration unit 224, the invoice information received from the seller terminal 400 in the invoice database 250 (step S1003).

[0069] Subsequently, the form management device 200 generates screen data for displaying the invoice information sending screen by the screen generation unit 225, and the display control unit 226 sends a display instruction for the invoice information sending screen to the seller terminal 400 (step S1004).

[0070] Upon receiving the display instruction, the seller terminal 400 displays the invoice sending screen on the display unit 440 (step S1005). Next, the seller terminal 400 accepts a registration operation for the list of invoices (step S1006).

[0071] Subsequently, when the seller terminal 400 accepts the designation of the invoice delivery destination (step S1007), it sends an invoice delivery request to the form management device 200 (step S1008).

[0072] The form management device 200 stores the invoice in association with the list screen address of the business partner management database 240 by the registration unit 224 (step S1009). Details of the processing in step S1009 will be described later.

[0073] Subsequently, the form management device 200 sends an email including the storage destination (link) of the invoice image data to the buyer terminal 300 designated as the delivery destination by the output unit 227 (step S1010).

[0074] The operations up to this point are the operations for sending invoice information from the seller terminal 400 to the buyer terminal 300. Note that the operations after step S1011 may be performed at an arbitrary timing independent of the operation for sending invoice information up to step S1010.

[0075] Next, when the received email is viewed on the buyer terminal 300 (step S1011) and the selection of the list screen address included in the email is accepted (step S1012), a display request for the invoice list screen is sent to the form management device 200 (step S1013).

[0076] When the form management device 200 receives a display request for a list screen of invoices from the screen generation unit 225, it generates screen data for displaying the list screen (step S1014). Note that the following processing indicates the case where no error occurs in the processing of step S1014. The details of the processing in step S1014 will be described later.

[0077] Subsequently, the form management device 200 transmits a display instruction for the list screen of invoices to the buyer terminal 300 by the display control unit 226 (step S1015).

[0078] The buyer terminal 300 receives the display instruction and causes the display unit 340 to display the list screen of invoices (step S1016).

[0079] In this embodiment, when an operation of receiving / downloading an invoice is received on the list screen of invoices displayed on the buyer terminal 300, the corresponding invoice information may be transmitted from the form management device 200 to the buyer terminal 300.

[0080] Hereinafter, with reference to FIG. 11, the processing of the registration unit 224 in this embodiment will be described. FIG. 11 is a first flowchart for explaining the processing of the form management device. In FIG. 11, the details of step S1009 in FIG. 10 are shown.

[0081] When the form management device 200 of this embodiment receives a sending request for an invoice by the specifying unit 223 of the form management unit 220, it specifies the invoices in the same month as the issue date of the invoice to be sent in the invoice database 250, and acquires the invoice numbers of the invoice information corresponding to the specified invoices (step S1101).

[0082] Subsequently, the registration unit 224 determines whether the corresponding invoice number has been acquired (step S1102). In step S1102, if the corresponding invoice number cannot be acquired, the form management unit 220 proceeds to step S1106, which will be described later.

[0083] In step S1102, when the corresponding claim number can be obtained, the registration unit 224 refers to the browsing management database 260 and obtains the list screen address corresponding to the obtained claim number (step S1103).

[0084] Subsequently, the registration unit 224 determines whether the corresponding list screen address can be obtained (step S1104). In step S1104, if the corresponding list screen address cannot be obtained, the form management unit 220 proceeds to step S1106 described later.

[0085] In step S1104, when the corresponding list screen address can be obtained, the registration unit 224 associates the obtained list screen address with the claim number obtained in step S1101 and registers (stores) it in the browsing management database 260 (step S1105), and ends the process.

[0086] If the corresponding claim number cannot be obtained in step S1103, or if the corresponding list screen address cannot be obtained in step S1104, the registration unit 224 generates a list screen address (step S1106).

[0087] Subsequently, the registration unit 224 associates the claim number included in the claim information indicating the claim form to be sent with the generated list screen address and stores it in the browsing management database 260 (step S1107), and ends the process.

[0088] The above is the process of the registration unit 224. Next, with reference to FIG. 12, the process of the screen generation unit 225 of the present embodiment will be described.

[0089] FIG. 12 is a second flowchart for explaining the process of the form management device. In FIG. 11, the details of step S1014 in FIG. 10 are shown.

[0090] When the invoice management device 200 of the present embodiment receives a display request for the list screen of invoices, the screen generation unit 225 of the invoice management unit 220 refers to the browsing management database 260 and acquires the claimant and invoice number corresponding to the list screen address (step S1201).

[0091] Subsequently, the screen generation unit 225 acquires all corresponding invoice information from the invoice database 250 based on the claimant and invoice number (step S1202). Subsequently, the screen generation unit 225 acquires the latest issue date from the acquired invoice information (step S1203).

[0092] Subsequently, the screen generation unit 225 refers to the viewing period management table 260-2 of the browsing management database 260 and calculates the valid period of the list screen address based on the issue date acquired in step S1203 (step S1204).

[0093] Subsequently, the screen generation unit 225 determines whether the date and time when the display request for the list screen address is received is within the valid period of the list screen address (step S1205).

[0094] In step S1205, if it is within the valid period, the screen generation unit 225 generates the screen data of the list screen of the invoice based on the invoice information acquired in step S1202 (step S1206) and ends the process.

[0095] In step S1205, if it is not within the valid period, the screen generation unit 225 generates the screen data for displaying an error (step S1207) and ends the process.

[0096] Next, with reference to FIGS. 13 to 16, the display example of the present embodiment will be described. FIG. 13 is a diagram showing an example of the invoice creation screen of the first embodiment.

[0097] The screen 130 shown in FIG. 13 is an example of the invoice creation screen displayed on the seller terminal 400 in step S1001 of FIG. 10.

[0098] The screen 130 has a display column 131 and operation buttons 132. In the display column 131, an input column for claim information is displayed. The operation buttons 132 are operation buttons for sending an instruction to create a claim document.

[0099] When claim information is input in the display column 131 and the operation buttons 132 are operated on the seller terminal 400 in the screen 130, the screen 130 is transitioned to a claim information sending screen.

[0100] FIG. 14 is a diagram showing an example of a claim document sending screen according to the first embodiment. The screen 140 shown in FIG. 14 is an example of a claim document sending screen displayed in step S1005 of FIG. 10.

[0101] The screen 140 includes a selection column 141, display columns 142 and 143, a selection column 144, and operation buttons 145. In the selection column 141, a list of email addresses to which the claim information is to be sent is displayed, and the destination of the claim information is selected.

[0102] In the display column 142, a claim document image indicated by the claim document image data generated based on the claim information is displayed. In the display column 143, the email body to be sent to the buyer terminal 300 when the claim information is sent is displayed.

[0103] The selection column 144 is a selection column for selecting registration of the claim information corresponding to the claim document image displayed in the display column 142 in the buyer's claim document list in the browsing management database 260. In the example of FIG. 14, registration in the buyer's claim document list is selected in the selection column 144.

[0104] Therefore, when the claim information corresponding to the claim document image displayed in the display column 142 is sent to the form management device 200, the registration unit 224 stores the claim document number of this claim information in the browsing management database 260 in association with the list screen address.

[0105] The operation button 245 is an operation button for transmitting the email body displayed in the display column 143 to the email address selected in the selection column 141 via the form management device 200.

[0106] When the operation button 145 is operated on the screen 140, the seller terminal 400 transmits a transmission instruction to the destination of the email shown in the selection column 141 to the form management device 200.

[0107] FIG. 15 is a diagram showing an example of a bill sending guidance screen according to the first embodiment. The screen 150 shown in FIG. 15 is an example of the sending guidance screen displayed on the buyer terminal 300 in step S1011 of FIG. 10.

[0108] The screen 150 includes display areas 151, 152, and 153. In the display area 151, the file name of the bill image data indicating the bill image is displayed. Information indicating the sending guidance is displayed in the display area 152.

[0109] In the display area 153, a list screen address (URL) for displaying the list screen of the bills is displayed.

[0110] In this embodiment, when the list screen address displayed in the display area 153 is selected, a display request for the list screen of the bills is transmitted from the buyer terminal 300 to the form management device 200.

[0111] Note that in this embodiment, the display request for this list screen may include the list screen address and the claimant included in the bill information corresponding to the bill image.

[0112] FIG. 16 is a diagram showing an example of a bill list screen according to the first embodiment. The screen 160 shown in FIG. 16 is a diagram showing an example of the bill list screen displayed on the buyer terminal 300 in step S1016 of FIG. 10. Further, the screen 160 shown in FIG. 16 shows a case where the claimant "B Co., Ltd." is included in the display request for the list screen.

[0113] The screen 160 includes display columns 161, 162, 163 and operation buttons 164. The display column 161 displays the list screen address.

[0114] The display column 162 displays a list of invoices whose claimant is "B Co., Ltd.". Specifically, the display column 162 displays a partial list of invoice information whose claimant is "B Co., Ltd.".

[0115] Note that in the display column 162, corresponding to each invoice, an operation button for displaying the invoice image on the buyer terminal 300 and an operation button for downloading the invoice information from the form management device 200 are displayed in association. Also, an operation button for sending a notice indicating that the invoice has been received to the form management device 200 may be displayed in the display column 162.

[0116] The operation button 164 is an operation button for downloading all the invoice information displayed as a list in the display column 162 at once.

[0117] In this embodiment, in this way, a list of invoice information with the same claimant and the same month of issue date can be displayed on the buyer terminal 300, and furthermore, the list-displayed invoice information can be downloaded to the buyer terminal 300 at once.

[0118] Therefore, according to this embodiment, the buyer terminal 300 does not need to perform the work of summarizing the invoices received during a certain period, and the convenience of the work can be improved.

[0119] Also, in this embodiment, since an expiration period for the list screen address is provided, it is possible to prevent the invoice information from being left in a state where it can be viewed for a long time, and the confidentiality of the information can be ensured.

[0120] (Second Embodiment) The second embodiment will be described below with reference to the drawings. In the second embodiment, it is different from the first embodiment in that the unit of the period for displaying the list of claims is set for each claim. Therefore, in the following description of the second embodiment, only the differences from the first embodiment will be described. For those having the same functional configuration as the first embodiment, the same reference numerals as those used in the description of the first embodiment will be assigned, and the description thereof will be omitted.

[0121] FIG. 17 is a diagram showing an example of the customer database in the second embodiment. The customer management database 240A in this embodiment may be provided for each tenant. The customer management database 240A includes items of information such as company name, email address, person in charge, period unit, etc.

[0122] The value of the item "period unit" indicates the unit of the period for displaying the list of claims. In the example of FIG. 17, in Company B, the period unit of the claimant "Company A" is "month". Therefore, the list of invoices of the claimant "Company A" is the list of invoices with the issue date within the same month.

[0123] Also, in the example of FIG. 17, in Company B, the period unit of the claimant "Company C" is "week". Therefore, the list of invoices of the claimant "Company C" is the list of invoices with the issue date within the same week.

[0124] In this embodiment, in this way, since the unit of the period for displaying the list of claims can be set for each claimant, a list screen of invoices corresponding to the form of the sales transaction can be displayed on the buyer terminal 300.

[0125] FIG. 18 is a diagram showing an example of the browsing management database in the second embodiment. The browsing management database 260A in this embodiment includes a browsing management table 260A-1 and a browsing expiration management table 260A-2.

[0126] The browsing management table 260A-1 includes, as information items, a list screen address, a status, a billing destination, a billing source, a period unit, and an invoice number. In the browsing management table 260A-1, the value of the item "period unit" indicates the unit of the period for displaying a list of invoices.

[0127] In addition, the browsing expiration management table 260A-2 stores information indicating the expiration period for each period unit. Specifically, in the browsing expiration management table 260A-2, when the period unit is "month", the expiration period of the list screen address is the end of the second month after the issue date, and when the period unit is "week", the expiration period of the list screen address is Friday two weeks after the issue date.

[0128] In this embodiment, the unit of the period for displaying a list of invoices can be set on the invoice sending screen.

[0129] FIG. 19 is a diagram showing an example of an invoice sending screen according to the second embodiment. The screen 140A shown in FIG. 19 includes a selection column 141, display columns 142 and 143, a selection column 144A, and an operation button 145. The selection column 144A is a selection column for selecting the registration of the invoice information corresponding to the invoice image displayed in the display column 142 in the buyer's invoice list in the browsing management database 260A.

[0130] The selection column 144A shown in FIG. 19 is configured to be able to select the unit of the period for displaying a list of invoices. In the example of FIG. 19, it can be seen that the unit of the period for displaying a list of invoices from "B Corporation" as the billing source is selected as "month".

[0131] In this embodiment, since the unit of the period for displaying a list of invoices can be set for each billing source in this way, a list screen of invoices corresponding to the form of the sales transaction can be displayed on the buyer terminal 300.

[0132] (Third Embodiment) The third embodiment will be described below with reference to the drawings. In the third embodiment, it is different from the first embodiment in that the list screen address is not distinguished for each claimant. In the following description of the third embodiment, the differences from the first embodiment will be described, and those 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 the description thereof will be omitted.

[0133] FIG. 20 is a diagram showing an example of the browsing management database of the third embodiment. In the browsing management table 260-1B shown in FIG. 20, it can be seen that a plurality of claimants are associated with one list screen address. In this way, the claim form information of a plurality of claimants can be displayed on the list screen.

[0134] Also, in this case, the business partner management database 240 does not have to be provided for each tenant and may be held as one table.

[0135] Next, with reference to FIG. 21, the list screen of the claim form of the present embodiment will be described. The screen 160A shown in FIG. 21 includes display columns 162A and 163A and an operation button 164A.

[0136] The display column 163A displays a list of claim forms for each claim form source associated with the list screen address. Specifically, the display column 163A includes a partial list of claim form information where the claimant is "B Co., Ltd." and a partial list of claim form information where the claimant is "D Co., Ltd.".

[0137] Also, in the display column 163A, the total amount of each claim amount in the claim forms listed for each claimant may be displayed.

[0138] Furthermore, in the display column 163A, corresponding to each bill, an operation button for displaying the bill image on the buyer terminal 300 and an operation button for downloading the bill information from the document management device 200 are displayed in association with each other. Also, in the display column 162A, an operation button for transmitting a notification indicating that the bill has been received to the document management device 200 may be displayed. Further, in the display column 162A, an operation button for downloading the bill information in a batch for each creditor may be displayed.

[0139] In the display column 162A, the number of bills listed in the display column 163A and the total amount of the claim amounts of each bill are displayed.

[0140] The operation button 164A is an operation button for downloading all the bill information listed as a list in the display column 163A in a batch.

[0141] In this embodiment, as described above, among the bills issued from a plurality of creditors, a list of bill information with the same issue month can be displayed on the buyer terminal 300, and further, the listed bill information can be downloaded to the buyer terminal 300 for each creditor or all at once.

[0142] Each function of the embodiment described above can be realized by one or a plurality of processing circuits. Here, the "processing circuit" in this specification refers to a processor programmed to execute each function by software like a processor implemented by an electronic circuit, an ASIC (Application Specific Integrated Circuit) designed to execute each function described above, a DSP (digital signal processor), an FPGA (field programmable gate array), and devices such as conventional circuit modules.

[0143] Also, the device groups described in the embodiments merely represent one of the multiple computing environments for implementing the embodiments disclosed in this specification.

[0144] In one embodiment, the document management device 200 includes a plurality of computing devices such as a server cluster. The plurality of computing devices are configured to communicate with each other via any type of communication link including a network or a shared memory, and implement the processes disclosed in this specification. Similarly, the document management device 200 can include a plurality of computing devices configured to communicate with each other.

[0145] Furthermore, the document management device 200 can be configured to share the disclosed processing steps in various combinations. For example, the process executed by the document management device 200 can be executed by other server devices. Similarly, the functions of the document management device 200 can be executed by other server devices. Also, each element of the server device and other server devices can be combined into one server device or divided into multiple devices.

[0146] Also, the correspondence table in the specification may be generated by the learning effect of machine learning. Also, by classifying keywords and accounting items that may be included in the description of transaction details using machine learning, it may not be necessary to use the correspondence table.

[0147] Here, machine learning is a technology for enabling a computer to acquire learning capabilities like those of humans. It refers to a technology in which a computer autonomously generates algorithms necessary for judgments such as data identification from pre-loaded learning data and applies this to new data for prediction. The learning method for machine learning can be any of supervised learning, unsupervised learning, semi-supervised learning, reinforcement learning, and deep learning methods. Furthermore, a learning method combining these learning methods is also acceptable, and the learning method for machine learning is not limited.

[0148] Although the present invention has been described based on each embodiment above, the present invention is not limited to the requirements shown in the above embodiments. In these respects, it can be changed without departing from the gist of the present invention, and can be appropriately determined according to its application form.

Explanation of Signs

[0149] 100 Form management system 200 Form management device 210 Storage unit 220 Form management unit 221 Input reception unit 222 Form image generation unit 223 Identification unit 224 Registration unit 225 Screen generation unit 226 Display control unit 227 Output unit 230 Tenant database 240 Customer management database 250 Invoice database 260 Browsing management database 300 Terminal device (buyer terminal) 400 Terminal device (seller terminal)

Prior Art Documents

Patent Documents

[0150]

Patent Document 1

Claims

1. A registration unit that registers by associating a plurality of forms issued to a specific destination with an address for displaying a list of the plurality of forms; A display control unit that causes a display unit to display a list of the plurality of forms based on access to the address by an operation of a user of the specific destination; A specifying unit that specifies form information that satisfies a preset condition in a storage unit in which form information indicating a form is stored, and has: The registration unit is: When a form for the specific destination is issued, it determines whether the address corresponding to the form information specified by the specifying unit can be obtained. If the address can be obtained, the obtained address and the issued form are associated and registered. An information processing apparatus.

2. The specifying unit is: The information processing apparatus according to claim 1, wherein the specifying unit specifies form information in which information regarding the issue date of the form is within a preset period.

3. The specifying unit is: The information processing apparatus according to claim 1 or 2, wherein the specifying unit specifies form information having the same form issuer.

4. The information processing apparatus according to any one of claims 1 to 3, further comprising an output unit that outputs information including the address to a destination registered in advance corresponding to the specific destination.

5. The registration unit is: The information processing apparatus according to claim 1, wherein it determines whether the address corresponding to the form information specified by the specifying unit can be obtained. If the address cannot be obtained, it generates an address corresponding to the form information specified by the specifying unit and registers it in association with the issued form.

6. Information indicating an expiration date is stored in a browsing management storage unit in the address, The display control unit is: Determines whether the date and time when a display request for the address is received is within the expiration date, The information processing apparatus according to claim 1, wherein when the date and time is within the expiration date, a list of the plurality of forms is displayed on a display unit.

7. An information processing system including a first terminal device, a second terminal device, and an information processing apparatus, The information processing apparatus is: A registration unit that registers by associating a plurality of forms issued in response to an operation of the second terminal device with an address for displaying a list of the plurality of forms; A display control unit that causes a display unit of the first terminal device to display a list of the plurality of forms based on access to the address by an operation on the first terminal device; In a storage unit storing form information indicating a form, there is a specifying unit that specifies form information satisfying preset conditions. The registering unit determines whether the address corresponding to the form information specified by the specifying unit can be acquired when a form for a specific recipient is issued. If the address can be acquired, the acquired address is registered in association with the issued form. The first terminal device has the display unit that displays a list of the plurality of forms. The second terminal device has a display unit that displays a form creation screen. An information processing system.

8. An information processing method by an information processing device, wherein the information processing device executes a procedure of registering in association a plurality of forms issued to a specific recipient and an address for displaying a list of the plurality of forms, a procedure of displaying a list of the plurality of forms on a display unit based on access to the address by an operation of a user of the specific recipient, and a procedure of specifying form information satisfying preset conditions in a storage unit storing form information indicating a form. The registering procedure determines whether the address corresponding to the form information specified by the specifying procedure can be acquired when a form for the specific recipient is issued. If the address can be acquired, the acquired address is registered in association with the issued form. An information processing method.

9. A process of registering in association a plurality of forms issued to a specific recipient and an address for displaying a list of the plurality of forms, a process of displaying a list of the plurality of forms on a display unit based on access to the address by an operation of a user of the specific recipient, and a process of specifying form information satisfying preset conditions in a storage unit storing form information indicating a form, and causing an information processing device to execute. The registering process determines whether the address corresponding to the form information specified by the specifying process can be acquired when a form for the specific recipient is issued. If the address can be acquired, the acquired address is registered in association with the issued form. A program.

Images