Collation device, collation method and collation program

The matching device and method address the complexity of comparing inspection and sales data by using a control unit to automate the matching process with preset keys, resulting in efficient and manageable data matching.

JP2025053945APending Publication Date: 2025-04-07OBIC CO LTD
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
JP2023163084
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-09-26
Publication Date
2025-04-07

AI Technical Summary

Technical Problem

Existing transaction details matching systems become complex and difficult to manage when comparing inspection data and sales data, especially when there are many items to match, leading to inefficiencies in matching settings.

Method used

A matching device and method that automatically performs efficient matching by using a control unit to associate sales data with inspection data through a preset check key and matching key, allowing for easy management of matching settings.

Benefits of technology

The solution enables automatic and efficient matching while simplifying the management of matching settings, ensuring accurate and efficient data comparison and processing.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2025053945000001_ABST
    Figure 2025053945000001_ABST
Patent Text Reader

Abstract

To provide a collation device, etc. which makes it easy to manage collation settings and performs automatic, efficient collation.SOLUTION: A collation device for collating sales data and acceptance data can access a billing destination master which associates the sales data and the acceptance data with collation method classification items for classifying billing destination items and collation methods, and a collation method master which associates collation method classification items with collation keys with which a collation item is set. A controlling unit obtains a collation method classification item from the billing estimation master based on a billing destination code item included in the acquired sales data and acceptance data, obtains a collation key from the collation method master based on the collation method classification item, collates sales data with acceptance data in a collation item set by the collation key and, if the sales data matches with the acceptance data in the collation item, collates the sales data with the acceptance data in a check item set by a check key to generate collation result data.SELECTED DRAWING: Figure 9
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a matching device, a matching method, and a matching program. [Background technology]

[0002] Conventionally, a transaction detail matching system that matches supplier detail data with supplier detail data using a matching key is known (see, for example, Patent Document 1). In the transaction detail matching system of Patent Document 1, when the supplier detail data and supplier detail data are matched using the matching key, if they do not match, the matching result indicates that there is something left to be dealt with, and when they match, the matching result indicates that the process has been completed. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2022-73054 A Summary of the Invention [Problem to be solved by the invention]

[0004] When verifying inspection data as supplier detail data and sales data as supplier detail data, the items included in the inspection data differ depending on the supplier. If there are many items to verify the inspection data and sales data, it is necessary to set many items to verify depending on the supplier, which makes management of the verification settings cumbersome.

[0005] The present invention has been made in consideration of the above-mentioned problems, and aims to provide a matching device, a matching method, and a matching program that can automatically perform efficient matching while facilitating management of matching settings. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, the collation device according to the present invention is a collation device having a control unit for collating a company's sales data with inspection data of a billing destination, the sales data and the inspection data being associated with a plurality of items including a check item to be collated based on a preset check key, a billing destination code item for identifying the billing destination, and a collation item used for the collation, the sales data, the inspection data, a billing destination master that associates the billing destination code item with a collation method classification item that classifies the collation method, and a collation method master that associates the collation method classification item with a collation key to which the collation item is set, The control unit acquires the sales data and the inspection data, acquires the matching method classification item from the billing master based on the billing code item included in the sales data and the inspection data, acquires the matching key from the matching method master based on the matching method classification item, compares the sales data with the inspection data in the matching item set in the matching key, and if the sales data and the inspection data match in the matching item, compares the sales data with the inspection data in the check item set in the check key, and generates the matching result as matching result data.

[0007] In addition, in the matching device according to the present invention, the control unit may determine that the matching result in the matching result data is positive when the sales data and the inspection data match in the check items, and may determine that the matching result in the matching result data is false when the sales data and the inspection data do not match in the check items.

[0008] In addition, in the matching device of the present invention, the check items include unit price, quantity, amount, and tax amount, and when the sales data and the inspection data mismatch in any of the check items, the control unit may determine the check items that have become mismatched.

