Document management system and data processing method in document transaction system

The document management system automates the verification of document transactions by using a transaction device and management system to store and update transaction flags, addressing the inefficiencies in manual form payment confirmation processes.

JP7758834B2Active Publication Date: 2025-10-22GLORY LTD
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
JP2024203201
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2024-11-21
Publication Date
2025-10-22
Estimated Expiration
2039-10-18

AI Technical Summary

Technical Problem

The manual process of confirming fee payments for issued forms at financial institutions is burdensome for staff, requiring manual unpacking, visual checking, and searching for payment advice information, leading to a need for improved usability.

Method used

A document management system with a document transaction device and management device that stores transaction data and presence/absence flags, allowing for automated identification and management of transacted documents, and outputting issuer-oriented data to update transaction flags, reducing manual intervention.

Benefits of technology

The system enhances the ease of use by automating the verification of document transactions, reducing the burden on staff and improving efficiency in managing and processing forms.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007758834000001
    Figure 0007758834000001
  • Figure 0007758834000002
    Figure 0007758834000002
  • Figure 0007758834000003
    Figure 0007758834000003
Patent Text Reader

Abstract

To provide a data processing method for a business form management system and a business form transaction system that can improve usability of a business form.SOLUTION: A business form management system 100 includes: a business form transaction device 1 that performs a transaction by a business form; and a management device 106 that manages a table 118. The business form transaction device 1 executes a transaction based on the business form and outputs, to the management device 106, issue source-destined data for specifying a business form F targeted at the executed transaction, which is issue source-destined data for an issue source of the business form to specify the business form having been subjected to the transaction. The management device 106 changes a state of a transaction presence / absence flag corresponding to data about the business form specified by the input issue source-destined data among data about business forms stored in the table 118 from first information corresponding to absence of transaction to second information corresponding to completion of transaction.SELECTED DRAWING: Figure 6
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] The present invention relates to a form management system including a form transaction device and a data processing method in the form transaction system. [Background technology]

[0002] The following Patent Document 1 discloses an automated teller machine that is installed in a financial institution and that automatically performs fee payment transactions. A user receives a slip on which information such as the amount of a fee to be paid is printed, and the user brings the slip to the financial institution and inserts it into the inlet / outlet of the automated teller machine. When the user then pays the fee by inserting cash into the automated teller machine, the slip is taken into the automated teller machine through the inlet / outlet, a receipt mark is entered on the slip, and the slip is then cut into a receipt and a payment notice. The receipt is ejected from the inlet / outlet and returned to the user, and the payment notice is collected in the automated teller machine and sent to the payee of the fee (i.e., the issuer of the slip). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2018-81381 Summary of the Invention [Problem to be solved by the invention]

[0004] In a typical process at the issuer of a payment advice sent after a transaction at an automated teller machine such as that described in Patent Document 1, a staff member at the issuer confirms whether or not the fee for the issued form has been paid by deleting the information on the form corresponding to the payment advice from a list of issued forms prepared in advance. In this process, the staff member must manually unpack the group of payment advices sent from the financial institution, remove the actual payment advice, visually check the contents of the payment advice, and then search for the information on the form corresponding to this payment advice from the list. This places a heavy burden on the staff member, and improvements in usability are desired.

[0005] The present invention has been made in light of the above background, and has as its object to provide a form management system and a data processing method in a form transaction system that can improve the ease of use of forms. [Means for solving the problem]

[0006] One embodiment of the present invention provides a document management system including a document transaction device that performs transactions using documents and a management device that manages a table in which data of issued documents and transaction presence / absence flags indicating whether the data of the issued documents have been transacted are stored in association with each other, wherein the document transaction device includes a transaction unit that executes transactions based on documents and an output unit that outputs issuer-oriented data to the management device, the issuer-oriented data being used to identify documents that were the subject of the transactions executed by the transaction unit, and allowing the issuer of the document to identify transacted documents.The management device may also include an input unit that receives the issuer-oriented data output by the output unit, and a flag change unit that changes the state of a transaction presence / absence flag corresponding to the document data identified by the issuer-oriented data input to the input unit, among the document data stored in the table, from first information corresponding to an untransacted state to second information corresponding to a transacted state. The management device may manage data of issued forms. Furthermore, the issuer-oriented data output by the output unit may be directly input from the output unit to the input unit. Furthermore, the flag change unit may leave data of a form identified by the issuer-oriented data input to the input unit without deleting it from the table.

[0007] One embodiment of the present invention provides a data processing method in a document management system that includes a document transaction device that performs transactions using documents, and a management device that manages a table in which data of issued documents and transaction presence / absence flags that indicate whether the data of the issued documents has been transacted are stored in correspondence with each other, the data processing method including: a transaction step that executes a transaction based on the document; an output step that outputs issuer-oriented data intended for the issuer of the document to the management device for identifying the document that was the subject of the transaction in the transaction step; and a flag change step that changes the state of the transaction presence / absence flag corresponding to the data of the document identified by the issuer-oriented data input to the management device from first information corresponding to an untransacted transaction to second information corresponding to a transacted transaction. The document transaction device may execute the transaction step and the output step. The management device may manage data of issued documents. The management device may execute the flag change step. The data for the issuer output from the document transaction device may be directly input to the management device. In the flag change step, the data for the document identified by the input data for the issuer may be left in the table without being deleted.

[0008] In one embodiment of the present invention, the data for the issuer may include identification information for identifying the document that was the subject of the transaction executed by the transaction unit.

[0009] One embodiment of the present invention provides a document transaction device for conducting transactions using documents. The document transaction device includes an acquisition unit that acquires transaction data related to the transaction, a generation unit that generates issuer-oriented data directed to the issuer of the document based on the transaction data, and an output unit that outputs the issuer-oriented data to an external device. The document transaction device further includes a transaction unit that executes the transaction based on the document. The output unit outputs the issuer-oriented data to an external device at a predetermined timing after the transaction is executed by the transaction unit.

[0010] In one embodiment of the present invention, the data for the issuer includes at least detail data of the transaction.

[0011] In one embodiment of the present invention, the acquisition unit includes a reading unit that reads image data of the form from the form, and the data for the issuer includes the image data.

[0012] In one embodiment of the present invention, the output unit outputs the issuer-destined data to the outside at the processing timing of the processing unit. The output unit may output the issuer-destined data to the outside at a predetermined timing after the execution timing of the transaction by the transaction unit. The predetermined timing may be the completion of the transaction by the transaction unit. The predetermined timing may be the time of closing work. The predetermined timing may be the time of the next startup of the document transaction device. The document transaction device may further include an attendant operation unit operable by an attendant, and the predetermined timing may be a timing when a predetermined operation is performed on the attendant operation unit. The generation unit may generate the issuer-oriented data collectively for a plurality of the transactions executed by the transaction unit.

[0013] In one embodiment of the present invention, the form transaction device includes a processing unit that performs processing for filling in forms and / or cutting forms, and the generating unit generates format data for the form format based on the image data read from the form by the reading unit, and the output unit outputs the format data to an external device at a timing later than the processing timing of the processing unit.

[0014] In addition, in one embodiment of the present invention, if the output unit fails to externally output the data for the issuer at the processing timing, the output unit externally outputs the data for the issuer at a timing later than the processing timing.

[0015] In one embodiment of the present invention, the document contains required data for the transaction. The acquisition unit includes an operation unit operated by a user who conducts a transaction using the document with the document transaction device to input the required data. The transaction includes a first transaction based on the required data included in the image data read by the reading unit and a second transaction based on the required data input by the user through operation of the operation unit. In the case of the first transaction, the output unit outputs the issuer-oriented data to an external device at the processing timing, and in the case of the second transaction, the output unit outputs the issuer-oriented data to an external device at the end of the second transaction.

[0016] In one embodiment of the present invention, the document transaction device further includes a creating unit that creates an electronic journal about the transaction history.

[0017] In addition, in one embodiment of the present invention, the output unit outputs the data for the issuer externally at least one of the following times: when the document transaction device is started, when an error that has occurred in the document transaction device is resolved, when the transaction data is canceled, and when the electronic journal is created.

[0018] Another embodiment of the present invention provides a document management system including a document transaction device that performs transactions using documents and a management device that manages a list of issued documents. The document transaction device includes a transaction unit that executes transactions based on documents, an acquisition unit that acquires transaction data related to the transactions performed by the transaction unit, a generation unit that generates issuer-oriented data based on the transaction data so that the issuer of the document can identify the transacted document, and an output unit that outputs the issuer-oriented data to an external device. The output unit outputs the issuer-oriented data to an external device at a predetermined timing after the transaction is performed by the transaction unit. The management device includes an input unit that receives the issuer-oriented data output by the output unit, and a reversal unit that reversals the data of the transacted document from the list based on the issuer-oriented data input to the input unit.

[0019] In one embodiment of the present invention, the form management system includes a relay device that relays the issuer-oriented data externally output by the output unit to the input unit.

[0020] In addition, in one embodiment of the present invention, the document transaction device includes a first memory unit that stores the data for the issuer, and the relay device includes a receiving unit that receives the data for the issuer that is output externally by the output unit, a second memory unit that stores the data for the issuer received by the receiving unit, and a transmitting unit that transmits the data for the issuer stored in the second memory unit to the input unit.

[0021] Another embodiment of the present invention provides a data processing method for a document transaction device that performs transactions using documents. The data processing method includes an acquisition step of acquiring transaction data related to the transaction, a generation step of generating issuer-oriented data for the issuer of the document based on the transaction data, and an output step of externally outputting the issuer-oriented data. The data processing method may further include a transaction step of executing a transaction based on the document. The output step may include a step of externally outputting the issuer-oriented data at a predetermined timing after the execution timing of the transaction in the transaction step. The output step may include a step of externally outputting the issuer-oriented data at a predetermined timing after the execution timing of the transaction in the transaction step. The predetermined timing may be the end of the transaction in the transaction step. The predetermined timing may be the time of closing work. The predetermined timing may be the next time the document transaction device is started. [Effects of the Invention]

