Electronic receipt matching method and device based on interconnection and intercommunication

Abstract

The invention discloses an electronic receipt matching method and device based on interconnection and interworking, and the method comprises the steps: carrying out the field information extraction of an electronic receipt query request reply message, and obtaining an interconnection and interworking account transaction detail table of an electronic receipt query request; initiating an electronic receipt issuing application, and after the electronic receipt is obtained, filling the stored electronic receipt index into an OFD receipt file index field of the interconnection and interworking account transaction detail table; according to a preset matching rule corresponding to the channel type of the bank transaction detail structured table, matching the bank transaction detail structured table with an interconnection and interworking account transaction detail table; and when the matching is successful, associating the electronic receipt index with the bank transaction detail structured table. And the electronic receipt file and the transaction structured data are rapidly and accurately matched correspondingly.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to an electronic receipt matching method and device based on interconnection and interoperability. Background Art

[0002] Each treasury system will obtain transaction structured data from the bank through online banking, bank-enterprise direct connection or RPA robots. With the promotion of the interconnection system, each treasury system will also choose to obtain OFD electronic receipts through the interconnection system.

[0003] Currently, the treasury system obtains structured data through the various channels mentioned above for accounting and generating financial vouchers, making it difficult to match the OFD electronic receipt files obtained through the interconnection system with the structured data. However, if the downloaded electronic receipt files cannot be matched with the structured data obtained through other channels, then these electronic receipt files will become unusable. Summary of the Invention

[0004] The embodiments of the present application provide an interconnection-based electronic receipt matching method and device, which are used to solve the problem that electronic receipt files cannot be accurately and efficiently matched with structured data obtained from other channels.

[0005] The embodiments of this application adopt the following technical solutions:

[0006] On the one hand, an embodiment of the present application provides an electronic receipt matching method based on interconnection and interoperability, the method including: extracting field information from an electronic receipt query request reply message to obtain an interconnection and interoperability account transaction details table of the electronic receipt query request; initiating an electronic receipt issuance application, and after obtaining the electronic receipt, filling the stored electronic receipt index into the OFD receipt file index field of the interconnection and interoperability account transaction details table; matching the bank transaction details structured table with the interconnection and interoperability account transaction details table according to the preset matching rules corresponding to the channel type of the bank transaction details structured table; when the match is successful, associating the electronic receipt index with the bank transaction details structured table.

[0007] In one example, the information extraction of the electronic receipt query request reply message to obtain the interoperability account transaction details table of the electronic receipt query request specifically includes: mapping the receipt field of the electronic receipt query request reply message according to the preset field direct correspondence relationship to obtain the first table field of the interoperability account transaction details table; converting the receipt field of the electronic receipt query request reply message according to the preset field extraction relationship to obtain the second table field of the interoperability account transaction details table; constructing the table field of the interoperability account transaction details table according to the OFD receipt file index field, the first table field and the second table field; filling the receipt field data associated with the first table field into the first table field of the interoperability account transaction details table; performing rule conversion on the receipt field data associated with the second table field, and filling the converted data into the second table field of the interoperability account transaction details table.

[0008] In one example, the first table fields include: account number, currency, voucher number, voucher date, transaction date, transaction serial number, and transaction amount; the second table fields include: counterparty account number, payment and receipt mark, detailed date type, and unique identification code; the payment and receipt mark includes receipt and payment, and the detailed date type includes current day and history.

[0009] In one example, the rule conversion of the receipt field data associated with the second table field specifically includes: performing payment and collection analysis on the receipt payment account data and the receipt receipt account data to obtain the counterparty account data and payment and collection flag data; judging whether the receipt transaction date is the same as the current query date; if they are the same, determining the detailed date type data as the current day; if they are different, determining the detailed date type data as history; and determining the unique identification code data based on the receipt number data, receipt currency data, receipt voucher number data, and receipt voucher date data.