[0009] Furthermore, in the matching device according to the present invention, when the sales data and the inspection data do not match in the matching items, the control unit may determine whether or not the sales data or the inspection data exists, and if it is determined that only the sales data exists, the matching result is incorrect and the data has not been inspected, and if it is determined that only the inspection data exists, the matching result is incorrect and the sales have not been recorded.

[0010] Further, the collation method according to the present invention is a collation method for collating a company's sales data with inspection data of a billing destination, the sales data and the inspection data are associated with a plurality of items including a check item to be collated based on a preset check key, a billing destination code item for identifying the billing destination, and a collation item used for collation, the sales data, the inspection data, a billing destination master in which the billing destination code item and a collation method classification item that classifies the collation method are associated with each other, and a collation method master in which the collation method classification item and a collation key to which the collation item is set are associated, and the sales data and the inspection data are collated with each other. a matching device having a control unit that acquires receipt data, acquires the matching method classification item from the billing destination master based on the billing destination code item included in the sales data and the inspection data, acquires the matching key from the matching method master based on the matching method classification item, compares the sales data and the inspection data in the matching item set in the matching key, and if the sales data and the inspection data match in the matching item, compares the sales data and the inspection data in the check item set in the check key, and generates the matching result as matching result data.

[0011] The collation program according to the present invention is a collation program for causing a collation device having a control unit to execute a collation method for collating a company's sales data with a billing destination's inspection data, the sales data and the inspection data being associated with a plurality of items including a check item to be collated based on a preset check key, a billing destination code item for identifying the billing destination, and a collation item used for the collation, the sales data, the inspection data, a billing destination master in which the billing destination code item and a collation method classification item that classifies the collation method are associated with each other, and a collation method master in which the collation method classification item and a collation key to which the collation item is set are associated with each other. the matching device executes the following operations: acquiring the sales data and the inspection data, acquiring the matching method classification item from the billing destination master based on the billing destination code item included in the sales data and the inspection data, acquiring the matching key from the matching method master based on the matching method classification item, matching the sales data with the inspection data in the matching item set in the matching key, and if the sales data and the inspection data match in the matching item, matching the sales data with the inspection data in the check item set in the check key, and generating the matching result as matching result data. Effect of the Invention

[0012] The present invention provides an advantage in that it is possible to easily manage collation settings and to automatically execute efficient collation. [Brief description of the drawings]

[0013] [Figure 1] FIG. 1 is a diagram illustrating an example of the configuration of a matching device. [Diagram 2] FIG. 2 is a diagram showing an example of sales data before being updated. [Diagram 3] FIG. 3 is a diagram illustrating an example of the inspection data before being updated. [Figure 4] FIG. 4 is a diagram illustrating an example of the billing destination master. [Diagram 5]FIG. 5 is a diagram illustrating an example of the verification method master. [Figure 6] FIG. 6 is a diagram showing an example of updated sales data. [Figure 7] FIG. 7 is a diagram showing an example of the updated inspection data. [Figure 8] FIG. 8 is a diagram showing an example of the matching result data. [Figure 9] FIG. 9 is a diagram illustrating an example of a flowchart relating to the matching method. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, a detailed description will be given of an embodiment of a matching device, a matching method, and a matching program according to the present invention with reference to the accompanying drawings. Note that the present invention is not limited to the embodiment.

[0015] [1. Configuration] An example of the configuration of the matching device 100 according to this embodiment will be described with reference to Fig. 1 etc. Fig. 1 is a block diagram showing an example of the configuration of the matching device 100.

[0016] The verification device 100 performs verification between the sales data of the transaction source and the inspection data of the transaction destination. The verification device 100 is constructed based on a commercially available desktop personal computer. The verification device 100 is not limited to being constructed based on a stationary information processing device such as a desktop personal computer, but may be constructed based on a portable information processing device such as a commercially available notebook personal computer, a PDA (Personal Digital Assistant), a smartphone, or a tablet personal computer.

[0017] The verification device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. The units included in the verification device 100 are connected to each other so as to be able to communicate with each other via any communication path.

