TWM650477U - Credit voucher image management system - Google Patents

Abstract

A credit voucher image management system is provided in present disclosure. The credit voucher image management system comprises a processing system, a storage server and a searching interface. The processing system is configured to receive a plurality of credit voucher data from an external financial system, and send notification messages to a bank notification system respectively based on the plurality of credit voucher data. The storage server is coupled to the processing system and is configured to store the plurality of credit voucher data, wherein each of the plurality of credit voucher data comprises an invoice and credit voucher image data. The searching interface is coupled to the storage server, configured to receive a searching instruction from a user device, perform searching among the plurality of credit voucher data stored in the storage service, and then transmit one of the plurality of credit voucher data corresponding to the searching instruction to the user device.

Description

Charge sheet image management system

This disclosure document relates to a charge sheet management system, in particular to a charge sheet image management system that can store and query electronic charge sheet images and transaction details.

Credit card transactions are one of the common transaction methods in today's society. According to the regulations of international financial organizations (such as VISA, JCB, CUP, etc.), when cardholders visit a special store to make a credit card transaction of a certain amount, they must sign the transaction receipt to serve as a reference for future consumption disputes. .

In the past, credit card transactions were usually made in paper form. However, according to relevant regulations, authorized stores must retain the credit card transaction receipt slip for at least 18 months. If billing operations are performed on paper, the accumulated paper will not only occupy a large amount of storage space, but also consume a lot of manpower when the billing slips need to be transmitted, sorted, and searched. Therefore, how to efficiently store and keep transaction receipts is one of the issues in this field.

This disclosure document provides a billing document image management system, including a processing system, a storage server and a query interface. The processing system is used to receive multiple bill data from an external financial system, and send notification messages to the bank notification system based on the multiple bill data. The storage server is coupled to the processing system for storing a plurality of bill data, wherein each of the plurality of bill data includes transaction details and bill image data. The query interface is coupled to the storage server for receiving query instructions from the user device, querying multiple bill data on the storage server, and then querying multiple bill data corresponding to the query command. One of them is sent to the user device.

Through the billing slip image management system of this disclosure document, the details and images of the billing slip can be stored and managed electronically, thus saving the consumption of human resources and the waste of space. In addition, the billing slip image management system in this disclosure document also provides ways to query billing slip information through a variety of different channels, as well as the function of logging in to manage user accounts.

The following disclosure provides many different embodiments or examples for implementing various features of the provided subject matter. Specific examples of components and arrangements are described below to simplify the present application. Of course, these are examples only and are not intended to be limiting.

In addition, the terms used throughout the specification and the scope of the patent application generally have the usual meaning of each term used in the field, in the content of this disclosure document, and in the special content, unless otherwise noted. meaning. Certain terms used to describe the present disclosure are discussed below or elsewhere in this specification to provide those skilled in the art with additional guidance in describing the present disclosure.

In this article, unless the article is specifically limited in the context, "a" and "the" can generally refer to one or more. It will be further understood that the words "include", "include", "have" and similar words used in this article specify the features, regions, integers, steps, operations, elements and/or components that they describe, but do not exclude one or more of its other features, regions, integers, steps, operations, elements, components, and/or groups thereof, described therein or in addition thereto.

Figure 1 is a functional block diagram of a bill image management system 100 according to some embodiments. In some embodiments, the bill image management system 100 includes a processing system 110, an extranet gateway system 120, a storage server 130 and a query interface 140.

The processing system 110 is coupled to the external connection gateway system 120 and the storage server 130, and is used to receive multiple bill data DATA from the external financial system through the external connection gateway system 120. The bill data DATA is the point of sale (POS) that consumers use through a physical point of sale (POS) (for example, a credit card swipe machine) or a mobile point of sale (mPOS) (for example, a mobile phone or tablet with a card swipe machine). Computer) record data generated when using credit card for transaction activities, and has specific specifications (the specifications are subject to the regulations of the external financial system). In some embodiments, the bill data DATA includes transaction details and bill image data to record transaction activity details (for example, date, time, consumption place, consumption object, etc.) and the signature of the consumer.

After receiving the bill data DATA via physical or mobile POS, the external financial system will determine whether the transaction was successful. When the external financial system determines that the transaction is successful, it will transmit the bill data DATA to the bill image management system 100 to facilitate the storage and management of the bill data DATA.

In some embodiments, when the processing system 110 receives the bill data DATA from the external financial system, it will send the notification message NT to the bank notification system to notify the bank clerk of the occurrence of new transaction activities. In some embodiments, the notification message NT is an email, a phone message, a text file, or any combination thereof.

In some embodiments, the processing system 110 may be composed of a central processing unit (CPU), a microprocessor (Microprocessor), a multi-processor (Multi-processor), a distributed processing system, or an application special integrated circuit (Application Specific Integrated Circuit). Specific Integrated Circuit (ASIC), other similar components, or any combination thereof.

