Financial data processing method and device and electronic equipment

Abstract

The invention provides a financial data processing method and device and electronic equipment. A reimbursement system cleans multi-source flow data pushed by a business and financial platform, and generates a deduction prepayment order based on the cleaned data and a preset field mapping relation; the reimbursement system performs red punching verification on the deduction prepayment order, and generates a deduction refund order based on the deduction prepayment order, a preset field mapping relation and a flow claiming red punching order pushed by the business and financial platform; the reimbursement system performs first examination and approval on the generated deducted document based on a preset examination and approval rule so as to push the deducted document to a financial system for second examination and approval when the first examination and approval of the deducted document are passed; and the reimbursement system synchronizes the first state of the deducted document in the first approval process and the second state of the deducted document in the second approval process to the business and financial platform. According to the invention, the document generation efficiency and accuracy and the abnormal business processing efficiency can be improved, and the business process integrity is guaranteed.

Description

Technical Field

[0001] This invention relates to the field of information management technology, and in particular to a financial data processing method, apparatus, and electronic device. Background Technology

[0002] In the context of digital financial management for large group enterprises, the efficient and accurate generation and closed-loop approval of bank fee receipts are core requirements for improving financial control efficiency. Taking a group enterprise with numerous legal entities as an example, each entity has multiple bank accounts, and each account generates daily fees. The entry and processing of these fee receipts is a crucial part of the company's daily financial work. Currently, companies generally use manual entry of fee receipts by administrative or financial personnel to complete accounting. However, as companies expand and the number of bank accounts increases, this manual processing method can no longer meet the actual business needs for efficient financial control.

[0003] The existing manual processing model has the following main problems: it relies on manual entry of bank fee information to generate documents, which greatly increases the workload of finance personnel. In addition, errors in key data such as amount, account information, and fee attribution are prone to occur during manual entry, affecting the accuracy of financial data. Manually generated fee documents need to be submitted for approval and pushed to the financial system manually. The approval status and rejection information cannot be automatically synchronized to the business initiator, resulting in a break in the business process. It is difficult for managers to track the progress of documents in real time, and it is impossible to quickly trace the root cause when problems occur. The business closed-loop control capability is lacking. Summary of the Invention

[0004] In view of this, the purpose of the present invention is to provide a financial data processing method, apparatus and electronic device to alleviate the above-mentioned problems existing in the related art.

[0005] In a first aspect, embodiments of the present invention provide a financial data processing method, comprising: a reimbursement system cleaning multi-source transaction data pushed by a business finance platform, and generating a prepayment deduction slip based on the cleaned data and a preset field mapping relationship; the reimbursement system performing a red-ink verification on the prepayment deduction slip, and generating a refund deduction slip based on the prepayment deduction slip, the preset field mapping relationship, and a red-ink verification slip for transaction claims pushed by the business finance platform; wherein, the red-ink verification slip for transaction claims is generated by the business finance platform based on the red-ink verification result when the prepayment deduction slip passes the red-ink verification; the reimbursement system performing a first approval on the generated depayment slip based on preset approval rules, and pushing the depayment slip to the financial system for a second approval when the first approval of the depayment slip passes; wherein, the depayment slip includes a prepayment deduction slip and / or a refund deduction slip; the reimbursement system synchronizing a first state of the depayment slip in the first approval process and a second state of the depayment slip in the second approval process to the business finance platform; wherein, the second state is synchronized from the financial system to the reimbursement system.

[0006] Secondly, embodiments of the present invention also provide a financial data processing apparatus, comprising: a cleaning and generation module, used by the reimbursement system to clean multi-source transaction data pushed by the business finance platform, and to generate a deduction prepayment slip based on the cleaned data and a preset field mapping relationship; and a verification and generation module, used by the reimbursement system to perform a red-ink verification on the deduction prepayment slip, and to generate a deduction refund slip based on the deduction prepayment slip, the preset field mapping relationship, and a transaction claim red-ink verification slip pushed by the business finance platform; wherein, the transaction claim red-ink verification slip is generated by the business finance platform when the deduction prepayment slip passes the red-ink verification. The system generates a verification result; an approval module, used by the reimbursement system to perform a first approval on the generated deduction documents based on preset approval rules, so that when the first approval of the deduction document is passed, the deduction document is pushed to the financial system for a second approval; wherein, the deduction document includes a deduction prepayment document and / or a deduction refund document; a status synchronization module, used by the reimbursement system to synchronize the first status of the deduction document in the first approval process and the second status of the deduction document in the second approval process to the business and finance platform; wherein, the second status is synchronized from the financial system to the reimbursement system.

[0007] Thirdly, embodiments of the present invention also provide an electronic device, including a processor and a memory, wherein the memory stores computer-executable instructions that can be executed by the processor, and the processor executes the computer-executable instructions to implement the financial data processing method described in the first aspect above.

[0008] This invention provides a financial data processing method, apparatus, and electronic device. The reimbursement system cleans multi-source transaction data pushed by a business finance platform and generates a prepayment deduction slip based on the cleaned data and a preset field mapping relationship. The reimbursement system performs a red-ink verification on the prepayment deduction slip and generates a refund deduction slip based on the prepayment deduction slip, the preset field mapping relationship, and the transaction claim red-ink verification slip pushed by the business finance platform. The reimbursement system performs a first approval on the generated depayment slip based on preset approval rules, and pushes the depayment slip to the financial system for a second approval when the first approval is passed. The reimbursement system synchronizes the first status of the depayment slip during the first approval process and the second status of the depayment slip during the second approval process to the business finance platform. By employing the aforementioned technologies, automatic cleaning of multi-source transaction data and intelligent generation of prepayment deduction orders can be achieved, replacing manual data entry and improving the efficiency and accuracy of document generation. By designing a mechanism for red-ink verification and refund document generation, accurate red-ink verification of erroneous documents and automatic generation of refund deduction orders can be achieved, improving the efficiency of handling abnormal business. Furthermore, automatic approval and real-time status synchronization of prepayment deduction orders and refund deduction orders can be realized, ensuring the integrity of business processes.