[0018] The communication interface unit 104 communicably connects the verification device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via the communication line. Here, the network 300 has a function of connecting the verification device 100 and the server 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network). The data stored in the memory unit 106 may be stored in the server 200, for example.

[0019] An input device 112 and an output device 114 are connected to the input / output interface unit 108. The output device 114 may be a monitor (including a home television), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that cooperates with a mouse to realize a pointing device function. In the following, the output device 114 may be referred to as the monitor 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.

[0020] Various databases, tables, files, etc. are stored in the storage unit 106. Computer programs for cooperating with an OS (Operating System) to give instructions to a CPU (Central Processing Unit) to perform various processes are recorded in the storage unit 106. For example, memory devices such as RAM (Random Access Memory) and ROM (Read Only Memory), fixed disk devices such as hard disks, flexible disks, optical disks, etc. can be used as the storage unit 106.

[0021] The storage unit 106 stores sales data 106a, inspection data 106b, billing destination master data 106c, and verification method master data 106d.

[0022] FIG. 2 is a diagram showing an example of sales data. The sales data 106a is information for managing the recording of sales by a supplier. The sales data 106a in FIG. 2 is data before collation. As shown in FIG. 2, the sales data 106a includes the following items: order number, billing code, delivery note number, inspection date, customer part number, product code, product name, quantity, unit price, base price, consumption tax, and collation key, and these pieces of information are associated with each other. The order number is a number for identifying an order of a product from a supplier, and is a number assigned to each order. The billing code is an identification code of the billing destination. The delivery note number is an identification number of the delivery note. The inspection date is the date on which the product is received by the supplier. The customer part number is an identification number of the product managed by the supplier. The product code is an identification code of the product. The product name is the name of the product. The quantity is the quantity of the product. The unit price is the unit price of the product. The base price is an amount obtained by multiplying the quantity and the unit price. The consumption tax is the amount of consumption tax to be paid. The matching key is information on the matching item used during matching.

[0023] FIG. 3 is a diagram showing an example of inspection data. The inspection data 106b is data provided by a business partner, and is data indicating that the business partner has received the product. Note that the inspection data 106b in FIG. 3 is data before collation. As shown in FIG. 3, the inspection data 106b includes items such as order number, billing code, delivery note number, inspection date, product code, product name, quantity, unit price, base price, consumption tax, and collation key, and these pieces of information are associated with each other. Note that each item is the same as the sales data 106a.

[0024] The sales data 106a and the inspection data 106b include check items that are checked based on a check key, and check items used for checking. The check items are, for example, quantity, unit price, base price, and consumption tax, which are fixed items. The check items are, for example, order number, billing code, delivery note number, and inspection date, which can be set arbitrarily.

[0025] FIG. 4 is a diagram showing an example of the billing destination master. The billing destination master 106c is information for classifying the verification method according to the billing destination code. The billing destination master 106c includes items of billing destination code and verification method classification, and these pieces of information are associated with each other. The billing destination code is the same as the sales data 106a. The verification method classification is a classification number assigned to each verification method.

[0026] FIG. 5 is a diagram showing an example of the matching method master. The matching method master 106d is information on the matching key set in the matching method category. The matching method master 106d includes items of the matching method category and the matching key, and these pieces of information are associated with each other. The matching method category is the same as the billing destination master 106c, and the matching key is the same as the sales data 106a. In the matching method master 10d, any matching item can be set via the input device 112.

[0027] The storage unit 32 also stores sales data 106a and inspection data 106b updated at the time of matching, and matching result data 106e as a result of matching, which will be described in detail later.

[0028] Next, the control unit 102 will be described with reference to Fig. 1 again. The control unit 102 is a CPU or the like that performs overall control of the collation device 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, and required data, and executes various information processing based on these stored programs.

[0029] The control unit 102 performs information processing by matching the sales data 106a with the inspection data 106b based on various data stored in the storage unit 106.

[0030] A specific example of the processing executed by the control unit 102 will be described in detail below in "2. Specific Example of Processing".

