Back-to-back settlement checking method and device, storage medium and server

Abstract

The embodiment of the invention discloses a back-to-back settlement checking method and device, a storage medium and terminal equipment, and relates to the field of data checking. After the power plant side generates the electric charge billing data according to the mask settlement data, the server immediately performs consistency check on the target field value in the original settlement data and the corresponding field value in the power plant billing data. Compared with a traditional method of performing consistency check afterwards, the method can find and solve the problem of data inconsistency earlier, thereby reducing the workload of processing data inconsistency in a subsequent settlement link on the whole, and reducing the complexity of settlement work.

Description

Technical Field

[0001] The present application relates to the field of data verification, and in particular to a back-to-back settlement verification method, device, storage medium and server. Background Art

[0002] With the continuous expansion and deepening of the power industry, the purchase and sales business structure of power grid companies and power generation companies has become increasingly diversified, and the accounting system of electricity charges and various subsidies has become complicated and involves a huge amount of funds. In the electricity bill settlement process, the power grid company as the buyer and the power generation company as the seller occasionally disagree on the calculation results of the electricity charges and subsidy amounts, which directly leads to inconsistencies between the invoice amount issued by the power plant and the actual settlement amount of the power grid. Given the urgency of the plant-grid settlement cycle and the wide distribution of power generation companies, it is often difficult to refund and re-issue invoices in a timely manner, forcing power grid companies to face and deal with these amount differences every month in financial processing.

[0003] When such business volume is large or occurs frequently, the complexity of the settlement business processing process of power grid enterprises increases significantly, which in turn restricts the overall efficiency of electricity bill settlement. In addition, in the subsequent electricity bill review, if the specific reasons for the historical settlement differences are to be traced, if they rely on incomplete manual records, it will greatly hinder the accurate analysis of the processing situation at the time, thereby weakening the accuracy and work efficiency of the power plant and grid electricity bill settlement as a whole.

[0004] In view of this, it is urgent to take effective measures to improve the level of automation of electricity bill settlement and enhance the accuracy of data recording and tracking, so as to optimize the settlement process, reduce human errors, improve the timeliness and accuracy of electricity bill settlement, and ensure the efficient and smooth operation of electricity bill settlement in power plants and grids. Summary of the invention

[0005] The embodiments of the present application provide a back-to-back settlement verification method, device, storage medium and server, which can solve the problems of low settlement verification efficiency and poor accuracy in the prior art. The technical solution is as follows:

[0006] In a first aspect, an embodiment of the present application provides a back-to-back settlement verification method, the method comprising:

[0007] Receive original settlement data from the power grid side;

[0008] Masking the field value of the target field in the original settlement data according to a preset masking rule to obtain masked settlement data;

[0009] Push the masked settlement data to the power plant side for display;

[0010] Acquire electricity billing data generated by the power plant side according to the target field in the masked settlement data;

[0011] Performing a consistency check on a first field value of the target field in the original settlement data and a second field value of the target field in the power plant invoicing data;

[0012] If the check result is passed, a check success message is synchronously sent to the grid side and the power plant side, and the masked settlement data displayed to the power plant side is updated to the original settlement data;

[0013] If the check result is not passed, the power plant is instructed to upload new original settlement data.

[0014] In a second aspect, an embodiment of the present application provides a back-to-back settlement verification device, the device comprising:

[0015] An acquisition unit, used for receiving original settlement data from the power grid side;

[0016] A masking unit, configured to perform masking processing on the field value of the target field in the original settlement data according to a preset masking rule to obtain masked settlement data;

[0017] A push unit, used to push the mask settlement data to the power plant side for display;

[0018] The acquisition unit is further used to acquire the electricity billing data generated by the power plant side according to the target field in the masked settlement data;

[0019] A checking unit, configured to perform a consistency check on a first field value of the target field in the original settlement data and a second field value of the target field in the power plant invoicing data;

[0020] The push unit is further configured to, if the check result is passed, synchronously send a check success message to the grid side and the power plant side, and update the masked settlement data displayed to the power plant side to the original settlement data;

