TWM584494U - Third-party checks management system - Google Patents

Abstract

A third party checks management system is provided. The third party checks management system includes a check storage module, a check waring module and a check retrieving module. The check storage module is configured to store data of plural third party checks. The check waring module is configured to check the data of the third party checks in accordance with a predetermined waring condition, so as to determine if a check warning message is outputted to warn a user. The check retrieving module is configured to perform a retrieving operation on the data of the third party checks to output a retrieving result for the user.

Description

Ticket management system

The present invention relates to a ticket management system, and in particular to a ticket management system that integrates information of various branches.

Ticket financing is a common bank financing business. In today's ticket financing business, when one branch conducts ticket financing, no other branch can know the relevant information. If the person in question is a fraudulent bank and provides false transaction tickets to different branches, these tickets may not be cashed. In this way, the creditor who was originally compensated for the passenger ticket cannot repay the principal, which in turn affects the bank's claims.

Therefore, a ticket management system is needed to solve the above problems.

Therefore, one of the objectives of the present invention is to provide a ticket management system that can integrate ticket information of all branches so that each branch operator can query related ticket information. In addition, you can also determine whether there are any problems with the received tickets and issue a warning message.

According to the above-mentioned purpose of the new model, the ticket management system includes Ticket storage module, ticket warning module and ticket retrieval module. The ticket storage module is used to store multiple ticket data of multiple tickets. The ticket warning module is used to check the ticket data according to the preset warning conditions to determine whether to output a ticket warning message to warn the user. The ticket retrieval module is used to retrieve the ticket data according to the retrieval conditions to output the ticket retrieval results for users to view.

According to an embodiment of the present invention, each ticket information includes the company name of the ticket, the name of the person in charge, the amount, the place of invoice, the date of the invoice, the creditor who received the ticket, and the business unit undertaking. The search conditions include the name of the company, the name of the person in charge, Amount, place of invoice, date of invoice, creditor who received the ticket, business unit undertaking, total number of tickets and total amount of ticket.

According to an embodiment of the present invention, the aforementioned preset warning condition includes a total amount of tickets corresponding to a company name.

According to an embodiment of the present invention, the aforementioned ticket warning module is used to determine whether the total amount of tickets corresponding to the company name exceeds an upper limit. When the total amount of tickets corresponding to the company name exceeds the upper limit, the ticket warning module Output a warning signal.

According to an embodiment of the present invention, the aforementioned warning condition includes a total amount of a ticket corresponding to a person in charge.

According to an embodiment of the present invention, the aforementioned ticket warning module is used to determine whether the total amount of the ticket corresponding to the person in charge exceeds the upper limit. When the total amount of the ticket corresponding to the person in charge exceeds the upper limit, the ticket warning module The group outputs a warning signal.

According to an embodiment of the present invention, the aforementioned warning condition includes The total number of tickets for a company name.

According to an embodiment of the present invention, the aforementioned ticket warning module is used to determine whether the total number of tickets corresponding to this company name exceeds the maximum number of sheets. When the total number of tickets corresponding to this company name exceeds the maximum number of sheets, The ticket warning module outputs a warning signal.

According to an embodiment of the present invention, the aforementioned warning condition includes a total number of tickets corresponding to a person in charge.

According to an embodiment of the present invention, the aforementioned ticket warning module is used to determine whether the total number of tickets corresponding to the person in charge exceeds the maximum number of tickets. When the total number of tickets corresponding to the person in charge exceeds the maximum number of tickets The ticket warning module outputs a warning signal.

110‧‧‧Ticket Management System

112‧‧‧Ticket Storage Module

114‧‧‧Ticket retrieval module

116‧‧‧Ticket Alert Module

118‧‧‧Data Transmission Module

120‧‧‧ Branch Computer

210 ~ 230‧‧‧step

310 ~ 330‧‧‧step

For a more complete understanding of the embodiment and its advantages, reference is now made to the following description in conjunction with the accompanying drawings, wherein: FIG. 1 is a functional block diagram of a ticket management system according to the new embodiment; FIG. 2 is a diagram based on A schematic diagram of a data storage process of the ticket management system of the present embodiment; and FIG. 3 is a schematic diagram of a data retrieval process of the ticket management system of the present embodiment.