[0031] [2. Specific examples of processing] Here, a specific example of the process executed by the collation device 100 will be described with reference to Figs. 6 to 9. Fig. 6 is a diagram showing an example of sales data after updating. Fig. 7 is a diagram showing an example of inspection data after updating. Fig. 8 is a diagram showing an example of collation result data. Fig. 9 is a diagram showing an example of a flowchart related to the collation method. As shown in Fig. 9, the collation device 100 collates the sales data 106a and the inspection data 106b using the sales data 106a, the inspection data 106b, the billing destination master 106c, and the collation method master 106d. Then, the collation device 100 generates collation result data 106e as the collation result.

[0032] As shown in Fig. 9, first, the control unit 102 acquires the sales data 106a and the inspection data 106b from the storage unit 106 (step S1). The control unit 102 acquires the verification method category from the billing destination master 106c in the storage unit 106 based on the billing destination code of the acquired sales data 106a and the inspection data 106b (step S2). Next, the control unit 102 acquires the verification key from the verification method master 106d in the storage unit 106 based on the acquired verification method category (step S3). Based on the verification key, the control unit 102 updates the sales data 106a shown in Fig. 2 to the sales data 106a shown in Fig. 6, and updates the inspection data 106b shown in Fig. 3 to the inspection data 106b shown in Fig. 7 (step S4). That is, in step S4, the control unit 102 updates the collation key item of the sales data 106a based on the billing destination master 106c and the collation method master 106d.

[0033] The control unit 102 collates the sales data 106a and the inspection data 106b in the collation items set in the collation key (step S5). The control unit 102 judges whether or not all the collation items match as a result of the collation in the collation items (step S6). If the control unit 102 judges that all the collation items match in step S6 (step S6: Yes), the control unit 102 collates the sales data 106a and the inspection data 106b in the check items set in the preset check key (step S7). The preset check key in step S7 is a fixed check item that cannot be arbitrarily set, and is the items of quantity, unit price, base price, and consumption tax. The control unit 102 judges whether or not all the check items match as a result of the collation in the check items (step S8). In step S8, the control unit 102 sequentially checks the check items of quantity, unit price, base price, and consumption tax.

[0034] If the control unit 102 determines in step S8 that all check items match (step S8: Yes), it determines that the matching result is positive (step S9) and proceeds to step S14. On the other hand, if the control unit 102 determines in step S8 that at least one check item does not match (step S8: No), it determines that the matching result is incorrect (step S10) and proceeds to step S14. In step S10, the control unit 102 determines which check items do not match.

[0035] Furthermore, if the control unit 102 determines in step S6 that there is no match in at least one comparison item (step S6: No), it determines whether or not there is sales data 106a (step S11). If the control unit 102 determines that there is sales data 106a (step S11: Yes), it determines that there is no inspection data 106b and that the data has not been inspected (step S12). On the other hand, if the control unit 102 determines that there is no sales data 106a (step S11: No), it determines that there is no sales data 106a and that the data has not been recorded (step S13).

[0036] Then, the control unit 102 generates the matching result data 106e based on the judgment results of steps S9, S10, S12, and S13 (step S14). As shown in FIG. 8, the matching result data 106e has items of billing destination (billing destination code), company information, billing destination information, and matching result. Items included in the company information include a matching key and check items including quantity, unit price, amount, and consumption tax, and similarly, items included in the billing destination information include a matching key and check items including quantity, unit price, amount, and consumption tax. As an example shown in FIG. 8, the matching result of the billing destination code "SE001" with which the matching key matches is the judgment result of step S9. The matching result of the billing destination code "SE002" with which the matching key matches is the judgment result of step S10, and the unit price is not matched. The matching result of the billing destination code "SE003" with which the matching key matches is the judgment result of step S10, and the quantity is not matched. The matching result for billing code "SE004" with a matching collation key is the judgment result of step S10, and the consumption tax does not match. The matching result for billing code "SE002" with a mismatched collation key is the judgment result of step S12, and it is not inspected. The matching result for billing code "SE005" with a mismatched collation key is the judgment result of step S13, and it is an unrecorded sale.