[0021] The instructing unit is used to instruct the power plant to upload new original settlement data if the inspection result is not passed.

[0022] In a third aspect, an embodiment of the present application provides a computer storage medium, wherein the computer storage medium stores a plurality of instructions, wherein the instructions are suitable for being loaded by a processor and executing the above-mentioned method steps.

[0023] In a fourth aspect, an embodiment of the present application provides a server, which may include: a processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the above-mentioned method steps.

[0024] The beneficial effects brought about by the technical solutions provided by some embodiments of the present application include at least:

[0025] By implementing a refined data processing and verification process, and innovatively adopting a back-to-back verification method to put data consistency checks in front, we have achieved a significant improvement in settlement efficiency and a rapid operation of power plant operating capital flows, bringing significant optimization and benefits to the settlement work between power plants and power grids. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0027] Figure 1 It is a schematic diagram of the network architecture provided by the embodiment of the present application;

[0028] Figure 2 It is a flowchart of a back-to-back settlement verification method provided in an embodiment of the present application;

[0029] Figure 3 It is a structural schematic diagram of a back-to-back settlement verification device provided by the present application;

[0030] Figure 4 It is a structural diagram of a server provided by this application. DETAILED DESCRIPTION

[0031] In order to make the objectives, technical solutions and advantages of the present application more clear, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings.

[0032] It should be noted that the back-to-back settlement verification method provided in the present application is generally executed by a server, and correspondingly, the back-to-back settlement verification device is generally set in the server.

[0033] Figure 1 An exemplary system architecture that can be applied to the back-to-back settlement verification method or the back-to-back settlement verification device of the present application is shown.

[0034] like Figure 1As shown, the system architecture may include: a grid-side terminal 101, a server 102, and a power plant-side terminal 103. The grid-side terminal 101, the power plant-side terminal 103, and the server 102 may communicate through a network, and the network is used as a medium for providing communication links between the above-mentioned units. The network may include various types of wired communication links or wireless communication links, for example: a wired communication link includes an optical fiber, a twisted pair, or a coaxial cable, etc., and a wireless communication link includes a Bluetooth communication link, a wireless fidelity (WIreless-FIdelity, Wi-Fi) communication link, or a microwave communication link, etc.

[0035] Among them, the grid-side terminal 101 is a terminal device deployed on the grid side, and the power plant-side terminal 103 is a terminal device deployed on the power plant side.

[0036] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be used as required.

[0037] The following will be combined with the attached Figure 2 , the back-to-back settlement verification method provided by the embodiment of the present application is described in detail. Among them, the back-to-back settlement verification device in the embodiment of the present application can be Figure 1 The server shown.

[0038] See also Figure 2 , which is a flow chart of a back-to-back settlement verification method provided in the present application embodiment. Figure 2 As shown, the method of the embodiment of the present application may include the following steps:

[0039] S201. The server receives original settlement data from the power grid side.

[0040] The server first configures the network interface (such as TCP / IP protocol, HTTP / HTTPS protocol, etc.) for communication with the power grid side, and sets the port for receiving data. The server listens to the configured port and waits for the power grid side to send the original settlement data. When receiving the data, the server parses the original settlement data according to the predefined format (such as XML, JSON, CSV, etc.) and converts it into the data structure inside the server for subsequent processing. The parsed original settlement data is stored in the server's database or cache for subsequent use.

[0041] S202. The server performs mask processing on the field value of the target field in the original settlement data according to a preset mask rule to obtain masked settlement data.

[0042] Among them, a set of masking rules are defined inside the server, which include which fields need to be masked and the masking method (such as replacing some characters with asterisks *, using encryption algorithms, etc.). According to the defined masking rules, select the target fields that need to be masked from the original settlement data. Mask the selected target fields and replace or encrypt the field values ​​according to the masking rules. Replace the processed field values ​​back to the corresponding positions in the original settlement data to generate masked settlement data. The number of target fields can be one or more, and the target fields include: unit number, project number, settlement electricity, electricity price, electricity fee, and subsidy amount.

