Financial linkage event processing method and device, electronic equipment and storage medium

Abstract

The application discloses a kind of accounting financial linkage event processing method, device, electronic equipment and storage medium, the target accounting event of multiple accounting systems in the application is received by target accounting system, target accounting event is sent after target accounting system completes the accounting operation corresponding to target accounting event, determine the accounting dimension information of target accounting event, based on accounting dimension information and accounting business mapping rule, generate the voucher of target accounting event corresponding, call the voucher entry interface of business system, and push the voucher to business system through voucher entry interface.This scheme introduces independent bridge system, fundamentally decouples accounting end and business end, ensures the real-time capture of data through multi-source event sensing technology, realizes the flexible mapping of complex business logic and accounting logic through preset rule engine, so as to solve the problem of high coupling degree, poor real-time performance and low reliability in prior art.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a method, apparatus, electronic device, and storage medium for processing financial linkage events. Background Technology

[0002] In current financial information management practices, enterprises typically deploy independent accounting systems to handle business-level expenses and costs, as well as independent bookkeeping systems (such as general ledger systems) to handle accounting-level bookkeeping and report generation.

[0003] To achieve synchronization between business data and financial data, existing technologies mainly employ the following methods: Manual import / export: Finance staff regularly export business data from the accounting system, organize it, and then manually enter it or import it using the import templates provided by the accounting system.

[0004] Point-to-point interface development: Develop customized one-to-one interfaces for specific accounting and bookkeeping systems. After completing business operations, the accounting system directly calls the bookkeeping system's interface through this interface to transfer voucher data.

[0005] However, the above-mentioned technologies have the following technical drawbacks in practical applications: Problem 1: High system coupling and high maintenance costs. With the "point-to-point interface development" approach, when multiple accounting systems need to be integrated with one accounting system, the number of interfaces forms a "network structure," growing exponentially. Any change to any system (such as upgrading the interface version in the accounting system or adjusting voucher fields in the accounting system) can cause all coupled interfaces to fail, requiring significant manpower for synchronous modification and maintenance, resulting in extremely poor flexibility.

[0006] Issue 2: Poor data real-time performance and inconsistencies between business and financial data. The "manual import / export" method relies on scheduled operations by finance personnel, resulting in significant time delays and failing to meet the requirements of real-time accounting. During critical periods such as month-end closing, this delay severely impacts the timeliness and accuracy of financial reports. Even with API-based methods, simple synchronous calls can easily lead to business processing blockages in the accounting system when the accounting system responds slowly or experiences network fluctuations, further exacerbating data synchronization delays. Summary of the Invention

[0007] To address the problems of existing technologies, embodiments of the present invention provide a method, apparatus, electronic device, and storage medium for handling accounting and financial linkage events. The technical solution is as follows: On the one hand, a method for handling accounting and financial linkage events is provided and applied to a bridging system. The method includes: Receive target accounting events sent by the target accounting system from multiple accounting systems; a target accounting event is sent by the target accounting system after completing the accounting operation corresponding to the target accounting event. Determine the accounting dimension information for the target accounting event; Based on accounting dimension information and accounting mapping rules, generate accounting vouchers corresponding to the target accounting event; Call the voucher entry interface of the accounting system to push accounting vouchers to the accounting system; accounting vouchers are used to enable the accounting system to complete the accounting operation based on the accounting vouchers.

[0008] In some possible embodiments, the bridging system includes a rules engine; Based on accounting dimension information and accounting mapping rules, accounting vouchers corresponding to the target accounting event are generated, including: The rule engine is invoked, and the target rule matching the target accounting event is determined from the accounting and accounting mapping rules based on the accounting dimension information. Generate accounting vouchers corresponding to the target accounting events based on the target rules.

[0009] In some possible embodiments, after receiving the target accounting event sent by the target accounting system in multiple accounting systems, the method further includes: Local storage is performed on the target accounting events; Return a successful event reception feedback to the target accounting system.

[0010] In some possible embodiments, after calling the voucher entry interface of the accounting system and pushing the accounting voucher to the accounting system through the voucher entry interface, the process further includes: Receive successful event processing feedback from the accounting system; successful event processing feedback is sent by the accounting system after completing the accounting operation based on the accounting voucher; Update the processing status of the target accounting event stored locally to "successfully processed".

[0011] In some possible embodiments, the method further includes: If no successful event processing feedback is received from the accounting system within the first preset time period, a retry mechanism is triggered. The retry mechanism involves repeatedly performing the push operation to the accounting system every second preset time period until the preset number of times is reached. In the event that the retry mechanism fails, an exception event is generated; Send abnormal events to preset maintenance equipment for early warning notification.

[0012] In some possible embodiments, the bridging system is an intermediary service deployed between multiple accounting and billing systems.

