JP7142669B2 - Expense reimbursement system, method and program - Google Patents

Description

The present invention relates to an expense settlement system, method and program. More specifically, the present invention provides an expense reimbursement system, method, and program for preventing unauthorized use of business credit cards, etc.

Japan's population and working-age population are expected to decline in the future. For this reason, domestic companies are faced with management challenges of improving productivity and securing human resources. Under such circumstances, many companies are working on work style reforms, or are showing interest in future efforts (Non-Patent Document 1). According to Non-Patent Literature 1, the objectives that are emphasized in efforts for work style reform include improving employee motivation, improving productivity, and responding to compliance.

As an example of work style reform efforts, an increasing number of companies are considering radically reviewing the workflow for expense reimbursement and travel expense reimbursement, and promoting cashless and digitalization at the same time. In conventional expense reimbursement and travel expense reimbursement, paper use in application and approval work, advance payment by employees, and post-reimbursement with receipts are performed, which is very difficult for employees, their superiors, and people in the accounting department. It was a time-consuming procedure, and there was a risk of falsification in that procedure.

In some cases, an expense reimbursement system using corporate cards (Patent Document 1) was introduced to eliminate replacement payments by employees, but it did not fundamentally change the workflow for expense reimbursement and travel expense reimbursement. .

JP 2004-341858 A

Teikoku Databank, Ltd., "Special Project: Corporate Awareness Survey on Work Style Reform (December 2019)", January 16, 2020 Government Public Relations Office, Cabinet Office, "Overview of ``Public Opinion Survey on Safety and Security of Credit Card Transactions,'' published in September 2016.

There are various types of credit cards for businesses, such as business cards for sole proprietors and small and medium enterprises, corporate cards and purchasing cards for large companies, and debit cards for corporations. , corporate prepaid cards, etc. Although business credit cards are convenient for companies, their introduction has not progressed. As one of the reasons for this, according to Non-Patent Document 2, about 58% of people answered that they do not want to actively use credit cards, and the reason for this is illegal use of credit cards. For this reason, there is a strong need for stronger measures against unauthorized use of cards.

In the workflow of expense reimbursement and travel expense reimbursement, cashless and digitization has not progressed, and there have been cases of fraudulent use such as deception of expense reimbursement including use of personal expenses, and rule violations due to lack of understanding of travel expense regulations. . Preventing such unauthorized use has become an important matter for companies.

SUMMARY OF THE INVENTION The present invention has been made to solve such problems, and it is an object of the present invention to provide an expense reimbursement system, method, and program that prevent unauthorized use.

In order to solve the above problems, an expense reimbursement system that prevents unauthorized use, which is one aspect of the present invention, includes:
receiving an inquiry message associated with the first user from the merchant terminal;
Usage control information corresponding to the card number is read based on the card number included in the inquiry message, and the usage control information is an expense usage application associated with the first user and approved by the second user. It is set based on the expense utilization application submitted,
Compare one or more of the period information, location information, amount information, member store business code, and face-to-face/non-face-to-face information included in the inquiry message with the corresponding information stored in the usage control information. ,
Sales data associated with the approved card payment is received from the member store terminal and stored as card usage detail information on the condition that it is determined to approve the card payment based on the inquiry message as a result of the comparison. death,
The card usage detail information is configured to be sent to an accounting system for settlement processing.

According to the present invention, it is possible to set the amount of money, place, period, etc. that can be used for each business credit card or the like, so that it becomes possible to issue an alert notification or restrict card usage when fraudulent use is made. Further, according to the present invention, it is possible to provide a series of workflows and functions from prior application/approval of expense use, card control, and interlocking with an accounting system in one system. Furthermore, according to the present invention, it becomes possible to monitor the card user's usage details and usage restriction information in real time.

