Data traceability system and method based on financial traceability model

Abstract

The invention discloses a data traceability system and method based on a financial traceability model. The system comprises a target financial data mirror image acquisition module, a financial traceability model integration module and a query request response module. The target business and financial data mirror image acquisition module is used for acquiring heterogeneous business and financial data and mapping the heterogeneous business and financial data to obtain a target business and financial data mirror image; the business and financial tracing model integration module is used for acquiring a voucher serial number and front-end business data input by a user, and integrating the voucher serial number, the front-end business data and the target business and financial data mirror image to obtain a business and financial tracing model; and the query request response module is used for acquiring a plurality of query requests of the user, and responding to post scenes of the plurality of query requests through the financial tracing model to obtain a response result. According to the invention, through mapping heterogeneous business and financial data and integrating voucher and business information, a business and financial tracing model is constructed, and accurate query response is realized.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, and in particular to a data traceability method, system, terminal, and computer-readable storage medium based on a business and financial traceability model. Background Technology

[0002] Currently, large group enterprises typically use mature suite ERP software such as Oracle and SAP for financial management. The accounting module (such as General Ledger GL) provides basic ledger query and voucher viewing functions. When business-financial tracing is required (i.e., tracing from financial data to the source of business operations), traditional solutions usually involve: 1. The system provides standardized, fixed financial and business reports, or secondary development of various reports and functions on Oracle. 2. Financial personnel need to first review financial statements (e.g., trial balance), then manually switch to different business modules (e.g., purchasing, sales, inventory) based on voucher numbers and other information, call the corresponding business query reports or transaction numbers, and input specific conditions to search for and locate related business documents. 3. The entire tracing process relies on the user's in-depth understanding of multiple system modules and complex operating procedures; the data chain is broken and manually pieced together.

[0003] Traditional ERP accounting systems suffer from several shortcomings: their generic interfaces are not adapted to diverse financial roles, resulting in complex operational paths and cumbersome information filtering; business and financial traceability requires manual cross-module queries, creating data and operational breakpoints, demanding high user skills and being inefficient; the closing process is a black box, lacking transparency and relying on manual verification and offline communication; and query responses are slow when dealing with massive amounts of data, disrupting the user experience. Therefore, existing data traceability solutions require further improvement and optimization. Summary of the Invention

[0004] The main objective of this invention is to provide a data tracing method, system, terminal, and computer-readable storage medium based on a business and financial tracing model. This aims to solve the problems that existing data tracing methods are difficult to meet, such as slow business data query speed, low response efficiency, and slow query response when dealing with massive amounts of data, which can easily lead to interrupted interactive experience.

[0005] To achieve the above objectives, the present invention provides a data traceability system based on a business and financial traceability model, wherein the data traceability method based on the business and financial traceability model includes the following steps: The target business and financial data mirroring acquisition module and the business and financial traceability model integration module are respectively connected to the query request response module; The target business and financial data mirror acquisition module is used to acquire heterogeneous business and financial data, and to map the heterogeneous business and financial data according to preset real-time synchronization rules and data mapping model to obtain the target business and financial data mirror. The business and financial traceability model integration module is used to obtain the voucher number and front-end business data input by the user, and integrate the voucher number, the front-end business data and the target business and financial data mirror according to a preset mechanism to obtain the business and financial traceability model; The query request response module is used to obtain multiple query requests from users, and respond to the job scenarios of the multiple query requests through the business and financial traceability model to obtain response results.

[0006] Optionally, in the data traceability system based on the business and financial traceability model, the target business and financial data mirroring acquisition module includes a data synchronization unit and a data separation unit, wherein the data synchronization unit and the data separation unit are connected sequentially: The data synchronization unit is used to acquire heterogeneous business and financial data, and to map the heterogeneous business and financial data through preset real-time synchronization rules and data mapping models to obtain a business and financial data mirror. The data separation unit is used to perform data synchronization and read / write separation on the business and financial data mirror using real-time monitoring technology to obtain the target business and financial data mirror.

[0007] Optionally, in the data traceability system based on the business and financial traceability model, the data synchronization unit includes a heterogeneous data synchronization subunit and a data mirroring mapping subunit, wherein the heterogeneous data synchronization subunit and the data mirroring mapping subunit are connected sequentially: The heterogeneous data synchronization subunit is used to acquire heterogeneous business financial data and synchronize the heterogeneous business financial data through preset real-time synchronization rules to obtain a first business financial data mirror. The data mirroring mapping subunit is used to map the first business and financial data mirror through a data mapping model to obtain the business and financial data mirror.

[0008] Optionally, in the data traceability system based on the business and finance traceability model, the preset mechanism includes a voucher layer mechanism, a business layer mechanism, and a business and finance layer mechanism.