[0013] In some possible embodiments, the bridging system includes a Webhook interface; each of the multiple computing systems is configured with the address of the Webhook interface; Receive target accounting events sent by the target accounting system in multiple accounting systems, including: Based on the Webhook interface, it receives target computing events sent by the target computing system in multiple computing systems.

[0014] On the other hand, a financial accounting linkage event processing device is provided for use in a bridging system. The device includes: The receiving module is used to receive target accounting events sent by the target accounting system in multiple accounting systems; the target accounting event is sent by the target accounting system after completing the accounting operation corresponding to the target accounting event. The information determination module is used to determine the accounting dimension information of the target accounting event; The voucher generation module is used to generate accounting vouchers corresponding to the target accounting event based on accounting dimension information and accounting mapping rules; The sending module is used to call the voucher entry interface of the accounting system and push accounting vouchers to the accounting system through the voucher entry interface; the accounting vouchers are used to enable the accounting system to complete the accounting operation based on the accounting vouchers.

[0015] In some possible embodiments, the bridging system includes a rules engine; The voucher generation module is used for: The rule engine is invoked, and the target rule matching the target accounting event is determined from the accounting and accounting mapping rules based on the accounting dimension information. Generate accounting vouchers corresponding to the target accounting events based on the target rules.

[0016] In some possible embodiments, the apparatus further includes: The storage module is used to perform local storage of target accounting events; The sending module is used to return a successful event reception feedback to the target accounting system.

[0017] In some possible embodiments, the apparatus further includes: The receiving module is used to receive event processing success feedback from the accounting system; the event processing success feedback is sent by the accounting system after completing the accounting operation based on the accounting voucher. The information update module is used to update the processing status of the target accounting event stored locally to "successfully processed".

[0018] In some possible embodiments, the apparatus further includes an exception handling module for: If no successful event processing feedback is received from the accounting system within the first preset time period, a retry mechanism is triggered. The retry mechanism involves repeatedly performing the push operation to the accounting system every second preset time period until the preset number of times is reached. In the event that the retry mechanism fails, an exception event is generated; Send abnormal events to preset maintenance equipment for early warning notification.

[0019] In some possible embodiments, the bridging system is an intermediary service deployed between multiple accounting and billing systems.

[0020] In some possible embodiments, the bridging system includes a Webhook interface; each of the multiple computing systems is configured with the address of the Webhook interface; The receiving module is used for: Based on the Webhook interface, it receives target computing events sent by the target computing system in multiple computing systems.

[0021] On the other hand, an electronic device is provided, including a processor and a memory, wherein the memory stores at least one instruction or at least one program, and the at least one instruction or at least one program is loaded and executed by the processor to implement the above-mentioned accounting and financial linkage event processing method.

[0022] On the other hand, a computer-readable storage medium is provided, which stores at least one instruction or at least one program, wherein the at least one instruction or at least one program is loaded and executed by a processor to implement the accounting and financial linkage event processing method described above.

[0023] On the other hand, a computer program product or computer program is provided, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the aforementioned accounting and financial linkage event processing method.

[0024] This invention receives target accounting events sent by target accounting systems from multiple accounting systems. These target accounting events are sent after the target accounting system completes the corresponding accounting operation. The invention determines the accounting dimension information of the target accounting event, generates accounting vouchers corresponding to the target accounting event based on the accounting dimension information and accounting mapping rules, calls the voucher entry interface of the accounting system, and pushes the accounting vouchers to the accounting system through the voucher entry interface. The accounting vouchers are used by the accounting system to complete the accounting operation. This solution fundamentally decouples the accounting end and the accounting end by introducing an independent bridging system. It ensures real-time data capture through multi-source event perception technology and achieves flexible mapping between complex business logic and accounting logic through a preset rule engine. Thus, it solves the problems of high coupling, poor real-time performance, and low reliability in existing technologies. Attached Figure Description

[0025] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0026] Figure 1 This is a schematic diagram of an implementation environment provided by an embodiment of the present invention; Figure 2 This is a flowchart illustrating a method for handling accounting and financial linkage events provided in an embodiment of the present invention; Figure 3 This is a flowchart illustrating a method for generating accounting vouchers corresponding to a target accounting event, provided by an embodiment of the present invention. Figure 4 This is a schematic diagram of the structure of a financial accounting linkage event processing device provided in an embodiment of the present invention; Figure 5 This is a hardware structure block diagram of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0027] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and 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.

[0028] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or server that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or devices.

[0029] It is understood that in the specific embodiments of this application, data such as user information are involved. When the above embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0030] To facilitate understanding of the technical solutions described above and their resulting technical effects in the embodiments of this disclosure, the terms used in the embodiments of this disclosure are briefly introduced as follows:

[0031] An accounting system refers to a system in financial information management that processes detailed business-level data. The accounting system focuses on the original information of each specific economic activity, including quantity, amount, time of occurrence, department, project, and customer. An accounting system can include expense reimbursement systems, purchase order systems, inventory management systems, project cost accounting systems, and sales invoicing systems. Its outputs are business documents, such as expense reports, purchase receipts, sales delivery slips, and cost calculation sheets.

[0032] An accounting system refers to a system in financial information management that processes aggregated and categorized compliance data at the accounting level. It transforms business documents into accounting entries according to accounting standards, ultimately generating financial statements.

[0033] In current financial information management practices, enterprises typically deploy independent accounting systems to handle business-level expenses and costs, as well as independent bookkeeping systems (such as general ledger systems) to handle accounting-level bookkeeping and report generation.

[0034] To achieve synchronization between business data and financial data, existing technologies mainly employ the following methods: Manual import / export: Finance staff regularly export business data from the accounting system, organize it, and then manually enter it or import it using the import templates provided by the accounting system.

[0035] Point-to-point interface development: Develop customized one-to-one interfaces for specific accounting and bookkeeping systems. After completing business operations, the accounting system directly calls the bookkeeping system's interface through this interface to transfer voucher data.

[0036] However, the above-mentioned technologies have the following technical drawbacks in practical applications: When m accounting systems need to interface with n accounting systems, the maximum number of point-to-point interfaces is m × n. For a medium-sized enterprise, there might be five accounting systems (expense reimbursement, purchasing, sales, cost, and assets) that need to interface with two accounting systems (general ledger and budget). This would require developing 5 × 2 = 10 independent interfaces. With each additional system, the number of interfaces increases linearly, but the maintenance complexity increases exponentially.

[0037] The "manual import / export" method relies on the scheduled operation of finance personnel. It's impossible for them to import data immediately after every transaction; they typically handle it only during daily, weekly, or even monthly closing. After exporting the spreadsheets, manual merging, checking, formatting adjustments, and account matching are often required—a time-consuming and error-prone process. If an import fails, the error may not be discovered until the next day, requiring a review of the business documents, corrections, and re-import, creating a weekly feedback cycle.

[0038] More seriously, these two problems reinforce each other: High coupling makes the system fragile, and the system dares not easily modify the interface logic (such as adding retry or transaction compensation mechanisms). Therefore, it can only use the simplest synchronous call or manual import, which ultimately leads to poor real-time performance and inconsistency. As a result, financial staff have to spend a lot of time reconciling accounts and fixing discrepancies. As a result, business departments lose trust in financial data and rely more on manual import in order to ensure "reliability".

[0039] In summary, the essence of the shortcomings of existing technologies lies in their use of a "hard-coded, tightly coupled, stateless" communication model to balance "flexible and ever-changing business needs" and "strict financial regulations." This model is unable to adapt to rapid changes in business systems, nor can it guarantee the real-time performance, consistency, and integrity of data transmission across systems.

[0040] Please see Figure 1 The diagram shown is an implementation environment provided by an embodiment of the present invention. The implementation environment may include an accounting system 110, a bridging system 120, and an accounting system 130.

[0041] The accounting system 110 and the bridging system 120, as well as the bridging system 120 and the accounting system 130, can communicate via a network. Optionally, the accounting system 110, the bridging system 120, and the accounting system 130 can be located in the same device.

[0042] Optionally, the bridging system 120 receives target accounting events sent by target accounting systems from multiple accounting systems. These target accounting events are sent after the target accounting system completes the corresponding accounting operation. The system determines the accounting dimension information of the target accounting event, generates accounting vouchers corresponding to the target accounting event based on the accounting dimension information and accounting mapping rules, calls the voucher entry interface of the accounting system, and pushes the accounting vouchers to the accounting system through the voucher entry interface. The accounting vouchers are used by the accounting system to complete the accounting operation. This solution, by introducing an independent bridging system, fundamentally decouples the accounting end from the accounting end. Multi-source event awareness technology ensures real-time data capture, and a preset rule engine enables flexible mapping between complex business logic and accounting logic. This solves the problems of high coupling, poor real-time performance, and low reliability in existing technologies.

[0043] In one exemplary implementation, the accounting system 110, bridging system 120, and accounting system 130 can all be node devices in a blockchain system, capable of sharing acquired and generated information with other node devices in the blockchain system, thus achieving information sharing among multiple node devices. Multiple node devices in the blockchain system can be configured with the same blockchain, which consists of multiple blocks, and adjacent blocks are related, ensuring that any data tampering in any block can be detected by the next block, thereby preventing data tampering in the blockchain and guaranteeing the security and reliability of the data in the blockchain.