[0009] Other features and advantages of the invention will be set forth in the description which follows, and will be apparent in part from the description, or may be learned by practicing the invention. The objects and other advantages of the invention are realized and obtained in accordance with the structures particularly pointed out in the description, claims and drawings.

[0010] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0011] To more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0012] Figure 1 This is a flowchart illustrating a financial data processing method according to an embodiment of the present invention; Figure 2 This is an architecture diagram of the financial data processing system in an embodiment of the present invention; Figure 3 This is a schematic diagram of the structure of a financial data processing device according to an embodiment of the present invention; Figure 4 This is a schematic diagram of the structure of an electronic device according to an embodiment of the present invention. Detailed Implementation

[0013] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the present invention will be clearly and completely described below in conjunction with the embodiments. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0014] To facilitate understanding of this embodiment, a financial data processing method disclosed in this invention will first be described in detail, see [link to relevant documentation]. Figure 1 As shown, the method may include the following steps: In step S102, the reimbursement system cleans the multi-source transaction data pushed by the business and finance platform and generates a deduction prepayment order based on the cleaned data and the preset field mapping relationship.

[0015] In step S104, the reimbursement system performs a red-ink verification on the prepayment deduction slip and generates a deduction refund slip based on the prepayment deduction slip, the preset field mapping relationship, and the red-ink verification slip pushed by the business finance platform.

[0016] Among them, the transaction history red-ink reversal order can be generated by the business finance platform based on the red-ink reversal verification result when the red-ink reversal verification of the prepayment deduction order passes.

[0017] In step S106, the reimbursement system performs a first approval on the generated deduction document based on preset approval rules, so that when the first approval of the deduction document is passed, the deduction document will be pushed to the financial system for a second approval.

[0018] The deduction documents may include deduction prepayment slips and / or deduction refund slips.

[0019] In step S108, the reimbursement system synchronizes the first status of the deduction document in the first approval process and the second status of the deduction document in the second approval process to the business and finance platform.

[0020] The second state can be the synchronization of the financial system to the reimbursement system.

[0021] This invention provides a financial data processing method in which a reimbursement system cleans multi-source transaction data pushed by a business finance platform and generates a deduction prepayment slip based on the cleaned data and a preset field mapping relationship; the reimbursement system performs a red-ink verification on the deduction prepayment slip and generates a deduction refund slip based on the deduction prepayment slip, the preset field mapping relationship, and the transaction claim red-ink verification slip pushed by the business finance platform; the reimbursement system performs a first approval on the generated deduction slip based on preset approval rules, and pushes the deduction slip to the financial system for a second approval when the first approval is passed; the reimbursement system synchronizes the first status of the deduction slip during the first approval process and the second status of the deduction slip during the second approval process to the business finance platform. By employing the aforementioned technologies, automatic cleaning of multi-source transaction data and intelligent generation of prepayment deduction orders can be achieved, replacing manual data entry and improving the efficiency and accuracy of document generation. By designing a mechanism for red-ink verification and refund document generation, accurate red-ink verification of erroneous documents and automatic generation of refund deduction orders can be achieved, improving the efficiency of handling abnormal business. Furthermore, automatic approval and real-time status synchronization of prepayment deduction orders and refund deduction orders can be realized, ensuring the integrity of business processes.

[0022] As one possible implementation, multi-source transaction data may include transaction claim form data after approval; based on this, before the reimbursement system cleans the multi-source transaction data pushed by the business and finance platform in step S102 above, the above financial data processing method may also include: the reimbursement system calls a preset transaction data receiving interface to receive the transaction claim form data pushed by the business and finance platform; wherein, the preset transaction data receiving interface transmits data in JSON format and supports breakpoint resume.

[0023] In practical applications, a dedicated interface can be pre-developed for the reimbursement system as a transaction data receiving interface. This interface receives transaction claim data pushed by the business finance platform after approval. It supports batch data reception and uses JSON format for data transmission. The core transmission fields include transaction number, bank account information, expense amount, expense occurrence period, and financial organization code. It also supports breakpoint resume to avoid data loss due to data transmission interruption. The reimbursement system can call the transaction data receiving interface to receive transaction claim data pushed by the business finance platform, so that the received transaction claim data can be cleaned later.

[0024] As one possible implementation, the step S102 above, in which the reimbursement system generates a deduction prepayment based on the cleaned data and the preset field mapping relationship, may include: the reimbursement system determining the first target data from the cleaned data according to the preset field mapping relationship, and generating a deduction prepayment based on the first target data.

[0025] Continuing from the previous example, standardized data field mapping relationships can be predefined to ensure data consistency between different systems. Taking the prepayment deduction field as an example, the specific mapping relationship is shown in Table 1.

[0026] Table 1. Field Mapping Relationship Table for Prepayment Orders

[0027] A multi-dimensional data cleaning algorithm can be pre-designed so that the reimbursement system can use it to comprehensively verify and correct the received transaction data. The core logic of the multi-dimensional data cleaning algorithm is as follows:

[0028] As one example of a multi-dimensional data cleaning algorithm, the business and finance platform pushes a transaction record to the expense reimbursement system: Document Date = 2025-10-26, Responsibility Attribution = 002, Reason = XX Bank Account Handling Fee, Supplier Code = GY001, Expense Receiving Unit = ORG005, Expense Amount = 1.5, Expense Occurrence Period = 2025-10, Preparer = bip00123, Budget Department = DEP008. The preset validation rules require: required fields include all the above fields, document date in YYYY-MM-DD format, expense amount > 0.01, and supplier code must exist in the master data. The multi-dimensional data cleaning algorithm process includes: 1) Verifying that all required fields exist and are not missing; 2) Verifying field format: the document date format is correct, and the expense amount of 1.5 > 0.01, meeting the requirements; 3) Calling the master data interface to verify that the supplier code GY001 exists; 4) Standardizing the data (removing leading and trailing spaces from field values). Finally, the transaction data cleaning is successful, and the process proceeds to the prepayment deduction generation stage.

[0029] As another example of a multi-dimensional data cleaning algorithm, the business and finance platform pushed a transaction data: document date = 2025 / 10 / 26, responsibility attribution = 008 (not within the enumeration range), reason = bank handling fee, supplier code = GY999 (master data does not exist), fee amount = 0.01, fee occurrence period = 202510; Algorithm processing: 1) No required fields are missing; 2) Format validation: The document date format is incorrect (should be YYYY-MM-DD), the responsibility attribution value is not within the enumeration range, the expense occurrence period format is incorrect (should be YYYY-MM), and the expense amount = 0.01 does not meet the requirement of >0.01; 3) Master data validation: Supplier code GY999 does not exist. Ultimately, the data cleaning failed, and the reason for the failure was recorded and reported to the business and finance platform.

[0030] Continuing from the previous example, the main methods for generating deduction prepayment slips can include: On the reimbursement system side, the cleaned data enters the deduction prepayment slip generation stage. The reimbursement system automatically fills in the main and detail fields of the deduction prepayment slip according to the preset field mapping relationship, and assigns the fixed value representing the bank handling fee to the expense type of the deduction prepayment slip; after the deduction prepayment slip is generated, the document status of the deduction prepayment slip is automatically set to "submitted".

[0031] As one possible implementation, step S104 (i.e., the reimbursement system performs red-ink verification on the prepayment deduction slip and generates a refund deduction slip based on the prepayment deduction slip, the preset field mapping relationship, and the transaction history red-ink verification slip pushed by the business and finance platform) may include: Step A1: After the reimbursement system responds to the red-ink reversal request initiated by the business finance platform, it performs red-ink reversal verification on the deduction documents and returns the red-ink reversal verification result to the business finance platform. This enables the business finance platform to generate a red-ink reversal document based on the red-ink reversal verification result when the red-ink reversal verification of the deduction prepayment document passes and push it to the reimbursement system.

[0032] For example, the reimbursement system may have a preset red-ink reversal verification interface. Based on this, before the reimbursement system performs red-ink reversal verification on the deduction documents in step A1 above, the business and finance platform can call the preset red-ink reversal verification interface to query the target deduction prepayment document corresponding to the target document number. Accordingly, the red-ink reversal verification of the deduction documents by the reimbursement system in step A1 above may include: the reimbursement system uses the preset red-ink reversal verification interface to determine whether the target deduction prepayment document meets the preset red-ink reversal conditions according to the preset red-ink reversal verification rules. If the target deduction prepayment document meets the preset red-ink reversal conditions, the red-ink reversal verification of the target deduction prepayment document passes.

[0033] Among them, the target deduction prepayment can meet the preset conditions for red-ink reversal, which may include simultaneously meeting the following conditions: the target order number exists in the reimbursement system, the target deduction prepayment has passed the second approval, the target deduction prepayment does not contain red-ink reversal records, and the generation event of the target deduction prepayment is within the preset validity period.

[0034] In step A2, the reimbursement system generates a deduction refund form based on the prepayment deduction form, preset field mapping relationships, and transaction history red-ink reversal form.

[0035] For example, the transaction history redemption slip may include a target slip number; based on this, step A2 above may include: the reimbursement system associates the target slip number with the core information of the target deduction prepayment slip, determines the second target data from the target deduction prepayment slip according to the preset field mapping relationship, and generates a target deduction refund slip based on the associated data and the second target data.

[0036] The core information may include the amount of the target prepayment order and the refund amount of the target prepayment refund order, which is consistent with the amount of the target prepayment order.

[0037] Following the previous example, in practical applications, a red-ink reversal verification interface can be developed for the reimbursement system. This allows the business and finance platform's transaction history claiming service to call this interface to query whether the deduction prepayment corresponding to a specified order number meets the red-ink reversal conditions (the red-ink reversal conditions may include: the deduction prepayment has completed financial approval, there are no outstanding refund records, and the red-ink reversal application time is within the document's validity period, etc.). The business and finance platform's transaction history claiming service can use this red-ink reversal verification interface to return the red-ink reversal status (yes / no), the reason for not being able to red-ink, and the document's core information to the business and finance platform.

[0038] Following the previous example, red-ink reversal verification rules can be preset for the reimbursement system so that when the business and finance platform calls the red-ink reversal verification interface, the following red-ink reversal verification process can be performed according to the preset red-ink reversal verification rules: 1) Document Existence Verification: Verify whether the input deduction prepayment order number exists in the reimbursement system. If the deduction prepayment order number does not exist in the reimbursement system, return "Cannot be reversed, document does not exist" to the business finance platform. 2) Document Status Verification: Verify the current status of the prepayment deduction. It can only be reversed if the status of the prepayment deduction is "Approval Completed". If the status of the prepayment deduction is "Submitting", "Approval Abnormal", "Reversed", etc., then return "Cannot be reversed, document status not allowed" to the business and finance platform. 3) Red-ink reversal record verification: Check whether there is a red-ink reversal record for the prepayment deduction. If there is an incomplete red-ink reversal record or a completed red-ink reversal record, return "Cannot be red-inked, red-ink reversal record exists" to the business finance platform. 4) Validity verification: Verify the generation time of the prepayment deduction. The prepayment deduction can only be reversed if the generation time is within the preset validity period (e.g., 3 months). If the generation time of the prepayment deduction exceeds the validity period, the platform will return "Cannot be reversed, document has expired".