[0043] S203. The server pushes the masked settlement data to the power plant for display.

[0044] The server configures the network interface and port for communication with the power plant. The mask settlement data is encapsulated into a format suitable for transmission (such as JSON, XML, etc.). The encapsulated mask settlement data is pushed to the power plant through the configured network interface and port. The confirmation message from the power plant is received to ensure that the mask settlement data has been successfully transmitted and displayed.

[0045] S204: The server obtains electricity billing data generated by the power plant side according to the target field in the masked settlement data.

[0046] The server monitors the port where the power plant uploads the electricity billing data, and receives the electricity billing data generated by the power plant according to the masked settlement data. The received electricity billing data is parsed to extract key information (such as invoice number, amount, invoicing date, etc.). The parsed electricity billing data is stored in the server's database for subsequent processing.

[0047] S205. The server performs a consistency check on the first field value of the target field in the original settlement data and the second field value of the target field in the power plant invoicing data.

[0048] The server extracts the first field value of the target field from the original settlement data, and extracts the second field value of the corresponding target field from the electricity billing data. The extracted field values ​​are compared to check whether they are consistent. This may include numerical comparison, string comparison, etc. The check result (pass / fail) is recorded in the server log, and the relevant field values ​​are saved for subsequent analysis.

[0049] In some embodiments of the present application, an absolute value deviation or a relative value error is used to perform consistency check.

[0050] The specific process includes: the server extracts the first field value of the target field from the original settlement data, which is recorded as A. The server extracts the second field value of the corresponding target field from the power plant invoicing data, which is recorded as B.

[0051] Calculate the absolute value deviation: Calculate the difference between A and B, that is, the absolute value deviation |AB|. Set an absolute value deviation threshold (for example, set it to a fixed value or percentage according to business requirements). If |AB| is less than or equal to the absolute value deviation threshold, the field values ​​are considered consistent and the check passes; otherwise, the check fails.

[0052] Calculate relative value deviation: If the business requirements are more stringent, you can consider using relative value deviation. The formula for calculating relative value deviation is |(AB) / A| (or |(AB) / B|, depending on which value is used as the benchmark) to obtain the relative deviation value. Set a relative value deviation threshold (for example, set it to a certain percentage based on business requirements). If the relative deviation value is less than or equal to the relative value deviation threshold, the field values ​​are considered consistent and the check passes; otherwise, the check fails.

[0053] Based on the above calculation results, determine whether the field values ​​are consistent. If consistent, record the result of passing the check and prepare for subsequent steps (such as S206). If inconsistent, record the result of failing the check and prepare for error handling (such as S207). Regardless of the inspection results, the inspection process, results, and related field values ​​should be recorded in the server log. The log record should include information such as timestamp, inspection type (absolute value deviation or relative value deviation), field name, field value A, field value B, error or deviation value, threshold, and inspection results.

[0054] Further, in some embodiments of the present application, the field value of the summary field in the original settlement data is compared with the field value of the summary field in the power plant invoicing data to see whether they are equal;

[0055] If not, continue to check whether the field values ​​of each detail field in the original settlement data and the power plant invoicing data are equal;

[0056] If not, a check result message is synchronously sent to the power plant side and the grid side.

[0057] Among them, the server extracts the field value of the summary field from the original settlement data, recorded as Sum_A. Extract the field value of the corresponding summary field from the power plant invoicing data, recorded as Sum_B. Compare whether Sum_A and Sum_B are equal. If equal, record the result of the summary field comparison and prepare for subsequent steps (such as S206). If not equal, continue to compare the detail fields.