[0009] Optionally, the data traceability system based on the business and financial traceability model includes a business and financial traceability model integration module comprising a user data collection unit, a data partitioning unit, a data entry unit, a data classification unit, and a data integration unit, wherein the user data collection unit, the data partitioning unit, the data entry unit, the data classification unit, and the data integration unit are connected sequentially. The user data collection unit is used to acquire multiple credential serial numbers and front-end business data input by the user; The data partitioning unit is used to partition the target business data image according to the business layer mechanism and the first preset data partitioning rule to obtain partitioned data; The data entry unit is used to enter the voucher number into journal entries according to the voucher layer mechanism and the second preset data segmentation rule to obtain entry data; The data classification unit is used to classify the front-end business data according to the business layer mechanism and the third preset data sharding rule to obtain classified data; The data integration unit is used to integrate the segmented data, the journal entry data, and the classification data to obtain the business and financial traceability model.

[0010] Optionally, in the data traceability system based on the business and financial traceability model, the data segmentation includes a balance sheet, a three-column ledger, and a chronological ledger.

[0011] Optionally, in the data traceability method based on the business and financial traceability model, the query request response module includes a query response unit and a response query unit, wherein the query response unit and the response query unit are connected sequentially: The query response unit is used to obtain multiple query requests from users, and respond to the job types of the multiple query requests through the microservice application architecture of the business and finance traceability model to obtain response instructions; The response query unit is used to query the response command through the K8s cluster of the business and financial traceability model to obtain the response result.

[0012] Optionally, in the data tracing method based on the business and financial tracing model, the response query unit includes a query instruction retrieval subunit and a data retrieval subunit, wherein the query instruction retrieval subunit and the data retrieval subunit are connected sequentially: The query instruction retrieval subunit is used to query the response instruction through multiple management nodes and multiple worker nodes of the K8s cluster to obtain the query instruction; The data retrieval subunit is used to retrieve multiple metadata and multiple data storage and log monitoring data of the accounting management platform mirror database and analysis database according to the query instruction, and obtain the response results.

[0013] Furthermore, to achieve the above objectives, the present invention also provides a data traceability system based on a business and financial traceability model and a data traceability method based on a business and financial traceability model, wherein the data traceability method based on the business and financial traceability model includes: The target business and financial data mirror acquisition module acquires heterogeneous business and financial data, and maps the heterogeneous business and financial data according to preset real-time synchronization rules and data mapping model to obtain the target business and financial data mirror. The business and financial traceability model integration module obtains the voucher number and front-end business data input by the user, and integrates the voucher number, the front-end business data and the target business and financial data mirror according to a preset mechanism to obtain the business and financial traceability model; The query request response module obtains multiple query requests from users, responds to the job scenarios of the multiple query requests through the business and financial traceability model, and obtains the response results.

[0014] The data traceability method based on the business and finance traceability model, wherein the query request response module obtains multiple query requests from users, responds to the job scenarios of the multiple query requests through the business and finance traceability model, and obtains response results, and then further includes: Determine whether the response result is abnormal; If the response result is abnormal, the access path of the log monitoring data is queried according to the response result to obtain the identification code, the document code is determined according to the identification code, and the corresponding data page is navigated to according to the document code.

[0015] Furthermore, to achieve the above objectives, the present invention also provides a computer-readable storage medium, wherein the computer-readable storage medium stores a data traceability program based on a business and financial traceability model, and when the data traceability program based on the business and financial traceability model is executed by a processor, it implements the steps of the data traceability method based on the business and financial traceability model as described above.

[0016] In this invention, the data traceability system based on the business and financial traceability model includes: a target business and financial data mirror acquisition module, a business and financial traceability model integration module, and a query request response module. The target business and financial data mirror acquisition module and the business and financial traceability model integration module are respectively connected to the query request response module. The target business and financial data mirror acquisition module is used to acquire heterogeneous business and financial data, and map the heterogeneous business and financial data according to preset real-time synchronization rules and a data mapping model to obtain a target business and financial data mirror. The business and financial traceability model integration module is used to acquire the voucher number and front-end business data input by the user, and integrate the voucher number, the front-end business data, and the target business and financial data mirror according to a preset mechanism to obtain a business and financial traceability model. The query request response module is used to acquire multiple query requests from the user, and respond to the multiple query requests for different job scenarios through the business and financial traceability model to obtain response results. This invention constructs a business and financial traceability model by mapping heterogeneous business and financial data and integrating vouchers and business information, achieving accurate query response for multiple job scenarios. Attached Figure Description

[0017] Figure 1 This is a schematic diagram of the principle of the data traceability system based on the business and financial traceability model of the present invention; Figure 2 This is a flowchart of the management platform of a preferred embodiment of the data traceability system based on the business and financial traceability model of the present invention; Figure 3 This is another specific schematic diagram of the data traceability system based on the business and financial traceability model of the present invention; Figure 4 This is a schematic diagram of the network topology of a preferred embodiment of the data traceability system based on the business and financial traceability model of the present invention; Figure 5 This is a schematic diagram of the management platform technical architecture of a preferred embodiment of the data traceability system based on the business and financial traceability model of the present invention; Figure 6 This is a schematic diagram of a K8s cluster representing a preferred embodiment of the data traceability system based on the business and financial traceability model of the present invention. Figure 7 This is a schematic diagram of the storage and database of a preferred embodiment of the data traceability system based on the business and financial traceability model of the present invention; Figure 8 This is a schematic diagram of the analysis database of a preferred embodiment of the data traceability system based on the business and financial traceability model of the present invention; Figure 9 This is a schematic diagram illustrating data integration of a preferred embodiment of the data traceability system based on the business and financial traceability model of the present invention; Figure 10 This is a schematic diagram of logs and monitoring of a preferred embodiment of the data traceability system based on the business and financial traceability model of the present invention; Figure 11 This is a schematic diagram of the processing flow in a preferred embodiment of the data traceability method based on the business and financial traceability model of the data traceability system based on the business and financial traceability model of the present invention. Detailed Implementation

