Information processing system and control method thereof, 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 that has been converted into electronic data. [Background technology]

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

[0003] In order to make it possible to search ledgers stored as electromagnetic records (hereinafter referred to as electronic ledgers), a system has been provided that stores index data as data linked to the electronic ledgers and makes it possible to search for the linked ledgers from the search results of the index data.

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

[0005] [Patent Document 1] JP 8-172514 DISCLOSURE OF THEINVENTION [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 for each document type.

[0007] For each document type, there are other conditions to search for besides "transaction date," "transaction amount," and "client," and the items to search for 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 the "expiration date" of the quotation, and index data is registered. Patent Document 1 does not take into consideration obtaining the additional items set for each document type using an information processing device and making them index data.

[0008] The present invention has an object to solve the above-mentioned problem, and has an object to appropriately obtain information having items set for each document type, and to register it as index data linked to an electronic ledger. [Means for solving the problem]

[0009] In order to solve the above problems, the present invention provides a setting unit for receiving settings for items of information associated with electronic documents for each document type to be acquired; a recording means for recording, when information related to the electronic document is acquired, the setting means for each electronic document related to the information as an item that has been set by the setting means; The present invention is characterized by having the following. Effect of the Invention

[0010] According to the present invention, information having parameters set for each document type can be appropriately acquired and registered as index data linked to an electronic ledger. [Brief description of the drawings]

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

[0012] Hereinafter, an embodiment 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 as to be able to send and receive data.

[0015] In the present invention, the Web server 105, the database server 106, and the batch server 107 are virtual servers located on the cloud 114. Note that each server does not have to be located on the cloud 114, and each may be located in its own housing, or each function may be integrated into 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 settings of attribute information (including index data) for the electronic ledger in various ways, 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 received 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 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 via a system bus 204.

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

[0024] The ROM 202 or external memory 211 holds a BIOS (Basic Input / Output System) and an 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 processes 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 give 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 be a touch panel capable of detecting positions touched by multiple fingers, such as a multi-touch screen.

[0028] The video controller 206 controls display on an external output device such as a display 210. The display also includes the display of a notebook computer integrated with 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 is capable of controlling a video memory (VRAM) for display control, and can use part of the RAM 203 as the video memory area, or can provide a separate dedicated video memory.

[0030] The memory controller 207 controls access to the external memory 211. As the external memory, an external storage device (hard disk) for storing a boot program, various applications, font data, user files, edit files, and various data, a flexible disk (FD), or a compact flash (registered trademark) memory connected to a PCMCIA card slot via an adapter, etc., can be used.

[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 in a display information area in the RAM 203. The CPU 201 also enables a user to give 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 a hardware configuration of the printing device 108 shown in FIG.

[0035] In FIG. 3, 316 denotes a controller unit which is connected to a scanner unit 314 functioning as an image input device and a printer unit 312 functioning as an image output device, and is 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 operation of the CPU 301, and also serves as a program memory for recording programs and an image memory for temporarily recording image data.

[0037] Reference numeral 303 denotes a ROM in which a boot program and various control programs for the system are stored, and 304 denotes a hard disk drive (HDD) in which various programs for controlling the system, image data, and the like are stored.

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

[0039] Reference numeral 305 denotes a network interface (Network I / F) which is connected to the network (LAN) 112. It is also configured to be capable of wireless communication, and connects to other devices via communication using infrared, Bluetooth (registered trademark), or Wi-Fi (registered trademark) to input and output data. Reference numeral 306 denotes a modem which connects to a public line and inputs and outputs data such as sending and receiving faxes.

[0040] Reference numeral 318 denotes an external interface (external I / F), which 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 reading of information from the IC card of the mobile terminal by the card reader 319 via this external I / F 318, and can obtain 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 and 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 section 312 to 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 section 314 to 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 and decompression 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 paper document, scans it with a CCD line sensor, and converts it into an electrical signal as raster image data. The document paper is set on the document feeder tray, 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 document paper one sheet at a time and performs the operation of reading the document image.

[0046] Printer unit 312 is a part that converts raster image data into an image on paper, and any method can be used, such as an electrophotographic method using a photosensitive drum or photosensitive belt, or an inkjet method in which ink is ejected from a minute nozzle array to directly print an image on paper. The printing operation is started by an instruction from CPU 301. Printer unit 312 has multiple paper feed stages so that different paper sizes or different paper orientations can be selected, and corresponding paper cassettes are provided.

[0047] The operation unit 308 has an LCD display unit with a touch panel sheet attached onto the LCD, and displays a system operation screen, and when a displayed key is pressed, transmits position information of the key 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] Furthermore, 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 character 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 when starting the operation of reading an original image, etc. A two-color LED, green and red, is located in the center of the start key, and the color indicates whether the start key is ready to use. The stop key on the operation unit 308 serves to stop an operation that is in progress. The ID key on the operation unit 308 is used when entering the user ID of the user. The reset key is used when initializing the settings from the operation unit.

[0050] Under the control of CPU 301, card reader 319 reads information stored in an IC card (which may be provided in a mobile terminal as an IC chip) 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 pairing is performed between the mobile terminal and the printing device.

[0052] It is then possible to establish communication (P2P) between the held-up mobile device and the printer, and to exchange data. It is also possible to hand over communication to Bluetooth (registered trademark) or Wi-Fi (registered trademark), which are high-speed communication standards, and have the mobile device and printer communicate with each other.

[0053] For example, by holding a mobile terminal over a card reader, it becomes possible to transmit images stored in the mobile terminal to a printing device. Note that details of the NFC communication standard are omitted here because they are conventional technology.

[0054] In the above-mentioned printing device 108, a platform for controlling the printing device 108 exists, 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] Furthermore, applications that extend the main functions of the printing device 108 are installed and run on the platform. These applications are executed using the API of the platform.

