CN113822660A

CN113822660A - Data processing method and device, electronic equipment and medium

Info

Publication number: CN113822660A
Application number: CN202111177937.2A
Authority: CN
Inventors: 冯钰栋; 张栋芳
Original assignee: Jingdong Technology Holding Co Ltd
Current assignee: Jingdong Technology Holding Co Ltd
Priority date: 2021-10-09
Filing date: 2021-10-09
Publication date: 2021-12-21

Abstract

The present disclosure relates to a method, an apparatus, an electronic device, and a medium for data processing, the method including: receiving a data operation request, wherein the data operation request comprises: target operating instructions for the bill to be returned; under the condition that the data operation request is received, acquiring the to-be-paid bill and to-be-processed data in the bill particulars of the to-be-paid bill; according to a preset subject, converting the data to be processed, and respectively and correspondingly obtaining the bill to be returned and the bill detail which are matched with a first data item and a second data item of the preset subject; and performing data cancellation and verification on the first data item and the second data item according to the target operation instruction and a preset cancellation rule and a preset verification rule to obtain a result after data processing.

Description

Data processing method and device, electronic equipment and medium

Technical Field

The present disclosure relates to the field of internet and the field of finance, and in particular, to a method and an apparatus for data processing, an electronic device, and a medium.

Background

With the development of information technology, business data processing for trading scenarios is becoming more and more intelligent and efficient. Taking financial institutions as an example, users conduct full payment or staged payment before a requested time limit after transacting credit cards or consuming in advance based on personal credit. The data processing procedure in the data processing scenario roughly includes: the bill is paid and cancelled, and then the payment and cancellation processing is carried out on each fund subject under the bill specification.

In the course of implementing the disclosed concept, the inventors found that there are at least the following technical problems in the related art: in a complex data processing scene, for example, a bill balance scene exists, in this case, when data processing is performed, only data of a bill and bill details can be acquired in the related art, and a payment result is obtained by making a payment for the bill according to the data, and then a payment is made for each subject of the bill details. Corresponding to a balance scenario or other complex data processing scenarios, the processing logic cannot determine whether the repayment amount is a subject in a reimbursed and balanced bill or a subject in a newly added bill, how to process the installments or non-installments, and in some services with the lowest payment amount requirement, the processing logic of the related art cannot update data of subjects which do not exist in the details, so that the related art has difficulty in realizing data processing of the complex data processing scenario, or has complex processing logic and is easy to make mistakes.

Disclosure of Invention

To solve the technical problem or at least partially solve the technical problem, embodiments of the present disclosure provide a method, an apparatus, an electronic device, and a medium for data processing.

In a first aspect, an embodiment of the present disclosure provides a data processing method. The method comprises the following steps: receiving a data operation request, wherein the data operation request comprises: target operating instructions for the bill to be returned; under the condition that the data operation request is received, acquiring the to-be-paid bill and to-be-processed data in the bill particulars of the to-be-paid bill; according to a preset subject, converting the data to be processed, and respectively and correspondingly obtaining the bill to be returned and the bill detail which are matched with a first data item and a second data item of the preset subject; and performing data cancellation and verification on the first data item and the second data item according to the target operation instruction and a preset cancellation rule and a preset verification rule to obtain a result after data processing.

According to an embodiment of the present disclosure, the performing data cancellation and verification on the first data item and the second data item according to the target operation instruction and a pre-configured cancellation rule and verification rule to obtain a result after data processing includes: checking the correctness of the first data item and the second data item according to a preset checking rule; when the correctness of the first data item and the second data item passes the verification, performing data cancellation on the second data item or the first data item and the second data item according to a preset cancellation rule and the target operation instruction to obtain cancelled bill data and bill detail data; according to the verification rule, verifying the correctness of the bill data and the bill detail data after the cancellation; and under the condition that the correctness of the bill data and the bill detail data after the cancellation passes the verification, taking the bill data and the bill detail data after the cancellation as the result after the data processing.

According to an embodiment of the present disclosure, the offset rule is associated with an identifier of a data processing scenario, and the offset rule includes: and under a candidate data processing scene, aiming at the preset punching and canceling sequence of the preset subjects and the first data processing logic of punching and canceling. The candidate data processing scenario includes: and processing data scenes corresponding to the target operation instructions. According to a pre-configured offset rule and the target operation instruction, performing data offset on the second data item to obtain offset bill data and bill detail data, including: determining a target cancellation rule corresponding to the target operation instruction according to the identifier of the data processing scene associated with the cancellation rule, where the target cancellation rule includes: aiming at the target punching and pinning sequence of the preset subjects, punching and pinning a first target logic; according to the first target logic, the following operations are executed: determining the target operation instruction corresponding to operation detail data of each preset branch objective based on the target punching and canceling sequence; based on the operation detail data, carrying out punching and canceling processing on the second data item to obtain punched and canceled bill detail data; and summarizing the bill detail data after the punching and the marketing to obtain the bill data after the punching and the marketing.

According to an embodiment of the present disclosure, the verifying the correctness of the cancelled bill data and the cancelled bill detail data includes: summarizing the operation detail data according to the preset subjects to obtain data to be punched and sold; based on the data to be punched and sold, punching and selling the first data item to obtain first bill data to be verified; determining whether the first bill data to be checked is consistent with the bill data after the cancellation; and under the condition that the first bill data to be verified is inconsistent with the bill data after the cancellation, the correctness verification of the bill data after the cancellation and the bill detail data is not passed.

According to another embodiment of the present disclosure, the offset rule is associated with an identifier of a data processing scenario, and the offset rule includes: and under a candidate data processing scene, aiming at the preset punching and canceling sequence of the preset subjects and a second data processing logic of punching and canceling. The data cancellation of the first data item and the second data item according to the pre-configured cancellation rule and the target operation instruction to obtain the cancelled bill data and bill detail data includes: determining a target cancellation rule corresponding to the target operation instruction according to the identifier of the data processing scene associated with the cancellation rule, where the target cancellation rule includes: aiming at the target punching and pinning sequence of the preset subjects, punching and pinning a second target logic; according to the second target logic, the following operations are executed: determining the target operation instruction corresponding to operation detail data of each preset branch objective based on the target punching and canceling sequence; based on the operation detail data, carrying out punching and canceling processing on the second data item to obtain punched and canceled bill detail data; summarizing the operation detail data according to the preset subjects to obtain data to be punched and sold; and carrying out punching and canceling processing on the first data item based on the data to be punched and canceled to obtain the bill data after punching and canceling.

According to an embodiment of the present disclosure, the verifying the correctness of the cancelled bill data and the cancelled bill detail data includes: summarizing the bill detail data after the cancellation to obtain second bill data to be verified; determining whether the second bill data to be checked is consistent with the bill data after the cancellation; and under the condition that the second bill data to be verified is inconsistent with the bill data after the cancellation, the correctness verification of the bill data after the cancellation and the bill detail data is not passed.

According to an embodiment of the present disclosure, the checking the correctness of the first data item and the second data item includes: checking the consistency of the first data item and the aggregated second data item; and if the first data item is inconsistent with the second data item after the aggregation, the correctness check of the first data item and the second data item is not passed.

According to an embodiment of the present disclosure, the target operation instruction includes at least one of: and carrying out a payment due operation of the first amount, carrying out a payment refund operation of the second amount, carrying out a fee deduction operation of the third amount and carrying out an advanced payment operation of the fourth amount.