The external connection gateway system 120 is coupled between the processing system 110 and the external financial system, and is used to provide the processing system 110 with a connection to the external financial system to receive the bill data DATA. In some embodiments, the external gateway system 120 includes Secure Sockets Layer (SSL) protocol, Transmission Control Protocol/Internet Protocol (TCP/IP), other security mechanisms, or any combination thereof.

The storage server 130 is coupled to the processing system 110 and the query interface 140, and is used to store multiple bill data DATA for the processing system 110 and the query interface 140 to read. In some embodiments, the storage server 130 may be implemented by dynamic random access memory (DRAM), static random access memory (SRAM), read only memory (ROM), or other components with storage functions.

The query interface 140 is coupled to the storage server 130 for receiving the query command SR from the user device (eg, mobile phone, personal computer, etc.), and querying the storage server 130 for the bill data corresponding to the query command SR. DATA, and then send this bill data DATA to the user device to complete the query of bill data DATA.

In some embodiments, the query command SR is sent by the user device through the bill URL. For example, when a consumer conducts a credit card transaction and generates the billing slip data DATA, he or she will receive an email containing the billing slip URL. The consumer can click on the billing slip URL in the email via a personal computer to send an inquiry. Command SR to the query interface 140 of the bill image management system 100, and then read the bill data DATA corresponding to the query command SR in the storage server 130, and the query interface 140 then transmits the queried bill data DATA to a personal computer and displayed on the computer screen.

In addition, different bill URLs correspond to different query instructions SR, that is, they correspond to different bill data DATA. For example, when a consumer conducts two credit card transactions, the first billing slip information and the second billing slip data will be generated respectively, and the consumer will receive the first billing slip URL and the second billing slip information respectively. Two emails for a single URL. When the consumer clicks on the first bill URL, the query interface 140 will query and send the first bill information to the consumer's personal computer; when the consumer clicks on the second bill URL, the query interface 140 will query and The second billing statement information is sent to the consumer's personal computer.

In some embodiments, the bill image management system 100 of this disclosure document further provides the function of a special store or bank to log in and view/manage bill data DATA and account information. As shown in Figure 1, in some embodiments, the bill image management system 100 further includes a login interface 150. The login interface 150 is coupled to the processing system 110 and the query interface 140 for receiving login information LO from the user device. , the query command SR and the account data modification command AC, and determine whether to send the query command SR and the account data modification command AC to the query interface 140 and the processing system 110 respectively according to the login information LO (that is, determine whether to agree to the user device to use the billing form function of the image management system 100). In some embodiments not shown, the storage server 130 is further configured to store multiple user account data, and the processing system 110 is further configured to modify a corresponding one of the user data according to the account data modification command AC (for example, , change password, contact number, business address, etc.).

In operation, when the login interface 150 receives the login information LO from the user device, the login interface 150 compares the login information LO with the user account information in the storage server 130 . When the login information LO does not match each user account information, the login interface 150 will determine that the login information LO is not compliant, and therefore refuse the user device to use the query interface 140 to query or use the processing system 110 to process user account information. Modifications.

On the contrary, when the login information LO matches one of the user account information, the login interface 150 determines that the login information LO is compliant, and therefore allows the user device to log in to the billing slip image management system 100 for use according to the query command SR. The query interface 140 performs query, and AC uses the processing system 110 to modify the user account data according to the account data modification instruction.

In some embodiments, when the query command SR does not correspond to any bill data DATA in the storage server 130 (for example, the content (date, bill number, etc.) of the input query command SR is incorrect), because The query interface 140 does not query the billing slip data DATA corresponding to the query command SR in the storage server 130. The query interface 140 will send a query failure prompt FA to the user device to remind the user that the relevant billing slip cannot be queried. DataDATA.

Figure 2 is a flow chart of a billing slip data query method 200 according to some embodiments. In some embodiments, the method 200 for querying bill information includes steps S210, S220, S230, S240, S250, S260, S270 and S280.

In step S210, the bill image management system 100 determines whether the query command SR is sent through the bill URL to determine whether the user is required to input the login information LO. When the query command SR is not sent through the bill URL, step S220 is executed; when the query command SR is sent through the bill URL, step S250 is executed.

In step S220, the login interface 150 receives the login information LO, and then executes step S230. In step S230, the login interface 150 determines whether the login information LO matches one of the user account information. When the login information LO does not match each user account information, step S240 is executed; when the login information LO matches one of the user account information, step S250 is executed.

In step S240, the login interface 150 refuses the user device to log in to the bill image management system 100, and then executes step S220 to require the user to re-enter the login information LO.

In step S250, the query interface 140 queries the storage server 130 according to the query command SR, and then executes step S260. In step S260, the query interface 140 determines whether the bill data DATA corresponding to the query command SR exists in the storage server 130. When the query interface 140 queries the bill data DATA corresponding to the query command SR in the storage server 130, When the data DATA is found, step S270 is executed; when the query interface 140 cannot query the billing slip data DATA corresponding to the query command SR in the storage server 130, step S280 is executed.

In step S270, the query interface 140 transmits the bill data DATA corresponding to the query command SR to the user device for display. In step S280, the query interface 140 sends a query failure prompt FA to the user device to remind the user that the relevant bill data DATA cannot be queried.

