JP6789869B2 - Transaction information collation system - Google Patents

Description

The present invention relates to a system for collating commercial transaction data.

There is an information exchange / sharing system between companies that is realized under a secure network infrastructure as an EDI (Electronic Data Interchange) mechanism that electronically processes business transactions between orderers of goods and services between companies. There is.

Information on commercial transactions is divided into categories called information categories such as quotations, orders, and payments, and the information categories exchanged differ depending on the business process of the orderer and the contractor.

Member companies of the information exchange / sharing system between companies generate data in a format that can be imported into the information exchange / sharing system for each information category, and carry out business-to-business transactions according to the protocol in the information exchange / sharing system. ..

By registering the generated format in the DB and via the Web server, the ordering party can refer to the commercial transaction information on the Web screen for each information category.

On the other hand, among the commercial transaction data, there is a premium matching system that automatically collates the premium detail data composed of the detail data related to accounts payable or accounts payable and the transaction details data such as the acceptance details data for accounts payable or the billing details data for accounts payable.

In the premium collation system, sales attribute items that are the key for collation are defined, detailed data matched between the attribute items are collated, and pre-defined collation target items are automatically collated. As a result, it is possible to refer to the difference information between the information types, and it is effective in preventing the proto-language of recognition among the ordering parties.

By collating the commercial transaction information generated from the orderer or the contractor on a detailed basis between the information generated in different business processes, it is possible to obtain knowledge that cannot be obtained only by the individual commercial transaction information.

As an example, the shipping information for which data is generated from the contractor to the orderer and the accounts payable item information for which data is generated from the orderer to the contractor will be described. The shipping information includes information such as the shipping date, quantity, and amount of goods and services at the time of shipment. The accounts payable details information includes information such as the acceptance date, acceptance quantity, and amount of the ordered goods and services. As a result of allocating and collating the shipping quantity and acceptance quantity in this information with key items such as order number for each item, if there is a difference, either the ordering party has some kind of recognition proto-language, or There is a possibility that the accepted quantity will be smaller than the shipped quantity due to some defect in the ordered goods and services, and there will be a difference. In this way, by collating data between information categories, it is possible to obtain knowledge that cannot be obtained from information by information alone.

As a background technique of the present invention, for example, Japanese Patent Application Laid-Open No. 2004-62378 (Patent Document 1) is available. Patent Document 1 describes "a premium verification system that can reliably collate transaction data such as accounts receivable detail data and acceptance detail data with a computer system even when the seller distributes the ordered products to the purchaser". Is described.

Japanese Unexamined Patent Publication No. 2004-62378

The screens of commercial transaction information on the Web are independent for each information category, and it is difficult to compare data between the information categories, such as changing the screen of each information type many times. Further, in the comprehensive system described in Patent Document 1, there are only two patterns of collable commercial transaction information: accounts payable information and acceptance inspection information, and accounts payable details information and billing details information.

Therefore, in the comprehensive system described in Patent Document 1, it is essential to modify the program of the system in order to collate other information. There are multiple pieces of information on commercial transactions, and there are many types of information that can be combined, but the cost and labor increase because repairs are required each time a matching combination is added. In addition, the value of the item to be collated can only be collated with the latest data without considering the past information of the same key, but it is correct if the item value that also considers the past information is not collated in the commercial transaction information. There are cases where the collation result is not obtained.

Therefore, the present invention provides a system and an information processing device for collating between commercial transaction data by using a collation master DB in a system for exchanging commercial transaction information between a plurality of companies.

One of the typical transaction information collation systems of the present invention for solving the above problems is a transaction information collation system that collates commercial transaction information with a first server that receives commercial transaction information from the ordering party. It is provided with a second server that stores a plurality of types of commercial transaction information, and when the first server receives the orderer's information and the first commercial transaction information from the orderer, the first server executes a collation task based on the orderer's information. Is specified, and based on the identified collation task, it is determined whether or not the first commercial transaction information is the collation target, and if the first commercial transaction information is the collation target, it is collated with the first commercial transaction information. Identification of the second commercial transaction information, information items to be collated among the first commercial transaction information and the second commercial transaction information, and registration patterns of the information items are extracted by the second server, and based on the extracted information. Provided is a transaction information collation system that creates a collation result and stores it in a second server.