According to an embodiment of the present disclosure, the converting the to-be-processed data according to a preset subject, and correspondingly obtaining the to-be-returned bill and the first data item and the second data item of which the bill details are matched with the preset subject respectively includes: acquiring a target data table template corresponding to the data processing scene of the account to be returned from pre-constructed data table templates aiming at different data processing scenes; obtaining preset subjects according to the column information of the target data table template; converting the data to be processed in the bill to be returned to obtain first column data of each preset subject corresponding to the same data row in the target data table template, wherein the first column data is a first data item; and converting the data to be processed in the current bill particulars to obtain second lines of data of each preset department corresponding to the same data row in the target data table template, wherein the second lines of data are second data items.

According to an embodiment of the present disclosure, the method further includes: and configuring a punching rule and a checking rule. The configuration cancellation rule and the verification rule comprise: receiving rule configuration information for candidate data processing scenarios, where the candidate data processing scenarios include data processing scenarios of the to-be-returned bill, and the rule configuration information includes: the method comprises the steps of canceling rule information, verifying rule information and generating a script type; performing semantic check on the rule configuration information; and when the rule configuration information passes semantic verification, generating an offset rule code and a verification rule code corresponding to the generated script type according to the generated script type, wherein the offset rule code and the verification rule code are used as configured offset rules and verification rules.

According to an embodiment of the present disclosure, the method further includes: and loading the punching rule and the verification rule. The loading cancellation rule and the verification rule comprise: acquiring the generation script types of the offset rule codes and the verification rule codes; determining a target loader to be started, which is matched with the generated script type, according to the generated script type; and starting the target loader to load the offset rule code and the check rule code.

In a second aspect, embodiments of the present disclosure provide an apparatus for data processing. The above-mentioned device includes: the device comprises a request receiving module, a data acquisition module, a data conversion module and a data processing module. The request receiving module is configured to receive a data operation request, where the data operation request includes: target operating instructions for the bill to be returned. The data acquisition module is used for acquiring the to-be-processed data in the bill particulars of the to-be-returned bill and the to-be-returned bill under the condition that the data operation request is received. The data conversion module is used for converting the data to be processed according to a preset subject, and correspondingly obtaining the bill to be returned and the bill detail which are matched with the first data item and the second data item of the preset subject respectively. And the data processing module is used for carrying out data cancellation and verification on the first data item and the second data item according to the target operation instruction and a preset cancellation rule and a preset verification rule to obtain a result after data processing.

In a third aspect, embodiments of the present disclosure provide an electronic device. The electronic equipment comprises a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory are communicated with each other through the communication bus; a memory for storing a computer program; a processor for implementing the data processing method described above when executing the program stored in the memory.

In a fourth aspect, embodiments of the present disclosure provide a computer-readable storage medium. The above-mentioned computer-readable storage medium has stored thereon a computer program which, when executed by a processor, implements the method of data processing as described above.

Compared with the prior art, the technical scheme provided by the embodiment of the disclosure at least has part or all of the following advantages:

uniformly converting the data to be processed in the bill statement and the bill counter statement into data items under preset subjects: the first data item and the second data item can be subjected to data cancellation and verification according to a target operation instruction and a preset cancellation rule and a preset verification rule, and a result after data processing is obtained; because the data items obtained after conversion are relied in the data reimbursement and verification processing process of the data, and the data items are not the original data to be processed corresponding to the bill particulars of the bill to be paid back, the decoupling of the service scene and the data items can be realized, and simultaneously reimbursement rules and verification rules such as processing sequence, processing logic, verification mode and the like of each subject under each data processing scene (for example, service scenes such as due payment, advanced payment, request expense reduction, refund and the like) are configured in advance, so that the data operation requests under various complex scenes can be processed efficiently and accurately, the error position can be verified, the data processing method is not only suitable for data processing under a final scene, but also can be applied to various data processing scenes with incidence relation.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure.

In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the related art will be briefly described below, and it is obvious for those skilled in the art to obtain other drawings without inventive exercise.

FIG. 1 schematically illustrates a system architecture of a method and apparatus for data processing suitable for use with embodiments of the present disclosure;

FIG. 2 schematically shows a flow diagram of a method of data processing according to an embodiment of the present disclosure;

fig. 3 schematically shows a detailed implementation flowchart of operation S203 according to an embodiment of the present disclosure;

fig. 4 schematically shows a detailed implementation flowchart of operation S204 according to an embodiment of the present disclosure;

FIG. 5A schematically illustrates a detailed implementation flow diagram for data cancellation according to an embodiment of the present disclosure;

FIG. 5B schematically illustrates a detailed implementation flow diagram for data cancellation according to another embodiment of the present disclosure;

FIG. 6 schematically shows a flow diagram of a method of data processing according to another embodiment of the present disclosure;

fig. 7 schematically shows a detailed implementation flowchart of operation S601 according to an embodiment of the present disclosure;

FIG. 8 schematically shows a flow chart of a method of data processing according to a further embodiment of the present disclosure;

fig. 9 schematically shows a detailed implementation flowchart of operation S801 according to an embodiment of the present disclosure;

fig. 10 schematically shows a block diagram of a data processing apparatus according to an embodiment of the present disclosure; and

fig. 11 schematically shows a block diagram of an electronic device provided in an embodiment of the present disclosure.

Detailed Description

The embodiment of the disclosure provides a data processing method and device, electronic equipment and a medium. The method comprises the following steps: receiving a data operation request, wherein the data operation request comprises: target operating instructions for the bill to be returned; under the condition that the data operation request is received, acquiring the to-be-paid bill and to-be-processed data in the bill particulars of the to-be-paid bill; according to a preset subject, converting the data to be processed, and respectively and correspondingly obtaining the bill to be returned and the bill detail which are matched with a first data item and a second data item of the preset subject; and performing data cancellation and verification on the first data item and the second data item according to the target operation instruction and a preset cancellation rule and a preset verification rule to obtain a result after data processing.

To make the objects, technical solutions and advantages of the embodiments of the present disclosure more clear, the technical solutions of the embodiments of the present disclosure will be described clearly and completely with reference to the drawings in the embodiments of the present disclosure, and it is obvious that the described embodiments are some embodiments of the present disclosure, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments disclosed herein without making any creative effort, shall fall within the protection scope of the present disclosure.

Fig. 1 schematically shows a system architecture of a method and apparatus for data processing suitable for use in embodiments of the present disclosure.

Referring to fig. 1, a system architecture 100 suitable for the method and apparatus for data processing according to the embodiment of the present disclosure includes:

terminal devices

101, 102, 103, a network 104 and a server 105. The network 104 is a medium that provides communication links between the

terminal devices

101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.

The user may use the

terminal devices

101, 102, 103 to interact with the server 105 via the network 104 to receive or send messages or the like. The

terminal devices

101, 102, 103 may have installed thereon various communication client applications, such as financial applications, which may be related to the consuming and repayment operations of the user. The user can operate the terminal equipment to realize payment operation, and the user can be a payment person or a staff of a financial institution.

In addition, the

terminal devices

101, 102, and 103 may further have a shopping application, a web browser application, a search application, an instant messaging tool, a mailbox client, social platform software, and the like (for example only) installed thereon.

The

terminal devices

101, 102, 103 may be various electronic devices having a display screen and supporting web browsing, such as electronic devices including but not limited to: smart phones, tablets, laptops, desktop computers, smart watches, and the like.

The server 105 may be a server providing various services, such as a background management server (for example only) providing service support for application interfaces or web pages browsed by users using the

terminal devices

101, 102, 103. The background management server may analyze and process the received request data (e.g., a payment operation request), and feed back a processing result (e.g., data, a web page, information, etc. obtained by processing the data according to the payment operation request of the user) to the terminal device.

