Information processing system, control method for information processing system, and program

Abstract

To provide an information processing system for properly fetching information having items set for each document type so as to register it as index data associated with an electronic book.SOLUTION: An information processing system includes: setting means for receiving setting of items of information which is associated with an electronic book for each type of acquired documents; and recording means for, when acquiring the information associated with the electronic book, recording it as the items whose setting has been received in the setting means for each electronic book associated with the information.SELECTED DRAWING: Figure 9

Description

[Technical Field]

[0001] The present invention relates to a method for referencing a document converted into electronic data. [Background technology]

[0002] In accordance with the Electronic Bookkeeping Act, when storing electronic records related to books, it is required to be able to set the book's "transaction date and other dates," "transaction amount," and "business partner" as search conditions.

[0003] In order to enable searching of ledgers stored as electronic records (hereafter referred to as electronic ledgers), a system is provided that stores index data as data linked to the electronic ledgers, and enables searching of linked ledgers from search results of the index data.

[0004] Patent document 1 discloses a device that can reliably separate multiple files into separate files, record read information, and automatically add predetermined index information (index data) to each file, even when multiple files are set at once. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 8-172514 DISCLOSURE OF THE INVENTION [Problem to be solved by the invention]

[0006] However, Patent Document 1 does not take into consideration the case where the index information (index data) to be read differs depending on the document type.

[0007] For each document type, there are other search conditions in addition to "transaction date," "transaction amount," and "client," and the items to be searched may differ depending on the document type. For example, additional items are set for each document type, such as "transfer destination information" for an "invoice" and "quote" for an "expiration date" of the quote, and index data is registered. Patent Document 1 does not take into consideration the acquisition of these additional items set for each document type by an information processing device and the creation of index data.

[0008] The present invention is calligraphy By category Facilitate the registration of index data That eye The target. [Means for solving the problem]

[0009] The present invention relates to electronic documents. Document type a first setting unit that sets index items that map index data of electronic documents, the first setting unit being arranged in correspondence with the document type; and a second setting unit that additionally sets the index items. setting Display the screen setting display Means and The aforementioned a setting means for adding the items additionally set based on the second setting unit as index items that can be set for the document type, and setting index items to be mapped by the first setting unit using items including the added index items; The setting means corresponds to the document type of the electronic document to be managed. setting and registering index data of the electronic document based on the index items. means and The present invention is characterized by having the following. [Effects of the Invention]

[0010] By the present invention, by document type To facilitate the registration of index data It is possible. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a diagram illustrating an example of a schematic configuration of an information processing system. [Figure 2] FIG. 2 is a block diagram showing an example of the hardware configuration of a person in charge terminal, a manager terminal, and a server. [Figure 3] FIG. 2 is a block diagram illustrating an example of a hardware configuration of a printing apparatus. [Figure 4] 10 is a flowchart illustrating an example of an electronic ledger registration process. [Figure 5] 10 is a flowchart illustrating an example of item mapping management. [Figure 6] 10 is a flowchart illustrating an example of an upload process. [Figure 7] 10 is a flowchart showing an example of a process for dividing an electronic ledger uploaded using a two-dimensional barcode. [Figure 8] 10 is a flowchart illustrating an example of a scanner storage requirement check process. [Figure 9] 10A to 10C are schematic diagrams showing examples of a document type selection screen, an item mapping management screen, and a document acquisition method selection screen. [Figure 10] 10A and 10B are schematic diagrams showing examples of a document inquiry screen and a document search screen. [Figure 11] 10A and 10B are schematic diagrams showing an example of a CSV file, corresponding database data, and a document inquiry screen. [Figure 12] 10A and 10B are schematic diagrams illustrating an example of a setting screen for electronic ledger post-registration and data for index advance registration and post-registration. [Figure 13] 10A and 10B are schematic diagrams illustrating an example of a folder structure generated for an upload batch execution file and an initial setting file when an upload batch is executed. DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

[0013] FIG. 1 is a diagram showing an example of a system configuration of an information processing system according to an embodiment of the present invention.

[0014] The information processing system 100 includes a scanner device 102, an administrator terminal 104, a web server 105, a database server 106, a batch server 107, an MFP (Multifunction Peripheral) 108, and a staff terminal 110, and the scanner device 102, MFP 108, and administrator terminal 104 are connected so that data can be sent and received.

[0015] In the present invention, the web server 105, database server 106, and batch server 107 are virtual servers that are placed on the cloud 114. Note that each server does not have to be placed on the cloud 114, and each may be placed in its own housing, or each function may be placed together in one or more housings.

[0016] The manager terminal 104, the cloud server group 114, the MFP 108, and the person in charge terminal 110 are connected via a network (LAN) 112 so as to be able to communicate with each other.

[0017] In the information processing system 100, the scanner device 102 or the MFP 108 scans the captured document or the like, and transmits the obtained data (hereinafter, electronic ledger) to the manager's terminal 104.

[0018] The manager terminal 104 displays the electronic ledger obtained by scanning with the scanner device 102 or MFP 108 on a display, accepts the setting of attribute information (including index data) for the electronic ledger using various methods, and stores the electronic ledger and the attribute information in association with each other in the server 106. The attribute information can be obtained, for example, from a two-dimensional barcode recorded in the electronic ledger or from a CSV file of data separate from the electronic ledger. Another method is for the manager to check the electronic ledger displayed on the display and input the attribute information using a keyboard or the like.

[0019] The manager's terminal 104 can search and display the electronic ledger stored in the server 106, and can also make changes to the electronic ledger (for example, replacing or deleting pages, changing the order of pages, etc.). The person in charge's terminal 110 can also search and display and make changes to the electronic ledger in the same way.

[0020] The MFP 108 prints the electronic ledger in response to a print instruction from the manager terminal 104 or the person in charge terminal 110 .

[0021] FIG. 2 is a block diagram showing an example of the hardware configuration of the manager terminal 104, Web server 105, database server 106, batch server 107, and person in charge terminal 110, as well as these information processing devices, in the embodiment of the present invention.

[0022] As shown in FIG. 2, these information processing devices are connected via a system bus 204 to a CPU (Central Processing Unit) 201, a ROM (Read Only Memory) 202, a RAM (Random Access Memory) 203, an input controller 205, a video controller 206, a memory controller 207, and a communication I / F controller 208.