[0018] To make the objectives, technical solutions, and advantages of this invention clearer and more explicit, the invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

[0019] It should be noted that if the embodiments of the present invention involve directional indicators (such as up, down, left, right, front, back, etc.), the directional indicators are only used to explain the relative positional relationship and movement of the components in a certain specific posture (as shown in the figure). If the specific posture changes, the directional indicators will also change accordingly.

[0020] Furthermore, if the embodiments of this invention involve descriptions such as "first" or "second," these descriptions are for descriptive purposes only and should not be construed as indicating or implying their relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature defined with "first" or "second" may explicitly or implicitly include at least one of those features. Additionally, the technical solutions of the various embodiments can be combined with each other, but this must be based on the ability of those skilled in the art to implement them. If the combination of technical solutions is contradictory or impossible to implement, it should be considered that such a combination of technical solutions does not exist and is not within the scope of protection claimed by this invention.

[0021] One embodiment of the data visualization display system described in the preferred embodiment of the present invention includes, as follows: Figure 1 and Figure 2 As shown, the data visualization display system includes: a target business and financial data mirror acquisition module 10, a business and financial traceability model integration module 20, and a query request response module 30; the target business and financial data mirror acquisition module 10 and the business and financial traceability model integration module 20 are respectively connected to the query request response module 30.

[0022] The target business and financial data mirror acquisition module 10 is used to acquire heterogeneous business and financial data, and map the heterogeneous business and financial data according to preset real-time synchronization rules and data mapping model to obtain a target business and financial data mirror; the business and financial traceability model integration module 20 is used to acquire the voucher number and front-end business data input by the user, and integrate the voucher number, the front-end business data and the target business and financial data mirror according to a preset mechanism to obtain a business and financial traceability model; the query request response module 30 is used to acquire multiple query requests from the user, and respond to the job scenarios of the multiple query requests through the business and financial traceability model to obtain response results.

[0023] For example, such as Figure 2 As shown, the process logic is as follows: user query request → query response unit job scenario identification → response query unit K8s cluster scheduling → data retrieval subunit multi-source data retrieval → return response result → if an exception occurs, closed-loop processing is triggered.

[0024] Specifically, the technical architecture and shortcomings of traditional business and finance systems are shown in Table 1: Table 1: Technical Architecture and Defects of Traditional Business and Finance Systems

[0025] like Figure 3As shown, another specific embodiment of the data visualization display system in this invention includes: a target business and financial data mirror acquisition module 10, a business and financial traceability model integration module 20, and a query request response module 30; the target business and financial data mirror acquisition module 10 and the business and financial traceability model integration module 20 are respectively connected to the query request response module 30.

[0026] Specifically, the target business and financial data mirroring acquisition module 10 includes a data synchronization unit 101 and a data separation unit 102, wherein the data synchronization unit 101 and the data separation unit 102 are connected sequentially. It acquires heterogeneous business and financial data, maps the heterogeneous business and financial data using preset real-time synchronization rules and a data mapping model to obtain a business and financial data mirror, and performs data synchronization and read / write separation on the business and financial data mirror using real-time monitoring technology to obtain the target business and financial data mirror. (A database twin system is built using real-time monitoring technology to achieve real-time data synchronization and read / write separation with the Oracle ERP production environment, forming a highly available mirrored data environment.) Figure 3 In the core display module, the hierarchical relationship between the modules and units is shown. The data synchronization unit receives heterogeneous data source input, maps it, and then transmits it to the data separation unit, ultimately generating a target business data mirror.

[0027] Specifically, the data synchronization unit 101 includes a heterogeneous data synchronization subunit 1011 and a data mirroring mapping subunit 1012, wherein the heterogeneous data synchronization subunit 1011 and the data mirroring mapping subunit 1012 are connected in sequence to acquire heterogeneous business financial data, synchronize the heterogeneous business financial data through preset real-time synchronization rules to obtain a first business financial data mirror, and map the first business financial data mirror through a data mapping model to obtain a business financial data mirror.

[0028] In this embodiment, as Figure 4 As shown, the data flow path is: external data source (ERP / expense database) → data integration cluster → storage and database (MySQL / REDIS / MinIO) → microserver cluster → analysis database cluster → user A / user B; Nginx is responsible for reverse proxy, and the link tracing and log service monitors the data flow in real time. Furthermore, the system achieves millisecond-level query response for hundreds of millions of account balances across the entire group, supporting multi-dimensional financial ledger penetration queries, including full-level project summaries. In addition, the system provides a highly user-friendly and scenario-based interactive interface and efficient data export function, which can generate result files within seconds. This results in an overall improvement of financial accounting query efficiency by up to nearly 4000 times compared to the past, completely breaking through the technical bottleneck of second-level retrieval of trillions of data points, significantly improving the efficiency of financial accounting queries, and effectively solving the performance bottleneck of massive data retrieval.