[0039] The red-ink reversal and refund process is as follows: 1) The business finance platform initiates a red-ink reversal claim request to the reimbursement system, calls the red-ink reversal verification interface of the reimbursement system, and passes in the deduction prepayment order number; 2) The reimbursement system performs the red-ink reversal verification and returns the red-ink reversal verification result to the business finance platform; 3) If the red-ink reversal verification passes, the business finance platform generates a red-ink reversal claim order and pushes it to the reimbursement system. After receiving the data, the reimbursement system automatically generates a deduction refund order; 4) The deduction refund order completes automatic approval, status synchronization, and push to the financial system according to the preset process; 5) If the red-ink reversal verification fails, the reimbursement system returns a reason why red-ink reversal is not allowed to the business finance platform, the business finance platform terminates the red-ink reversal process, and prompts the user to handle it.

[0040] The main methods for generating deduction refund slips include: When the business finance platform initiates a red-ink reversal request to the reimbursement system and passes the red-ink reversal verification of the original document (i.e., the deduction prepayment slip) through the reimbursement system, the reimbursement system automatically associates the core information of the original document (such as the expense receiving unit, supplier code, expense amount, etc.) based on the received deduction prepayment slip number to generate a deduction refund slip; the main fields of the deduction refund slip include the deduction prepayment slip number, the preparer, the budget department, etc. The preparer is entered with the BIP account of the user who initiated the red-ink reversal, and the budget department is entered with the HCM human resources department code of the user; after the deduction refund slip is generated, the document status of the deduction refund slip is automatically set to "submitted".

[0041] As one possible implementation, the above step S108 (i.e., the reimbursement system synchronizes the first status of the deduction document in the first approval process and the second status of the deduction document in the second approval process to the business and finance platform) may include: the reimbursement system synchronizes the first status to the business and finance platform, and at the same time pushes the deduction document to the financial system for second approval, so that the financial system synchronizes the second status to the reimbursement system; the reimbursement system synchronizes the second status to the business and finance platform.

[0042] For example, the step of the reimbursement system synchronizing a first state to the business and finance platform may include: if the first state changes, the reimbursement system calls a preset synchronization interface to synchronize the first state to the business and finance platform. Correspondingly, the step of the financial system synchronizing a second state to the reimbursement system may include: if the second state changes, the financial system calls a preset synchronization interface to synchronize the second state to the reimbursement system, so that the reimbursement system calls the preset synchronization interface to synchronize the second state to the business and finance platform.

[0043] Following the previous example, automatic approval rules can be preset for the reimbursement system. This allows for an automatic approval process triggered when prepayment or refund deductions are generated and in the "submit" state. For prepayment deductions, since the expense type is fixed as bank fees and the original transaction data has been cleaned and verified using multi-dimensional data cleaning algorithms, no manual intervention is required. The reimbursement system automatically completes the business approval, resulting in "Approval Passed." For refund deductions, the associated prepayment deduction has been approved, and the transaction claim request initiated by the business finance platform to the reimbursement system has passed verification. The reimbursement system automatically completes the business approval, resulting in "Approval Passed." If an anomaly occurs during the automatic approval process (such as an abnormal original document status or missing data), the reimbursement system automatically sets the document status to "Approval Anomaly" and triggers an alarm to notify the administrator for handling.

[0044] A two-way synchronization interface can be pre-developed as a synchronization interface for order numbers and statuses, used to synchronize order numbers and statuses between the reimbursement system and the business and finance platform's transaction claim service and the financial system. This synchronization interface supports real-time push notifications. When the status of a prepayment / refund order changes, such as being generated, approved, rejected, or completed, the synchronization interface is automatically triggered to synchronize relevant information. The synchronized data includes the order number, order type, status code, status description, and synchronization time.

[0045] Continuing from the previous example, the status synchronization process for prepayment deductions is as follows: 1) The reimbursement system generates a prepayment deduction slip (status: "Submitted"), and the prepayment deduction slip is automatically approved (status: "Approved"); 2) The reimbursement system synchronizes the prepayment deduction slip number and status ("Approved") to the business and finance platform's transaction history claim service through the corresponding synchronization interface; 3) The reimbursement system pushes the prepayment deduction slip to the finance system, awaiting approval; 4) If the finance system rejects the prepayment deduction slip during the approval process, the finance system synchronizes the rejection status of the prepayment deduction slip to the reimbursement system, which then synchronizes the rejection status to the business and finance platform's transaction history claim service, and simultaneously updates the slip status to "Rejected by Finance System"; 5) If the financial system approves the prepayment deduction, the financial system will synchronize the approval completion status of the prepayment deduction to the reimbursement system. The reimbursement system will then synchronize the approval completion status to the business finance platform's transaction record claim service and update the document status to "approval completed" to trigger subsequent processes such as voucher generation.

[0046] Continuing from the previous example, the status synchronization process for deduction refund orders is as follows: 1) The reimbursement system generates a deduction refund order (status: "Submitted"), and the deduction refund order is automatically approved (status: "Approved"); 2) The reimbursement system synchronizes the deduction refund order number and status ("Approved") to the business and finance platform's transaction history claim service; 3) The reimbursement system pushes the deduction refund order to the finance system, awaiting its approval; 4) If the finance system rejects the deduction refund order during the approval process, the finance system synchronizes the rejection status of the deduction refund order to the reimbursement system, which then synchronizes the rejection status to the business and finance platform, and updates the document status to "Rejected by Finance System"; 5) If the finance system approves the deduction refund order, the finance system synchronizes the approval completion status of the deduction refund order to the reimbursement system, which then synchronizes the approval completion status to the business and finance platform, and updates the document status to "Approval Completed," completing the refund business loop.