[0023] The CPU 201 comprehensively controls each device and controller connected to the system bus 204 .

[0024] The ROM 202 or external memory 211 stores the BIOS (Basic Input / Output System) and OS (Operating System), which are control programs executed by the CPU 201, programs that can be read and executed by this information processing device, and various necessary data (including data tables).

[0025] The RAM 203 functions as a main memory, a work area, etc. for the CPU 201. The CPU 201 loads programs and the like required for executing processing from the ROM 202 or the external memory 211 into the RAM 203, and executes the loaded programs to realize various operations.

[0026] The input controller 205 controls input from an input device such as a keyboard 209 or a pointing device such as a mouse (not shown). If the input device is a touch panel, the user can issue various instructions by pressing (touching with a finger or the like) icons, cursors, or buttons displayed on the touch panel.

[0027] The touch panel may also be a touch panel capable of detecting positions touched by multiple fingers, such as a multi-touch screen.

[0028] The video controller 206 controls the display on an external output device such as a display 210. The display also includes the display of a notebook computer integrated into the main body. Note that the external output device is not limited to a display, and may be, for example, a projector. In addition, for devices capable of receiving the above-mentioned touch operation, an input device is also provided.

[0029] The video controller 206 can control a video memory (VRAM) for display control, and can use part of the RAM 203 as a video memory area, or can provide a separate dedicated video memory.

[0030] The memory controller 207 controls access to the external memory 211. The external memory may be an external storage device (hard disk) that stores a boot program, various applications, font data, user files, edited files, and various data, a flexible disk (FD), or a CompactFlash (registered trademark) memory connected to a PCMCIA card slot via an adapter.

[0031] The communication I / F controller 208 connects and communicates with external devices via a network, and executes communication control processing on the network. For example, communication using TCP / IP, telephone lines such as ISDN, and 3G lines for mobile phones are possible.

[0032] The CPU 201 enables display on the display 210 by, for example, executing a process of expanding (rasterizing) an outline font into a display information area in the RAM 203. The CPU 201 also enables user instructions using a mouse cursor (not shown) on the display 210.

[0033] Next, the hardware configuration of the printing device 108 shown in FIG. 1 will be described with reference to FIG.

[0034] FIG. 3 is a block diagram showing an example of the hardware configuration of the printing device 108 shown in FIG.

[0035] In FIG. 3, 316 is a controller unit that is connected to a scanner unit 314 that functions as an image input device and a printer unit 312 that functions as an image output device, and also connected to a LAN (e.g., LAN 112 shown in FIG. 1) or a public line (WAN) (e.g., PSTN or ISDN, etc.) to input and output image data and device information.

[0036] In the controller unit 316, a CPU 301 is a processor that controls the entire system. A RAM 302 is a system work memory for the CPU 301 to operate, and also serves as a program memory for recording programs and an image memory for temporarily recording image data.

[0037] 303 is a ROM that stores a system boot program and various control programs, and 304 is a hard disk drive (HDD) that stores various programs for controlling the system, image data, and the like.

[0038] An operation unit interface (operation unit I / F) 307 is an interface unit with an operation unit (keyboard) 308. The operation unit I / F 307 also serves to transmit key information input from the operation unit 308 (for example, pressing the start button) to the CPU 301.

[0039] A network interface (I / F) 305 is connected to the network (LAN) 112. It is also configured to enable wireless communication, connecting to other devices via infrared, Bluetooth (registered trademark), or Wi-Fi (registered trademark) for data input and output. A modem (MODEM) 306 is connected to a public line for data input and output, such as sending and receiving faxes.

[0040] An external interface (external I / F) 318 is an I / F unit that accepts external inputs such as USB, IEEE1394, a printer port, and RS-232C, and in this embodiment, a card reader 319 for reading an IC card (storage medium) of a mobile terminal required for authentication is connected to the external I / F 318. The CPU 301 controls the card reader 319 to read information from the IC card of the mobile terminal via the external I / F 318, and can acquire the information read from the IC card of the mobile terminal. The above devices are arranged on a system bus 309.

[0041] An image bus interface (IMAGE BUS I / F) 320 is a bus bridge that connects the system bus 309 with an image bus 315 that transfers image data at high speed and converts the data structure.

[0042] The image bus 315 is configured as a PCI bus or IEEE 1394. The following devices are connected to the image bus 315.

[0043] Reference numeral 310 denotes a raster image processor (RIP), which develops vector data such as PDL code into a bitmap image. Reference numeral 311 denotes a printer interface (printer I / F), which connects a printer unit 312 with a controller unit 316 and performs synchronous / asynchronous conversion of image data. Reference numeral 313 denotes a scanner interface (scanner I / F), which connects a scanner unit 314 with the controller unit 316 and performs synchronous / asynchronous conversion of image data.

[0044] An image processing unit 317 performs correction, processing, and editing on input image data, and performs printer correction, resolution conversion, etc. on print output image data. In addition, the image processing unit 317 also performs image data rotation and compression / expansion processing such as JPEG for multi-value image data and JBIG, MMR, MH for binary image data.

[0045] The scanner unit 314 illuminates an image on a piece of paper that serves as an original, scans it with a CCD line sensor, and converts it into an electrical signal as raster image data. The original paper is set on the tray of the original feeder, and when the device user issues a command to start reading from the operation unit 308, the CPU 301 gives a command to the scanner unit 314, and the feeder feeds the original paper one sheet at a time and performs the operation of reading the original image.

[0046] The printer unit 312 converts raster image data into an image on paper, and any method can be used, including electrophotography using a photosensitive drum or belt, or inkjet printing, which ejects ink from a micro-nozzle array to print an image directly on paper. The printing operation is initiated by a command from the CPU 301. The printer unit 312 has multiple paper feed trays, each with a corresponding paper cassette, so that different paper sizes or orientations can be selected.

[0047] The operation unit 308 has an LCD display unit with a touch panel sheet attached to the LCD, which displays the system operation screen, and when a displayed key is pressed, transmits the position information to the CPU 301 via the operation unit I / F 307. The operation unit 308 also has various operation keys, such as a start key, a stop key, an ID key, and a reset key.