[0029] For example, existing data synchronization: full synchronization at night (time: 00:00-04:00); real-time data synchronization: real-time data monitoring, database-side solution: notify DBA, freeze synchronization account; business-side solution: stop data synchronization task, stop data synchronization process.

[0030] Specifically, the business and financial traceability model integration module 20 includes a user data collection unit 201, a data partitioning unit 202, a data entry unit 203, a data classification unit 204, and a data integration unit 205. The user data collection unit 201, the data partitioning unit 202, the data entry unit 203, the data classification unit 204, and the data integration unit 205 are sequentially connected to each other, acquiring multiple voucher serial numbers and front-end business data input by the user (achieving complete penetration query between general ledger books, and from general ledger books to voucher serial numbers, and then to front-end business data). The business and finance layer mechanism and the first preset data sharding rule divide the target business and finance data mirror into partitioned data (account balance sheet, three-column detailed ledger, and chronological ledger). According to the voucher layer mechanism and the second preset data sharding rule, the voucher serial number is entered into journal entries to obtain journal entry data (multiple accounting entries). According to the business layer mechanism and the third preset data sharding rule, the front-end business data is classified to obtain classified data. The partitioned data, the journal entry data, and the classified data are integrated to obtain the business and finance traceability model. The preset mechanism includes the voucher layer mechanism, the business layer mechanism, and the business and finance layer mechanism.

[0031] In this embodiment, the account balance sheet, at the end of a specific accounting period (such as the end of the month or year), is the collection of balances of all general ledger accounts and forms the basis for preparing the balance sheet and income statement. It presents the summary and net results of each accounting item at a specific point in time. The hierarchical summary structure of the accounts forms the core framework for top-down tracing and analysis of financial data. First-level account summaries provide a strategic-level financial view, such as the total amount of "accounts receivable," reflecting the overall size of the enterprise in that asset class. Second-level accounts undergo initial business segmentation within this framework, such as breaking down "bank deposits" into deposits of different currencies, serving high-level management analysis. Third-level accounts further align with operations, such as subdividing "bank deposits" into specific branch information, supporting refined management. Finally, the detailed accounts, which are summaries of the fourth-level accounts, reach the endpoint of financial data tracing; their balances are directly derived from the summation of all journal entries using that account. This hierarchical design, from level one to four, is essentially a continuum from total financial figures to business facts. The summaries at each level strictly govern the sums of the details at their subordinate levels, ensuring that summary data at any level can be systematically drilled down to the most specific transaction vouchers and business entities. Three-column ledgers and chronological ledgers are detailed records of general ledger accounts, aggregated according to the chronological order of transactions (essentially journal entries) or accounting objects (such as customers, suppliers, and projects). They establish a link between general ledger data and specific business objects / periods. Ledger tracing begins here, starting from the result or status. Simultaneously, by querying the detailed ledgers under specific general ledger accounts, three-column ledgers and chronological ledgers can break down the summary balance into a series of increase and decrease records constituting that balance. Tracing from the account balance sheet to the three-column ledger, the system automatically retrieves all detailed transaction records for that account within the corresponding period using "account code" + "accounting period" as filtering conditions, achieving accurate reconciliation between summary data and detailed data. Each record in the three-column ledger is accompanied by a voucher number and voucher date, which are key links to the chronological ledger. When drilling down based on a specific detail record, the system will extract the chronological ledger for that record containing "voucher number + voucher date + accounting period" to view the complete business voucher corresponding to that detail, clarifying all account relationships and the original business background of this accounting transaction.

[0032] Furthermore, accounting vouchers are accounting documents prepared based on verified original documents, containing clear accounting entries (debit accounts, credit accounts, and amounts). They are the direct basis for translating economic transactions into accounting language and recording them in the books. Tracing back to accounting vouchers from chronological ledgers or three-column subsidiary ledgers is another crucial verification path based on time sequence and transaction flow, following the tracing from the trial balance. Unlike the "static summary" perspective of the trial balance, chronological ledgers provide a complete flow record of all accounting entries arranged strictly in chronological order of business occurrence. The core of its tracing logic lies in the fact that any chronological ledger record is itself a microcosm of an accounting voucher, and the two are directly and precisely linked through a unique voucher number or system index number.

[0033] Specifically, the drill-down paths between different financial ledger levels, and from the ledger level to the voucher level, are shown in Table 2: Table 2: Drill-down paths between different financial ledger levels, and from the ledger level to the voucher level.

[0034] Furthermore, tracing vouchers back to original business documents is a core process for ERP systems to achieve business-finance integration and closed-loop audit evidence. This process is not simply document association, but relies on the system proactively establishing strong correlation indexes through built-in business logic and data structures when generating vouchers. This system enables tracing back to associated business information through the journal entry of any voucher. For example, a voucher of the type "Debit: Inventory, Credit: Accrued Payables" can be linked to a purchase order number, allowing for one-click retrieval of the complete purchase order, supplier information, material information, and payment details, thereby understanding the complete background and business substance. This is tailored to different business types and specific scenarios.