[0058] If the summary field comparison fails, the server will extract the field values ​​of each detail field in the original settlement data and the power plant invoicing data. Compare each pair of detail fields (recorded as Detail_A_i and Detail_B_i, where i represents the index of the detail field). Compare Detail_A_i and Detail_B_i for equality. If all detail fields are equal, record the result that the detail field comparison passed (although the summary fields do not match, this is rare and may require further manual review). If there is any detail field mismatch, record the result that the detail field comparison failed. Based on the comparison results of the summary field and the detail field, determine the final consistency check result. If the summary field and all detail fields match, the check passes. If the summary field does not match and at least one detail field does not match, the check fails. Regardless of the check result, the check process, results, and related field values ​​should be recorded in the server log. The log record should include information such as timestamp, check type (summary field comparison and / or detail field comparison), field name, field value (recorded separately for summary fields and detail fields), comparison results, etc.

[0059] S206. If the inspection result is passed, the server sends a synchronous inspection success message to the grid side and the power plant side, and updates the masked settlement data displayed to the power plant side to the original settlement data.

[0060] The server sends a message of successful synchronization check to the power grid side and the power plant side. For the masked settlement data displayed on the power plant side, the server updates it to the original settlement data and re-pushes it to the power plant side for display.

[0061] S207: If the inspection result is failed, the server instructs the power plant to upload new original settlement data.

[0062] Among them, an instruction message is sent to the power plant side, requiring it to upload new original settlement data. The server continues to listen to the port for uploading new data on the power plant side, waiting to receive new original settlement data. After receiving the new data, the server repeats the processing flow from step S202 until the inspection result is passed.

[0063] In some embodiments of the present application, it also includes:

[0064] If the number of times the check result fails exceeds the number threshold, a check failure message is sent to the power plant side, instructing the power plant side to stop uploading new original settlement data.

[0065] Among them, the consistency check in S205 is performed according to the previous steps, including summary field comparison and (if necessary) detail field comparison. Each time the consistency check fails, the server records a failure in an internal counter or database. The recorded information should include the timestamp of the failure, the checked field (summary or detail), the mismatched field value, and any relevant error code or message. The server checks whether the number of recorded failures exceeds the preset number threshold regularly (such as after each check, daily, weekly, etc.) or when a new check result is failed. If the number of failures does not exceed the threshold, the normal process continues, which may include sending an inspection result message to the power plant side and allowing it to upload new original settlement data for re-checking. If the number of failures exceeds the threshold, execute the next step.

[0066] When the number of failures exceeds the threshold, the server sends a verification failure message to the power plant. The message should include the reason and instructions to stop uploading new data. The message can also include recommended measures for the power plant to take, such as checking its internal system, rechecking the data, etc.

[0067] After the verification failure message is sent, manual intervention is required to solve the problem. The server can generate a task message to notify relevant personnel (such as data administrators, technical support personnel, etc.) for further investigation and processing. Relevant personnel can contact the power plant side to understand the cause of the data inconsistency and provide technical support or guidance. Once the problem is resolved and the power plant side can provide accurate data, the power plant side is required to submit a verified and accurate original settlement data and pass the server's re-check. Through the above steps, the server can more effectively manage the failure of data consistency checks, prevent excessive failed attempts from burdening the system, and ensure the accuracy and integrity of the data. At the same time, through the manual intervention mechanism, the reliability and maintainability of the system are improved.

[0068] In some embodiments of the present application, the method further includes: the server receiving a configuration instruction from the power grid side, and configuring a corresponding mask rule and a consistency check rule for the target field based on the configuration instruction.