[0048] The display performance of the display unit varies depending on the printing device, and the present invention is composed of a printing device that can be operated via a touch panel, and a printing device that simply has an LCD screen and displays text strings (such as the printing status and the name of the document being printed).

[0049] The start key on the operation unit 308 is used to start the operation of reading an original image, etc. The center of the start key has a two-color LED, green and red, which indicates whether the start key is ready to use depending on its color. The stop key on the operation unit 308 stops an operation that is in progress. The ID key on the operation unit 308 is used to input the user's user ID. The reset key is used to initialize the settings made on the operation unit.

[0050] Under the control of CPU 301, card reader 319 reads information stored on an IC card (which may be provided as an IC chip in the mobile terminal) and notifies CPU 301 of the read information via external I / F 318.

[0051] The card reader 319 is compatible with the NFC communication standard and is configured to be able to read and write data from and to IC chips on IC cards and mobile terminals. When an NFC-compatible mobile terminal is held over an NFC-compatible card reader, authentication is performed and the mobile terminal and printing device are paired.

[0052] Then, communication (P2P) can be established between the held-up mobile device and the printer, and data can be exchanged. Alternatively, communication can be handed over to high-speed communication standards such as Bluetooth (registered trademark) or Wi-Fi (registered trademark), allowing communication between the mobile device and the printer.

[0053] For example, by holding a mobile terminal over a card reader, it becomes possible to send images stored in the mobile terminal to a printing device. Details of the NFC communication standard are conventional technology, so a detailed explanation will be omitted.

[0054] The printing device 108 described above has a platform for controlling the printing device 108, and an authentication application for communicating with an authentication server (which may be the server 106) runs on this platform. The authentication application is stored in the HDD 304. Areas are reserved on the HDD 304 for login contexts that store user information at login and various setting information, which are managed by the platform.

[0055] Additionally, applications that extend the main functions of the printing device 108 are installed and run on the platform. These applications are executed using the platform's API.

[0056] Each function of the printing device 108 can be controlled via this platform.

[0057] The printing device 108 also stores a Web browser, allowing it to cooperate with a Web system. In this case, a screen received from a Web application server is displayed using the Web browser. A command given on the Web browser is requested to the Web application server, and by receiving the command from the Web application server, the printing device 108 can execute an operation (such as scanning or printing).

[0058] With the above configuration, the printing device 108 can transmit image data read from the scanner unit 314 onto the LAN 112 , and can print out print data received from the LAN 112 using the printer unit 312 .

[0059] Furthermore, image data read from the scanner unit 314 can be transmitted by fax over a public line using the modem 306 , and image data received by fax over a public line can be output by the printer unit 312 .

[0060] Next, the process of registering an electronic ledger (electronic document) will be described using the flowchart shown in Fig. 4. Note that although the present embodiment will be described as an electronic ledger, it may also be an electronic document that generates index data.

[0061] Each step in FIG. 4 is a processing step executed by the CPU 201 of the administrator terminal 104 and the batch server 107, respectively.

[0062] 4, a browser or an application is launched on the administrator terminal 104 to start communication with the Web server 105 or the batch server 107. FIG. 4 shows an example of communication with the batch server 107.

[0063] In S401, the manager terminal 104 transmits to the batch server 107 an instruction to perform item mapping management for setting document index items, etc., when acquiring index data to be linked to the electronic ledger acquired in S403. The document index items are the items and item order of the index data that are linked to the electronic ledger to be acquired and recorded in advance.

[0064] In S402, the batch server 107 performs an item mapping management process to acquire item mapping settings for different document index items depending on the method of acquiring index data, as will be described in detail with reference to FIG.

[0065] FIG. 5A is a flowchart illustrating the process of managing the item mapping of the index data to be acquired in the batch server 107.

[0066] Each step in FIG. 5 is a processing step executed by the CPU 201 of the batch server 107.

[0067] In S501, the batch server 107 transmits a selection screen for the set document type to the manager terminal 104. The process after the transmitted screen image will be described with reference to FIG.

[0068] FIG. 9(a) is a screen image of a UI that allows you to set the document index item type and item mapping for each document type.

[0069] Document types are displayed as a list in 904 in the document type list screen 901, and the item types and item mappings described below can be changed for each document type.

[0070] When the batch server 107 receives the press of the item type button 903 (S502), it is possible to add a document index item for "invoice (received)." For example, the items that a user wants to search for vary depending on the document type, such as "transfer account number" and "registered transfer account name" for an invoice, "expiration date" for an estimate, and "contract number" for a contract. Therefore, by pressing the item type button 903 and adding an item as described above, a document index item related to "invoice (received)" can be added as a search condition for the user. Furthermore, by pressing the add button 905, it is possible to add further document types to 904.

[0071] When the batch server 107 receives that the item mapping button 902 has been pressed (S502), it sends a selection screen (item mapping management screen) for setting item mapping for "Invoice (Received)" to the administrator terminal 104 (S503).

[0072] Figure 9(b) is a screen image of the item mapping management UI.

[0073] The item mapping management screen 911 is a screen image that is displayed on the manager terminal 104 when the item mapping button 902 corresponding to "invoice" is pressed.

[0074] Tabs 912, 913, 919 to 921, etc., within the item mapping management screen 911 allow you to set up item mapping for index data, taking into consideration the method of acquiring index data (upload method) and differences in the order in which electronic ledgers and index data are imported. 916 is a list that defines the document index items to be acquired. In the example of 916, the first column of the data to be acquired is "transaction date," the second column is "client," the third column is "transaction amount," and the fourth column is "prefecture."