[0035] As an example, by building a unified data docking and synchronization engine, data from business systems such as ERP and expense reporting platforms are collected and integrated in real time or on a regular schedule, covering nine core business modules including receiving, inventory, sales, expense reporting, human resources, projects, supervision, assets, and customer service. Specifically, it traces material vouchers to purchase orders and expense reports; traces inventory vouchers to material inbound and outbound details and related business document chains; traces accounts receivable / settlement vouchers to settlement statements and receipt verification records; traces expense reporting vouchers to expense reports and purchase orders; traces payroll vouchers to full payroll batch data; traces project vouchers to miscellaneous information and specific projects; traces supervision vouchers to projects and receipt verification information; traces asset vouchers to asset cards and business documents (categorized data, including receiving slips, expense reports, and inbound slips); and traces customer service system vouchers to detailed data and performs automatic amount verification. A total of 368 integrated business and finance scenarios were connected, incorporating more than 22,000 key business data entities. A unified business and finance data mapping and association engine was built, realizing end-to-end data connectivity across core business modules. It can automatically locate and connect the full-link information on the business side based on the line-level amount of financial vouchers, thereby forming a complete and traceable business-finance closed-loop traceability chain (business and finance traceability model) while ensuring data consistency and auditability.

[0036] In this embodiment, the system uses business substance as the anchor point and employs a structured identification method based on both "voucher type" and "business object." The system pre-configures a unique standardized voucher template (i.e., voucher type) for each core business process (such as sales, procurement, expense reimbursement, and asset depreciation). This template mandates the corresponding debit and credit accounting subjects for this type of business, ensuring automatic logical matching between financial records and business events. Simultaneously, each voucher is automatically bound to the specific business entity that triggered it (such as customer, supplier, material, cost center, or project), thus fully embedding business traceability information into the financial records. The essence of this classification rule is to systematically link discrete accounting vouchers to continuous business processes through standardized business rules, establishing a traceability foundation from business to financial data. The current level of business and financial data management is relatively high, with nearly 40 standardized voucher categories.

[0037] Furthermore, the granularity rule for voucher generation, which determines "how much business data is aggregated to generate one accounting voucher," is a core standard. Its fundamental principle is to map a complete, independent business transaction unit (such as a sales order, a purchase receipt, or an expense reimbursement form) to a financial posting unit. This system employs two voucher generation modes: summary transmission and detailed transmission. The first is the summary transmission mode. For continuous, high-frequency business events, such as purchase orders, a single voucher is generated based on the period in which the event occurs, maintaining the financial integrity of the business event and improving processing efficiency. The second is the detailed transmission mode. For each independent, clearly defined business event, such as an employee expense reimbursement form, regardless of the number of expense details it contains, an independent voucher is generated to ensure direct correspondence with independent approval flows, payment actions, and audit trails. This design ensures that financial records and business processes are logically and strictly mirrored, allowing each voucher to be clearly traced to a specific business source. Regarding voucher serial number rules, to ensure the sequentiality and non-repeatability of vouchers, the current method is to generate them using "company code + year + serial number". In group-based or multi-company structures, the company code is the primary distinguishing key. It ensures complete isolation of voucher number ranges for different legal entities (such as "Company A" and "Company B") and directly supports financial reporting and access control by company. The year enables annual reset and archiving of voucher numbers. The inclusion of the year allows serial numbers to restart from 1 in each accounting year, avoiding the management complexity and system limitations caused by infinitely growing numbers. It also intuitively reflects the accounting period to which the voucher belongs. Within a given company code and year dimension, the serial number provides a continuous, unique, and incremental sequence number. This is the core identifier of the voucher, automatically assigned and managed by the system (through the "number range" function).

[0038] As an example, based on the core logic of ERP's integrated business and finance system, the system uses a dual classification standard—business-assigned module and business-finance conversion association attributes—to accurately classify the front-end business data of nine major business sub-modules: procurement, inventory, expense reimbursement, sales, assets, customer service, miscellaneous projects, supervision, and human resources. The specific classification criteria are shown in the table below. The first-level classification is based on the business-assigned module: Based on the origin of the business event, front-end data is directly assigned to the corresponding business sub-module, forming a first-level business classification. For example, purchase order generation data is classified as "Procurement," inventory inbound / outbound operation data as "Inventory," and employee expense reimbursement data as "Expense Reimbursement," ensuring a one-to-one correspondence between data and business scenarios. The second-level classification is based on business-finance conversion association attributes: Under each business sub-module, different business events trigger preset business-finance conversion rules, forming a second-level business classification. Under the second-level business classification, the system extracts core accounting elements from the business data based on the rules (such as transaction amount, counterparties, business type, etc.) and associates them with corresponding financial attribute tags, automatically generating standardized financial vouchers containing debit and credit accounts, voucher summaries, and accounting dimensions.