[0047] As one possible implementation, after step A2 (i.e., the reimbursement system generates a deduction refund form based on the deduction prepayment form, the preset field mapping relationship, and the transaction history red-ink reversal form), the above financial data processing method may further include: the reimbursement system associates the target deduction refund form with the target form number, and simultaneously records the red-ink reversal record in the target deduction prepayment form; if the first approval or the second approval of the target deduction refund form fails, the reimbursement system updates the red-ink reversal record in the target deduction prepayment form to the first state, so as to re-verify the deduction document after responding to the transaction history red-ink reversal request re-initiated by the business finance platform; if the second approval of the target deduction refund form passes, the reimbursement system updates the red-ink reversal record in the target deduction prepayment form to the second state; wherein, the second state indicates that the red-ink reversal of the target deduction prepayment form is completed.

[0048] Following the previous example, the reimbursement system implements full-process control over deduction refund orders to ensure that the refund amount matches the original invoice amount and avoid duplicate refunds. The full-process control of deduction refund orders mainly includes the following parts: 1) Amount consistency verification: When generating a deduction refund order, the amount of the original deduction prepayment order is automatically associated. The refund amount of the deduction refund order is consistent with the amount of the original deduction prepayment order by default, and the refund amount cannot be manually modified. 2) Red Reversal Record Association: After the deduction refund order is generated, it is automatically associated with the original deduction prepayment order number, and the red reversal record is recorded in the original document to form an association relationship for easy traceability; 3) Status linkage: If the deduction refund order is rejected or fails to be approved, the status of the original deduction prepayment order's red-ink reversal record will be updated to "Red-ink reversal failed" and the business finance platform can re-initiate the transaction claim red-ink reversal request; if the deduction refund order is approved, the status of the original document's red-ink reversal record will be updated to "Red-ink reversal completed" and the original document cannot be red-inked again.

[0049] For ease of understanding, the implementation of the above financial data processing method is described below using a specific application as an example.

[0050] A financial data processing system can be designed to implement the above financial data processing methods. See [link / reference]. Figure 2 As shown, the architecture of the financial data processing system can mainly include: an interface integration and data flow module, a data cleaning and intelligent generation module for deduction documents, a fully automated approval and status synchronization module, and an abnormal red-ink verification and refund control module.

[0051] The interface integration and data flow module is fundamental to achieving data interoperability and process closure across different systems. Its core function is to develop and integrate interfaces between the business and finance platform's transaction history claiming service, the expense reimbursement system, and the financial system, defining standardized data flow formats and interaction protocols. The interfaces developed and integrated by this module mainly include: transaction history data receiving interface, order number and status synchronization interface, and red-ink verification interface. The interface integration and data flow module also pre-defines standardized data field mapping relationships (as shown in Table 1).

[0052] The interface integration and data flow module can also be optimized in the following ways: adopt a distributed architecture design and introduce a load balancing mechanism to distribute large-scale document generation requests to multiple nodes for processing; optimize the database by sharding and partitioning, and store data in shards according to financial organization codes or expense accounting units to improve data read and write efficiency; set up a request queue to queue concurrent requests and avoid system overload; and configure a monitoring and alarm mechanism to monitor system concurrency, response time and other indicators in real time, and automatically trigger alarms when the indicators approach the preset alarm threshold to ensure stable system operation.

[0053] In practical applications, a centralized architecture can be used to replace the aforementioned distributed architecture in order to simplify development and deployment and reduce development and deployment costs.

[0054] The data cleaning and intelligent deduction document generation module is mainly responsible for receiving transaction data pushed by the business and finance platform. After multi-dimensional cleaning and verification, it automatically generates deduction prepayment documents or deduction refund documents. The core is to ensure the accuracy and completeness of the generated documents. This module is pre-designed with a multi-dimensional data cleaning algorithm for the reimbursement system to perform multi-dimensional cleaning and verification on the transaction data pushed by the business and finance platform. This module is also pre-configured with deduction document generation logic for the reimbursement system to generate deduction documents. The fully automated approval and status synchronization module is used to realize the automatic approval process for prepayment and refund orders, as well as the real-time synchronization of the status of prepayment and refund orders between different systems, ensuring a closed-loop business process. This module has preset automatic approval rules, which trigger the automatic approval process when a prepayment or refund order is generated and is in the "submitted" state. This module can also be used to call the synchronization interface of order number and status to synchronize relevant information of the deduction documents.

[0055] The following functions can also be introduced into the end-to-end automated approval and status synchronization module: 1) Full field validation: Before pushing a message, perform integrity and format validation on all fields of the message to ensure that there are no missing fields and that the field format meets the requirements of the receiving end; 2) Anomaly detection and retry: During message push, when a push fails, the reason for the failure is recorded and the message is automatically retried (maximum of 3 retries, with a 5-second interval between each retrieval); if the retry fails, an alarm is triggered to notify the administrator to handle it manually. 3) Log recording: Records detailed information such as the push time, receiving end, push status, and failure reason for each message, which facilitates subsequent troubleshooting.

[0056] The Abnormal Red-Invoice Verification and Refund Control Module is used to accurately verify prepaid orders and manage the entire process of refund orders, ensuring the accuracy and efficiency of abnormal business processing. This module has preset red-invoice verification rules, and when the red-invoice verification interface is called, the prepaid orders are verified according to the red-invoice verification rules. This module can also perform the above-mentioned red-invoice and refund processes, as well as implement full-process control of refund orders.