[0010] In one example, the bank transaction details structured table is matched with the interoperable account transaction details table according to the preset matching rules of the channel type, specifically including: when the channel type is bank-enterprise direct connection data, adding an interoperable serial number field to the bank transaction details structured table; extracting the bank-enterprise serial number of the bank transaction details structured table; the bank-enterprise serial number is a unique transaction identifier; performing a mapping relationship conversion on the bank-enterprise serial number to obtain the interoperable serial number of the bank transaction details structured table; judging whether the interoperable serial number is consistent with the content of a designated field of the interoperable account transaction details table; the designated field is a unique transaction identifier; when they are consistent, determining that the bank transaction details structured table and the interoperable account transaction details table are successfully matched; when they are inconsistent, performing data comparison between the bank transaction details structured table and the interoperable account transaction details table according to a preset number of fields; and determining whether the bank transaction details structured table and the interoperable account transaction details table are successfully matched based on the data comparison result.

[0011] In one example, the method of determining whether the bank transaction details structured table and the interoperable account transaction details table are successfully matched based on the data comparison result specifically includes: when the data of multiple fields are successfully compared, judging whether the number of transaction records involved in the comparison of the bank transaction details structured table is consistent with the number of transaction records involved in the comparison of the interoperable account transaction details table; if they are consistent, determining that the bank transaction details structured table and the interoperable account transaction details table are successfully matched; if they are inconsistent, adding spare fields to a preset number of fields to obtain an updated preset number of fields; based on the updated preset number of fields, re-comparing the bank transaction details structured table and the interoperable account transaction details table; and determining whether the bank transaction details structured table and the interoperable account transaction details table are successfully matched based on the re-comparison result.

[0012] In one example, the bank transaction details structured table is matched with the interoperable account transaction details table according to the preset matching rules of the channel type, specifically including: when the channel type is online banking data or data crawled by RPA, the bank transaction details structured table and the interoperable account transaction details table are compared according to a preset number of fields; based on the data comparison results, it is determined whether the bank transaction details structured table and the interoperable account transaction details table are successfully matched.

[0013] In one example, the method further includes: when the matching is unsuccessful, parsing and identifying the electronic receipt to obtain electronic receipt data; matching the electronic receipt data with the bank transaction details structured table; when the matching is successful, associating the electronic receipt index with the bank transaction details structured table.

[0014] In one example, before matching the bank transaction details structured table with the interoperability account transaction details table according to the preset matching rules corresponding to the channel type of the bank transaction details structured table, the method also includes: determining that the number of days between the transaction date of the electronic receipt and the current matching time is less than a preset matching quantity threshold.

[0015] On the other hand, an embodiment of the present application provides an interconnection-based electronic receipt matching device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute any one of the above-mentioned interconnection-based electronic receipt matching methods.

[0016] At least one of the above technical solutions adopted in the embodiments of the present application can achieve the following beneficial effects:

[0017] By extracting field information from the reply message of the electronic receipt query request, the interoperability account transaction details table of the electronic receipt query request is obtained, and the return content of the interoperability electronic receipt query is used as the interoperability transaction details. The query results in the electronic receipt download process are regarded as the transaction details of an independent channel. The uniqueness of the business information of the data obtained between different channels is used to complete the automatic matching of the electronic receipt file and the transaction details structured table, and the matching of the interoperability transaction details with the transaction details from different sources is realized (for example, the interoperability serial number field attribute is added to the bank-enterprise direct connection transaction details, which actually realizes the comparison of the corresponding fields of the interoperability transaction details with the bank serial number of the bank-enterprise direct connection transaction details).

[0018] In summary, a faster and more accurate matching of electronic receipt files with transaction structured data is achieved. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the technical solution of the present application, some embodiments of the present application will be described in detail below with reference to the accompanying drawings, in which:

[0020] Figure 1 A flowchart of an interconnection-based electronic receipt matching method provided in an embodiment of the present application;