It should be noted that the method for processing data provided by the embodiment of the present disclosure may be generally executed by the server 105 or the

terminal devices

101, 102, and 103 having a certain computing capability. Accordingly, the data processing apparatus provided by the embodiment of the present disclosure may be generally disposed in the server 105 or the

terminal devices

101, 102, and 103 with certain computing capability. The method for processing data provided by the embodiments of the present disclosure may also be performed by a server or a server cluster different from the server 105 and capable of communicating with the

terminal devices

101, 102, 103 and/or the server 105. Accordingly, the data processing apparatus provided by the embodiment of the present disclosure may also be disposed in a server or a server cluster different from the server 105 and capable of communicating with the

terminal devices

101, 102, 103 and/or the server 105.

When the data processing method of the embodiment of the disclosure is executed by a terminal device, an application (for example, a financial application) may be installed on the terminal device, and a rule engine is embedded in the application. The rule engine is developed from an inference engine, is a component embedded in an application program, and can separate business decisions from application program codes and write the business decisions by using a predefined semantic module. The rule engine is used for receiving data input, explaining the business rules, making business decisions according to the business rules and obtaining business results.

It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

Embodiments of the present disclosure are described in detail below with reference to the accompanying drawings.

A first exemplary embodiment of the present disclosure provides a method of data processing.

Fig. 2 schematically shows a flow diagram of a method of data processing according to an embodiment of the present disclosure.

Referring to fig. 2, a method for data processing provided by an embodiment of the present disclosure includes the following operations: s201, S202, S203 and S204.

In operation S201, a data operation request is received, where the data operation request includes: target operating instructions for the bill to be returned.

In operation S202, when the data operation request is received, the to-be-returned bill and the to-be-processed data in the bill particulars of the to-be-returned bill are acquired.

In operation S203, the to-be-processed data is converted according to a preset subject, and the to-be-returned bill and the bill particulars are respectively and correspondingly obtained to be matched with the first data item and the second data item of the preset subject.

In operation S204, data cancellation and verification are performed on the first data item and the second data item according to the target operation instruction and a preset cancellation rule and a preset verification rule, so as to obtain a result after data processing.

The above-described operations S201 to S204 may be performed by a terminal device or a server.

In the embodiments of the present disclosure, the data processing scenarios include, but are not limited to: due repayment, advanced repayment, request expense exemption, refund and other business scenes. Accordingly, the target operating instructions for the pending invoice include, but are not limited to, at least one of: performing a due payment operation for a first amount, performing a refund operation for a second amount, performing a charge deduction operation for a third amount, performing an advance payment operation for a fourth amount, and the like.

In the embodiment of the present disclosure, the precondition for generating the account to be returned may be: the customer (fund spending person, which may be an individual or a business) performs various arrears in advance on the terminal device installed with the financial application program, such as: borrowing or loan (e.g., borrowing or loan from a financial institution), making advance consumption (post-payment/repayment) based on credit line (e.g., using credit card for consumption, using flower for consumption, etc.), and the like.

In the embodiment of the disclosure, the account to be paid is a broad concept, which refers to a debt payment amount voucher corresponding to the consumer, and the debt payment amount voucher can be in the form of a flower bill, a borrow book, a loan bill, a debit bill and the like in an actual application scene.

When the above operation S201 is performed by the terminal device, the corresponding scenario may be: the payment personnel (which may correspond to the customer who actually performs the capital expenditure or a person/enterprise associated with the customer) initiates a data operation request corresponding to due payment, advanced payment, request cost deduction, refund and the like through a financial application program on the terminal device, or the payment personnel performs business transaction such as due payment, advanced payment, request cost deduction, refund and the like on a counter of the financial institution, and the data operation request is initiated by the staff based on the terminal device. In this case, a data operation request initiated by a customer or a worker is received on the terminal device.

When the above operation S201 is performed by the server, the corresponding scenario may be: the user (which may be a payment person or a financial institution staff member) initiates a data operation request on a financial application program of a terminal device, and the terminal device sends the data operation request to the server. The above-described data operation request is received at the server side (corresponding to operation S201).

When the operation S202 is executed by the terminal device, the terminal device may obtain the to-be-processed data in the bill particulars of the to-be-returned bill and the to-be-returned bill from the server with the database service, or obtain the to-be-processed data from the corresponding database through the server; in other scenarios, the terminal device may also obtain the data to be processed from a local memory or storage device.

When the above operation S202 is performed by the server, the server acquires the to-be-returned bill and the to-be-processed data in the bill particulars of the to-be-returned bill from the database.

In operation S203, the preset subjects may be subjects adapted to a current data processing scene, where the current data processing scene is a data processing scene corresponding to the to-be-returned bill. The predetermined subjects can at least cover the types of data to be processed for data cancellation.

For example, in a data processing scenario of carrying out a payment operation on a transferred bill, subjects of the bill to be paid include: total waiting for redemptions, waiting for periodic commission fees, waiting for daily returns, waiting for penalties, waiting for redemptions of the principal, and lowest payoff amount. The detailed subjects of the bill to be returned include: the system comprises a total waiting fee, a pending payment due installment fee, a pending payment daily, a pending payment penalty, a installment type, a service identifier and a lowest payment amount, wherein the installment type comprises: not staging, order staging, bill staging; the service identification comprises: and (5) common cash withdrawal.

The preset subjects can be adapted to a data processing scenario of a payment operation for a transferred bill, and for example, the preset subjects may include part or all of the following: total pending return, pending return daily, non-installment lowest (optional), balance bill installment principal, balance order installment principal, balance non-installment lowest (optional), balance withdrawal, and lowest payoff amount. For optional content with parenthesis labels, the subjects are necessary in a business scene in which calculation is needed and the lowest detail is given, and the subjects which can be labeled are not necessary in a scene in which the lowest detail does not need to be calculated.

In operation S203, the to-be-processed data in the to-be-returned bill and the bill particulars thereof are converted, so that the to-be-processed data are uniformly converted into data items (including the first data item and the second data item) under the preset subjects, and decoupling of the service scene and the data items can be achieved. In subsequent operation S204, only the data items (including the first data item and the second data item) need to be correspondingly processed based on the preset cancellation rule, the verification rule, and the target operation instruction, so that the logic of data processing for various complex data processing scenarios is simplified.

In operation S204, the cancellation rule and the verification rule are pre-configured. The corresponding scenario may be: the research and development personnel or the business personnel of the financial application program can perform pre-configuration according to rules such as processing sequence, processing logic, verification mode and the like of each subject under each data processing scene (for example, a business scene) based on the terminal equipment to obtain the reimbursement rule and the verification rule.

The above service scenarios are such as: due payment, advanced payment, request for cost reduction and exemption, refund and the like. Such cost reductions include, but are not limited to, at least one of the following: the data processing logic performs data reimbursement processing on data items under related subjects such as rest fee, commission fee and the like in the scene of fee reduction. For a scenario of payment in advance (for example, closing before the due date), the processing logic performs data cancellation processing for the fee deduction operation in combination with the payment operation, performs the fee deduction operation first (the fee deduction of the unexpired part), and then performs the payment operation for the actual arrears. In a refund scene (for example, a scene of canceling an original transaction), data items under subjects relevant to refund are subjected to data reimbursement processing, and meanwhile, data changes are made on subjects relevant to treatment and return.

In these data processing scenarios, the data reimbursement process is consistent with the data reimbursement process in the payment scenario, and the data items (including the first data item and the second data item) in the bill and the bill detail subject are updated according to the target operation instruction. Meanwhile, the data item needs to be verified before the data is punched and sold, and the punching and selling result needs to be verified again after the data is punched and sold.