[0044] Please see Figure 2 The diagram shown is a flowchart illustrating a method for handling accounting and financial linkage events according to an embodiment of the present invention. This method can be applied to... Figure 1 The implementation environment shown can be the subject executing this method. Figure 1 The bridging system accounting system in the document. It should be noted that this specification provides the operational steps of the methods described in the embodiments or flowcharts, but based on conventional or non-inventive labor, more or fewer operational steps may be included. The order of steps listed in the embodiments is merely one possible execution order among many, and does not represent the only execution order. In actual system or product execution, the methods shown in the embodiments or drawings can be executed sequentially or in parallel (e.g., in a parallel processor or multi-threaded processing environment). Specifically, as shown... Figure 2 As shown, the method may include: S201: Receive target accounting events sent by the target accounting system in multiple accounting systems; the target accounting event is sent by the target accounting system after completing the accounting operation corresponding to the target accounting event.

[0045] The framework of this application embodiment may include multiple accounting systems, bridging systems and an accounting system, or it may include multiple accounting systems, bridging systems and multiple accounting systems.

[0046] Optionally, multiple accounting systems may include a loan disbursement system, an expense reimbursement system, a purchase order system, an inventory management system, a project cost accounting system, and a sales invoicing system.

[0047] In this embodiment, the bridging system is an intermediary service deployed between multiple accounting systems and (multiple or one) accounting systems. Specifically, the bridging system can be deployed within the local area network where the multiple accounting systems and (multiple or one) accounting systems reside.

[0048] In this embodiment of the application, the bridging system includes a Webhook interface, and each of the multiple computing systems is configured with the address of the Webhook interface.

[0049] Specifically, after deploying the bridging system within the local area network where multiple accounting and billing systems reside, interface parameters can be configured.

[0050] Optionally, each of the multiple computing systems can be configured with the address of the Webhook interface exposed by the bridging system, such as http: / / core-system:8080 / event.

[0051] Optionally, the bridging system can be configured with the address of the voucher entry interface provided by the accounting system, such as http: / / account-system:8081 / account.

[0052] Next, access tokens and communication ports can be configured for both systems to ensure network connectivity between the bridging system and the two systems (accounting system and accounting system).

[0053] In this embodiment, the access token is a security credential in both the accounting system and the bridging system. It is used to prove that the accounting system has permission to call the interface of the bridging system, and that the bridging system has permission to call the interface of the accounting system. The party holding the token presents it when calling the interface, and the receiving party (bridging system or accounting system) verifies it before allowing the execution of the operation (such as receiving events or entering vouchers).

[0054] In some possible embodiments, the target accounting event is sent by the target accounting system after completing the accounting operation corresponding to the target accounting event. Correspondingly, the bridging system can receive target accounting events sent by the target accounting systems in multiple accounting systems based on the Webhook interface.

[0055] Specifically, assuming the target accounting system is a loan disbursement system, after completing the loan disbursement accounting operation, the loan disbursement system calls back the Webhook interface. That is, the loan disbursement system automatically pushes a POST request to the Webhook interface of the bridging system. This POST request carries the target accounting event corresponding to the loan disbursement.

[0056] In this embodiment of the application, the target accounting event may include core parameter information such as event identifier, accounting dimension information, and timestamp.

[0057] Optionally, the accounting dimension information represents the event type. Specifically, the event type may include one or more of the business type and product type.

[0058] In some possible embodiments, when the loan disbursement system completes a loan disbursement of 50,000 yuan to customer Zhang San, contract number CON202405210001, the target accounting event pushed may include: { "eventId": "EVT_20240521_001", "eventType": "LOAN_DISBURSEMENT", "timestamp": "2024-05-21T09:30:15.123+08:00", "sourceSystem": "loan-system", "businessData": { "contractNo": "CON202405210001", "customerName": "Zhang San", "customerId": "CUST001234", "productType": "Personal Consumer Loan" "loanAmount": 50000.00, "loanTerm": 12, "repaymentMethod": "Equal principal and interest payments", "disbursementDate": "2024-05-21", "interestRate": 0.08 } }

[0059] S203: Determine the accounting dimension information for the target accounting event.

[0060] In some possible embodiments, the bridging system can parse the target accounting event to determine the accounting dimension information of the target accounting event.

[0061] In another possible embodiment, the bridging system can perform local storage on the target accounting event and return a successful event reception feedback to the target accounting system. The bridging system can then parse the target accounting event to determine its accounting dimension information.

[0062] Optionally, the bridging system can store the target accounting event as a raw event in the bridging system's local message table.

[0063] Thus, by storing the target accounting events through the bridging system, a complete basis can be provided for tracing the source of any possible anomalies.

[0064] S205: Based on accounting dimension information and accounting mapping rules, generate accounting vouchers corresponding to the target accounting event.

[0065] In this embodiment of the application, the bridging system includes a rule engine, that is, the rule engine can be configured in the bridging system as a business translator.