According to the present invention, the administrator updates the collation information master table to see if there is any difference in the information associated with the key information between two different information types in the commercial transaction information. Since the comparison can be performed without changing the input information, the work man-hours for the comparison can be reduced.

Issues, configurations and effects other than those described above will be clarified by the description of the following embodiments.

It is an overall system configuration diagram of an information exchange / sharing system between companies. It is a figure which shows the example of the hardware configuration in the EDI server of the information exchange / sharing system between companies. It is a figure which shows the example of the hardware configuration in the Web server of the information exchange / sharing system between companies. It is a figure which shows the hardware configuration example in the DB server of the information exchange / sharing system between companies. It is a list of the master table of collation information. This is a list of tables for registering the screen display contents of collation information and collation results. It is an overall processing sequence diagram from the registration of commercial transaction data to the screen display of the collation result. It is a flow chart of the collation target determination process of the registered commercial transaction data. It is the figure which showed the data registration content of the collation registration pattern of the commercial transaction data at the time of the difference registration and the collation screen result information. It is a flow chart of the collation result determination processing of the registered commercial transaction data. It is an image diagram of the search screen in the Web screen display of the collation result. It is an image diagram of the list display screen in the Web screen display of the collation result.

Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings.

FIG. 1 is a diagram showing an overall configuration example of the information exchange / sharing system 1 between companies according to the present embodiment.
The inter-company information exchange / sharing system 1 includes a core server 11 that manages information on the ordering party side, an EDI server 12 that electronically processes commerce transactions between ordering parties, and input regarding commerce transactions from a contractor who is a business partner. It is composed of a Web server 13 that accepts information, a DB server 14 that stores various information, an operation terminal 15 that performs maintenance of each server and registration of a master, and a user terminal 16 that accepts input from a contractor.

The core server 11 and the EDI server 12 are connected via a network, and the user terminal 16 and the Web server 13 are also connected via a network (for example, the Internet). Further, the EDI server 12, the Web server 13, the DB server 14, and the operation terminal 15 are connected by another network (for example, LAN or WAN).

The DB server 14 is composed of transaction data information DB 141, collation master information DB 142, and collation screen information DB 143. Details of each DB will be described later. The DB server 14 may store information other than the above. Further, although the specific configuration is not shown, the operation terminal 15 and the user terminal 16 in the business partner 1 may be equivalent to a general PC. Further, since the core server 11 may be a known core server, the description thereof will be omitted.

FIG. 2 is a diagram showing a hardware configuration example of the EDI server 12. The EDI server 12 includes a storage unit 21, an input unit 22, a control unit 23, and a network interface unit 24. Each part is connected by a bus (BUS). The storage unit 21 stores a program composed of an authentication function 211, a data reception function 212, a data registration function 213, a collation target determination function 214, a collation allocation function 215, a collation result determination function 216, and a collation data registration function 217. Has been done.

The input unit 22 is an input device such as a keyboard, a mouse, and a touch panel. The control unit 23 includes a CPU (Central Processing Unit) and a memory, and loads the program stored in the storage unit 21 into the memory and executes the program. The network interface unit 24 connects to the core server 11 and the Web server 13 via the above-mentioned network.

FIG. 3 is a diagram showing a hardware configuration example of the Web server 13. The Web server 13 includes a storage unit 31, a display unit 32, an input unit 33, a control unit 34, and a network interface unit 35. Each part is connected by a bus (BUS). The storage unit 31 stores a program including an authentication function 311, a menu display function 312, a collation result search function 313, and a collation result display function 314.

The input unit 33 is an input device such as a keyboard, a mouse, and a touch panel. The display unit 32 is a display device such as a liquid crystal display. A touch panel that also serves as an input device and a display device may be used. The control unit 34 includes a CPU and a memory, loads the program stored in the storage unit 31 into the memory, and executes the program. The network interface unit 35 connects the user terminal 16 to the EDI server 13 and the like via the above-mentioned network.