[0021] Figure 2 A schematic diagram of the structure of an interconnected electronic receipt matching device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0022] To make the objectives, technical solutions, and advantages of this application more clear, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the embodiments described are only part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0023] Some embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0024] Figure 1 This is a flow chart of an interconnected electronic receipt matching method provided in an embodiment of the present application. Certain input parameters or intermediate results in the process allow for manual intervention and adjustment to help improve accuracy.

[0025] The analysis method involved in the embodiments of the present application can be implemented by a terminal device or a server, and the present application does not impose any special restrictions on this. For ease of understanding and description, the following embodiments are described in detail using a server as an example.

[0026] It should be noted that the server can be a single device or a system composed of multiple devices, that is, a distributed server, and this application does not make any specific restrictions on this.

[0027] It should be noted that according to the interoperability system external system docking specifications, OFD electronic receipt files can be downloaded by following the steps below:

[0028] 1. Complete the contract confirmation with the bank where the OFD electronic receipt file is downloaded

[0029] 2. The recipient of the OFD electronic receipt file can query the list of contracted bank accounts

[0030] 3. Initiate an electronic receipt query request

[0031] 4. Initiate an issuance request based on the electronic receipt query request result

[0032] 5. Check the information of the issued electronic receipt.

[0033] It should be noted that this application uses the return data from initiating an electronic receipt query request as another channel for obtaining transaction details. One of the key features of this application is that the return content of the interoperable electronic receipt query is used as the interoperable transaction details. The data returned by this channel is then compared with the data returned by other channels to complete the matching of OFD electronic receipt files with structured data. This application assumes that the current electronic receipt matching system already has the ability to connect to the interoperable system and download electronic receipts from the interoperable system. On this basis, the method described in this application is applied to complete the matching with the structured data returned by each channel.

[0034] Figure 1 The process in includes the following steps:

[0035] S101: extracting field information from the reply message of the electronic receipt query request to obtain the interconnection account transaction details table of the electronic receipt query request.

[0036] In some embodiments of the present application, the table fields of the interoperability account transaction details table are pre-set, and the table fields can be established based on the core fields of the electronic receipt query request reply message. For example, as shown in Table 1.

[0037] Table 1

[0038]

[0039]

[0040] For example, through the interface with the interconnection system "Electronic Receipt Query Request Message<T2003.01> " and "Electronic Receipt Query Request Response Message<T2003.02> "Interaction, the OFD electronic receipt interaction data queried from the bank will be established into the interconnection account transaction details table for storage, which will become the interconnection account transaction details data.

[0041] Among them, the interconnection interface<T2003.02> The response message can be processed slightly to form the transaction details list of the interconnected account.

[0042] For example, the payment account and payment account in the message returned by the interconnection system are compared with the account of the party concerned to identify the account number and payment mark of the transaction counterparty.

[0043] If the transaction date is the same as the query date, the detail date type is T. If the transaction date is different from the query date, the detail type is set to H.