[0069] Among them, the server receives the configuration instructions from the power grid side through a secure channel (such as HTTPS, SSH, etc.). The configuration instructions can be in text format (such as JSON, XML), binary format or messages of a specific protocol. The server parses the received configuration instructions and extracts key information therein. The key information includes the identifier of the target field (such as field name, field ID, etc.), mask rules (such as which characters need to be hidden, replaced or encrypted), and consistency check rules (such as comparison method, threshold, etc.). The server verifies the legality and validity of the configuration instructions. Check whether the instruction format is correct and whether it contains necessary fields and information. Verify whether the rules in the instructions meet the requirements and restrictions of the system. According to the parsed and verified configuration instructions, the server configures the corresponding mask rules and consistency check rules for the target field. The mask rules are stored in an internal database or configuration file for application during data processing. The consistency check rules are stored in an internal database or configuration file for application during data consistency check. The server records relevant information about the reception, parsing, verification and configuration process of the configuration instructions. The log record should include information such as timestamp, content of the configuration instruction, identifier of the target field, configured mask rules and consistency check rules, and configuration results. The server sends a configuration success message to the grid side to confirm that the configuration instructions have been correctly received and processed. If the configuration fails, a configuration failure message is sent to the grid side, and the reasons for the failure and possible solutions are provided. Once the configuration is successful, the server will apply new mask rules and consistency check rules to the target field. During the data processing process, the server will hide, replace or encrypt the value of the target field according to the mask rules. During the data consistency check process, the server will compare and verify the value of the target field according to the consistency check rules. Through the above steps, the server is able to receive configuration instructions from the grid side, and configure the corresponding mask rules and consistency check rules for the target field according to these instructions. This enhances the flexibility and configurability of the system, allowing the system to be customized and optimized according to actual needs. At the same time, by recording configuration logs and notifying relevant parties, the traceability and transparency of the system are improved.

[0070] The embodiments of the present application specifically include the following beneficial effects:

[0071] By implementing a series of refined data processing and verification processes, the settlement work between the power plant and the power grid has been significantly optimized. Specifically, as the center of data processing and verification, the server first receives the original settlement data from the power grid side, and masks the field values ​​of the target fields according to the preset masking rules to protect sensitive information while pushing the processed masked settlement data to the power plant side for display. This step not only ensures the security of the data, but also facilitates the subsequent electricity billing work on the power plant side.

[0072] The innovative back-to-back verification method is adopted to put the data consistency check in advance. That is, after the power plant generates electricity billing data based on the masked settlement data, the server immediately performs a consistency check on the target field value in the original settlement data and the corresponding field value in the power plant billing data. Compared with the traditional post-conclusion consistency check, this method can detect and solve data inconsistency problems earlier, thereby reducing the workload of handling data inconsistencies in the subsequent settlement links as a whole and reducing the complexity of settlement work.

[0073] Through the pre-check of data consistency, this technical solution also fundamentally solves the data quality problem and ensures the accuracy and reliability of the settlement data between the power plant and the power grid. This not only saves the settlement time between the power plant and the power grid, but also significantly improves the efficiency of the plant-grid settlement. Furthermore, a faster settlement process means that the power plant can receive the settlement electricity fee faster, thereby ensuring the rapid operation of the power plant's operating capital flow, which is of great significance to the stable operation and sustainable development of the power plant.

[0074] The following is an embodiment of the device of the present application, which can be used to execute the embodiment of the method of the present application. For details not disclosed in the embodiment of the device of the present application, please refer to the embodiment of the method of the present application.

[0075] See also Figure 3 , which shows a schematic diagram of the structure of a back-to-back settlement verification device provided by an exemplary embodiment of the present application, hereinafter referred to as device 3. The device 3 can be implemented as all or part of the server through software, hardware or a combination of both. The device 3 includes: an acquisition unit 301, a mask unit 302, a push unit 303, a check unit 304, and an indication unit 305.

[0076] The acquisition unit 301 is used to receive the original settlement data from the power grid side;

[0077] The masking unit 302 is used to perform masking processing on the field value of the target field in the original settlement data according to a preset masking rule to obtain masked settlement data;

[0078] A push unit 303 is used to push the masked settlement data to the power plant side for display;

[0079] The acquisition unit 301 is further used to acquire the electricity billing data generated by the power plant side according to the target field in the masked settlement data;

[0080] A checking unit 304, configured to perform a consistency check on a first field value of the target field in the original settlement data and a second field value of the target field in the power plant invoicing data;

[0081] The push unit 303 is further configured to, if the check result is passed, send a check success message to the grid side and the power plant side synchronously, and update the masked settlement data displayed to the power plant side to the original settlement data;

