TWI868873B - 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

Bill Image Management System

This disclosure relates to a receipt management system, and more particularly to a receipt image management system capable of storing and querying electronic receipt images and transaction details.

Credit card transactions are one of the most common transaction methods in today's society. According to the regulations of international financial organizations (such as VISA, JCB, CUP, etc.), when a cardholder visits a contracted store and makes a credit card transaction of a certain amount, he or she must sign the transaction receipt, which will be used as a reference in the event of a consumer dispute in the future.

In the past, credit card transactions were usually processed on paper. However, according to relevant regulations, franchised stores must keep credit card transaction receipts for at least 18 months. If transactions are processed on paper, the accumulated paper will not only take up a lot of storage space, but also consume a lot of manpower when it is necessary to transmit, sort, and find receipts. Therefore, how to efficiently store and keep transaction receipts is one of the topics in this field.

The disclosed document provides a bill 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 transmit notification messages to a bank notification system according to each of the multiple bill data. The storage server is coupled to the processing system, and is used to store multiple bill data, wherein each of the multiple bill data includes transaction details and bill image data. The query interface is coupled to the storage server, and is used to receive a query instruction from a user device, and query the multiple bill data in the storage server, and then transmit one of the multiple bill data corresponding to the query instruction to the user device.

Through the bill image management system of this disclosure, the bill details and images can be stored and managed electronically, thereby saving the consumption of human resources and waste of space. In addition, the bill image management system of this disclosure also provides a way to query bill data 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 to implement different features of the subject matter provided. Specific examples of components and arrangements are described below to simplify the present case. Of course, these are only examples and are not intended to be limiting.

In addition, the terms used throughout the specification and the patent application generally have the ordinary meaning of each term used in this field, in the context of this disclosure, and in the specific context, unless otherwise specified. Certain terms used to describe the present disclosure will be discussed below or elsewhere in this specification to provide additional guidance to those skilled in the art in the description of the present disclosure.

In this article, unless the context specifically limits the article, "a", "an" and "the" may refer to one or more. It will be further understood that "include", "comprise", "have" and similar words used in this article indicate the characteristics, regions, integers, steps, operations, elements and/or components recorded therein, but do not exclude the described or additional one or more other characteristics, regions, integers, steps, operations, elements, components, and/or groups thereof.

FIG. 1 is a functional block diagram of a receipt image management system 100 according to some embodiments. In some embodiments, the receipt 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 gateway system 120 and the storage server 130, and is used to receive multiple billing slip data DATA from the external financial system through the external gateway system 120. The billing slip data DATA is the record data generated when the consumer uses a credit card to conduct transaction activities through a physical point of sale (POS) system (for example, a credit card swiping machine) or a mobile point of sale (mPOS) system (for example, a mobile phone or tablet computer with a swiping machine), and has specific specifications (the content of the specifications depends on the regulations of the external financial system). In some embodiments, the billing slip data DATA includes transaction details and billing slip image data to record the details of the transaction activity (for example, date, time, consumption place, consumption object, etc.) and the consumer's signature.

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

In some embodiments, when the processing system 110 receives the bill data DATA from the external financial system, a notification message NT is sent to the bank notification system to notify the bank staff of the occurrence of new transaction activities. In some embodiments, the notification message NT is an e-mail, a phone message, a text file or any combination thereof.

In some embodiments, the processing system 110 can be implemented by a central processing unit (CPU), a microprocessor, a multi-processor, a distributed processing system, an application specific integrated circuit (ASIC), other similar components, or any combination thereof.

The external gateway system 120 is coupled between the processing system 110 and the external financial system to provide the processing system 110 with a connection to the external financial system to receive the billing data DATA. In some embodiments, the external gateway system 120 includes a secure sockets layer (SSL) protocol, a transmission control communication protocol/Internet communication 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 to store multiple bill data DATA for reading by the processing system 110 and the query interface 140. In some embodiments, the storage server 130 can be implemented by a dynamic random access memory (DRAM), a static random access memory (SRAM), a read-only memory (ROM) or other components with storage functions.