[0057] The core idea of ​​the basic implementation scheme of the above-mentioned financial data processing method is as follows: Establish standardized data flow specifications by connecting the data interfaces between the business and finance platform's transaction history claiming service, the reimbursement system, and the financial system; design an automatic extraction and cleaning mechanism for bank transaction data, automatically generating deduction prepayment slips (with the expense type fixed as bank handling fees) based on preset document generation logic; construct an automatic approval and status synchronization mechanism to automatically complete business approval and bidirectionally synchronize the status to different systems after document submission; design red-ink verification and refund document generation methods to ensure accurate handling of abnormal transactions; optimize the system architecture to improve concurrent processing capabilities, ultimately achieving full-process automation and closed-loop management of bank handling fee document processing, improving financial processing efficiency and data accuracy.

[0058] The core implementation process of the above financial data processing method is as follows: 1) Interface Integration and Rule Configuration Phase: The administrator completes the interface integration configuration between the business and finance platform's transaction claim service, expense reimbursement system, and financial system, and presets document generation rules (including fixed expense type as bank handling fee, mandatory field validation rules, enumeration values ​​of rights and responsibilities, amount thresholds, etc.), approval flow rules (including automatic business approval after each submission of deduction prepayment order and deduction refund order), data synchronization rules, and concurrent processing parameters.

[0059] 2) Bank statement retrieval and claiming stage: The business finance platform's statement claiming service periodically retrieves statement records from different payment channels and different banks, generates statement claiming forms, and after manual review and approval, pushes the relevant data to the reimbursement system.

[0060] 3) Data cleaning and prepayment deduction generation stage: After receiving the data pushed by the business and finance platform, the reimbursement system uses a pre-designed multi-dimensional data cleaning algorithm to clean the data (including field format verification, mandatory field integrity verification, master data consistency verification, data standardization processing, etc.), and automatically generates a prepayment deduction form according to the preset document generation rules (filling in core fields such as document date, attribution of rights and responsibilities, reason, supplier code, etc., and the expense type is fixed as bank handling fee).

[0061] 4) Automatic Approval and Status Synchronization Stage: After the prepayment deduction order is generated, it automatically enters the submission state, triggering the preset approval process and automatically completing the business approval; the reimbursement system transmits the generated order number and approval status back to the business and finance platform's transaction claim service, and automatically pushes the order to the financial system; if the order is rejected during the financial system's approval process, the rejection status is synchronized back to the reimbursement system, and then the reimbursement system synchronizes the rejection status to the business and finance platform's transaction claim service; after the reimbursement system completes the approval, the completion status is synchronized back to the reimbursement system, and then the reimbursement system synchronizes the completion status to the business and finance platform's transaction claim service, realizing a closed-loop synchronization of the entire process status.

[0062] 5) Abnormal Red Reversal and Refund Processing Stage: When the transaction claim information automatically generated by the reimbursement system is incorrect or a refund transaction occurs, the user initiates a red reversal request to the reimbursement system through the transaction claim service on the business and finance platform. Before initiating the red reversal request on the business and finance platform, the platform calls the red reversal verification interface of the reimbursement system to query the order number to verify whether the document is refundable. For documents that are eligible for red reversal, the platform calls the interface of the reimbursement system to generate a deduction refund order. After the deduction refund order is submitted, the business approval is automatically completed, and the order number and status are synchronized to the business and finance platform and pushed to the financial system. Subsequent statuses such as document rejection and approval completion are synchronized to different systems according to the above status synchronization process, completing the closed loop of the refund business.

[0063] 6) Message push phase: Perform full field validation, exception capture and retries, and log recording to ensure that key information such as document status and document number can be pushed to the corresponding system normally and avoid message loss.

[0064] The beneficial effects of the above-mentioned financial data processing methods are mainly reflected in the following aspects: (i) Replace manual entry and improve document generation efficiency and accuracy: By automatically pulling bank statements, cleaning data and generating documents intelligently, the traditional manual entry mode is completely replaced, significantly improving the efficiency of handling fee documents and the accuracy of document generation, greatly reducing the workload and error rate of financial personnel.

[0065] (ii) Achieve closed-loop management and control of the entire process and improve business processing efficiency: Construct a fully automated approval and status synchronization system. Document approval and status synchronization do not require manual intervention, the business processing cycle is significantly shortened, and it is convenient for managers to track document progress in real time and improve business management efficiency.

[0066] (III) Optimize system integration and data flow to ensure data consistency: Through standardized interfaces and data mapping rules, achieve efficient data flow between different systems, avoid data inconsistency in the data flow process, reduce data synchronization latency, and improve the reliability of financial data.

[0067] (iv) Improve the abnormal handling mechanism and reduce control risks: The red-ink verification method and refund control method ensure the accurate red-inking and refund of abnormal documents, avoid problems such as duplicate refunds and incorrect refunds, significantly improve the efficiency of abnormal business processing, and reduce financial control risks.

[0068] (v) Enhance system concurrent processing capabilities to adapt to large-scale business needs: The distributed architecture and load balancing mechanism ensure that the system can support the concurrent business processing of a large number of legal entities, with a short document generation response time. The system stability and adaptability are significantly improved to meet the needs of enterprise scale development.

[0069] (vi) Optimize the message push process and ensure smooth workflow: By performing full field validation, exception capture and retries, and logging, the problem of outbound messages being unable to be sent is completely solved, the message push success rate is significantly improved, and the smoothness of the entire process status synchronization is ensured.