[0066] Optionally, standardized accounting mapping rules can be pre-entered into the rules engine within the bridging system. These accounting account mapping rules can support multi-condition combinations configured according to accounting dimensions, covering accounting business across all scenarios.

[0067] In an optional embodiment, the accounting account mapping rules can be embodied as follows: Table 1: Account Mapping Rules

[0068] Please see Figure 3 The diagram shows a flowchart of a method for generating accounting vouchers corresponding to a target accounting event according to an embodiment of the present invention, including: S2051: Call the rule engine. Through the rule engine, determine the target rule that matches the target accounting event from the accounting and accounting mapping rules based on the accounting dimension information.

[0069] In some possible embodiments, the bridging system can send the target accounting event and the corresponding accounting dimension information to the rule engine.

[0070] Taking the target accounting event in the example above as an example, the accounting dimension information is: business type = loan issuance, product type = personal consumer loan.

[0071] Optionally, the accounting dimension information can be matched against the accounting account mapping rule table mentioned above to determine the target rules as R001 and R002.

[0072] R001 includes: Debit / Credit Direction = Debit, Account Code = 130300, Summary Template = "{customerName} Loan Disbursement, Contract No. {contractNo}, Amount {loanAmount}". R002 includes: Credit / Credit Direction = Credit, Account Code = 200100, Summary Template = "{customerName} Loan Disbursement, Contract No. {contractNo}, Amount {loanAmount}".

[0073] In other possible embodiments, the bridging system can send the target accounting event to the rule engine, which then extracts the corresponding accounting dimension information from the target accounting event. After obtaining the accounting dimension information, the rule engine determines the target rule matching the target accounting event from the accounting account mapping rules based on that information.

[0074] S2053: Generate accounting vouchers corresponding to the target accounting events based on the target rules.

[0075] Optionally, the rules engine can generate accounting vouchers corresponding to the target accounting events based on the target rules.

[0076] Optionally, two accounting vouchers corresponding to R001 and R002 can be generated separately: Generate vouchers (two journal entries): { "voucherId": "VOU_20240521_001", "voucherDate": "2024-05-21", "sourceEventId": "EVT_20240521_001", "entries": [ { "entryId": "ENT_001", "accountCode": "130300", "accountName": "Loan principal amount disbursed", "debitAmount": 50000.00, "creditAmount": 0, "description": "Loan issued to Zhang San, contract number CON202405210001, amount 50,000.00 yuan" }, { "entryId": "ENT_002", "accountCode": "200100", "accountName": "Deposits Received", "debitAmount": 0, "creditAmount": 50000.00, "description": "Loan issued to Zhang San, contract number CON202405210001, amount 50,000.00 yuan" } ], "summary": "Loan disbursement - Zhang San" } S207: Call the voucher entry interface of the accounting system and push accounting vouchers to the accounting system through the voucher entry interface; accounting vouchers are used to enable the accounting system to complete the accounting operation based on the accounting vouchers.

[0077] In this embodiment of the application, the bridging system can call the voucher entry interface of the accounting system and push accounting vouchers to the accounting system through the voucher entry interface.

[0078] Optionally, accounting vouchers are used to enable the accounting system to complete accounting operations based on the accounting vouchers. Specifically, after receiving the vouchers, the accounting system can automatically perform accounting operations and update the data in the general ledger, subsidiary ledgers, and other ledgers.

[0079] In this embodiment of the application, after the accounting system completes the accounting operation based on the accounting voucher, it can send an event processing success feedback to the bridging system. In this way, the bridging system can receive the event processing success feedback from the accounting system.

[0080] Optionally, after the adjustment system receives successful event processing feedback from the government system, it can update the processing status of the target collaborative event stored locally to "successfully processed".

[0081] In this embodiment of the application, the framework built on the accounting system, bridging system and accounting system is also equipped with an exception handling mechanism.

[0082] In this embodiment, if no successful event processing feedback is received from the accounting system within a first preset time period, a retry mechanism is triggered. Optionally, if the retry mechanism fails, an abnormal event is generated and sent to a preset maintenance device for early warning notification.

[0083] In this embodiment of the application, the retry mechanism is to repeatedly perform the push operation to the accounting system every second preset time interval until the preset number of times is reached.

[0084] Optionally, the first preset time, the second preset time, and the preset number of times can be set in advance by the programmer. In some possible embodiments, the first preset time, the second preset time, and the preset number of times can be set based on the actual processing situation. The first preset time can be five minutes, the second preset time can be one minute, and the preset number of times can be three.

[0085] Specifically, if the bridging system does not receive successful event processing feedback from the accounting system due to interface timeout, error code return, or other reasons, it can trigger an automatic retry mechanism, which means repeatedly performing the push operation to the accounting system every minute until it reaches three times.