[0044] It should be noted that you can also create a daily detailed table and a historical detailed table to store these two parts of data separately. Usually, banks also divide detailed data into these two categories, and banks will make some necessary modifications or generate new detailed data when transferring historical data on the same day (mainly for the bank's transaction date cut operation). Type-based storage or table-based storage is mainly more convenient for subsequent use of the interconnected account transaction detailed table data and for reconciliation with the detailed structured data returned from other channels.

[0045] Use account number + currency + voucher date + voucher number as the data ID card to uniquely identify a transaction and use it as the primary key of the database table.

[0046] It's important to note that a bank transaction serial number is a unique identification code generated by the banking system for each transaction. It's used to record and track the details of a specific transaction. Therefore, both the bank transaction serial number and the unique identification code can actually uniquely correspond to a single transaction.

[0047] In addition, the transaction time is stored in the transaction date field, and other fields can also be processed accordingly.

[0048] It should be noted that the purpose of the above conversion is to make the electronic receipt data returned by the interconnection more like transaction details.

[0049] Based on this, the process of constructing the interoperability account transaction details table for the electronic receipt query request is as follows:

[0050] According to the preset field direct correspondence, the receipt fields of the electronic receipt query request reply message are mapped to obtain the first table field of the interconnection account transaction details table.

[0051] Based on the preset field extraction relationship, the receipt fields of the electronic receipt query request reply message are converted to obtain the second table field of the interconnection account transaction details table. For example, the above process of identifying the transaction counterparty account number and payment mark.

[0052] Based on the OFD receipt file index field, the first table field, and the second table field, the table fields of the interconnection account transaction details table are constructed.

[0053] Fill the receipt field data associated with the first table field into the first table field of the interoperability account transaction details table.

[0054] Perform rule conversion on the receipt field data associated with the second table field, and fill the converted data into the second table field of the interconnection account transaction details table.

[0055] It should be noted that the fields of the first table include: account number, currency, voucher number, voucher date, transaction date, transaction serial number, and transaction amount.

[0056] The fields in the second table include: counterparty account number, payment and receipt mark, detailed date type, and unique identification code; the payment and receipt mark includes receipt and payment, and the detailed date type includes current day and history.

[0057] It should be noted that at this time, the OFD receipt file index field content in the interconnection account transaction details table is empty.

[0058] The process of performing rule conversion on the receipt field data associated with the second table field can be as follows:

[0059] Perform payment and receipt analysis on the receipt payment account data and receipt payment account data to obtain the counterparty account data and payment and receipt mark data.

[0060] In addition, determine whether the transaction date of the receipt is the same as the current query date.

[0061] When they are the same, the detailed date type data is determined to be the current day; when they are different, the detailed date type data is determined to be historical.

[0062] Determine the unique identification code data based on the receipt number data, receipt currency data, receipt voucher number data and receipt voucher date data.

[0063] S102: Initiate an application for issuing an electronic receipt. After obtaining the electronic receipt, fill the stored electronic receipt index into the OFD receipt file index field of the interconnection account transaction details table.

[0064] In some embodiments of the present application, the bank sends an "electronic receipt request message" based on the information returned by the bank in the transaction details.<T1001.01> " and "Electronic Receipt Issuance Request Response Message<T1001.02> "Initiate an electronic receipt application and obtain the binary content of the OFD file (Base64 string carrier). The file content can be stored in an archive or imaging system, and the index of the accessed file can be stored in the "OFD Receipt File Index" column for subsequent matching to structured data.

[0065] S103: Matching the bank transaction detail structured table with the interconnection account transaction detail table according to a preset matching rule corresponding to the channel type of the bank transaction detail structured table.

[0066] In some embodiments of the present application, the source of the real bank transaction detail structured data may be the details downloaded from online banking, the details returned by the bank-enterprise direct connection, or the data crawled by RPA on the web page. The interconnected transaction details are matched with the transaction details from different sources (for example, compared with the bank serial number of the bank-enterprise direct connection transaction details). Among them, adding the interconnected serial number field attribute to the detail structured data returned by the bank-enterprise direct connection is one of the important features of the present application. The corresponding matching methods of these data are introduced below.

[0067] It's important to note that the details returned by the bank-enterprise direct link are typically the primary source of structured data for most current treasury systems. For this type of data, banks return unique identifiers, which often have a certain relationship or are identical to a field returned by the interoperability system. Therefore, users can identify the interoperability-specific fields that represent the same transaction unique identifier as the bank-enterprise direct link, thereby identifying the relationship between the two data.

[0068] For example, the bank-enterprise serial number returned by the bank and the transaction serial number in the interconnection account transaction details table represent the same content.

[0069] Furthermore, an additional attribute is added to the details returned by the bank-enterprise direct connection. The attribute is called the interconnection serial number. According to the relationship between the above two data, the transaction unique identifier is converted, and the conversion result is filled in the interconnection serial number field, so that the interconnection serial number field can be matched with the interconnection specified field.

[0070] Based on this, when the channel type is bank-enterprise direct connection data, a new intercommunication serial number field is added to the bank transaction details structured table.

[0071] Extract the bank-enterprise serial number from the structured table of bank transaction details. The bank-enterprise serial number is the unique identifier of the transaction.

[0072] The mapping relationship between bank and enterprise serial numbers is converted to obtain the interoperable serial numbers of the bank transaction details structured table.

[0073] Determine whether the interoperability serial number is consistent with the content of a designated field in the interoperability account transaction details table. The designated field is the transaction unique identifier.

[0074] When they are consistent, it is determined that the bank transaction details structured table and the interconnection account transaction details table are matched successfully.

[0075] In the event of inconsistencies, the bank transaction details structured table is compared with the interoperability account transaction details table based on a preset number of fields. For example, the preset number of fields include the bank's account number, the other party's account number, the transaction amount, and the debit / credit direction.

[0076] Based on the data comparison results, determine whether the bank transaction details structured table and the interconnection account transaction details table match successfully.

[0077] The process of determining whether the bank transaction details structured table and the interconnection account transaction details table are successfully matched is as follows:

[0078] When the data in multiple fields are successfully compared, determine whether the number of transaction records involved in the comparison in the bank transaction details structured table is consistent with the number of transaction records involved in the comparison in the interconnection account transaction details table.

[0079] When they are consistent, it is determined that the bank transaction details structured table and the interconnection account transaction details table are matched successfully.

[0080] When there is inconsistency, spare fields are added to the preset number of fields to obtain updated preset number of fields.

[0081] Based on the updated preset number of fields, the bank transaction details structured table and the interconnection account transaction details table are re-compared.

[0082] Based on the results of the re-data comparison, determine whether the bank transaction details structured table and the interconnection account transaction details table are successfully matched.

[0083] It should be noted that in the matching process of re-data comparison, when the data of multiple fields are successfully compared, it is determined whether the number of transaction records participating in the comparison of the bank transaction details structured table is consistent with the number of transaction records participating in the comparison of the interconnection account transaction details table.

[0084] When they are consistent, it is determined that the bank transaction details structured table and the interconnection account transaction details table are matched successfully.

[0085] In the event of inconsistency, it is determined that the bank transaction details structured table and the interconnection account transaction details table are unsuccessfully matched.

[0086] In some embodiments of the present application, when the channel type is online banking data or data crawled by RPA, the bank transaction details structured table and the interconnection account transaction details table are compared based on a preset number of fields.

[0087] Based on the data comparison results, determine whether the bank transaction details structured table and the interconnection account transaction details table match successfully.

[0088] It should be noted that for the process of determining whether the matching is successful, please refer to the above matching process.

[0089] It should be noted that since neither RPA nor online banking data has a unique identification code, automatic matching rules can be developed in the system. For example, the account number, counterparty account number, transaction amount, and debit / credit direction in the RPA or online banking data can be compared. If the four elements are the same and the number of comparisons is consistent (the number is consistent, meaning that the interconnection returns X items and the RPA or online banking also returns X items), then the match is considered successful. For inconsistent numbers, a date matching condition can be added, and a match using the five-element matching method is also considered successful if the number is consistent.

[0090] For example, for bank-enterprise direct connection data, a scheduled task can be used to match the data with the same "interconnection serial number" in the transaction details structure table and the "transaction serial number" in the interconnection account transaction details table. In case of inconsistency, the account number of the party, the other party's account number, the transaction amount, and the debit and credit direction are used for comparison. If the above four elements are the same and the comparison quantity is consistent, the match is determined to be successful; for inconsistent quantities, the matching can be completed by adding the aforementioned five-element business information matching method.

[0091] It should be noted that for online banking detailed data and RPA crawled data that can return unique identifiers, an "interconnection serial number" field can also be added to the detailed data. When importing data into the system, it can be initialized based on the identified relationship. At this time, the processing method applied to the data returned by "bank-enterprise direct connection" can be applied to online banking detailed data or RPA crawled data, so that the overall program processing adopts a unified processing flow, which is convenient for overall implementation.

[0092] S104: When the matching is successful, the electronic receipt index is associated with the bank transaction detail structured table.

[0093] In some embodiments of the present application, for data that cannot be matched using the above solutions, a better processing solution is to parse the OFD file and compare the XBRL data in the OFD file with the structured data to improve the matching accuracy. Since the data in XBRL is usually more of the bank's internal accounting information, this method requires the structured data to have more data characteristics to be applicable, otherwise it cannot be applied.

[0094] Based on this, when the matching is unsuccessful, the electronic receipt is parsed and identified to obtain the electronic receipt data.

[0095] Match the electronic receipt data with the structured table of bank transaction details.

[0096] When the match is successful, the electronic receipt index is associated with the transaction detail structured table.

[0097] If the matching is unsuccessful, it will be manually identified and matched again.

[0098] It should be noted that when matching electronic receipt data with the bank transaction details structured table, the process is as follows:

[0099] Based on multiple set fields, the electronic receipt data is compared with the transaction details table of the interconnection account.

[0100] When the data in multiple fields are successfully compared, determine whether the number of transaction records involved in the comparison of the electronic receipt data is consistent with the number of transaction records involved in the comparison of the interconnection account transaction details table.

[0101] When they are consistent, it is determined that the electronic receipt data is successfully matched with the interconnection account transaction details table.

[0102] In the event of inconsistency, it is determined that the electronic receipt data and the interconnection account transaction details table are unsuccessful in matching.

[0103] In some embodiments of the present application, a day limit and a matching number limit may also be set for unmatched electronic receipts.

[0104] Because banks vary in the timeframe for generating OFD electronic receipt files, with some supporting generation on T day and others only on T+1, the scheduled task responsible for matching receipts needs to support recurring execution. To avoid long-term matching failures, consider increasing the number of matches in the detail data table and adding a system-level matching days parameter. The matching days parameter controls the data range within which the scheduled task matches. Based on this parameter setting, the scheduled task only matches unmatched data within the specified number of days from the current execution.

[0105] For data that has exceeded the parameter range, the number of matches for the detail entry is set to greater than 0. The scheduled task scans the data when this field is greater than 0, providing a matching execution opportunity for data that exceeds the matching days. After the matching operation, the number of matches is reduced by one until it returns to zero after several subsequent matching processes and no longer processed.

[0106] Based on this, before matching the bank transaction details structured table with the interconnection account transaction details table according to the preset matching rules corresponding to the channel type of the bank transaction details structured table, it is determined that the number of days between the transaction date of the electronic receipt and the current matching time is less than the preset matching quantity threshold.

[0107] It should be noted that although the embodiments of this application are based on Figure 1 Steps S101 to S104 are described in sequence, but this does not mean that steps S101 to S104 must be performed in a strict order. Figure 1The order shown in FIG1 is to introduce and explain step S101 to step S104 in order to facilitate those skilled in the art to understand the technical solution of the embodiment of the present application. In other words, in the embodiment of the present application, the order between step S101 to step S104 can be appropriately adjusted according to actual needs.

[0108] pass Figure 1 This method treats the query results during the electronic receipt download process as the transaction details of an independent channel, and uses the uniqueness of business information obtained from different channels to automatically match the electronic receipt file with the transaction detail structured table, quickly and accurately matching the electronic receipt file with the transaction structured data.

[0109] By converting the electronic receipt query results returned by the interconnection and interoperability into an interconnection and interoperability account transaction details table, in addition to completing the above matching with the structured bank transaction data from different sources, these data can also be used for the visualization requirements of the treasury system construction, mainly using these data for comparison to complete reconciliation and consistency verification of business data.

[0110] Based on this, information integration and accuracy are improved: field information is extracted from the reply message of the electronic receipt query request to generate the interconnected account transaction details table. This operation can systematically collect and organize information related to account transactions, forming a structured data table with the field information originally scattered in the message. At the same time, after obtaining the electronic receipt, the electronic receipt index is populated into the specific fields of the details table, ensuring the accurate association between transaction information and the corresponding receipt index, further improving the accuracy and integrity of the data and facilitating the subsequent management and query of transactions and receipts.

[0111] Efficient data matching and association: The bank's transaction details structured table is matched with the interconnected account transaction details table according to pre-set matching rules. Upon a successful match, the electronic receipt index is associated with the transaction details structured table, effectively integrating different data sources (bank transaction details and interconnected account transaction details). This data matching and association mechanism ensures that transaction information and electronic receipt information correspond to each other, improving data processing efficiency and facilitating comprehensive auditing, supervision, and analysis of transactions by banks or related institutions. For example, the electronic receipt corresponding to a transaction can be quickly located, or related transaction details can be traced back through the receipt index.

[0112] Optimizing and Automating Business Processes: This technical solution automates a series of operations, including electronic receipt application, information extraction, filling, matching, and association. This reduces manual intervention and the risk of human error, while improving the efficiency and quality of business processing. The automated process further standardizes and streamlines electronic receipt management and transaction detail management, helping to improve the smoothness and reliability of overall business processes and providing strong support for the operations of banks and other financial institutions.

[0113] Based on the same idea, some embodiments of the present application also provide devices and non-volatile computer storage media corresponding to the above methods.

[0114] Figure 2 A schematic diagram of the structure of an interconnected electronic receipt matching device provided in an embodiment of the present application includes:

[0115] at least one processor; and,

[0116] a memory communicatively connected to the at least one processor; wherein,

[0117] The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute any one of the above-mentioned electronic receipt matching methods based on interconnection and interoperability.

[0118] Some embodiments of the present application provide a non-volatile computer storage medium for interconnection-based electronic receipt matching, which stores computer-executable instructions. The computer-executable instructions can execute any of the above-mentioned methods for interconnection-based electronic receipt matching.

[0119] The various embodiments in this application are described in a progressive manner. Similar portions between the various embodiments can be referred to in conjunction with each other. Each embodiment focuses on the differences between the other embodiments. In particular, the device and medium embodiments are generally similar to the method embodiments, so their descriptions are relatively simple. For relevant portions, refer to the descriptions of the method embodiments.

[0120] The devices and media provided in the embodiments of the present application correspond one-to-one to the methods. Therefore, the devices and media also have similar beneficial technical effects to their corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the devices and media will not be repeated here.

[0121] It will be understood by those skilled in the art that embodiments of the present invention may be provided as methods, systems, or computer program products. Thus, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Furthermore, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0122] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowcharts and / or block diagrams, as well as combinations of processes and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowcharts and / or block diagrams. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0123] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0124] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0125] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0126] Memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0127] Computer-readable media includes permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. The information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media (transitory media), such as modulated data signals and carrier waves.