[0082] The instructing unit 305 is used to instruct the power plant to upload new original settlement data if the inspection result is not passed.

[0083] In one or more possible embodiments, back-to-back data comparison is performed in the form of masked settlement data.

[0084] In one or more possible embodiments, the consistency check is performed using an absolute value deviation or a relative value deviation.

[0085] In one or more possible embodiments, the target field includes a summary field and a plurality of detail fields;

[0086] Comparing whether the field value of the summary field in the original settlement data is equal to the field value of the summary field in the power plant invoicing data;

[0087] If not, continue to check whether the field values ​​of each detail field in the original settlement data and the power plant invoicing data are equal;

[0088] If not, a check result message is synchronously sent to the power plant side and the grid side.

[0089] In one or more possible embodiments, it further includes:

[0090] The retransmission unit is used to send a verification failure message to the power plant side if the number of times the inspection result fails exceeds a threshold, instructing the power plant side to stop uploading new original settlement data.

[0091] In one or more possible embodiments, the target field includes: unit number, project number, settlement electricity volume, electricity price, electricity fee, and subsidy amount.

[0092] In one or more possible embodiments, it further includes:

[0093] The configuration unit is used to receive a configuration instruction from the power grid side, and configure a corresponding mask rule and a consistency check rule for the target field based on the configuration instruction.

[0094] It should be noted that the device 3 provided in the above embodiment only uses the division of the above functional modules as an example when executing the back-to-back settlement verification method. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the above functions. In addition, the back-to-back settlement verification device provided in the above embodiment and the back-to-back settlement verification method embodiment belong to the same concept, and the implementation process thereof is detailed in the method embodiment, which will not be repeated here.

[0095] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0096] The present application also provides a computer storage medium, which can store multiple instructions, and the instructions are suitable for being loaded and executed by a processor as described above. Figure 2 The method steps of the embodiment shown in the figure can be found in the specific implementation process. Figure 2 The specific description of the illustrated embodiment will not be repeated here.

[0097] The present application also provides a computer program product, which stores at least one instruction, and the at least one instruction is loaded and executed by the processor to implement the back-to-back settlement verification method described in the above embodiments.

[0098] See also Figure 4 , which is a schematic diagram of the structure of a server provided in the embodiment of the present application. Figure 4 As shown, the server 400 may include: at least one processor 401 , at least one network interface 404 , a user interface 403 , a memory 405 , and at least one communication bus 402 .

[0099] The communication bus 402 is used to realize the connection and communication between these components.

[0100] The user interface 403 may include a display screen (Display) and a camera (Camera), and the optional user interface 403 may also include a standard wired interface and a wireless interface.

[0101] The network interface 404 may optionally include a standard wired interface or a wireless interface (such as a WI-FI interface).

[0102] Among them, the processor 401 may include one or more processing cores. The processor 401 uses various interfaces and lines to connect various parts within the entire server 400, and executes various functions and processes data of the server 400 by running or executing instructions, programs, code sets or instruction sets stored in the memory 405, and calling data stored in the memory 405. Optionally, the processor 401 can be implemented in at least one hardware form of digital signal processing (Digital Signal Processing, DSP), field programmable gate array (Field-Programmable Gate Array, FPGA), and programmable logic array (Programmable Logic Array, PLA). The processor 401 can integrate one or more combinations of a central processing unit (Central Processing Unit, CPU), a graphics processing unit (Graphics Processing Unit, GPU) and a modem. Among them, the CPU mainly processes the operating system, user interface and application programs; the GPU is responsible for rendering and drawing the content to be displayed on the display screen; the modem is used to process wireless communications. It can be understood that the above-mentioned modem may not be integrated into the processor 401, and it can be implemented by a single chip.

[0103] Among them, the memory 405 may include a random access memory (Random Access Memory, RAM) and may also include a read-only memory (Read-Only Memory). Optionally, the memory 405 includes a non-transitory computer-readable storage medium. The memory 405 can be used to store instructions, programs, codes, code sets or instruction sets. The memory 405 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the above-mentioned method embodiments, etc.; the data storage area may store data involved in the above-mentioned method embodiments, etc. The memory 405 may optionally be at least one storage device located away from the aforementioned processor 401. As Figure 4 As shown, the memory 405 as a computer storage medium may include an operating system, a network communication module, a user interface module, and an application program.