[0037] After executing step S14, the control unit 102 ends the comparison between the sales data 106a and the inspection data 106b.

[0038] As described above, according to this embodiment, after the sales data 106a and the inspection data 106b are collated in the collation items of the collation key, the sales data 106a and the inspection data 106b can be collated in the check items of the check key. In this case, since only the collation items of the collation key need to be set arbitrarily according to the billing destination, the management of the collation settings can be simplified. In addition, since the sales data 106a and the inspection data 106b can be collated based on the collation key and the check key, efficient collation can be performed automatically.

[0039] Furthermore, according to this embodiment, it is possible to appropriately determine whether the collation result is correct or incorrect for the check items.

[0040] Furthermore, according to this embodiment, when the comparison result is incorrect for a check item, it is possible to determine which check items are not identical.

[0041] Furthermore, according to this embodiment, when there is a mismatch in the collation items, it is possible to determine whether the item is uninspected or has not been recorded as sales by determining whether sales data 106a or inspection data 106b exists. Therefore, detailed collation results can be obtained by making a determination using the collation key and the check key.

[0042] [3. Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This embodiment can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby contributing to goals 8 and 9 of the SDGs.

[0043] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of SDGs Goals 12, 13, and 15.

[0044] Furthermore, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.

[0045] [4. Other embodiments] The present invention may be embodied in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

[0046] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using known methods.

[0047] In addition, the processing procedures, control procedures, specific names, information including parameters such as registered data and search conditions for each process, screen examples, and database configurations shown in this specification and drawings may be changed as desired unless otherwise specified.

[0048] Moreover, with regard to the verification device 100, the components shown in the figures are merely functional concepts, and the devices do not necessarily have to be physically configured as shown in the figures.

[0049] For example, the processing functions of the collation device 100, particularly the processing functions performed by the control unit, may be realized in whole or in part by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded in a non-transient computer-readable recording medium that includes programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the collation device 100 as necessary. That is, a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive). This computer program is executed by being loaded into a RAM, and cooperates with the CPU to form a control unit.

[0050] In addition, this computer program may be stored in an application program server connected to the verification device 100 via any network, and it is also possible to download all or a part of it as necessary.

[0051] In addition, the program for executing the process described in this embodiment may be stored in a non-transitory computer-readable recording medium, or may be configured as a program product. Here, the "recording medium" includes any "portable physical medium" such as a memory card, a Universal Serial Bus (USB) memory, a Secure Digital (SD) card, a flexible disk, a magneto-optical disk, a ROM, an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable and Programmable Read Only Memory (EEPROM (registered trademark)), a Compact Disk Read Only Memory (CD-ROM), a Magneto-Optical disk (MO), a Digital Versatile Disk (DVD), and a Blu-ray (registered trademark) Disc.

[0052] Moreover, a "program" is a data processing method written in any language or description method, and may be in any form, such as source code or binary code. Note that a "program" is not necessarily limited to a single configuration, but also includes a distributed configuration as multiple modules or libraries, and a program that works with a separate program, such as an OS, to achieve its function. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in the embodiments, as well as the installation procedure after reading, may use well-known configurations and procedures.

[0053] The various databases etc. stored in the memory unit are storage means such as memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files etc. used for various processes and providing websites.

[0054] The verification device 100 may be configured as an information processing device such as a known personal computer or a workstation, or may be configured as the information processing device to which any peripheral device is connected. The verification device 100 may be realized by installing software (including programs or data) that causes the device to realize the processing described in this embodiment.

[0055] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be functionally or physically distributed and integrated in any unit according to various additions or functional loads. In other words, the above-mentioned embodiments can be implemented in any combination, or the embodiments can be implemented selectively. [Industrial Applicability]

[0056] The present invention is useful for trading companies that mainly deal with machinery and steel. [Explanation of symbols]