Please refer to FIG. 1, which is a functional block diagram of a ticket management system 110 according to an embodiment of the present invention. The ticket management system 110 is used to receive ticket data uploaded by each branch to store these ticket data and analyze them. For example, when a branch member receives a ticket, the branch member will use the branch computer 120 to register the relevant information of the ticket, and then upload the ticket information to the ticket management system 110 to use the ticket management system 110 for storage and analysis. This ticket information. In this embodiment, the ticket management system 110 may be a server, but the embodiment of the present invention is not limited to this.

The ticket management system 110 includes a ticket storage module 112, a ticket retrieval module 114, and a ticket warning module 116. The ticket storage module 112 is used to store the ticket data uploaded by the branch. In this embodiment, each ticket information includes the company name / person in charge of the ticket, the amount, the place of invoice, the date of the invoice, the creditor who received the ticket, and the undertaking business unit, but the new embodiment is not limited to this this. The ticket storage module 112 may be various types of storage devices, such as a hard disk drive, a solid state disk, a floppy diskette drive, a magnetic tape machine, etc., but The embodiments of the present invention are not limited to this.

The ticket retrieval module 114 is configured to retrieve the ticket data in the ticket storage module 112 according to the retrieval conditions uploaded by the branch computer 120, and return the retrieved results to the branch computer 120. For example, if the user enters a search condition of "100,000 to 200,000" on the branch computer 120, the ticket retrieval module 114 will retrieve the ticket data in the ticket storage module 112 according to this retrieval condition to find the amount as "100,000 to 200,000" ticket data and return it to the branch computer 120 for retrieval. In this embodiment, the search bar The documents include the company name, the name of the person in charge, the amount, the invoice place, the invoice date, the credit recipient who received the ticket, the business unit undertaking, the total number of tickets and the total amount of the ticket. However, the embodiments of the present invention are not limited to this.

The ticket warning module 116 is used to check the ticket data in the ticket storage module 112 according to a preset warning condition to determine whether to output a ticket warning message to the branch computer 120. For example, when a branch computer 120 sends a new ticket data to the ticket management system 110, the ticket data will be stored in the ticket storage module 112, and then the ticket alert module 116 will process the ticket according to the preset alert conditions. Check in the ticket data in the storage module 112.

In one embodiment of the present invention, the preset warning condition includes a company's total ticket amount. In this embodiment, if the ticket alert module 116 finds that the total amount of all tickets corresponding to a certain company name exceeds an amount limit, the ticket alert module 116 will issue a warning message to each branch computer 120 to notify each branch of the company The total amount of tickets in the first name has exceeded the upper limit. Please pay attention to the tickets of this company name in each branch.

In another embodiment of the present invention, the preset warning condition includes the total amount of the ticket of the person in charge. In this embodiment, if the ticket alert module 116 finds that the total amount of all tickets corresponding to a person in charge exceeds the upper limit, the ticket alert module 116 will issue a warning message to each branch computer 120 to notify each branch that it is responsible The total amount of tickets with a person's name has exceeded the upper limit. Please pay attention to the tickets with the person in charge.

In another embodiment of the present invention, the preset warning condition includes the total number of tickets of the company. In this embodiment, if the ticket alert module 116 issues When the total number of all tickets corresponding to a company name exceeds the maximum number, the ticket warning module 116 will issue a warning message to each branch computer 120 to notify each branch that the total number of tickets for this company name has exceeded the upper limit. Please pay attention to the ticket of this company name at each branch.

In another embodiment of the present invention, the preset warning condition includes the total number of tickets of the person in charge. In this embodiment, if the ticket alert module 116 finds that the total number of all tickets corresponding to a person in charge exceeds the maximum number of tickets, the ticket alert module 116 will issue a warning message to each branch computer 120 to notify each branch The total number of tickets in this person's name has exceeded the limit. Please pay attention to the tickets in this person's name.

In addition, in order to facilitate data transmission between the branch computer 120 and the ticket management system 110, the ticket management system 110 includes a data transmission module 118. The data transmission module 118 is electrically connected to the ticket storage module 112, the ticket retrieval module 114, and the ticket warning module 116 to transmit the ticket data to the ticket storage module 112; the retrieval conditions are transmitted to the ticket retrieval module 114; and Send the search result / warning message to the branch computer 120. In this embodiment, the data transmission module 118 is a network interface card (NIC), which can be connected to the branch computer 120 through the Internet to establish a communication link with each other.