A detailed understanding of the embodiments disclosed herein can be obtained from the following description, taken in conjunction with the accompanying drawings.
1 is a configuration diagram of an entire system including an expense settlement system, a member store terminal, a user terminal and an accounting system according to an embodiment of the present invention; FIG. 1 is a system configuration diagram of an expense settlement system according to an embodiment of the present invention; FIG. It is a figure which shows an example of the data structure of the user master based on embodiment of this invention. It is a figure which shows an example of the data structure of the member store master which concerns on embodiment of this invention. It is a figure which shows an example of the data structure of the application content which concerns on embodiment of this invention. 4 is a diagram showing an example of the data structure of usage control information according to the embodiment of the present invention; FIG. It is a figure which shows an example of the data structure of the card usage statement which concerns on embodiment of this invention. 1 shows a processing flow for setting employee card use control based on the content of an expense application made by an employee and approved by the superior. A processing flow that judges whether the employee's actual card usage matches the content of the expense request, and if it matches, performs the settlement process, and if it does not match, processes the unusable process. indicates A processing flow for performing expense application after the fact and performing settlement processing based on the content of the application is shown. FIG. 4 is a diagram illustrating a management screen displaying card user application details, card usage details, and usage restriction information according to the embodiment of the present invention.

(overall structure)
FIG. 1 is a configuration diagram of an entire system including an expense settlement system 10, a member store terminal 11, a user terminal 12 and an accounting system 13 according to an embodiment of the present invention. The expense settlement system 10 is connected to a member store terminal 11, a user terminal 12 and an accounting system 13 so as to be able to communicate with each other. Although only one member store terminal 11, one user terminal 12 and one accounting system 13 are shown in FIG. For example, user terminals 12 include, but are not limited to, user terminal 12-1 used by employees of a company, user terminal 12-2 used by an employee's superior, and user terminal 12-2 used by an accountant. Terminal 12-3 may be included.

The expense reimbursement system 10 provides an expense reimbursement application/approval function, a card usage control function associated with approval details, and an expense reimbursement processing function based on card usage data.

With regard to the expense reimbursement application/approval function, the expense reimbursement system 10 receives application data for expense use from the user terminal 12-1 associated with the employee of the company, and notifies the superior of the employee of the existence of the application data. , the approval result for the application data made by the user terminal 12-2 associated with the employee's superior can be sent to the user terminal 12-1.

Regarding the card usage control function associated with the approval content, the expense reimbursement system 10 controls usage such as the amount, location, industry, method (face-to-face/non-face-to-face) and period of use based on the positive approval result for the application data. setting control information, performing authorization (processing for determining whether card payment is possible) based on information contained in an inquiry message received from the member store terminal 11, and transmitting the determination result to the member store terminal 11; An alert notification or usage restriction can be performed for card usage that is not permitted in light of the usage control information. Note that "face-to-face" means card settlement at an actual store or the like, and "non-face-to-face" means card settlement at a shop or the like on the Internet.

Regarding the settlement processing function based on card usage data, the expense settlement system 10 receives sales data from the member store terminal 11 and stores it as card usage statement data. The sales data is transmitted to the expense settlement system 10 after the card member enters the personal identification number at the member store terminal 11 after authorization or signs the issued sales slip. After that, the expense settlement system 10 transmits the card usage detail data to the accounting system 13 for settlement processing.

The accounting system 13 generates journal data based on the received card usage statement data and executes settlement processing. The accounting system 13 may exist inside the expense settlement system 10, or may be an external system connected via a network as shown in FIG. 1, and is not limited.

Although the expense settlement system 10 is described herein as one system or device, the various processes performed by the expense settlement system 10 may be configured to be distributed among multiple systems or devices. .

The member store terminal 11 may be a card payment terminal installed at the storefront of the member store, capable of processing payment by card, or may be a system for electronic commerce operated by the member store. There may be. The member store terminal 11 may be incorporated in a POS terminal.

The member store terminal 11 transmits an inquiry message for authorization to the expense reimbursement system 10 and receives the determination result (for example, approval or disapproval). The member store terminal 11 transmits the sales data to the expense reimbursement system 10 when approved.