[0086] If all three attempts fail, the bridging system can generate an abnormal event containing information such as event identifier, error type, error description, and timestamp. Then, the abnormal event can be sent to the preset maintenance equipment (financial operation and maintenance platform) and a warning notification can be sent to the preset operation and maintenance personnel via message or email.

[0087] In this embodiment, the bridging system can record full-link logs throughout the entire lifecycle of the target accounting event, including normal logs and abnormal logs. This provides a complete basis for tracing the source of abnormal events in the future.

[0088] In summary, the above embodiments can achieve the following beneficial effects: (1) By deploying an independent bridging system, the accounting system and the bookkeeping system are completely decoupled. In this scheme, all accounting systems no longer need to directly call the bookkeeping system interface. Instead, they uniformly push events to the Webhook endpoint of the bridging system (such as http: / / agent:8080 / webhook / event), and the bridging system is responsible for subsequent voucher conversion and accounting calls. When the interface address of the bookkeeping system changes (for example, from http: / / account-system:8081 / account to a new address) or the voucher fields need to be adjusted, only the adaptation configuration or rule engine on the bridging system side needs to be modified, without changing the code of any accounting system. Similarly, when an accounting system upgrades or changes its interface version, other systems are not affected. This "many-to-one, one-to-many" star architecture completely breaks the mesh coupling structure of the traditional point-to-point interface, reducing maintenance costs from exponential to linear.

[0089] (2) The bridging system adopts a Webhook proactive push mechanism to replace the traditional manual import and export method. In specific implementation, after the accounting system completes business operations such as loan disbursement, repayment, and accrual, it immediately sends a POST request to the Webhook interface exposed in advance by the bridging system, carrying core parameters such as event identifier, amount, and accounting dimension. After receiving the request, the bridging system completes rule matching and voucher conversion within milliseconds and calls the voucher entry interface of the accounting system in real time to complete the accounting. The entire process from business occurrence to financial entry is controlled within milliseconds, which is more than 10,000 times more efficient than the previous time when financial personnel exported tables periodically and manually sorted and entered data. At the same time, the synchronization of business and financial data is fundamentally guaranteed, and the enterprise management can query the accurate financial status in real time.

[0090] (3) The bridging system has a built-in comprehensive exception handling mechanism to ensure the reliability and consistency of data transmission. When the bridging system receives an event pushed by the accounting system, it first stores the event completely in the local message table and can immediately return an HTTP 202 Accepted confirmation, and then enters the asynchronous processing flow. During the processing, if the call to the accounting system interface fails due to network jitter or temporary service unavailability, the bridging system will automatically trigger the retry state machine and use an exponential backoff strategy (such as 1 second, 2 seconds, 4 seconds, 8 seconds...) to automatically retry multiple times until success or the maximum number of retries is reached. For records that ultimately fail, the bridging system will not discard any data, but will mark them as failed and retain the original event and processing log completely, while actively sending a warning notification to the operation and maintenance personnel. In addition, the idempotency check of the event identifier avoids the problem of duplicate accounting caused by repeated pushes. This whole mechanism ensures that every piece of business data can ultimately be correctly accounted for or have traceable exception handling.

[0091] (4) The bridging system provides full-link logging functionality, connecting every key node of a message from its entry into the system to its final completion, forming a complete data view. Specifically, this includes: the receiving records of the original events from the accounting system, the matching process of the rule engine, the content of the generated standard vouchers, details of requests and responses to the accounting system, retry history, and the final processing status. Maintenance personnel can quickly retrieve the complete processing link of any message through a unified management console, based on conditions such as event identifier, time range, or status. When accounting failures or data inconsistencies occur, there is no need to switch back and forth between the accounting system, accounting system, and network devices for troubleshooting; only the system needs to be checked. Bridging system By viewing the full-link logs of the corresponding message, the fault point can be accurately located, which greatly simplifies the problem diagnosis and handling process.

[0092] (5) The built-in rule engine of the bridging system supports flexible configuration of multiple condition combinations, which can cover the accounting needs of different business scenarios. In practical applications, operation and maintenance or business personnel can define the mapping rules from various accounting events to accounting vouchers through configuration files. For example, they can distinguish between management expenses and sales expenses by department code, select different accounting subjects by amount threshold, and generate accounting entries in different directions by event type (loan / repayment / accrual). When the enterprise adds new business types or adjusts accounting policies, it only needs to modify or add rule configuration files. The bridging system supports hot loading without restarting the service. This flexible configuration capability enables the same middleware to serve multiple scenarios such as loan business, deposit business, and expense reimbursement at the same time, truly realizing the design goal of "one solution, full scenario coverage".