[0128] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.

[0129] The foregoing is merely an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various modifications and variations. Any modifications, equivalent replacements, improvements, etc. made within the technical principles of the present application should fall within the scope of protection of the present application.

Claims

1. An electronic receipt matching method based on interconnection and intercommunication, characterized in that: The method comprises: Extract field information from the reply message of the electronic receipt query request to obtain the interoperability account transaction details table of the electronic receipt query request; Initiate an application for electronic receipt issuance. After obtaining the electronic receipt, fill the stored electronic receipt index into the OFD receipt file index field in the interoperability account transaction details table; Matching the bank transaction details structured table with the interconnection account transaction details table according to a preset matching rule corresponding to the channel type of the bank transaction details structured table; When the match is successful, the electronic receipt index is associated with the bank transaction detail structured table.

2. The method according to claim 1, characterized in that The information extraction from the reply message of the electronic receipt query request is performed to obtain the interconnection account transaction details table of the electronic receipt query request, specifically including: Mapping the receipt fields of the electronic receipt query request reply message according to the preset field direct correspondence relationship to obtain the first table field of the interconnection account transaction details table; According to the preset field extraction relationship, the receipt fields of the electronic receipt query request reply message are converted to obtain the second table fields of the interconnection account transaction details table; Construct the table fields of the interoperability account transaction details table based on the OFD receipt file index field, the first table field, and the second table field; Fill the receipt field data associated with the first table field into the first table field of the interoperability account transaction details table; Perform rule conversion on the receipt field data associated with the second table field, and fill the converted data into the second table field of the interconnection account transaction details table.