[0070] Based on the above-described financial data processing method, this invention also provides a financial data processing apparatus, see [link to apparatus]. Figure 3 As shown, the device may include the following modules: The cleaning and generation module 302 is used by the reimbursement system to clean the multi-source transaction data pushed by the business and finance platform, and generate a deduction prepayment order based on the cleaned data and the preset field mapping relationship.

[0071] The verification generation module 304 is used by the reimbursement system to perform red-ink verification on the deduction prepayment, and generate a deduction refund order based on the deduction prepayment, the preset field mapping relationship and the transaction claim red-ink order pushed by the business finance platform; wherein, the transaction claim red-ink order is generated by the business finance platform based on the red-ink verification result when the deduction prepayment passes the red-ink verification.

[0072] The approval module 306 is used by the reimbursement system to perform a first approval on the generated deduction documents based on preset approval rules, so as to push the deduction documents to the financial system for a second approval when the first approval of the deduction documents is passed; wherein, the deduction documents include deduction prepayment documents and / or deduction refund documents.

[0073] The status synchronization module 308 is used by the reimbursement system to synchronize the first status of the deduction document in the first approval process and the second status of the deduction document in the second approval process to the financial platform; wherein, the second status is synchronized from the financial system to the reimbursement system.

[0074] Using the aforementioned financial data processing device, automatic cleaning of multi-source transaction data and intelligent generation of deduction and prepayment slips can be achieved, replacing manual entry and improving the efficiency and accuracy of document generation. By designing a mechanism for red-ink verification and refund document generation, accurate red-ink verification of erroneous documents and automatic generation of deduction and refund slips can be achieved, improving the efficiency of abnormal business processing. It can also realize automatic approval and circulation of deduction and prepayment slips and real-time status synchronization, ensuring the integrity of business processes.

[0075] The financial data processing device provided in this embodiment of the invention has the same implementation principle and technical effects as the aforementioned method embodiment. For the sake of brevity, any parts not mentioned in the device embodiment can be referred to the corresponding content in the aforementioned method embodiment.

[0076] This invention also provides an electronic device, such as... Figure 4 The diagram shows the structure of the electronic device, which includes a processor 41 and a memory 40. The memory 40 stores computer-executable instructions that can be executed by the processor 41. The processor 41 executes the computer-executable instructions to implement the aforementioned financial data processing method.

[0077] exist Figure 4 In the illustrated embodiment, the electronic device further includes a bus 42 and a communication interface 43, wherein the processor 41, the communication interface 43, and the memory 40 are connected via the bus 42.

[0078] The memory 40 may include high-speed random access memory (RAM) and may also include non-volatile memory, such as at least one disk storage device. Communication between this system network element and at least one other network element is achieved through at least one communication interface 43 (which can be wired or wireless), such as the Internet, wide area network, local area network, metropolitan area network, etc. The bus 42 may be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus, etc. The bus 42 can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 4 The symbol is represented by a single double-headed arrow, but this does not mean that there is only one bus or one type of bus.

[0079] Processor 41 may be an integrated circuit chip with signal processing capabilities. In implementation, each step of the aforementioned financial data processing method can be completed by the integrated logic circuitry in the hardware of processor 41 or by software instructions. Processor 41 can be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; it can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the financial data processing method disclosed in the embodiments of this invention can be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in the memory, and the processor 41 reads the information in the memory and, in conjunction with its hardware, completes the steps of the financial data processing method of the aforementioned embodiment.

[0080] Unless otherwise specifically stated, the relative steps, numerical expressions, and values ​​of the components and steps described in these embodiments do not limit the scope of the invention.

[0081] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a processor-executable, non-volatile, computer-readable storage medium. Based on this understanding, the technical solution of this invention, essentially, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0082] In the description of this invention, it should be noted that the terms "center," "upper," "lower," "left," "right," "vertical," "horizontal," "inner," and "outer," etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are used only for the convenience of describing the invention and for simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on the invention. Furthermore, the terms "first," "second," and "third" are used for descriptive purposes only and should not be construed as indicating or implying relative importance.

[0083] Finally, it should be noted that the above-described embodiments are merely specific implementations of the present invention, used to illustrate the technical solutions of the present invention, and not to limit it. The scope of protection of the present invention is not limited thereto. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can still modify or easily conceive of changes to the technical solutions described in the foregoing embodiments within the technical scope disclosed in the present invention, or make equivalent substitutions for some of the technical features; and these modifications, changes, or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be covered within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A financial data processing method, characterized in that, include: The reimbursement system cleans the multi-source transaction data pushed by the business and finance platform, and generates a deduction prepayment slip based on the cleaned data and the preset field mapping relationship; The reimbursement system performs a red-ink verification on the prepayment deduction slip and generates a refund slip based on the prepayment deduction slip, the preset field mapping relationship, and the red-ink verification slip pushed by the business finance platform; wherein, the red-ink verification slip is generated by the business finance platform based on the red-ink verification result when the prepayment deduction slip passes the red-ink verification. The reimbursement system performs a first approval on the generated deduction documents based on preset approval rules, and pushes the deduction documents to the financial system for a second approval when the first approval of the deduction documents is passed; wherein, the deduction documents include deduction prepayment documents and / or deduction refund documents; The reimbursement system synchronizes the first status of the deduction document in the first approval process and the second status of the deduction document in the second approval process to the business and finance platform; wherein, the second status is synchronized from the financial system to the reimbursement system.