[0039] Specifically, the business classification data is shown in Table 3: Table 3: Business Category Data

[0040] Specifically, the query request response module 30 includes a query response unit 301 and a response query unit 302, wherein the query response unit 301 and the response query unit 302 are connected in sequence to obtain multiple query requests from users, respond to the job types of the multiple query requests through the microservice application architecture of the business and finance traceability model to obtain response instructions, and query the response instructions through the K8s cluster of the business and finance traceability model to obtain response results.

[0041] Specifically, the response query unit 302 includes a query instruction retrieval subunit 3021 and a data retrieval subunit 3022, wherein the query instruction retrieval subunit 3021 and the data retrieval subunit 3022 are connected sequentially. The response instruction is queried through multiple management nodes and multiple worker nodes of the K8s cluster to obtain the query instruction. Based on the query instruction, multiple metadata and multiple data storage and log monitoring data of the accounting management platform mirror database and analysis database are retrieved to obtain the response result.

[0042] In this embodiment, as Figure 2The diagram illustrates the overall process of a microservice application architecture based on Kubernetes (K8s). The system centers on microservice applications and encompasses functional modules such as service gateway, access control, ledger query, voucher tracing, month-end closing, closing monitoring, and a registry center. These services are deployed on a K8s cluster consisting of 3 management nodes and 5 worker nodes. The architecture includes a message center responsible for handling logs and monitoring, database sharding, data tracing, message queues, and metadata and data storage. Furthermore, the system includes an account management platform mirror database and an Oracle EBS system database, both encompassing database, cache, and object storage. A data integration module enables unified processing of streaming data, batch data, and data synchronization, supporting end-to-end data flow and business collaboration.

[0043] For example, such as Figure 5 and Figure 6 As shown, Kubernetes uses Rancher RKe2, referencing the New CIS project group; it provides rich features such as an application store, monitoring and alerting, and log collection, simplifying application deployment and management; it supports multi-cloud and hybrid cloud environments, enabling unified management of multiple Kubernetes clusters and reducing operational costs; it integrates various security features and has passed multiple security certifications and compliance reviews, such as user authentication, access control, and image security scanning. Figure 5 As shown, the microservice application is deployed on a Kubernetes cluster. It receives requests through the Gateway, verifies permissions, and then distributes them to the corresponding services (e.g., ledger query / voucher tracing). The data integration module implements streaming / batch data synchronization, and the logging and monitoring module records the entire process status, such as... Figure 6 As shown, three management nodes (10.9.11.128-130) are responsible for cluster scheduling, monitoring, and resource management, while five worker nodes (10.9.11.131-135) deploy microservice application Pods, with load balancing distributed according to service type. Figure 7 As shown, the database management system uses the open-source MySQL 8 database, which has a good ecosystem and is easy to integrate with data integration tools; the caching database uses the industry-standard open-source high-performance key-value database Redis; and the object storage uses the open-source high-performance object storage MinIO. Among them, the Oracle database stores core business data, MySQL stores structured financial data, Redis caches hot query data (cache hit rate ≥85%), and MinIO stores object data (such as report files and attachments). Data is stored with multiple replicas to ensure high availability.

[0044] Furthermore, such as Figure 8As shown, Doris offers high performance: supporting sub-second queries to meet real-time analysis needs, such as processing 10 billion rows of data daily in advertising reports, handling tens of thousands of concurrent queries with a latency of 150ms; efficient data processing: supporting multiple data sources for fast data loading and synchronization; continuous kernel updates with over 600 kernel contributors contributing over 160 PRs weekly; ease of use and compatibility: compatible with the MySQL protocol, supporting standard SQL, and rich community resources; scalable architecture: easily horizontally scalable; high availability and stability: multi-replica data storage with automatic repair; streaming data (10.9.11.143-144) for real-time synchronization, and batch data (10.9.11.145-147) for full synchronization; supports multiple task types including Shell, SQL, and Spark; workflows can be configured via drag and drop; and real-time monitoring metrics such as synchronization task QPS and data volume are provided.

[0045] In this embodiment, as Figure 9 As shown, for example: users can define complex workflows through drag-and-drop; rich task types; multiple task types including Shell, SQL, MapReduce, Spark, Python, Sub_Process, Procedure, etc.; decentralized multi-Master and multi-Worker service peer-to-peer architecture; support for scheduled and manual scheduling based on cron expressions; providing configuration options such as task dependencies, priorities, and failure policies; an open-source distributed data integration platform designed specifically for large-scale data processing; rich connectors, with hundreds of connectors already available, such as MySQL, Oracle, Kafka, Rabbit MQ, etc.; providing rich data processing and transformation plugins; such as SQL converters, field mapping, aggregation converters, filters, script converters, etc.; and providing comprehensive real-time monitoring functions, intuitively understanding the amount, size, QPS, etc., of data read and written by synchronous tasks. Figure 9 As shown, streaming data (10.9.11.143-144) processes real-time synchronized data, while batch data (10.9.11.145-147) processes full synchronized data. It supports multiple task types such as Shell, SQL, and Spark. Workflows can be configured by dragging and dropping, and real-time monitoring metrics such as synchronization task QPS and data volume are provided.