[0022] According to the present invention, the ease of use of forms can be improved. [Brief explanation of the drawings]

[0023] [Figure 1]FIG. 2 is a schematic diagram illustrating an example of a form used in one embodiment of the present invention. [Figure 2] FIG. 10 is a schematic diagram showing the form in a separated state after a receipt stamp has been written. [Figure 3] 1 is a schematic diagram illustrating an overview of a form management system according to an embodiment of the present invention. [Figure 4] 1 is a perspective view of a document transaction device constituting a document management system. [Figure 5] 1 is a schematic side view showing the internal structure of a document transaction device. [Figure 6] FIG. 2 is a block diagram showing the electrical configuration of the document management system. [Figure 7] 2 is a diagram showing a table stored in a management device constituting a form management system; FIG. [Figure 8] 4 is a flowchart showing the content of processing performed in the document transaction device during a transaction. [Figure 9] 4 is a flowchart showing the content of processing performed in the document transaction device during a transaction. [Figure 10] 2 is a schematic diagram showing an example of the display content of a display operation unit of a document transaction device. FIG. [Figure 11] FIG. 3 is a schematic diagram showing an example of display content of a display operation unit. [Figure 12] FIG. 3 is a schematic diagram showing an example of display content of a display operation unit. [Figure 13] FIG. 3 is a schematic diagram showing an example of display content of a display operation unit. [Figure 14] FIG. 3 is a schematic diagram showing an example of display content of a display operation unit. [Figure 15] FIG. 3 is a schematic diagram showing an example of display content of a display operation unit. [Figure 16] FIG. 3 is a schematic diagram showing an example of display content of a display operation unit. [Figure 17] FIG. 3 is a schematic diagram showing an example of display content of a display operation unit. [Figure 18] 4 is a flowchart showing the content of processing performed in the document transaction device during a transaction. [Figure 19]FIG. 3 is a schematic diagram showing an example of display content of a display operation unit. [Figure 20] FIG. 2 is a schematic diagram of a receipt issued from the document transaction device. [Figure 21] 10 is a flowchart showing the content of processing performed in the document transaction device at startup. [Figure 22] 10 is a flowchart showing the content of processing performed in the document transaction device when a predetermined operation is performed by a clerk. [Figure 23] 10 is a flowchart showing the content of processing performed in the document transaction device after business hours. DETAILED DESCRIPTION OF THE INVENTION

[0024] An embodiment of the present invention will be described in detail below with reference to the accompanying drawings. Figures 1 and 2 are schematic diagrams showing an example of a form F used in an embodiment of the present invention. Form F is a payment slip or invoice issued by a government agency, a retailer, or the like, and in this embodiment, it is a payment slip issued by a local government. Form F is delivered by mail or the like to a user who is to pay taxes, utility bills, or other charges, and then the user takes form F to a financial institution such as a bank to pay the charges.

[0025] The entire document F is, for example, a rectangular piece of paper. In document F, a receipt F1, which is returned to the user after payment of the fee, and a copy F2 are arranged side by side in the longitudinal direction LD of document F. In this embodiment, the copy F2 includes a delivery note F2A, which is kept by a financial institution or the like after payment of the fee, and a delivery notice F2B, which is sent to the local government that issued document F after payment of the fee.

[0026] The front FA of each of the receipt F1, delivery note F2A, and delivery notice F2B is pre-printed with the respective title T, information J regarding the amount of the fee to be paid (i.e., the payment amount), and a frame-shaped seal field R. Note that information J is not limited to letters and numbers, but also includes various symbols such as codes designed to be read at convenience stores (two-dimensional codes such as barcodes). Information J includes at least payment amount information J1 regarding the amount to be paid and payment deadline information J2, i.e., the deadline for payment of the fee. Furthermore, although not shown, information J further includes the user's personal information (such as name and phone number) and identification information for identifying each document F.

[0027] As shown in FIG. 1, when the document F arrives at the user, the receipt F1 and copy F2 are integrated together. The document F has a boundary line L1 (see dashed line) between the receipt F1 and copy F2. The copy 2F has a boundary line L2 (see dashed line) between the delivery note F2A and the delivery notice F2B. The boundary lines L1 and L2 each extend linearly along the short-edge direction SD, which is perpendicular to the long-edge direction LD, of the document F, and cross the document F. The boundary lines L1 and L2 are straight lines printed on the document F in advance. In this embodiment, the boundary line L1 has a perforation M that extends linearly on the boundary line L1 along the short-edge direction SD.

[0028] When a user brings slip F to a manned counter at a financial institution, the counter clerk will tell the user the amount to be paid based on the payment amount information J1 listed on slip F. If the payment deadline listed in information J2 on slip F has passed by the day the user visits the financial institution, late fees may have been incurred. Also, if the issuer of slip F has already sent a reminder to the user, a reminder fee may have been incurred in addition to the late fees. The counter clerk will then check the additional amounts, such as the late payment amount and reminder fee, and will tell the user the total amount of the fee to be paid, calculated by adding the additional amounts to the payment amount listed in payment amount information J1. The user will then settle the fee by paying the amount notified by the clerk in cash or by credit card.

[0029] Once the payment is complete, the clerk enters receipt stamp A, which serves as proof of payment completion, in each stamp column R on document F, as shown in Figure 2. The clerk then separates document F into receipt F1 and copy F2. When the clerk hands receipt F1 to the user, the transaction between the user and the clerk regarding the payment of the fee is complete. In other words, the transaction is not complete just because the payment has been completed; the entire transaction is completed when receipt F1 with receipt stamp A is handed to the user after the payment has been completed.

[0030] Receipt F2 is temporarily collected by the financial institution, and then separated into invoice F2A and invoice notice F2B, which are then mailed to their respective destinations. When separating invoice F2A and invoice notice F2B, boundary line L2 may be cut with scissors or the like, or perforation M may be provided in boundary line L2 in advance, and invoice F2A and invoice notice F2B may be separated at perforation M in the same manner as boundary line L1.

[0031] 3 is a schematic diagram showing an overview of a document management system 100 according to one embodiment of the present invention. The document management system 100 includes a document transaction device 1 installed in, for example, an ATM (Automated Teller Machine) corner in a building of a financial institution, a relay device 101 installed in, for example, a backyard or the like in the building of the financial institution, and a counter terminal 102 installed at a counter of the financial institution.

[0032] The document transaction device 1 and the counter terminal 102 are communicatively connected via a LAN (Local Area Network) 103 consisting of wired or wireless communication lines. The LAN 103 is connected to a public line 104 such as the Internet. The relay device 101 is communicatively connected to each of the document transaction device 1 and the counter terminal 102 via the LAN 103 and the public line 104, or via only the LAN 103. The relay device 101 may be part of the document transaction device 1 or the counter terminal 102, or may be installed in a separate location away from the financial institution.

[0033] The document transaction device 1 is an automated transaction device that performs transactions between a user and a clerk using document F, as described above. In this embodiment, the document transaction device 1 is a tax and public money processing machine for taxes and utility bills. The payment amount information J1 written on document F is an example of essential data for the transaction. The relay device 101 is a server that stores transaction information for transactions completed by the document transaction device 1 as a transaction history. The counter terminal 102 is a personal computer operated by a counter clerk. In relation to the document management system 100, a card settlement server 105, a management device 106, and a dictionary server 107 are installed outside the financial institution building and are connected to a public line 104. The card settlement server 105 may be owned by a credit card company or a manufacturer of the tax and public money processing machine. The management device 106 is a server owned by the issuer of document F (a local government in this embodiment). The number of issuers is not limited to one, and therefore there may be multiple management devices 106, but the following description focuses on one issuer and one management device 106 owned by this issuer. The dictionary server 107 is owned by an organization (such as a dictionary distribution center) that manages the format data of form F.

[0034] 4 is a perspective view of a document transaction device 1 according to one embodiment of the present invention. The document transaction device 1 includes a vertically long, box-shaped device main body 2. On the front surface 3, which is the side surface on the front side of the device main body 2, an upper area 3A is shifted one step rearward from a lower area 3B, thereby forming a horizontally extending boundary area 3C between the upper area 3A and the lower area 3B.

[0035] The upper portion of the upper area 3A is provided with a display / operation unit 4, which is configured, for example, as a touch-panel LCD monitor. The display / operation unit 4 functions as an example of an acquisition unit and an operation unit. A recess 3D is formed in the area of ​​the upper area 3A to the right of the display / operation unit 4, recessing toward the rear. The recess 3D houses a receipt outlet 5 and a card slot 6, each with a long, narrow slit running from side to side, and an input unit 7, such as a PIN pad, arranged vertically. The upper area 3A is provided below the display / operation unit 4 with a take-in / out opening 8, which is configured with a long, narrow slit running from side to side, and a plate-like tray 9 that protrudes horizontally forward, framing the bottom end of the take-in / out opening 8.

[0036] In an upper portion of the lower region 3B of the front surface 3, for example in an area closer to the right, a banknote insertion slot 10 and a banknote withdrawal slot 11, each shaped like a narrow slit extending from left to right, are provided side by side, one above the other. The banknote insertion slot 10 and the banknote withdrawal slot 11 are opened and closed together by a shutter 12 bent into a substantially L-shape across the lower region 3B and the boundary region 3C. A coin withdrawal slot 13 is provided in an area to the left of the banknote insertion slot 10 and the banknote withdrawal slot 11 in the upper portion of the lower region 3B, and a coin insertion slot 14 is provided in the boundary region 3C at the same position as the coin withdrawal slot 13 in the left-right direction. The coin withdrawal slot 13 and the coin insertion slot 14 are opened and closed together by a shutter 15 bent into a substantially L-shape like the shutter 12. The shutter 12 may be divided into a shutter that opens and closes only the banknote insertion slot 10 and a shutter that opens and closes only the banknote withdrawal slot 11. Similarly, the shutter 15 may be divided into a shutter that opens and closes only the coin dispensing opening 13 and a shutter that opens and closes only the coin insertion opening 14.