2. The financial data processing method according to claim 1, characterized in that, The reimbursement system performs a red-inking verification on the prepayment deduction slip, and generates a deduction refund slip based on the prepayment deduction slip, the preset field mapping relationship, and the red-inking slip claimed in the transaction history pushed by the business and finance platform, including: After the reimbursement system responds to the red-inking request for cash flow claim initiated by the business finance platform, it performs red-inking verification on the deduction document and returns the red-inking verification result to the business finance platform, so that when the red-inking verification of the deduction prepayment document passes, the business finance platform generates a cash flow claim red-inking document based on the red-inking verification result and pushes it to the reimbursement system. The reimbursement system generates a deduction refund form based on the deduction prepayment form, the preset field mapping relationship, and the transaction history red-ink reversal form.

3. The financial data processing method according to claim 2, characterized in that, The reimbursement system synchronizes the first status of the deduction slip during the first approval process and the second status of the deduction slip during the second approval process to the business and finance platform, including: The reimbursement system synchronizes the first status to the business and finance platform, and at the same time pushes the deduction document to the financial system for second approval, so that the financial system synchronizes the second status to the reimbursement system; The reimbursement system synchronizes the second status to the business and finance platform.

4. The financial data processing method according to claim 1, characterized in that, The multi-source transaction data includes approved transaction claim form data; before the reimbursement system cleans the multi-source transaction data pushed by the business and finance platform, it also includes: The reimbursement system calls a preset transaction data receiving interface to receive transaction claim data pushed by the business and finance platform; wherein, the preset transaction data receiving interface transmits data in JSON format and supports breakpoint resume.

5. The financial data processing method according to claim 3, characterized in that, The reimbursement system synchronizes the first state to the business and finance platform, including: if the first state changes, the reimbursement system calls a preset synchronization interface to synchronize the first state to the business and finance platform. The financial system synchronizes the second state to the reimbursement system by: if the second state changes, the financial system calls the preset synchronization interface to synchronize the second state to the reimbursement system, so that the reimbursement system calls the preset synchronization interface to synchronize the second state to the financial platform.

6. The financial data processing method according to claim 5, characterized in that, The reimbursement system has a preset red-ink reversal verification interface; before the reimbursement system performs red-ink reversal verification on the deduction document, it also includes: the business and finance platform calls the preset red-ink reversal verification interface to query the target deduction prepayment document corresponding to the target document number; The reimbursement system performs a red-ink reversal verification on the deduction document, including: the reimbursement system determines whether the target deduction prepayment document meets the preset red-ink reversal conditions according to the preset red-ink reversal verification rules through the preset red-ink reversal verification interface; if the target deduction prepayment document meets the preset red-ink reversal conditions, the red-ink reversal verification of the target deduction prepayment document passes; wherein, the target deduction prepayment document meeting the preset red-ink reversal conditions includes simultaneously meeting the following conditions: the target document number exists in the reimbursement system, the second approval of the target deduction prepayment document is approved, the target deduction prepayment document does not contain red-ink reversal records, and the generation event of the target deduction prepayment document is within the preset validity period.

7. The financial data processing method according to claim 6, characterized in that, The reimbursement system generates a deduction prepayment slip based on the cleaned data and a preset field mapping relationship, including: the reimbursement system determines a first target data from the cleaned data according to the preset field mapping relationship, and generates a deduction prepayment slip based on the first target data; The transaction history red-ink reversal slip includes the target order number; the reimbursement system generates a deduction refund slip based on the prepayment deduction slip, the preset field mapping relationship, and the transaction history red-ink reversal slip, including: the reimbursement system associates the target order number with the core information of the target prepayment deduction slip, determines the second target data from the target prepayment deduction slip according to the preset field mapping relationship, and generates the target deduction refund slip based on the associated data and the second target data; wherein, the core information includes the expense amount of the target prepayment deduction slip, and the refund amount of the target deduction refund slip is consistent with the expense amount of the target prepayment deduction slip.

8. The financial data processing method according to claim 7, characterized in that, After the reimbursement system generates a deduction refund form based on the prepayment deduction form, the preset field mapping relationship, and the transaction history red-ink reversal form, it also includes: The reimbursement system associates the target deduction refund order with the target order number, and simultaneously records the red-ink reversal record in the target deduction prepayment order; If the first or second approval of the target deduction refund order fails, the reimbursement system will update the red-ink record in the target deduction prepayment order to the first status, so as to re-verify the deduction document after responding to the red-ink claim request re-initiated by the business finance platform. If the second approval of the target deduction refund order is approved, the reimbursement system will update the red-ink reversal record in the target deduction prepayment order to the second status; wherein, the second status indicates that the red-ink reversal of the target deduction prepayment order is completed.

9. A financial data processing device, characterized in that, include: The cleaning and generation module is used by the reimbursement system to clean the multi-source transaction data pushed by the business and finance platform, and generate deduction and prepayment slips based on the cleaned data and preset field mapping relationships. The verification generation module is used by the reimbursement system to perform red-ink verification on the deduction prepayment slip, and generate a deduction refund slip based on the deduction prepayment slip, the preset field mapping relationship, and the transaction claim red-ink slip pushed by the business finance platform; wherein, the transaction claim red-ink slip is generated by the business finance platform based on the red-ink verification result when the deduction prepayment slip passes the red-ink verification. An approval module is used by the reimbursement system to perform a first approval on the generated deduction documents based on preset approval rules, so as to push the deduction documents to the financial system for a second approval when the first approval of the deduction documents is passed; wherein, the deduction documents include deduction prepayment documents and / or deduction refund documents; The status synchronization module is used by the reimbursement system to synchronize the first status of the deduction document in the first approval process and the second status of the deduction document in the second approval process to the financial platform; wherein, the second status is synchronized from the financial system to the reimbursement system.

10. An electronic device, characterized in that, The method includes a processor and a memory, the memory storing computer-executable instructions that can be executed by the processor, the processor executing the computer-executable instructions to implement the financial data processing method according to any one of claims 1 to 8.

Images