[0057] 100 Collation device 102 Control section 104 Communication interface section 106 Storage section 106a Sales Data 106b Inspection data 106c Billing Master 106d Matching Method Master 108 Input / Output Interface Section 112 Input Devices 114 Output Device 200 Servers 300 Network

Claims

1. A verification device having a control unit for verifying a company's sales data and a billing recipient's inspection data, The sales data and the inspection data are associated with a plurality of items including a check item to be verified based on a preset check key, a billing destination code item for identifying the billing destination, and a verification item to be used for verification, a billing destination master in which the sales data, the inspection data, the billing destination code item, and a matching method classification item that classifies a matching method are associated with each other, and a matching method master in which the matching method classification item and a matching key to which the matching item is set are associated with each other; The control unit is Acquire the sales data and the inspection data; The verification method classification item is obtained from the billing destination master based on the billing destination code item included in the sales data and the inspection data; The matching key is obtained from the matching method master based on the matching method classification item. The sales data is collated with the inspection data in the collation items set in the collation key; When the sales data and the inspection data match in the verification item, the sales data and the inspection data are verified in the check item set in the check key; A matching device that generates matching results as matching result data.

2. The control unit is If the sales data and the inspection data match in the check items, the matching result is determined to be positive in the matching result data, 2. The collation device according to claim 1, wherein when the sales data and the inspection data do not match with respect to the check items, the collation result data indicates that the collation result is incorrect.

3. The check items include unit price, quantity, amount, and tax amount. The control unit is 3. The collation device according to claim 2, wherein when the sales data and the inspection data are inconsistent with each other for any of the check items, the check items in which the data are inconsistent are determined.

4. The control unit is If the sales data and the inspection data do not match in the comparison item, it is determined whether the sales data or the inspection data exists; If it is determined that only the sales data exists, the collation result is incorrect and the product has not been inspected.

2. The collation device according to claim 1, wherein when it is determined that only the inspection data exists, the collation result is determined to be incorrect, and sales have not been recorded.

5. A method for matching a company's sales data with a billing recipient's inspection data, comprising the steps of: The sales data and the inspection data are associated with a plurality of items including a check item to be checked based on a preset check key, a billing destination code item for identifying the billing destination, and a check item to be used for checking, A billing destination master in which the sales data, the inspection data, the billing destination code item, and a matching method classification item that classifies the matching method are associated with each other, and a matching method master in which the matching method classification item and a matching key to which the matching item is set are associated with each other are used, Acquire the sales data and the inspection data; The verification method classification item is obtained from the billing destination master based on the billing destination code item included in the sales data and the inspection data; The matching key is obtained from the matching method master based on the matching method classification item. The sales data is collated with the inspection data in the collation items set in the collation key; When the sales data and the inspection data match in the verification item, the sales data and the inspection data are verified in the check item set in the check key; A matching method in which a matching device including a control unit generates a matching result as matching result data.

6. A matching program for causing a matching device having a control unit to execute a matching method for matching a company's sales data with a billing recipient's inspection data, The sales data and the inspection data are associated with a plurality of items including a check item to be checked based on a preset check key, a billing destination code item for identifying the billing destination, and a check item to be used for checking, A billing destination master in which the sales data, the inspection data, the billing destination code item, and a matching method classification item that classifies the matching method are associated with each other, and a matching method master in which the matching method classification item and a matching key to which the matching item is set are associated with each other are used, Acquire the sales data and the inspection data; The verification method classification item is obtained from the billing destination master based on the billing destination code item included in the sales data and the inspection data; The matching key is obtained from the matching method master based on the matching method classification item. The sales data is collated with the inspection data in the collation items set in the collation key; When the sales data and the inspection data match in the verification item, the sales data and the inspection data are verified in the check item set in the check key; A collation program for causing the collation device to generate a collation result as collation result data.

Citation Information

Patent Citations

  • Collation system for sales credits

    JP1995129685A

  • Transaction details reconciliation system and transaction details reconciliation method

    JP2022050756A

  • Electronic application support apparatus, electronic application support method, and electronic application support program

    JP2022073054A