The user terminal 12 is a terminal used by company employees, their superiors, accountants, and the like, and can be a computer with communication functions such as a personal computer (PC), but a specific device or device.

(System configuration)
FIG. 2 is a system configuration diagram of the expense settlement system 10 according to the embodiment of the present invention. As shown in FIG. 2, the expense settlement system 10 includes a control unit 101, a main storage unit 102, an auxiliary storage unit 103, and an interface (IF) unit 104, which are interconnected by a bus 120 or the like, like a general computer. , and an output unit 105 . The auxiliary storage unit 103 stores a program implementing each function of the expense settlement system 10 and data handled by the program. Auxiliary storage unit 103 includes user master 106, member store master 107, application details 108, usage control information 109, and card usage details 110 in the form of a file/database. Each program stored in the auxiliary storage unit 103 is executed by the expense settlement system 10 .

The control unit 101, also called a central processing unit (CPU), controls each component of the expense reimbursement system 10 and calculates data. and execute it. The main storage unit 102 is also called a main memory, and stores various types of received data, computer-executable instructions, data after arithmetic processing according to the instructions, and the like. The auxiliary storage unit 103 is a storage device typified by a hard disk (HDD), and is used for long-term storage of data and programs.

The embodiment of FIG. 2 describes an embodiment in which the control unit 101, the main storage unit 102 and the auxiliary storage unit 103 are provided inside the same computer. By using a plurality of main storage units 102 and auxiliary storage units 103, it is also possible to realize parallel distributed processing by a plurality of computers. As another embodiment, it is also possible to install a plurality of servers for the expense settlement system 10 and share one auxiliary storage unit 103 among the plurality of servers.

The IF unit 104 serves as an interface for transmitting and receiving data to and from other systems and devices, and also provides an interface for receiving various commands and input data (various masters, tables, etc.) from the system operator. The output unit 105 provides a display screen for displaying processed data, printing means for printing the data, and the like.

The user master 106 stores information of users (e.g., company employees, their superiors, accountants, etc.) who use the expense settlement system 10 according to the present invention.

FIG. 3 is a diagram showing an example of the data structure of the user master 106 according to the embodiment of the invention. User master 106 may include user ID 301, user information 302, company ID 303, route information 304, and card number 305, but is not limited to these data items and may include other data items. is.

The user ID 301 is an identifier that identifies a user who uses the expense settlement system 10 according to the present invention. User information 302 indicates information related to the user, such as the user's name, password, and contact information (including email address). Company ID 303 is the identifier of the company to which the user belongs. The route information 304 indicates the route through which the expense claim is routed in the expense settlement system 10 according to the present invention. In the route information 304, for example, if the user ID 301 is an employee, the direct superior is designated as the next route for sending the expense request. The designation of superior may be set based on the company ID 303 and the user ID 301 . The card number 305 indicates the card number of a business credit card or the like used by the user.

Returning to FIG. 2, the member store master 107 is a master file that stores member store information. FIG. 4 is a diagram showing an example of the data structure of the member store master 107 according to the embodiment of the present invention. The merchant master 107 can include merchant ID 401, merchant name 402, location 403, and industry code 404, but is not limited to these data items and can include other data items. be.

A member store ID 401 is an identifier that identifies a member store. The member store name 402 indicates the name of the member store. The location 403 is information indicating the location of the member store. The business type code 404 is information indicating the business type of the member store (for example, airline, restaurant, etc.).

Returning to FIG. 2, the application content 108 stores data representing the content of the expense use application. The application for use of expenses should be made before the expenses are actually used, but in some cases it may be done after the fact. FIG. 5 is a diagram showing an example of the data structure of application content 108 according to the embodiment of the present invention. Application content 108 may include, but is not limited to, application ID 501, application content 502, duration 503, location 504, amount 505, approval flag 506, and post-application information 507. It can also contain data items.