[0046] Furthermore, such as Figure 10As shown, the system includes: Distributed Tracing: Distributed tracing uses the top-level Apache SkyWalking project, designed specifically for microservices and cloud-native architectures; it provides real-time performance metrics such as request volume, response time, and error rate for each service; it records the services and components each request passes through, as well as the time spent by each request in each component; Log Collection: Fluent Bit is an open-source, lightweight log data collector and converter; Log Storage: Elasticsearch can store, retrieve, and analyze data in real time; Log Analysis: Kibana is used to perform efficient searching, visualization, and analysis of indexed data in Elasticsearch, such as... Figure 10 As shown, the tracing mechanism uses Apache SkyWalking to record the services a request passes through and the time it takes. Logs are collected through Fluent Bit, stored in Elasticsearch, and retrieved and visualized using Kibana. It also supports configuration of anomaly alerts.

[0047] Furthermore, based on Figure 1 The data traceability system based on the business and financial traceability model shown in the present invention, and the data traceability method based on the business and financial traceability model of the preferred embodiment of the present invention, are as follows: Figure 11 As shown, the data traceability method based on the business and financial traceability model includes the following steps: Step S10: The target business and financial data mirror acquisition module acquires heterogeneous business and financial data, and maps the heterogeneous business and financial data according to the preset real-time synchronization rules and data mapping model to obtain the target business and financial data mirror.

[0048] Step S20: The business and financial traceability model integration module obtains the voucher number and front-end business data input by the user, and integrates the voucher number, the front-end business data and the target business and financial data mirror according to a preset mechanism to obtain the business and financial traceability model.

[0049] Step S30: The query request response module obtains multiple query requests from the user, responds to the job scenarios of the multiple query requests through the business and financial traceability model, and obtains the response results.

[0050] Furthermore, after step S30, the method further includes determining whether the response result is abnormal. If the response result is abnormal, the method queries the access path of the log monitoring data based on the response result to obtain an identification code, determines the document code based on the identification code, and navigates to the corresponding data page based on the document code.

[0051] In this embodiment, the checkout inspection provides a guided, closed-loop collaborative method for handling checkout anomalies. The system not only automatically scans and identifies inconsistencies in business and financial data, but more importantly, it constructs a collaborative workflow from problem discovery to problem localization, ultimately guiding the process to problem resolution. This significantly reduces the costs of manual switching, verification, and communication between different systems. For each anomaly record detected, the system synchronously obtains and stores the unique identifier and access path of its corresponding source business document. Clicking on the document code in each row of the anomaly list automatically navigates to the corresponding document details page.

[0052] As an example, by defining standardized closing stages and progress quantification methods, the system provides users at different roles and levels within the group with a global view and detailed insights that match their responsibilities, achieving centralized and transparent management of closing work. The data page provides a group-wide closing overview, displaying a distribution chart of the closing progress of all subsidiaries from a group-wide perspective (e.g., using different colored dots to represent the number of companies in different progress intervals), as well as the group's overall average progress percentage. The group overview interface supports interactive drill-down, allowing users to directly click on a company name or dot to jump directly to and focus on the closing details page of that specific company, displaying the specific completion status of the company's seven standard closing points, listing the completion time and responsible person for each item. This view focuses on the implementation of specific tasks, providing multi-level views for group consolidation positions, individual company closing accountants, and financial management personnel of each parent company to view the corresponding progress and status.

[0053] Specifically, the performance test benchmark data is shown in Table 4: Table 4: Performance Test Benchmark Data

[0054] In summary, this invention provides a data traceability system and method based on a business and financial traceability model. The method includes: acquiring heterogeneous business and financial data; mapping the heterogeneous business and financial data according to preset real-time synchronization rules and a data mapping model to obtain a target business and financial data mirror; acquiring user-inputted voucher numbers and front-end business data; integrating the voucher numbers, the front-end business data, and the target business and financial data mirror according to a preset mechanism to obtain a business and financial traceability model; acquiring multiple query requests from the user; and responding to multiple job scenarios of the query requests through the business and financial traceability model to obtain response results. This invention constructs a business and financial traceability model by mapping heterogeneous business and financial data and integrating vouchers and business information, achieving accurate query responses for multiple job scenarios.

[0055] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal system that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or terminal system. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or terminal system that includes that element.

[0056] Of course, those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware (such as a processor, controller, etc.). The program can be stored in a computer-readable storage medium, and when executed, it can include the processes described in the above method embodiments. The computer-readable storage medium can be a memory, magnetic disk, optical disk, etc.

[0057] It should be understood that the application of the present invention is not limited to the examples above. Those skilled in the art can make improvements or modifications based on the above description, and all such improvements and modifications should fall within the protection scope of the appended claims.

Claims