[0037] The positions of the display operation unit 4, receipt outlet 5, card slot 6, input unit 7, take-in / take-out port 8, banknote insertion slot 10, banknote withdrawal slot 11, coin withdrawal slot 13, and coin insertion slot 14 can be changed as desired as long as they are easily accessible to users. Also, the banknote insertion slot 10 and the banknote withdrawal slot 11 may be combined into a banknote insertion / withdrawal slot, and the coin withdrawal slot 13 and the coin insertion slot 14 may be combined into a coin insertion / withdrawal slot.

[0038] Transactions that can be performed with the document transaction device 1 include a first transaction, which is an automatic transaction using a document F, and a second transaction, which is a different transaction from the first transaction and does not require the use of a document F. Briefly describing the first transaction, a user first stands in front of the document transaction device 1. The user then places a document F, which is horizontally positioned longitudinally in the front-to-back direction of the document transaction device 1 and has its front surface FA facing upward, on the tray 9 with the receipt F1 at the end and the copy F2 at the front, and inserts the document F into the input / output port 8. This causes the document F to be taken into the device main body 2 through the input / output port 8. The document transaction device 1 then reads the image data of the document F, and the payment amount information J1 (see FIG. 1, etc.) included in this image data is displayed on the display operation unit 4 as the payment amount.

[0039] A user who wishes to pay in cash inserts cash into the open banknote slot 10 or coin slot 14. A user who wishes to pay by credit card inserts their credit card into the card slot 6 and then enters a PIN number and other information using the input unit 7. Note that while the payment methods in this embodiment are cash payment and credit card payment, another example of a payment method is account payment, in which money is transferred from the user's account to the payee. In this case, the user inserts their cash card into the card slot 6 and then enters a PIN number and other information using the input unit 7.

[0040] When the above settlement is completed, receipt stamps A are entered in each stamp column R on the document F within the document transaction device 1, and the document F is cut along perforations M to separate it into receipt F1 and copy F2 (see FIG. 2). Copy F2 is collected within the document transaction device 1, and receipt F1 is ejected from the device main body 2 through the inlet / outlet 8 and returned to the user. If change is required for cash settlement, the change is returned to the user through the banknote outlet 11 or coin outlet 13. A receipt showing the details of this transaction is also issued from the receipt outlet 5. In this way, the first transaction is a transaction in which the settlement, the entry of receipt stamps A on document F, separation of document F, and return of receipt F1 to the user are completed within the document transaction device 1.

[0041] On the other hand, the second transaction is a transaction in which, for document F that is not handled by the document transaction device 1, the user manually inputs the payment amount (payment amount information J1 written on document F) using the display operation unit 4, and the payment amount is settled by the document transaction device 1, and the counter clerk then enters receipt stamp A on document F, separates document F, and returns receipt F1 to the user.

[0042] As described above, the first transaction is a transaction based on payment amount information J1 contained in image data read from form F, and the second transaction is a transaction based on payment amount information J1 manually input by the user through operation of display operation unit 4. Hereinafter, the first transaction may be referred to as a "normal transaction," and the second transaction may be referred to as a "manually input transaction." The first and second transactions will be described in detail later.

[0043] Next, the main parts of the document transaction device 1 will be described. Figure 5 is a schematic diagram of the internal structure of the upper part of the document transaction device 1 as seen from the right side. The left side of Figure 5 is the front side of the document transaction device 1, the right side of Figure 5 is the rear side of the document transaction device 1, and the direction perpendicular to the plane of Figure 5 is the left-right direction of the document transaction device 1. In the following, the front-rear, left-right, and up-down directions of the document transaction device 1 will be used for the explanation. For ease of explanation, the receipt outlet 5, card slot 6, input unit 7, etc. described in Figure 4 are omitted from Figure 5. A document processing unit 20, an example of a processing unit, is provided in the upper part of the device body 2 of the document transaction device 1.

[0044] In relation to the document processing unit 20, a transport path 21 for transporting a document F inserted into the intake / discharge opening 8 is provided within the device body 2. The transport path 21 is a space that extends along the trajectory of the document F being transported within the device body 2. The width direction of the transport path 21 coincides with the left-right direction. The transport path 21 includes a first transport path 21A that extends horizontally rearward from the intake / discharge opening 8 to just before the rear surface 22 of the device body 2, a second transport path 21B that curves from the rear end of the first transport path 21A and then extends downward, and a third transport path 21C that curves from the bottom end of the second transport path 21B and then extends forward.

[0045] A form F inserted into the intake / discharge opening 8 and taken into the conveyance path 21 is conveyed in this order by the first conveyance path 21A, the second conveyance path 21B, and the third conveyance path 21C. Therefore, in the conveyance direction of the form F (hereinafter simply referred to as the "conveyance direction"), the first conveyance path 21A is located upstream and close to the intake / discharge opening 8, and the third conveyance path 21C is located downstream and away from the intake / discharge opening 8. The form F conveyed in the conveyance path 21 normally moves along the front-to-rear direction while maintaining a posture in which two sides of the form F (the two upper and lower sides shown in FIG. 1) are aligned with the front-to-rear direction. The form processing unit 20 includes a conveyance section 25, a collection section 26, an intake / discharge section 27, a separation section 28, a reading section 29 as an example of an acquisition section, an alignment section 31, a writing section 33, and a detection section 34.

[0046] The conveying unit 25 includes a plurality of conveying rollers 40 distributed throughout the conveying path 21. Each conveying roller 40 is a cylindrical body elongated in the left-right direction. The conveying unit 24 also includes a motor (not shown) for rotating the conveying rollers 40 forward and backward. A conveying roller 40 rotating forward conveys a form F in contact with its outer circumferential surface downstream in the conveying direction within the conveying path 21. A conveying roller 40 rotating backward conveys a form F in contact with its outer circumferential surface upstream in the conveying direction within the conveying path 21. The conveying rollers 40 may be arranged opposite each other in pairs and in contact with each other within the conveying path 21. The two conveying rollers 40 in a pair rotate in opposite directions while sandwiching the form F between them, thereby conveying the form F upstream or downstream within the conveying path 21. Note that other rollers (except for the correction roller 47) described below are configured similarly to the conveying roller 40.

[0047] The collection unit 26 is a space reserved within the device body 2 for storing copies F2 (see FIG. 2) of the separated forms F. The collection unit 26 is connected to the downstream end of the third conveying path 21C in the conveying direction, i.e., the front end of the third conveying path 21C. The collection unit 26 may be detachable from the device body 2 so that the copies F2 stored in the collection unit 26 can be removed. Alternatively, the collection unit 26 may be accessible from outside the device body 2 by opening a door (not shown) provided on the surface of the device body 2.

[0048] The intake / discharge unit 27 is configured to take in a form F inserted into the intake / discharge opening 8 into the first conveying path 21A, and to discharge all or part of the form F in the first conveying path 21A to the intake / discharge opening 8. The intake / discharge unit 27 includes at least a pair of intake / discharge rollers 41 arranged to sandwich from above and below the front end of the first conveying path 21A adjacent to the intake / discharge opening 8, and a motor (not shown) that rotates these intake / discharge rollers 41 forward and reverse.

[0049] Separation unit 28 is configured to separate forms F at perforations M, and is disposed downstream in the conveying direction, i.e., rearward, of first conveying path 21A from intake / discharge unit 27. Separation unit 28 includes a cutting member 42, an actuator 43, a first roller 44 and a second roller 45, and a motor (not shown) that rotates first roller 44 and second roller 45 forward and reverse.

[0050] The cutting member 42 is a cutter made of metal or resin, and the blade length direction of the cutting edge 42A extends in the left-right direction. The cutting member 42 is movable in a movement direction (vertical direction in FIG. 5) that intersects or is perpendicular to the first conveying path 21A so that the cutting edge 42A can cross the first conveying path 21A. As shown in FIG. 5, the cutting member 42 in the standby position is separated from the first conveying path 21A to one side in the movement direction (upward in FIG. 5). The actuator 43 is constituted by, for example, a motor, and moves the cutting member 42 along the movement direction.

[0051] At least one pair of first rollers 44 and second rollers 45 are provided along first conveying path 21A. The two first rollers 44 in each pair are arranged opposite each other so as to come into contact with each other within first conveying path 21A, and the two second rollers 45 in each pair are arranged opposite each other so as to come into contact with each other within first conveying path 21A. Note that multiple first rollers 44 and multiple second rollers 45 may be arranged side by side in the left-right direction so as to overlap when viewed from the left-right direction. The first roller 44 is located upstream of the second roller 45 in the conveying direction, and the cutting member 42 is located between the first roller 44 and the second roller 45 in the conveying direction.

[0052] The reading unit 29 is disposed on the first conveying path 21A downstream of the separating unit 28 in the conveying direction, and crosses the first conveying path 21A in the left-right direction. The reading unit 29 optically reads the image on the front side of the form F from above to obtain image data of the form F, and is configured, for example, by a line sensor such as a CIS (Contact Image Sensor).

[0053] The alignment unit 31 is configured to correct the posture of the document F to eliminate skew, i.e., correct skew, and is arranged around the separation unit 28 in the conveying direction on the first conveying path 21A. The alignment unit 31 includes a positioning unit 46, a correction roller 47, and a motor (not shown) that rotates the correction roller 47.