Figure 3 is a flow chart of a method 300 for modifying user data according to some embodiments. In some embodiments, the user data modification method 300 includes steps S310, S320, S330 and S340.

In step S310, the login interface 150 receives the login information LO and the account information modification command AC, and then executes step S320. In step S320, the login interface 150 determines whether the login information LO matches one of the user account information. When the login information LO matches one of the user account information, step S330 is executed; when the login information LO does not match each user account information, step S340 is executed.

In step S330, the login interface 150 determines that the login information LO is compliant, and therefore allows the user device to log in to the bill image management system 100 to use the processing system 110 to modify the user account information according to the account information modification instruction AC.

In step S340, the login interface 150 determines that the login information LO is not compliant, and therefore refuses the user device to use the processing system 110 to modify the user account information, and then executes step S310 to require the user to enter the login information LO again.

It should be noted that the number and sequence of steps in the query method 200 and the modification method 300 of this disclosure are only examples and are not intended to limit this disclosure. The number and sequence of other steps are within the scope of this disclosure. In some embodiments, steps S260 and S280 may be omitted, so step S270 is directly executed after step S250 is completed.

Through the billing slip image management system of this disclosure document, the transaction details and billing slip images in the billing slip data can be stored electronically in the storage server to avoid the manpower and space caused by paper billing slips. consumption. In addition, for consumers, they can directly query the billing slip information by just clicking on the URL; for special merchants and banks, they can log in to the billing slip image management system to query/manage the billing slip information and modify it. or account information. The bill image management system of this disclosure document provides a variety of functions to consumers, authorized merchants and banks, and only improves the convenience of bill query/management.

The above are only preferred embodiments of this disclosure document. The structure of this disclosure document can be modified and equivalently changed in various ways without departing from the scope or spirit of this disclosure document. In summary, all modifications and equivalent changes made to this disclosure document within the scope of the following requirements are within the scope of this disclosure document.

100:Bill image management system 110:Processing system 120:Outreach gateway system 130:Storage server 140: Query interface 150:Login interface 200: How to query billing slip information S210, S220, S230, S240: steps S250, S260, S270, S280: steps 300: How to modify user information S310, S320, S330, S340: steps AC:Account information modification instructions DATA: bill information FA: Query failure prompt LO:Login information NT: notification message SR: query command

In order to make the above and other objects, features, advantages and embodiments of this disclosure more obvious and understandable, the accompanying drawings are described as follows: Figure 1 is a functional block diagram of a bill image management system according to some embodiments; Figure 2 is a flow chart of a method for querying billing slip data according to some embodiments; and Figure 3 is a flow chart of a method for modifying user data according to some embodiments.

100:Bill image management system

110:Processing system

120:Outreach gateway system

130:Storage server

140: Query interface

150:Login interface

AC:Account information modification instructions

DATA: bill information

FA: Query failure prompt

LO:Login information

NT: notification message

SR: query command

Claims (10)

A billing document image management system, including: A processing system for receiving a plurality of bill data from an external financial system and sending a notification message to a bank notification system based on the plurality of bill data respectively; A storage server coupled to the processing system for storing the plurality of bill data, wherein the plurality of bill data each includes a transaction detail and a bill image data; and A query interface coupled to the storage server for receiving a query command from a user device, querying the plurality of bill data in the storage server, and then querying the data corresponding to the query One of the plurality of bill information of the instruction is sent to the user device. The charge sheet image management system as described in claim 1 further includes an extranet gateway system coupled to the processing system to provide the processing system with a connection to the external financial system to receive The multiple billing slip information. The billing slip image management system as described in claim 1, wherein the notification message is an email, a phone message, a text file or any combination thereof. The bill image management system as described in request item 1, wherein the query command is sent by the user device through a bill URL, and the bill URL is associated with the multiple bill data. Corresponding to one. The bill image management system as described in claim 1 further includes a login interface coupled to the query interface, and the storage server is further used to store multiple user account information, wherein the login interface is used to automatically The user device receives a login information and compares the login information with the plurality of user account information to determine whether the user device is allowed to use the bill image management system. The bill image management system as described in request item 5, wherein when the login information does not match the multiple user account information, the login interface does not allow the user device to use the query interface for query. The bill image management system as described in request item 5, wherein when the login information matches one of the plurality of user account information, the login interface allows the user device to use the query interface according to the query command. Read the corresponding one of the plurality of bill data from the storage server. The bill image management system as described in request item 7, wherein when the query interface determines that the plurality of bill data does not correspond to the query command, the query interface is further used to send a query failure prompt to the user. device. The bill image management system as described in claim 5, wherein the bill image management system is further configured to receive an account information modification instruction from the user device, and the processing system is further configured to act according to the account information modification instruction. Modify one of the multiple user profiles. The bill image management system as described in request item 9, wherein when the login information does not match the user account information, the login interface does not allow the processing system to modify one of the user information. who; and When the login information matches one of the user account information, the login interface allows the processing system to modify the one of the user information according to the account information modification instruction.

Images