1. A data traceability system based on a business and financial traceability model, characterized in that, The data tracing system based on the business and financial tracing model includes: a target business and financial data mirror acquisition module, a business and financial tracing model integration module, and a query request response module; The target business and financial data mirroring acquisition module and the business and financial traceability model integration module are respectively connected to the query request response module; The target business and financial data mirror acquisition module is used to acquire heterogeneous business and financial data, and to map the heterogeneous business and financial data according to preset real-time synchronization rules and data mapping model to obtain the target business and financial data mirror. The business and financial traceability model integration module is used to obtain the voucher number and front-end business data input by the user, and integrate the voucher number, the front-end business data and the target business and financial data mirror according to a preset mechanism to obtain the business and financial traceability model; The query request response module is used to obtain multiple query requests from users, and respond to the job scenarios of the multiple query requests through the business and financial traceability model to obtain response results.

2. The data traceability system based on the business and financial traceability model according to claim 1, characterized in that, The target business data mirroring acquisition module includes a data synchronization unit and a data separation unit, wherein the data synchronization unit and the data separation unit are connected in sequence: The data synchronization unit is used to acquire heterogeneous business and financial data, and to map the heterogeneous business and financial data through preset real-time synchronization rules and data mapping models to obtain a business and financial data mirror. The data separation unit is used to perform data synchronization and read / write separation on the business and financial data mirror using real-time monitoring technology to obtain the target business and financial data mirror.

3. The data traceability system based on the business and financial traceability model according to claim 2, characterized in that, The data synchronization unit includes a heterogeneous data synchronization subunit and a data mirroring mapping subunit, wherein the heterogeneous data synchronization subunit and the data mirroring mapping subunit are connected sequentially: The heterogeneous data synchronization subunit is used to acquire heterogeneous business financial data and synchronize the heterogeneous business financial data through preset real-time synchronization rules to obtain a first business financial data mirror. The data mirroring mapping subunit is used to map the first business and financial data mirror through a data mapping model to obtain the business and financial data mirror.

4. The data traceability system based on the business and financial traceability model according to claim 1, characterized in that, The preset mechanism includes a certificate layer mechanism, a business layer mechanism, and a business and finance layer mechanism.

5. The data traceability system based on the business and financial traceability model according to claim 4, characterized in that, The business and financial traceability model integration module includes a user data collection unit, a data segmentation unit, a data entry unit, a data classification unit, and a data integration unit, wherein the user data collection unit, the data segmentation unit, the data entry unit, the data classification unit, and the data integration unit are connected sequentially. The user data collection unit is used to acquire multiple credential serial numbers and front-end business data input by the user; The data partitioning unit is used to partition the target business data image according to the business layer mechanism and the first preset data partitioning rule to obtain partitioned data; The data entry unit is used to enter the voucher number into journal entries according to the voucher layer mechanism and the second preset data segmentation rule to obtain entry data; The data classification unit is used to classify the front-end business data according to the business layer mechanism and the third preset data sharding rule to obtain classified data; The data integration unit is used to integrate the segmented data, the journal entry data, and the classification data to obtain the business and financial traceability model.

6. The data traceability system based on the business and financial traceability model according to claim 5, characterized in that, The data segmentation includes account balance sheets, three-column detailed ledgers, and chronological ledgers.

7. The data traceability system based on the business and financial traceability model according to claim 6, characterized in that, The query request response module includes a query response unit and a response query unit, wherein the query response unit and the response query unit are connected sequentially: The query response unit is used to obtain multiple query requests from users, and respond to the job types of the multiple query requests through the microservice application architecture of the business and finance traceability model to obtain response instructions; The response query unit is used to query the response command through the K8s cluster of the business and financial traceability model to obtain the response result.

8. The data traceability system based on the business and financial traceability model according to claim 7, characterized in that, The response query unit includes a query instruction retrieval subunit and a data retrieval subunit, wherein the query instruction retrieval subunit and the data retrieval subunit are connected sequentially: The query instruction retrieval subunit is used to query the response instruction through multiple management nodes and multiple worker nodes of the K8s cluster to obtain the query instruction; The data retrieval subunit is used to retrieve multiple metadata and multiple data storage and log monitoring data of the accounting management platform mirror database and analysis database according to the query instruction, and obtain the response results.

9. A data traceability method based on the business and financial traceability model of the data traceability system according to any one of claims 1-8, characterized in that, The data tracing method based on the business and financial tracing model includes: The target business and financial data mirror acquisition module acquires heterogeneous business and financial data, and maps the heterogeneous business and financial data according to preset real-time synchronization rules and data mapping model to obtain the target business and financial data mirror. The business and financial traceability model integration module obtains the voucher number and front-end business data input by the user, and integrates the voucher number, the front-end business data and the target business and financial data mirror according to a preset mechanism to obtain the business and financial traceability model; The query request response module obtains multiple query requests from users, responds to the job scenarios of the multiple query requests through the business and financial traceability model, and obtains the response results.

10. The data traceability method based on the business and financial traceability model according to claim 9, characterized in that, The query request response module acquires multiple query requests from users, responds to the job scenarios of the multiple query requests through the business and financial traceability model, obtains response results, and then further includes: Determine whether the response result is abnormal; If the response result is abnormal, the access path of the log monitoring data is queried according to the response result to obtain the identification code, the document code is determined according to the identification code, and the corresponding data page is navigated to according to the document code.

Images