WO2019179025A1 - 关联交易识别方法、程序、装置及存储介质 - Google Patents

关联交易识别方法、程序、装置及存储介质 Download PDF

Info

Publication number
WO2019179025A1
WO2019179025A1 PCT/CN2018/102087 CN2018102087W WO2019179025A1 WO 2019179025 A1 WO2019179025 A1 WO 2019179025A1 CN 2018102087 W CN2018102087 W CN 2018102087W WO 2019179025 A1 WO2019179025 A1 WO 2019179025A1
Authority
WO
WIPO (PCT)
Prior art keywords
name
contract
seal
transaction
list
Prior art date
Application number
PCT/CN2018/102087
Other languages
English (en)
French (fr)
Inventor
苟翔
Original Assignee
平安科技（深圳）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2019179025A1 publication Critical patent/WO2019179025A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/12—Accounting
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions

Definitions

  • the present application relates to the field of computer technologies, and in particular, to an associated transaction identification method, a program, an electronic device, and a computer readable storage medium.
  • the existing related party transactions are issued by the parent and subsidiary companies within the enterprise group.
  • the transaction volume is very large. It is necessary to manually identify whether the related transactions are related to the system through the staff, and the manual information needs to be manually re-recorded to increase the staff. A lot of work, can not guarantee the accuracy of the associated transaction identification.
  • the current identification of related transactions is identified based on the contents of the accounting after the transaction is completed. Therefore, there is a need to provide a method for quickly and accurately identifying associated transactions from a large amount of transaction data.
  • the present application provides an associated transaction identification method, program, electronic device and computer readable storage medium, the main purpose of which is to accurately identify whether there is a related transaction in the process of printing the transaction.
  • the print application including one or more seals and contract participants of the application call;
  • the names of other contract participants except the contract participants are respectively matched with the list of related parties.
  • the matching is successful, the related transactions are identified from the transaction, and the recognition result is presented to the user.
  • the present application further provides an associated transaction identification method, the method comprising:
  • the print application including one or more seals and contract participants of the application call;
  • the list of related parties is retrieved according to the seal number of the seal as a list of related parties of the contract participant;
  • the names of other contract participants except the contract participants are respectively matched with the list of related parties.
  • the matching is successful, the related transactions are identified from the transaction, and the recognition result is presented to the user.
  • the present application further provides an associated transaction identification program, the program comprising:
  • a receiving module configured to receive a print application submitted by a user for a transaction, where the print application includes one or more seals and contract participants requested by the application;
  • a matching module configured to match, respectively, a name of the contract participant with a legal entity name corresponding to the one or more seals according to a preset first matching rule
  • a retrieving module configured to: when the name of the contract participant exactly matches the name of the legal entity corresponding to the seal, the list of related parties is retrieved according to the seal number of the seal as a list of related parties of the contract participant;
  • An identification module configured to match a name of another contract participant other than the contract participant with the related party list, and when the matching is successful, identify the related transaction from the transaction, and display the recognition result to user.
  • the present application further provides a computer readable storage medium having an associated transaction identification program stored thereon, and the program is implemented by the processor to implement the associated transaction identification method as described above. Any step.
  • the associated transaction identification method, the program, the electronic device and the computer readable storage medium proposed by the present application can accurately identify whether the transaction has a related transaction in the process of printing for a certain transaction, without The accounting accounts identify related transactions and improve the processing efficiency of subsequent related transactions.
  • FIG. 1 is a schematic diagram of a preferred embodiment of an electronic device of the present application.
  • FIG. 2 is a schematic diagram of a program module of a related transaction identification program according to the present invention.
  • FIG. 3 is a flow chart of a preferred embodiment of the associated transaction identification method of the present application.
  • the present application provides an associated transaction identification method, which is applied to an electronic device 1.
  • FIG. 1 it is a schematic diagram of a preferred embodiment of the electronic device 1 of the present application.
  • the electronic device 1 may be a terminal device with a data processing function, such as a server, a smart phone, a tablet computer, a portable computer, a desktop computer, etc.
  • the server may be a rack server, a blade server, or a tower. Server or rack server.
  • the electronic device 1 includes a memory 11, a processor 12, a communication bus 13, a display 14, and a network interface 15.
  • the memory 11 includes at least one type of readable storage medium including a flash memory, a hard disk, a multimedia card, a card type memory (for example, an SD or DX memory, etc.), a magnetic memory, a magnetic disk, an optical disk, and the like.
  • the memory 11 may be an internal storage unit of the electronic device 1, such as a hard disk of the electronic device 1, in some embodiments.
  • the memory 11 may also be an external storage device of the electronic device 1 in other embodiments, such as a plug-in hard disk equipped on the electronic device 1, a smart memory card (SMC), and a secure digital (Secure Digital) , SD) card, flash card (Flash Card), etc. Further, the memory 11 may also include both an internal storage unit of the electronic device 1 and an external storage device.
  • the memory 11 can be used not only for storing application software and various types of data installed in the electronic device 1, such as the associated transaction identification program 10, a preset first matching rule, and a preset second matching rule, and the like. Store data that has been output or will be output.
  • the related transaction identification program 10 is installed between the company printing system (not identified in the figure) and the related business system (not shown), and is used for receiving the application for printing of a transaction submitted by the user through the printing system.
  • the preset first matching rule is used to accurately specify the name of the contract participant entered by the user and the legal entity name corresponding to the seal Matching;
  • the preset second matching rule is used to vaguely match the name of the contract participant entered by the user with the name of the legal entity corresponding to the seal.
  • the processor 12 may be a Central Processing Unit (CPU), controller, microcontroller, microprocessor or other data processing chip for running program code or processing stored in the memory 11. Data, such as associated transaction identification program 10, and the like.
  • CPU Central Processing Unit
  • controller microcontroller
  • microprocessor or other data processing chip for running program code or processing stored in the memory 11.
  • Data such as associated transaction identification program 10, and the like.
  • Communication bus 13 is used to implement connection communication between these components.
  • the display 14 can be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, and an Organic Light-Emitting Diode (OLED) touch device.
  • the display 14 may also be referred to as a display screen or a display unit for displaying information processed in the electronic device 1 and a user interface for displaying visualization.
  • the network interface 15 may include a standard wired interface, a wireless interface (such as a WI-FI interface), and is generally used to establish a communication connection between the electronic device 1 and other electronic devices.
  • the electronic device 1 establishes a communication connection with the client (not identified in the figure) through the network interface 15, and the user accesses the printing system through the client, and submits the application for printing through the printing system.
  • Figure 1 shows only the electronic device 1 with components 11-15, but it should be understood that not all illustrated components may be implemented, and more or fewer components may be implemented instead.
  • the electronic device 1 may further include a user interface
  • the user interface may include an input unit such as a keyboard
  • the optional user interface may further include a standard wired interface and a wireless interface.
  • the associated transaction identification program 10 is stored in the memory 11.
  • the processor 12 executes the associated transaction identification program 10 stored in the memory 11, the following steps are implemented:
  • the print application including one or more seals and contract participants of the application call;
  • the list of related parties is retrieved according to the seal number of the seal as a list of related parties of the contract participant;
  • related party transactions are transactions between related parties of the enterprise.
  • Common related party transactions include: buying or selling goods, purchasing other assets (for example, equipment or buildings, etc.), providing or accepting labor services, guarantees, providing funds, leasing, agency, etc. .
  • Related party transactions are indispensable for the existence and development of a company. Therefore, the company must be cautious in dealing with related party transactions. However, the identification of connected transactions is crucial in the process of related party transactions. Next, the process of identifying the associated transaction will be explained.
  • the user refers to a company employee, for example, a company legal person
  • the user inputs specific information of the application for printing through the company's printing system for a transaction, including: one or more seals invoked, the pen The name of the contract involved in the transaction, the name of the two or more contract participants, the amount of the agreement, the number of contracts, etc., and submit the application for printing.
  • the name of the legal entity corresponding to the seal invoked by the printing application and the name of the contract participant entered by the user are read from the printing application.
  • the transaction involves only one contract, and the contract has only two contract participants (ie, Party A and Party B participants).
  • the preset first matching rule It is judged whether the contract participant entered by the user can accurately match the name of the legal entity corresponding to the seal.
  • the preset first matching rule includes: when the name of the contract participant is completely consistent with the name of the legal entity corresponding to the seal, it is determined that the contract participant and the seal can achieve accurate matching.
  • the number of contract participants entered by the user may be one or more, and one or more contract participants can accurately match the different seals invoked in the printed application, then one will be Or a plurality of contract participants respectively link with the seals that can be precisely matched with them, and retrieve the list of related parties corresponding to each seal according to the seal number as a list of related parties of the contract participants linked to the seal. Then the related party list is matched with other contract participants respectively. If the matching is successful, it indicates that there is a related transaction in the transaction.
  • the seal invoked in the application for printing includes A
  • the seal A called in the application can be accurately matched with Party A, according to the seal.
  • A's seal number from the related party trading system, retrieves the corresponding list of related parties, as the list of related parties of Party A's participant A, and matches with the entered Party B's participant M.
  • Party A's list of related parties includes Party B's participation.
  • the square M it is judged that there is a relationship between A and M, that is, there is an associated transaction AM in the transaction, and the result is presented to the user through the display interface of the client.
  • Party A and Party A match the seals A and B respectively, and the associations of A and B are respectively obtained.
  • the party list is matched with Party B's participant M. If both Party A and B's related party list include Party B Party M, there are related transactions AM and BM in the transaction, and the result is displayed to the user through the client's display interface. .
  • the number of seals is consistent with the total number of contract participants: Assume that three seals are used in the application for printing, and Party A's participants enter A (standard name) and B (non-standard name), and Party B's participants enter M. (non-standard name or standard name), the number of seals (three) is the same as the total number of contract participants (two contract party A parties, one contract party B party, a total of three), and there is no error in the user input process. Under the premise, the contract participants who can be entered by the user by default can be matched with the different seals invoked in the application for printing.
  • the corresponding list of related parties of each seal can be directly retrieved, and then the names of the legal entities corresponding to the other seals are respectively
  • the related party list is accurately matched, and the matching result is de-duplicated to obtain the recognition result of identifying the related transaction from the transaction.
  • the number of seals invoked in the application for printing is inconsistent with the total number of contract participants: assuming that two seals are invoked in the application for printing, the parties to Party A enter A (standard name) and B (non-standard name), Party B Participants enter M (non-standard name or standard name).
  • a preset second matching rule when the legal entity name corresponding to the seal completely includes the name of the contract participant, or the name of the contract participant completely includes the legal entity name corresponding to the seal, The contract participants match the seal implementation. It can be understood that when the user enters the name of the contract participant, the non-standard name of the company corresponding to the contract participant is entered. When the name of the participant entered is not exactly the same as the legal entity name corresponding to the seal, the participant There is no exact match between the seal and the seal.
  • the above steps need to be performed on the premise that the related party list is maintained in a timely manner. Otherwise, the recognition result may be wrong.
  • the user may determine whether there is a related transaction in the transaction according to the actual situation, and receive the judgment result input by the user, and if the same as the above recognition result, retain the existing recognition result. If the above recognition results are inconsistent, the judgment result input by the user is retained, and the user is prompted to adjust the recognition result.
  • the electronic device 1 proposed in the above embodiment improves the processing efficiency of the subsequent related transaction by accurately identifying whether the transaction exists in the transaction during the printing process for a certain transaction.
  • the associated transaction identification program 10 may also be divided into one or more modules, one or more modules are stored in the memory 11 and executed by one or more processors (this implementation)
  • the processor 12 is executed to complete the application
  • a module referred to herein refers to a series of computer program instructions that are capable of performing a particular function.
  • FIG. 2 it is a schematic diagram of a program module of the associated transaction identification program 10 of the present application.
  • the associated transaction identification program 10 can be divided into a receiving module 110, a matching module 120, a calling module 130, and an identification module. 140.
  • the functions or operation steps implemented by the modules 110-140 are as follows:
  • the receiving module 110 is configured to receive a print application submitted by the user for a transaction, where the print application includes one or more seals and contract participants of the application call;
  • the matching module 120 is configured to match the name of the contract participant with the legal entity name corresponding to the one or more seals according to a preset first matching rule
  • the retrieving module 130 is configured to: when the name of the contract participant completely matches the name of the legal entity corresponding to the seal, retrieve the list of related parties according to the seal number of the seal, as the list of related parties of the contract participant ;and
  • the user refers to a company employee, for example, a company legal person
  • the user inputs specific information of the application for printing through the company's printing system for a transaction, including: one or more seals invoked, the pen The name of the contract involved in the transaction, the name of the two or more contract participants, the amount of the agreement, the number of contracts, etc., and submit the application for printing.
  • the name of the legal entity corresponding to the seal invoked by the printing application and the name of the contract participant entered by the user are read from the printing application.
  • the transaction involves only one contract, and the contract has only two contract participants (ie, Party A and Party B participants).
  • the preset first matching rule It is judged whether the contract participant entered by the user can accurately match the name of the legal entity corresponding to the seal.
  • the preset first matching rule includes: when the name of the contract participant is completely consistent with the legal entity name corresponding to the seal, determining that the contract participant and the seal can achieve an exact match.
  • the seal of the company is invoked by the application for printing, because the legal entity name corresponding to the seal is the company standard name, That is to say, when the name of the contracted party entered is exactly the same as the name of the legal entity corresponding to the seal, the contract participant and the seal can be accurately matched.
  • the number of contract participants entered by the user may be one or more, and one or more contract participants can accurately match the different seals invoked in the printed application, then one will be Or a plurality of contract participants respectively link with the seals that can be precisely matched with them, and retrieve the list of related parties corresponding to each seal according to the seal number as a list of related parties of the contract participants linked to the seal. Then the related party list is matched with other contract participants respectively. If the matching is successful, it indicates that there is a related transaction in the transaction.
  • the seal invoked in the application for printing includes A
  • the seal A called in the application can be accurately matched with Party A, according to the seal.
  • A's seal number from the related party trading system, retrieves the corresponding list of related parties, as the list of related parties of Party A's participant A, and matches with the entered Party B's participant M.
  • Party A's list of related parties includes Party B's participation.
  • the square M it is judged that there is a relationship between A and M, that is, there is an associated transaction AM in the transaction, and the result is presented to the user through the display interface of the client.
  • Party A and Party A match the seals A and B respectively, and the associations of A and B are respectively obtained.
  • the party list is matched with Party B's participant M. If both Party A and B's related party list include Party B Party M, there are related transactions AM and BM in the transaction, and the result is displayed to the user through the client's display interface. .
  • the number of seals is consistent with the total number of contract participants: Assume that three seals are used in the application for printing, and Party A's participants enter A (standard name) and B (non-standard name), and Party B's participants enter M. (non-standard name or standard name), the number of seals (three) is the same as the total number of contract participants (two contract party A parties, one contract party B party, a total of three), and there is no error in the user input process. Under the premise, the contract participants who can be entered by the user by default can be matched with the different seals invoked in the application for printing.
  • the corresponding list of related parties of each seal can be directly retrieved, and then the names of the legal entities corresponding to the other seals are respectively
  • the related party list is accurately matched, and the matching result is de-duplicated to obtain the recognition result of identifying the related transaction from the transaction.
  • the number of seals invoked in the application for printing is inconsistent with the total number of contract participants: assuming that two seals are invoked in the application for printing, the parties to Party A enter A (standard name) and B (non-standard name), Party B Participants enter M (non-standard name or standard name).
  • a and M are related, that is, Said that there is a related transaction AM in the transaction; then, according to the seal number of the seal that does not match any of the contract participants, the corresponding list of related parties is retrieved, respectively Please make a fuzzy match for all contract participants.
  • a preset second matching rule when the legal entity name corresponding to the seal completely includes the name of the contract participant, or the name of the contract participant completely includes the legal entity name corresponding to the seal, The contract participants match the seal implementation. It can be understood that when the user enters the name of the contract participant, the non-standard name of the company corresponding to the contract participant is entered. When the name of the participant entered is not exactly the same as the legal entity name corresponding to the seal, the participant There is no exact match between the seal and the seal.
  • the above steps need to be performed on the premise that the related party list is maintained in a timely manner. Otherwise, the recognition result may be wrong.
  • the user may determine whether there is a related transaction in the transaction according to the actual situation, and receive the judgment result input by the user, and if the same as the above recognition result, retain the existing recognition result. If the above recognition results are inconsistent, the judgment result input by the user is retained, and the user is prompted to adjust the recognition result.
  • the present application also provides an associated transaction identification method.
  • FIG. 3 it is a flowchart of a preferred embodiment of the associated transaction identification method of the present application. The method can be performed by a device that can be implemented by software and/or hardware.
  • the associated transaction identification method includes: steps S1-S4.
  • Step S1 receiving a print application submitted by the user for a transaction, the print application including one or more seals and contract participants of the application call;
  • Step S2 matching the name of the contract participant with the name of the legal entity corresponding to the one or more seals according to a preset first matching rule
  • Step S3 when the name of the contract participant completely matches the name of the legal entity corresponding to the seal, the list of related parties is retrieved according to the seal number of the seal as a list of related parties of the contract participant;
  • step S4 the names of other contract participants except the contract participants are respectively matched with the list of related parties.
  • the matching is successful, the related transactions are identified from the transaction, and the identification result is displayed to the user.
  • related party transactions are transactions between related parties of the enterprise.
  • Common related party transactions include: buying or selling goods, purchasing other assets (for example, equipment or buildings, etc.), providing or accepting labor services, guarantees, providing funds, leasing, agency, etc. .
  • Related party transactions are indispensable for the existence and development of a company. Therefore, the company must be cautious in dealing with related party transactions. However, the identification of connected transactions is crucial in the process of related party transactions. Next, the process of identifying the associated transaction will be explained.
  • the user refers to a company employee, for example, a company legal person
  • the user inputs specific information of the application for printing through the company's printing system for a transaction, including: one or more seals invoked, the pen The name of the contract involved in the transaction, the name of the two or more contract participants, the amount of the agreement, the number of contracts, etc., and submit the application for printing.
  • the name of the legal entity corresponding to the seal invoked by the printing application and the name of the contract participant entered by the user are read from the printing application.
  • the transaction involves only one contract, and the contract has only two contract participants (ie, Party A and Party B participants).
  • the preset first matching rule It is judged whether the contract participant entered by the user can accurately match the name of the legal entity corresponding to the seal.
  • the preset first matching rule includes: when the name of the contract participant is completely consistent with the legal entity name corresponding to the seal, determining that the contract participant and the seal can achieve an exact match.
  • the seal of the company is invoked by the application for printing, because the legal entity name corresponding to the seal is the company standard name, That is to say, when the name of the contracted party entered is exactly the same as the name of the legal entity corresponding to the seal, the contract participant and the seal can be accurately matched.
  • the seal A called in the application for printing can be accurately matched with Party A, according to the seal.
  • A's seal number from the related party trading system, retrieves the corresponding list of related parties, as the list of related parties of Party A's participant A, and matches with the entered Party B's participant M.
  • Party A's list of related parties includes Party B's participation.
  • the square M it is judged that there is a relationship between A and M, that is, there is an associated transaction AM in the transaction, and the result is presented to the user through the display interface of the client.
  • Party A and Party A match the seals A and B respectively, and the associations of A and B are respectively obtained.
  • the party list is matched with Party B's participant M. If both Party A and B's related party list include Party B Party M, there are related transactions AM and BM in the transaction, and the result is displayed to the user through the client's display interface. .
  • the number of seals is consistent with the total number of contract participants: Assume that three seals are used in the application for printing, and Party A's participants enter A (standard name) and B (non-standard name), and Party B's participants enter M. (non-standard name or standard name), the number of seals (three) is the same as the total number of contract participants (two contract party A parties, one contract party B party, a total of three), and there is no error in the user input process. Under the premise, the contract participants who can be entered by the user by default can be matched with the different seals invoked in the application for printing.
  • the corresponding list of related parties of each seal can be directly retrieved, and then the names of the legal entities corresponding to the other seals are respectively
  • the related party list is accurately matched, and the matching result is de-duplicated to obtain the recognition result of identifying the related transaction from the transaction.
  • the number of seals invoked in the application for printing is inconsistent with the total number of contract participants: assuming that two seals are invoked in the application for printing, the parties to Party A enter A (standard name) and B (non-standard name), Party B Participants enter M (non-standard name or standard name).
  • a and M are related, that is, Said that there is a related transaction AM in the transaction; then, according to the seal number of the seal that does not match any of the contract participants, the corresponding list of related parties is retrieved, respectively Please make a fuzzy match for all contract participants.
  • a preset second matching rule when the legal entity name corresponding to the seal completely includes the name of the contract participant, or the name of the contract participant completely includes the legal entity name corresponding to the seal, The contract participants match the seal implementation. It can be understood that when the user enters the name of the contract participant, the non-standard name of the company corresponding to the contract participant is entered. When the name of the participant entered is not exactly the same as the legal entity name corresponding to the seal, the participant There is no exact match between the seal and the seal.
  • the above steps need to be performed on the premise that the related party list is maintained in a timely manner. Otherwise, the recognition result may be wrong.
  • the user may determine whether there is a related transaction in the transaction according to the actual situation, and receive the judgment result input by the user, and if the same as the above recognition result, retain the existing recognition result. If the above recognition results are inconsistent, the judgment result input by the user is retained, and the user is prompted to adjust the recognition result.
  • the related transaction identification method proposed in the above embodiment improves the processing efficiency of the subsequent related transaction by accurately identifying whether the transaction exists in the transaction in the process of printing for a certain transaction.
  • the embodiment of the present application further provides a computer readable storage medium, where the associated transaction identification program 10 is stored, and when the program is executed by the processor, the following operations are implemented:
  • the list of related parties is retrieved according to the seal number of the seal as a list of related parties of the contract participant;
  • the names of other contract participants except the contract participants are respectively matched with the list of related parties.
  • the matching is successful, the related transactions are identified from the transaction, and the recognition result is presented to the user.
  • the technical solution of the present application which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM as described above). , a disk, an optical disk, including a number of instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the methods described in the various embodiments of the present application.
  • a terminal device which may be a mobile phone, a computer, a server, or a network device, etc.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Engineering & Computer Science (AREA)
  • Marketing (AREA)
  • Economics (AREA)
  • Development Economics (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Technology Law (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

一种关联交易识别方法，电子装置及计算机可读存储介质，该方法包括：接收用户提交的用印申请，包括：申请调用的印章及合同参与方；分别将所述合同参与方的名称与所述印章对应的法人主体名称进行匹配；当存在合同参与方的名称与所述印章对应的法人主体名称完全匹配时，根据所述印章的印章编号调取关联方清单，作为所述合同参与方的关联方清单；及，将除所述合同参与方的其他合同参与方的名称分别与所述关联方清单进行匹配，当匹配成功时，从该笔交易中识别出关联交易，并将识别结果展示给用户。利用该方法，在进行交易的用印过程中，准确识别是否存在关联交易。

Description

关联交易识别方法、程序、装置及存储介质
本申请基于巴黎公约申明享有2018年3月19日递交的申请号为CN 2018102251411、名称为“关联交易识别方法、装置及存储介质”的中国专利申请的优先权，该中国专利申请的整体内容以参考的方式结合在本申请中。
技术领域
本申请涉及计算机技术领域，尤其涉及一种关联交易识别方法、程序、电子装置及计算机可读存储介质。
背景技术
随着我国市场经济的发展，部分企业集团的规模日益庞大、产业分布和产权结构也越来越复杂，其内部各公司间的关联交易业务越来越多、越来越频繁。例如：集团企业母、子公司之间或子公司之间的内部购销存货业务、内部固定资产购销业务、提供或接受劳务、担保、租赁、提供资金等。
现有的关联交易是通过企业集团内的母子公司下发，交易数据量很大，均需要通过工作人员在系统中人工识别是否为关联交易，且需要人工补录相关信息，给工作人员额外增加了大量工作，无法保证关联交易识别的准确性。另外，目前识别关联交易都是在交易完成后根据会计账目内容识别。因此，需要提供一种能快速、准确从大量的交易数据中识别出关联交易的方法。
发明内容
本申请提供一种关联交易识别方法、程序、电子装置及计算机可读存储介质，其主要目的在于在进行交易的用印过程中，准确识别是否存在关联交易。
为实现上述目的，本申请提供一种电子装置，该装置包括存储器、处理器，所述存储器上存储有可在所述处理器上运行的关联交易识别程序，该程序被所述处理器执行时实现如下步骤：
接收用户针对一笔交易提交的用印申请，该用印申请包括申请调用的一个或多个印章及合同参与方；
按照预设的第一匹配规则，分别将所述合同参与方的名称与所述一个或多个印章对应的法人主体名称进行匹配；
当存在合同参与方的名称与所述印章对应的法人主体名称完全匹配时，根据所述印章的印章编号调取关联方清单，作为所述合同参与方的关联方清单；及
将除所述合同参与方的其他合同参与方的名称分别与所述关联方清单进行匹配，当匹配成功时，从该笔交易中识别出关联交易，并将识别结果展示给用户。
此外，为实现上述目的，本申请还提供一种关联交易识别方法，该方法包括：
接收用户针对一笔交易提交的用印申请，该用印申请包括申请调用的一个或多个印章及合同参与方；
按照预设的第一匹配规则，分别将所述合同参与方的名称与所述一个或多个印章对应的法人主体名称进行匹配；
当存在合同参与方的名称与所述印章对应的法人主体名称完全匹配时，根据所述印章的印章编号调取关联方清单，作为所述合同参与方的关联方清单；及
将除所述合同参与方的其他合同参与方的名称分别与所述关联方清单进行匹配，当匹配成功时，从该笔交易中识别出关联交易，并将识别结果展示给用户。
此外，为实现上述目的，本申请还提供一种关联交易识别程序，该程序包括：
接收模块，用于接收用户针对一笔交易提交的用印申请，该用印申请包括申请调用的一个或多个印章及合同参与方；
匹配模块，用于按照预设的第一匹配规则，分别将所述合同参与方的名称与所述一个或多个印章对应的法人主体名称进行匹配；
调取模块，用于当存在合同参与方的名称与所述印章对应的法人主体名称完全匹配时，根据所述印章的印章编号调取关联方清单，作为所述合同参与方的关联方清单；及
识别模块，用于将除所述合同参与方的其他合同参与方的名称分别与所 述关联方清单进行匹配，当匹配成功时，从该笔交易中识别出关联交易，并将识别结果展示给用户。
此外，为实现上述目的，本申请还提供一种计算机可读存储介质，所述计算机可读存储介质上存储有关联交易识别程序，该程序被处理器执行时实现如上所述的关联交易识别方法的任意步骤。
相较于现有技术，本申请提出的关联交易识别方法、程序、电子装置及计算机可读存储介质，通过在针对某笔交易的用印过程中，准确识别该笔交易是否存在关联交易，无需根据会计账目识别关联交易，提高后续关联交易的处理效率。
图1为本申请电子装置较佳实施例的示意图；
图2为本发明关联交易识别程序的程序模块示意图；
图3为本申请关联交易识别方法较佳实施例的流程图。
本申请目的的实现、功能特点及优点将结合实施例，参照附图做进一步说明。
具体实施方式
应当理解，此处所描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。
本申请提供一种关联交易识别方法，该方法应用于一种电子装置1。参照图1所示，为本申请电子装置1较佳实施例的示意图。
在本实施例中，电子装置1可以是服务器、智能手机、平板电脑、便携计算机、桌上型计算机等具有数据处理功能的终端设备，所述服务器可以是机架式服务器、刀片式服务器、塔式服务器或机柜式服务器。
该电子装置1包括存储器11、处理器12，通信总线13，显示器14以及网络接口15。
其中，存储器11至少包括一种类型的可读存储介质，所述可读存储介质包括闪存、硬盘、多媒体卡、卡型存储器(例如，SD或DX存储器等)、磁性存储器、磁盘、光盘等。存储器11在一些实施例中可以是所述电子装置1 的内部存储单元，例如该电子装置1的硬盘。存储器11在另一些实施例中也可以是所述电子装置1的外部存储设备，例如该电子装置1上配备的插接式硬盘，智能存储卡(Smart Media Card,SMC)，安全数字(Secure Digital,SD)卡，闪存卡(Flash Card)等。进一步地，存储器11还可以既包括该电子装置1的内部存储单元也包括外部存储设备。存储器11不仅可以用于存储安装于该电子装置1的应用软件及各类数据，例如关联交易识别程序10、预设的第一匹配规则及预设的第二匹配规则等，还可以用于暂时地存储已经输出或者将要输出的数据。具体地，所述关联交易识别程序10架设于公司用印系统(图中未标识)及关联业务系统(图中未标识)之间，用于接收用户通过用印系统提交的某笔交易的用印申请，提取用印申请中的信息，在关联业务系统中从该笔交易中识别出关联交易；所述预设的第一匹配规则用于将用户录入的合同参与方名称与印章对应的法人主体名称进行精准匹配；所述预设的第二匹配规则用于将用户录入的合同参与方名称与印章对应的法人主体名称进行模糊匹配。
处理器12在一些实施例中可以是一中央处理器(Central Processing Unit,CPU)、控制器、微控制器、微处理器或其他数据处理芯片，用于运行存储器11中存储的程序代码或处理数据，例如关联交易识别程序10等。
通信总线13用于实现这些组件之间的连接通信。
显示器14可以是LED显示器、液晶显示器、触控式液晶显示器以及有机发光二极管(Organic Light-Emitting Diode，OLED)触摸器等。其中，显示器14也可以称为显示屏或显示单元，用于显示在电子装置1中处理的信息以及用于显示可视化的用户界面。
网络接口15可以包括标准的有线接口、无线接口(如WI-FI接口)，通常用于在该电子装置1与其他电子设备之间建立通信连接。在本实施例中，电子装置1通过网络接口15与客户端(图中未标识)之间建立通信连接，用户通过所述客户端访问用印系统，并通过用印系统提交用印申请。
图1仅示出了具有组件11-15的电子装置1，但是应理解的是，并不要求实施所有示出的组件，可以替代的实施更多或者更少的组件。
可选地，该电子装置1还可以包括用户接口，用户接口可以包括输入单元比如键盘(Keyboard)，可选的用户接口还可以包括标准的有线接口、无线 接口。
在图1所示的装置实施例中，存储器11中存储有关联交易识别程序10。处理器12执行存储器11中存储的关联交易识别程序10时实现如下步骤：
接收用户针对一笔交易提交的用印申请，该用印申请包括申请调用的一个或多个印章及合同参与方；
按照预设的第一匹配规则，分别将所述合同参与方的名称与所述一个或多个印章对应的法人主体名称进行匹配；
当存在合同参与方的名称与所述印章对应的法人主体名称完全匹配时，根据所述印章的印章编号调取关联方清单，作为所述合同参与方的关联方清单；及
将除所述合同参与方的其他合同参与方的名称分别与所述关联方清单进行匹配，当匹配成功时，从该笔交易中识别出关联交易，并将识别结果展示给用户。
所谓关联交易就是企业关联方之间的交易，常见的关联交易包括：购买或销售商品、购买其他资产(例如，设备或建筑物等)、提供或接受劳务、担保、提供资金、租赁、代理等。关联交易对于一个公司的存在及发展是不可或缺的，因此，公司对关联交易的处理必须慎重。然而关联交易处理过程中，关联交易的识别至关重要。接下来对关联交易的识别过程进行说明。
在本实施例中，所述用户指某公司员工，例如，公司法务人员，用户针对某笔交易，通过公司的用印系统录入用印申请的具体信息，包括：调用的一个或多个印章、该笔交易涉及到的合同名称、两个或两个以上合同参与方的名称、协议金额、合同数量等，并提交该用印申请。在接收到用户针对该笔交易提交的用印申请后，从用印申请中读取该用印申请调用的印章对应的法人主体名称及用户录入的合同参与方的名称。
在本实施例中，以该笔交易仅涉及一份合同，且该合同只有两个合同参与方(即，甲方参与方及乙方参与方)为例，首先，根据预设的第一匹配规则，判断用户录入的合同参与方是否能和与印章对应的法人主体名称精准匹配。作为一种实施方式，所述预设的第一匹配规则包括：当合同参与方的名称与印章对应的法人主体名称完全一致时，判断该合同参与方与该印章之间 可实现精准匹配。例如，若用户在录入合同参与方的名称时，录入的是该合同参与方对应的公司的标准名称，而用印申请调用了该公司的印章，因为印章对应的法人主体名称为公司标准名称，也就是说，当录入的合同参与方名称与印章对应的法人主体名称完全一致时，合同参与方与印章之间可实现精准匹配。
需要说明的是，用户录入的某一个合同参与方数量可以为一个，也可以为多个，且一个或多个该合同参与方可分别与用印申请中调用的不同印章精准匹配，那么，将一个或多个该合同参与方分别与能与之精准匹配的印章进行挂钩，并根据印章编号调取各印章对应的关联方清单，作为与该印章挂钩的合同参与方的关联方清单。然后将关联方清单分别与其他合同参与方进行匹配，若匹配成功，则说明该笔交易中存在关联交易。
例如，用户录入甲方参与方的名称为A、乙方参与方的名称为M，用印申请中调用的印章包括A，那么用印申请中调用的印章A可与甲方参与方A精准匹配，根据印章A的印章编号，从关联交易系统中调取相应的关联方清单，作为甲方参与方A的关联方清单，并与录入的乙方参与方M进行匹配，当A的关联方清单中包括乙方参与方M时，判断A与M存在关联关系，即该笔交易中存在关联交易A-M，并将该结果通过客户端的展示界面向用户展示。同理，若用户录入了两个甲方参与方A、B，乙方参与方的名称为M，且甲方参与方A、B分别与印章A、B精准匹配，分别调取A、B的关联方清单与乙方参与方M进行匹配，若A、B的关联方清单中均包括乙方参与方M时，该笔交易中存在关联交易A-M、B-M，并将该结果通过客户端的展示界面向用户展示。
需要说明的是，上述步骤需满足某一合同参与方可完全与印章精准匹配，那么，以甲方参与方A、B为例，需满足合同中甲方参与方A、B均能与用印申请中调用的印章匹配，才能从关联交易系统中调取相应的关联方清单，并进行关联交易识别。当甲方参与方A可与印章匹配，但甲方参与方B无法与印章匹配时，则需要进行进一步地匹配操作。
具体地，当所述两个或两个以上的合同参与方均不能完全与所述用印申请中调用的印章对应的法人主体名称匹配时，判断用印申请中调用的印章数量与合同参与方的总数量是否一致，存在两种情况：
一、印章数量与合同参与方的总数量一致的情况：假设用印申请中调用了三枚印章，合同甲方参与方录入A(标准名称)、B(非标准名称)，合同乙方参与方录入M(非标准名称或者标准名称)，印章数量(三枚)与合同参与方的总数量(两个合同甲方参与方，一个合同乙方参与方，共三个)一致，在用户录入过程中没有出错的前提下，可以默认为用户录入的合同参与方可分别与用印申请中调用的不同印章匹配，故可直接调取各印章相应的关联方清单，然后分别将其他印章对应的法人主体名称与该关联方清单进行精准匹配，并对匹配结果进行去重处理，得到从该笔交易中识别关联交易的识别结果。
二、用印申请中调用的印章数量与合同参与方总数量不一致的情况：假设用印申请中调用了两枚印章，合同甲方参与方录入A(标准名称)、B(非标准名称)，合同乙方参与方录入M(非标准名称或者标准名称)，当印章数量(两枚)与合同参与方的总数量(3个)不一致时，首先，获取部分能与印章精准匹配的合同参与方，例如，甲方参与方A，根据与甲方参与方A匹配的印章的印章编号，调取相应的关联方清单作为甲方参与方A的关联方清单，然后根据预设的第二匹配规则，将与其他合同参与方(例如，乙方参与方M)的名称进行模糊匹配，判断甲方参与方A与乙方参与方M之间是否存在关联关系，若匹配成功，说明A和M存在关联关系，也就是说该笔交易中存在关联交易A-M；然后，根据未与任一合同参与方匹配的印章的印章编号，调取相应的关联方清单，分别与所述用印申请中全部合同参与方进行模糊匹配。
需要说明的是，同属于合同的甲方参与方的A、B，即使两者之间存在关联交易，但在该笔交易中，A、B之间不存在关联交易，因此，在上述步骤得到匹配结果后，若匹配结果中包含同一合同参与方的两个公司，对该部分结果进行过滤处理，然后将经过过滤处理后的匹配结果作为识别结果。
具体地，预设的第二匹配规则：当所述印章对应的法人主体名称完全包含所述合同参与方的名称，或者，所述合同参与方的名称完全包含所述印章对应的法人主体名称，所述合同参与方与印章实现匹配。可以理解的是，用户在录入合同参与方的名称时，录入的是该合同参与方对应的公司的非标准名称，当录入的参与方名称与印章对应的法人主体名称不完全一致时，参与方与印章之间无法精准匹配。
需要说明的是，上述步骤需在关联方清单维护及时的前提下进行，否则，识别结果可能出现错误。可选地，若存在关联方清单维护不及时的情况，用户可根据实际情况判断该笔交易中是否存在关联交易，接收用户输入的判断结果，若与上述识别结果一致，保留已有的识别结果；若上述识别结果不一致，保留用户输入的判断结果，并提示用户已对识别结果进行调整。
上述实施例提出的电子装置1，通过在针对某笔交易的用印过程中，准确识别该笔交易是否存在关联交易，提高后续关联交易的处理效率。
可选地，在其他的实施例中，关联交易识别程序10还可以被分割为一个或者多个模块，一个或者多个模块被存储于存储器11中，并由一个或多个处理器(本实施例为处理器12)所执行，以完成本申请，本申请所称的模块是指能够完成特定功能的一系列计算机程序指令段。例如，参照图2所示，为本申请关联交易识别程序10的程序模块示意图，该实施例中，关联交易识别程序10可以被分割为接收模块110、匹配模块120、调取模块130及识别模块140，所述模块110-140所实现的功能或操作步骤如下：
接收模块110，用于接收用户针对一笔交易提交的用印申请，该用印申请包括申请调用的一个或多个印章及合同参与方；
匹配模块120，用于按照预设的第一匹配规则，分别将所述合同参与方的名称与所述一个或多个印章对应的法人主体名称进行匹配；
调取模块130，用于当存在合同参与方的名称与所述印章对应的法人主体名称完全匹配时，根据所述印章的印章编号调取关联方清单，作为所述合同参与方的关联方清单；及
识别模块140，用于将除所述合同参与方的其他合同参与方的名称分别与所述关联方清单进行匹配，当匹配成功时，从该笔交易中识别出关联交易，并将识别结果展示给用户。
所谓关联交易就是企业关联方之间的交易，常见的关联交易包括：购买或销售商品、购买其他资产(例如，设备或建筑物等)、提供或接受劳务、担保、提供资金、租赁、代理等。关联交易对于一个公司的存在及发展是不可或缺的，因此，公司对关联交易的处理必须慎重。然而关联交易处理过程中，关联交易的识别至关重要。接下来对关联交易的识别过程进行说明。
在本实施例中，所述用户指某公司员工，例如，公司法务人员，用户针对某笔交易，通过公司的用印系统录入用印申请的具体信息，包括：调用的一个或多个印章、该笔交易涉及到的合同名称、两个或两个以上合同参与方的名称、协议金额、合同数量等，并提交该用印申请。在接收到用户针对该笔交易提交的用印申请后，从用印申请中读取该用印申请调用的印章对应的法人主体名称及用户录入的合同参与方的名称。
在本实施例中，以该笔交易仅涉及一份合同，且该合同只有两个合同参与方(即，甲方参与方及乙方参与方)为例，首先，根据预设的第一匹配规则，判断用户录入的合同参与方是否能和与印章对应的法人主体名称精准匹配。作为一种实施方式，所述预设的第一匹配规则包括：当合同参与方的名称与印章对应的法人主体名称完全一致时，判断该合同参与方与该印章之间可实现精准匹配。例如，若用户在录入合同参与方的名称时，录入的是该合同参与方对应的公司的标准名称，而用印申请调用了该公司的印章，因为印章对应的法人主体名称为公司标准名称，也就是说，当录入的合同参与方名称与印章对应的法人主体名称完全一致时，合同参与方与印章之间可实现精准匹配。
需要说明的是，用户录入的某一个合同参与方数量可以为一个，也可以为多个，且一个或多个该合同参与方可分别与用印申请中调用的不同印章精准匹配，那么，将一个或多个该合同参与方分别与能与之精准匹配的印章进行挂钩，并根据印章编号调取各印章对应的关联方清单，作为与该印章挂钩的合同参与方的关联方清单。然后将关联方清单分别与其他合同参与方进行匹配，若匹配成功，则说明该笔交易中存在关联交易。
例如，用户录入甲方参与方的名称为A、乙方参与方的名称为M，用印申请中调用的印章包括A，那么用印申请中调用的印章A可与甲方参与方A精准匹配，根据印章A的印章编号，从关联交易系统中调取相应的关联方清单，作为甲方参与方A的关联方清单，并与录入的乙方参与方M进行匹配，当A的关联方清单中包括乙方参与方M时，判断A与M存在关联关系，即该笔交易中存在关联交易A-M，并将该结果通过客户端的展示界面向用户展示。同理，若用户录入了两个甲方参与方A、B，乙方参与方的名称为M，且甲方参与方A、B分别与印章A、B精准匹配，分别调取A、B的关联方清单 与乙方参与方M进行匹配，若A、B的关联方清单中均包括乙方参与方M时，该笔交易中存在关联交易A-M、B-M，并将该结果通过客户端的展示界面向用户展示。
需要说明的是，上述步骤需满足某一合同参与方可完全与印章精准匹配，那么，以甲方参与方A、B为例，需满足合同中甲方参与方A、B均能与用印申请中调用的印章匹配，才能从关联交易系统中调取相应的关联方清单，并进行关联交易识别。当甲方参与方A可与印章匹配，但甲方参与方B无法与印章匹配时，则需要进行进一步地匹配操作。
具体地，当所述两个或两个以上的合同参与方均不能完全与所述用印申请中调用的印章对应的法人主体名称匹配时，判断用印申请中调用的印章数量与合同参与方的总数量是否一致，存在两种情况：
一、印章数量与合同参与方的总数量一致的情况：假设用印申请中调用了三枚印章，合同甲方参与方录入A(标准名称)、B(非标准名称)，合同乙方参与方录入M(非标准名称或者标准名称)，印章数量(三枚)与合同参与方的总数量(两个合同甲方参与方，一个合同乙方参与方，共三个)一致，在用户录入过程中没有出错的前提下，可以默认为用户录入的合同参与方可分别与用印申请中调用的不同印章匹配，故可直接调取各印章相应的关联方清单，然后分别将其他印章对应的法人主体名称与该关联方清单进行精准匹配，并对匹配结果进行去重处理，得到从该笔交易中识别关联交易的识别结果。
二、用印申请中调用的印章数量与合同参与方总数量不一致的情况：假设用印申请中调用了两枚印章，合同甲方参与方录入A(标准名称)、B(非标准名称)，合同乙方参与方录入M(非标准名称或者标准名称)，当印章数量(两枚)与合同参与方的总数量(3个)不一致时，首先，获取部分能与印章精准匹配的合同参与方，例如，甲方参与方A，根据与甲方参与方A匹配的印章的印章编号，调取相应的关联方清单作为甲方参与方A的关联方清单，然后根据预设的第二匹配规则，将与其他合同参与方(例如，乙方参与方M)的名称进行模糊匹配，判断甲方参与方A与乙方参与方M之间是否存在关联关系，若匹配成功，说明A和M存在关联关系，也就是说该笔交易中存在关联交易A-M；然后，根据未与任一合同参与方匹配的印章的印章编号，调取 相应的关联方清单，分别与所述用印申请中全部合同参与方进行模糊匹配。
需要说明的是，同属于合同的甲方参与方的A、B，即使两者之间存在关联交易，但在该笔交易中，A、B之间不存在关联交易，因此，在上述步骤得到匹配结果后，若匹配结果中包含同一合同参与方的两个公司，对该部分结果进行过滤处理，然后将经过过滤处理后的匹配结果作为识别结果。
具体地，预设的第二匹配规则：当所述印章对应的法人主体名称完全包含所述合同参与方的名称，或者，所述合同参与方的名称完全包含所述印章对应的法人主体名称，所述合同参与方与印章实现匹配。可以理解的是，用户在录入合同参与方的名称时，录入的是该合同参与方对应的公司的非标准名称，当录入的参与方名称与印章对应的法人主体名称不完全一致时，参与方与印章之间无法精准匹配。
需要说明的是，上述步骤需在关联方清单维护及时的前提下进行，否则，识别结果可能出现错误。可选地，若存在关联方清单维护不及时的情况，用户可根据实际情况判断该笔交易中是否存在关联交易，接收用户输入的判断结果，若与上述识别结果一致，保留已有的识别结果；若上述识别结果不一致，保留用户输入的判断结果，并提示用户已对识别结果进行调整。
此外，本申请还提供一种关联交易识别方法。参照图3所示，为本申请关联交易识别方法较佳实施例的流程图。该方法可以由一个装置执行，该装置可以由软件和/或硬件实现。
在本实施例中，关联交易识别方法包括：步骤S1-S4。
步骤S1，接收用户针对一笔交易提交的用印申请，该用印申请包括申请调用的一个或多个印章及合同参与方；
步骤S2，按照预设的第一匹配规则，分别将所述合同参与方的名称与所述一个或多个印章对应的法人主体名称进行匹配；
步骤S3，当存在合同参与方的名称与所述印章对应的法人主体名称完全匹配时，根据所述印章的印章编号调取关联方清单，作为所述合同参与方的关联方清单；及
步骤S4，将除所述合同参与方的其他合同参与方的名称分别与所述关联方清单进行匹配，当匹配成功时，从该笔交易中识别出关联交易，并将识别 结果展示给用户。
所谓关联交易就是企业关联方之间的交易，常见的关联交易包括：购买或销售商品、购买其他资产(例如，设备或建筑物等)、提供或接受劳务、担保、提供资金、租赁、代理等。关联交易对于一个公司的存在及发展是不可或缺的，因此，公司对关联交易的处理必须慎重。然而关联交易处理过程中，关联交易的识别至关重要。接下来对关联交易的识别过程进行说明。
在本实施例中，所述用户指某公司员工，例如，公司法务人员，用户针对某笔交易，通过公司的用印系统录入用印申请的具体信息，包括：调用的一个或多个印章、该笔交易涉及到的合同名称、两个或两个以上合同参与方的名称、协议金额、合同数量等，并提交该用印申请。在接收到用户针对该笔交易提交的用印申请后，从用印申请中读取该用印申请调用的印章对应的法人主体名称及用户录入的合同参与方的名称。
在本实施例中，以该笔交易仅涉及一份合同，且该合同只有两个合同参与方(即，甲方参与方及乙方参与方)为例，首先，根据预设的第一匹配规则，判断用户录入的合同参与方是否能和与印章对应的法人主体名称精准匹配。作为一种实施方式，所述预设的第一匹配规则包括：当合同参与方的名称与印章对应的法人主体名称完全一致时，判断该合同参与方与该印章之间可实现精准匹配。例如，若用户在录入合同参与方的名称时，录入的是该合同参与方对应的公司的标准名称，而用印申请调用了该公司的印章，因为印章对应的法人主体名称为公司标准名称，也就是说，当录入的合同参与方名称与印章对应的法人主体名称完全一致时，合同参与方与印章之间可实现精准匹配。
需要说明的是，用户录入的某一个合同参与方数量可以为一个，也可以为多个，且一个或多个该合同参与方可分别与用印申请中调用的不同印章精准匹配，那么，将一个或多个该合同参与方分别与能与之精准匹配的印章进行挂钩，并根据印章编号调取各印章对应的关联方清单，作为与该印章挂钩的合同参与方的关联方清单。然后将关联方清单分别与其他合同参与方进行匹配，若匹配成功，则说明该笔交易中存在关联交易。
例如，用户录入甲方参与方的名称为A、乙方参与方的名称为M，用印申请中调用的印章包括A，那么用印申请中调用的印章A可与甲方参与方A 精准匹配，根据印章A的印章编号，从关联交易系统中调取相应的关联方清单，作为甲方参与方A的关联方清单，并与录入的乙方参与方M进行匹配，当A的关联方清单中包括乙方参与方M时，判断A与M存在关联关系，即该笔交易中存在关联交易A-M，并将该结果通过客户端的展示界面向用户展示。同理，若用户录入了两个甲方参与方A、B，乙方参与方的名称为M，且甲方参与方A、B分别与印章A、B精准匹配，分别调取A、B的关联方清单与乙方参与方M进行匹配，若A、B的关联方清单中均包括乙方参与方M时，该笔交易中存在关联交易A-M、B-M，并将该结果通过客户端的展示界面向用户展示。
需要说明的是，上述步骤需满足某一合同参与方可完全与印章精准匹配，那么，以甲方参与方A、B为例，需满足合同中甲方参与方A、B均能与用印申请中调用的印章匹配，才能从关联交易系统中调取相应的关联方清单，并进行关联交易识别。当甲方参与方A可与印章匹配，但甲方参与方B无法与印章匹配时，则需要进行进一步地匹配操作。
具体地，当所述两个或两个以上的合同参与方均不能完全与所述用印申请中调用的印章对应的法人主体名称匹配时，判断用印申请中调用的印章数量与合同参与方的总数量是否一致，存在两种情况：
一、印章数量与合同参与方的总数量一致的情况：假设用印申请中调用了三枚印章，合同甲方参与方录入A(标准名称)、B(非标准名称)，合同乙方参与方录入M(非标准名称或者标准名称)，印章数量(三枚)与合同参与方的总数量(两个合同甲方参与方，一个合同乙方参与方，共三个)一致，在用户录入过程中没有出错的前提下，可以默认为用户录入的合同参与方可分别与用印申请中调用的不同印章匹配，故可直接调取各印章相应的关联方清单，然后分别将其他印章对应的法人主体名称与该关联方清单进行精准匹配，并对匹配结果进行去重处理，得到从该笔交易中识别关联交易的识别结果。
二、用印申请中调用的印章数量与合同参与方总数量不一致的情况：假设用印申请中调用了两枚印章，合同甲方参与方录入A(标准名称)、B(非标准名称)，合同乙方参与方录入M(非标准名称或者标准名称)，当印章数量(两枚)与合同参与方的总数量(3个)不一致时，首先，获取部分能与印 章精准匹配的合同参与方，例如，甲方参与方A，根据与甲方参与方A匹配的印章的印章编号，调取相应的关联方清单作为甲方参与方A的关联方清单，然后根据预设的第二匹配规则，将与其他合同参与方(例如，乙方参与方M)的名称进行模糊匹配，判断甲方参与方A与乙方参与方M之间是否存在关联关系，若匹配成功，说明A和M存在关联关系，也就是说该笔交易中存在关联交易A-M；然后，根据未与任一合同参与方匹配的印章的印章编号，调取相应的关联方清单，分别与所述用印申请中全部合同参与方进行模糊匹配。
需要说明的是，同属于合同的甲方参与方的A、B，即使两者之间存在关联交易，但在该笔交易中，A、B之间不存在关联交易，因此，在上述步骤得到匹配结果后，若匹配结果中包含同一合同参与方的两个公司，对该部分结果进行过滤处理，然后将经过过滤处理后的匹配结果作为识别结果。
具体地，预设的第二匹配规则：当所述印章对应的法人主体名称完全包含所述合同参与方的名称，或者，所述合同参与方的名称完全包含所述印章对应的法人主体名称，所述合同参与方与印章实现匹配。可以理解的是，用户在录入合同参与方的名称时，录入的是该合同参与方对应的公司的非标准名称，当录入的参与方名称与印章对应的法人主体名称不完全一致时，参与方与印章之间无法精准匹配。
需要说明的是，上述步骤需在关联方清单维护及时的前提下进行，否则，识别结果可能出现错误。可选地，若存在关联方清单维护不及时的情况，用户可根据实际情况判断该笔交易中是否存在关联交易，接收用户输入的判断结果，若与上述识别结果一致，保留已有的识别结果；若上述识别结果不一致，保留用户输入的判断结果，并提示用户已对识别结果进行调整。
上述实施例提出的关联交易识别方法，通过在针对某笔交易的用印过程中，准确识别该笔交易是否存在关联交易，提高后续关联交易的处理效率。
此外，本申请实施例还提出一种计算机可读存储介质，所述计算机可读存储介质上存储有关联交易识别程序10，该程序被处理器执行时实现如下操作：
接收用户针对一笔交易提交的用印申请，该用印申请包括申请调用的一个或多个印章及合同参与方；
按照预设的第一匹配规则，分别将所述合同参与方的名称与所述一个或多个印章对应的法人主体名称进行匹配；
当存在合同参与方的名称与所述印章对应的法人主体名称完全匹配时，根据所述印章的印章编号调取关联方清单，作为所述合同参与方的关联方清单；及
将除所述合同参与方的其他合同参与方的名称分别与所述关联方清单进行匹配，当匹配成功时，从该笔交易中识别出关联交易，并将识别结果展示给用户。
本申请计算机可读存储介质具体实施方式与上述关联交易识别方法中各实施例基本相同，在此不作累述。
需要说明的是，上述本申请实施例序号仅仅为了描述，不代表实施例的优劣。并且本文中的术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、装置、物品或者方法不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、装置、物品或者方法所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、装置、物品或者方法中还存在另外的相同要素。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在如上所述的一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本申请各个实施例所述的方法。
以上仅为本申请的优选实施例，并非因此限制本申请的专利范围，凡是利用本申请说明书及附图内容所作的等效结构或等效流程变换，或直接或间接运用在其他相关的技术领域，均同理包括在本申请的专利保护范围内。

Claims (20)

  1. 一种关联交易识别方法，应用于电子装置，其特征在于，该方法包括：
    接收用户针对一笔交易提交的用印申请，该用印申请包括申请调用的一个或多个印章及合同参与方；
    按照预设的第一匹配规则，分别将所述合同参与方的名称与所述一个或多个印章对应的法人主体名称进行匹配；
    当存在合同参与方的名称与所述印章对应的法人主体名称完全匹配时，根据所述印章的印章编号调取关联方清单，作为所述合同参与方的关联方清单；及
    将除所述合同参与方的其他合同参与方的名称分别与所述关联方清单进行匹配，当匹配成功时，从该笔交易中识别出关联交易，并将识别结果展示给用户。
  2. 如权利要求1所述的关联交易识别方法，其特征在于，该方法还包括：
    当所述合同参与方的名称不能完全与所述一个或多个印章对应的法人主体名称匹配时，判断所述用印申请中调用的印章数量与合同参与方数量是否一致；及
    当所述用印申请中调用的印章数量与所述合同参与方数量一致时，根据印章编号调取各印章相应的关联方清单，分别将所述一个或多个印章对应的法人主体名称与所述关联方清单进行匹配，根据匹配结果判断该笔交易中是否存在关联交易。
  3. 如权利要求2所述的关联交易识别方法，其特征在于，该方法还包括：
    当所述用印申请中调用的印章数量与合同参与方数量不一致时，获取与所述印章对应的法人主体名称部分匹配的合同参与方的关联方清单；
    根据预设的第二匹配规则，将所述关联方清单与其他合同参与方的名称进行匹配；
    根据未与合同参与方匹配的印章编号，调取相应的关联方清单，分别与所述用印申请中全部合同参与方进行匹配；及
    根据匹配结果得到从该笔交易中识别关联交易的识别结果。
  4. 如权利要求3所述的关联交易识别方法，其特征在于，所述预设的第一匹配规则包括：
    当所述合同参与方的名称与所述印章对应的法人主体名称完全一致时， 所述合同参与方与所述印章实现精准匹配。
  5. 如权利要求3至4中任意一项所述的关联交易识别方法，其特征在于，所述预设的第二匹配规则包括：
    当所述印章对应的法人主体名称完全包含所述合同参与方的名称，或者，当所述合同参与方的名称完全包含所述印章对应的法人主体名称，所述合同参与方与所述印章实现模糊匹配。
  6. 一种电子装置，其特征在于，该装置包括：存储器、处理器，所述存储器上存储有可在所述处理器上运行的关联交易识别程序，该程序被所述处理器执行时实现如下步骤：
    接收用户针对一笔交易提交的用印申请，该用印申请包括申请调用的一个或多个印章及合同参与方；
    按照预设的第一匹配规则，分别将所述合同参与方的名称与所述一个或多个印章对应的法人主体名称进行匹配；
    当存在合同参与方的名称与所述印章对应的法人主体名称完全匹配时，根据所述印章的印章编号调取关联方清单，作为所述合同参与方的关联方清单；及
    将除所述合同参与方的其他合同参与方的名称分别与所述关联方清单进行匹配，当匹配成功时，从该笔交易中识别出关联交易，并将识别结果展示给用户。
  7. 如权利要求6所述的电子装置，其特征在于，该程序被所述处理器执行时，还实现如下步骤：
    当所述合同参与方的名称不能完全与所述一个或多个印章对应的法人主体名称匹配时，判断所述用印申请中调用的印章数量与合同参与方数量是否一致；及
    当所述用印申请中调用的印章数量与所述合同参与方数量一致时，根据印章编号调取各印章相应的关联方清单，分别将所述一个或多个印章对应的法人主体名称与所述关联方清单进行匹配，根据匹配结果判断该笔交易中是否存在关联交易。
  8. 如权利要求7所述的电子装置，其特征在于，该程序被所述处理器执行时，还实现如下步骤：
    当所述用印申请中调用的印章数量与合同参与方数量不一致时，获取部分能与印章精准匹配的合同参与方的关联方清单；
    根据预设的第二匹配规则，将所述关联方清单与其他合同参与方的名称进行匹配；
    根据未与合同参与方匹配的印章编号，调取相应的关联方清单，分别与所述用印申请中全部合同参与方进行匹配；及
    根据匹配结果得到从该笔交易中识别关联交易的识别结果。
  9. 如权利要求8所述的电子装置，其特征在于，所述预设的第一匹配规则包括：当所述合同参与方的名称与所述印章对应的法人主体名称完全一致时，所述合同参与方与所述印章实现精准匹配。
  10. 如权利要求8至9中任意一项所述的电子装置，其特征在于，所述预设的第二匹配规则包括：
    当所述印章对应的法人主体名称完全包含所述合同参与方的名称，或者，当所述合同参与方的名称完全包含所述印章对应的法人主体名称，所述合同参与方与所述印章实现模糊匹配。
  11. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质上存储有关联交易识别程序，该程序被所述处理器执行时实现如下步骤：
    接收用户针对一笔交易提交的用印申请，该用印申请包括申请调用的一个或多个印章及合同参与方；
    按照预设的第一匹配规则，分别将所述合同参与方的名称与所述一个或多个印章对应的法人主体名称进行匹配；
    当存在合同参与方的名称与所述印章对应的法人主体名称完全匹配时，根据所述印章的印章编号调取关联方清单，作为所述合同参与方的关联方清单；及
    将除所述合同参与方的其他合同参与方的名称分别与所述关联方清单进行匹配，当匹配成功时，从该笔交易中识别出关联交易，并将识别结果展示给用户。
  12. 如权利要求11所述的计算机可读存储介质，其特征在于，该程序被所述处理器执行时，还实现如下步骤：
    当所述合同参与方的名称不能完全与所述一个或多个印章对应的法人主 体名称匹配时，判断所述用印申请中调用的印章数量与合同参与方数量是否一致；及
    当所述用印申请中调用的印章数量与所述合同参与方数量一致时，根据印章编号调取各印章相应的关联方清单，分别将所述一个或多个印章对应的法人主体名称与所述关联方清单进行匹配，根据匹配结果判断该笔交易中是否存在关联交易。
  13. 如权利要求12所述的计算机可读存储介质，其特征在于，该程序被所述处理器执行时，还实现如下步骤：
    当所述用印申请中调用的印章数量与合同参与方数量不一致时，获取部分能与印章精准匹配的合同参与方的关联方清单；
    根据预设的第二匹配规则，将所述关联方清单与其他合同参与方的名称进行匹配；
    根据未与合同参与方匹配的印章编号，调取相应的关联方清单，分别与所述用印申请中全部合同参与方进行匹配；及
    根据匹配结果得到从该笔交易中识别关联交易的识别结果。
  14. 如权利要求13所述的计算机可读存储介质，其特征在于，所述预设的第一匹配规则包括：当所述合同参与方的名称与所述印章对应的法人主体名称完全一致时，所述合同参与方与所述印章实现精准匹配。
  15. 如权利要求13至14中任意一项所述的计算机可读存储介质，其特征在于，所述预设的第二匹配规则包括：
    当所述印章对应的法人主体名称完全包含所述合同参与方的名称，或者，当所述合同参与方的名称完全包含所述印章对应的法人主体名称，所述合同参与方与所述印章实现模糊匹配。
  16. 一种关联交易识别程序，其特征在于，该程序包括：
    接收模块，用于接收用户针对一笔交易提交的用印申请，该用印申请包括申请调用的一个或多个印章及合同参与方；
    匹配模块，用于按照预设的第一匹配规则，分别将所述合同参与方的名称与所述一个或多个印章对应的法人主体名称进行匹配；
    调取模块，用于当存在合同参与方的名称与所述印章对应的法人主体名称完全匹配时，根据所述印章的印章编号调取关联方清单，作为所述合同参 与方的关联方清单；及
    识别模块，用于将除所述合同参与方的其他合同参与方的名称分别与所述关联方清单进行匹配，当匹配成功时，从该笔交易中识别出关联交易，并将识别结果展示给用户。
  17. 如权利要求16所述的关联交易识别程序，其特征在于，所述识别模块还用于：
    当所述合同参与方的名称不能完全与所述一个或多个印章对应的法人主体名称匹配时，判断所述用印申请中调用的印章数量与合同参与方数量是否一致；及
    当所述用印申请中调用的印章数量与所述合同参与方数量一致时，根据印章编号调取各印章相应的关联方清单，分别将所述一个或多个印章对应的法人主体名称与所述关联方清单进行匹配，根据匹配结果判断该笔交易中是否存在关联交易。
  18. 如权利要求17所述的关联交易识别程序，其特征在于，所述识别模块还用于：
    当所述用印申请中调用的印章数量与合同参与方数量不一致时，获取部分能与印章精准匹配的合同参与方的关联方清单；
    根据预设的第二匹配规则，将所述关联方清单与其他合同参与方的名称进行匹配；
    根据未与合同参与方匹配的印章编号，调取相应的关联方清单，分别与所述用印申请中全部合同参与方进行匹配；及
    根据匹配结果得到从该笔交易中识别关联交易的识别结果。
  19. 如权利要求18所述的关联交易识别程序，其特征在于，所述预设的第一匹配规则包括：当所述合同参与方的名称与所述印章对应的法人主体名称完全一致时，所述合同参与方与所述印章实现精准匹配。
  20. 如权利要求18至19中任意一项所述的关联交易识别程序，其特征在于，所述预设的第二匹配规则包括：
    当所述印章对应的法人主体名称完全包含所述合同参与方的名称，或者，当所述合同参与方的名称完全包含所述印章对应的法人主体名称，所述合同参与方与所述印章实现模糊匹配。
PCT/CN2018/102087 2018-03-19 2018-08-24 关联交易识别方法、程序、装置及存储介质 WO2019179025A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810225141.1 2018-03-19
CN201810225141.1A CN108470305B (zh) 2018-03-19 2018-03-19 关联交易识别方法、装置及存储介质

Publications (1)

Publication Number Publication Date
WO2019179025A1 true WO2019179025A1 (zh) 2019-09-26

Family

ID=63265486

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/102087 WO2019179025A1 (zh) 2018-03-19 2018-08-24 关联交易识别方法、程序、装置及存储介质

Country Status (2)

Country Link
CN (1) CN108470305B (zh)
WO (1) WO2019179025A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109784922B (zh) * 2019-01-02 2023-09-22 深圳壹账通智能科技有限公司 电子合同签署方法、装置、计算机设备和存储介质
CN112258324B (zh) * 2020-11-06 2023-11-10 泰康保险集团股份有限公司 一种合同审批方法、合同审批服务器、设备及介质
CN112597181B (zh) * 2020-11-25 2022-11-04 贝壳技术有限公司 一种连环单查找方法及装置
CN113436017B (zh) * 2021-07-07 2022-06-21 支付宝(杭州)信息技术有限公司 交易处理方法、装置及设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103761573A (zh) * 2013-12-23 2014-04-30 远光软件股份有限公司 实现内部交易业务进行对账关联的方法及装置
CN104616389A (zh) * 2015-02-12 2015-05-13 西安印艺苑实业有限公司 印章识别方法和装置
CN104732133A (zh) * 2015-03-31 2015-06-24 努比亚技术有限公司 电子合同签署方法和系统
TWI517072B (zh) * 2014-09-25 2016-01-11 天逸財金科技服務股份有限公司 交易單據比對系統及方法

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1482560A (zh) * 2002-09-11 2004-03-17 辉 刘 网络印章认证系统
CN1517911A (zh) * 2003-01-17 2004-08-04 辉 刘 网络印章查询验证方法
CN104915789B (zh) * 2015-06-25 2019-06-07 中国工商银行股份有限公司 安全用印方法、装置及其系统
CN107784074B (zh) * 2017-09-25 2020-09-01 平安科技（深圳）有限公司 关联交易的识别方法、装置和、计算机设备和存储介质

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103761573A (zh) * 2013-12-23 2014-04-30 远光软件股份有限公司 实现内部交易业务进行对账关联的方法及装置
TWI517072B (zh) * 2014-09-25 2016-01-11 天逸財金科技服務股份有限公司 交易單據比對系統及方法
CN104616389A (zh) * 2015-02-12 2015-05-13 西安印艺苑实业有限公司 印章识别方法和装置
CN104732133A (zh) * 2015-03-31 2015-06-24 努比亚技术有限公司 电子合同签署方法和系统

Also Published As

Publication number Publication date
CN108470305A (zh) 2018-08-31
CN108470305B (zh) 2021-08-24

Similar Documents

Publication Publication Date Title
WO2019179025A1 (zh) 关联交易识别方法、程序、装置及存储介质
US10546351B2 (en) System and method for automatic generation of reports based on electronic documents
US11782892B2 (en) Method and system for migrating content between enterprise content management systems
US9213893B2 (en) Extracting data from semi-structured electronic documents
US11792257B2 (en) Form engine
US9129276B1 (en) Inventory management
US11157850B2 (en) Automated information retrieval based on supplier risk
WO2019062191A1 (zh) 电子装置、提取数据表的数据的方法、系统及存储介质
US11580096B2 (en) System for uploading information into a metadata repository
WO2018184548A1 (zh) 保单的试报价方法、装置、终端设备及介质
US20170169292A1 (en) System and method for automatically verifying requests based on electronic documents
CN110851298A (zh) 异常分析及处理方法、电子装置及存储介质
WO2021017458A1 (zh) 图像识别的辅助处理方法、装置及系统
CN107741954B (zh) 电子单证的申报录入方法、服务器及存储介质
US10430760B2 (en) Enhancing communications based on physical trade documents
US20140244346A1 (en) Real estate transaction management platform
CN109918385A (zh) 三方对账方法、电子装置及可读存储介质
US20230281654A1 (en) Systems and methods for autonomous management of manufacturer coupons
US10410168B2 (en) Preventing restricted trades using physical documents
US9864789B2 (en) Method and system for implementing an on-demand data warehouse
US20170147978A1 (en) Executing shipments based on physical trade documents
CN113961672A (zh) 信息标注方法、装置、电子设备和存储介质
CN114693035A (zh) 企业知识产权管理系统时限任务的生成方法、系统及装置
US10319025B2 (en) Executing terms of physical trade documents
CN111833028B (zh) 项目管理方法、装置、电子设备和计算机可读存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18910723

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 12/01/2021)

122 Ep: pct application non-entry in european phase

Ref document number: 18910723

Country of ref document: EP

Kind code of ref document: A1