[0093] Please see Figure 4 The diagram shows a structural schematic of an accounting and financial linkage event processing device provided in an embodiment of the present invention. This device has the function of implementing the accounting and financial linkage event processing method described in the above-described method embodiment. This function can be implemented by hardware or by hardware executing corresponding software. Figure 4 As shown, the accounting and financial linkage event processing device 400 may include: The receiving module 401 is used to receive target accounting events sent by the target accounting system in multiple accounting systems; the target accounting event is sent by the target accounting system after completing the accounting operation corresponding to the target accounting event; The information determination module 402 is used to determine the accounting dimension information of the target accounting event; The voucher generation module 403 is used to generate accounting vouchers corresponding to the target accounting event based on accounting dimension information and accounting mapping rules. The sending module 404 is used to call the voucher entry interface of the accounting system and push accounting vouchers to the accounting system through the voucher entry interface; the accounting vouchers are used to enable the accounting system to complete the accounting operation based on the accounting vouchers.

[0094] In some possible embodiments, the bridging system includes a rules engine; The voucher generation module is used for: The rule engine is invoked, and the target rule matching the target accounting event is determined from the accounting and accounting mapping rules based on the accounting dimension information. Generate accounting vouchers corresponding to the target accounting events based on the target rules.

[0095] In some possible embodiments, the apparatus further includes: The storage module is used to perform local storage of target accounting events; The sending module is used to return a successful event reception feedback to the target accounting system.

[0096] In some possible embodiments, the apparatus further includes: The receiving module is used to receive event processing success feedback from the accounting system; the event processing success feedback is sent by the accounting system after completing the accounting operation based on the accounting voucher. The information update module is used to update the processing status of the target accounting event stored locally to "successfully processed".

[0097] In some possible embodiments, the apparatus further includes an exception handling module for: If no successful event processing feedback is received from the accounting system within the first preset time period, a retry mechanism is triggered. The retry mechanism involves repeatedly performing the push operation to the accounting system every second preset time period until the preset number of times is reached. In the event that the retry mechanism fails, an exception event is generated; Send abnormal events to preset maintenance equipment for early warning notification.

[0098] In some possible embodiments, the bridging system is an intermediary service deployed between multiple accounting and billing systems.

[0099] In some possible embodiments, the bridging system includes a Webhook interface; each of the multiple computing systems is configured with the address of the Webhook interface; The receiving module is used for: Based on the Webhook interface, it receives target computing events sent by the target computing system in multiple computing systems.

[0100] It should be noted that the apparatus provided in the above embodiments is only illustrated by the division of the above functional modules when implementing its functions. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the apparatus and method embodiments provided in the above embodiments belong to the same concept, and the specific implementation process can be found in the method embodiments, which will not be repeated here.

[0101] In the embodiments of this application, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.

[0102] This invention provides an electronic device including a processor and a memory. The memory stores at least one instruction or at least one program, which is loaded and executed by the processor to implement the accounting and financial linkage event processing method provided in the above method embodiments.

[0103] The memory can be used to store software programs and modules. The processor executes various functional applications and clustering results determination by running the software programs and modules stored in the memory. The memory can mainly include a program storage area and a data storage area. The program storage area can store the operating system, application programs required for functions, etc.; the data storage area can store data created according to the use of the device, etc. In addition, the memory can include high-speed random access memory, and can also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. Accordingly, the memory can also include a memory controller to provide the processor with access to the memory.

[0104] The methods and embodiments provided in this invention can be executed on a computer terminal, server, or similar computing device. Taking running on a server as an example... Figure 5 This is a hardware structure block diagram of a server for running a financial accounting linkage event processing method provided in an embodiment of the present invention, as shown below. Figure 5As shown, the server 2000 can vary significantly due to different configurations or performance. It may include one or more central processing units (CPUs) 2010 (CPUs 2010 may include, but are not limited to, microprocessors (MCUs) or programmable logic devices (FPGAs), a memory 2030 for storing data, and one or more storage media 2020 (e.g., one or more mass storage devices) for storing application programs 2023 or data 2022. The memory 2030 and storage media 2020 may be temporary or persistent storage. The program stored in the storage media 2020 may include one or more modules, each module may include a series of instruction operations on the server. Furthermore, the CPU 2010 may be configured to communicate with the storage media 2020 and execute the series of instruction operations stored in the storage media 2020 on the server 2000. Server 2000 may also include one or more power supplies 2060, one or more wired or wireless network interfaces 2050, one or more input / output interfaces 2040, and / or one or more operating systems 2021, such as Windows Server™, MacOS X™, Unix™, Linux™, FreeBSD™, etc.

[0105] The input / output interface 2040 can be used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the communication provider of server 2000. In one example, the input / output interface 2040 includes a network interface controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the input / output interface 2040 may be a radio frequency (RF) module used for wireless communication with the Internet.

[0106] Those skilled in the art will understand that Figure 5 The structure shown is for illustrative purposes only and does not limit the structure of the aforementioned electronic device. For example, the server 2000 may also include... Figure 5 The more or fewer components shown, or having the same Figure 5 The different configurations shown.

[0107] Embodiments of the present invention also provide a computer-readable storage medium, which can be disposed in an electronic device to store at least one instruction or at least one program related to implementing an accounting and financial linkage event processing method. The at least one instruction or the at least one program is loaded and executed by the processor to implement the accounting and financial linkage event processing method provided in the above-described method embodiments.

[0108] Optionally, in this embodiment, the storage medium may include, but is not limited to, various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0109] It should be noted that the order of the above embodiments of the present invention is merely for descriptive purposes and does not represent the superiority or inferiority of the embodiments. Furthermore, specific embodiments have been described above. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps described in the claims can be performed in a different order than that shown in the embodiments and still achieve the desired result. Additionally, the processes depicted in the drawings do not necessarily require a specific or sequential order to achieve the desired result. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0110] Embodiments of the present invention also provide a computer program product or computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the aforementioned accounting and financial linkage event processing method.