FIG. 4 is a diagram showing a hardware configuration example of the DB server 14. The DB server 14 includes a storage unit 41, an input unit 42, a control unit 43, and a network interface unit 44. Each part is connected by a bus (BUS). In the storage unit 41, user authentication information 411, transaction relationship information 412, commercial transaction data information 413, collation orderer master information 414, collation key master information 415, collation item master information 416, collation screen display item information 417, and collation result information 418 It is composed of data consisting of. Details of various information will be described later.

The input unit 42 is an input device such as a keyboard, a mouse, and a touch panel. Various information stored in the storage unit 41 is referred to by the EDI server 12 and the Web server 13 via the network interface unit 44. The control unit 43 includes a CPU and a memory (not shown).

FIG. 5 is a diagram showing a data configuration example of a collation information master table in which collation master information 142 for collation is defined. The collation information master table receives the request of the orderer including the orderer code for collation and information on what kind of collation is performed between which information categories, and the operation manager operates the operation terminal 16 in advance. It is created and stored in the DB server 14 as the collation master information 142.

The collation information master table described in this embodiment is composed of collation orderer master information 414, collation key master 415, and collation item master 416.

The collation orderer master information 414 stores the orderer code corresponding to the orderer and the collation task executed for the orderer code in association with each other. For example, when registering commercial transaction data, the value of the orderer code in the commercial transaction data is referred to, and if it is in the collation orderer master information 414, one or more collation tasks corresponding to the orderer code are executed. To do. Specifically, in the case of the orderer code HATTYUSYA1, the collation task SYOUGOU1 is hit.

The collation key master information 415 is used to define in which item the details of each commercial transaction data are assigned as collation key data, and to collate the details in which the items registered as key data match. In this embodiment, the collation task, the collation source information category, the collation destination information category, the information category key item 1, and the information category key item 2 are set as the collation key master information 415. Although the information classification key item can be set to two in this embodiment, three or more may be set.

Therefore, the collation key master information 415 is defined when the collation task includes the information category of the commercial transaction data registered in the collation source information category or the collation destination information category corresponding to the collation task to be executed in the collation key master information 415. Collation is performed using the provided information classification key items. More specifically, when the collation task is SYOUGOU1, the collation key master information 415 contains the shipping information which is the collation source information category and the accounts payable detail information which is the collation destination information category based on the entry corresponding to SYOUGOU1. A matching item is searched for using the order number which is the information classification key item 1 and the delivery key number which is the information classification key item 2.

The collation item master information 416 specifically defines which item is collated in the details in which the key data match. The collation source item and the collation destination item are defined respectively, and the items are collated with each other. In this embodiment, the collation item master information 416 is used as a collation task, collation item ID, collation source information classification, collation destination information classification, collation source item, collation source item value registration pattern, collation destination item, and collation destination item value registration pattern. , Is composed of the entries.

Needless to say, information other than the above may be used. In addition, the collation registration pattern can be selected from two patterns, normal registration and differential registration. In normal registration, the latest information is collated. In the difference registration, the registration is performed in consideration of the information of the same key item registered in the past. Details of each process will be described later.

FIG. 6 is a diagram showing a data configuration example of a collation information display table that stores collation results and is used at the time of screen display. The collation screen display item information 417 stores a collation ID that associates the collation task at the time of collation with the information classification, the key item, and the result. The collation result information 418 stores the collation result, the value of the collation source, and the value of the collation destination for the collation ID.

In the examples of FIGS. 5 and 6, the shipping information is obtained with respect to the shipping information data such as the orderer code "HATTYUSYA1", the contractor code "JUTYUSYA1", the order number "CHUBAN1", and the delivery key number "NOUHIN1". The result of comparing the shipment quantity "100" and the acceptance quantity "100" of the accounts payable detail information is registered as the collation result "no difference".

FIG. 7 describes an example of the processing operation of the information exchange / sharing system 1 between companies in this embodiment. In FIG. 7, the commercial transaction data uploaded by the core server 11 to the EDI server 12 of the inter-company information exchange / sharing system 1 is collated between the information categories on the contractor side user terminal 31 via the Web server 13 and the DB server 14. It is a figure explaining the process sequence diagram until the screen display that information becomes referenceable.