The application ID 501 is an identifier that identifies the expense use application made by the employee. The application content 502 indicates the content of the expense use application made by the employee. For example, the application content 502 is "I will travel to the United States during the period from September 1 to 10, 2020, and visit company A and its factory in XX state. is 500,000 yen." A period 503 indicates the period during which the expenses are used, extracted from the application content 502 .

A place 504 indicates a place to use the expense extracted from the application content 502 . The amount 505 indicates the amount of expenses to be used extracted from the application content 502 . Approval flag 506 indicates whether the application has been approved or denied. Post-application information 507 includes a flag indicating post-application data and information specifying the corresponding card usage statement that has already been used.

Returning to FIG. 2, the usage control information 109 stores information about restrictions on usage of credit cards for business operators and the like. FIG. 6 is a diagram showing an example of the data structure of usage control information 109 according to the embodiment of the present invention. Usage control information 109 can include card number 305, usage period 601, usage location 602, usage amount 603, usage type 604, and usage method 605, but is limited to these data items. It can contain other data items as well.

The card number 305 indicates the card number of the business credit card or the like used by the employee, as described with reference to FIG. The usable period 601 indicates the period during which payment can be made with a business credit card or the like. The usable place 602 indicates a place where payment can be made with a business credit card or the like, such as one or more specific member store IDs, a specific area (country, address, etc.).

The available amount 603 indicates the amount that can be settled with a business credit card or the like. The usable business type 604 indicates the business type (for example, airlines, restaurants, etc.) that can be settled with a business credit card or the like. The available method 605 indicates the method (face-to-face, non-face-to-face) that can be settled with a business credit card or the like.

Returning to FIG. 2, the card usage statement 110 stores card settlement information. FIG. 7 is a diagram showing an example of the data structure of the card usage details 110 according to the embodiment of the present invention, and the data structure of the card usage details 110 may follow a known format.

Card usage details 110 can include transaction ID 701, card number 305, transaction date 702, merchant ID 401, and payment amount 703, but are not limited to these data items and other data items. can be included.

Since the card number 305 and member store ID 401 are as described above, detailed description thereof will be omitted. The transaction ID 701 is an identifier that identifies a card payment transaction, and is also called a slip number. Transaction date 702 indicates information on the date when the card payment was made. The settlement amount 703 indicates the settlement amount of the card settlement transaction.

Next, referring to FIGS. 8 and 9, fraudulent use can be prevented by enabling payment with a business credit card or the like when the expense payment conditions that have been applied for in advance are met. Explain the scheme of the expense reimbursement system. The processing flow of FIGS. 8 and 9 is a comprehensive mechanism provided by the expense settlement system according to the present invention, but for convenience of explanation, it will be described separately in FIGS. 8 and 9. FIG.

(Processing flow: advance application and card usage control setting processing)
FIG. 8 shows a processing flow in which the expense reimbursement system 10 sets the employee's card use control based on the content of the application approved by the superior for the expense application made by the employee.

At S801, the expense settlement system 10 receives advance application data for expense use from the user terminal 12-1. As mentioned above, user terminal 12-1 is a terminal associated with or used by an employee of an enterprise. The expense reimbursement system 10 stores the received advance application data in the application content 108 . The expense reimbursement system 10 makes an inquiry to the user master 106 based on the user ID 301 of the employee who accessed via the user terminal 12-1, and obtains application circulation route information (for example, company ID and user ID) from the route information 304. ID, etc.). The expense reimbursement system 10 reads out the contact information of the superior who is the referral destination from the user master 106 based on the acquired information on the referral route, and uses the read contact information to notify that there is an application. do.