When the operations S203 to S204 are performed by a terminal device, the terminal device may have an application (e.g., a financial application) installed thereon, and the application has a rule engine embedded therein, and the operations S203 and S204 are implemented based on a function module in the rule engine.

When the above operations S203 to S204 are performed by a server, the server may have a function module therein to perform data conversion and rule-based calculation.

Based on the above operations S201 to S204, the to-be-returned bill and the to-be-processed data in the bill particulars are uniformly converted into data items under the preset subjects: the first data item and the second data item can be subjected to data cancellation and verification according to a target operation instruction, a preset cancellation rule and a preset verification rule, and a result after data processing is obtained; because the converted data items are relied in the data cancellation and verification processing process of the data and the data to be processed corresponding to the original bill to be returned and the bill particulars are not the original bill to be returned, the decoupling of the service scene and the data items can be realized, meanwhile, cancellation rules and verification rules such as processing sequence, processing logic, verification mode and the like of each department under each service scene are configured in advance, so that the data operation requests under various complex scenes can be processed efficiently and accurately, the error positions can be verified, the method and the system are not only suitable for data processing under the final scene, but also can be applied to various data processing scenes with data in association.

Fig. 3 schematically shows a detailed implementation flowchart of operation S203 according to an embodiment of the present disclosure.

According to an embodiment of the present disclosure, as shown in fig. 3, the operation S203 of converting the to-be-processed data according to a preset subject, and obtaining the to-be-paid bill and the bill detail respectively corresponding to the first data item and the second data item of the preset subject includes the following operations: s301, S302, S303 and S304.

In operation S301, a target data table template corresponding to the data processing scenario of the account to be returned is obtained from pre-constructed data table templates for different data processing scenarios.

In operation S302, a preset subject is obtained according to the column information of the target data table template.

In operation S303, the data to be processed in the bill to be returned is converted to obtain first column data of each preset subject corresponding to the same data row in the target data table template, where the first column data is a first data item.

In operation S304, for the to-be-processed data in each bill specification, the to-be-processed data in the current bill specification is converted to obtain second lines of data of each preset department corresponding to the same data row in the target data table template, where the second lines of data are second data items.

For example, in the embodiment of operation S301, the pre-constructed data table template has scene identifiers of different data processing scenes, and the target data table template corresponding to the data processing scene of the pending payment account can be located through the scene identifiers. Or the data table template constructed according to different data processing scenes has certain relevance and coverage with the account in the bill particulars and the to-be-returned bill under each data processing scene, and the target data table template corresponding to the current data processing scene is correspondingly obtained by matching special accounts, for example, under some data processing scenes, accounts related to the balance item exist; in some data processing scenes, subjects related to the forwarding items do not exist; in some data processing scenarios, it is required to set the minimum amount of each type of payment, and the like, and these different subjects can be used as special subjects distinguished in different service scenarios.

The column information of the data table template is configured in advance, and may cover types of each data to be processed by data reimbursement in a data processing scenario (a large-scale data processing scenario, for example, a payment scenario, or a fine-scale data processing scenario, for example, due payment, advanced payment, fee reduction and exemption operations in the payment scenario (for example, commission fees and interest fees), refund operations, and the like) corresponding to the data table template. In the operation S302, a part of column information or all column information in the target data table template may be used as the preset subject.

In the operation S303, the data to be processed in the bill to be returned is converted to obtain the first data item.

In the operation S304, the data to be processed in the bill specification of the bill to be returned is converted to obtain the second data item.

The method for processing data according to the embodiment of the present disclosure is described in detail below with reference to specific data to be processed.

In an exemplary embodiment, the data to be processed in the bill to be reconciled and the bill specification of the bill to be reconciled acquired in the operation S202 correspond to the data exemplified in the following table 1 and table 2, respectively.

For ease of understanding, the contents of the above table 1 will be described below. In table 1, the account to be returned in the carry forward scenario is exemplified. The bill to be paid comprises two major parts, wherein one major part is the forwarded bill, and the other major part is the bill at the current period (which can also be described as the current period). Wherein, in the transferred bill, the transfer amount is 800 yuan, the daily interest to be returned generated by the transfer amount is 33, and the penalty to be returned is 17; in the bill in this period (current period), the balance of money to be paid in this period is 150. According to the preset stipulation, the lowest payment amount (775 Yuan) is 10% of the money to be paid in the period (150 Yuan x 10% is 15 Yuan) + the daily information to be paid (33 Yuan) + the penalty information to be paid (17 Yuan) + the lowest payment amount of the original transfer bill (710 Yuan).

For ease of understanding, the contents of table 2 are described below. In table 2, corresponding to the bill to be paid in the forwarding scenario of table 1, the detail of the forwarded bill may refer to the data in the first 4 rows (except for the header column and the header) in the 5 rows of data in table 2, and the detail of the bill in this period may refer to the data in the last row (row 5) in the 5 rows of data in table 2. Wherein, for the non-installled bill data 150 (data of line 5), the minimum payoff amount is 10% of the amount thereof, that is: 150 yuan × 10% ═ 15 yuan.

In the data processing scenario taking the balance scenario as an example, in the related art, there are problems that repayment data processing in a complex scenario cannot be performed, for example, it cannot be determined whether the target operation instruction is a subject in a bill for reimbursement balance or a subject in a newly added bill in the details, how to process the services with or without an installment, and in some services with the lowest payoff amount requirement, the processing logic of the related art cannot perform data update on subjects that do not exist in the details. Furthermore, the associated processing logic, even if forced to do so, then there is: and the processed detailed data offset data of the bill is inconsistent with the data offset data of the bill, and the data cannot be verified whether the data is correct or not.

Specifically, if the target operation instruction for the user to pay the account to be paid is 500 yuan, based on the processing logic in the related art, data cancellation is performed on the bill level first, and then data cancellation is performed on the bill detail level. And (4) canceling the total data 1000 to be paid to obtain the bill data 500 after canceling, wherein the specific canceling is to pay the money, pay the day or carry over amount is not clear. If 500-inch deduction can be performed at the billing level, for example, 500-yuan deduction can be performed for the transfer amount, and thus the transfer amount (for simplification of explanation, only numerical values will be explained later, and units are omitted) after deduction at the billing level (corresponding to table 1) is 800-500-300. However, in the detail level processing, for example, when the service is actually processed, there is no preset logic for performing the data cancellation of the pending date or the cancellation of the carry-over amount, that is, in the detail level (corresponding to table 2), it is not possible to determine how to perform the corresponding cancellation. If there is a corresponding sequence of punches, it is evident that: the detailed data of the daily interest to be restored after the cancellation are as follows: if the counter balance for the offset balance is less than 500 (450) and 50-50 is 0, the processed detailed data offset data of the bill is inconsistent with the data offset data of the bill, and the verification cannot be performed.

In the embodiment of the present disclosure, by implementing the operations S201 to S204, the above technical problem can be effectively solved, and meanwhile, the method can also be applied to data processing scenarios such as due payment, advanced payment, requested cost exemption, refund, and the like. The implementation of operations S302 to S304 in operation S203 is described below with reference to the embodiments corresponding to tables 1 and 2 above.

For example, in operation S302, all of the column information in the target data table template are used as preset subjects, and the preset subjects can be adapted to the transfer statement bill illustrated in tables 1 and 2 as a data processing scenario of the bill to be paid back, and the preset subjects may include the following subjects: the total waiting for returning, the waiting for returning daily, the non-installments are lowest, the non-installments are not lowest, the balance bill is balance, the balance order is balance, the balance is not lowest, the balance is taken out, and the balance is lowest.