First, the EDI server 12 receives the authentication request 5111 sent by the upload command executed by the core server 11.

The authentication function 211 of the EDI server 12 confirms that the user ID and password of the authentication request 5111 exist in the user authentication information 411 of the DB server 14, and the user has the authority to use the inter-company information exchange / sharing system 1. The authentication process 5121 for checking the existence is executed.

Next, in the authentication process 5121, the authentication information extraction 5141 is supported by the DB server 14, and the authentication process 5121 is performed using the information required for authentication received from the DB server. After that, the authentication result 5122 is returned to the core server.

Specifically, when the user ID and password do not exist in the user authentication information 411 of the DB server 14 (in the case of authentication NG), the authentication function 211 of the EDI server 12 ends with an error, and the return value is set to the orderer's core server 11. Send to. In this case, the process may be terminated when the process is transmitted to the core server 11, or the process may be continued until the authentication is OK.

When the user ID and password exist in the user authentication information 411 of the DB server 14 (that is, when the authentication is OK), the core server 11 executes the commercial transaction data transmission 5112. The message reception function 212 of the EDI server 12 that has received the commercial transaction data executes the commercial transaction data reception process 5123.

After receiving the commercial transaction information, the data registration function 213 of the EDI server 12 instructs the commercial transaction data information 413 of the DB server 14 to register the data 5124. Since the details of the commercial transaction data differ depending on each information category, the commercial transaction data information 413 in the DB server 14 is stored separately for each information category.

After registering the commercial transaction data information, the determination process 5125 is performed to determine whether the commercial transaction data is data that uses the collation function. FIG. 8 is a flowchart of a determination process for determining whether or not the data uses the collation function.

In the flowchart of the determination process, it is mainly determined whether or not the user is a user who uses the determination process and whether or not the information classification requires the determination process.

In any information category, user information is included in the commercial transaction data. The orderer is the orderer code, and the contractor is the contractor code, which are included in the commercial transaction data. The collation target determination function 214 of the EDI server 12 extracts and transmits the collation orderer master information 414 in the DB server 14. Further, based on the received collation orderer master information 414, the EDI server 12 searches for master information that matches the orderer code in the commercial transaction data. If they do not match, the processing of the flowchart of FIG. 8 is completed and the processing of the sequence diagram of FIG. 7 is also completed because the user does not use the collation function.

If the orderer codes match, then it is determined whether the information classification exists in the collation key master information 415 in the DB server 14. Similar to the collation orderer master information 414, the collation target determination function 214 of the EDI server 12 extracts the information category from the collation key master information 415 in the DB server 14 and causes the information classification to be transmitted. The EDI server 12 determines whether or not the information classification registered in the received collation key master information 415 and the information classification of the commercial transaction data match, and if they do not match, the processing ends because the information classification is not applicable. If the information categories match, both the user and the information categories match, so it is regarded as the collation function target data and the process proceeds to the next process.

Returning to the flowchart of FIG. 7, the process to be executed next will be described. After executing the determination process, the collation data master allocation process 5126 of the EDI server 12 instructs the DB server 14 to extract the collation information. The information to be extracted in this embodiment is three types of collation key data 5143, collation item data 5144, and collation registration pattern 5145, but information other than the above may be extracted.

The collation key data is extracted from the collation key master information 415, the item of each commercial transaction data to be assigned is defined, and the items registered as the key data are collated with each other.

The collation item data and the collation registration pattern are extracted from the collation item master information 416. The collation item data defines which item is collated in the item with the same key. The collation source item and the collation destination item are defined respectively, and the items are collated with each other. Two patterns of collation registration pattern, normal registration or difference registration, can be selected. In normal registration, the latest information is collated. In the difference registration, the registration is performed in consideration of the information of the same key item registered in the past.

A more specific example will be described. FIG. 9 is a diagram showing the collation registration pattern in the accounts payable detail information in the data registration contents of the commercial transaction data at the time of differential registration and the collation screen result information.