[0075] When the batch server 107 receives the selection of a tab such as 912, 913, or 919 to 921 through the operation of the administrator of the administrator terminal 104 (S504), a screen relating to the acquisition method (upload method) for the displayed tab is displayed in the list section 916. In the case of the screen 911, 912 is selected, and the list section 916 displays a list of document index items and the item order when acquiring index data with a 2D barcode + document (a document + a 2D barcode in which index data within the document is registered: a document such as 1023 in FIG. 10). In addition, when 913 is selected, a list of document index items and the item order when acquiring index data with index data + document (a document + document and index data uploaded as CSV data of a separate data item) are displayed, and when 919 is selected, a list of document index items and the item order when index data of an already registered electronic ledger is acquired (updated) later as CSV data are displayed. When 920 is selected, a list of document index items and the item order are displayed for the case of an electronic ledger upload method in which index data such as CSV data is registered first and the index data is associated with an electronic ledger to be registered later. When 921 is selected, a setting screen is displayed for associating an electronic ledger to be registered later with the index data uploaded as the index data set in 920. Details of the 921 screen will be described later with reference to FIG. 12.

[0076] In S505, the batch server 107 accepts document index item settings from the administrator via the administrator terminal 104. For example, by changing the column 914, which is "Prefecture" in 911, to the added item "Transfer Account Number" using the item type button 903, etc., index data can be acquired as items in the order of "Transaction Date," "Transfer Partner," "Transaction Amount," and "Transfer Account Number," which match the index data registered in the two-dimensional barcode. Items can be added to this item in the fifth and sixth lines by pressing the + button 915.

[0077] In S506, when the batch server 107 receives a press of the setting button 917 from the administrator via the administrator terminal 104, it registers the document index item set by the administrator in S505 as the document index item.

[0078] In S507, the batch server 107 determines whether a setting end button (not shown) has been pressed. If the setting end button has been pressed, the process of the flowchart in Fig. 5 ends, and if another tab such as 912 or 913 or the back button 918 is pressed, the process proceeds to S508.

[0079] In S508, the batch server 107 determines the destination of the process depending on whether the button pressed in S507 was the tab button 912 or 913, or the back button 918. When the tab button 912 or 913 is pressed, the process transitions to S504, and the process returns to the process of accepting the tab selection, and the setting of the document index items for the other index data upload method is repeated. On the other hand, when the back button 918 is pressed, the process transitions to S501, and the set document type selection screen 901 is displayed. By transitioning to S501, the administrator can repeatedly set the document index items for the other document type that he or she wants to import.

[0080] As described above, the present invention allows the settings of document index items to be changed and registered depending on the method of uploading index data linked to an electronic ledger (for example, differences such as acquisition by two-dimensional barcode (912) as in 1024 in Figure 10 or acquisition of data in CSV format (913) as in 1001 in Figure 10) or the order in which the electronic ledger and index data are acquired (such as a method of acquiring the electronic ledger and index data at the same time as in 912 or 913, a method of acquiring only the electronic ledger first and then acquiring and associating the index data later as in 919, or a method of acquiring the index data first and then acquiring and associating the electronic ledger later as in 920 and 921), and allows document index items to be set for each method of uploading index data.

[0081] In addition, since it is possible to set the document index items of the index data to be acquired for each document type, it is possible to change and set the search items (=document index items) for each document type. Returning to the explanation of the flowchart in FIG.

[0082] In S403, the manager terminal 104 performs processing to acquire the electronic ledger as a file, the details of which will be described with reference to FIG.

[0083] FIG. 5(b) is a flowchart illustrating the flow of processing in which the manager terminal 104 acquires an electronic ledger as a file.

[0084] Each step in FIG. 5B is a processing step executed by the CPU 201 of the manager terminal 104.

[0085] In S511, the administrator terminal 104 acquires the electronic ledger as a scanned image from the scanner device 102 or MFP 108, or acquires it as a file if it is an electronically created file (for example, a PDF file attached to an email).

[0086] In S512, the administrator terminal 104 processes the acquired data depending on whether it is electronic transaction data that must be managed under the Electronic Bookkeeping Act, a scanned image that requires scanner storage requirements for management under the Electronic Bookkeeping Act, or other data.

[0087] If the administrator determines that the electronic ledger is electronic transaction data that must be managed under the Electronic Bookkeeping Act, the process proceeds to S513, and the administrator terminal 104 saves the data as an electronically created PDF file or the like containing index data. The index data may be included in the PDF file as a two-dimensional barcode, or may be stored in a separate CSV file in a specified folder and read in S404.

[0088] If the administrator determines that the scanned image requires scanner storage requirements for management under the Electronic Bookkeeping Act, the process proceeds to S514, where the administrator terminal 104 saves the scanned image as a file together with information for checking whether the scanner storage requirements are met (resolution and gradation of the scanned image, document size, etc.). The index data may be included as a two-dimensional barcode in the scanned image, or may be stored in a separate CSV file in a specified folder and read in S404.

[0089] If the administrator determines that the data is other data, the process proceeds to S515, and the administrator terminal 104 saves the scanned image or file as a file that does not satisfy the above conditions. This concludes the explanation of the flowchart in Figure 5(b). Returning to the explanation of the flowchart in Figure 4.

[0090] In S404, the administrator terminal 104 performs a process of uploading the file acquired in S403 to the batch server 107. The detailed process will be described with reference to Fig. 6 and Fig. 13 or Fig. 9(c).

[0091] FIG. 6 is a flowchart illustrating the flow of file upload processing using a batch file executed on the administrator terminal 104.

[0092] Each step in FIG. 6 is a processing step executed by the CPU 201 of the manager terminal 104.

[0093] Before starting the flowchart of Fig. 6, the administrator creates a predetermined folder structure under the folder set by the user and stores the files acquired in S403 in each folder. An example of the folder structure created by the administrator and the files to be stored will be described with reference to Fig. 13.

[0094] Figure 13(a) shows an example of the folder structure generated on the administrator terminal 104 when an upload batch execution file is executed. Two major folders ([Batch1] (1302) and [Batch2] (1305)) are generated in 1301, and an upload batch is executed for each folder. A [CSV] folder (1303) and a [DATA] folder (1304) are generated under the [Batch1] folder (1302), and the [CSV] folder (1303) stores index data when index data is obtained from CSV data, and the [DATA] folder (1304) stores the electronic ledger obtained in S403.

[0095] In S601, the administrator terminal 104 acquires an initial setting file. An example of the initial setting file will be described with reference to FIG.