The target data table template is illustrated in table 3, where the number of rows of the target data table template is merely an example, and may be added or deleted according to actual data requirements.

For convenience of example, the execution sequence of the operation S303 and the operation S304 is not limited, and the operation S303 may be executed sequentially or may be executed synchronously, where the operation S303 is executed first and then the operation S304 is executed, and a first target data table obtained after the target data table template is filled with a first data item is shown in table 4; the second target data table resulting after the target data table template is populated with second data items is illustrated in table 5. The actually obtained target data table is a data table obtained by superimposing the first data table and the second data table, as shown in fig. 6.

In table 4, the minimum non-installments can be obtained according to a preset rule, the minimum non-installments obtained by 150 (to be returned) × 10% is 15, and the corresponding non-installments are: 150 (pending reduction of gold) -15 (not phased lowest) -135.

In tables 4 to 6, the blank part means: without a data item. Having a data item value is the corresponding first data item and second data item, where the value of the data item may be 0.

The operation S204 executed subsequently can be regarded as an operation of performing data cancellation and verification on the target data table.

Fig. 4 schematically shows a detailed implementation flowchart of operation S204 according to an embodiment of the present disclosure.

According to an embodiment of the present disclosure, as shown in fig. 4, the operation S204, which performs data cancellation and verification on the first data item and the second data item according to the target operation instruction, the pre-configured cancellation rule and the verification rule, and obtains a result after data processing, includes the following operations: s401, S402a, S403, and S404 a.

In operation S401, correctness of the first data item and the second data item is checked according to a pre-configured check rule.

In operation S402a, if the correctness of the first data item and the second data item is verified, the second data item or the first data item and the second data item are subjected to data cancellation according to a preset cancellation rule and the target operation command, so as to obtain cancelled bill data and bill detail data.

In operation S403, the correctness of the cancelled bill data and the cancelled bill detail data is verified according to the verification rule.

In operation S404a, if the verification of the correctness of the invoiced bill data and the bill particulars data passes, the invoiced bill data and the bill particulars data are processed as a result of the data processing.

According to an embodiment of the present disclosure, referring to fig. 4, the operation S204 may further include the following operations: s402b, S404 b.

In operation S402b, in a case that the correctness checks of the first data item and the second data item do not pass, a data item having a problem in the first data item and the second data item is located and prompted.

In operation S404b, if the verification of correctness of the invoiced bill data and the bill particulars data fails, the data item with the problem in the invoiced bill data and the bill particulars data is located and verified and corrected by the invoiced bill data and the bill particulars data, and the corrected bill data and the bill particulars data are used as the result of data processing.

Based on the logics of primary verification, cancellation and secondary verification, the correctness of the initial data is ensured by verifying the correctness of the first data item and the second data item obtained after conversion in advance; then carrying out data punching and canceling on the correct initial data to obtain a result after punching and canceling; furthermore, the correctness of the result after the offset is checked again, so that the problems occurring in the offset calculation process can be found in time, and the problems occurring can be positioned and updated in real time, thereby ensuring that the result of data processing is correct and realizing the efficient and accurate processing of the data operation request.

According to an embodiment of the present disclosure, the operation S401 of checking correctness of the first data item and the second data item includes: checking the consistency of the first data item and the aggregated second data item; and if the first data item is inconsistent with the second data item after the aggregation, the correctness check of the first data item and the second data item is not passed.

For example, for the consistency check on the first data item and the summarized second data item in the target data table of table 6, it is verified whether the sum corresponding to the details 1 to 5 is consistent with the value of the bill in the subject of the lowest payoff amount, and it can be seen from the data example of table 6 that the value of the summarized second data item of the details 1 to 5 of the lowest payoff amount is: (15+315+215+215+15) — 775, the value of the first data item with the lowest payoff amount in the bill: 775 is uniform.

An embodiment of data cancellation is described below with reference to fig. 5A and 5B.

There are two implementations of the above operation S402 a: operation S510 or operation S520.

In operation S510, according to the pre-configured offset rule and the target operation command, performing data offset on the second data item to obtain the offset bill data and the bill detail data.

In operation S520, data cancellation is performed on the first data item and the second data item according to a preset cancellation rule and the target operation command, so as to obtain cancelled bill data and bill detail data.

FIG. 5A schematically illustrates a detailed flow chart for performing data cancellation according to an embodiment of the present disclosure.

According to an embodiment of the present disclosure, the offset rule is associated with an identifier of a data processing scenario, and the offset rule includes: and under a candidate data processing scene, aiming at the preset punching and canceling sequence of the preset subjects and the first data processing logic of punching and canceling. The candidate data processing scenario includes: and processing data scenes corresponding to the target operation instructions.

In the operation S510, performing data cancellation on the second data item according to a pre-configured cancellation rule and the target operation instruction to obtain cancelled bill data and bill detail data, including: determining a target cancellation rule corresponding to the target operation instruction according to the identifier of the data processing scene associated with the cancellation rule, where the target cancellation rule includes: aiming at the target punching and pinning sequence of the preset subjects, punching and pinning a first target logic; and according to the first target logic, executing the following operations: s511, S512, and S513, as shown in fig. 5A.

In operation S511, it is determined that the target operation command corresponds to operation detail data of each preset subject based on the preset cancellation order.

In operation S512, the second data item is processed for offset based on the operation detail data, so as to obtain the bill detail data after offset.

In operation S513, the detailed billing data after the offset is summarized to obtain the billing data after the offset.

For example, the above operations S511 to S513 may be performed for the target data table illustrated in table 6. First, based on the preset cancellation order and the target operation command, the corresponding operation and the amount (in this case, the corresponding payment amount) are assigned to each preset subject in the target data table, and the operation detail data is obtained (corresponding to operation S511). Then, based on the operation detail data, the second data item is subjected to cancellation processing, that is, cancellation operation is performed using the numerical value of the second data item corresponding to each preset subject and the corresponding operation amount (taking the repayment operation as an example, here, the repayment detail data is subtracted from the second data item), so as to obtain the bill detail data after cancellation (corresponding to operation S512). And finally, summarizing the detailed bill data after the cancellation to obtain the detailed bill data after the cancellation, for example, summing up the detailed bill data after the cancellation of all the detailed bill data under the same preset subject to obtain the detailed bill data after the cancellation.

In this embodiment, the operation S403 for verifying the correctness of the cancelled bill data and the cancelled bill detail data includes: summarizing the operation detail data according to the preset subjects to obtain data to be punched and sold; based on the data to be punched and sold, punching and selling the first data item to obtain first bill data to be verified; determining whether the first bill data to be checked is consistent with the bill data after the cancellation; and under the condition that the first bill data to be verified is inconsistent with the bill data after the cancellation, the correctness verification of the bill data after the cancellation and the bill detail data is not passed.

In this embodiment, the result obtained by separately calculating the first data item for offset is compared with the bill data obtained by aggregating the bill detail data after offset, so as to be used as a necessary condition for checking the correctness of the bill data after offset and the bill detail data.

Fig. 5B schematically illustrates a detailed implementation flowchart for performing data cancellation according to another embodiment of the present disclosure.

According to another embodiment of the present disclosure, the offset rule is associated with an identifier of a data processing scenario, and the offset rule includes: and under a candidate data processing scene, aiming at the preset punching and canceling sequence of the preset subjects and a second data processing logic of punching and canceling. The candidate data processing scenario includes: and processing data scenes corresponding to the target operation instructions.