Accounts payable details information This is an information category generated from the orderer to the contractor, but the same key data may be generated for the same contractor. In this embodiment, the data that the value of the key item is A, the acceptance amount is "100", and the correction category is new is already registered, and then a minus occurs due to the return of goods and services. I will explain.

In this case, for example, it is assumed that the data that the value of the key item is A, the acceptance amount is "20", and the correction category is canceled is generated. At this time, in the case of the normal registration pattern, since the latest information is collated with each other, the collation is performed with the acceptance amount being "20". However, in reality, the value of "20" in the acceptance amount is a minus, and the acceptance amount in the original key item A is "80" obtained by subtracting "20" from "100". In this way, considering the information of the same key registered in the past, when it is necessary to register the collation target item data, the registration pattern is defined in the master as the difference registration and the collation data is registered. Although the collation result is already registered in FIG. 9, the collation result is normally input when the process of FIG. 10 is completed.

After receiving the key information, item information, and registration pattern of the collation data extracted by the collation data master allocation process 5126 from the DB server 14, the collation result determination process 5127 is performed. The determination of the collation result is shown in FIG.

First, it is determined whether the collation destination or collation source commercial transaction data of the same key information is already registered. For example, in the case of shipping information and accounts payable details information, it is searched whether or not there is shipping information with the same key information when the accounts payable details information is registered.

If there is no collation destination or collation source commercial transaction data, no collation information is set as the collation result, and the transition to the collation screen display item data / collation result data DB registration process 5128 (hereinafter referred to as DB registration process 5128) in FIG. To do. When the collation destination or collation source commercial transaction data exists, the values are compared between the collation target items, and if they match, there is no difference, and if they do not match, there is a difference, and the process proceeds to the DB registration process 5128.

Returning to FIG. 7, the following flow will be described. After the collation result determination process 5127, the DB registration process 5128 is executed for the collation screen display item information 417 and the collation result information 418 of the DB server 14. In this DB registration process 5128, the value extracted by the collation data master allocation process 5126 of the EDI server 12 is registered in the collation screen display item information 417, and the result of the collation result determination process 5127 of the EDI server 12 is registered in the collation result information 418. To register. Although the flow of collation result display is described in FIG. 7 after the DB registration process 5128, it is not always necessary that the process is continuous, and the process may be temporarily completed by the DB registration process 5128.

Next, the process for displaying the collation information will be described. The registered information is displayed as a Web screen on a display device (not shown) provided in the user terminal 16 by the collation result display function 314 of the Web server 13, and can be referred to on the browser by the user operating the input device. Is.

When referencing on the Web screen displayed on the user terminal 16, the user inputs the user ID and password on the browser by the input device of the user terminal 16. This input is transmitted to the Web server 13 as an authentication request 5161, and the authentication process 5131 is executed by the authentication function 311 included in the Web server 13.

After the DB server 14 extracts the authentication information 5147 and returns the authentication result 5132 to the user terminal 16, the user can log in. After logging in, the user transitions to the collation result search screen by selecting the collation function menu displayed by the menu display function 312 via the Web screen. In this embodiment, the collation result search function 313 of the Web server 13 searches for the collation result to be displayed on the screen by executing the collation data result search process 5133 based on the information input to the search screen. Further, even when there are a plurality of collation patterns within one user, such as information category A and information category B, information category C and information category D, they can be selected from the search screen.

The collation data / result based on the search result is acquired 5134, and the collation screen display item information 417 and the collation result information 418 of the DB server 14 are extracted 5148 to be displayed based on the collation search result. The Web server displays the extracted information on the screen 5135. As a result, the user can refer to the collation result in the item unit between each information category on the browser.

FIG. 11 is a diagram showing a collation information search screen displayed as a Web screen on the display device of the user terminal 16. Although the subject is described as a user for the sake of simplification of the explanation of FIG. 11, in reality, the process performed by the user terminal 16, the Web server 13, and the DB server 14 that have received the user's operation as described above is performed in cooperation with each other. Is.

The screen name of the collation information search screen is message collation search. On the search screen, first, the search target pull-down is displayed according to the setting contents of the collation master, so the user selects the search target. If the user has two or more collation patterns, the collation pattern desired to be collated is selected from this pull-down menu.