The query interface 140 is coupled to the storage server 130 to receive a query command SR from a user device (e.g., a mobile phone, a personal computer, etc.), query the storage server 130 for the bill data DATA corresponding to the query command SR, and then transmit the bill data DATA to the user device to complete the query of the bill data DATA.

In some embodiments, the query command SR is sent by the user device via a billing statement URL. For example, when a consumer performs a credit card transaction and generates billing statement data DATA, an email containing the billing statement URL is received. The consumer can click on the billing statement URL in the email via a personal computer to send the query command SR to the query interface 140 of the billing statement image management system 100, and then read the billing statement data DATA corresponding to the query command SR in the storage server 130. The query interface 140 then transmits the retrieved billing statement data DATA to the personal computer and displays it on the computer screen.

In addition, different billing form URLs correspond to different query commands SR, that is, to different billing form data DATA. For example, when a consumer conducts two credit card transactions, first billing form data and second billing form data are generated respectively, and the consumer receives two emails containing the first billing form URL and the second billing form URL respectively. When the consumer clicks on the first billing form URL, the query interface 140 queries and transmits the first billing form data to the consumer's personal computer; when the consumer clicks on the second billing form URL, the query interface 140 queries and transmits the second billing form data to the consumer's personal computer.

In some embodiments, the bill image management system 100 of the present disclosure further provides a function for a contracted store or bank to log in and view/manage bill data DATA and account data. As shown in FIG. 1 , in some embodiments, the bill image management system 100 further includes a login interface 150, which is coupled to the processing system 110 and the query interface 140, and is used to receive the login data LO, the query command SR and the account data modification command AC from the user device, 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 data LO (i.e., determine whether to allow the user device to use the function of the bill image management system 100). In some embodiments not shown, the storage server 130 is further used to store multiple user account data, and the processing system 110 is further used to modify a corresponding one of these user data according to the account data modification instruction AC (for example, change the password, contact number, merchant address, etc.).

In operation, when the login interface 150 receives the login data LO from the user device, the login interface 150 compares the login data LO with the user account data in the storage server 130. When the login data LO does not match each user account data, the login interface 150 determines that the login data LO is not compliant, and thus denies the user device from using the query interface 140 to query or using the processing system 110 to modify the user account data.

On the contrary, when the login data LO matches one of the user account data, the login interface 150 will determine that the login data LO is compliant, and therefore agree to allow the user device to log in to the bill image management system 100, to use the query interface 140 to query according to the query instruction SR, and to use the processing system 110 to modify the user account data according to the account data modification instruction AC.

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), since the query interface 140 does not find the bill 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 prompt the user that the relevant bill data DATA cannot be found.

FIG. 2 is a flow chart of a billing data query method 200 according to some embodiments. In some embodiments, the billing data query method 200 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 via the bill website to determine whether the user needs to enter the login information LO. When the query command SR is not sent via the bill website, step S220 is executed; when the query command SR is sent via the bill website, step S250 is executed.

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

In step S240, the login interface 150 denies the user device from logging into the receipt image management system 100, and then executes step S220 to require the user to input the login information LO again.

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 there is a billing data DATA corresponding to the query command SR in the storage server 130. When the query interface 140 has found the billing data DATA corresponding to the query command SR in the storage server 130, step S270 is executed; when the query interface 140 cannot find the billing 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 transmits a query failure notification FA to the user device to prompt the user that the relevant bill data DATA cannot be found.

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

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

In step S330, the login interface 150 determines that the login data LO complies with the regulations, and therefore agrees to the user device to log into the receipt image management system 100, so as to modify the user account data using the processing system 110 according to the account data modification instruction AC.