3. The method according to claim 2, characterized in that The fields of the first table include: account number, currency, voucher number, voucher date, transaction date, transaction serial number, and transaction amount; The fields of the second table include: transaction counterparty account number, payment and receipt mark, detailed date type, and unique identification code; the payment and receipt mark includes receipt and payment, and the detailed date type includes current day and history.

4. The method according to claim 3, characterized in that The rule conversion of the receipt field data associated with the second table field specifically includes: Perform payment and receipt analysis on the receipt payment account data and receipt payment account data to obtain the counterparty account data and payment and receipt mark data; Determine whether the transaction date of the receipt is the same as the current query date; If they are the same, the detailed date type data is determined to be the current day; if they are different, the detailed date type data is determined to be historical; Determine the unique identification code data based on the receipt number data, receipt currency data, receipt voucher number data and receipt voucher date data.

5. The method according to claim 1, characterized in that Matching the bank transaction details structured table with the interconnection account transaction details table according to the preset matching rule of the channel type specifically includes: When the channel type is bank-enterprise direct connection data, a new intercommunication serial number field is added to the bank transaction detail structured table; Extracting the bank-enterprise serial number from the bank transaction details structured table; the bank-enterprise serial number is a unique identifier for the transaction; Performing mapping conversion on the bank-enterprise serial number to obtain the intercommunication serial number of the bank transaction detail structured table; Determining whether the interoperability serial number is consistent with the content of a designated field in the interoperability account transaction details table; the designated field is a unique transaction identifier; If they are consistent, determining that the bank transaction details structured table and the interconnection account transaction details table are matched successfully; In case of inconsistency, the bank transaction details structured table is compared with the interconnection account transaction details table based on a preset number of fields; Based on the data comparison result, it is determined whether the bank transaction details structured table and the interconnection account transaction details table are successfully matched.