When the user selects a search target, search items, conditions, and search values are displayed on the search screen. In FIG. 11, an example will be described in which the shipping information and the accounts payable detail information are collated, and the collation target items are the shipping quantity and the acceptance quantity, the shipping unit price and the acceptance unit price, and the shipping date and the acceptance date. It is possible to enter the items of each item on the search screen. For example, the search item is an orderer code, a contractor code, or the like, and conditions such as whether to search for an item equal to the input value can be set. Further, the following conditions (a) to (c) can be set for the search of the collation result. The conditions are that (a) there is both shipping information and accounts payable details information, (b) a message containing only shipping information is targeted, and (c) a message containing only accounts payable details information is targeted.

By satisfying the above conditions (a) to (c), whether to display the details in which both the collation source information and the collation destination information exist, or to display the information registered as the details in only one of them. It can be selectable.

Further, when displaying the details in which both the collation source information and the collation destination information exist, the following four search values (a1) to (a4) can be further selected. The conditions are that (a1) there is a quantity collation difference, (a2) there is a unit price collation difference, (a3) there is a shipment / acceptance date collation difference, and (a4) there is no difference. ..

In this embodiment, the items of quantity, unit price, and shipping / acceptance date are the items to be collated. Therefore, in FIG. 11, the above items (a1) to (a3) are checked. As a result, it is possible to search only the information having a difference from the collation result.

FIG. 12 is a diagram showing a collation information result list screen. When the user sets conditions and search values for each search item on the search screen shown in FIG. 11 and presses the search button, a collation list targeting the shipping information and accounts payable details information in FIG. 12 is displayed on the web of the user terminal 16. It is displayed on the screen.

In this embodiment, it is assumed that the search result screen shown in FIG. 12 has the following display items. The display items are (1) No. , (2) Orderer code, (3) Contractor code, (4) Order number, (5) Delivery key number, (6) Quantity verification, (6-1) Verification result, (6-2) Shipment quantity, (6-3) Acceptance quantity, (7) Unit price collation, (7-1) Collation result, (7-2) Shipment quantity, (7-3) Acceptance quantity, (8) Shipment / acceptance date verification, (8- 1) Collation result, (8-2) shipping date, (8-3) acceptance date.

(1) is a number assigned to each display item. Since the collation result is determined for each item of commercial transaction information, it is equal to the number of items. (2) displays the orderer code of the search result. (3) displays the contractor code of the search result. (4) displays the order number of the search result. (5) displays the delivery key number of the search result. The keys of the collation information master are targeted for (4) and (5).

(6) displays the shipping quantity of the collation source, the accepted quantity of the collation destination, and the collation result when collating them. The shipping quantity, acceptance quantity, and collation result are displayed according to the values in the collation result table. (7) displays the shipping unit price of the collation source, the acceptance unit price of the collation destination, and the collation result when collating them. The shipping unit price, acceptance unit price, and collation result are displayed according to the values in the collation result table. (8) displays the shipping date of the collation source, the acceptance date of the collation destination, and the collation result when collating them. The shipping date, acceptance date, and collation result are displayed according to the values in the collation result table. The values of (6) to (8) differ depending on the collation target item.

As described above, by having the collation information master table of this embodiment and the collation information display table created by collating various information using the collation information master table, the information of commercial transactions is different. It is possible to more easily confirm whether or not there is a difference in the information associated with the key information between the two information types. Specifically, when the administrator updates the collation information master table, comparison can be performed without changing the input information, so that the man-hours for comparison can be reduced. In addition, the user can access each information by operating the search screen and can more easily confirm whether or not there is a difference in the information by comparing the screens.

Furthermore, when adding a pattern to be collated, it is possible to freely change the key item, the item to be collated, and the registration pattern by adding the definition of the master information without modifying the collation processing program. It is possible to carry out the determination process of the collation result according to the above.