In step S340, the login interface 150 determines that the login data LO is not compliant, and therefore denies the user device from using the processing system 110 to modify the user account data, and then executes step S310 to require the user to re-enter the login data LO.

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

Through the bill image management system of this disclosure, the transaction details in the bill data and the bill image can be electronically saved in the storage server to avoid the consumption of manpower and space caused by paper bills. In addition, for consumers, they can directly query the bill data by simply clicking on the URL; for special merchants and banks, they can log in to the bill image management system to query/manage the bill data and modify user account information. The bill image management system of this disclosure provides consumers, special merchants and banks with a variety of functions, which only improves the convenience of bill query/management.

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

100: Invoice image management system 110: Processing system 120: External gateway system 130: Storage server 140: Query interface 150: Login interface 200: Invoice data query method S210, S220, S230, S240: Steps S250, S260, S270, S280: Steps 300: User data modification method S310, S320, S330, S340: Steps AC: Account data modification command DATA: Invoice data FA: Query failure prompt LO: Login data NT: Notification message SR: Query command

In order to make the above and other purposes, features, advantages and embodiments of this disclosure document more clearly understandable, the attached drawings are described as follows: Figure 1 is a functional block diagram of a receipt image management system according to some embodiments; Figure 2 is a flow chart of a receipt data query method according to some embodiments; and Figure 3 is a flow chart of a user data modification method according to some embodiments.

Domestic storage information (please note in the order of storage institution, date, and number) None Foreign storage information (please note in the order of storage country, institution, date, and number) None

100: Bill image management system

110: Processing system

120: External gate system

130: Storage server

140: Query interface

150: Login interface

AC: Account data modification instructions

DATA: Billing data

FA: Query failed prompt

LO: Login information

NT: Notification message

SR: Query command

Claims (9)

A bill image management system includes: 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 according to each of the bill data; a storage server coupled to the processing system for storing the plurality of bill data, wherein each of the bill data includes a transaction detail and a bill image data; and a query interface coupled to the processing system. A storage server is used to receive a query instruction from a user device, query the multiple billing slip data in the storage server, and then transmit one of the multiple billing slip data corresponding to the query instruction to the user device, wherein the multiple billing slip data at least includes a first billing slip data and a first billing slip URL associated with a credit card swiped in a first consumption, the first billing slip data includes a first billing slip image associated with the first consumption swiped and a user signature, and a second billing slip data and a second billing slip URL generated when the credit card is swiped in a second consumption, the second billing slip data includes a second billing slip image associated with the second consumption swiped and the user signature, and the first billing slip URL and the second billing slip URL are transmitted to the user device respectively. The user device sends a first query instruction through the first billing form website, and the query interface queries the storage server according to the first query instruction to transmit the first billing form data to the user device, and the user device sends a second query instruction through the second billing form website, and the query interface queries the storage server according to the second query instruction to transmit the second billing form data to the user device. The bill 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 bill data. A bill image management system as described in claim 1, wherein the notification message is an email, a text message, a text file, or any combination thereof. The receipt 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 data, wherein the login interface is used to receive a login data from the user device and compare the login data with the multiple user account data to determine whether to allow the user device to use the receipt image management system. A bill image management system as described in claim 4, 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 to query. A bill image management system as described in claim 4, wherein when the login data matches one of the multiple user account data, the login interface allows the user device to use the query interface to read the corresponding one of the multiple bill data from the storage server according to the query instruction. The bill image management system as described in claim 6, wherein when the query interface determines that the multiple bill data do not correspond to the query instruction, 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 4, wherein the bill image management system is further used to receive an account data modification instruction from the user device, and the processing system is further used to modify one of the multiple user data according to the account data modification instruction. The receipt image management system as described in claim 8, wherein when the login data does not match the multiple user account data, the login interface does not agree with the processing system to modify one of the multiple user data; and when the login data matches one of the multiple user account data, the login interface agrees with the processing system to modify one of the multiple user data according to the account data modification instruction.

Images