Please refer to FIG. 2, which is a schematic diagram illustrating a data storage process of the ticket management system 110 according to the embodiment of the present invention. As shown in FIG. 2, step 210 is first performed to use the data transmission module 118 to receive ticket data from the branch computer 120. Then, step 220 is performed to use the ticket storage module 112 to store the ticket data. Then proceed to step 230 to utilize the ticket alert Module 116 checks the ticket data in the ticket storage module 112. In this embodiment, whenever the ticket storage module 112 stores a new piece of ticket data, the ticket warning module 116 checks the ticket data in the ticket storage module 112, but the new embodiment is not limited. this. In other embodiments of the new form, the ticket warning module 116 checks the ticket data in the ticket storage module 112 according to a preset inspection period.

Please refer to FIG. 3, which is a schematic diagram illustrating a data retrieval process of the ticket management system 110 according to the embodiment of the present invention. As shown in FIG. 3, step 310 is first performed to use the data transmission module 118 to receive the retrieval conditions from the branch computer 120. Next, step 320 is performed to use the ticket retrieval module 114 to retrieve the ticket data in the ticket storage module 112. Then, step 330 is performed to use the data transmission module 118 to transmit the search result back to the branch computer 120 for searching.

As can be seen from the above description, the ticket management system 110 of the present embodiment not only can be used by branches to query information about all tickets, but can also actively check tickets as a risk control mechanism. In addition, if a bounce ticket is found, the crew can also upload relevant information to the ticket management system 110 through the branch computer 120, so that the ticket warning module 116 can check / provide an alert for the relevant ticket.

Although the new model has been disclosed as above, it is not intended to limit the new model. Any person skilled in the art can make various changes and retouches without departing from the spirit and scope of the new model. Therefore, the new model is protected. The scope shall be determined by the scope of the attached patent application.

Claims (10)

A ticket management system includes: a ticket storage module for storing a plurality of ticket data of a plurality of tickets; a ticket warning module for checking the ticket data according to a preset warning condition to determine whether to output A ticket warning message; and a ticket retrieval module for retrieving the ticket data according to a retrieval condition to output a ticket retrieval result. If the ticket management system described in item 1 of the scope of patent application, each of these ticket information includes the name of the ticket company, the name of the person in charge, the amount, the invoice place, the invoice date, the credit recipient who received the ticket, and the business unit undertaking, The search conditions include the company name, the person in charge, the amount, the invoice place, the invoice date, the credit recipient who received the ticket, the business unit undertaking, the total number of tickets, and the total amount of the ticket. The ticket management system according to item 1 of the scope of patent application, wherein the preset warning condition includes a total amount of a ticket corresponding to a company name. The ticket management system described in item 3 of the scope of patent application, wherein the ticket warning module is used to determine whether the total amount of the ticket corresponding to the company name exceeds an upper limit, and when the total amount of the ticket corresponding to the company name exceeds the When the amount is capped, the ticket warning module outputs a warning signal. The ticket management system according to item 1 of the scope of patent application, wherein the warning condition includes a total amount of a ticket corresponding to a person in charge. The ticket management system described in item 5 of the scope of patent application, wherein the ticket warning module is used to determine whether the total amount of the ticket corresponding to the person in charge exceeds an upper limit, and when the total amount of the ticket corresponding to the person in charge corresponds When the amount exceeds the upper limit, the ticket warning module outputs a warning signal. The ticket management system according to item 1 of the scope of patent application, wherein the warning condition includes a total number of tickets corresponding to a company name. The ticket management system described in item 7 of the scope of patent application, wherein the ticket warning module is used to determine whether the total number of tickets corresponding to the company name exceeds the maximum number of sheets. When the total number of tickets corresponding to the company name is When the number exceeds the upper limit, the ticket warning module outputs a warning signal. The ticket management system according to item 1 of the scope of patent application, wherein the warning condition includes a total number of tickets corresponding to a person in charge. Ticket management as described in item 9 of the scope of patent application System, wherein the ticket warning module is used to determine whether the total number of tickets corresponding to the person in charge exceeds the maximum number of tickets, and when the total number of tickets corresponding to the person in charge exceeds the maximum number of tickets, the ticket The warning module outputs a warning signal.