[0054] The positioning unit 46 is formed in the shape of a block that is long in the front-rear direction. The side of the positioning unit 46 that faces the first conveying path 21A is a flat abutment surface that is aligned with the traveling direction of the form F in the first conveying path 21A. The correction roller 47 is disposed at the same position as the positioning unit 46 in the front-rear direction and faces the first conveying path 21A. Unlike the other rollers, the correction roller 47 rotates around a rotation axis (not shown) that extends in the front-rear direction. The form F being conveyed in the first conveying path 21A comes into contact with the rotating correction roller 47 and is brought to the abutment surface of the positioning unit 46. There are cases where the form F is conveyed at an angle to the traveling direction, and by bringing this form F into abutment with the abutment surface, the form F is prevented from moving. F's posture is corrected and the tilted position is eliminated.

[0055] The writing unit 33 is disposed downstream of the reading unit 29 in the first conveying path 21A in the conveying direction, i.e., at the rear end of the first conveying path 21A, facing the first conveying path 21A from above. A stamping unit 33A is provided on the lower end surface of the writing unit 33 for writing a receipt stamp A (see FIG. 2) in each stamp field R on the form F. A pattern matching a reversed version of the receipt stamp A is engraved on the stamping unit 33A. The stamping unit 33A may consist of only this pattern, or part or all of the stamping unit 33A may be formed by a print head (not shown) such as a dot impact printer. In this case, the entire receipt stamp A and the payment date portion of the receipt stamp A are reproduced by the print head and printed on the form F. The writing unit 33 may also be capable of writing information other than the receipt stamp A on the form F. The form processing unit 20 also includes a drive unit (not shown) such as an actuator that raises and lowers the writing unit 33.

[0056] As an example, the detection unit 34 is disposed between the reading unit 29 and the entry unit 33 in the conveyance direction. The detection unit 34 is, for example, a photointerrupter, and includes a light-emitting element 34A and a light-receiving element 34B disposed above and below the first conveyance path 21A. When no form F is present between the light-emitting element 34A and the light-receiving element 34B, detection light (not shown) emitted by the light-emitting element 34A is received by the light-receiving element 34B. When a form F is present between the light-emitting element 34A and the light-receiving element 34B, the detection light is blocked by the form F. When the form F passes between the light-emitting element 34A and the light-receiving element 34B, the detection light is again received by the light-receiving element 34B. The detection unit 34 detects the passage of the form F between the light-emitting element 34A and the light-receiving element 34B by this blocking or reception of the detection light.

[0057] FIG. 6 is a block diagram showing the electrical configuration of the document management system 100. In addition to the document processing unit 20, the device main body 2 of the document transaction device 1 is provided with a receipt printing unit 51, a card processing unit 52, and a cash processing unit 53. The receipt printing unit 51 is a printer or the like that prints receipts, and a laser printer or thermal printer can be used as the receipt printing unit 51. The receipt printing unit 51 prints receipts and ejects them through the receipt outlet 5. For credit card payments, the card processing unit 52 reads necessary information from a credit card inserted into the card slot 6 and ejects the credit card from the card slot 6 in response to the cancellation or completion of a transaction. For cash payments, the cash processing unit 53 counts and stores cash inserted into the banknote slot 10 or coin slot 14, calculates change, and dispenses cash for return, such as change, through the banknote outlet 11 or coin outlet 13.

[0058] The document transaction device 1 includes a control unit 54, which is an example of a transaction unit, acquisition unit, generation unit, output unit, processing unit, and creation unit. The control unit 54 is configured by a microcomputer including a CPU, ROM, RAM, timer, etc. The display operation unit 4, input unit 7, document processing unit 20, receipt printing unit 51, card processing unit 52, and cash processing unit 53 are electrically connected to the control unit 54. The control unit 54 controls the content displayed on the display operation unit 4 and accepts operations by users on the touch panel of the display operation unit 4 and the input unit 7. The control unit 54 causes the document processing unit 20, receipt printing unit 51, card processing unit 52, and cash processing unit 53 to execute their respective processes for transactions. In particular, the control unit 54 and the reading unit 29 of the document processing unit 20 form an OCR (Optical Character Reader).

[0059] The document transaction device 1 further includes, as other components electrically connected to the control unit 54, a shutter actuator 55, an interface (I / F) unit 56 as an example of an output unit, and a memory unit 57 as an example of a first memory unit. The control unit 54 opens and closes the shutters 12 and 15 by operating the shutter actuator 55. The I / F unit 56 is connected to the above-mentioned LAN 103, and the control unit 54 can communicate with the relay device 101, the counter terminal 102, etc. via the I / F unit 56.

[0060] The memory unit 57 stores various information, and in particular, information for identifying the type of form F to be handled by the form transaction device 1 is compiled and stored in advance for each type of form F. Specifically, the memory unit 57 stores dictionary data 57A that is referenced when the control unit 54 performs OCR processing on image data acquired by the reading unit 29. The dictionary data 57A includes format data for the format of each type of form F. Multiple format data are provided according to the type of form F to be handled. Examples of format data include the shape and size of the corresponding type of form F, the position of letters, numbers, etc., and the type of letters and numbers.

[0061] The form data also includes external identification information such as the size of the corresponding type of form F and the characteristic pattern of its lines, position information of the seal area R on the form F, the presence or absence of perforations M, and information on the separation position on the form F. Dictionary data 57A including such form data is data that serves as a reference when identifying the type of form F from various information included in the image data of the form F. Various form data are registered in the dictionary server 107. The control unit 54 can communicate with the dictionary server 107 via the I / F unit 56, obtain the latest form data stored in the dictionary server 107, and update the dictionary data 57A.

[0062] A form F for which corresponding format data exists in the dictionary data 57A is a form F that can be handled by the form transaction device 1, and a form F for which corresponding format data is not registered in the dictionary data 57A is a form F that cannot be handled by the form transaction device 1. Examples of forms F that cannot be handled include forms F on which some information, such as payment amount information J1, is handwritten.

[0063] The relay device 101 further includes a control unit 110 configured by a microcomputer, an I / F unit 111 connected to the public line 104, and a storage unit 112 as an example of a second storage unit. The control unit 110 and the I / F unit 111 function as an example of a receiving unit and a transmitting unit. The control unit 110 is electrically connected to the I / F unit 111 and the storage unit 112.

[0064] The management device 106 further includes a control unit 115 configured by a microcomputer, an I / F unit 116 connected to the public line 104, and a memory unit 117. The control unit 115 functions as an example of a flag change unit, an input unit, and a clearing unit, and the I / F unit 116 functions as an example of an input unit. The control unit 115 is electrically connected to the I / F unit 116 and the memory unit 117. The management device 106 can be considered to be a part of the document management system 100.

[0065] The memory unit 117 stores a list of forms F issued by the issuer (local government) that owns the management device 106, for example, as table 118 in Fig. 7. In other words, the management device 106 manages the list of issued forms F. For each issued but unpaid form F, table 118 stores various form information such as the issue date, issuer, type of fee to be paid, identification information assigned to each form F, personal information of the billing destination (i.e., the user), fee, and payment deadline. The issuer information may also include information about the recipient, i.e., each department to which the fee is paid (e.g., the water department at a city hall).

[0066] The processing performed in the document transaction device 1 during a transaction will be described mainly with reference to the flowcharts in Figures 8 and 9. In the standby state, the display operation unit 4 of the document transaction device 1 displays a standby screen 61 shown in Figure 10. The standby screen 61 displays a guide message 61A, as well as touch keys such as a transaction start key 62, a manual input transaction selection key 63, and an attendant call key 64. Note that all of the following names ending in "key" are touch keys.