In the operation S520, the data offsetting of the first data item and the second data item according to the pre-configured offsetting rule and the target operation command to obtain the offset bill data and the bill detail data includes: determining a target cancellation rule corresponding to the target operation instruction according to the identifier of the data processing scene associated with the cancellation rule, where the target cancellation rule includes: the target punching and pinning sequence and the second target logic of punching and pinning aiming at the preset subjects; and according to the second target logic of the punching pin, executing the following operations: s521, S522, S523, and S524, as shown in fig. 5B.

In operation S521, it is determined that the target operation command corresponds to operation detail data of each preset subject based on the preset cancellation order.

In operation S522, the second data item is offset based on the operation detail data, and the post-offset billing detail data is obtained.

In operation S523, the operation detail data is summarized according to the preset subjects, so as to obtain the data to be punched and sold.

In operation S524, the first data item is processed for offset based on the to-be-offset data, so as to obtain the bill data after offset.

The sequence between the operations S522 and S523 is not limited, and the operations may be performed simultaneously or sequentially.

For example, the above operations S521 to S524 may be performed for the target data table illustrated in table 6. First, based on the preset cancellation order and the target operation order, the corresponding operation and the allocation of the amount (in this case, the corresponding payment amount) are performed for each preset subject in the target data table, and the operation detail data is obtained (corresponding to operation S521). Then, based on the above operation detail data, the second data item is subjected to cancellation processing, that is, the corresponding target operation instruction is subtracted from the value of the second data item corresponding to each preset subject, so as to obtain the cancelled bill detail data (corresponding to operation S522). Meanwhile, or before or after operation S522, the operation detail data in the same preset subject is summarized to obtain payment data in each preset subject, and the payment data in each preset subject is used as the to-be-distributed data (corresponding to operation S523). Finally, based on the data to be punched and sold, the first data item is punched and sold, for example, for a value of the first data item in the same preset subject, the value of the first data item is subtracted by the data to be punched and sold in the same preset subject, so as to obtain a punching and selling result in the preset subject, and the punching and selling results in all the preset subjects are the bill data after punching and selling (corresponding to operation S524).

In this embodiment, the operation S403 for verifying the correctness of the cancelled bill data and the cancelled bill detail data includes: summarizing the bill detail data after the cancellation to obtain second bill data to be verified; determining whether the second bill data to be checked is consistent with the bill data after the cancellation; and under the condition that the second bill data to be verified is inconsistent with the bill data after the cancellation, the correctness verification of the bill data after the cancellation and the bill detail data is not passed.

In this embodiment, the invoice data of the offset obtained by summarizing the invoice detail data after the offset is used, and the result obtained by separately calculating the first data item for the offset is compared with consistency, so as to be used as a necessary condition for checking the correctness of the invoice data after the offset and the invoice detail data.

According to an embodiment of the present disclosure, the target operation instruction includes one of: the method includes performing a payment due operation for a first amount, performing a payment refund operation for a second amount, performing a fee deduction operation for a third amount, or performing an advance payment operation for a fourth amount. The cost-reduced operation object includes at least one of: commission, day, penalty.

In the above operations S511 and S521, when the target operation command includes an operation of payment due for a first amount, determining that the target operation command corresponds to operation detail data of each preset department based on the target reimbursement order includes: and dividing the first amount into each preset subject in sequence based on the target reimbursement sequence to obtain operation detail data of the payment operation corresponding to each preset subject.

In the above operations S511 and S521, when the target operation command includes a refund operation for a second amount of money, determining that the target operation command corresponds to operation detail data of each preset subject based on the target reimbursement order includes: under the condition that the second amount is lower than the refund limit amount, sequentially dividing the second amount into each preset subject based on the target reimbursement sequence to obtain operation detail data of the refund operation corresponding to each preset subject; and under the condition that the second amount is larger than the refund limit, sequentially dividing the refund limit into each preset subject based on the target reimbursement sequence to obtain operation detail data of the refund operation corresponding to each preset subject.

In the operations S511 and S521, when the target operation command includes a charge deduction operation for performing a third amount of money, determining that the target operation command corresponds to operation detail data of each preset subject based on the target reimbursement order includes: under the condition that the third limit is lower than the charge reduction limit, sequentially dividing the third amount into each preset subject based on the target reimbursement sequence to obtain operation detail data of charge reduction and exemption operation corresponding to each preset subject; and under the condition that the third limit is larger than the charge reduction limit, sequentially dividing the charge reduction limit to each preset subject based on the target reimbursement sequence to obtain operation detail data of the charge reduction and exemption operation corresponding to each preset subject.

In the operations S511 and S521, when the target operation command includes an advance payment operation for a fourth amount, the advance payment operation is divided into a fee deduction operation and a payment operation, and the fee deduction operation is performed first and then the payment operation is performed. Determining that the target operation instruction corresponds to operation detail data of each preset branch objective based on the target cancellation sequence, wherein the determining comprises the following steps: determining the amount of the non-payment waiting corresponding to the advance payment operation; deducting the amount of non-occurrence pending payment from the fourth amount to obtain an actual payment amount; and on the basis of the target cancellation sequence, sequentially dividing the amount of money which is not yet to be paid and the actual payment amount into each preset subject, and correspondingly obtaining first operation detail data and second operation detail data of the expense reduction operation and the payment operation corresponding to each preset subject.

In the operations S512 and S522, for an advance payment operation, the obtaining the billing detail data after the offset by performing the offset processing on the second data item based on the operation detail data includes: performing offset processing under cost reduction and exemption operation on the second data item based on the first operation detail data to obtain a first detail result; and performing punching and canceling processing under the payment operation on the first detail result based on the second operation detail data to obtain the bill detail data after punching and canceling.

In a specific embodiment, for example, the target offset sequence in the repayment scenario is: the method comprises the steps of firstly carrying out cancellation on the periodic commission, the daily interest and the penalty in sequence, and then carrying out cancellation on the cash withdrawal principal, the bill periodic principal, the order periodic principal and the non-periodic principal in sequence. The billing data and the billing statement data after the offset are obtained by performing the above-described operations S511 to S513, and the processes are shown in tables 7 and 8.

Fig. 6 schematically shows a flow chart of a method of data processing according to another embodiment of the present disclosure.

On the basis of the foregoing embodiment, the method for processing data provided by the embodiment of the present disclosure includes, in addition to the above operations S201 to S204, the following operation S601: and configuring a punching rule and a checking rule. For the sake of simplicity of representation, only operation S601 and operation S204 are illustrated in fig. 6. Referring to fig. 6, the above-described operation S601 is performed before the operation S204. In other embodiments, the above operation S601 is performed before operations S201 to S204.

Fig. 7 schematically shows a detailed implementation flowchart of operation S601 according to an embodiment of the present disclosure.

According to an embodiment of the present disclosure, referring to fig. 7, the operation S601 of configuring the cancellation rule and the verification rule includes the following operations: s701, S702, and S703.

In operation S701, rule configuration information for a candidate data processing scenario including a data processing scenario of the to-be-returned bill is received, where the rule configuration information includes: the method comprises the steps of canceling rule information, verifying rule information and generating a script type.

In the implementation scenario of operation S701, operation S701 may be performed by the terminal device. The operation S701 may be executed by the server, and the rule configuration information may be configured by the user on the terminal device, and the terminal device transmits the rule configuration information of the user to the server, and receives the rule configuration information on the server side.

In operation S702, semantic checking is performed on the rule configuration information.