[0096] Figure 13(b) shows a configuration file created in advance by the administrator, a data file such as 1311. ":Batch1" in 1312 is the title of the batch file to be executed, a title set as one of the options when executing batch processing. For example, if "UploadData.Exe 1 Batch1" is entered when executing a batch, the information under ":Batch1" will be used when the batch is executed. "Batch1.mode" in 1313 corresponds to the IDs of tabs 912, 913, 919-921 in Figure 9(b) and specifies the method for obtaining (uploading) the index data for the electronic ledger to be imported and the order in which the electronic ledger and index data will be imported. "Batch1.dir" in 1314 is the folder path where the electronic ledger and CSV files obtained in S403 are stored. "Batch1.doctp" in 1315 is the document type of the electronic ledger to be uploaded, and the ID corresponding to 904 in Figure 9(a) is entered.

[0097] In S602, the administrator terminal 104 reads the electronic ledger acquired in S403 from the value (folder path) of the initial setting file read in S601, and the CSV file in the case of an upload method using a CSV file.

[0098] In S603, the administrator terminal 104 determines whether "Batch.mode" in the initial setting file is a setting ID for reading the electronic ledger together with the two-dimensional barcode. If it is a setting ID for reading together with the two-dimensional barcode, the process proceeds to S604, and if it is not a setting ID for reading together with the two-dimensional barcode, the process proceeds to S606.

[0099] In S604, the manager terminal 104 reads the two-dimensional barcode registered in the electronic ledger and converts the two-dimensional barcode into CSV data.

[0100] In S605, the manager terminal 104 transmits the data converted into CSV data in S604 to the batch server 107.

[0101] In S620, the manager terminal 104 transmits (uploads) the electronic ledger read in S602 to the batch server 107, and the processing of the flowchart in FIG. 6 ends.

[0102] On the other hand, if it is determined in S603 that the setting ID is not one that is read together with the two-dimensional barcode, the process proceeds to S606, where the administrator terminal 104 determines whether "Batch.mode" in the initial setting file is a setting ID for acquiring both CSV data and an electronic ledger. If it is a setting ID for acquiring both CSV data and an electronic ledger, the process proceeds to S607, and if it is not a setting ID for acquiring both CSV data and an electronic ledger, the process proceeds to S608.

[0103] In S607, the administrator terminal 104 transmits the CSV file acquired in S602 to the batch server 107.

[0104] In S621, the manager terminal 104 transmits (uploads) the electronic ledger read in S602 to the batch server 107, and the processing of the flowchart in FIG. 6 ends.

[0105] Furthermore, if it is determined in S606 that the setting ID is not for acquiring both CSV data and an electronic ledger, the process proceeds to S608, where the administrator terminal 104 determines whether "Batch.mode" in the initial setting file is a setting ID for only updating CSV data (without uploading an electronic ledger). If the setting ID is for only updating CSV data, the process proceeds to S609, and if the setting ID is not for only updating CSV data, the process proceeds to S610.

[0106] In S609, the administrator terminal 104 transmits the CSV file acquired in S602 to the batch server 107. The batch server processes the transmitted CSV file as data linked to the electronic ledger already registered in the database server 106, thereby updating the index data.

[0107] If it is determined in S608 that the setting ID is not for only updating CSV data, the process proceeds to S610, where the administrator terminal 104 determines whether "Batch.mode" in the initial setting file is a setting ID for only pre-registering CSV data (not uploading electronic ledgers). If it is a setting ID for only pre-registering CSV data, the process proceeds to S611, and if it is not a setting ID for only pre-registering CSV data, the process proceeds to S612.

[0108] In S611, the administrator terminal 104 transmits the CSV file acquired in S602 to the batch server 107. The batch server registers only the index data of the transmitted CSV file in the database server 106, and records the data in association with the electronic ledger to be registered later. Details will be described later with reference to FIG. 12.

[0109] If it is determined in S610 that the setting ID is not for pre-registering CSV data only, the process proceeds to S612, where the manager terminal 104 transmits the file name of the electronic ledger acquired in S602 to the batch server 107. Thereafter, in S622, the manager terminal 104 transmits (uploads) the electronic ledger read in S602 to the batch server 107, and the process of the flowchart in Fig. 6 ends. Details will be described later with reference to Fig. 12. Note that, although the flowchart in Fig. 6 describes transmitting a file name, the data to be transmitted does not have to be a file name, and other attribute information may be used as long as it is data that is uniquely linked to the CSV data transmitted in S611.

[0110] 6 and 13 have been described as the process of transmitting (uploading) the electronic ledger acquired in S602 to the batch server 107, but the electronic ledger may also be transmitted (uploaded) to the database server 106 via the Web server 105. An example of uploading an electronic ledger by the Web server 105 will be described with reference to FIG. 9(c).

[0111] FIG. 9(c) is an image of a web screen displayed on the browser of the manager terminal 104 when uploading an electronic ledger to the web server 105.

[0112] On the document upload screen 931, the file drag-and-drop field 932 and file selection field 933 allow users to upload files using WebDAV technology. The data classification field 934 allows the administrator to select whether the data is a scanned image requiring scanner storage for management under the Electronic Bookkeeping Act, electronic transaction data requiring management under the Electronic Bookkeeping Act, or other data. When uploading from the document upload screen 931, the 2D barcode is read from the 2D barcode position on the file image defined by the QR position button 906 in Figure 9(a), and the data is automatically captured as an index within the 2D barcode. The QR division field 935 allows the administrator to select whether to divide the acquired electronic ledger using a 2D barcode. This 2D barcode division process is a setting for dividing and registering files using 2D barcodes as delimiters when registering multiple electronic ledger files together. Details will be described later with reference to Figure 7. For electronic ledger files without 2D barcodes, the administrator can directly set index data in the document index input field 936 on the document upload screen. Returning to the explanation of the flowchart in Figure 4.

[0113] In S405, the batch server 107 (Web server 105 in the case of Figure 9(c)) registers the electronic ledger sent from the administrator terminal 104 in the database server 106, and registers the CSV data as index data. The data items and item order when registering are set according to the document index items set in the document type and index data upload method set in S506. However, if QR Splitting 935 is selected or if the "Batch1.qrdiv" setting is "1" in the initial setting file 1311, index data is not registered in S405, and index data is registered for each two-dimensional barcode in S406.

