Transaction approval method, transaction approval program, and transaction approval system
The transaction approval method provides quantitative evaluation through transaction ID acquisition, qualified invoice verification, and scoring, enhancing the accuracy and efficiency of transaction approval decisions.
Patent Information
- Application Number
- JP2023081167
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-17
- Publication Date
- 2024-11-28
AI Technical Summary
Existing transaction approval systems lack the ability to provide quantitative evaluation of transaction impacts, making it difficult for companies to assess the potential business effects accurately.
A transaction approval method involving transaction ID acquisition, number acquisition for qualified invoice verification, and processing result output, along with scoring and judgment steps, to facilitate quantitative assessment and decision-making.
Enables businesses to make informed, quantitative judgments on transaction suitability, supporting efficient and accurate approval processes.
Smart Images

Figure 2024165219000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a method for contributing to transaction approval within one business regarding a transaction carried out between businesses. [Background technology]
[0002] In the course of daily transactions, businesses often internally review the appropriateness of a transaction, especially when the transaction partner is a new business partner. The decision-maker within the business must decide whether or not to approve the transaction based on the results of credit assessments and anti-social checks, and various technologies have been developed to support such decisions. Specifically, as described in Patent Document 1, a technology has been disclosed that makes it possible to extract and display web pages related to people who are related to a supply chain. Using this technology, it is possible to support the collection of information within a business to review the appropriateness of a transaction. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] Patent Publication No. 2020-166506 Summary of the Invention [Problem to be solved by the invention]
[0004] However, even when using such technology, the impact on a company's business that can be inferred from the information collected there is often only qualitative, such as "whether there is a risk" or not, making a quantitative assessment extremely difficult. [Means for solving the problem]
[0005] In order to solve the above problems, the present invention proposes a transaction approval method that uses a computer to execute the following steps: a transaction ID acquisition step for accepting input of a transaction ID that identifies a specified transaction from a user with certain authority within the business; a number acquisition step for acquiring a qualified invoice issuer registration number associated with the transaction; and a processing result output step for linking the processing result of the number acquisition step with the transaction ID and outputting it to another user with authority within the business.
[0006] In addition, in relation to the above invention, we also propose a transaction approval method further comprising an approval receiving step for receiving a decision on whether or not to approve the transaction identified by the transaction ID from the output destination of the processing result output step, and a decision result output step for outputting the decision result to the user who inputted the transaction ID.
[0007] In addition, in relation to the above invention, we also propose a transaction approval method which further includes a scoring processing step which performs scoring to determine whether the transaction is appropriate using other information linked to the transaction ID together with the processing result of the number acquisition step, and the processing result output step further includes a score output sub-step which outputs the scoring result together with the processing result.
[0008] The present invention also proposes a transaction approval method in which the transaction ID acquisition step further includes a purpose acquisition sub-step of accepting input of the transaction ID together with the purpose of the predetermined transaction.
[0009] Furthermore, the present invention also proposes inventions relating to programs, systems, etc., associated with the above-mentioned methods. Effect of the Invention
[0010] The present invention having the above-mentioned main configuration makes it easy for a decision-maker to determine the suitability of a transaction from a quantitative standpoint on the workflow. [Brief description of the drawings]
[0011] [Figure 1] Schematic diagram of the system of the present invention. [Diagram 2] FIG. 1 is a diagram showing an example of a functional block of a system according to a first embodiment. [Diagram 3] FIG. 13 is a diagram showing an example of a transaction ID acquired by a transaction ID acquisition unit; [Figure 4] FIG. 1 is a schematic diagram showing an example of a configuration in which the functional components of the system according to the first embodiment are integrated and realized as one piece of hardware. [Diagram 5] FIG. 1 is a diagram showing an example of a processing flow in the system of the first embodiment. [Figure 6] FIG. 13 is a diagram showing an example of a functional block of a system according to a second embodiment. [Figure 7] FIG. 11 is a diagram showing an example of a processing flow in the system of the second embodiment. [Figure 8] FIG. 13 is a diagram showing an example of a functional block of a system according to a third embodiment. [Figure 9] FIG. 13 is a diagram showing an example of a processing flow in the system of the third embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0012] First, Fig. 1 is shown. Fig. 1 is a diagram showing an overview of the present invention. As shown in the figure, the present invention can be realized through the transmission and reception of information via a network between one or more server computers 0101, 0102 and a terminal (decider terminal) 0111 managed by a person with decision-making authority in a business, or terminals (employee terminals) 0112, 0113 managed by a person with authority different from the person with decision-making authority.
[0013] As mentioned above, the present invention can be realized by one or more server computers 0101, 0102. As a specific example of using multiple server computers, a trading partner management database server that stores trading details such as trading partner credit information, antisocial check results, and specific trading performance by linking them with specific trading partners, and a business management server for managing workflow and other business execution within a business, etc., can be used by connecting them to each other via an online or offline network. In addition, these server computers may be connected online to external server computers 0121, 0122 (for example, a server of the National Tax Agency that manages the qualified invoice issuing business registration number, or a trading partner terminal that is a terminal managed by the trading partner).
[0014] Next, the types of various terminals connected to the various computers that realize the present invention are not particularly limited, and examples thereof include personal computers 0111, 0113 and smartphones 0112, as well as various terminals that can be used for decision-making on transaction execution at business locations, such as tablets and various workflow management terminals.
[0015] Up to this point, the explanation has been given with reference to Figure 1 on the assumption that the server computers 0101, 0102 are configured separately from the authorizer terminal 0111 and are provided in the form of cloud computing via a network, but the present invention is not limited to this form of use. In other words, the present invention may be provided in a so-called on-premise form, in which a program capable of executing the functions of the present invention is installed in the authorizer terminal, and all or part of the processing of the functions that can be provided by the present invention is executed in the authorizer terminal. It can also be realized by using a recording medium on which the program described here is stored.
[0016] Each embodiment of the present invention will be described below with reference to the drawings. First, the relationship between the embodiments and the claims is as follows. First, embodiment 1 mainly corresponds to claims 1, 4, 5, 6, etc.; embodiment 2 mainly corresponds to claim 2, etc.; embodiment 3 mainly corresponds to claim 3, etc. However, the technical features described in each embodiment can also be used in combination with the technical features described in other embodiments.
[0017] It should be noted that the present invention is not limited to these embodiments, but rather has the technical ideas described in each claim in accordance with common technical knowledge, and can be embodied in various forms without departing from the spirit of the invention.
[0018] <<Embodiment 1>> <Summary> 2 is a diagram showing an example of a functional block of the transaction approval system of this embodiment. As shown in the figure, the "transaction approval system" 0200 of this embodiment has a "transaction ID acquisition unit" 0201, a "number acquisition unit" 0202, and a "processing result output unit" 0203.
[0019] The transaction approval system described in detail below may be configured to realize one or more of its functions using multiple devices, and the functional blocks may be realized as hardware or software. Examples of a system using a computer include hardware components such as a CPU, main memory, GPU, TPU, image memory, bus, secondary storage device (hard disk or non-volatile memory), keyboard, microphone, touch panel, electronic pen for touching the touch panel, various input devices such as various terminals, speakers, displays and other various output devices, and other external peripheral devices, as well as interfaces for the external peripheral devices, communication interfaces, driver programs for controlling the hardware, and other application programs.
[0020] Then, by performing arithmetic processing according to the program deployed on the main memory, data input from an input device or other interface and held in the memory or hardware is processed and stored, and instructions for controlling the above-mentioned hardware and software are created. Here, the above-mentioned program may be realized as a plurality of modularized programs, or two or more programs may be combined by cloud computing or other methods to be realized as one program.
[0021] <Functional configuration> The "transaction ID acquisition unit" 0201 is configured to receive an input of a transaction ID for identifying a specific transaction from a user with a specific authority within the business. The transaction ID received here is an identifier that is linked to information for making a specific transaction identifiable at the same time or in advance, and specifically, it is considered to link the business partner, the transaction purpose, the transaction item, the transaction amount, the transaction time, and other information that is considered to be useful for identifying the transaction.
[0022] FIG. 3 is shown here. The figure shows an example of the storage of a transaction ID acquired by the transaction ID acquisition unit. The record can be acquired, edited, and deleted at an appropriate timing by the server used in the present invention. In the figure, the transaction ID identified by the numbers S10423 to S10427 is shown to be recorded in association with information such as the transaction partner, transaction purpose, expense item, amount (estimated / confirmed), and transaction time. A user with a certain authority within the business entity identifies this information as an acquisition target via the transaction ID. To take one of the examples shown in the figure, when the input of the transaction ID "S10424" is accepted, the information stored in association with the transaction ID is the transaction partner "Office Q", the transaction purpose "customer", the expense item "service provision", the transaction amount "960,000 yen", and the transaction start time "August 2020".
[0023] Here, in more detail, an example of directly or indirectly accepting input of the purpose of a given transaction with respect to the items shown in FIG. 3 will be described. The transaction purposes shown in the figure are "customer" and "purchase / procurement", and by accepting input of the transaction purpose in this way, it is possible to clarify whether one is on the supplier side or the demand side of the transaction. The transaction purpose may be accepted through a configuration that can accept a selection of whether one is on the supplier side or the demand side in advance, or may be accepted by accepting input of keywords (e.g., "purchase", "sale", "trial", etc.) related to the transaction purpose arbitrarily input by the user, performing a process to infer which of the above-mentioned positions the user is in from the accepted keywords, and accepting input of the result of the process, or a combination of these configurations.
[0024] In addition, in transactions subject to consumption tax, a mechanism called "input tax credit" is adopted in the Japanese tax system (described later), and it is basically the demand side in the transaction that can receive certain tax and financial benefits by applying this credit. In other words, especially when the demand side is planning to carry out a transaction, whether or not the input tax credit can be applied is useful information in estimating the tax burden in the transaction, and ultimately the quantitative business impact. Therefore, it is desirable for information on the purpose of the transaction to be obtained directly or indirectly and used as material for the decision-making authority.
[0025] The transaction ID acquisition unit may accept input of the transaction ID itself, or may indirectly acquire the transaction ID by accepting input of various information recorded in association with the transaction ID, as shown in Figure 3 and above. By using a database such as that shown in Figure 3 to select information that can identify a transaction partner under specific transaction conditions, and adopting a configuration that can identify a specific transaction in accordance with the selection, even business operators with a large number of transaction partners can implement the present invention without incurring complicated management costs.
[0026] Incidentally, the presence or absence of a specific authority within the business for a user and the details of that authority are preset, recorded, and made changeable when the user registers an account to use this system. Examples of the specific authority include the authority to handle transactions over a specific amount, or transactions for a specific purpose or expense item, and by linking the type and details of such authority with the user who inputs the transaction ID, it is possible to determine in advance whether the user is qualified to request approval for the transaction, and to limit the matters that the person with the authority should consider other than the transaction content itself.
[0027] The "number acquisition unit" 0202 is configured to acquire the registration number of the qualified invoice issuer related to the transaction. A qualified invoice is also called an invoice, and is a mechanism used to identify whether or not a transaction is eligible for input tax credit in the field of consumption tax. Specifically, if a business is registered with the National Tax Agency as a business that can issue a qualified invoice, the business can receive input tax credit and preferential tax treatment for transactions made using a qualified invoice issued by the business. The amount of consumption tax paid by the business changes depending on whether or not the preferential treatment is applied, and in short, in transactions with businesses that do not issue qualified invoices, the business profit is compressed by the amount of the preferential treatment that cannot be received compared to businesses that issue qualified invoices. The larger the transaction amount or the more frequently the transaction occurs, the more the business impact of the profit compression cannot be ignored, so the decision-maker will view the approval of the transaction as a negative one.
[0028] A specific method of obtaining the qualified invoice issuer registration number related to a specified transaction may be to send a notification to the contact of the business directly or indirectly linked to the transaction ID to confirm the presence or absence of the qualified invoice issuer registration number and the number, and obtain the number by responding to the notification, or to obtain the number by using an external system that can search for the qualified invoice issuer registration number stored on a server managed by the National Tax Agency or other third parties through API or other linkages. By adopting such a configuration, it becomes possible for the decision maker to know whether or not the transaction in question is eligible for the input tax credit without the need for cumbersome procedures such as analog interviews.
[0029] The "processing result output unit" 0203 is configured to output the processing result of the number acquisition unit to another authorized user in the business by linking it to the transaction ID. The processing result to be output here may include not only the registration number itself related to the issuance of qualified invoices by the business linked to the transaction ID, but also a wide range of information that can be used to recognize whether or not the business has the registration number (including processing results that indirectly infer the presence or absence of a registration number, such as whether or not a search result was found or whether or not there was a response from a notification to the business's contact point). By adopting this configuration, it becomes possible for the decision-maker to easily understand whether or not input tax credit is applicable when deciding whether or not to proceed with a specific transaction, and ultimately to support decision-making from a quantitative perspective based on the information.
[0030] Incidentally, from the viewpoint of the above-mentioned utility, the processing result in the number acquisition unit is not prevented from being linked to the transaction ID and output together with other information that contributes to the decision-making. For example, based on the transaction amount of the transaction, the tax saving amount and other tax saving effects in the case where the input tax credit is applied to the transaction can be calculated and output, or the presence or absence of the tax saving effect or the tax saving scale can be calculated and output by comparing with the similar transactions performed by the same business in the past (a method of inferring from information such as "expense item" and "transaction time" among the information shown in Figure 3 can be considered). By adopting the configuration that outputs using information on transactions linked to transaction IDs recorded and stored in the past, it becomes possible to support decision-makers in making decision-making decisions from the perspective of quantitative business impacts that take into account factors over time.
[0031] <Specific configuration> Here, Fig. 4 is shown. This figure is a schematic diagram showing an example of a configuration when each functional component of the transaction approval system of this embodiment is integrated and realized as a single piece of hardware. Each device has a "CPU" 0401 for executing various arithmetic processes, a "storage device (storage medium)" 0402, a "main memory" 0403, an "input / output interface" 0404, and a "network interface" 0405, and transmits and receives information to and from external peripheral devices such as a "keyboard" 0406 via the input / output interface.
[0032] Furthermore, the transaction approval system of this embodiment may transmit and receive information via a network interface with external devices such as a plurality of "settlement officer terminals" 0407 and "employee terminals" 0408, or an "external server" 0409 that performs various processes externally. The specific form of this network interface may be wired or wireless, and the communication method may be direct or indirect between the two terminals. Therefore, it is also possible to adopt a so-called cloud computing format in which information is transmitted and received between a specific external device or a server managed by a third party linked to the user of the device.
[0033] The storage device stores various programs as described below, and the CPU reads, expands, and executes these programs in the work area of the main memory. These components are interconnected by a data communication path such as a "system bus" 0499, and transmit and receive information and perform processing (the basic configuration described above is the same for any of the other devices described below).
[0034] (Specific configuration of transaction ID acquisition unit) The transaction ID acquisition unit is composed of a computer program and computer hardware, and specifically, the CPU reads the "transaction ID acquisition program" 0410 from the storage device into the main memory and executes it, accepts input of a transaction ID that identifies a specific transaction from a terminal operated by a user with specific authority within the business, and stores it at a specific address in the main memory.
[0035] At this time, a process may be performed to receive input of the purpose of the specified transaction together with the specified ID, and in that case, the information received by this process is also stored at a specified address in the main memory.
[0036] (Specific configuration of the number acquisition unit) The number acquisition unit is composed of a computer program and computer hardware. Specifically, the CPU reads out the “number acquisition program” 0420 from the storage device into the main memory and executes it, acquires the qualified invoice issuer registration number related to the transaction through sending and receiving information with an external server, and stores it in a specified address in the main memory.
[0037] (Specific configuration of the processing result output unit) The processing result output unit is composed of a computer program and computer hardware. Specifically, the CPU reads out the “processing result output program” 0430 from the storage device into the main memory and executes it. The processing result obtained through the execution of the number acquisition program is linked to the transaction ID and output to a terminal managed by another authorized user within the business.
[0038] <Processing flow> Figure 5 is a diagram showing an example of the process flow in the transaction approval system of this embodiment. The process flow in this figure consists of the following steps. First, in step S0501, input of a transaction ID that identifies a specific transaction is accepted from a user with specific authority within the business (transaction ID acquisition step), and in step S0502, processing is performed to acquire the qualified invoice issuer registration number associated with the transaction (number acquisition step). Then, in step S0503, the processing result of the number acquisition step is linked to the transaction ID and output to another authorized user within the business (processing result output step).
[0039] Incidentally, in the transaction IT acquisition step, a process may be performed in which the input of the transaction ID together with the purpose of the specified transaction is accepted (purpose acquisition sub-step), and for example, if it is possible to determine that the transaction is to be carried out by the supplier rather than the consumer as a result of the process, the result of the determination may be output in the process result output step without performing the subsequent number acquisition step. If such a configuration is adopted, it is possible to reduce the time and cost required for the number acquisition step, and to support rapid decision-making by the decision-maker.
[0040] <Effects> By using a transaction approval system having the above configuration, it becomes easy for the decision maker to determine the suitability of a transaction from a quantitative standpoint in the workflow.
[0041] <<Embodiment 2>> <Summary> The transaction approval system of this embodiment basically has the same technical features as the transaction approval system described in embodiment 1, but has the additional feature of accepting a decision from the output destination of the processing result as to whether or not to approve the transaction identified by the transaction ID, and outputting the decision result to the user who input the transaction ID.
[0042] <Functional configuration> Fig. 6 is a diagram showing an example of a functional block of the transaction approval system of this embodiment. As shown in the figure, the "transaction approval system" 0600 of this embodiment has a "transaction ID acquisition unit" 0601, a "number acquisition unit" 0602, a "processing result output unit" 0603, an "approval acceptance unit" 0604, and a "judgment result output unit" 0605. The basic configuration is the same as that of the transaction approval system described using Fig. 2 of the first embodiment, so the following describes the functions of the "approval acceptance unit" 0604 and the "judgment result output unit" 0605, which are the differences.
[0043] The "approval reception unit" 0604 is configured to receive a decision on whether or not to approve the transaction identified by the transaction ID from the output destination of the processing result output unit. This is one aspect of the decision processing by the decision-maker, which has been mentioned many times in the first embodiment, and there is no particular limitation on how the decision is indicated other than the decision-making process through the decision-maker's operation input on the payment terminal. To give an example, a configuration that accepts a decision indicated together with an indication of intention with quantitative confirmation items for the transaction (for example, information on whether or not to discount the price, acceptable amount fluctuation range, etc., adjustment of the transaction timing based on the budget, etc.) in addition to information on an indication of intention only on whether or not to approve the transaction is conceivable. By adopting this configuration, it is possible to easily and quickly inform the intention of the decision-maker.
[0044] The "judgment result output unit" 0605 is configured to output the judgment result of the approval reception unit to the user who input the transaction ID. There is no particular limit to the output mode, such as sending an email to the user's preregistered contact address or outputting a message through the message function of this system, but in any case, by adopting this configuration, the decision-maker's intention on whether to carry out the transaction can be quickly conveyed to the employee who applied for the approval of the transaction.
[0045] The result of the decision may be output to the user and may be recorded in association with the transaction ID as shown in Fig. 3. By adopting this configuration, the process of the approval process for a certain transaction can be easily understood by performing a search process on another occasion, and employees can also prepare in advance and apply for approval when making a similar transaction, so as not to place an unnecessary burden on the person with the approval authority.
[0046] <Specific configuration> The hardware configuration of each device constituting the transaction approval system of this embodiment is basically the same as the hardware configuration in the transaction approval system of embodiment 1 described with reference to Fig. 4. Therefore, in the following, specific processing of the "approval receiving unit" and "judgment result output unit" that have not been described so far will be described.
[0047] (Specific Composition of the Approval Reception Department) The approval receiving unit is specifically composed of a computer program and computer hardware, and the CPU reads the "approval receiving program" from the storage device into the main memory and executes it, and receives a decision as to whether or not to approve the transaction identified by the transaction ID from the information output destination by executing the processing result output program, and stores the result of the decision at a specified address in the main memory.
[0048] (Specific configuration of the judgment result output unit) The judgment result output unit is specifically composed of a computer program and computer hardware, and the CPU reads the ``judgment result output program'' from the storage device into the main memory and executes it, reading out the judgment result and outputting it to the terminal managed by the user from which the transaction ID was input.
[0049] <Processing flow> Figure 7 is a diagram showing an example of the process flow in the transaction approval system of this embodiment. The process flow in this figure consists of the following steps. First, in step S0701, input of a transaction ID that identifies a specific transaction is accepted from a user with specific authority within the business (transaction ID acquisition step), and in step S0702, processing is performed to acquire the qualified invoice issuer registration number associated with the transaction (number acquisition step). Then, in step S0703, the processing result of the number acquisition step is linked to the transaction ID and output to another authorized user within the business (processing result output step).
[0050] Then, in step S0704, it is determined whether a decision on whether to approve the transaction identified by the transaction ID has been output from the output destination in the processing result output step, and if the decision result has been output, the output content is output to the user who input the transaction ID in step S0705 (decision result output step). If the decision result has not been output, no subsequent processing is performed.
[0051] <Effects> By using the transaction approval system of this embodiment, it is possible to convey the intention of the decision maker to the employee who has submitted the approval request more quickly and clearly than when the transaction approval system of embodiment 1 is used.
[0052] <<Embodiment 3>> <Summary> The transaction approval system of this embodiment basically has the same technical features as the transaction approval system described in embodiment 1, but has an additional feature in that it further has a score output sub-step that performs scoring to determine whether the transaction is appropriate using the processing result in the number acquisition unit and other information linked to the transaction ID, and outputs the scoring result together with the processing result in the number acquisition unit in the processing result output unit.
[0053] <Functional configuration> Fig. 8 is a diagram showing an example of a functional block of the transaction approval system of this embodiment. As shown in the figure, the "transaction approval system" 0800 of this embodiment has a "transaction ID acquisition unit" 0801, a "number acquisition unit" 0802, a "processing result output unit" 0803, and a "scoring processing unit" 0804, and the processing result output unit further has a "score output means" 0813. Since the basic configuration is the same as the transaction approval system described using Fig. 2 of the first embodiment, the following describes the functions of the "scoring processing unit" 0804 and the "score output means" 0813, which are the differences.
[0054] The "scoring processing unit" 0804 is configured to perform scoring for judging whether or not a transaction is appropriate using the processing result of the number acquisition unit and other information linked to the transaction ID. The other information here can be information such as the transaction partner, transaction purpose, expense item, transaction amount, and transaction time shown in FIG. 3, as explained above, but also includes indirect use of information related to the transaction partner. For example, past transaction records with the transaction partner, press releases and other reports about the transaction partner, and press releases and other reports by competitors of the transaction partner. By using such information, it is possible to improve the accuracy of analysis that contributes to judging whether or not a transaction is appropriate.
[0055] It should be noted that the scoring here does not particularly limit the specific processing manner or processing means. Various methods may be used as long as they are generally used to convert the above-mentioned qualitative information into quantitative information. For example, for various qualitative information, weighting is set in advance for the contents and types of the information, and the information obtained in association with a specific transaction ID is subjected to the weighting process, and then a scoring process is performed based on a predetermined rule or an analysis based on artificial intelligence.
[0056] In addition to the information associated with the specific transaction ID, the scoring may be performed using information within the business. For example, quantitative information such as the business's current sales, budget consumption rate, and the degree of achievement of various pre-set KPIs may be obtained from a server managed by the business and used for the scoring. By adopting such a configuration, it becomes possible to provide information that goes beyond general and abstract decision-making and helps the business consider whether or not the transaction at the time is appropriate.
[0057] The "score output means" 0813 is configured to output the scoring result together with the processing result of the number acquisition unit in the processing result output unit. The scoring result is preferably presented as quantitative information, such as "The tax saving effect of this transaction is equivalent to XX yen, and the transaction tolerance is 80%" or "The input tax credit is not applied, and the past transaction performance is also ranked D." By adopting this configuration that provides quantitative information on factors other than the application or non-application of the input tax credit, it is possible to support more intuitive decision-making by the decision-maker.
[0058] <Specific configuration> The hardware configuration of each device constituting the transaction approval system of this embodiment is basically the same as the hardware configuration in the transaction approval system of embodiment 1 described with reference to Fig. 4. Therefore, in the following, specific processing of the "scoring processing unit" and "score output means" that have not been described so far will be described.
[0059] (Specific configuration of the scoring processing unit) The scoring processing unit is specifically composed of a computer program and computer hardware, and the CPU reads the ``scoring processing program'' from the storage device into the main memory and executes it, and performs scoring to determine whether the transaction is appropriate using the execution result of the number acquisition program and other information linked to the transaction ID, and stores the processing result at a specified address in the main memory.
[0060] (Specific configuration of score output means) The score output means is specifically composed of a computer program and computer hardware, and when the processing result output program is executed, the CPU reads the "score output subprogram" from the storage device into the main memory and executes it, outputting the scoring result along with the execution result of the number acquisition program.
[0061] <Processing flow> Figure 9 is a diagram showing an example of the process flow in the transaction approval system of this embodiment. The process flow in this figure consists of the following steps. First, in step S0901, input of a transaction ID that identifies a specific transaction is accepted from a user with a specific authority within the business (transaction ID acquisition step), and in step S0902, processing is performed to acquire the qualified invoice issuer registration number associated with the transaction (number acquisition step).
[0062] Next, in step S0903, scoring is performed to determine whether the transaction is valid or not using the processing result of the number acquisition step and other information linked to the transaction ID (scoring processing step), and in step S0904, the processing result of the number acquisition step and the scoring result are linked to the transaction ID and output to another authorized user within the business (score output step).
[0063] <Effects> Use of the transaction approval system of this embodiment makes it possible to support quantitative judgment on the suitability of a transaction, taking into account multiple factors, compared to the case where the transaction approval system of embodiment 1 is used. [Explanation of symbols]
[0064] 0200: Transaction approval system, 0201: Transaction ID acquisition unit, 0202: Number acquisition unit, 0203: Processing result output unit
Claims
1. a transaction ID acquisition step of accepting an input of a transaction ID for identifying a specific transaction from a user having a specific authority within the business; obtaining a qualified billing business registration number associated with the transaction; a processing result output step of linking the processing result of the number acquisition step with the transaction ID and outputting the processing result to another authorized user within the business; A transaction approval method that uses a computer to execute the above steps.
2. an approval receiving step of receiving a decision as to whether or not to approve the transaction identified by the transaction ID from an output destination of the processing result output step; a determination result output step of outputting the determination result to a user who input the transaction ID; The method of claim 1 further comprising:
3. The method further includes a scoring process step for performing scoring to determine whether or not a transaction is appropriate using a processing result of the number acquisition step and other information linked to the transaction ID, 2. The method of claim 1, wherein the processing result output step further comprises a score output sub-step of outputting the scoring result together with the processing result of the number acquisition step.
4. The transaction ID acquisition step is 2. The method of claim 1, further comprising a purpose acquisition substep of accepting input of a transaction ID along with a purpose for the given transaction.
5. a transaction ID acquisition step of accepting an input of a transaction ID for identifying a specific transaction from a user having a specific authority within the business; obtaining a qualified billing business registration number associated with the transaction; a processing result output step of linking the processing result of the number acquisition step with the transaction ID and outputting the processing result to another authorized user within the business; A transaction approval program that enables the above to be executed on a computer.
6. a transaction ID acquisition unit that receives an input of a transaction ID that identifies a specific transaction from a user having a specific authority within the business; a number acquisition unit that acquires a qualified invoice issuer registration number associated with the transaction; a processing result output unit that links the processing result of the number acquisition step with the transaction ID and outputs the processing result to another authorized user within the business; A transaction approval system having:
Citation Information
Patent Citations
Examination support device and examination support program
JP2020166506A