For example, a value is taken from an object in which the property should exist. For example, if a predetermined subject is used in the predetermined offset sequence, the predetermined subject must be defined.

In operation S703, if the rule configuration information passes semantic verification, an offset rule code and a verification rule code corresponding to the generated script type are generated according to the generated script type, where the offset rule code and the verification rule code are configured as an offset rule and a verification rule.

Fig. 8 schematically shows a flow chart of a method of data processing according to a further embodiment of the present disclosure.

On the basis of the foregoing embodiment, the method for processing data provided by the embodiment of the present disclosure includes, in addition to the above operations S201 to S204 and S601, operation S801: and loading the punching rule and the verification rule. For the sake of simplicity of representation, only operation S601, operation S204, and operation S801 are illustrated in fig. 7. Referring to fig. 8, the above-described operation S801 is performed after operation S601 and before operation S204. In the implementation scenario of operation S801, operation S801 may be executed by the terminal device or the server.

Fig. 9 schematically shows a detailed implementation flowchart of operation S801 according to an embodiment of the present disclosure.

According to an embodiment of the present disclosure, referring to fig. 9, the operation S801 of loading the cancellation rule and the verification rule includes the following operations: s901, S902, and S903.

In operation S901, the generation script types of the offset rule code and the verification rule code are obtained.

In operation S902, a target loader to be started is determined according to the generated script type, where the target loader is matched with the generated script type.

In operation S903, the target loader is started to load the cancellation rule code and the verification rule code.

According to an embodiment of the present disclosure, in operation S903, the method may further include: and determining whether the loading of the offset rule codes and the check rule codes is finished.

A second exemplary embodiment of the present disclosure provides an apparatus for data processing.

Fig. 10 schematically shows a block diagram of a data processing apparatus according to an embodiment of the present disclosure.

Referring to fig. 10, an apparatus 1000 for data processing provided by an embodiment of the present disclosure includes: a request receiving module 1001, a data obtaining module 1002, a data converting module 1003 and a data processing module 1004.

The request receiving module 1001 is configured to receive a data operation request, where the data operation request includes: target operating instructions for the bill to be returned.

The data obtaining module 1002 is configured to obtain the to-be-paid account list and the to-be-processed data in the bill particulars of the to-be-paid account list when the data operation request is received.

The data conversion module 1003 is configured to convert the to-be-processed data according to a preset subject, and correspondingly obtain the to-be-returned bill and the bill detail, where the bill detail is matched with the first data item and the second data item of the preset subject, respectively. The data conversion module 1003 may include functional modules or sub-modules for implementing the operations S301 to S304.

The data processing module 1004 is configured to perform data cancellation and verification on the first data item and the second data item according to the target operation instruction and a cancellation rule and a verification rule configured in advance, so as to obtain a result after data processing. The data processing module 1004 may include functional modules or sub-modules for implementing the operations S401, S402a, S402b, S403, S404a, and S404 b.

The apparatus 1000 may be a terminal device or a server. In the terminal device, the data conversion module 1003 and the data processing module 1004 may be functional modules in a rule engine, and the rule engine may be embedded in an application program (for example, a financial application) installed in the apparatus and used for processing a data operation request.

According to an embodiment of the present disclosure, the apparatus 1000 further includes the following modules: a configuration module and a loading module.

The configuration module is used for configuring the punching rule and the verification rule module. The configuration module includes a functional module or a sub-module for implementing operations S701 to S703.

The loading module is used for loading the punching rule and the verification rule. The loading module includes a functional module or a sub-module for implementing operations S901 to S903.

Any number of the request receiving module 1001, the data obtaining module 1002, the data converting module 1003, the data processing module 1004, the configuring module and the loading module may be combined into one module to be implemented, or any one of the modules may be split into a plurality of modules. Alternatively, at least part of the functionality of one or more of these modules may be combined with at least part of the functionality of the other modules and implemented in one module. At least one of the request receiving module 1001, the data obtaining module 1002, the data converting module 1003, the data processing module 1004, the configuring module and the loading module may be at least partially implemented as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented by hardware or firmware in any other reasonable manner of integrating or packaging a circuit, or implemented by any one of three implementations of software, hardware and firmware, or an appropriate combination of any several of them. Alternatively, at least one of the request receiving module 1001, the data obtaining module 1002, the data converting module 1003, the data processing module 1004, the configuring module and the loading module may be at least partially implemented as a computer program module, which when executed, may perform a corresponding function.

A third exemplary embodiment of the present disclosure provides an electronic apparatus.

Referring to fig. 11, an electronic device 1100 provided in the embodiment of the present disclosure includes a processor 1101, a communication interface 1102, a memory 1103, and a communication bus 1104, where the processor 1101, the communication interface 1102, and the memory 1103 complete communication with each other through the communication bus 1104; a memory 1103 for storing a computer program; the processor 1101 is configured to implement the data processing method described above when executing the program stored in the memory.

A fourth exemplary embodiment of the present disclosure also provides a computer-readable storage medium. The above-mentioned computer-readable storage medium has stored thereon a computer program which, when executed by a processor, implements the method of data processing as described above.

The computer-readable storage medium may be contained in the apparatus/device described in the above embodiments; or may be present alone without being assembled into the device/apparatus. The computer-readable storage medium carries one or more programs which, when executed, implement the method according to an embodiment of the disclosure.

According to embodiments of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, for example but is not limited to: 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), 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 disclosure, 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.

It is noted that, in this document, relational terms such as "first" and "second," and the like, may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.

The foregoing are merely exemplary embodiments of the present disclosure, which enable those skilled in the art to understand or practice the present disclosure. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the disclosure. Thus, the present disclosure is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method of data processing, comprising:

receiving a data operation request, the data operation request comprising: target operating instructions for the bill to be returned;

under the condition that the data operation request is received, acquiring the to-be-paid bill and to-be-processed data in bill particulars of the to-be-paid bill;

converting the data to be processed according to a preset subject, and respectively and correspondingly obtaining the bill to be returned and the bill detail which are matched with a first data item and a second data item of the preset subject; and

and performing data cancellation and verification on the first data item and the second data item according to the target operation instruction and a preset cancellation rule and a preset verification rule to obtain a result after data processing.

2. The method of claim 1, wherein the performing data cancellation and verification on the first data item and the second data item according to the target operation instruction and a pre-configured cancellation rule and verification rule to obtain a result after data processing comprises:

checking the correctness of the first data item and the second data item according to a pre-configured checking rule;

under the condition that the correctness of the first data item and the second data item passes the verification, performing data punching and canceling on the second data item or the first data item and the second data item according to a pre-configured punching and canceling rule and the target operation instruction to obtain punched and canceled bill data and bill detail data;

according to the verification rule, verifying the correctness of the bill data and the bill detail data after the cancellation;

and under the condition that the correctness of the bill data and the bill detail data after the cancellation passes the verification, taking the bill data and the bill detail data after the cancellation as the result after data processing.

3. The method of claim 2, wherein the offset rule is associated with an identification of a data processing scenario, and wherein the offset rule comprises: in a candidate data processing scenario, a preset cancellation sequence for the preset subjects and a first data processing logic for cancellation, where the candidate data processing scenario includes: a data processing scene corresponding to the target operation instruction;

the data cancellation of the second data item according to the pre-configured cancellation rule and the target operation instruction to obtain cancelled bill data and bill detail data includes:

determining a target cancellation rule corresponding to the target operation instruction according to the identifier of the data processing scene associated with the cancellation rule, wherein the target cancellation rule comprises: aiming at the target punching and pinning sequence of the preset subjects, punching and pinning a first target logic;