[0114] In S406, the batch server 107 executes a process of dividing the acquired electronic ledger for each acquired two-dimensional barcode. The detailed flow of the process will be described with reference to FIG.

[0115] FIG. 7 is a flowchart illustrating the process of dividing the acquired electronic ledger using two-dimensional barcodes.

[0116] Each step in FIG. 7 is a processing step executed by the CPU 201 of the batch server 107.

[0117] In S701, the batch server 107 acquires the document type from the information acquired from the administrator terminal 104. When data is acquired from the batch server 107 by executing a batch file, the document type is acquired from the setting value of "Batch1.doctp" in the initial setting file 1311, and when data is acquired from the document upload screen 931 through the Web server 105, the document type is acquired from the setting value in the document type field 937.

[0118] In S702, the batch server 107 acquires the file registered in the database server 106 in S405.

[0119] In S703, the batch server 107 determines whether or not to execute processing to split the acquired file using a two-dimensional barcode. If it is determined that the file is to be split using a two-dimensional barcode, the process proceeds to S704, and if it is determined that the file is not to be split using a two-dimensional barcode, the process of the flowchart in Figure 7 ends. The determination of whether or not the file is to be split using a two-dimensional barcode is made by checking whether the setting value 1316 of "Batch1.qrdiv" in the initial setting file 1311 is "1" when data is acquired from the batch server 107 by executing a batch file, or by checking whether the check box for the QR split execution field 935 is ON when data is acquired from the document upload screen 931 via the Web server 105.

[0120] In S704, the batch server 107 repeats the processes from S704 to S716 for the number of files acquired in S702.

[0121] In S705, the batch server 107 acquires two-dimensional barcode reading position information for each document type. The two-dimensional barcode reading position information is acquired from the position of the two-dimensional barcode on the file image defined by the QR position button 906 in FIG. 9(a).

[0122] In S706, the batch server 107 reads the image in the acquired file.

[0123] In S707, the batch server 107 identifies the position of the two-dimensional barcode on the image of the file acquired in S706, and stores it as an image for each page of the file.

[0124] In S708, the batch server 107 repeats the processes from S708 to S710 for the number of images stored in S707.

[0125] In S709, the batch server 107 reads the two-dimensional barcode at the position defined by the QR position button 906 and stores the page from which the two-dimensional barcode was read. In the processing of S709, no processing is performed on images from which the two-dimensional barcode could not be read.

[0126] In S710, the batch server 107 repeats the process from S708 until all images have been processed.

[0127] In S711, the batch server 107 repeats the processes from S711 to S713 for the number of pages for which the two-dimensional barcode was read in S709.

[0128] In S712, the batch server 107 divides the images of each page by the two-dimensional barcode, stores them as files with the page stored in S709 (the page on which the two-dimensional barcode existed) as the head of the file, and transmits them to the database server 106.

[0129] In S713, the batch server 107 repeats the process from S711 for the number of pages for which the two-dimensional barcodes have been read.

[0130] In S714, the batch server 107 checks whether the value read from the 2D barcode read in S709 is appropriate as index data. For example, it checks whether the character type in the "transaction amount" field is numeric, and whether anything other than the prefecture name has been entered in the field for entering prefectures, such as field 914 in Figure 9(b).

[0131] In S715, the batch server 107 associates the index data checked in S714 with the file names divided and stored in S712, stores them, and transmits them to the database server 106.

[0132] In S716, the batch server 107 repeats the process from S704 for the number of files acquired in S702.

[0133] As described above, if index data is stored as a 2D barcode in an electronic ledger, multiple electronic ledger files can be uploaded at once, and each 2D barcode can be separated into a separate file. Conventionally, linking an electronic ledger to its index data required alternating between registering the index data and scanning the electronic ledger, but by using the processing in the flowchart of Figure 7, electronic ledger files with 2D barcodes can be linked together with their index data. This concludes the explanation of the flowchart in Figure 7. Return to the explanation of the flowchart in Figure 4.

[0134] In S407, the batch server 107 performs processing when the file registered in S405 is a file that must satisfy the scanner storage requirements, as will be described in detail with reference to FIG.

[0135] FIG. 8 is a flowchart illustrating the flow of processing for checking scanner storage requirements.

[0136] Each step in FIG. 8 is a processing step executed by the CPU 201 of the batch server 107.

[0137] In S801, the batch server 107 acquires the files that were divided in S405 and S406 and registered in the database server 106. Note that the process in the flowchart of Fig. 8 is repeated for each file.

[0138] In S802, the batch server 107 determines whether the file is required to satisfy the scanner storage requirements. If the file is required to satisfy the scanner storage requirements, the process proceeds to step S803. If the file is not required to satisfy the scanner storage requirements, the flowchart in Figure 8 ends. When data is acquired from the batch server 107 by executing a batch file, the determination of whether the file is required to satisfy the scanner storage requirements is made by checking whether a predetermined ID (in this case, "0") is set by the administrator in the setting value 1317 of "Batch1.datatp" in the initial setting file 1311. When data is acquired from the document upload screen 931 via the Web server 105, the determination is made by checking whether the data classification field 934 is set to "scanner storage."

[0139] In S803, the batch server 107 acquires information (resolution and gradation of the scanned image, document size, etc.) for checking whether the scanner storage requirements acquired in the process of S514 are met.

[0140] In step S804, the batch server 107 determines whether the scanner storage requirement check information acquired in step S803 matches the following conditions. -One image per page - Resolution must be 200 dpi or higher -256 gradations The color space is RGB or grayscale Image height and width: 1mm or more If the file satisfies all of the above conditions, the process proceeds to S805. If the file does not satisfy all of the above conditions, the process proceeds to S807.

[0141] When the process proceeds to S805, the batch server 107 determines that the file (electronic ledger) satisfies the scanner storage requirements, and in S806, turns on a flag indicating that the timestamp assignment requirements are met.

[0142] When the process proceeds to S807, the batch server 107 determines that the file (electronic ledger) does not satisfy the scanner storage requirements, and in S808 sets the flag indicating that the timestamp assignment conditions are satisfied to error. This concludes the explanation of the flowchart in Figure 8. Returning to the explanation of the flowchart in Figure 4.