In S802, the expense settlement system 10 reads the advance application data from the application content 108 in response to the access from the user terminal 12-2, and provides it to the user terminal 12-2. User terminal 12-2 is the terminal associated with or used by the employee's superior. The expense reimbursement system 10 receives the judgment result for the advance application data from the user terminal 12-2, and judges whether the judgment result indicates approval or denial. When indicating approval, the expense reimbursement system 10 sets a flag indicating approval in the approval flag 506 of the application data, and the process proceeds to S803. On the other hand, when indicating denial, the expense reimbursement system 10 sets a flag indicating denial in the approval flag 506 of the application data, and transmits a notification to the employee who made the advance application indicating that the application has been denied. do. If denied, the employee reapply in S801.

In S803, the expense reimbursement system 10 reads the approved advance application data from the application content 108, and obtains the usage period 601, the usage location 602, the usage amount 603, the usage type 604, and the usage control information 109 in the usage control information 109. Information corresponding to each possible method 605 is set.

With the above-described processing, the expense reimbursement system 10 enables settlement with a business credit card or the like when the expense payment conditions for which an expense use application has been applied in advance are met, thereby preventing unauthorized use of the business credit card or the like. be able to prevent it.

(Processing flow: Card usage determination and settlement processing)
In FIG. 9, the expense reimbursement system 10 determines whether or not the contents of the expense application match the employee's actual use of the card, and if they match, the expense reimbursement system 10 performs reimbursement processing, and if they do not match. In this case, a processing flow for performing use-disabling processing is shown.

At S<b>901 , the expense settlement system 10 receives an inquiry message from the member store terminal 11 . The inquiry message is a message that is sent to determine whether card payment is possible when a card user (employee in this embodiment) makes a card payment at a member store in Japan or overseas. The inquiry message includes card number, amount information, period information (including settlement date), country code, merchant ID, merchant name, merchant location, merchant industry code, face-to-face/non-face-to-face information, etc. However, it is not limited to these, and other information may be included.

The process of determining whether card payments are possible is called authorization. Authorization generally asks whether the merchant terminal is valid, whether the merchant is normal, whether the card is valid (i.e. not canceled, etc.), whether it fits within the usage limit, and whether the member's credit status is good. Determinations are made with respect to security and premature credit (i.e., is there any overdue, etc.), is there a risk of counterfeiting and misuse, and so on. In addition to these, the expense reimbursement system 10 of the present invention can determine whether or not the contents of the card payment are used as requested in advance, or whether they conflict with the administrator's preset settings. The administrator's pre-setting refers to usage control information set without going through expense request and approval. For example, as a pre-setting by the administrator, the usage limit of an employee's business credit card, etc. is always set to 0 yen, or the usage limit for one month is set to 50,000 yen. It is possible. The expense reimbursement system 10 can provide the user terminal 12 with a screen for presetting the administrator.

At S902, the expense settlement system 10 inquires of the usage control information 109 based on the card number included in the inquiry message, and reads usage control information corresponding to the card number. The expense reimbursement system 10 includes one or more of the period information, location information (country code, member store location), amount information, member store industry code, and face-to-face/non-face-to-face information included in the inquiry message, and to the usage control information 109. Compare corresponding stored information. As a result of the comparison, the expense reimbursement system 10 determines whether to approve (not control usage) or deny (control usage) the card settlement based on the inquiry message. If the usage is to be controlled, the process proceeds to S903, and if the usage is not to be controlled, the process proceeds to S904.

In S903, the expense reimbursement system 10 notifies the member store terminal 11 of the denial of settlement, inquires of the user master 106, and obtains the contact information of the card user (employee) and his superior. Get alerts to card users (employees) and their superiors based on the acquired contact information. The notified alert may indicate that the card payment was denied and that the card payment details do not match one or more of the expense requisition details.

In another embodiment of the present invention, the expense settlement system 10 approves the card payment itself and notifies the member store terminal 11 that the payment can be made even if it is determined to be denied, and then Alerts can also be sent to card users (employees) and their superiors. The alert notified may indicate that the card payment details do not match one or more of the expense claim details, but the card payment itself will be made. In such a case, since the card settlement itself can be performed, it is possible to transmit the card usage detail information to the accounting system 13 in S905 as will be described later.

