JP2020030799A - Settlement management system - Google Patents

Abstract

To provide information capable of more accurately identifying an inappropriate payer.SOLUTION: A settlement management system 1 registers settlement data input by a settlement data input section 11, aggregates the settlement data, and generates information indicating a payer performing a settlement matching conditions on the basis of a predetermined settlement pattern. Thus, since the settlement management system 1 aggregates the settlement data and outputs the information indicating the payer matching the conditions on the basis of the predetermined settlement pattern, an improper settlement candidate can be easily identified.SELECTED DRAWING: Figure 1

Description

  The present invention relates to an account management technique, and more particularly to a technique effective when applied to an account management system.

  Conventionally, when an employee who goes out to work is required to settle expenses such as transportation expenses when going out, the employee inputs the details of the expenses (such as the amount of settlement), and the settlement data is data based on the contents. To pay the expenses.

  In order to detect inappropriate payment (for example, improper payment) in expense settlement, there is a technique for totalizing settlement data. A technique for summarizing such adjustment data is described in, for example, Japanese Patent Application Laid-Open No. 2008-234412 (Patent Document 1). Specifically, Patent Document 1 discloses that a settler indicated by the settlement data and a unit period obtained by summarizing the date of occurrence indicated by the settlement data for each scheduled unit are used as aggregation items to cross the settlement amount indicated by the settlement data. Aggregate, calculate the total amount of settlement for each accountant, and create an aggregation table sorted in descending order of the total.

JP 2008-234412 A

  According to the technology described in Patent Document 1, by calculating the sum of the settlement amounts for each settlement person and sorting the results, it is possible to specify the settlement person with a high settlement amount. It may not be possible to identify those who make improper payments. For example, a settler with a high settlement frequency tends to have a high settlement amount even if it is not a fraudulent settler.

  Therefore, an object of the present invention is to provide a payment management system that provides information capable of more accurately specifying an improper payment user (a payment user who has a possibility of incorrect payment).

  The above and other objects and novel features of the present invention will become apparent from the description of the present specification and the accompanying drawings.

  The outline of a representative invention among the inventions disclosed in the present application will be briefly described as follows.

  A payment management system according to a representative embodiment of the present invention is a payment management system that manages payment data, and includes a payment data input unit that accepts input of payment data, and a payment data input unit that inputs payment data. An information generation unit that totals and generates information indicating a clearing person who is performing a payment that meets conditions based on a predetermined payment pattern.

  The effects obtained by typical aspects of the invention disclosed in the present application will be briefly described as follows.

  That is, according to the representative embodiment of the present invention, it is possible to provide information that can specify an inappropriate accountant more accurately.

BRIEF DESCRIPTION OF THE DRAWINGS It is the figure which showed the outline | summary about the structure of the payment management system which is embodiment of this invention. It is a figure showing the processing phase managed by the settlement management system which is an embodiment of the invention. FIG. 4 is a diagram illustrating an example of a pre-check and a post-check according to the embodiment of the present invention. It is a figure showing an example of application data in an embodiment of the invention. It is an example of a scatter diagram which the settlement management system in an embodiment of the invention outputs. It is a flowchart in the embodiment of this invention which shows the flow of the process which outputs the information which shows the candidate of an unauthorized accountant. It is a flowchart which shows the flow of the process which outputs scatter diagram information in Embodiment of this invention. It is a figure which shows the tendency of the settlement of daily allowance in embodiment of this invention.

  Hereinafter, the present embodiment will be described in detail with reference to the drawings. In all the drawings for describing the embodiments, the same portions are denoted by the same reference numerals in principle, and the repeated description thereof will be omitted. On the other hand, parts described with reference numerals in one drawing may be referred to with the same reference numerals, although not shown again, in the description of other drawings.