6. The method according to claim 5, characterized in that Determining whether the bank transaction details structured table and the interconnection account transaction details table are successfully matched based on the data comparison result specifically includes: When the data in multiple fields are successfully compared, determine whether the number of transaction records involved in the comparison in the bank transaction details structured table is consistent with the number of transaction records involved in the comparison in the interoperability account transaction details table; If they are consistent, it is determined that the bank transaction details structured table and the interconnection account transaction details table are successfully matched; When there is inconsistency, spare fields are added to the preset number of fields to obtain updated preset number of fields; Re-comparing the bank transaction details structured table with the interoperability account transaction details table based on the updated preset number of fields; Based on the re-data comparison result, it is determined whether the bank transaction details structured table and the interconnection account transaction details table are successfully matched.

7. The method according to claim 1, characterized in that Matching the bank transaction details structured table with the interconnection account transaction details table according to the preset matching rule of the channel type specifically includes: When the channel type is online banking data or data crawled by RPA, the bank transaction details structured table is compared with the interconnection account transaction details table based on a preset number of fields; Based on the data comparison result, it is determined whether the bank transaction details structured table and the interconnection account transaction details table are successfully matched.

8. The method according to claim 1, characterized in that The method further comprises: When the matching is unsuccessful, the electronic receipt is parsed and identified to obtain the electronic receipt data; Matching the electronic receipt data with the bank transaction details structured table; When the match is successful, the electronic receipt index is associated with the bank transaction detail structured table.

9. The method according to claim 1, characterized in that Before matching the bank transaction detail structured table with the interconnection account transaction detail table according to the preset matching rule corresponding to the channel type of the bank transaction detail structured table, the method further includes: Determine whether the number of days between the transaction date of the electronic receipt and the current matching time is less than a preset matching quantity threshold.

10. An electronic receipt matching device based on interconnection, characterized in that: include: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the electronic receipt matching method based on interconnection and interoperability as described in any one of claims 1 to 9 above.

Images