[0143] In S408, the batch server 107 sends a timestamp generation request for the file whose flag indicating that the timestamp assignment condition is met in S407 to the timestamp server (TSA), and receives a timestamp token from the timestamp server. By assigning a timestamp, it is possible to prove that the electronic document existed before the time stamped on the timestamp and that it has not been tampered with.

[0144] By performing the above process, in order to ensure the search function of electronic ledgers, index data is registered in the database server, and by linking the index data to electronic ledgers, the linked electronic ledgers can be searched from the search results of the index data.At this time, if it is desired to change the index data assigned to the electronic ledgers for each document type, the index data can be changed so that the selection screen for each document type in Figure 9(a) transitions to Figure 9(b), and the administrator can set the search items.

[0145] Furthermore, even if the order of data items in index data differs for the same document type due to differences in the method of providing index data, the order of data items in index data for each method of provision can be appropriately imported using 912, 913, 919, 920, etc. on the selection screen in Figure 9(b).

[0146] With reference to FIG. 10, an image of the CSV data, the data to be registered in the database server 106, and the data to be registered displayed on the manager terminal 104 and the person in charge terminal 110 will be described.

[0147] FIG. 10(a) shows an example of CSV data, in which the contents of 1001 are encoded and embedded as a two-dimensional barcode such as 1024 in FIG. 10(c). When data is registered as a two-dimensional barcode without an item name, the corresponding index data must be appropriately set. Index data without item name information, such as data 1001 in this embodiment, may be sent from the publisher of the electronic ledger. Since the relationship between each value and item is unknown, it becomes necessary to identify the relationship between the index data and the item name (column name 1011). To this end, processing is performed in 911 in FIG. 9(b) to link the data (1001) embedded in the two-dimensional barcode with the item name.

[0148] Figure 10(b) shows an example of data 1001 registered in the database. In data example 1011, data 1001 is acquired as index data set in 1022 in Figure 10(c). The file name associated with the index data is also registered as "contract_20221014.pdf", with a file name such as 1023.

[0149] Figure 10(c) is an example of a document inquiry screen displayed on the manager terminal 104 or the person in charge terminal 110. A screen reflecting data example 1011 is displayed in browser 1021, and the acquired electronic ledger is displayed in document display field 1023. Index data acquired from two-dimensional barcode 1024 is acquired using the document index items set on a screen such as 911 in Figure 9(b), and each index data is reflected as shown in 1022. The file name is registered in document name field 1025 to link it to the electronic ledger. By clicking the file name in document name field 1025 with the mouse, the corresponding file "Contract_20221014.pdf" can be opened.

[0150] An image of the document search screen will be described with reference to FIG.

[0151] 1101 in FIG. 11 is an example of a document search screen. The text input area 1102 is a field for entering search conditions when searching an electronic ledger, and the search condition input field 1103 corresponds to the document index items set by the administrator on a screen such as 911 in FIG. 9(b). In the case of the search condition input field 1103, in addition to the default settings of "client," "transaction amount," and "transaction date," index data "unit price" is specified in 911. The search results are displayed in the result display field 1104. When the details button 1105 is pressed by the administrator or user, a document inquiry screen such as 1021 in FIG. 10(c) is displayed.

[0152] As described above, if the administrator sets index data for the document index items on a screen such as 911 in FIG. 9B, the index data can be set as search items as in the search condition input field 1103 on the document search screen.

[0153] The process of prior registration of index data and subsequent registration of files (electronic ledger) will be described with reference to FIG.

[0154] 12(a) is a screen image when the document (post-registration) tab 921 is selected on the screen 911. Unlike the other tabs, when the document (post-registration) tab 921 is selected, the list section 916 does not display a list of document index items, but displays a screen for setting information to be linked to previously registered index data. Note that when a document is to be post-registered, it is assumed that the index data of the document index item set using the index only (pre-registration) tab 920 has already been registered.

[0155] 12B shows an example of pre-registered index data. In the pre-registered index example 1221, the document name has not yet been registered in the linked document name column 1223.

[0156] In the list section 916 of FIG. 12(a), parameters are set for linking the file name with the previously registered index data using the file name as a key.

[0157] The separator column 1203 specifies the symbol of the delimiter that separates the file names. The key item specification position 1204 sets the position of the word in the file names separated by the separator column 1203 to be used as the key item. The key item specification 1205 specifies which data among the pre-registered index data is to be used as the key for the word specified in the key item specification position 1204. In the example of the list section 916, the key item specification position 1204 is "2" and the key item specification 1205 is "Customer", so for example, in the file name example 1211 shown in Figure 12(c), the second value separated by the separator "_ (underscore)", such as "Company A" or "Company B", becomes the key item.

[0158] From the settings in list section 916 and file name example 1211 in Fig. 12(a), the data in index advance registration example 1221 in Fig. 12(b) links business partner 1222 with file name example 1211, and links the file as in index after retroactive registration example 1231 in Fig. 12(d). In document name column 1233 corresponding to the data for business partner 1232, the corresponding file name is registered, and the file is retroactively registered in the advance registered index data (1221).

[0159] The index data to which a file has been added and the index data to which a file has not yet been added may be displayed in a distinguishable manner.

[0160] In this way, it is possible to receive only the index data first and link it to the electronic ledger that will be received later, making it possible to pre-register the index data even in cases where the electronic form arrives late, such as invoice information from overseas.In the example in Figure 12, the key item is extracted from the file name, but the key item does not have to be the file name; it can also be data embedded in the properties of the file.

[0161] As described above, it is possible to properly acquire index data even when different indexes are assigned to different document types or when the order of index items differs depending on the method of acquiring the index data. Furthermore, while it was previously necessary to alternate between registering index data and scanning electronic documents, this process allows the registration of index data and the scanning of electronic documents to be performed separately.

[0162] Although the embodiments of the present invention have been described above, the present invention can also be embodied as, for example, a system, an apparatus, a method, a program, or a recording medium, etc. Specifically, the present invention may be applied to a system made up of multiple devices, or may be applied to an apparatus made up of a single device.