<Overview>
FIG. 1 is a diagram showing an outline of a configuration of a settlement management system 1 according to the present embodiment. The settlement management system 1 shown in FIG. 1 is a server device or the like. The settlement management system 1 can transmit and receive information to and from a terminal device 3 used by a user 2 (for example, a company employee) who is a settlement person via a network (not shown) such as a LAN (Local Area Network). The payment management system 1 is a system that receives payment data input by the user 2 via the terminal device 3 and manages the payment data. Here, the settlement data is data relating to a settlement request, and is data including information indicating a settlement person, settlement contents (category), payment date (including payment time), billing amount, and the like. It is assumed that the settlement data is appropriately associated with a separately requested business trip application.

  The payment management system 1 aggregates the payment data that has been input for each payment content (category) and each user, and generates information indicating a payment clerk who meets conditions based on a predetermined payment pattern. Here, the condition based on the predetermined payment pattern is a condition having a probability of incorrect payment or the like. In addition, the settlement pattern is a settlement method that has a high possibility of improper settlement if the frequency is high, and is, for example, a settlement by manual input.

  Note that the settlement management system 1 uses information (for example, a scatter diagram) that can be compared based on the frequency and total amount of settlement status of other users as information indicating a settlement person who meets conditions based on the predetermined settlement pattern. Etc.) may be output.

  In the settlement management of a company or the like, it is generally necessary to obtain the approval of the superior of the user 2 who made the application in order to prevent improper application or erroneous application. In the settlement management system 1 according to the present embodiment, even if the confirmation work such as the above-described approval of the superior is omitted or simplified, a process of appropriately managing the confirmation work is performed.

  For example, the settlement management system 1 suppresses or detects improper application / erroneous application in three phases of “preliminary check”, “visualization”, and “post-check” as shown in FIG. First, as a “prior check”, the payment management system 1 simply checks whether the input payment data is appropriate before registering the payment data input by the terminal device 3. For example, the payment management system 1 checks whether or not the transaction date (payment date) in the input payment data is appropriate.

  As “visualization”, the settlement management system 1 determines whether or not the settlement data input by the terminal device 3 deviates from the pre-stored settlement reference data. (Flag information) is registered so that information including the flag information can be referred to members of the accounting department and the superior of the department to which the applicant belongs. Here, the settlement reference data is data that defines a reference (settlement pattern) relating to settlement contents (category), and is information for determining whether the settlement is appropriate.

  As a “post-check”, the payment management system 1 aggregates the registered payment data for each payment content and each user 2 and provides information (eg, a scatter diagram) that can be compared with the billing status of other users 2. Provides information that can identify a user 2 (an unauthorized accountant candidate) who has a possibility of improper account settlement (information for specifying an accountant who performs account settlement that meets conditions based on a predetermined account settlement pattern). I do. In addition, as a “post-check”, the settlement management system 1 provides information that can be used to check in detail the past settlement of a fraudulent accountant candidate.

  Here, an example of the pre-check and the post-check will be described with reference to FIG. As shown in FIG. 3, the contents (category) of the settlement include "train / bus", "taxi / highway bus", "Shinkansen / Limited Express", "flight ticket", and "accommodation cost". The category is not limited to the above, and a drinking party (banquet) in which a plurality of people participate may be included as a category. In this case, it is conceivable that the settlement data also includes the names of the participants.

  For example, in the case of “taxi / highway bus”, a warning message (warning) is output as a pre-check if the transaction day is a weekend, a holiday, or a holiday (that is, a day that is not considered to be a business day). As a post-check, matching is performed with business hours data. For example, it is checked whether or not the number of times of using a taxi is greater than that of other office workers, even though the work end time is not midnight.

  Also, in the case of "accommodation cost", as a preliminary check, it is checked whether or not the accommodation is other than the standard arrangement (standard settlement plan). Here, the standard arrangement indicates a predetermined recommended accommodation plan (for example, an accommodation plan recommended by a travel agency). In addition, as a post-check, employees who have a large number of cases and large amounts of money by region are checked. This number may be the number of accommodations other than the standard arrangement. In addition, as a post-check, employees near the predetermined upper limit are checked or matched with business hours data.

  Returning to FIG. 1, the details of the settlement management system 1 will be described. The settlement management system 1 is configured by, for example, a server device or a virtual server constructed on a cloud computing service as described above. The settlement management system 1 also includes an OS (Operating System), a DBMS (DataBase Management System), and a Web server program developed on a memory from a recording device such as a HDD (Hard Disk Drive) by a CPU (Central Processing Unit) not shown. And other middleware, and the software running on it. As a result, various functions described later relating to management of the adjustment data received from the terminal device 3 are realized.

  The settlement management system 1 includes, for example, each unit such as a settlement data input unit 11, a settlement data registration unit 12, and an information generation unit 15 implemented as software. The settlement management system 1 includes a settlement data DB 13 implemented by a database, a file, a memory table, and the like, a settlement reference data DB 14 (a settlement reference information storage unit), and the like.

  The payment data input unit 11 is a part that receives the input of payment data. Specifically, the payment data input unit 11 receives the input of the payment data from the terminal device 3. For example, when accepting payment from the terminal device 3 of the user 2 who has paid using a credit card distributed by the company, the payment data input unit 11 transmits the credit card from the credit card company to the user 2. The used information is acquired, and a payment target is selected from a list or the like from the information and an input is received.

  When accepting the payment from the terminal device 3 of the user 2 who has paid using the transportation IC card distributed from the company or the like, the payment data input unit 11 transmits the information stored in the transportation IC card to the public. And the user is allowed to select a payment target from a list or the like from the information and accept an input.

  As described above, the payment management system 1 acquires paid data such as a credit card and a transportation IC card, and receives an input based on the acquired data. As a result, the settlement management system 1 can prevent improper settlement or erroneous settlement by receiving data proved that payment was actually made.

  The settlement data input unit 11 does not use the data linked to the credit card or the transportation IC card as described above, but performs the settlement based on the information (manually input information) input from the user 2 of the terminal device 3. Data input may be accepted. It is assumed that the payment management system 1 recommends that data be input using data linked to a credit card or a transportation IC card.

  The terminal device 3 inputs payment data including an application date, an affiliation, a name, a payment date (including a payment time), an expense type (a category indicating payment details), a payee, an amount, and the like. The settlement data input unit 11 accepts the input of the settlement data in response thereto.

  Note that the settlement data input unit 11 may be configured to select an expense type, a payee, and the like from a list or the like and receive the input. As a result, it is possible to prevent the input contents from being skewed.

  When the expense type is accommodation, the settlement data input unit 11 accepts input of information indicating whether or not accommodation is standard arrangement accommodation.

  Note that the settlement data input unit 11 may output a warning message (warning) as a preliminary check when the payment date is a holiday or when the accommodation is not a standard arrangement.

  When receiving the payment data input by the terminal device 3, the payment data input unit 11 sends the payment data to the payment data registration unit 12. The settlement data input unit 11 sends the settlement data to the settlement data registration unit 12 together with information indicating whether or not a manual input has been made.

  The settlement data registration unit 12 is a part for registering the settlement data input by the settlement data input unit 11. When the payment data registration unit 12 acquires payment data from the payment data input unit 11, the payment data registration unit 12 registers the payment data in the payment data DB 13. In addition, the adjustment data registration unit 12 stores information indicating whether or not the accommodation is of standard arrangement in the input adjustment data, and indicates that the accommodation is not accommodation of standard arrangement. Registration) with flag information indicating other than "use".

  The payment data DB 13 is a database that stores payment data registered by the payment data registration unit 12.

  The settlement reference data DB 14 is a database that stores, for each settlement content, settlement reference information that defines a reference for the settlement.

  For example, the settlement reference data DB 14 stores settlement reference information such as a threshold amount of each settlement content and a transaction date of a warning in each settlement content. When the category is train use, information based on use on weekdays (other than holidays) is stored as settlement reference information. When the category is taxi use, information based on non-use at midnight (for example, after 23:00) is stored as a settlement reference.

  When the category is accommodation, information based on standard use (standard arrangement accommodation) is stored as settlement reference information. When the category is accommodation, information on the basis that the accommodation reference amount is less than 30,000 yen per night is stored as settlement reference information.

  In addition, regardless of the category, information based on non-manual input is stored as settlement reference information.

  The information generation unit 15 sums up the adjustment data input by the adjustment data input unit 11 and generates information indicating an accountant (user 2) performing an adjustment that meets conditions based on a predetermined adjustment pattern. Part.

  For example, the information generation unit 15 compares the adjustment data registered in the adjustment data DB 13 with the adjustment reference information corresponding to the content of the adjustment data among the adjustment reference information stored in the adjustment reference data DB 14. (Flag information) based on the information.

  The information generating unit 15 generates the flag information at a timing when the adjustment data is registered to some extent (for example, once a week). That is, the information generation unit 15 regenerates the flag information at each predetermined timing.

  For example, when the category of the adjustment data stored in the adjustment data DB 13 is train use (train / bus), the information generation unit 15 outputs the adjustment reference information in the case where the category is train use from the adjustment reference data DB 14. get. As described above, when the category is train use, since the settlement reference information based on the use of weekdays is stored, the information generating unit 15 determines that the payment date of the settlement data stored in the settlement data DB 13 is Determine if it is a weekday. When the payment date of the settlement data is a holiday, the information generation unit 15 adds information indicating “use of holiday” as flag information to the settlement data. As described above, as a result of comparing the payment date of the settlement data with the settlement reference information, if the criterion of the settlement reference information is not satisfied, the information generation unit 15 may have a problem with the settlement data. Information indicating "holiday use" is added to the settlement data.

  When the category of the adjustment data stored in the adjustment data DB 13 is taxi use, the information generation unit 15 acquires from the adjustment reference data DB 14 the adjustment reference information when the category is taxi use. As described above, when the category is taxi use, since the settlement reference information based on non-night use is stored, the information generation unit 15 sets the payment time of the settlement data stored in the settlement data DB 13. Is determined to be midnight (for example, after 23:00).

  When the payment time of the settlement data indicates midnight, the information generating unit 15 adds information indicating “use at midnight” as flag information to the settlement data. As described above, as a result of comparing the payment time of the settlement data with the settlement reference information, if the criterion of the settlement reference information is not satisfied, the information generation unit 15 may have a problem with the settlement data. Information indicating "midnight use" is added to the settlement data.

  For example, when the category of the adjustment data stored in the adjustment data DB 13 is accommodation, the information generation unit 15 acquires, from the adjustment reference data DB 14, the adjustment reference information when the category is accommodation use.

  As described above, when the category is accommodation use, since the settlement reference information based on non-expensive use is stored, the information generating unit 15 determines whether the amount of the settlement data stored in the settlement data DB 13 is Determine if it is expensive. When indicating that the amount of the settlement is high, the information generating unit 15 adds information indicating “high-price use” as flag information to the settlement data. As described above, if the information generation unit 15 compares the amount of the settlement data with the settlement reference information and does not satisfy the criterion of the settlement reference information, the settlement data may have a problem. Information indicating "expensive use" is added to the data.

  When the category is accommodation use, since information based on standard use (standard arrangement accommodation) is stored as settlement reference information, the information generation unit 15 stores the information in the settlement data DB 13. It is determined whether or not the settlement data is for standard use. If the settlement data is not for standard use, information indicating “out of standard use” is added to the settlement data as flag information. This is because the use of the standard use route set in advance in the settlement management system 1 may involve an improper incentive.

  In addition, the information generation unit 15 assigns information indicating “manual input” as flag information to manually-entered adjustment data based on information based on the fact that no manual input is performed for all categories based on the adjustment reference information. .

  Here, FIG. 4 illustrates an example of the adjustment data after the information generation unit 15 generates the flag information. FIG. 4 is a diagram illustrating an example of a record of the payment data stored in the payment data DB 13.

  The record R1 is a record of payment data in which the category (expense type) is accommodation. In the example of the record R1, the usage amount is 100,000 yen, which is a high-priced usage, and thus the flag information of the high-priced usage of the confirmation point is set. The record R1 is also provided with flag information indicating that the record is out of standard use.

  The record R2 is a record of the adjustment data whose category is train travel. In the case of the example of the record R2, since the payment date is a holiday (Saturday), the flag information of the confirmation point using the holiday is set. In addition, flag information indicating that the record R2 has been manually input is also set.

  The record R3 is a record of payment data whose category is taxi use (note that the payment time is a time indicating midnight). In the case of the example of the record R3, since the payment time on the payment day is midnight, flag information of the midnight use of the confirmation point is set.

  The record R4 is a record of payment data whose category is accommodation. In the example of the record R4, since the usage is standard and the usage amount is not high, no flag information is set in the confirmation point.

  The information generating unit 15 displays and outputs a record as shown in FIG. 4 to various devices at a predetermined timing. For example, the information generation unit 15 transmits and outputs a record as shown in FIG. 4 to a terminal device of an accounting department in charge or a manager of each department (not shown), and causes the record to be displayed and output. Thereby, the settlement management system 1 can realize the above-described “visualization”.

  Further, the information generation unit 15 may perform statistical processing on the flag, and transmit and output information based on the result of the statistical processing to the terminal device of the accounting department charge or the manager of each department.

  For example, the information generation unit 15 counts the number of flags (the number of flags) set for each accountant for the adjustment data stored in the adjustment data DB 13 at a predetermined timing, and stores the number of flags in advance. The payment data of the clearer who is equal to or greater than the threshold value may be transmitted and output to the terminal device of the accounting department or the manager of each department.

  In this case, the information generation unit 15 can extract a candidate of an unauthorized accountant who is likely to be an unauthorized accountant, and can output adjustment data of the candidate of the unauthorized accountant.

  Specifically, the information generation unit 15 counts the number for which the flag for manual input is set and the number of settlement applications for each accountant, and the ratio of manual input is high (for example, 100 Among them, the settlement data of the accountant is sent and output to the terminal device of the accounting department charge or the manager of each department. In addition, the information generation unit 15 aggregates the number of the flag indicating non-standard use and the number of settlement applications in the settlement of the accommodation category for each settler, so that the settler having a high ratio of non-standard use is calculated. The accounting data is transmitted and output to the terminal of the accounting department or the manager of each department.

  In addition, the information generation unit 15 uses the adjustment data registered in the adjustment data registration unit 12 to provide information indicating a fraudulent settlement candidate based on the billing frequency and billing amount of each settler for the predetermined settlement content. Generate and output the information.

  For example, the information generating unit 15 outputs a scatter diagram based on the billing frequency and the billing amount of each biller as information indicating an improper billing candidate.

  For example, the information generating unit 15 outputs, as information indicating a fraudulent settlement candidate, a scatter diagram based on the billing frequency of a certain category (for example, using a taxi) of each biller and the sum of the billing amount of the category.

  When generating a scatter diagram relating to taxi use, the information generating unit 15 refers to the settlement data in the settlement data DB 13 to obtain records in which the category of each accountant is taxi use, and determines the number of records and the number of records. Calculate the total amount of the records (total amount charged) and generate a scatter chart based on the calculated result. In the case of this scatter diagram, the vertical axis is the sum of billing amounts, the horizontal axis is frequency, and points indicating each claimant are plotted based on the billing amount and frequency.

  In addition, the information generating unit 15 includes, as information indicating the fraudulent settlement candidate, a billing frequency other than the standard use of the accommodation type of each settlementr (a frequency not using a predetermined standard settlement plan) and a billing due to the accommodation. A scatter diagram based on the total amount of money may be output.

  In this case, the information generating unit 15 refers to the settlement data in the settlement data DB 13 to obtain a record in which the category of each settlement person is staying, and obtains the number of flags for which non-standard use flag information is set in the record. And the sum of the amounts of money of records in which flag information other than the standard use is set (total amount of charges), and generates a scatter diagram based on the calculated result. In the case of this scatter diagram, the vertical axis is the sum of billing amounts, the horizontal axis is frequency, and points indicating each claimant are plotted based on the billing amount and frequency.

  Here, FIG. 5 shows an example of a scatter diagram generated by the information generating unit 15. As shown in FIG. 5, the vertical axis is the sum of the billing amounts, and the horizontal axis is the frequency (number of times). In this case, the payer corresponding to the point 5 indicates that the amount is higher, though less frequent, than other payers. Therefore, there is a possibility that the accountant corresponding to point 5 is an unauthorized accountant. Further, the payer corresponding to the point 6 has a higher frequency and money amount than other payers. Also in this case, there is a possibility that the user is an unauthorized accountant.

  As described above, the information generating unit 15 generates and outputs a scatter diagram based on the frequency and the billing amount, thereby providing information that can identify a clearer who may have performed improper payment at a glance. can do.

  Further, when each point of the scatter diagram is selected at the output destination terminal device, the information generation unit 15 may further output the settlement data of the improper settlement person of the point. For example, the information generating unit 15 outputs a scatter diagram in which each point is associated with a settler indicated by the point by a known technique. When a certain point is selected in the scatter diagram, the information generation unit 15 specifies a settler indicated by the selected point in the scatter diagram, refers to the adjustment data DB 13, and sets the adjustment data corresponding to the settler. And outputs the payment data to the output destination terminal device.

  In addition, the information generation unit 15 may output information that can be compared with the settlement status of another accountant based on the frequency and the billing amount, in addition to the scatter diagram.

  The information generating unit 15 creates the scatter diagram based on the history of the adjustment data for the latest predetermined period (for example, one year). Further, the information generation unit 15 may identify and output a candidate for an unauthorized accountant instead of a scatter diagram.

  Using the information generated by itself, the information generating unit 15 notifies a clearing person who makes a payment that matches the condition based on the payment pattern that the condition based on the payment pattern matches.

  In the above description, the number of flags set for each accountant (the number of flags) is totaled, and the settlement data of the accountant whose flag number is equal to or greater than a threshold value stored in advance is managed by the accounting department or by each department. The case of transmitting and outputting to the office terminal device has been described. Instead, the information generation unit 15 refers to the generated information, and setstle the terminal device 3 of the accountant who is performing the payment that matches the condition (for example, the ratio of manual input is high) based on the payment pattern. A notification that the condition based on the settlement pattern is met may be given. As the notification, for example, a warning is given that there is a tendency that there is a lot of settlement by manual input instead of using a card. Also, as the notification, for example, a warning is issued that the ratio of not using the standard settlement plan tends to be high.

  As described above, the settlement management system 1 can prevent the occurrence of impropriety by notifying the terminal device 3 of the user 2 who may have made an improper or incorrect settlement.

  Note that the information generation unit 15 may change the notification method based on the regenerated result. For example, the information generation unit 15 may change the notification message when the user 2 of the terminal device 3 that has been notified once has settled again according to the condition based on the adjustment pattern. For example, the settlement management system 1 may notify a message whose warning level has been changed. Alternatively, when the effect is not visible, for example, when the number of users matching the condition based on the settlement pattern is increasing, the timing at which the information generating unit 15 generates the flag information is advanced, and the timing at which the information is notified is advanced. It may be.

  As described above, the settlement management system 1 refers to the information generated by the information generation unit 15 after the notified result, and changes the notification method based on the result, thereby not only providing uniform notification. By monitoring the trend after the notification and dynamically changing the notification method according to the trend, it is possible to prevent the occurrence of fraud.

<Processing procedure>
FIG. 6 is a flowchart illustrating a flow of a process of outputting information indicating a candidate for an improper account adjuster according to the present embodiment.

  First, the adjustment data input unit 11 receives an input of adjustment data from the terminal device 3 (S01). The settlement data registration unit 12 registers the settlement data in the settlement data DB 13 (S02). At a predetermined timing, the information generation unit 15 adds flag information based on the result of comparing the adjustment data stored in the adjustment data DB 13 with the adjustment reference information corresponding to the content (category) of the adjustment data. (S03).

  Further, at a predetermined timing, the information generation unit 15 totals the flag information and the like (S04), and based on the totaled result, the terminal device of the accountant who performs the settlement that matches the condition based on the settlement pattern. 3 is notified that the condition based on the settlement pattern is met (S05).

  FIG. 7 is a flowchart illustrating a flow of a process of outputting scatter diagram information as information indicating a candidate of an unauthorized accountant in the present embodiment.

  First, the adjustment data input unit 11 receives an input of adjustment data from the terminal device 3 (S11). The settlement data registration unit 12 registers the settlement data in the settlement data DB 13 (S12). At a predetermined timing, the information generation unit 15 adds flag information based on the result of comparing the adjustment data stored in the adjustment data DB 13 with the adjustment reference information corresponding to the content (category) of the adjustment data. (S13).

  Further, at a predetermined timing, the information generating unit 15 generates a scatter diagram based on the billing frequency and the billing amount of each clearing person as information indicating the improper payment candidate (S14), and the scatter diagram is processed by the accounting unit. The information is transmitted to the terminal device of the responsible person or the manager of each department (S15).

  Although not particularly described in the above embodiment, the settlement management system 1 may store address information of the user 2 in advance and generate flag information based on the address information. For example, the information generation unit 15 compares the address of the payee with the address of the user 2 to determine whether or not the address is smaller than a predetermined reference distance. Information (flag information) to the effect may be added.

Although not particularly described in the above-described embodiment, the settlement management system 1 stores in advance user-related information that is information defining users 2 having some kind of relevance (a friend or the like) to each other, and sets a flag based on this information. Information may be generated. For example, the information generation unit 15
If each of the users 2 defined as having relevance in the user related information has a large number of settlement requests on the same payment date, the information (flag indicating that there is a possibility of collusion and private use) (Information).

  As an example of a method for specifying a relevant user as described above, it is conceivable to apply the technology described in Japanese Patent Application Laid-Open No. 2009-140029.

  Although not particularly described in the above-described embodiment, the settlement management system 1 collects the settlement contents for which the company has an upper limit, such as daily allowance, by the information generation unit 15, and based on the totaled result. Alternatively, it may be determined whether the application is appropriate or not, and the result of the determination may be output. Here, the daily allowance can be claimed within the upper limit during a business trip.

  Here, FIG. 8 shows a graph of the settlement contents of the daily allowance with an upper limit of 3000 yen. FIG. 8 is a diagram showing a tendency of a daily allowance. As shown in FIG. 8, there is a tendency for many people to settle the lower limit of 0 yen or the upper limit of 3000 yen (the graph is a camel-shaped camel type). If it is a distant business trip, there is no problem even if you charge 3000 yen, but it is not always appropriate to charge 3000 yen even in a place close to the company for the purpose of daily allowance. Therefore, it is presumed that the accountant who constantly applies for the upper limit may have made an improper account settlement. Therefore, the information generation unit 15 generates flag information indicating whether or not the daily allowance settlement data is the upper limit amount, and determines the accountant who has a larger number of requests for the upper limit amount with respect to the entire number of daily allowance settlement cases. The obtained information may be output.

  In addition, there may be various extraction patterns of the settlement tendency. As an example, if the frequency of settlement at the middle amount (the amount between the upper limit and the lower limit) is high, but the frequency of settlement at the upper limit has increased from a certain point in time even though the business has not changed Attention is needed. This is because it is estimated that those who have applied for expenses only for the actual usage amount have come to apply for settlement of imaginary expenses up to the maximum amount. As described above, focusing on not only the settlement tendency at a certain point in time but also a change in the settlement tendency in a time series leads to the discovery of inhibition of improper settlement.

  It should be noted that, with respect to the daily allowance adjustment data, information indicating the business trip destination is also associated, and flag information indicating whether or not the maximum amount of daily allowance is being charged even though the business trip destination is close may be generated. Good.

  Although not particularly described in the above embodiment, the settlement management system 1 may store user information including a face image of the user 2 in advance, and generate flag information based on this information. .

  For example, the settlement management system 1 acquires the name of the participant and an image of a group photograph as settlement data for a request for group participation such as a drinking party, and registers the acquired image in the settlement data DB 13. The information generation unit 15 specifies a face portion from the group photograph. Then, the information generating unit 15 compares the face portion and the face image of the user information by image analysis processing of a known technique, specifies an attendee, compares the specified result with a participant of the application, It is determined whether or not the application is appropriate, and if inappropriate, information (flag information) indicating that the application is an unauthorized application may be added.

  Although not particularly described in the above embodiment, the billing tendency is specified based on the result of the past payment data of the user 2 specified as the fraudulent payer, and the probability of the fraudulent bill is determined based on the specified result. A certain user 2 may be specified.

  For example, an unauthorized accountant specified based on the scatter diagram generated by the information generating unit 15 is stored. The information generation unit 15 identifies a tendency of past settlement data of the settlement data of the unauthorized settlement person and stores information indicating the tendency. For example, the information generation unit 15 stores information indicating a change in the settlement frequency and a change tendency in the bill amount. The information generation unit 15 outputs information indicating that there is a possibility that the user 2 whose settlement data corresponds to the above tendency is likely to be an unauthorized accountant by batch processing.

  Further, although not particularly described in the above-described embodiment, the settlement data input unit 11 may receive input of image data of a receipt such as a taxi and a travel expense as the settlement data. In this case, the adjustment data input unit 11 may compare the result of the image analysis of the image data with the input amount of money or the like to determine whether the input value is appropriate.

  Further, although not described in detail in the above-described embodiment, information on the clock-in / out of each user 2 (business time data) is stored in advance, and the information generation unit 15 generates the flag information based on this information. It may be. That is, the settlement management system 1 may perform matching with the above-mentioned business time data. Alternatively, matching may be performed with information on the position and time of a mobile phone or smartphone lent by a company.

  For example, the information generation unit 15 adds information (flag information) indicating that there is a possibility of private use when the billing content relates to a taxi or a train, and the payment time is too different from the time of leaving / working. You may do so. For example, based on the information of attendance and departure, a case where the payment time of the taxi-based payment data is 22:00 even though the user 2 has left at regular time (for example, 18:00) on the payment date of the payment data Then, the information generating unit 15 generates flag information.

  Further, the example in which the settlement management system 1 is realized by one server device for convenience of description has been described, but the settlement management system 1 may be realized by an information processing device such as a plurality of server devices. For example, a server device having a function of generating flag information using the settlement data stored in the settlement data DB 13 and the settlement reference information stored in the settlement reference data DB 14, and a server device that is stored in the settlement data DB 13. The server device that generates the scatter diagram using the adjustment data may be configured separately.

  As described above, according to the settlement management system 1, the settlement data input by the settlement data input unit 11 is registered, the settlement data is totaled, and the settlement that matches the condition based on the predetermined settlement pattern is performed. Generates information indicating the accountant who is paying. As described above, the settlement management system 1 aggregates the settlement data and sets the conditions based on a predetermined settlement pattern (for example, manual input) (for example, the frequency of manual input is 80 out of 100 times). Since information indicating a matching accountant is output, an incorrect accountant candidate can be easily and more accurately specified. That is, the settlement management system 1 can provide information that can specify an inappropriate settlement person with higher accuracy.

  Since the above-mentioned settlement management system 1 performs settlement using information obtained based on a card (credit card or transportation IC card), it is linked with reliable information (information indicating that a formal payment has been made) (data It can be settled by cooperating) and can be easily input by the adjuster (inputless). Further, the settlement management system 1 can increase the transparency of the settlement data by performing the settlement by the data linkage as described above, and as a result, the conventional approval processing can be omitted or simplified.

  It is also conceivable that the settlement management system 1 performs settlement only with data obtained based on the card, but there are cases where the card cannot be used, and if settlement by manual input is not allowed, the convenience of the settlement person is lacking. Therefore, the settlement management system 1 operates to allow settlement by manual input. However, there is a high possibility of improper settlement in the settlement by manual input, so the settlement management system 1 omits the approval by notifying the settlement person who frequently performs the settlement by manual entry individually after the fact (no approval).・ Achieve simplification.

  In the first place, by making payment based on data based on the card as a basis, the transparency of the whole data is enhanced, so that it is easy to identify people who pass through unlit routes (payers who are likely to pay incorrectly). You can manage payment data. As a result, more effects can be obtained than in the case of the conventional prior approval system. The settlement management system 1 implements a data-assisted settlement out of the three elements of so-called fraud (motivation, opportunity, and justification) and performs a post-check to realize a system that does not give a fraudulent opportunity. Can be.

  In addition, the payment management system 1 gives a warning to a payer who frequently inputs manually or a payer who is avoiding the standard plan, and thus has an effect of spreading to other than the payer who issued the warning (a crack window effect). Can be demonstrated. As described above, the settlement management system 1 can detect a fraud in advance based on how an opponent reacts to an action, and can prevent fraud before it occurs.

  Further, according to the settlement management system 1, the settlement data input by the settlement data input unit 11 is registered, and the settlement contents (category) of the settlement data are illegal based on the billing frequency and billing amount of each settlement person. Information indicating a payment candidate is generated using the payment data registered in the payment data DB 13 and the information is output. As described above, since the settlement management system 1 outputs information based on the billing frequency and the billing amount, it is possible to easily identify an improper settlement candidate. That is, the settlement management system 1 can provide information that can identify an unauthorized settlement person.

  Further, the settlement management system 1 further outputs the claimant's billing data from the information based on the billing frequency and the billing amount, so that the billing data of the improper settlement candidate can be confirmed, and more specifically, the fraudulent settlement Can be provided that can determine the presence or absence of an error.

  In addition, since the settlement management system 1 outputs a scatter diagram based on the billing frequency and billing amount of the accountant, it is possible to provide information at a glance that can identify an unauthorized accountant.

  In addition, the settlement management system 1 outputs information based on the frequency at which the standard settlement plan is not used and the amount charged when the standard settlement plan is not used, thereby paying attention to exceptional claims having a high probability of improper settlement. Since the result is output, it is possible to output information that can identify the improper payment candidate more reliably.

  Further, according to the settlement management system 1, the settlement data input by the settlement data input section 11 is registered, and the settlement reference data DB14 stores, for each billing content, settlement reference information that defines a reference relating to the settlement. It generates information based on the result of comparing the adjusted settlement data with the adjustment reference information, and outputs the information. As described above, the settlement management system 1 can output information that can specify an illegal settlement person candidate by outputting information obtained by comparing the settlement reference information and the settlement data.

  As described above, the invention made by the inventor has been specifically described based on the embodiments. However, the present invention is not limited to the above embodiments, and can be variously modified without departing from the gist thereof. Needless to say. For example, the above-described embodiments have been described in detail for easy understanding of the present invention, and are not necessarily limited to those having all the configurations described above. Further, a part of the configuration of one embodiment can be replaced with the configuration of another embodiment, and the configuration of one embodiment can be added to the configuration of another embodiment. . Further, for a part of the configuration of each embodiment, it is possible to add / delete / replace another configuration.

  In addition, each of the above-described configurations, functions, processing units, processing means, and the like may be partially or entirely realized by hardware by, for example, designing an integrated circuit. In addition, the above-described configurations, functions, and the like may be realized by software by a processor interpreting and executing a program that realizes each function. Information such as a program, a table, and a file for realizing each function can be stored in a recording device such as a memory, a hard disk, an SSD (Solid State Drive), or a recording medium such as an IC card, an SD card, or a DVD.

  Further, in each of the above-described drawings, control lines and information lines are considered to be necessary for explanation, and do not necessarily indicate all control lines and information lines on mounting. In fact, almost all components may be considered to be interconnected.

  INDUSTRIAL APPLICABILITY The present invention is applicable to a payment management system that manages payment data.

DESCRIPTION OF SYMBOLS 1 ... Payment management system, 2 ... User, 3 ... Terminal device, 11 ... Payment data input part, 12 ... Payment data registration part, 13 ... Payment data DB, 14 ... Payment reference data DB, 15 ... Information generation part.

Claims (3)

A payment management system for managing payment data,
A payment data input unit for receiving input of the payment data,
An information generation unit that aggregates the adjustment data input by the adjustment data input unit and generates information indicating an accountant who is performing an adjustment that matches a condition based on a predetermined adjustment pattern;
A payment management system. The settlement management system according to claim 1,
The information generation unit, using the generated information, to the adjuster who performs the settlement that matches the condition based on the settlement pattern, to notify that the condition based on the settlement pattern matches the settlement management, system. The settlement management system according to claim 2,
The information generating unit, after the notification, sums up the settlement data input by the settlement data input unit, information indicating a settlement person who is performing the settlement that matches the condition based on the predetermined settlement pattern. A payment management system that regenerates and changes the notification method based on the regenerated result.

Images