The present invention is not limited to the above-mentioned examples, and includes various modifications. For example, the above-described embodiment has been described in detail in order to explain the present invention in an easy-to-understand manner, and is not necessarily limited to those having all the described configurations. Further, it is possible to replace a part of the configuration of one embodiment with the configuration of another embodiment, and it is also possible to add the configuration of another embodiment to the configuration of one embodiment. Further, it is possible to add / delete / replace a part of the configuration of each embodiment with another configuration. Further, each of the above configurations, functions, processing units, processing means and the like may be realized by hardware by designing a part or all of them by, for example, an integrated circuit. Further, each of the above configurations, functions, and the like may be realized by software by the processor interpreting and executing a program that realizes each function. Information such as programs, tables, and files that realize each function can be placed in a memory, a hard disk, a recording device such as an SSD (Solid State Drive), or a recording medium such as an IC card, an SD card, or a DVD.

1 ... Inter-company information exchange / sharing system, 11 ... Core server, 12 ... EDI server, 13 ... Web server, 14 ... DB server, 15 ... Operation terminal, 16 ... -User terminal, 21 ... storage unit, 22 ... input unit, 23 ... control unit, 24 ... network interface unit, 31 ... storage unit, 32 ... display unit, 33 ...・ Input unit, 34 ・ ・ ・ Control unit, 35 ・ ・ ・ Network interface unit, 41 ・ ・ ・ Storage unit, 42 ・ ・ ・ Input unit, 43 ・ ・ ・ Control unit, 44 ・ ・ ・ Network interface unit, 211 ・・ ・ Authentication function, 212 ・ ・ ・ Data reception function, 213 ・ ・ ・ Data registration function, 214 ・ ・ ・ Collation target judgment function, 215 ・ ・ ・ Collation allocation function, 216 ・ ・ ・ Collation result judgment function, 217 ・ ・-Collaboration data registration function, 311 ... Authentication function, 312 ... Menu display function, 313 ... Collation result search function, 314 ... Collation result display function, 411 ... User authentication information, 412 ... -Business relationship information, 413 ... Commercial transaction data information, 414 ... Verification orderer master information, 415 ... Verification key master information, 416 ... Verification item information, 417 ... Verification screen display item information, 418・ ・ ・ Collation result information

Claims (6)

It is a transaction information collation system that collates between commercial transaction information.
A first server that connects to the orderer's server and receives commercial transaction information from the orderer,
Equipped with a second server that stores multiple types of commercial transaction information
The first server is
Upon receiving the ordering party information and the first commercial transaction information from the ordering party, the collation task to be executed is specified based on the received information of the ordering party.
Based on the identified collation task, it is determined whether or not the first commercial transaction information is the collation target.
When the first commercial transaction information is a collation target, the identification of the second commercial transaction information to be collated with the first commercial transaction information and the collation target of the first commercial transaction information and the second commercial transaction information. The information item to be used and the registration pattern of the information item are extracted by the second server.
A transaction information collation system characterized in that a collation result is created based on the extracted information and stored in the second server. The transaction information collation system according to claim 1.
A third server that accepts input of information from the contractor among the plurality of commercial transaction information is further provided.
The third server is a transaction information collation system characterized in that, based on an input from the contractor, the collation result stored in the second server is searched and a screen is output to the contractor. The transaction information collation system according to claim 2.
A management device for managing the first server, the second server, and the third server is further provided.
The management device secondly includes the collation task stored in the second server, the second commercial transaction information to be collated, the information item, and registration information or modification information including at least one of the registration patterns. Transaction information collation system characterized by sending to the server of. The transaction information collation system according to claim 1.
The registration pattern is a transaction information collation system comprising at least a normal registration in which the value of the information item is registered as it is and a difference registration in which the value of the information item is registered as a difference. The transaction information collation system according to claim 2.
The input from the contractor includes an input for selecting from predetermined items for specifying a search target, an input for selecting whether or not there is a difference in the information items, and the first commercial transaction information or the second. A transaction information collation system characterized in that it has at least one of an input for selecting one of the commercial transaction information. The transaction information collation system according to claim 1.
The collation task is a transaction information collation system characterized in that it includes one or more information classification key items for identifying a first information as a collation source and a second information as a collation destination.

Images