according to the first target logic, performing the following operations:

determining that the target operation instruction corresponds to operation detail data of each preset department based on the target punching and canceling sequence;

based on the operation detail data, carrying out cancellation processing on the second data item to obtain bill detail data after cancellation; and

and summarizing the detailed bill data after the punching and the marketing to obtain the bill data after the punching and the marketing.

4. The method of claim 3, wherein said verifying the correctness of said post-reimbursement billing data and billing statement data comprises:

summarizing the operation detail data according to the preset subjects to obtain data to be punched and sold;

based on the data to be punched and sold, punching and selling the first data item to obtain first bill data to be verified;

determining whether the first bill data to be checked is consistent with the bill data after offset or not;

and under the condition that the first bill data to be verified is inconsistent with the bill data after the cancellation, the correctness verification of the bill data after the cancellation and the bill detail data is not passed.

5. The method of claim 2, wherein the offset rule is associated with an identification of a data processing scenario, and wherein the offset rule comprises: in a candidate data processing scenario, a preset cancellation sequence for the preset subject and a second data processing logic for cancellation, where the candidate data processing scenario includes: a data processing scene corresponding to the target operation instruction;

the data cancellation of the first data item and the second data item according to the pre-configured cancellation rule and the target operation instruction to obtain the cancelled bill data and bill detail data includes:

determining a target cancellation rule corresponding to the target operation instruction according to the identifier of the data processing scene associated with the cancellation rule, wherein the target cancellation rule comprises: aiming at the target punching and pinning sequence of the preset subjects, punching and pinning a second target logic;

according to the second target logic, performing the following operations:

based on the operation detail data, carrying out cancellation processing on the second data item to obtain bill detail data after cancellation;

summarizing the operation detail data according to the preset subjects to obtain data to be punched and sold; and

and carrying out punching and canceling processing on the first data item based on the data to be punched and canceled to obtain the bill data after punching and canceling.

6. The method of claim 5, wherein said verifying the correctness of said post-reimbursement billing data and billing statement data comprises:

summarizing the bill detail data after the cancellation to obtain second bill data to be verified;

determining whether the second bill data to be checked is consistent with the bill data after offset;

and under the condition that the second bill data to be verified is inconsistent with the bill data after the cancellation, the correctness verification of the bill data after the cancellation and the bill detail data is not passed.

7. The method of any of claims 3-6, wherein the target operational instruction comprises at least one of: carrying out a payment due operation of a first amount, carrying out a refund operation of a second amount and carrying out a fee deduction operation of a third amount;

wherein the determining that the target operation instruction corresponds to the operation detail data of each preset subject based on the target cancellation sequence includes at least one of the following operations:

on the basis of the target reimbursement sequence, sequentially dividing the first amount into each preset subject to obtain operation detail data of the repayment operation corresponding to each preset subject; alternatively, the first and second electrodes may be,

under the condition that the second amount is lower than the refund limit amount, sequentially dividing the second amount into each preset subject based on the target reimbursement sequence to obtain operation detail data of the refund operation corresponding to each preset subject; under the condition that the second amount is larger than the refund limit amount, sequentially dividing the refund limit amount into each preset subject based on the target reimbursement sequence to obtain operation detail data of the refund operation corresponding to each preset subject; alternatively, the first and second electrodes may be,

under the condition that the third limit is lower than the charge reduction limit, sequentially dividing the third amount into each preset subject based on the target reimbursement sequence to obtain operation detail data of charge reduction and exemption operations corresponding to each preset subject; and under the condition that the third limit is larger than the charge reduction limit, sequentially dividing the charge reduction limit to each preset subject based on the target reimbursement sequence to obtain operation detail data of the charge reduction and exemption operation corresponding to each preset subject.

8. The method of any of claims 3-6, wherein the target operation instruction comprises: carrying out advanced repayment operation of a fourth amount;

wherein the determining that the target operation instruction corresponds to the operation detail data of each preset branch objective based on the target cancellation sequence comprises:

determining the amount of the non-occurrence to-be-paid money corresponding to the advance payment operation; deducting the amount which is not yet paid from the fourth amount to obtain an actual payment amount; on the basis of the target cancellation sequence, sequentially dividing the amount of money not yet to be paid and the actual payment amount into each preset subject, and correspondingly obtaining first operation detail data and second operation detail data of a expense deduction operation and a payment operation corresponding to each preset subject;

aiming at the advance repayment operation, the canceling processing is carried out on the second data item based on the operation detail data to obtain the bill detail data after canceling, and the method comprises the following steps: based on the first operation detail data, performing cancellation processing on the second data item under cost reduction and exemption operation to obtain a first detail result; and based on the second operation detail data, performing punching and canceling processing under the repayment operation on the first detail result to obtain the bill detail data after punching and canceling.

9. The method of any of claims 2-6, wherein the checking the correctness of the first data item and the second data item comprises:

checking the consistency of the first data item and the summarized second data item;

and in the case that the first data item is inconsistent with the second data item after the first data item and the second data item are collected, the correctness check of the first data item and the second data item is not passed.

10. The method according to claim 1, wherein the converting the data to be processed according to a preset subject to obtain the bill to be returned and the bill detail respectively corresponding to a first data item and a second data item of the preset subject comprises:

acquiring a target data table template corresponding to the data processing scene of the account to be returned from pre-constructed data table templates aiming at different data processing scenes;

obtaining preset subjects according to the column information of the target data table template;

converting the data to be processed in the bill to be returned to obtain first column data of each preset subject corresponding to the same data row in the target data table template, wherein the first column data is a first data item;

and converting the data to be processed in the current bill particulars to obtain second lines of data of each preset department corresponding to the same data row in the target data table template, wherein the second lines of data are second data items.

11. The method of claim 1, further comprising: configuring a punching rule and a verification rule; the configuration of the offset rule and the verification rule comprises the following steps:

receiving rule configuration information for candidate data processing scenarios, wherein the candidate data processing scenarios include data processing scenarios of the to-be-returned bill, and the rule configuration information includes: the method comprises the steps of canceling rule information, verifying rule information and generating a script type;

performing semantic verification on the rule configuration information;

and under the condition that the rule configuration information passes semantic verification, generating an offset rule code and a verification rule code corresponding to the generated script type according to the generated script type, wherein the offset rule code and the verification rule code are used as configured offset rules and verification rules.

12. The method of claim 11, further comprising: loading a punching rule and a verification rule; the loading cancellation rule and the verification rule comprise:

acquiring the generation script types of the offset rule codes and the verification rule codes;

determining a target loader to be started, which is matched with the type of the generated script, according to the type of the generated script;

starting the target loader to load the offset rule code and the check rule code.

13. An apparatus for data processing, comprising:

a request receiving module, configured to receive a data operation request, where the data operation request includes: target operating instructions for the bill to be returned;

the data acquisition module is used for acquiring the to-be-processed data in the bill particulars of the bill to be returned and the bill to be returned under the condition that the data operation request is received;

the data conversion module is used for converting the data to be processed according to a preset subject, and correspondingly obtaining the bill to be returned and the bill detail which are matched with a first data item and a second data item of the preset subject respectively; and

and the data processing module is used for carrying out data cancellation and verification on the first data item and the second data item according to the target operation instruction and a preset cancellation rule and a preset verification rule to obtain a result after data processing.

14. An electronic device is characterized by comprising a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory are communicated with each other through the communication bus;

a memory for storing a computer program;

a processor for implementing the method of any one of claims 1 to 12 when executing a program stored on a memory.

15. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the method of any one of claims 1-12.