CN111415263A - Data matching method and device - Google Patents
Data matching method and device Download PDFInfo
- Publication number
- CN111415263A CN111415263A CN202010266126.9A CN202010266126A CN111415263A CN 111415263 A CN111415263 A CN 111415263A CN 202010266126 A CN202010266126 A CN 202010266126A CN 111415263 A CN111415263 A CN 111415263A
- Authority
- CN
- China
- Prior art keywords
- matching
- data
- data matching
- service type
- request
- Prior art date
- Legal status (The legal status 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 status listed.)
- Pending
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/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
Abstract
The invention discloses a data matching method and device, and relates to the technical field of computers. One embodiment of the method comprises: receiving a data matching request aiming at any secondary resource sent by a client, wherein the data matching request carries: the identification of the secondary resource, the data category for which the match is made, and actual data provided by the second subject; determining the matched service type according to the received data matching request, wherein the service type comprises: pre-value derivative matching, advance matching or cross-cycle matching; judging whether the information carried in the data matching request meets the detection condition determined for the service type in advance; and when the judgment result is yes, executing data matching operation, and feeding back response information representing successful matching to the client after the execution is finished. The implementation mode can provide various data matching service types such as pre-income value derivative value matching, advance matching, cross-cycle matching and the like, thereby meeting complex and various actual service scenes.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a data matching method and apparatus.
Background
Currently, after resources such as bonds, funds, etc. are transferred between entities, a resource transferor needs to provide data related to the resource, such as value attribute values (e.g., principal) and value derivative values (e.g., interest) to a resource holder according to a pre-agreed return period, which data needs to be matched with planning data for the corresponding return period. In the prior art, the matching operation can only be executed according to the fixed matching date and the plan data of the return period, the matching of the pre-income value derivative value, the matching in advance or the matching across periods cannot be executed, and the executed matching operation cannot be cancelled or modified.
In the process of implementing the invention, the inventor finds that the prior art has at least the following problems:
in the prior art, the matching of the pre-income value derivative value, the matching in advance or the matching across periods cannot be executed, so that the special service requirements of complex scenes are difficult to adapt; the failure to cancel or modify the matched operation is not conducive to processing the error information in time, resulting in the risk of inconsistency between the accounting and the actual situation of some resources.
Disclosure of Invention
In view of this, embodiments of the present invention provide a data matching method and apparatus, which can provide multiple data matching service types, such as pre-harvest value derivative matching, advance matching, cross-cycle matching, and the like, so as to meet complex and diverse actual service scenarios.
To achieve the above object, according to one aspect of the present invention, a data matching method is provided.
The data matching method is used for matching actual data provided by the second main body according to a preset return period with predetermined plan data after the ownership of the secondary resource is transferred from the second main body to the first main body; the method is applied to a server side where a first main body is located, and the data comprise value attribute values and value derivative values of secondary resources; the method comprises the following steps: receiving a data matching request aiming at any secondary resource sent by a client, wherein the data matching request carries: the identification of the secondary resource, the data category for which the match is made, and actual data provided by the second subject; determining the matched service type according to the received data matching request, wherein the service type comprises: pre-value derivative matching, advance matching or cross-cycle matching; judging whether the information carried in the data matching request meets the detection condition determined for the service type in advance; and when the judgment result is yes, executing data matching operation, and feeding back response information representing successful matching to the client after the execution is finished.
Optionally, determining the service type of the current matching according to the received data matching request includes: and when the data type carried in the data matching request is judged to be the value derivative value and the actual data carried in the data matching request is larger than the plan data of the current return period, determining the matched service type as the matching of the pre-receiving value derivative value.
Optionally, the method further comprises: under the condition that the service type is matched with the pre-value derivative value: after the data matching operation is executed, the difference value between the actual data carried in the data matching request and the plan data of the current return cycle is determined as the pre-receiving actual data of the next return cycle.
Optionally, determining the service type of the current matching according to the received data matching request includes: and when the sending time of the data matching request is judged to be earlier than the plan matching time of the current return cycle, determining the matched service type as advanced matching.
Optionally, determining the service type of the current matching according to the received data matching request includes: and when judging that a history return period without data matching operation exists before the current return period, determining the matched service type as cross-period matching.
Optionally, the matching of the pre-value derivative value to the corresponding detection condition includes: the secondary resource belongs to a preset first resource category; the sending time of the data matching request is equal to the plan matching time of the current return cycle; and there is no history return period before the current return period in which no data matching operation is performed.
Optionally, matching the corresponding detection condition in advance includes: the secondary resource belongs to a preset second resource category; the actual data provided by the second subject is equal to the planned data of the current return cycle; and there is no history return period before the current return period in which no data matching operation is performed.
Optionally, matching the corresponding detection condition across cycles includes: the sending time of the data matching request is equal to the plan matching time of the current return cycle; and the actual data provided by the second subject is equal to the planned data for the current return cycle.
Optionally, the detection condition corresponding to each service type further includes: the secondary resource is not currently in any of the resource handling flows.
Optionally, the detection condition corresponding to each service type further includes: the plan data for the current return cycle is greater than zero.
Optionally, the method further comprises: after the data matching operation is executed, distributing the plan data of the current return cycle to a plurality of primary resources associated with the secondary resources according to the resource configuration proportion.
Optionally, the method further comprises: receiving a revocation matching request sent by a client; the revocation matching request aims at any return period of any secondary resource, and the return period carries out data matching operation at historical time; and when the secondary resource is judged to meet the preset withdrawal condition, recovering the plan data distributed to the primary resource associated with the secondary resource so as to restore the return period to a state of not executing the data matching operation.
Optionally, the revocation condition comprises: the secondary resources are associated with the same primary resources at the current moment and the historical moment, and the primary resources have the same resource configuration proportion at the current moment and the historical moment.
To achieve the above object, according to another aspect of the present invention, there is provided a data matching apparatus.
The data matching device is used for matching actual data provided by the second main body according to a preset return period with predetermined plan data after the ownership of the secondary resource is transferred from the second main body to the first main body; the device is arranged at a server side where a first main body is arranged, and the data comprise value attribute values and value derivative values of the secondary resources; the apparatus may comprise: a request receiving unit, configured to receive a data matching request for any secondary resource, where the data matching request carries: the identification of the secondary resource, the data category for which the match is made, and actual data provided by the second subject; a service type determining unit, configured to determine a service type matched this time according to the received data matching request, where the service type includes: pre-value derivative matching, advance matching or cross-cycle matching; a logic judgment unit, configured to judge whether information carried in the data matching request meets a detection condition predetermined for the service type; and when the judgment result is yes, executing data matching operation, and feeding back response information representing successful matching to the client after the execution is finished.
To achieve the above object, according to still another aspect of the present invention, there is provided an electronic apparatus.
An electronic device of the present invention includes: one or more processors; the storage device is used for storing one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors realize the data matching method provided by the invention.
To achieve the above object, according to still another aspect of the present invention, there is provided a computer-readable storage medium.
A computer-readable storage medium of the present invention has stored thereon a computer program which, when executed by a processor, implements the data matching method provided by the present invention.
According to the technical scheme of the invention, one embodiment of the invention has the following advantages or beneficial effects: after receiving a data matching request sent by a client, the server determines the matched service type based on the data matching request, judges whether to execute data matching operation according to a detection condition determined for the service type in advance, and further feeds back response information to the client. Through the steps and the predetermined judgment logic in each service type detection condition, the accurate judgment and the high-efficiency execution of various service types such as the matching of the pre-income value derivative value, the early matching, the cross-period matching and the like can be realized, and various specific service requirements of complex scenes are fully met. Meanwhile, the embodiment of the invention also realizes the cancellation function aiming at the matched operation, and after the server receives the cancellation matching request sent by the client, if the resource is judged to accord with the preset cancellation condition, the corresponding information can be restored to the state of not executing the data matching operation, thereby realizing the timely processing of the error operation and effectively avoiding the risk of inconsistent accounts.
Further effects of the above-mentioned non-conventional alternatives will be described below in connection with the embodiments.
Drawings
The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:
FIG. 1 is a schematic diagram of the main steps of a data matching method according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of the logic for determining matching of derived pre-value values according to the first embodiment of the present invention;
FIG. 3 is a logic diagram illustrating the determination of early match according to the first embodiment of the present invention;
FIG. 4 is a schematic diagram of the cross-cycle matching determination logic in the first embodiment of the present invention;
FIG. 5 is a diagram illustrating the steps performed to undo the matching in the first embodiment of the present invention;
FIG. 6 is a schematic diagram of the components of a data matching apparatus in an embodiment of the present invention;
FIG. 7 is an exemplary system architecture diagram in which embodiments of the present invention may be employed;
fig. 8 is a schematic structural diagram of an electronic device for implementing the data matching method in the embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which various details of embodiments of the invention are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
It is to be understood that the terms "first," "second," and the like as used herein are used herein to describe various objects, but these objects are not limited by the above terms. The above terms are used only to distinguish one object from another. For example, without departing from the scope of the present invention, the first body may be referred to as the second body, and the second body may also be referred to as the first body, both bodies being, but not the same. Similarly, a primary resource may be referred to as a secondary resource, and a secondary resource may be referred to as a primary resource, with both the primary and secondary resources being resources, but not the same resource, without departing from the scope of the invention. It should be noted that the embodiments of the present invention and the technical features of the embodiments may be combined with each other without conflict.
Fig. 1 is a schematic diagram of main steps of a data matching method according to an embodiment of the present invention.
As shown in fig. 1, the data matching method according to the embodiment of the present invention may be specifically executed according to the following steps:
step S101: and receiving a data matching request aiming at any secondary resource sent by the client.
In the embodiment of the present invention, after the ownership of the secondary resource is transferred from the second agent to the first agent, the second agent generally needs to provide actual data to the first agent according to a preset return cycle, and the actual data needs to be matched with the predetermined plan data. The first subject may be a subject holding the resource, such as a financial institution, and the second subject may be a distribution subject or an assignment subject of the resource as a counterparty of the first subject. The secondary resource may be an asset such as a bond, fund, etc., transferred between the first and second subjects, and the primary resource, which will be described below, refers to a financial product such as a financial product transferred between the sponsor and the first subject. The actual data and the plan data may each include a value attribute value (e.g., principal) and a value derivative value (e.g., interest) of the secondary resource, which may be in two different data categories. In practical application, after receiving the actual data provided by the second main body, a service person of the first main body can select a value attribute value or a value derivative value at the client to initiate matching of the actual data and the plan data to the server where the first main body is located, and the server determines whether to execute data matching operation by judging whether to meet a preset condition.
In this step, the service person operates at the client to send a data matching request to the server, where the data matching request may carry an identifier of the secondary resource, a data category targeted by the matching, and actual data provided by the second main body. In a specific application, the data matching request may further carry information such as an identifier of a current return cycle (for example, a serial number of the current return cycle), a plan matching time of the current return cycle, plan data of the current return cycle, an identifier of a second main body that transfers the secondary resource, and a request sending time, where the identifier of the secondary resource may be a name of the secondary resource or a resource code, the plan matching time and the request sending time are time points corresponding to the same time unit, for example, when the time unit is day, both the plan matching time and the request sending time are a certain date.
Step S102: and determining the matched service type according to the received data matching request.
In this step, the service types may include: pre-value derivative matching, advance matching, and cross-cycle matching. The pre-collection value derived value matching refers to receiving actual data (the data category is a value derived value) larger than plan data as a pre-collection value derived value of a next return period, the pre-matching refers to matching before the plan matching time of the current return period, and the cross-period matching refers to matching performed in the current return period before a historical return period without data matching operation exists. In the prior art, matching can only be performed according to the plan matching time and the plan data of the current return cycle, and the matching processes of the three service types cannot be executed, so that complex and various service scenes are difficult to meet.
In some embodiments, the service end may determine the traffic type by the following policy: when the server side judges that the data type carried in the data matching request is a value derivative value and the actual data carried in the data matching request is larger than the plan data of the current return period, determining the matched service type as pre-income value derivative value matching; when the server side judges that the sending time of the data matching request is earlier than the plan matching time of the current return period, the service type matched at this time is determined as advanced matching; and when the server side judges that a historical return period without data matching operation exists before the current return period, determining the matched service type as cross-period matching.
Step S103: judging whether the information carried in the data matching request meets the detection condition determined for the service type in advance; and when the judgment result is yes, executing data matching operation, and feeding back response information representing successful matching to the client after the execution is finished.
In specific application, corresponding detection conditions can be formulated for each service type according to requirements. For example, the following detection conditions may be established for the pre-value derivative value matching (the following detection conditions generally need to be met at the same time):
the secondary resource belongs to a preset first resource category;
the sending time of the data matching request is equal to the plan matching time of the current return period (the condition limits that the matching of the derived values of the pre-income value cannot be performed in advance at the same time);
there is no historical return cycle before the current return cycle where no data matching operation is performed (this condition limits the pre-harvest value derivative matches not being able to be a cross-cycle match at the same time);
the secondary resource is not in any resource disposal flow (the resource disposal flow can be resource procurement, resource maintenance, resource transfer, resource selling, resource redemption, etc.);
the plan data for the current return cycle is greater than zero.
The following detection conditions may be established for the advance matching (the following detection conditions generally need to be met simultaneously):
the secondary resource belongs to a preset second resource category;
the actual data provided by the second subject is equal to the plan data for the current return cycle (the conditional constraint advance match cannot be matched for the pre-paid value derivative at the same time);
there is no historical return cycle before the current return cycle where no data matching operation is performed (this condition limits the pre-harvest value derivative matches not being able to be a cross-cycle match at the same time);
the secondary resource is not currently in any resource handling process;
the plan data for the current return cycle is greater than zero.
The following detection conditions may be formulated for cross-cycle matching (the following detection conditions generally need to be met simultaneously):
the sending time of the data matching request is equal to the plan matching time of the current return cycle (the condition limits that the cross-cycle matching cannot be simultaneously the advance matching);
the actual data provided by the second subject is equal to the plan data for the current return cycle (this condition limits that cross-cycle matches cannot be matched for the pre-paid value derivative at the same time);
the secondary resource is not currently in any resource handling process;
the plan data for the current return cycle is greater than zero.
When the server performs logic judgment according to a plurality of detection conditions of any service type, the execution sequence of each detection condition can be flexibly adjusted according to needs, which is not limited by the invention. And if the information carried in the data matching request conforms to the detection condition of the corresponding service type, the server performs data matching operation, namely matching the actual data with the plan data and triggering accounting while matching. When the service type is the match of the pre-income value derivative value, after the server performs the data matching operation, the difference between the actual data carried in the data matching request and the plan data of the current return period can be determined as the pre-income actual data of the next return period. And then, the server side can distribute the plan data of the current return period to a plurality of primary resources associated with the secondary resources according to the resource configuration proportion, and returns response information to the client side to represent that the data matching operation is completed, thereby finishing the data matching process.
In the prior art, the matched operation cannot be cancelled or modified, so that error information cannot be processed in time, and partial resources have the risk of inconsistent accounts. Specifically, the invention realizes the revocation of the matched operation according to the following steps. And the server receives a revocation matching request sent by the client, wherein the revocation matching request aims at any return period of any secondary resource, and the return period carries out data matching operation at historical time. And when judging that the secondary resource meets the preset withdrawal condition, the server recovers the plan data distributed to the primary resource associated with the secondary resource so as to restore the return period to a state without executing the data matching operation. As a preferred scheme, the revocation condition may include: the secondary resources are associated with the same primary resources at the current moment and the historical moment, and the primary resources have the same resource allocation proportion at the current moment and the historical moment.
The technical solution of the present invention will be described below by a first embodiment in an application scenario, and for convenience of description, various concepts and objects in the solution will be described by using specific examples in the application scenario, and it should be understood that this does not set any limit to the coverage of the concepts and objects. The first embodiment is applied to an asset management system, the first main body is a financial institution (hereinafter referred to as a institution), the second main body is a transaction opponent (hereinafter referred to as a customer) of the institution, the first-level resource is financial products (hereinafter referred to as products) such as financial products transferred from the institution to a sponsor, the second-level resource is assets such as bonds and funds transferred from the customer to the institution, the actual data is the actual income amount, the plan data is the receivable amount, the value attribute value is the principal, the value derivative value is interest, the matching is checking (the principal of checking is the project logic corresponding relation between a certain accounting statement and another accounting statement and inside the accounting statement, the plan matching time is the receivable date after checking and confirming the amount to be received in different return periods by a service end of the institution in the asset management system and the actual repayment amount of the customer), the resource disposition comprises asset procurement (i.e. further buying the asset), asset maintenance (e.g. adjusting asset interest rate), asset resale (i.e. changing the product associated with the asset), asset selling and asset redemption, and the resource allocation proportion is the position proportion.
In this embodiment, the assets are first entered into the server-side audit list through asset declaration, asset allocation (associating resources with products and determining the proportion of taken positions), and fund allocation. And then, the customer repays according to each return period, the service personnel enters a service end check interface to check specific assets after receiving the repayment of the customer, namely, the corresponding assets are determined at the check interface, check is performed on principal money or interest, real income amount, check ending difference and the like, then a corresponding button is clicked to send a data matching request to the service end, the service end judges information carried in the data matching request according to preset conditions so as to determine whether to check, if checking is performed, accounting is triggered at the same time, and after checking is completed, the corresponding amount is distributed to products related to the assets according to a warehouse holding proportion.
In the prior art, audit aiming at each asset must be carried out according to the current return period, and once audit is successful, subsequent revocation or modification is not allowed. Due to the complexity and diversity of the asset management service, the following situations exist in the actual service scenario: returning interest or principal in the current return period by part of clients aiming at the condition that interest or principal in a certain historical return period is not paid for the moment; when partial customers pay, the partial customers do not pay in advance according to an appointed time plan; when partial customers pay, the customers do not pay more interest according to the amount of the interest due in the current return period; the service personnel make mistakes in the checking process and cannot revoke the mistakes. The prior art cannot support special scenes, so that the audit records of partial assets have potential risks of inconsistent accounts.
Based on the above consideration, the invention provides the audit checking method and the audit cancellation method which meet various specific service scenes. Specifically, the records of the historical return period are allowed to be unrepensed first, and the corresponding records of the current return period are returned first, so that cross-period check is realized; pre-interest check of a first resource category is supported; support advanced audit of a second resource category; the method can cancel the error check operation. Through the arrangement, the asset management system can meet complex and various actual scenes, can quickly respond to special service requirements, and improves user experience.
Fig. 2 is a schematic diagram of the logic for determining matching of the pre-paid value derivative according to the first embodiment of the present invention, as shown in fig. 2, in step S201, the server determines whether the real amount of money in the data matching request is greater than the amount of money to be collected and does not check the end difference: if yes, returning prompt information to the client, such as 'whether the current mode is a pre-paid interest check mode and is continued' and if the business personnel clicks 'yes', executing the next step; if the server judges that the actual amount of money in the data matching request is not more than the amount of money to be received or the service personnel clicks 'no', the flow of checking the pre-paid interest is ended. Step S202, the server determines whether the asset belongs to a first resource category (the first resource category may be defined according to actual needs, and includes, for example, outsourcing investment, asset management plan, and public fund): if yes, executing the next step; otherwise, ending the flow. Step S203, the server determines whether the asset is not in the resource handling process: if yes, executing the next step; otherwise, the flow is ended and prompt information is returned to the client to remind the service personnel to execute the resource disposal flow first and then check. Step S204, the server judges whether the request sending time (namely the current business day) is equal to the receivable date: if yes, executing the next step; otherwise, ending the flow. Step S205, the server determines whether there is no history returning period without performing audit: if yes, executing the next step; otherwise, ending the flow. Step S206, the server judges whether the amount of money to be received is larger than zero: if not, ending the flow; if yes, it indicates that the information carried in the data matching request meets all the detection conditions, at this time, the data checking operation in step S207 may be performed, and step S208 is performed to determine the difference between the actual amount of money and the amount of money to be received as the interest of the next return period. And step S209, distributing the interest received in the current return period to each product associated with the asset according to the position holding ratio.
It should be noted that, under the condition of pre-interest collection, if the interest amount of the subsequent schedule increases due to asset procurement, the interest amount of the subsequent schedule decreases due to asset redemption or asset selling, and the interest amount of the subsequent schedule is uncertain change due to asset maintenance in the later period, the server needs to sum up all the pre-interest collections, allocate the pre-interest collections to each return period after the asset disposal, and further recalculate the interest due to each return period. Under the condition of pre-interest collection, if the assets are maintained, the interest-counting finishing day of the corresponding schedule is limited not to be earlier than the current business day; if the assets are transferred, the pre-paid interest amount needs to be determined as the sum of the checked future real-paid amounts.
Fig. 3 is a logic diagram illustrating the determination of early matching according to the first embodiment of the present invention, as shown in fig. 3, in step S301, the server determines whether the sending time of the data matching request is earlier than the receivable date: if yes, returning prompt information to the client, such as 'the current mode is an advance check mode and whether the mode is continued', and if the service personnel clicks 'yes', executing the next step; if the server judges that the request sending time is not earlier than the receivable date or the service personnel clicks 'no', the flow of checking in advance is ended. Step S302, the server determines whether the asset belongs to a second resource category (the second resource category may be defined according to actual needs, for example, including non-standardized bonds, equity assets, and industry fund): if yes, executing the next step; otherwise, ending the flow. Step S303, the server judges whether the assets are not in the resource disposal flow: if yes, executing the next step; otherwise, the flow is ended and prompt information is returned to the client to remind the service personnel to execute the resource disposal flow first and then check. Step S304, the server judges whether the real amount in the data matching request is equal to the receivable amount: if yes, executing the next step; otherwise, ending the flow. Step S305, the server determines whether there is no history return period without performing audit: if yes, executing the next step; otherwise, ending the flow. Step S306, the server judges whether the amount of money to be received is larger than zero: if not, ending the flow; if yes, the information carried in the data matching request is in accordance with all detection conditions, at this time, the data auditing operation in the step S307 can be executed, and the step S308 is executed to distribute the principal or interest amount received in the current return period to each product associated with the asset according to the position holding proportion.
If some asset is checked in advance, when the asset is maintained in the later period, the server needs to ensure that the interest end date of the subsequent schedule is not earlier than the last recorded interest end date; when the capital is transferred, the amount of receivable charge for accounting and keeping accounts by the server side is the smaller value between the amount of receivable charge and the amount of tail difference deducted from the amount of real charge.
Fig. 4 is a schematic diagram of a cross-cycle matching determination logic in the first embodiment of the present invention, as shown in fig. 4, in step S401, the server determines whether there is a history return cycle in which checking is not performed: if yes, returning prompt information to the client, such as 'whether the current mode is cross-period checking and whether the mode is continued', and if the service personnel clicks 'yes', executing the next step; if the server judges that no history return period which is not checked exists or the service personnel clicks 'no', the cross-period checking process is ended. Step S402, the server judges whether the assets are not in the resource disposal flow: if yes, executing the next step; otherwise, the flow is ended and prompt information is returned to the client to remind the service personnel to execute the resource disposal flow first and then check. Step S403, the server determines whether the real amount in the data matching request is equal to the receivable amount: if yes, executing the next step; otherwise, ending the flow. Step S404, the server judges whether the sending time of the data matching request is equal to the receivable date: if yes, executing the next step; otherwise, ending the flow. Step S405, the server side judges whether the amount of money to be received is larger than zero: if not, ending the flow; if yes, the information carried in the data matching request is in accordance with all detection conditions, at this time, the data auditing operation in the step S406 can be executed, and the step S407 is executed to distribute the principal or interest amount received in the current return period to each product associated with the asset according to the position holding proportion.
Fig. 5 is a schematic diagram of a step of performing revocation matching in the first embodiment of the present invention, as shown in fig. 5, in step S501, a service person clicks a revocation button to send a revocation matching request, where the request carries an asset identifier and an identifier of any return cycle for which data matching operation has been performed, and after receiving the request sent by a client, a server performs the following determination. Step S502, the server judges whether the product associated with the asset is unchanged: if yes, executing the next step, otherwise ending the revocation flow. Step S503, the server judges whether the position holding proportion of the assets is unchanged: if yes, executing the next step, otherwise ending the revocation flow. And step S504, carrying out revocation in different modes according to the asset types. Preferably, if the asset classes are outsourcing investment, asset management plans and public fund raising, the last audit record can be withdrawn one by one; if the asset class is other assets that are allowed to be revoked, a return period may be selected by the business personnel for revocation. And step S505, the real sum and the tail sum which are distributed to the related products are collected, so that the corresponding collection period is recovered to the state of not executing the data matching operation, and the corresponding financial processing is offset. In step S506, the data matching operation is performed again according to the correct real payment amount.
In the technical scheme of the embodiment of the invention, after receiving a data matching request sent by a client, a server determines the matched service type based on the data matching request, judges whether to execute data matching operation according to a detection condition determined for the service type in advance, and further feeds back response information to the client. Through the steps and the predetermined judgment logic in each service type detection condition, the accurate judgment and the high-efficiency execution of various service types such as the matching of the pre-income value derivative value, the early matching, the cross-period matching and the like can be realized, and various specific service requirements of complex scenes are fully met. Meanwhile, the embodiment of the invention also realizes the cancellation function aiming at the matched operation, and after the server receives the cancellation matching request sent by the client, if the resource is judged to accord with the preset cancellation condition, the corresponding information can be restored to the state of not executing the data matching operation, thereby realizing the timely processing of the error operation and effectively avoiding the risk of inconsistent accounts.
It should be noted that, for the convenience of description, the foregoing method embodiments are described as a series of acts, but those skilled in the art will appreciate that the present invention is not limited by the order of acts described, and that some steps may in fact be performed in other orders or concurrently. Moreover, those skilled in the art will appreciate that the embodiments described in the specification are presently preferred and that no acts or modules are necessarily required to implement the invention.
To facilitate a better implementation of the above-described aspects of embodiments of the present invention, the following also provides relevant means for implementing the above-described aspects.
Referring to fig. 6, a data matching apparatus 600 according to an embodiment of the present invention may be used to match actual data provided by a second principal according to a preset return period with predetermined plan data after an ownership of a secondary resource is transferred from the second principal to a first principal; the device 600 is located at a server side where a first subject is located, and the data includes a value attribute value and a value derivative value of the secondary resource. The apparatus 600 may comprise: a request receiving unit 601, a service type determining unit 602 and a logic judging unit 603.
The request receiving unit 601 may be configured to receive a data matching request for any secondary resource, where the data matching request carries: the identification of the secondary resource, the data category for which the match is made, and actual data provided by the second subject; the service type determining unit 602 may be configured to determine a service type of the current matching according to the received data matching request, where the service type includes: pre-value derivative matching, advance matching or cross-cycle matching; the logic determining unit 603 may be configured to determine whether information carried in the data matching request meets a detection condition predetermined for the service type; and when the judgment result is yes, executing data matching operation, and feeding back response information representing successful matching to the client after the execution is finished.
In this embodiment of the present invention, the service type determining unit 602 may further be configured to: and when the data type carried in the data matching request is judged to be the value derivative value and the actual data carried in the data matching request is larger than the plan data of the current return period, determining the matched service type as the matching of the pre-receiving value derivative value.
In a specific application, the logic determining unit 603 may be further configured to: under the condition that the service type is matched with the pre-value derivative value: after the data matching operation is executed, the difference value between the actual data carried in the data matching request and the plan data of the current return cycle is determined as the pre-receiving actual data of the next return cycle.
In practical applications, the service type determining unit 602 may be further configured to: and when the sending time of the data matching request is judged to be earlier than the plan matching time of the current return cycle, determining the matched service type as advanced matching.
As a preferred solution, the service type determining unit 602 may further be configured to: and when judging that a history return period without data matching operation exists before the current return period, determining the matched service type as cross-period matching.
In a specific scenario, the detection condition corresponding to the matching of the pre-value derivative value may include: the secondary resource belongs to a preset first resource category; the sending time of the data matching request is equal to the plan matching time of the current return cycle; and there is no history return period before the current return period in which no data matching operation is performed.
In an actual scenario, matching the corresponding detection conditions in advance may include: the secondary resource belongs to a preset second resource category; the actual data provided by the second subject is equal to the planned data of the current return cycle; and there is no history return period before the current return period in which no data matching operation is performed.
Preferably, matching the corresponding detection conditions across cycles may include: the sending time of the data matching request is equal to the plan matching time of the current return cycle; and the actual data provided by the second subject is equal to the planned data for the current return cycle.
In an optional implementation manner, the detection condition corresponding to each service type may further include: the secondary resource is not currently in any of the resource handling flows.
In some embodiments, the detection condition corresponding to each service type may further include: the plan data for the current return cycle is greater than zero.
Preferably, the logic determining unit 603 is further configured to: after the data matching operation is executed, distributing the plan data of the current return cycle to a plurality of primary resources associated with the secondary resources according to the resource configuration proportion.
In particular, the apparatus 600 may further comprise a revocation unit for: receiving a revocation matching request sent by a client; the revocation matching request aims at any return period of any secondary resource, and the return period carries out data matching operation at historical time; and when the secondary resource is judged to meet the preset withdrawal condition, recovering the plan data distributed to the primary resource associated with the secondary resource so as to restore the return period to a state of not executing the data matching operation.
Furthermore, in the embodiment of the present invention, the revocation condition may include: the secondary resources are associated with the same primary resources at the current moment and the historical moment, and the primary resources have the same resource configuration proportion at the current moment and the historical moment.
In the technical scheme of the embodiment of the invention, after receiving a data matching request sent by a client, a server determines the matched service type based on the data matching request, judges whether to execute data matching operation according to a detection condition determined for the service type in advance, and further feeds back response information to the client. Through the steps and the predetermined judgment logic in each service type detection condition, the accurate judgment and the high-efficiency execution of various service types such as the matching of the pre-income value derivative value, the early matching, the cross-period matching and the like can be realized, and various specific service requirements of complex scenes are fully met. Meanwhile, the embodiment of the invention also realizes the cancellation function aiming at the matched operation, and after the server receives the cancellation matching request sent by the client, if the resource is judged to accord with the preset cancellation condition, the corresponding information can be restored to the state of not executing the data matching operation, thereby realizing the timely processing of the error operation and effectively avoiding the risk of inconsistent accounts.
Fig. 7 shows an exemplary system architecture 700 to which the data matching method or data matching apparatus of the embodiments of the present invention may be applied.
As shown in fig. 7, the system architecture 700 may include terminal devices 701, 702, 703, a network 704 and a server 705 (this architecture is merely an example, and the components included in a specific architecture may be adjusted according to specific application). The network 704 serves to provide a medium for communication links between the terminal devices 701, 702, 703 and the server 705. Network 704 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
A user may use the terminal devices 701, 702, 703 to interact with a server 705 over a network 704, to receive or send messages or the like. Various client applications, such as a data matching application (for example only), may be installed on the terminal devices 701, 702, 703.
The terminal devices 701, 702, 703 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.
The server 705 may be a server providing various services, such as a business server (for example only) providing support for data matching applications operated by users with the terminal devices 701, 702, 703. The service server may process the received data matching request and feed back a processing result (for example, response information representing successful matching — only an example) to the terminal devices 701, 702, and 703.
It should be noted that the data matching method provided by the embodiment of the present invention is generally executed by the server 705, and accordingly, the data matching apparatus is generally disposed in the server 705.
It should be understood that the number of terminal devices, networks, and servers in fig. 7 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
The invention also provides the electronic equipment. The electronic device of the embodiment of the invention comprises: one or more processors; the storage device is used for storing one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors realize the data matching method provided by the invention.
Referring now to FIG. 8, shown is a block diagram of a computer system 800 suitable for use in implementing an electronic device of an embodiment of the present invention. The electronic device shown in fig. 8 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.
As shown in fig. 8, the computer system 800 includes a Central Processing Unit (CPU)801 that can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)802 or a program loaded from a storage section 808 into a Random Access Memory (RAM) 803. In the RAM803, various programs and data necessary for the operation of the computer system 800 are also stored. The CPU801, ROM 802, and RAM803 are connected to each other via a bus 804. An input/output (I/O) interface 805 is also connected to bus 804.
To the I/O interface 805, AN input section 806 including a keyboard, a mouse, and the like, AN output section 807 including a network interface card such as a Cathode Ray Tube (CRT), a liquid crystal display (L CD), and the like, a speaker, and the like, a storage section 808 including a hard disk, and the like, and a communication section 809 including a network interface card such as a L AN card, a modem, and the like are connected, the communication section 809 performs communication processing via a network such as the internet, a drive 810 is also connected to the I/O interface 805 as necessary, a removable medium 811 such as a magnetic disk, AN optical disk, a magneto-optical disk, a semiconductor memory, and the like is mounted on the drive 810 as necessary, so that a computer program read out therefrom is mounted into the storage section 808 as.
In particular, the processes described in the main step diagrams above may be implemented as computer software programs, according to embodiments of the present disclosure. For example, embodiments of the invention include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the main step diagram. In the above-described embodiment, the computer program can be downloaded and installed from a network via the communication section 809 and/or installed from the removable medium 811. The computer program, when executed by the central processing unit 801, performs the above-described functions defined in the system of the present invention.
It should be noted that the computer readable medium shown in the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units described in the embodiments of the present invention may be implemented by software or hardware. The described units may also be provided in a processor, and may be described as: a processor includes a request receiving unit, a service type determining unit, and a logic judging unit. Where the names of these units do not in some cases constitute a limitation of the unit itself, for example, the request receiving unit may also be described as a "unit providing a data matching request to the service type determining unit".
As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs which, when executed by the apparatus, cause the apparatus to perform steps comprising: receiving a data matching request aiming at any secondary resource sent by a client, wherein the data matching request carries: the identification of the secondary resource, the data category for which the match is made, and actual data provided by the second subject; determining the matched service type according to the received data matching request, wherein the service type comprises: pre-value derivative matching, advance matching or cross-cycle matching; judging whether the information carried in the data matching request meets the detection condition determined for the service type in advance; and when the judgment result is yes, executing data matching operation, and feeding back response information representing successful matching to the client after the execution is finished.
In the technical scheme of the embodiment of the invention, after receiving a data matching request sent by a client, a server determines the matched service type based on the data matching request, judges whether to execute data matching operation according to a detection condition determined for the service type in advance, and further feeds back response information to the client. Through the steps and the predetermined judgment logic in each service type detection condition, the accurate judgment and the high-efficiency execution of various service types such as the matching of the pre-income value derivative value, the early matching, the cross-period matching and the like can be realized, and various specific service requirements of complex scenes are fully met. Meanwhile, the embodiment of the invention also realizes the cancellation function aiming at the matched operation, and after the server receives the cancellation matching request sent by the client, if the resource is judged to accord with the preset cancellation condition, the corresponding information can be restored to the state of not executing the data matching operation, thereby realizing the timely processing of the error operation and effectively avoiding the risk of inconsistent accounts.
The above-described embodiments should not be construed as limiting the scope of the invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (16)
1. A data matching method is used for matching actual data provided by a second main body according to a preset return period with predetermined plan data after the ownership of a secondary resource is transferred from the second main body to a first main body; the method is applied to a server side where a first main body is located, and the data comprise value attribute values and value derivative values of secondary resources;
characterized in that the method comprises:
receiving a data matching request aiming at any secondary resource sent by a client, wherein the data matching request carries: the identification of the secondary resource, the data category for which the match is made, and actual data provided by the second subject;
determining the matched service type according to the received data matching request, wherein the service type comprises: pre-value derivative matching, advance matching or cross-cycle matching;
judging whether the information carried in the data matching request meets the detection condition determined for the service type in advance; and when the judgment result is yes, executing data matching operation, and feeding back response information representing successful matching to the client after the execution is finished.
2. The method of claim 1, wherein determining the matched service type according to the received data matching request comprises:
and when the data type carried in the data matching request is judged to be the value derivative value and the actual data carried in the data matching request is larger than the plan data of the current return period, determining the matched service type as the matching of the pre-receiving value derivative value.
3. The method of claim 2, further comprising:
under the condition that the service type is matched with the pre-value derivative value: after the data matching operation is executed, the difference value between the actual data carried in the data matching request and the plan data of the current return cycle is determined as the pre-receiving actual data of the next return cycle.
4. The method of claim 1, wherein determining the matched service type according to the received data matching request comprises:
and when the sending time of the data matching request is judged to be earlier than the plan matching time of the current return cycle, determining the matched service type as advanced matching.
5. The method of claim 1, wherein determining the matched service type according to the received data matching request comprises:
and when judging that a history return period without data matching operation exists before the current return period, determining the matched service type as cross-period matching.
6. The method of claim 2, wherein matching the pre-value derivative value to the corresponding detection condition comprises:
the secondary resource belongs to a preset first resource category;
the sending time of the data matching request is equal to the plan matching time of the current return cycle;
and there is no history return period before the current return period in which no data matching operation is performed.
7. The method of claim 4, wherein matching the corresponding detection condition in advance comprises:
the secondary resource belongs to a preset second resource category;
the actual data provided by the second subject is equal to the planned data of the current return cycle;
and there is no history return period before the current return period in which no data matching operation is performed.
8. The method of claim 5, wherein matching corresponding detection conditions across cycles comprises:
the sending time of the data matching request is equal to the plan matching time of the current return cycle;
and the actual data provided by the second subject is equal to the planned data for the current return cycle.
9. The method of claim 6, 7 or 8, wherein the detecting condition for each service type further comprises:
the secondary resource is not currently in any of the resource handling flows.
10. The method of claim 9, wherein the detecting condition for each service type further comprises:
the plan data for the current return cycle is greater than zero.
11. The method of claim 1, further comprising:
after the data matching operation is executed, distributing the plan data of the current return cycle to a plurality of primary resources associated with the secondary resources according to the resource configuration proportion.
12. The method of claim 1, further comprising:
receiving a revocation matching request sent by a client; the revocation matching request aims at any return period of any secondary resource, and the return period carries out data matching operation at historical time;
and when the secondary resource is judged to meet the preset withdrawal condition, recovering the plan data distributed to the primary resource associated with the secondary resource so as to restore the return period to a state of not executing the data matching operation.
13. The method of claim 12, wherein the revocation condition comprises:
the secondary resources are associated with the same primary resources at the current moment and the historical moment, and the primary resources have the same resource configuration proportion at the current moment and the historical moment.
14. A data matching device is used for matching actual data provided by a second main body according to a preset return period with predetermined plan data after the ownership of a secondary resource is transferred from the second main body to a first main body; the device is arranged at a server side where a first main body is arranged, and the data comprise value attribute values and value derivative values of the secondary resources;
characterized in that the device comprises:
a request receiving unit, configured to receive a data matching request for any secondary resource, where the data matching request carries: the identification of the secondary resource, the data category for which the match is made, and actual data provided by the second subject;
a service type determining unit, configured to determine a service type matched this time according to the received data matching request, where the service type includes: pre-value derivative matching, advance matching or cross-cycle matching;
a logic judgment unit, configured to judge whether information carried in the data matching request meets a detection condition predetermined for the service type; and when the judgment result is yes, executing data matching operation, and feeding back response information representing successful matching to the client after the execution is finished.
15. An electronic device, comprising:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-13.
16. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-13.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010266126.9A CN111415263A (en) | 2020-04-07 | 2020-04-07 | Data matching method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010266126.9A CN111415263A (en) | 2020-04-07 | 2020-04-07 | Data matching method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111415263A true CN111415263A (en) | 2020-07-14 |
Family
ID=71493364
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010266126.9A Pending CN111415263A (en) | 2020-04-07 | 2020-04-07 | Data matching method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111415263A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115712843A (en) * | 2022-12-01 | 2023-02-24 | 潍坊羞摆信息科技有限公司 | Data matching detection processing method and system based on artificial intelligence |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103198091A (en) * | 2012-12-04 | 2013-07-10 | 网易（杭州）网络有限公司 | User-behavior-based online data request processing method and equipment |
| CN103810635A (en) * | 2014-03-05 | 2014-05-21 | 南京聪诺信息科技有限公司 | Method and device for realizing checking of loan business processing flow |
| WO2017041398A1 (en) * | 2015-09-08 | 2017-03-16 | 安一恒通（北京）科技有限公司 | Data transmission method and device |
| CN107798448A (en) * | 2016-12-15 | 2018-03-13 | 平安科技（深圳）有限公司 | The determination methods and device of black list user |
| CN110458556A (en) * | 2019-07-02 | 2019-11-15 | 阿里巴巴集团控股有限公司 | A kind of fund checking method, device, computer equipment and system architecture |
| CN110598993A (en) * | 2019-08-19 | 2019-12-20 | 深圳市鹏海运电子数据交换有限公司 | Data processing method and device |
-
2020
- 2020-04-07 CN CN202010266126.9A patent/CN111415263A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103198091A (en) * | 2012-12-04 | 2013-07-10 | 网易（杭州）网络有限公司 | User-behavior-based online data request processing method and equipment |
| CN103810635A (en) * | 2014-03-05 | 2014-05-21 | 南京聪诺信息科技有限公司 | Method and device for realizing checking of loan business processing flow |
| WO2017041398A1 (en) * | 2015-09-08 | 2017-03-16 | 安一恒通（北京）科技有限公司 | Data transmission method and device |
| CN107798448A (en) * | 2016-12-15 | 2018-03-13 | 平安科技（深圳）有限公司 | The determination methods and device of black list user |
| CN110458556A (en) * | 2019-07-02 | 2019-11-15 | 阿里巴巴集团控股有限公司 | A kind of fund checking method, device, computer equipment and system architecture |
| CN110598993A (en) * | 2019-08-19 | 2019-12-20 | 深圳市鹏海运电子数据交换有限公司 | Data processing method and device |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115712843A (en) * | 2022-12-01 | 2023-02-24 | 潍坊羞摆信息科技有限公司 | Data matching detection processing method and system based on artificial intelligence |
| CN115712843B (en) * | 2022-12-01 | 2023-10-27 | 北京国联视讯信息技术股份有限公司 | Data matching detection processing method and system based on artificial intelligence |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8301533B1 (en) | Automated fulfilling of currency exchange requests over a computer network | |
| CN109584031A (en) | Account checking method, device, electronic equipment and computer-readable medium | |
| CN111476460B (en) | Method, equipment and medium for intelligent operation scheduling of self-service equipment of bank | |
| CN109285069B (en) | Resource transfer method, device and server | |
| CN110599323A (en) | Resource processing method and processing equipment | |
| CN111444213B (en) | Ledger clearing system and method based on credit business | |
| CN112184240A (en) | Refund request processing method and device | |
| US20210224895A1 (en) | Settlement management system and settlement management method | |
| CN110889686A (en) | Multi-level account data processing method, device, equipment and readable storage medium | |
| KR102063877B1 (en) | Method of managing a trust agreement and computer program stored on a computer readable storage medium for executing the method | |
| CN112907344A (en) | Accounting data processing method and device, electronic equipment and storage medium | |
| CN111415263A (en) | Data matching method and device | |
| CN111401873A (en) | Task creation method and device, storage medium and electronic equipment | |
| CN112184418A (en) | Inter-company loan processing method, inter-company loan processing device, computer equipment and storage medium | |
| JP7212186B1 (en) | Information processing system, information processing method and information processing program | |
| JP2023076425A (en) | Information processing device, information processing method and information processing program | |
| CN111429092B (en) | Method, apparatus, device and computer readable medium for paying an accumulation fund | |
| JP6058620B2 (en) | Loan transaction automatic execution system and method | |
| CN112258306B (en) | Account information checking method, device, electronic equipment and storage medium | |
| CN110135803B (en) | Item management method and block chain link point equipment | |
| CN112132692A (en) | Policy data processing method and device, storage medium and electronic equipment | |
| CN109359965A (en) | A kind of transfer charge method of payment and system | |
| KR102236887B1 (en) | A method and apparatus of transferring funds including fees and grant | |
| CN113379523A (en) | Bill generation method, device, medium and electronic equipment | |
| CN115496581A (en) | Account amount transferring method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20220920 Address after: 25 Financial Street, Xicheng District, Beijing 100033 Applicant after: CHINA CONSTRUCTION BANK Corp. Address before: 25 Financial Street, Xicheng District, Beijing 100033 Applicant before: CHINA CONSTRUCTION BANK Corp. Applicant before: Jianxin Financial Science and Technology Co.,Ltd. |