[0067] A user who comes to a financial institution with document F (or a financial institution clerk at the user's request) touches the transaction start key 62 on the standby screen 61. The control unit 54 of the document transaction device 1 then accepts that a regular transaction has been selected. On the other hand, when the manual input transaction selection key 63 is touched, the control unit 54 accepts that a manual input transaction has been selected. In this way, by touching either the transaction start key 62 or the manual input transaction selection key 63 on the display operation unit 4, it is possible to select either a regular transaction or a manual input transaction. When the clerk call key 64 is touched, the control unit 54 calls a clerk, for example, by sounding a buzzer (not shown) provided on the document transaction device 1.

[0068] When a normal transaction is selected by touching the transaction start key 62 (step S1), the control unit 54 takes in the user's document F (step S2). Specifically, in response to touching the transaction start key 62, the control unit 54 first switches the display operation unit 4 to display a start screen 65 shown in Fig. 11. Note that a warning screen (not shown) may be displayed between the standby screen 61 and the start screen 65, warning the user not to insert documents F that are easily torn.

[0069] The start screen 65 displays an attendant call key 64, a guide 65A encouraging the user to insert a document F, and a cancel key 66 that can be touched to cancel the current transaction. The start screen 65 may also display an illustration showing the position in the document transaction device 1 where the document F should be inserted. After viewing the guide 65A, the user inserts the document F, with its front surface FA facing upward, into the intake / discharge slot 8 with the copy F2 at the front. When the leading end of the document F on the copy F2 side is pinched between the pair of intake / discharge rollers 41, the control unit 54 rotates the intake / discharge rollers 41 and the transport rollers 40 in the forward direction, thereby taking the document F from the intake / discharge slot 8 into the first transport path 21A inside the device main body 2 (step S2). As a result, the document F is transported rearward within the first transport path 21A with the copy F2 at the front while maintaining a longitudinal and horizontal orientation, and passes through the reading unit 29.

[0070] When the document F passes through the reading unit 29, the control unit 54 reads the image data of the front side FA of the document F using the reading unit 29 (step S3). In step S3, the control unit 54 performs OCR processing by comparing the image data of the front side FA read from the document F with dictionary data 57A in the memory unit 57, thereby identifying the type of document F corresponding to the image data. A document F whose type has been identified by the control unit 54 is a document F that can be accepted by the document transaction device 1. Furthermore, the control unit 54 performs OCR processing by identifying characters and numbers contained in the image data, thereby acquiring payment amount information J1, etc. from the image data. The image data and the information contained in the image data (i.e., the information written on the document F) are an example of transaction data related to the current transaction.

[0071] A form F whose type cannot be identified by the control unit 54 is a non-target form F that cannot be accepted by the form transaction device 1. When the control unit 54 cannot identify the type of form F (NO in step S4), it returns the form F from the intake / ejection port 8 by reversing the conveyance rollers 40 and the intake / ejection rollers 41 (step S5). Note that the intake / ejection port 8 may be divided into an intake port for taking in the form F and an ejection port for ejecting the form F.

[0072] If the control unit 54 can identify the type of document F (YES in step S4), it temporarily holds this acceptable document F in the transport path 21 and switches the display operation unit 4 to display a confirmation screen 67 shown in FIG. 12 (step S6). The confirmation screen 67 displays an attendant call key 64 and a cancel key 66, as well as a message 67A urging the user to confirm the payment details, a payment amount display field 67B, a payment slip display key 68, and a confirmation key 69. The control unit 54 displays the payment amount in the payment amount information J1 read from the document F in step S3 in the payment amount display field 67B. When the payment slip display key 68 is touched by the user, the control unit 54 causes the display operation unit 4 to display the image data of the front side FA of the document F read in step S3.

[0073] When the user touches the confirmation key 69 after confirming the payment amount, the control unit 54 switches the display operation unit 4 to display the input screen 70 shown in FIG. 13 and accepts the input of personal information for identifying the user (step S7). The input screen 70 displays the attendant call key 64 and the cancel key 66, as well as a message 70A prompting the user to input personal information, a personal information display field 70B, an input key 71, a delete key 72, and a continue key 73. In this embodiment, the personal information is the user's telephone number, for example, and the input keys 71 are accordingly numeric keys. The user inputs their own telephone number by operating the input keys 71. The control unit 54 displays the telephone number entered by the user in the personal information display field 70B. If the user inputs an incorrect telephone number, the user can touch the delete key 72 to delete the input and re-enter the telephone number. The input screen 70 may also allow the user to input other personal information, such as the user's name (e.g., entering the user's name in kana). In this case, the input keys 71 are configured as a keyboard.

[0074] When the user who has input the personal information touches the continue key 73, the control unit 54 performs the payment by cash payment or credit card payment as described above (transaction step, step S8). Therefore, the control unit 54 switches the display operation unit 4 to display a payment method selection screen (not shown), and accepts the user's selection of the payment method on the payment method selection screen.

[0075] When cash payment is selected, the control unit 54 switches to display a cash payment screen 74 shown in Fig. 14 on the display operation unit 4. The cash payment screen 74 displays an attendant call key 64 and a cancel key 66, as well as a message 74A encouraging the user to make a deposit, a payment amount display field 74B, a deposit amount display field 74C, a change amount display field 74D, and a completion key 75. The cash payment screen 74 may also display an illustration indicating the position in the document transaction device 1 where cash should be inserted.

[0076] The control unit 54 displays the payment amount in the payment amount information J1 read from the document F in step S3 in the payment amount display field 74B. The control unit 54 displays the total amount of cash inserted by the user into the banknote insertion slot 10 and the coin insertion slot 14 as the deposit amount in the deposit amount display field 74C. If the deposit amount is more than the payment amount, the control unit 54 displays the difference as the change amount in the change amount display field 74D. When the user touches the completion key 75 when the deposit amount is equal to or greater than the payment amount, the payment is completed. Thus, in step S8, the control unit 54 accepts payment based on the payment amount information J1 included in the image data acquired from the document F by the reading unit 29 in step S3 as payment for a normal transaction (transaction step).

[0077] When credit card payment is selected, the control unit 54 switches the display operation unit 4 to display a credit card payment screen 76 shown in FIG. 15. The credit card payment screen 76 displays an attendant call key 64 and a cancel key 66, as well as a guide 76A urging the user to insert a credit card into the card slot 6 and enter a PIN, a PIN display field 76B, an input key 77, a delete key 78, and a continue key 79. In this embodiment, the input keys 77 are numeric keys. The user enters a PIN by operating the input keys 77. The control unit 54 displays the PIN entered by the user (more specifically, a black circle indicating the input of a PIN) in the PIN display field 76B. If the user enters an incorrect PIN, the user can touch the delete key 78 to delete the input and re-enter the PIN.

[0078] When a user inserts a credit card into card slot 6, enters a personal identification number, and then touches continue key 79, control unit 54 communicates with external card settlement server 105 (see FIG. 3) via I / F unit 56. At that time, control unit 54 performs credit card settlement based on information read from the credit card by card processing unit 52 (transaction step).

[0079] After the cash or credit card payment is completed, the control unit 54 processes the form F that has been temporarily held in the conveyance path 21 (hereinafter referred to as "form processing") (transaction step, step S9). Form processing is part of a normal transaction, and in this embodiment, it includes both writing a receipt stamp A on the form F and cutting the form F, but either one of these steps may be performed. Specifically, the control unit 54 reverses the conveyance rollers 40 to convey the form F toward the intake / discharge opening 8, and at that time, corrects the posture of the form F using the alignment unit 31. Then, the control unit 54 adjusts the position of the form F in the conveyance direction within the first conveyance path 21A using the conveyance unit 25, and then lowers the marking unit 33 to bring the stamping unit 33A of the marking unit 33 into contact with the front surface FA of the form F, and marks the receipt stamp A in the appropriate location on the front surface FA. Thereafter, the control unit 54 causes the conveying unit 25 to convey the stamped form F until the perforation M of the form F reaches directly below the cutting member 42 of the separation unit 28. The control unit 54 then lowers the cutting member 42, which is in the standby position, to at least the perforation M to separate the form F. The time required to write the receipt stamp A and cut the form F (i.e., the time required for form processing) is 20 to 40 seconds, depending on the length of the form F.

[0080] In step S9, the control unit 54 also generates an archive file for this transaction. The archive file is a file containing data for the issuer of the form F, and its format is, for example, CSV. The data for the issuer includes at least detailed data for this transaction. The breakdown of the detailed data is made up of, for example, the following items (1) to (17). Item (1) Name of the financial institution where the document transaction device 1 is installed and its identification information (branch number) Item (2) Machine number, which is the identification information of the document transaction device 1 Item (3) Processing date and time, which is the date and time when this transaction was made Item (4) Customer processing serial number assigned to the customer Item (5) Personal information entered by the user in step S7 (telephone number, name in kana, etc.) Item (6) Type of transaction (regular transaction or manual transaction) Item (7) Payment method for this fee (cash or credit card) Item (8) Date of receipt stamp A entered on Form F Item (9) Card slip number to be attached to the receipt issued later in the case of credit card payment Item (10) Processing sequence number assigned to each document F traded on the same business day Item (11) File name of the archive file to be generated Item (12) Payment due date as stated on Form F Item (13) Total and breakdown of charges listed on Form F Item (14) The issuer of document F (e.g., city hall) Item (15) Details of the issuer of Form F, namely, the recipient (e.g., the waterworks bureau at a city hall) Item (16) Type of charge (e.g., water charge) Item (17) Identification information for identifying individual forms F

[0081] Items (1) and (2) are pre-stored in the memory unit 57 of the document transaction device 1. Items (3) to (11) are acquired or assigned by the control unit 54 during the transaction. Items (12), (13), and (17) are acquired by the control unit 54 through OCR processing in step S3. Note that, with regard to the breakdown of the fee in item (13), if any additional amounts (late fees or dunning fees) have been incurred, the breakdown includes the additional amounts and the payment amount, and the total of these is the fee. If any additional amounts have been incurred when document F is issued, information about the additional amounts is recorded on document F. Items (14) to (16) are, for example, pre-recorded on document F and acquired by the control unit 54 through OCR processing in step S3. If the aforementioned barcode is recorded on document F, item (17) is information about the barcode.

[0082] These items (1) to (17) are an example of transaction data related to the current transaction. The control unit 54 generates data for the issuer based on this transaction data and stores it as an archive file in a temporary storage folder 57B (see FIG. 6) in the storage unit 57. The folder name of the temporary storage folder 57B is set to a name including the current date, and archive files for all transactions performed today are accumulated in the temporary storage folder 57B. Note that when generating the data for the issuer, not all of the items (1) to (17) are required as detailed data; they may be selected as appropriate. Furthermore, multiple temporary storage folders 57B may exist depending on the number of issuers. Furthermore, if the total fee (hereinafter referred to as the "transaction amount") is equal to or greater than a predetermined amount (e.g., 10,000 yen), the control unit 54 also includes the image data of the form F acquired in step S3 in the data for issuance. In this case, the image data may be in the form of, for example, encrypted JPEG. Note that image data of the form F may be acquired at a timing after the receipt stamp A is entered on the form F (that is, at a timing different from step S3), and this image data may be included in the data for issuance.

[0083] In step S9, the control unit 54 of the document transaction device 1 outputs the archive file generated for this transaction to the outside from the I / F unit 56. That is, in the case of a normal transaction, the control unit 54 outputs the archive file to the outside in parallel with the document processing timing of entering a receipt stamp A on the document F and cutting the document F in step S9. As described above, depending on whether the transaction amount is equal to or greater than a predetermined amount, the control unit 54 determines whether to output image data as part of the archive file. Because image data is large in volume and therefore imposes a heavy communication load, an archive file containing image data is output to the outside only if the transaction amount is equal to or greater than a predetermined amount. Note that, for example, if a storage period for the archive file is stipulated by law or the like, the archive file is output to the outside together with information regarding this storage period. The storage period may be changed depending on the transaction amount. For example, if the transaction amount is 10,000 yen or more, the storage period is set to seven years, and if the transaction amount is less than 10,000 yen, the storage period is set to any period less than seven years.

[0084] The external output destination of the archive file is the relay device 101. The control unit 110 of the relay device 101 receives the externally output archive file at the I / F unit 111 and stores it in the storage unit 112 (see FIG. 6). Specifically, individual folders 112A are provided in the storage unit 112, each of which has a folder name that combines the name and branch number of the financial institution (item (1) described above) and the machine number at which the transaction was performed (item (2) described above). Under each individual folder 112A, date folders 112B are provided, each of which has a folder name that is the date, similar to the temporary storage folder 57B (see FIG. 6). Within each individual folder 112A, multiple date folders 112B with different dates in their folder names are provided. There are multiple individual folders 112A depending on the number of branches of the financial institution, the number of document transaction devices 1, etc. The control unit 110 identifies an individual folder 112A based on the name and store number of item (1) and the unit number of item (2) contained in the archive file, and stores the archive file in a date folder 112B within this individual folder 112A that has the same date and time as the processing date and time of the archive file (item (3) mentioned above).

[0085] Sending and receiving of archive files between the document transaction device 1 and the relay device 101 is performed by mirroring (synchronizing) between the temporary storage folder 57B of the document transaction device 1 and the corresponding date folder 112B of the relay device 101. The mirroring is performed by cooperation between the control unit 54 of the document transaction device 1 and the control unit 110 of the relay device 101. As an example of the mirroring, data that exists in the temporary storage folder 57B but does not exist in the date folder 112B is added to the date folder 112B. Furthermore, data that does not exist in the temporary storage folder 57B but exists in the date folder 112B is deleted from the date folder 112B.

[0086] The control unit 110 of the relay device 101 relays the archive file externally output from the document transaction device 1 to the I / F unit 116 by transmitting the archive file stored in the date folder 112B of the memory unit 112 from the I / F unit 111 to the I / F unit 116 of the management device 106 (see FIG. 6). The transmission of the archive file from the relay device 101 to the management device 106 may be performed sequentially each time the relay device 101 receives an archive file from the document transaction device 1, or multiple archive files may be temporarily stored in the date folder 112B and then transmitted collectively at a predetermined timing. Note that when the storage period of the archive file has elapsed, the control unit 110 sequentially deletes the archive file from the memory unit 112. In this case, the corresponding date folder 112B may be deleted as well.

[0087] The control unit 115 of the management device 106 automatically deletes the data of the currently transacted form F from the table 118 of the storage unit 117 based on the issuer-oriented data in the archive file input to the I / F unit 116 (see FIGS. 6 and 7). Specifically, the control unit 115 identifies the transacted form F linked to the same information in table 118 based on the personal information (item (5) described above) and the identification information of form F (item (17) described above) contained in the issuer-oriented data. The control unit 115 then determines that the fee for this form F has been paid, and deletes the data of this form F from table 118 (all the data in the horizontal column in FIG. 7). Note that, instead of deleting the data of this form F from table 118, it is also possible to register a flag indicating whether payment has been made (transaction flag) in table 118 and change this flag (transaction flag) from "unpaid" (first information) to "paid" (second information) (flag change step). In this case, the data of form F for which the fee has already been paid will also remain in table 118.

[0088] In this way, the data for the issuer is deletion data for deleting the data of the paid form F from table 118. Note that the deletion of the data of the paid form F in table 118 does not have to be performed automatically, but may be performed in response to a check and deletion instruction by an attendant. In this case, a monitor (not shown) is provided in the management device 106, and the data for the issuer in the archive file and the data of the corresponding form F in table 118 are displayed side by side on the monitor, allowing the attendant to check by comparing these data. Note that it is preferable that the data in the archive file is not compressed so that it can be viewed immediately.

[0089] When the control unit 54 of the document transaction device 1 outputs the archive file in step S9, the control unit 110 of the relay device 101, which is the external output destination, transmits a success notification to the document transaction device 1 indicating that the external output was successful in response to the completion of storing the archive file in the date folder 112B of the storage unit 112. If the control unit 54 receives the success notification from the relay device 101 within a predetermined time after the archive file is externally output, the control unit 54 determines that the external output of the archive file was successful. The predetermined time is set to a value (e.g., 20 seconds) that does not exceed the time required for the document processing (applying receipt stamp A and cutting document F) in step S9 (the aforementioned 20 to 40 seconds). On the other hand, if the predetermined time has timed out, i.e., if the control unit 54 does not receive a success notification from the relay device 101 even after the predetermined time has elapsed since the archive file was externally output, the control unit 54 determines that the external output of the archive file failed.

[0090] A transmission reservation flag indicating whether the previous external output of the archive file was successful or not is stored in the storage unit 57 of the document transaction device 1. If the external output of the archive file is unsuccessful (NO in step S10), the control unit 54 changes the transmission reservation flag from 0 (zero) to 1 (step S11) and then proceeds to the next step S12. If the external output of the archive file is successful (YES in step S10), the control unit 54 keeps the transmission reservation flag at 0. Then, proceed to the next step without making any changes.

[0091] In the documents F that have been fed in with copy F2 at the front, after separation in step S9, receipt F1 is located closer to the inlet / outlet opening 8 than copy F2 and is sandwiched between the pair of first rollers 44, and copy F2 is sandwiched between the pair of second rollers 45 (see FIG. 5). In this state, the control unit 54 reverses the rotation of the first rollers 44, and the conveyance rollers 40 and inlet / outlet rollers 41 that are upstream of the first rollers 44. As a result, receipt F1 advances through the first conveyance path 21A and is ejected from the device main body 2 through the inlet / outlet opening 8, and is returned to the user (step S12).

[0092] When returning the receipt F1, the control unit 54 switches the display operation unit 4 to display a return screen 80 shown in FIG. 16. The return screen 80 displays the attendant call key 64, as well as a guide message 80A urging the user to pick up the receipt F1 and a warning message 81 to be careful not to forget to pick up items to be returned, such as the receipt F1. The return screen 80 may also display an illustration indicating the location in the document transaction device 1 where the receipt F1 will be returned. Furthermore, if there is change, a guide message indicating that the change will be returned after the receipt F1 is returned may be displayed on the return screen 80.

[0093] At the same time as the receipt F1 is returned, the control unit 54 causes the second roller 45 and the conveying roller 40 downstream of the second roller 45 to rotate forward. As a result, the copy F2 moves backward within the first conveying path 21A, passes through the second conveying path 21B and the third conveying path 21C in this order, and is collected in the collection unit 26 within the device main body 2.

[0094] If the user wishes to transact two or more forms F, the user inserts the second form F into the intake / ejection slot 8 in the same manner as the first form F, in response to the return of the receipt F1 for the first form F. When the leading edge of the second, or next, form F on the side of the copy F2 is pinched between the pair of intake / ejection rollers 41 (YES in step S13), the control unit 54 takes this form F from the intake / ejection slot 8 into the first transport path 21A inside the device main body 2 (step S2), and repeats the processing of steps S3 to S12 for this form F. The same is true for the third and subsequent forms F.

[0095] If there is no next document F to be inserted into the inlet / outlet port 8 (NO in step S13), the control unit 54 causes the receipt printing unit 51 to issue a receipt showing the details of this transaction from the receipt outlet 5 (step S14 in FIG. 9). At that time, the control unit 54 switches the display operation unit 4 to display a receipt issuance screen 82 shown in FIG. 17. The receipt issuance screen 82 displays the attendant call key 64 and also displays a message 82A urging the user to receive the receipt. The receipt issuance screen 82 may also display an illustration indicating the location of the receipt outlet 5 from which the receipt is issued in the document transaction device 1. In the case of a credit card payment, the receipt contains the card slip number described above. In the case of a cash payment, if change is due, the control unit 54 opens the appropriate shutter of the shutters 12 and 15 in step S14 and returns the change. In this case, the message 82A also includes a message urging the user to receive the change.

[0096] The control unit 54 creates format data for the form F related to the current transaction based on the image data read from the form F in step S3, and outputs the data to the outside from the I / F unit 56 (step S15). In this embodiment, the format data is externally output at a timing later than the form processing timing in step S9. However, the format data may be created not in step S15 but in step S3, for example. The externally output format data is sent to and registered in the dictionary server 107 (see FIG. 3), thereby updating the latest format data in the dictionary server 107. In other words, the external output destination of the format data (dictionary server 107) is different from the external output destination of the archive file (relay device 101). Furthermore, the format data may be externally output in a compressed state to reduce communication load.

[0097] Finally, the control unit 54 checks the transmission reservation flag stored in the storage unit 57 (step S16). If the transmission reservation flag is 0, that is, if the transmission of the archive file in step S9 was successful (NO in step S16), the current normal transaction is completed. On the other hand, if the transmission reservation flag is 1, that is, if the transmission of the archive file at the processing timing in step S9 failed (YES in step S16), the control unit 54 outputs the archive file again to the outside at a timing after the processing timing (step S17). If the external output of the archive file this time also failed (NO in step S18), the control unit 54 maintains the transmission reservation flag at 1 and forcibly cancels the transmission of the archive file (step S19). If the external output of the archive file was successful (YES in step S18), the control unit 54 resets the transmission reservation flag from 1 to 0 (step S20) and completes the current normal transaction.

[0098] On the other hand, the processing when the document F brought by the user is the subject of a manual input transaction will be described mainly with reference to the flowchart in FIG. 18. In this case, the user selects a manual input transaction by touching the manual input transaction selection key 63 on the standby screen 61 (see FIG. 10) described above. Then (step S1), the control unit 54 switches the display operation unit 4 to display the payment screen 83 shown in FIG. 19, accepts the user's input of the payment amount on the payment screen 83, and obtains the payment amount information J1 described on the document F (step S21). The document F may also include a two-dimensional code indicating the payment amount information J1. In this case, the control unit 54 may accept the input of the payment amount information J1 by having the user hold the two-dimensional code over a reading unit (not shown), such as a two-dimensional code reader, provided on the document transaction device 1. The payment screen 83 displays an attendant call key 64, a cancel key 66, and a complete key 75, as well as a message 83A prompting the user to input the payment amount, a payment amount display field 83B, and a numeric keypad 84.

[0099] When the user operates the numeric keypad 84 to input the payment amount (payment amount information J1) for one item, that is, one sheet of document F, and touches the confirmation key 84A of the numeric keypad 84, the control unit 54 displays the payment amount in the payment amount display field 83B. When the user has finished inputting the payment amount for document F and touches the completion key 75, the control unit 54 assigns the aforementioned processing serial number to this document F and links it to the payment amount.

[0100] Next, the control unit 54 displays the input screen 70 (see FIG. 13) as in step S7, accepts the input of personal information by the user (step S22), and links the input to the previous processing sequence number. After accepting the input of personal information, the control unit 54 displays the cash payment screen 74 (see FIG. 14) or the credit card payment screen 76 (see FIG. 15) as in step S8, and performs the payment (step S23).

[0101] Next, similar to step S14, the control unit 54 displays the receipt issuance screen 82 (see FIG. 17) and issues a receipt 85 showing the details of this transaction from the receipt outlet 5 (step S24). If payment is made in cash and change is due, the control unit 54 also returns the change in step S24.

[0102] However, the receipt 85 issued for manual transactions differs from the receipt (not shown) issued for regular transactions. Specifically, as shown in FIG. 20 , the receipt 85 includes a title 85A, a guide 85B urging the user to take the receipt 85 to the counter, and transaction details 85C of the current manual transaction. The same guide 85B may be displayed on the receipt issuance screen 82. The transaction details 85C include the transaction sequence number assigned to the current document F, personal information (here, a phone number) corresponding to the transaction sequence number, and the settled payment amount. The control unit 54 may automatically assign a reception number, which indicates the order in which transactions are accepted at the counter, and write it on the receipt 85. Alternatively, the control unit 54 may issue a numbered tag bearing the reception number following the receipt 85. Of course, the numbered tag may be issued by a ticket issuing machine (not shown) separate from the document transaction device 1, in response to the user's or staff's operation or the issuance of the receipt 85.

[0103] Next, the control unit 54 generates an archive file for this manual input transaction (step S25), similar to step S9. However, in a manual input transaction, the document F is not imported into the document transaction device 1 and read, so the data for the issuer in this archive file does not include at least items (12), (13), and (17) that are read from the document F. Items (14) to (16) related to the issuer of the document F may be acquired by the control unit 54 by being input by the user through operation of the display operation unit 4, etc., during the manual input transaction.

[0104] Furthermore, in step S25, the control unit 54 changes the transmission reservation flag from 0 to 1. As a result, the control unit 54 goes through step S16 in FIG. 9 and outputs the archive file related to this manual input transaction to the outside (step S17). If the external output of the archive file fails (NO in step S18), the control unit 54 stops sending the archive file (step S19). If the external output of the archive file is successful (YES in step S18), the processing to be performed by the document transaction device 1 for this manual input transaction is completed. In the case of a manual input transaction, the control unit 54 outputs the archive file to the outside in this way at the end of the manual input transaction (although in practice there may be some time lag). In the relay device 101 that has received the archive file for the manual input transaction, the control unit 110 associates the archive file with a transaction status flag of "incomplete" and stores the archive file in the memory unit 112.

[0105] In the case of a manual transaction, after completing payment using the document transaction device 1, the user brings receipt 85 and document F to the counter and hands them to a counter clerk. The clerk compares the payment amount listed on document F with the payment amount listed on receipt 85. If the payment amount listed on document F matches the payment amount listed on receipt 85, the clerk determines that the payment for document F is complete, enters receipt stamps A in the stamp fields R on document F, separates document F, and hands the separated receipt F1 to the user. The clerk then operates counter terminal 102 to send an instruction to relay device 101 to update the transaction status flag in the archive file corresponding to this manual transaction from "incomplete" to "completed." In response to this instruction, control unit 110 of relay device 101 updates the corresponding transaction status flag from "incomplete" to "completed." This completes this manual transaction.

[0106] It is also possible to settle multiple forms F in a single manual transaction. In this case, in step S21, payment amounts for multiple forms F can be entered, and a separate processing sequence number is assigned to each payment amount. Then, in step S23, these payment amounts can be settled together, and these payment amounts and the corresponding processing sequence numbers are written together on receipt 85. Then, in step S25, multiple archive files corresponding to each form F are generated.

[0107] As described above, in the form transaction device 1, an archive file containing data for the issuer of form F regarding transactions using form F is generated and output externally. Therefore, at the issuer that manages table 118, which is a list of issued forms F, in management device 106, management device 106 can automatically receive the externally output archive file and delete the data of transacted form F from the list based on the data for the issuer contained in this archive file. In other words, the issuer can manage the handling of issued form F using electronic data rather than physical management.

[0108] This reduces the manual work required by issuer staff in the reversal process, which is post-processing for transaction-completed ledger sheets F, thereby easing the burden on staff. Furthermore, the reversal process can be performed before the actual delivery notice F2B from the financial institution arrives at the issuer, eliminating the need for the issuer to create reversal data based on the delivery notice F2B, as was done in the past. As a result of the above, usability in handling ledger sheets F can be improved. Furthermore, during the reversal process at the issuer, an additional check can be performed by comparing the delivery notice F2B mailed by the financial institution with the archive file, thereby improving the accuracy of the reversal process.

[0109] Furthermore, in the case of a normal transaction, the archive file is also output externally at the time of form processing (step S9) when form F is filled out and / or cut. This reduces the user's waiting time until the transaction is completed. The archive file is also output externally using a processing timing that precedes the timing of external output of the form data (step S15). This reduces the user's waiting time until the transaction is completed compared to when these data are output externally at the same time. If the archive file also includes image data of form F, the archive file size will be large, but by utilizing the processing timing of form processing, the archive file can be output externally efficiently. In this way, by transmitting the archive file and form data for each form F externally at separate times rather than all at once, the communication load is reduced, shortening the time required for the transaction and further improving usability.

[0110] Furthermore, if the external output of the archive file fails at the timing of the aforementioned report processing, a retry will be made at a later timing, thereby increasing the possibility that the management device 106 will receive the archive file, thereby helping to reduce the burden on the issuing staff.

[0111] The timing for outputting the archive file to the outside is not limited to the aforementioned processing timing, but can vary widely, such as after the completion of each transaction or during closing procedures after the end of business hours of a financial institution. For example, as shown in FIG. 21, when the power is turned on and the document transaction device 1 is started (step S31), the control unit 54 checks the transmission reservation flag stored in the memory unit 57 (step S32). This transmission reservation flag indicates whether there are any unsent archive files at the time when the power of the document transaction device 1 is most recently turned off. That is, in step S32, the control unit 54 checks whether there are any unsent archive files.

[0112] If there are no unsent archive files, the transmission reservation flag is 0 (NO in step S32), and the control unit 54 executes other processing to be executed after startup. On the other hand, if there are unsent archive files, the transmission reservation flag is 1 (YES in step S32), and the control unit 54 outputs the archive files to the outside (step S33). If there is no success notification from the relay device 101 even after a predetermined time (e.g., 900 seconds) has elapsed, the external output of the archive files has failed. If the external output of the archive files has failed (NO in step S34), the control unit 54 keeps the transmission reservation flag at 1 and cancels the transmission of the archive files (step S35). If the external output of the archive files has succeeded (YES in step S34), the control unit 54 resets the transmission reservation flag from 1 to 0 (step S36) and executes the next processing. Note that if the temporary storage folder 57B exists in the storage unit 57 at power-on, the archive files in the temporary storage folder 57B may be externally output regardless of the transmission reservation flag.

[0113] 22, in the document transaction device 1 after startup, when a staff member (which may be a maintenance worker) performs a predetermined operation such as inserting a dedicated key into a keyhole 86A (staff operation unit, see FIG. 4) of a lock 86 provided on the document transaction device 1 and turning it to a predetermined position (YES in step S41), the control unit 54 switches to display a staff screen (not shown) for the staff member on the display operation unit 4 (step S42). The control unit 54 checks the transmission reservation flag stored in the memory unit 57 (step S43).

[0114] If the transmission reservation flag is 1 (YES in step S43), the control unit 54 displays, for example, a pop-up warning on the clerk screen of the display operation unit 4 indicating that there is an archive file that has not been sent (step S44). After displaying the warning for a predetermined time, the control unit 54 ends the display of the clerk screen on the display operation unit 4 (step S45). The clerk who received the warning may instruct the document transaction device 1 to output the archive file externally, for example, by operating the display operation unit 4. On the other hand, if the transmission reservation flag is 0 because there are no unsent archive files (NO in step S43), the control unit 54 ends the display of the clerk screen on the display operation unit 4 after, for example, a predetermined time has elapsed (step S45).

[0115] The document transaction device 1 may be provided with an error detection unit (not shown) that detects errors in the document transaction device 1, and a release key (not shown) that is touched by a staff member to release the error. For example, if an error occurs during document processing in step S9 during a normal transaction and the processing is interrupted, and the staff member touches the release key to start releasing the error, the control unit 54 resumes the generation of the archive file that was interrupted in step S9, and after externally outputting the generated archive file, executes the processing from step S10 onwards. However, in this case, the predetermined time that serves as the criterion for determining whether the external output of the archive file in step S10 has been successful (the timeout mentioned above) is set to 60 seconds, which is longer than the 20 seconds mentioned above.

[0116] In the case of manual input transactions, it is conceivable that an archive file may be output externally with an incorrect payment amount or other information entered due to a user error. In this case, the user or a staff member requested by the user can operate the display operation unit 4 or the counter terminal 102 to input a cancel command to the document transaction device 1, causing the document transaction device 1 to output a new archive file reflecting the correct payment amount or other information externally, replacing the original archive file. This cancels the original archive file. Specifically, in response to the input of the cancel command, the control unit 54 of the document transaction device 1 creates a new archive file and transmits it externally. If the external output of the archive file fails, the control unit 54 changes the transmission reservation flag from 0 to 1. Therefore, the control unit 54 will output the archive file externally again when it subsequently checks the transmission reservation flag.

[0117] For example, when business hours end at a financial institution where the document transaction device 1 is installed, a clerk touches a completion key (not shown) on the document transaction device 1 as a closing procedure. In this case, as shown in FIG. 23, in response to touching the completion key (YES in step S51), the control unit 54 of the document transaction device 1 causes the receipt printing unit 51 to create a paper journal printing a history of all transactions during a predetermined period (specifically, during today's business hours) and issues the paper journal to the receipt outlet 5 (step S52). This history corresponds to a compilation of archive files (excluding image data) generated during the predetermined period. Next, the control unit 54 creates an electronic journal, which is electronic data about the history, and stores it in the memory unit 57 (step S53).

[0118] Next, the control unit 54 outputs the archive file stored in the temporary storage folder 57B to the outside (step S54). If a success notification is received from the relay device 101 within a predetermined time (e.g., 60 seconds), the external output of the archive file is successful. If the external output of the archive file is successful (YES in step S55), the control unit 54 deletes all archive files that have been sent from the temporary storage folder 57B or the temporary storage folder 57B itself (step S56), and transmits the electronic journal to a higher-level device (e.g., the relay device 101) (step S57).

[0119] On the other hand, if there is no notification of success from the relay device 101 even after the predetermined time has elapsed, the external output of the archive file has failed. In this case (NO in step S55), the control unit 54 pops up a warning screen (not shown) indicating that the external output of the archive file has failed, for example, on the display operation unit 4 (step S58). The warning screen displays a retry key for retrying the external output of the archive file. The warning screen may also include a message urging the user to restart the document transaction device 1 or to retry the next day. If the clerk touches the retry key upon seeing the warning screen (YES in step S59), the control unit 54 repeats the processing from step S54 onward. If the retry key is not touched even after the predetermined time has elapsed since the warning screen was displayed (NO in step S59), the control unit 54 changes the transmission reservation flag from 0 to 1 (step S60) and then transmits the electronic journal (step S57). In this case, the archive file in the storage unit 57 continues to exist. Therefore, the next time the document transaction device 1 is started, the archive file will be output to the outside again (see FIG. 21).

[0120] Since an electronic journal is created that is easier to store and handle than a paper journal, usability is improved. The electronic journal is stored in both the document transaction device 1 and the relay device 103. Archive files deleted from the temporary storage folder 57B in the memory unit 57 of the document transaction device 1 are stored in a separate storage folder 57C (see FIG. 6) provided in the memory unit 57. The electronic journal may also be stored in the storage folder 57C. When the document transaction device 1 is subsequently started, it is assumed that there is a file that does not exist in the temporary storage folder 57B but exists in the date folder 112B of the relay device 101. However, the mirroring process at the time of start-up of the document transaction device 1 is skipped for this file, and the file may remain in the date folder 112B.

[0121] When an electronic journal is created, the operation of the paper journal may be discontinued, and accordingly, the processing of step S52 related to the paper journal may be omitted. Information on the cash balance within the document transaction device 1 may be transmitted to a host device in the same manner as the electronic journal, and may be remotely monitored by the host device. The archive file may also include an electronic journal, in which case step S57 may be omitted, and the archive file including the electronic journal is output externally in step S54.

[0122] As described above, the control unit 54 may output the archive file externally at least at any of the following times: when the document transaction device 1 is started (see Figure 21), when an error that has occurred in the document transaction device 1 is resolved, when transaction data (an archive file in which the payment amount, etc. has been entered incorrectly) is canceled, and when an electronic journal is created (see Figure 23).

[0123] The present invention is not limited to the contents of the above-described embodiment, and various modifications are possible within the scope of the claims.

[0124] For example, in the document management system 100, the relay device 101 described above may be omitted, in which case the archive file is directly output externally from the document transaction device 1 to the issuing management device 106. As a result, a mirroring process is performed between the document transaction device 1 and the management device 106, and archive files and the like are shared in real time.

[0125] In the above-described embodiment, a document F whose type could not be identified is considered to be a document F that cannot be accepted by the document transaction device 1, but even if the type can be identified, a document F that is designated as not subject to normal processing by the document transaction device 1 may also be considered a document F that cannot be accepted by the document transaction device 1 and subject to manual input transactions.

[0126] The document transaction device 1 may be installed not only in a financial institution but also in a store such as a convenience store. In that case, a store clerk plays the role of the aforementioned teller.

[0127] The document transaction device 1 in this embodiment can communicate with an external device such as a card payment server 105 (see FIG. 3). For example, a communication problem may occur in which the communication line (e.g., the public line 104) between the document transaction device 1 and the card payment server 105 is temporarily interrupted due to a malfunction on the card payment server 105 side or a lightning strike. During the communication problem, the document transaction device 1 cannot process credit card payments, but can perform degenerate transactions using cash payments. The communication problem can be resolved by restarting the document transaction device 1. Specifically, after restarting the document transaction device 1, the control unit 54 of the document transaction device 1 automatically performs an online test with the card payment server 105. If the transmission and reception of an online test signal between the document transaction device 1 and the card payment server 105 is successful, the online test is passed, and the document transaction device 1 is restored from the communication problem. Because the online test places a heavy load on the control unit 54, it is desirable to perform the online test when no transactions are being performed.

[0128] Therefore, a predetermined waiting time is set in connection with the online test. If no transactions occur within the waiting time, it is highly likely that there are no customers near the document transaction device 1, so the online test can be performed when no transactions are occurring. Specifically, if a communication problem occurs, the control unit 54 restarts the document transaction device 1 and performs the transaction in degraded operation after the restart. If there is no next transaction between the end of the transaction and the waiting time, the control unit 54 performs the online test as the waiting time elapses. If the online test passes, the document transaction device 1 is fully restored, and the control unit 54 can handle not only cash payments but also credit card payments. This is particularly convenient when the document transaction device 1 is installed in an unmanned store because it eliminates the need for an attendant to resolve the communication problem. However, if the problem does not automatically recover even after restarting (such as an error pause or out of receipt paper) or if the problem does not allow degraded operation for cash payments, the online test will not be performed automatically and an attendant must be dispatched to the store.

[0129] The various features described above can be combined as appropriate. [Explanation of symbols]

[0130] 1. Document transaction device 4 Display operation section 20. Document Processing Unit 29 Reading unit 54 Control Unit 56 I / F section 57 Memory section 100 Document Management System 101 Relay device 106 Management device 110 control section 111 I / F section 112 Storage section 115 Control Unit 116 I / F section 118 tables F Report J1 Payment Information

Claims

1. A document management system including a document transaction device that performs transactions using documents, and a management device that manages a table in which data of issued documents and a transaction presence / absence flag indicating whether the data of the issued documents have been transacted are stored in association with each other, The document transaction device includes a transaction unit that executes a transaction based on a document, and an output unit that outputs to the management device issuer-oriented data for identifying a document that was the subject of the transaction executed by the transaction unit, the issuer-oriented data being used by the document issuer to identify a document that has already been transacted, The management device, which manages data on issued forms, includes an input unit to which the data for the issuer output by the output unit is directly input from the output unit, and a flag change unit that changes the state of a transaction presence / absence flag corresponding to the data on the form from first information corresponding to no transaction to second information corresponding to a transaction completed, while leaving the data on the form identified by the data for the issuer input to the input unit from the data on the form stored in the table without deleting it from the table.

2. The document management system according to claim 1 , wherein the issuer data includes identification information for identifying the document that was the subject of the transaction executed by the transaction unit.

3. A data processing method in a document management system including a document transaction device that performs transactions using documents, and a management device that manages a table in which data of issued documents and transaction presence / absence flags that indicate whether the data of the issued documents have been transacted are stored in association with each other, comprising: a transaction step in which the document transaction device executes a transaction based on the document; an output step of outputting issuer-oriented data, which is intended for the issuer of the document, for identifying the document that was the subject of the transaction in the transaction step by the document transaction device, to the management device; A data processing method including a flag change step in which the management device, which manages data on issued forms, leaves the data on forms stored in the table that is identified by the data for the issuer directly input to the management device from the form transaction device without deleting it from the table, and changes the state of the transaction presence / absence flag corresponding to the data on the form from first information corresponding to no transaction to second information corresponding to a transaction.

4. 4. The data processing method according to claim 3, wherein the data for the issuer includes identification information for identifying the form that was the subject of the transaction in the transaction step.

Citation Information

Patent Citations

  • Business form handling device

    JP2005222354A

  • Settlement system

    JP2012238081A

  • Gift certificate issue system

    JP2016177533A

  • Transaction device and method of handling paper using transaction device

    JP2018081381A