[0163] Furthermore, the program of the present invention is a program that enables a computer to execute the processing methods of the flowcharts shown in Figures 4 to 8, and the storage medium of the present invention stores a program that enables a computer to execute the processing methods of Figures 4 to 8. Note that the program of the present invention may be a program for each processing method of each device in Figures 4 to 8.

[0164] As described above, it goes without saying that the object of the present invention can also be achieved by supplying a recording medium on which a program that realizes the functions of the above-mentioned embodiments is recorded to a system or device, and having the computer (or CPU or MPU) of that system or device read and execute the program stored on the recording medium.

[0165] In this case, the program itself read from the recording medium will realize the novel functions of the present invention, and the recording medium on which the program is recorded will constitute the present invention.

[0166] Examples of recording media for supplying the program include flexible disks, hard disks, optical disks, magneto-optical disks, CD-ROMs, CD-Rs, DVD-ROMs, magnetic tapes, non-volatile memory cards, ROMs, EEPROMs, and silicon disks.

[0167] Furthermore, it goes without saying that not only are the functions of the above-mentioned embodiments realized by the computer executing a program it has read, but also cases are included in which an OS (operating system) running on the computer performs some or all of the actual processing based on the instructions of the program, and the functions of the above-mentioned embodiments are realized through that processing.

[0168] Furthermore, it goes without saying that this also includes cases where a program read from a recording medium is written into a memory provided on a function expansion board inserted into a computer or a function expansion unit connected to the computer, and then a CPU or the like provided on the function expansion board or function expansion unit performs some or all of the actual processing based on the instructions of the program code, thereby realizing the functions of the above-mentioned embodiments.

[0169] Furthermore, the present invention may be applied to a system consisting of multiple devices, or to a device consisting of a single device. It goes without saying that the present invention can also be applied to a case where the present invention is achieved by supplying a program to a system or device. In this case, the system or device can enjoy the effects of the present invention by reading a recording medium containing a program for achieving the present invention into the system or device.

[0170] Furthermore, by downloading and reading a program for achieving the present invention from a server, database, etc. on a network using a communication program, the system or device can enjoy the effects of the present invention. Note that the present invention also includes configurations that combine the above-mentioned embodiments and their modified examples. [Explanation of symbols]

[0171] 100 Information Processing Systems 102 Scanner device 104 Administrator terminal 105 Web Server 106 Database Server 107 Batch Server 108 MFP 110 Personnel terminal 112 Internet lines 114 Cloud Environment

Claims

1. a display control means for controlling the display of the first reception section and the second reception section in association with each other for each document type of electronic documents; controlling the first reception unit to receive settings of candidate items related to data to be registered among data included in an electronic document of a document type corresponding to the first reception unit based on a user operation on the first reception unit; a control means for controlling the second receiving unit to accept, based on a user's operation on the second receiving unit, items related to data to be registered among data included in an electronic document of a document type corresponding to the second receiving unit from among the set candidate items; a registration means for registering data relating to an item that is accepted as an item relating to the data to be registered among data included in the electronic document in a database; An information processing system comprising:

2. a selection receiving means for receiving a selection of an acquisition format for acquiring data included in the electronic document for each document type of the electronic document; The control means controls the receiving unit to receive items related to the data to be registered for each of the acquisition formats for the document type based on a user's operation on the second receiving unit.

2. The information processing system according to claim 1, wherein:

3. The acquisition format of the data to be registered includes an acquisition format in which the data to be registered is acquired by reading a two-dimensional code attached to an electronic document; the control means performs control based on a user's operation on the second reception unit to receive settings of items related to the data to be registered, the settings corresponding to an acquisition format for acquiring the data to be registered by reading the two-dimensional code; The registration means registers the data to be registered, which is acquired from the two-dimensional code and is related to the item accepted as the item related to the data to be registered, in a database.

2. The information processing system according to claim 1, wherein:

4. the display control means controls to display a third reception unit in association with each document type of the electronic document; the control means controls to accept a setting of a position of the two-dimensional code on the electronic document based on a user's operation on the third acceptance unit; a reading means for reading the two-dimensional code based on the position of the two-dimensional code for which the setting has been accepted; 4. The information processing system according to claim 3, further comprising:

5. The electronic document group including a plurality of electronic documents is divided into individual electronic documents based on the two-dimensional code, and an acquisition means is further provided for acquiring the divided electronic documents, The registration means registers the data to be registered, which is acquired from the two-dimensional code, for each of the divided electronic documents acquired by the acquisition means.

4. The information processing system according to claim 3, wherein:

6. the display control means controls to display a list of document types of a plurality of electronic documents; Controlling to display a first reception section and a second reception section corresponding to each document type of the plurality of electronic documents controlled to be displayed in a list by the display control means at positions corresponding to the document types of the plurality of electronic documents.

2. The information processing system according to claim 1, wherein:

7. The display control means controls the display so that first reception sections relating to a plurality of document types are arranged in a vertical line, and controls the display so that second reception sections relating to a plurality of document types are arranged in a vertical line.

7. The information processing system according to claim 6, wherein:

8. The display control means controls to display a list of character strings indicating a plurality of document types in a vertical row, and controls to display the first reception section and the second reception section corresponding to the document type in a horizontal row with the character strings indicating the document type.

8. The information processing system according to claim 6 or 7, wherein:

9. further comprising a search means for searching the electronic document from a database; The control means controls to set the items related to the data to be registered as items for accepting setting of search conditions when the search means searches for electronic documents.

2. The information processing system according to claim 1, wherein:

10. A display control means of the information processing system a display control step of controlling the display of the first reception unit and the second reception unit in association with each other for each document type of electronic documents; The control means of the information processing system controlling the first reception unit to receive settings of candidate items related to data to be registered among data included in an electronic document of a document type corresponding to the first reception unit based on a user operation on the first reception unit; a control step of controlling the second receiving unit to accept, based on a user's operation on the second receiving unit, items related to data to be registered among data included in an electronic document of a document type corresponding to the second receiving unit from among the set candidate items; The registration means of the information processing system a registration step of registering data relating to items that are accepted as items relating to the data to be registered among data included in the electronic document into a database; An information processing method comprising:

11. A program for causing at least one computer to function as each of the means of the information processing system according to any one of claims 1 to 7 or 9.

Images