[0056] Through this platform, each function of the printing device 108 can be controlled.

[0057] The printing device 108 also stores a Web browser, and can 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 (scanning or printing).

[0058] With the above-described 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] In addition, image data read from a scanner unit 314 can be sent by FAX over a public line via a modem 306 , and image data received by FAX from a public line can be output by a printer unit 312 .

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

[0061] 4 are processing steps 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 a command to perform item mapping management for setting document index items and the like when acquiring index data to be linked to the electronic ledger acquired in S403. The document index items are items and item order of index data that are linked to the electronic ledger acquired and recorded in advance.

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

[0065] FIG. 5A is a flowchart illustrating a process for managing item mapping of 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 screen image is transmitted will be described with reference to FIG.

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

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

[0070] When the batch server 107 accepts that the item type button 903 has been pressed (S502), it is possible to add a document index item for "invoice (received)." For example, the items that a user wishes to search for differ 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. Also, by pressing the add button 905, a document type can be further added to 904.

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

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

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

[0074] Using tabs 912, 913, 919 to 921 in the item mapping management screen 911, item mapping of index data can be set taking into consideration the method of acquiring index data (upload method) and differences in the order of importing electronic ledgers and index data. 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 accepts the selection of a tab such as 912, 913, or 919 to 921 by the administrator of the administrator terminal 104 (S504), a screen related to the acquisition method (upload method) by the displayed tab is displayed in the list section 916. In the case of the screen of 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 2D barcode + document (document + 2D barcode in which index data in the document is registered: 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 (document + document and uploading index data as CSV data of separate data) are displayed, and when 919 is selected, a list of document index items and the item order when acquiring (updating) index data of an electronic ledger that has already been registered later with CSV data are displayed. When 920 is selected, a list of document index items and the order of items are displayed for the case of an upload method of an electronic ledger 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 are described later with reference to FIG.

[0076] In S505, the batch server 107 accepts document index item settings from the administrator via the administrator terminal 104. For example, by changing column 914, which is "Prefecture" in 911, to "Transfer Account Number," which has been added using 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 correspond to the index data registered in the two-dimensional barcode. Items can be added to the fifth and sixth lines by pressing + 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, the batch server 107 registers the document index item set by the administrator in S505 as .

[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 changes the processing destination 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 processing transitions to S504, where the processing returns to the processing for accepting the selection of a tab, and the setting of document index items for a different index data upload method is repeated. On the other hand, when the back button 918 is pressed, the processing transitions to S501, and the set document type selection screen 901 is displayed. By transitioning to S501, the administrator can repeatedly set document index items for another document type that he or she wishes to import.

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

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

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

[0083] FIG. 5B is a flowchart illustrating the flow of a process for acquiring an electronic ledger as a file in the manager terminal 104.

[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 according to whether it is electronic transaction data that needs to be managed under the Electronic Bookkeeping Act, a scanned image that needs to be stored by a scanner for management under the Electronic Bookkeeping Act, or other data.

[0087] If the administrator judges that the electronic book is electronic transaction data that needs to be managed under the Electronic Bookkeeping Act, the process proceeds to S513, and the administrator terminal 104 stores the electronically created PDF file or the like that contains 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, and the administrator terminal 104 stores 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 stores 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 manager 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 a file upload process 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] 13(a) shows an example of the folder configuration generated in 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] FIG. 13(b) shows a configuration file that is generated in advance by the administrator, and is a data file such as 1311. ":Batch1" in 1312 is the title of the batch file to be executed, and is a title that is set as one of the options when executing the batch process. For example, when "UploadData.Exe 1 Batch1" is entered when executing the batch, the information under ":Batch1" is used when executing the batch. "Batch1.mode" in 1313 corresponds to the IDs of the tabs such as 912, 913, and 919 to 921 in FIG. 9(b), and sets the method of acquiring index data of the electronic ledger to be imported (upload method) and the order of importing the electronic ledger and index data. "Batch1.dir" in 1314 is the folder path where the electronic ledger and CSV file acquired 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 FIG. 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 manager terminal 104 judges 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 ends the processing of the flowchart in FIG.

[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 manager 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 manager 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 ends the processing of the flowchart in FIG.

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

[0106] In S609, the manager terminal 104 transmits the CSV file acquired in S602 to the batch server 107. The batch server performs a process of updating index data for the transmitted CSV file as data linked to an electronic ledger already registered in the database server 106.

[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 manager terminal 104 determines whether the "Batch.mode" in the initial setting file is a setting ID for only pre-registering CSV data (not uploading an electronic ledger). 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 manager terminal 104 transmits the CSV file acquired in S602 to the batch server 107. In the batch server, only the index data of the transmitted CSV file is registered in the database server 106, and is recorded in association with an electronic ledger to be registered later. Details will be described later with reference to FIG.

[0109] If it is determined in S610 that the ID is not the setting ID for only pre-registering CSV data, 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 ends the process of the flowchart in Fig. 6. Details will be described later with reference to Fig. 12. Note that, although the file name is transmitted in the flowchart in Fig. 6, the data to be transmitted does not have to be the 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 be transmitted (uploaded) to the database server 106 via the Web server 105. An embodiment in which the electronic ledger is uploaded by the Web server 105 will be described with reference to FIG. 9(c).

[0111] FIG. 9C 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] In the document upload screen 931, the file drag and drop field 932 and the file selection field 933 are fields where files can be uploaded using WebDAV technology. The data classification field 934 is a field where the administrator can select whether the data is a scanned image that requires a scanner storage requirement for management under the Electronic Bookkeeping Act, electronic transaction data that requires management under the Electronic Bookkeeping Act, or other data. When uploading from the document upload screen 931, the two-dimensional barcode is read from the position of the two-dimensional barcode on the file image defined by the QR position button 906 in FIG. 9(a), and data is automatically acquired as an index in the two-dimensional barcode. The QR division execution field 935 is a selection item where the administrator can select whether or not to divide the acquired electronic ledger with a two-dimensional barcode. This two-dimensional barcode division process is a setting for dividing and registering a file using a two-dimensional barcode as a separator when registering multiple electronic ledger assemblies. Details will be described later with reference to FIG. 7. In the case of an electronic ledger that does not have a two-dimensional barcode, the administrator can directly set index data from the document index input field 936 on the document upload screen. Return to the explanation of the flowchart in FIG. 4.

[0113] In S405, the batch server 107 (Web server 105 in the case of FIG. 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 at the time of registration are set according to the document index items set in the document type and index data upload method set in S506. However, if QR division execution 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 2D 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. A detailed process flow will be described with reference to FIG.

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

[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 judges whether or not to execute a process of splitting the acquired file by a two-dimensional barcode. If it is judged that the file is to be split by a two-dimensional barcode, the process proceeds to S704, and if it is judged that the file is not to be split by a two-dimensional barcode, the process of the flowchart in Fig. 7 ends. The judgment of whether or not the file is to be split by a two-dimensional barcode is made by whether the setting value 1316 of "Batch1.qrdiv" in the initial setting file 1311 is "1" if data is acquired from the batch server 107 by executing a batch file, and by whether or not the check item in the QR split execution field 935 is ON if 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 the position of the two-dimensional barcode on the file image defined by the QR position button 906 in FIG. 9A.

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

[0123] In S707, the batch server 107 specifies 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 process of S709, no processing is performed on the image from which the two-dimensional barcode was not 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 the same number of times as 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 beginning with the page stored in S709 (the page on which the two-dimensional barcode existed), 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 barcode has been read.

[0130] In S714, the batch server 107 performs a process to check whether the value read from the two-dimensional barcode read in S709 is appropriate as index data. For example, it checks whether the character type in the "transaction amount" field is numeric, whether anything other than the prefecture name has been entered in the field for entering prefectures, such as field 914 in Fig. 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 two-dimensional barcode in an electronic ledger, multiple electronic ledger documents can be uploaded at once, and each can be split into a separate file for each two-dimensional barcode. Conventionally, linking an electronic ledger to index data required alternating between registering the index data and scanning the electronic ledger, but by using the process shown in the flowchart of Figure 7, it is possible to link electronic ledger documents with index data all at once, as long as the electronic ledger contains a two-dimensional barcode. 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 in the case where 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 process of checking the 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 judges 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, and if the file is not required to satisfy the scanner storage requirements, the flow chart in Fig. 8 is terminated. When data is acquired from the batch server 107 by executing a batch file, the judgment of whether the file is required to satisfy the scanner storage requirements is made based on 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 judgment is made based on whether the data classification field 934 is set to scanner storage.

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

[0140] In S804, the batch server 107 determines whether the scanner storage requirement check information acquired in S803 matches the following conditions. -There is one image per page - Resolution must be 200dpi or higher - 256 gradations -The color space must be RGB or grayscale. Image height / 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 time stamp attachment 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 sets the flag indicating that the time stamp assignment requirements are satisfied to an error in S808. This concludes the explanation of the flowchart in Fig. 8. Returning to the explanation of the flowchart in Fig. 4.

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

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

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

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

[0147] FIG. 10(a) is an example of CSV data, and the contents of 1001 are embedded as symbols in a two-dimensional barcode such as 1024 in FIG. 10(c). In this way, when data is registered without an item name entered in the two-dimensional barcode, the corresponding index data must be appropriately set. Index data without item name information, such as the data 1001 in this embodiment, may be sent from the issuer of the electronic ledger, and since the relationship between each value and the item is unknown, it becomes necessary to specify the relationship between the index data and the item name (column name of 1011). For this purpose, in 911 in FIG. 9(b), a process is performed to link the data (1001) embedded in the two-dimensional barcode with the item name.

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

[0149] FIG. 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 in a screen such as 911 in FIG. 9(b), and each index data is reflected as shown in 1022. The file name is registered in document name field 1025 to link with the electronic ledger. The corresponding file "contract_20221014.pdf" can be opened by clicking the file name in document name field 1025 with the mouse, etc.

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

[0151] An example of a document search screen is shown at 1101 in Fig. 11. A text input section 1102 is a field for inputting search conditions when searching an electronic ledger, and a 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," this is an example in which index data "unit price" is specified in 911. The search results are displayed in a result display field 1104. When a 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 such as the search condition input field 1103 on the document search screen.

[0153] The process of prior registration of index data and subsequent registration of a file (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. When the document (post-registration) tab 921 is selected, unlike the other tabs, the list of document index items is not displayed in the list section 916, but a screen for setting information to be linked to previously registered index data is displayed. Note that when performing post-registration of a document, it is assumed that the index data of the document index item set by the index only (pre-registration) tab 920 has already been registered.

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

[0156] In the list section 916 in 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] In the separator column 1203, a delimiter symbol for separating file names is specified. In the key item specification position 1204, the number of words in the file names separated in the separator column 1203 that are to be used as the key item are set. In the key item specification 1205, which data of the pre-registered index data is to be used as the key by the word specified in the key item specification position 1204 is specified. In the example of the list section 916, the key item specification position 1204 is "2" and the key item specification 1205 is "business partner", so for example, in the file name example 1211 as shown in FIG. 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 post-registration index 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 post-registered in the advance registered index data (1221).

[0159] Incidentally, index data to which a file has been added and 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, and it is possible to pre-register the index data even in cases where the electronic document arrives late, such as invoice information from overseas. Note that in the example of Figure 12, the key item is extracted from the file name, but the key item does not have to be the file name, and can be data embedded in the properties of the file.

[0161] As described above, even if different indexes are assigned to different document types or the order of index items differs depending on the method of obtaining the index data, the index data can be obtained appropriately. In addition, while it was necessary to alternate between registering index data and scanning electronic documents in the past, this process allows the registration of index data and the scanning of electronic documents to be performed separately.

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

[0163] Moreover, 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. The program of the present invention may be a program for each processing method of each device of Figures 4 to 8.

[0164] As described above, it goes without saying that the object of the present invention can 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 out 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, silicon disks, etc.

[0167] Furthermore, it goes without saying that the functions of the above-mentioned embodiments are not only realized by the computer executing a program it has read, but also includes cases where 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 a 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] The present invention may be applied to a system consisting of multiple devices, or to an apparatus consisting of a single device. Needless to say, the present invention can also be applied to a case where the object is achieved by supplying a program to a system or apparatus. In this case, the effect of the present invention can be enjoyed by the system or apparatus by reading a recording medium storing a program for achieving the present invention into the system or apparatus.

[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 line 114 Cloud Environment

Claims

1. A setting display means for displaying a setting screen having a document type of an electronic document, a first setting section for setting index items arranged corresponding to the document type, which are to be mapped to index data of the electronic document, and a second setting section for additionally setting the index items; 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; a registering means for registering index data of the electronic document based on the index item set by the setting means corresponding to the document type of the electronic document to be managed; An information processing system comprising:

2. The information processing system described in Claim 1, characterized in that the registration means registers the index data using index items set for the document type in accordance with the acquisition format of the index data of the electronic document.

3. The information processing system according to claim 2, characterized in that the setting by the first setting unit makes it possible to specify, for each document type, an index item to which the index data is mapped in accordance with an acquisition format of the index data of the electronic document.

4. An information processing system as described in any one of claims 1 to 3, characterized in that the registration means registers the index data using information contained in identification information added to the electronic document.

5. The information processing system of claim 4, characterized in that when registering index data from the identification information, the registration means registers the index data using index items set by the setting means corresponding to the identification information.

6. The setting screen displayed on the setting display means further includes a third setting section that sets a position of identification information added to the electronic document in the electronic document, the position being arranged in correspondence with the document type; 5. The information processing system according to claim 4, further comprising a reading unit for reading the identification information based on the position set by the third setting unit.

7. The setting screen displays a list of document types, and the first setting section, the second setting section, and the third setting section are arranged corresponding to the document types, enabling settings for each document type; The information processing system according to claim 6, characterized in that the registration means registers index data of an electronic document using settings made by the first setting unit, the second setting unit, and the third setting unit based on the document type of the electronic document being managed.

8. an acquisition means for acquiring the electronic document by dividing the electronic document according to identification information added to the electronic document; 5. The information processing system according to claim 4, wherein the registration means registers information included in the divided identification information for each electronic document divided and acquired by the acquisition means.

9. The information processing system described in claim 4, characterized in that the identification information is a two-dimensional barcode.

10. 4. The information processing system according to claim 1, wherein the index data of the electronic document does not include item name information of the index data.

11. A setting display step of displaying a setting screen having a document type of an electronic document, a first setting section for setting index items arranged corresponding to the document type, which are used to map index data of the electronic document, and a second setting section for additionally setting the index items; a setting step in which the items additionally set based on the second setting unit are added as index items that can be set for the document type, and index items to be mapped by the first setting unit are set using items including the added index items; a registering step of registering index data of the electronic document based on the index items set in the setting step corresponding to the document type of the electronic document to be managed; 13. A method for controlling an information processing system comprising:

12. 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 3.

Images