In S904, the expense reimbursement system 10 notifies the member store terminal 11 of the approval of the payment, receives sales data associated with the approved card payment from the member store terminal 11, and records the card usage details 110. store in

In S<b>905 , expense settlement system 10 reads the card usage details information from card usage details 110 and transmits it to accounting system 13 . The accounting system 13 generates journal data based on the received card usage statement information and executes settlement processing.

With the above-described processing, the expense settlement system 10 sets the amount of money, place, period, etc. that can be used for each business credit card, etc., so when a card payment that violates the application content occurs, an alert notification or usage restriction is issued. be able to do it. 8 and 9, the expense reimbursement system 10 can provide a series of workflows and functions, including prior application/approval of expense usage, card control, and interlocking with an accounting system, in one system. become.

(Processing flow: Subsequent application and settlement processing)
FIG. 10 shows a processing flow in which the expense reimbursement system 10 submits an expense application after the actual use of the card by an employee who did not apply for expense use in advance, and performs reimbursement processing based on the contents of the application. .

At S1001, the user terminal 12-1 accesses the expense settlement system 10 and acquires card usage statement information associated with the employee's card number 305 from the card usage statement 110. FIG. The user terminal 12 - 1 identifies target data for post facto application from among the acquired card usage detail information, and transmits post facto application data for expense use associated with the identified object data to the expense settlement system 10 . A post-application is made when there is a use of expenses that was not anticipated in the prior application described with reference to FIGS. 8 and 9. FIG.

The expense reimbursement system 10 stores the received post-application data in the application content 108 . In the post-application information 507, a predetermined value is set in a flag indicating post-application data, and information (for example, transaction ID 701) specifying the identified card usage statement information is set.

The expense reimbursement system 10 makes an inquiry to the user master 106 based on the user ID 301 of the employee who has accessed through the user terminal 12-1, reads out the route information 304, and acquires the information on the circulation route of the application. The expense reimbursement system 10 reads out the contact information of the superior who is the referral destination from the user master 106 based on the acquired information on the referral route, and uses the read contact information to notify that there is an application. do.

In S1002, the expense settlement system 10 reads post-application data from the application contents 108 in response to the access from the user terminal 12-2, and provides it to the user terminal 12-2. User terminal 12-2 is the terminal associated with or used by the employee's superior. The expense reimbursement system 10 receives the judgment result for the post-application data from the user terminal 12-2, and judges whether the judgment result indicates approval or denial. When indicating approval, the expense reimbursement system 10 sets a flag indicating approval in the approval flag 506 of the application data, and the process proceeds to S1003. On the other hand, when indicating denial, the expense reimbursement system 10 sets a flag indicating denial in the approval flag 506 of the application data, and transmits a notification to the employee who made the advance application indicating that the application has been denied. do. If denied, the employee reapply in S1001.

At S<b>1003 , expense settlement system 10 reads target card usage details information from card usage details 110 based on post-application information 507 of the approved application data, and transmits it to accounting system 13 . The accounting system 13 generates journal data based on the received card usage statement information and executes settlement processing.

The expense reimbursement system 10 of the present invention responds to a request from the user terminal 12, and manages and manages to display the card user's (employee's) application details, card usage details, and usage restriction information, as shown in FIG. A screen 1100 can be provided. Through the management screen 1100, it becomes possible to monitor the card user's usage details and usage restriction information in real time. The management screen 1100 includes application details 1101, card usage details 1102, and usage restriction information 1103, but may be configured to display other information.

The application content 1101 displays the information of the application content 502 . The card usage details 1102 are the contents included in the inquiry message received in S901, such as card number, amount information, period information (including settlement date), country code, member store ID, member store name, member store location. , member store industry code, face-to-face/non-face-to-face information, etc. The usage restriction information 1103 displays usage period 601 , usage location 602 , usage amount 603 , usage type 604 , and usage method 605 .