[0104] exist Figure 4In the server 400 shown in FIG. 1 , the user interface 403 is mainly used to provide an input interface for the user and obtain the data input by the user; and the processor 401 can be used to call the application stored in the memory 405 and specifically execute the following steps: Figure 2 The specific process can be referred to Figure 2 As shown, no further description is given here.

[0105] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing related hardware through a computer program, and the program can be stored in a computer-readable storage medium, and when the program is executed, it can include the processes of the embodiments of the above-mentioned methods. The storage medium can be a disk, an optical disk, a read-only storage memory, or a random access memory, etc.

[0106] The above disclosure is only the preferred embodiment of the present application, which certainly cannot be used to limit the scope of rights of the present application. Therefore, equivalent changes made according to the claims of the present application are still within the scope covered by the present application.

Claims

1. A back-to-back settlement verification method, characterized in that: include: Receive original settlement data from the power grid side; Masking the field value of the target field in the original settlement data according to a preset masking rule to obtain masked settlement data; Push the masked settlement data to the power plant side for display; Acquire electricity billing data generated by the power plant side according to the target field in the masked settlement data; Performing a consistency check on a first field value of the target field in the original settlement data and a second field value of the target field in the power plant invoicing data; If the check result is passed, a check success message is synchronously sent to the grid side and the power plant side, and the masked settlement data displayed to the power plant side is updated to the original settlement data; If the check result is not passed, the power plant is instructed to upload new original settlement data.

2. The method according to claim 1, characterized in that: Back-to-back data comparison is performed in the form of masked settlement data.

3. The method according to claim 1 or 2, characterized in that: Use absolute or relative deviations for consistency checks.

4. The method according to claim 3, characterized in that: The target field includes a summary field and multiple detail fields; Comparing whether the field value of the summary field in the original settlement data is equal to the field value of the summary field in the power plant invoicing data; If not, continue to check whether the field values ​​of each detail field in the original settlement data and the power plant invoicing data are equal; If not, a check result message is synchronously sent to the power plant side and the grid side.

5. The method according to claim 1, 2 or 4, characterized in that: Also includes: If the number of times the check result fails exceeds the threshold, a check failure message is synchronously sent to the power plant side, instructing the power plant side to stop uploading new original settlement data.

6. The method according to claim 5, characterized in that The target fields include: unit number, project number, settlement electricity volume, electricity price, electricity fee, and subsidy amount.

7. The method according to claim 1 or 2 or 4 or 5, characterized in that: Also includes: A configuration instruction is received from the power grid side, and a corresponding mask rule and consistency check rule are configured for the target field based on the configuration instruction.

8. A back-to-back settlement verification device, characterized in that: include: An acquisition unit, used for receiving original settlement data from the power grid side; A masking unit, configured to perform masking processing on the field value of the target field in the original settlement data according to a preset masking rule to obtain masked settlement data; A push unit, used to push the mask settlement data to the power plant side for display; The acquisition unit is further used to acquire the electricity billing data generated by the power plant side according to the target field in the masked settlement data; A checking unit, configured to perform a consistency check on a first field value of the target field in the original settlement data and a second field value of the target field in the power plant invoicing data; The push unit is further configured to, if the check result is passed, synchronously send a check success message to the grid side and the power plant side, and update the masked settlement data displayed to the power plant side to the original settlement data; The instructing unit is used to instruct the power plant to upload new original settlement data if the inspection result is not passed.

9. A computer storage medium, characterized in that: The computer storage medium stores a plurality of instructions, and the instructions are suitable for being loaded by a processor and executing the method steps according to any one of claims 1 to 7.

10. A server, characterized in that: include: A processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the method steps as claimed in any one of claims 1 to 7.

Images