[0111] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the apparatus embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0112] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0113] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A method for handling accounting and financial linkage events, characterized in that, Applied to bridging systems, the method includes: Receive target accounting events sent by a target accounting system in multiple accounting systems; the target accounting event is sent by the target accounting system after completing the accounting operation corresponding to the target accounting event; Determine the accounting dimension information of the target accounting event; Based on the accounting dimension information and accounting mapping rules, accounting vouchers corresponding to the target accounting event are generated; The accounting system's voucher entry interface is invoked, and the accounting voucher is pushed to the accounting system through the voucher entry interface; the accounting voucher is used to enable the accounting system to complete the accounting operation based on the accounting voucher.

2. The accounting and financial linkage event processing method according to claim 1, characterized in that, The bridging system includes a rules engine; The step of generating accounting vouchers corresponding to the target accounting event based on the accounting dimension information and accounting mapping rules includes: The rule engine is invoked, and the target rule matching the target accounting event is determined from the accounting and accounting mapping rules based on the accounting dimension information. The accounting voucher corresponding to the target accounting event is generated according to the target rule.

3. The accounting and financial linkage event processing method according to claim 1, characterized in that, After receiving the target accounting event sent by the target accounting system in multiple accounting systems, the method further includes: Local storage is performed on the target accounting events; The system returns a successful event reception feedback to the target accounting system.

4. The accounting and financial linkage event processing method according to claim 3, characterized in that, After calling the voucher entry interface of the accounting system and pushing the accounting voucher to the accounting system through the voucher entry interface, the method further includes: The system receives a successful event processing feedback from the accounting system; the successful event processing feedback is sent by the accounting system after completing the accounting operation based on the accounting voucher. Update the processing status of the target accounting event stored locally to "successfully processed".

5. The accounting and financial linkage event processing method according to claim 4, characterized in that, The method further includes: If no successful event processing feedback is received from the accounting system within the first preset time period, a retry mechanism is triggered; the retry mechanism involves repeatedly performing the push operation to the accounting system every second preset time period until a preset number of times is reached; If the retry mechanism fails, an exception event is generated; The abnormal event is sent to the preset maintenance equipment for early warning notification.

6. The accounting and financial linkage event processing method according to any one of claims 1-5, characterized in that, The bridging system is an intermediary service deployed between the multiple accounting systems and the accounting system.

7. The accounting and financial linkage event processing method according to any one of claims 1-5, characterized in that, The bridging system includes a Webhook interface; each of the multiple computing systems is configured with the address of the Webhook interface; The receiving of target accounting events sent by the target accounting system in multiple accounting systems includes: Based on the Webhook interface, target computing events sent by target computing systems in multiple computing systems are received.

8. A financial accounting linkage event processing device, characterized in that, The device, used in bridging systems, includes: A receiving module is used to receive target accounting events sent by a target accounting system in multiple accounting systems; the target accounting event is sent by the target accounting system after completing the accounting operation corresponding to the target accounting event; The information determination module is used to determine the accounting dimension information of the target accounting event; The voucher generation module is used to generate accounting vouchers corresponding to the target accounting event based on the accounting dimension information and accounting mapping rules. The sending module is used to call the voucher entry interface of the accounting system and push the accounting voucher to the accounting system through the voucher entry interface; the accounting voucher is used to enable the accounting system to complete the accounting operation based on the accounting voucher.

9. An electronic device, characterized in that, It includes a processor and a memory, wherein the memory stores at least one instruction or at least one program, and the at least one instruction or the at least one program is loaded and executed by the processor to implement the accounting and financial linkage event processing method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores at least one instruction or at least one program, which is loaded and executed by a processor to implement the accounting and financial linkage event processing method as described in any one of claims 1 to 7.

11. A computer program, characterized in that, When the computer program is executed by the processor, it implements the accounting and financial linkage event processing method as described in any one of claims 1 to 7.

Images