When performing usage control, the expense settlement system 10 may visually indicate the data item causing the usage control on the data item of the usage restriction information 1103, as shown in FIG.

In one embodiment of the present invention, the expense reimbursement system 10 can set the card user's usage limit to 0 yen. When the expense settlement system 10 receives a usage limit increase request from the user terminal 12-2 or the user terminal 12-3, it can update the usage limit of the corresponding card according to the requested amount, On the other hand, when a request to reduce the available credit limit is received, the credit limit of the corresponding card can be updated according to the requested amount. These operations may be performed through a screen for setting administrator preferences. As a result, the company does not allow employees to freely use business credit cards, etc., and controls the use of such cards so that they can be used only when the company approves. Note that the user terminal 12-3 is a terminal associated with, that is, used by, the company's accounting staff.

Although the principles of the present invention have been described with reference to exemplary embodiments, those skilled in the art will appreciate that various embodiments can be implemented that change in arrangement and detail without departing from the spirit of the invention. will understand. That is, the present invention can be embodied as, for example, a system, device, method, program, storage medium, or the like.

10 expense settlement system 11 member store terminal 12 user terminal 13 accounting system 101 control unit 102 main storage unit 103 auxiliary storage unit 104 interface (IF) unit 105 output unit 106 user master 107 member store master 108 application content 109 usage control information 110 card Usage details 1100 Management screen

Claims (5)

An expense reimbursement system that prevents fraudulent use by determining whether card settlement is possible based on an application for expense use that has been made in advance,
receiving an inquiry message associated with the first user from the merchant terminal;
Usage control information corresponding to the card number is read based on the card number included in the inquiry message, and the usage control information is an expense usage application associated with the first user and approved by the second user. is set each time the approval of the expense usage application is made based on the expense usage application submitted, and the expense usage application is made before the expense is actually used;
Compare one or more of the period information, location information, amount information, member store business code, and face-to-face/non-face-to-face information included in the inquiry message with the corresponding information stored in the usage control information. ,
Sales data associated with the approved card payment is received from the member store terminal and stored as card usage detail information on the condition that it is determined to approve the card payment based on the inquiry message as a result of the comparison. death,
sending the card usage statement information to an accounting system for settlement processing;
As a result of the comparison, on the condition that it is determined not to approve the card payment based on the inquiry message, the member store terminal is notified of the rejection of the payment, and the first user and the second user are notified of the rejection of the payment. Notify the first alert
An expense reimbursement system configured to: 2. The expense of claim 1 , wherein the first alert indicates that the card payment has been denied and that the details of the card payment do not match one or more of the details of the expense use application. clearing system. 3. The expense reimbursement system of Claim 1, wherein the location information is at least one of a country code and a merchant location. A method executed by an expense reimbursement system that prevents fraudulent use by judging whether or not a card payment can be made based on an application for expense use that has been made in advance,
receiving an inquiry message associated with the first user from the merchant terminal;
reading usage control information corresponding to the card number based on the card number included in the inquiry message, wherein the usage control information is an expense usage application associated with the first user; is set upon said approval of said expense application based on said expense application approved by a user of said expense application, said expense application being made prior to actual use of the expense;
Comparing one or more of period information, location information, amount information, member store industry code, and face-to-face/non-face-to-face information included in the inquiry message with corresponding information stored in the usage control information. When,
Sales data associated with the approved card payment is received from the member store terminal and stored as card usage detail information on the condition that it is determined to approve the card payment based on the inquiry message as a result of the comparison. and
transmitting the card statement information to an accounting system for settlement processing ;
As a result of the comparison, on the condition that it is determined not to approve the card payment based on the inquiry message, the member store terminal is notified of the rejection of the payment, and the first user and the second user are notified of the rejection of the payment. notifying a first alert;
How to prepare. A program for causing a computer to execute the method according to claim 4 .

Images