Tax declaration method and device based on dynamic rule engine, medium and product

Abstract

A tax filing method, apparatus, medium, and product based on a dynamic rule engine, relating to the field of computer technology, is disclosed. This method acquires tax form data to be filed, and through a dynamic rule engine, converts the tax form data into conversion parameters conforming to the format specifications of the automated filing interface based on pre-configured parameter mapping rules. The conversion parameters are then filled into the parameter structure of the automated filing interface to obtain the filing message. The filing message is then sent to the e-tax bureau system through the automated filing interface. This not only automates tax filing and significantly reduces the time cost of tax filing, but also, through the configured parameter mapping rules, it can adapt to different tax management systems. Even if the tax filing rules change, there is no need to redevelop the interface; only the corresponding parameter mapping rules need to be configured, which can significantly reduce operation and maintenance costs.

Description

Technical Field

[0001] The technical solution relates to the field of computer technology, specifically to a tax declaration method, device, medium, and product based on a dynamic rule engine. Background Technology

[0002] Currently, although tax return forms for various tax types can be generated through the tax management information system, after the tax forms are generated, subsequent operations such as data entry, declaration, and payment still require manual input through the e-tax bureau. Companies need to manually enter the tax form information generated by their internal tax system into the e-tax bureau, which is not only inefficient but also extremely prone to errors. Furthermore, due to regional differences and frequent updates to the declaration rules for different tax types, the manual maintenance costs are extremely high. Summary of the Invention

[0003] This content section is provided to briefly introduce the concepts, which will be described in detail in the subsequent specific examples section. This content section is not intended to identify key or essential features of the claimed technical solution, nor is it intended to limit the scope of the claimed technical solution.

[0004] Firstly, a tax filing method based on a dynamic rule engine is provided, including: Obtain the tax return data to be filed; The dynamic rule engine converts the tax form data into conversion parameters that conform to the format specifications of the automated filing interface based on pre-configured parameter mapping rules. The automated filing interface is an interface provided by the e-tax bureau system, and the parameter mapping rules are used to describe the mapping relationship between the tax form fields and the parameters of the automated filing interface. The conversion parameters are filled into the parameter structure of the automated declaration interface to obtain the declaration message; The declaration message is sent to the electronic tax bureau system through the automated declaration interface.

[0005] Optionally, the step of converting the tax form data into conversion parameters conforming to the format specifications of the automated filing interface through a dynamic rule engine based on pre-configured parameter mapping rules includes: Based on the tax return data submitted in the previous period, the tax return data to be submitted is verified to obtain the verification results. If the verification result indicates that the tax form data to be declared has passed the verification, the tax form data is converted into conversion parameters that conform to the format specifications of the automated declaration interface through the dynamic rule engine based on the pre-configured parameter mapping rules.

[0006] Optionally, the parameter mapping rules are obtained through the following steps: Obtain the rule document for the automated declaration interface, wherein the rule document describes the interface parameter specifications of the automated declaration interface; Parse the rule document and extract the field metadata included in the rule document; Based on the field metadata, a mapping suggestion is generated using a large language model. The mapping suggestion includes the mapping relationship between the parameter field corresponding to the field metadata and the corporate tax form field, and the confidence level between the mapping relationship. The corporate tax form field is predicted by the large language model. Retrieve the set of tax table fields corresponding to the enterprise's tax table data; Based on the mapping hint information, each tax form field in the tax form field set is aligned with the parameter field to obtain the parameter mapping rule.

[0007] Optionally, the method further includes: Receive the declaration failure information returned by the electronic tax bureau system; Based on the reported application failure information, the parameter mapping rules are modified to obtain the modified parameter mapping rules.

[0008] Optionally, the step of modifying the parameter mapping rules based on the application failure information to obtain modified parameter mapping rules includes: The declaration failure information, the tax form data, the parameter mapping rules used, and the interface parameter specifications of the automated declaration interface are input into the large language model to obtain rule correction instructions. Based on the rule correction instructions, the parameter mapping rules are updated to obtain the corrected parameter mapping rules.

[0009] Optionally, the method further includes: Record the tax form fields, the corresponding conversion parameters, and the target mapping rules in the tax form data, wherein the target mapping rule is the mapping rule in the parameter mapping rules used to convert the tax form fields into the conversion parameters; The tax form fields, the corresponding conversion parameters, and the target mapping rules are associated to obtain the association relationship, and the association relationship is stored.

[0010] Secondly, a tax filing device based on a dynamic rule engine is provided, including: The acquisition module is configured to acquire tax form data to be submitted; The conversion module is configured to convert the tax form data into conversion parameters that conform to the format specifications of the automated filing interface based on pre-configured parameter mapping rules through a dynamic rule engine; wherein, the automated filing interface is an interface provided by the e-tax bureau system, and the parameter mapping rules are used to describe the mapping relationship between tax form fields and parameters of the automated filing interface; The filling module is configured to fill the conversion parameters into the parameter structure of the automated declaration interface to obtain the declaration message; The sending module is configured to send the declaration message to the electronic tax bureau system through the automated declaration interface.

[0011] Thirdly, a computer-readable medium is provided having a computer program stored thereon, wherein the computer program, when executed by a processing device, implements the steps of the method described in the first aspect.

[0012] Fourthly, an electronic device is provided, comprising: A storage device on which computer programs are stored; A processing device for executing the computer program in the storage device to implement the steps of the method described in the first aspect.

[0013] Fifthly, a computer program product is provided, comprising a computer program, wherein the computer program, when executed by a processor, implements the steps of the method described in the first aspect.

[0014] The above technical solution acquires the tax form data to be declared, and uses a dynamic rule engine to convert the tax form data into conversion parameters that conform to the format specifications of the automated declaration interface based on pre-configured parameter mapping rules. The conversion parameters are then filled into the parameter structure of the automated declaration interface to obtain the declaration message, which is then sent to the e-tax bureau system through the automated declaration interface. This not only automates tax declaration and significantly reduces the time cost of tax declaration, but also adapts to different tax management systems through the configured parameter mapping rules. Even if the tax declaration rules change, there is no need to redevelop the interface; only the corresponding parameter mapping rules need to be configured, which can significantly reduce operation and maintenance costs.

[0015] Other features and advantages of the technical solution will be described in detail in the subsequent specific examples section. Attached Figure Description

[0016] The above and other features, advantages, and aspects of the technical solution will become more apparent when considered in conjunction with the accompanying drawings and the following specific examples. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and the originals and elements are not necessarily drawn to scale. In the drawings: Figure 1This is a flowchart illustrating a tax filing method based on a dynamic rules engine, based on certain scenarios.

[0017] Figure 2 This is a schematic diagram of a tax filing device based on a dynamic rules engine, shown under certain circumstances.

[0018] Figure 3 This is a schematic diagram of the structure of an electronic device shown under certain circumstances. Detailed Implementation

[0019] The technical solution will now be described in more detail with reference to the accompanying drawings. Although certain scenarios are shown in the drawings, it should be understood that the technical solution can be implemented in various forms and should not be construed as limited to the scenarios described herein. Rather, these scenarios are provided to provide a more thorough and complete understanding of the technical solution. It should be understood that the accompanying drawings and the scenarios described are for illustrative purposes only and are not intended to limit the scope of protection of the technical solution.

[0020] It should be understood that the steps described in the method examples may be performed in different orders and / or in parallel. Furthermore, the method examples may include additional steps and / or omit the steps shown. The scope of the technical solution is not limited in this respect.

[0021] The term "comprising" and its variations as used herein can be open-ended, meaning "including but not limited to". The term "based on" can mean "at least partially based on". The term "one case" means "at least one case"; the term "another case" means "at least one additional case"; the term "some cases" means "at least some cases". Definitions of other terms will be given in the following description.

[0022] It should be noted that the concepts of "first" and "second" mentioned here are only used to distinguish different devices, modules or units, and are not used to limit the order of the functions performed by these devices, modules or units or their interdependencies.

[0023] It should be noted that the terms "one" and "more" used here are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0024] The names of the messages or information exchanged between the multiple devices in the example are for illustrative purposes only and are not intended to limit the scope of these messages or information.

[0025] Figure 1 This is a flowchart illustrating tax filing methods based on a dynamic rule engine, illustrating various scenarios. For example... Figure 1As shown, a tax filing method based on a dynamic rule engine is provided, which can be executed by electronic devices, specifically a tax filing device based on a dynamic rule engine, which can be implemented through software and / or hardware. Figure 1 As shown, the method may include the following steps.

[0026] In step 110, the tax form data to be filed is obtained.

[0027] Here, the tax return data to be filed can be generated through the enterprise's tax management system. Tax return data includes, but is not limited to, various tax return forms such as value-added tax returns, corporate income tax returns, and individual income tax returns. Tax return data may include fields such as taxpayer basic information, the period to which the declaration pertains, tax type information, tax base, applicable tax rate, tax payable, tax reductions and exemptions, and tax already paid.

[0028] In step 120, the tax form data is converted into conversion parameters that conform to the format specifications of the automated filing interface based on the pre-configured parameter mapping rules through the dynamic rule engine; wherein, the automated filing interface is the interface provided by the e-tax bureau system, and the parameter mapping rules are used to describe the mapping relationship between the tax form fields and the parameters of the automated filing interface.

[0029] Here, the automated filing interface is an interface provided by the e-Tax Bureau system, used to receive filing messages submitted by third-party tax-related platforms and complete tax filing processing. For example, the automated filing interface could be the LeQi interface provided by the e-Tax Bureau system.

[0030] Parameter mapping rules are used to describe the mapping relationship between tax form fields and parameters of the automated filing interface. For example, the mapping relationship can be represented as: Tax field A → Parameter B. Here, tax field A refers to the field in the tax data, and parameter B refers to the parameter that conforms to the format specification of the automated filing interface.

[0031] It should be understood that parameter mapping rules can be user-configured or automatically configured. Different parameter mapping rules can correspond to different types of taxes and / or the design specifications of tax management systems. In this way, even if the tax filing rules change, there is no need to redevelop the interface; only the corresponding parameter mapping rules need to be configured, which can significantly reduce operation and maintenance costs.

[0032] The dynamic rule engine adopts a rule-configurable design, supporting dynamic loading, hot updating, and version management of parameter mapping rules. Parameter mapping rules can be stored in a rule repository and maintained through a visual configuration interface or configuration file, enabling real-time application of changes without modifying the source code. When executing parameter mapping rules, the dynamic rule engine can read them through a rule parser, utilize reflection to execute the logic of the parameter mapping rules, and convert each field in the tax form data into transformation parameters conforming to the format specifications of the automated filing interface.

[0033] In step 130, the conversion parameters are filled into the parameter structure of the automated declaration interface to obtain the declaration message.

[0034] Here, the automated filing interface provided by the e-Tax Bureau system has a corresponding parameter structure and follows the message specifications stipulated by the e-Tax Bureau system. During the parameter filling process, the dynamic rule engine can sequentially fill the generated transformation parameters into the corresponding positions in the parameter structure according to the parameter structure of the automated filing interface to obtain the filing message.

[0035] In step 140, a declaration message is sent to the electronic tax bureau system through the automated declaration interface.

[0036] Here, the automated filing interface can use an encrypted communication channel. Correspondingly, filing messages can be sent to the e-Tax Bureau system through this encrypted communication channel. For example, an encrypted communication channel can be established with the e-Tax Bureau system. In accordance with the e-Tax Bureau system's security access requirements, a two-way authentication method is used to transmit filing messages to the e-Tax Bureau system over a secure and reliable encrypted communication channel.

[0037] It should be understood that after sending the declaration message, you can wait for the response from the e-Tax Bureau system and use the response to mark the task status corresponding to the declaration task. A declaration task refers to the task used to submit a tax declaration to the e-Tax Bureau system. For example, if the response indicates that the declaration was successful, the task status can be marked as successful; if the response indicates that the declaration failed, the task status can be marked as failed.

[0038] Of course, this content can also provide a retry mechanism. For example, if the response from the e-Tax Bureau system indicates that the declaration has failed, the declaration message can be resent to the e-Tax Bureau system until the declaration is successful or the preset number of retries is reached.

[0039] Therefore, by acquiring the tax form data to be declared, and using a dynamic rule engine based on pre-configured parameter mapping rules, the tax form data is converted into conversion parameters that conform to the format specifications of the automated declaration interface. The conversion parameters are then filled into the parameter structure of the automated declaration interface to obtain the declaration message. The declaration message is then sent to the e-tax bureau system through the automated declaration interface. This not only automates tax declaration and significantly reduces the time cost of tax declaration, but also, through the configured parameter mapping rules, it can be adapted to different tax management systems. Even if the tax declaration rules change, there is no need to redevelop the interface; only the corresponding parameter mapping rules need to be configured, which can significantly reduce operation and maintenance costs.

[0040] In some embodiments, in step 120, the tax form data to be declared can be verified based on the tax form data declared in the previous period to obtain a verification result. If the verification result indicates that the tax form data to be declared has passed the verification, the tax form data can be converted into conversion parameters that conform to the format specifications of the automated declaration interface through the dynamic rule engine based on the pre-configured parameter mapping rules.

[0041] Here, before converting tax form data into conversion parameters that conform to the format specifications of the automated filing interface through the dynamic rule engine based on pre-configured parameter mapping rules, the tax form data can be validated.

[0042] The tax return data from the previous period refers to the historical tax return data that the taxpayer has successfully filed and archived through the e-tax bureau system during the previous tax filing period. This tax return data can be stored in the database of the company's internal tax management system.

[0043] For example, taking monthly VAT returns for general taxpayers as an example, assuming the current filing period is June 2027, the previous period's tax return data would be the VAT return data from May 2027. The previous period's tax return data includes, but is not limited to, fields such as: taxpayer identification number, filing period, taxable sales amount, output VAT, input VAT, carryforward VAT from the previous period, tax payable, tax already paid, and filing status.

[0044] It should be understood that tax filing is a business continuity process. By using the tax data from the previous period's filing, the data for the current tax return to be filed can be verified to ensure the accuracy of the data.

[0045] Business continuity verification can be performed on the tax return data to be filed based on the data from the previous period's tax return, and the verification results can be obtained. Business continuity verification can include verification of the reporting period continuity, verification of the carry-forward tax credit from the previous period continuity, and verification of the consistency of the beginning data. Verification of the reporting period continuity means verifying whether the reporting period of the tax return data to be filed is the period following the reporting period of the previous period. For example, if the reporting period of the previous period was May 2027, then the reporting period of the tax return data to be filed should be June 2027. Verification of the carry-forward tax credit continuity means verifying whether the carry-forward tax credit in the tax return data to be filed is equal to the ending carry-forward tax credit in the previous period's tax return data. Verification of the consistency of the beginning data means, for taxes filed quarterly such as corporate income tax, verifying whether the beginning data (such as beginning total assets, beginning total liabilities, etc.) in the tax return data to be filed is consistent with the ending data in the previous period's tax return data.

[0046] The process involves validating the tax return data to be submitted. If the validation result indicates that the data passes the verification, the dynamic rule engine converts the data into parameters conforming to the format specifications of the automated filing interface based on pre-configured parameter mapping rules. If the validation result indicates that the data fails the verification, the user is prompted to review the data.

[0047] Therefore, by using the tax form data verification mechanism and combining the parameter conversion capabilities of the dynamic rule engine, the pre-verification and intelligent conversion of tax declaration data are realized. This not only effectively identifies data anomalies and reduces the error rate of declarations, but also allows for rapid adaptation to business changes through dynamic updates of rule configurations, significantly improving the reliability, flexibility, and efficiency of automated tax declaration.

[0048] In some embodiments, the rule document of the automated declaration interface can be obtained, the rule document can be parsed, the field metadata included in the rule document can be extracted, and a mapping prompt information can be generated based on the field metadata through a large language model to obtain the set of tax form fields corresponding to the enterprise tax form data; based on the mapping prompt information, each tax form field in the set of tax form fields is aligned with the parameter field to obtain the parameter mapping rule.

[0049] Here, the automated filing interface is an interface provided by the e-Tax Bureau system, used to receive filing messages submitted by third-party tax-related platforms and complete tax filing business processing. The rules document describes the interface parameter specifications of the automated filing interface. Specifically, the rules document is a technical document published by the e-Tax Bureau system that describes the interface parameter specifications of the automated filing interface. The rules document includes, but is not limited to, the following: basic interface information, request parameter definitions, response parameter definitions, parameter structure relationships, and business rule descriptions. Basic interface information may include interface name, interface code, interface version, request method (e.g., POST / GET), request address, communication protocol, etc. Request parameter definitions may include parameter name, parameter code, data type (e.g., string, number, date, enumeration), field length, whether it is required, default value, value range, parameter description, etc. Response parameter definitions may include return code, return message, business data fields, etc. Parameter structure relationships may include hierarchical nesting relationships between parameters, array structures, and dependency relationships, etc. Business rule descriptions may include the business meaning of the parameters, calculation logic, validation rules, and a description of their correspondence with tax form fields, etc.

[0050] Since rule documents are typically published in unstructured or semi-structured formats, they can be parsed to extract the field metadata of the interface parameter fields described within. This field metadata includes, but is not limited to, parameter encoding, parameter name, data type, field length, whether it is required, value range, description of the parameter's business meaning, and the parameter's hierarchical path in the message structure.

[0051] It should be understood that the extracted field metadata can be stored in memory in the form of structured data objects, forming a field metadata set for subsequent processing by the large language model.

[0052] It can leverage the powerful semantic understanding and reasoning capabilities of the Large Language Model (LLM) to automatically predict the mapping relationship between the interface parameter fields and the enterprise's internal tax form fields based on the metadata information, and provide a confidence assessment of the mapping relationship.

[0053] The constructed prompts and field metadata can be input into the large language model to guide it in generating mapping prompt information. This mapping prompt information includes the mapping relationship between the parameter fields corresponding to the field metadata and the corporate tax form fields, as well as the confidence level between these mapping relationships. The corporate tax form fields are predicted by the large language model.

[0054] The prompts can include role definition, task description, and output format. Role definition defines the role of the large language model; for example, it could be "You are a senior tax information expert, proficient in the e-tax bureau interface specifications and the data structure design of the enterprise tax management system." Task description defines the task the large language model needs to perform. For example, it could be "Based on the field metadata of the following e-tax bureau automated filing interface, predict the most likely corresponding internal tax form field name for each parameter field, and provide the confidence level of the mapping relationship." Output format defines the format specifications of the large language model's output; for example, it could require outputting mapping prompt information in JSON format, including parameter field encoding, predicted enterprise tax form field name, mapping relationship type, confidence score, and reasoning basis.

[0055] The large language model can perform semantic analysis on each parameter field in the automated filing interface based on field metadata (especially business semantic information such as parameter name, parameter description, data type, and value range), combined with tax domain knowledge and natural language understanding capabilities learned during the large language model training phase, and predict the most likely corresponding internal tax form field of the enterprise.

[0056] The confidence level between mapping relationships is used to quantify the accuracy of the large language model's prediction results for the mapping relationship. The confidence level can be a value between 0% and 100%, and the higher the value, the higher the certainty of the large language model for the mapping relationship.

[0057] The set of tax form fields corresponding to corporate tax form data refers to the set of field names corresponding to the tax form data stored in the company's internal tax management system. The system's database can be accessed to query the data table structure corresponding to the tax form, obtain information such as field names, data types, and field comments, and then generate the tax form field set based on this information.

[0058] The predicted corporate tax form fields in the mapping prompts can be matched and aligned with the actual tax form field set to generate parameter mapping rules.

[0059] For example, if the predicted tax form field name in the mapping prompt is exactly the same as (or matches after synonym expansion) a field name in the tax form field set, then the mapping relationship is directly confirmed. For example, if the mapping prompt predicts that "Taxpayer Identification Number" corresponds to the corporate tax form field "Taxpayer Identification Number", and the two are exactly the same, then the mapping relationship is confirmed.

[0060] If the predicted tax form field names in the mapping prompt are not exactly the same as the field names in the tax form field set, but the semantic similarity exceeds a preset threshold, then fuzzy matching is performed. For example, if the mapping prompt predicts "declaration period", and the tax form field set contains "declaration period start" and "declaration period end", semantic analysis can be used to confirm that these two field combinations correspond to the interface parameter "declaration period".

[0061] Therefore, by parsing the rule documents of the automated declaration interface of the e-tax bureau system, the semantic understanding capabilities of the large language model are used to automatically generate the mapping relationship between parameter fields and corporate tax form fields, thereby significantly reducing the cost and error rate of manually configuring mapping rules.

[0062] In some embodiments, the system may receive declaration failure information returned by the e-tax bureau system, and then modify the parameter mapping rules based on the declaration failure information to obtain the modified parameter mapping rules.

[0063] Here, after the declaration message is sent to the e-Tax Bureau system through the automated declaration interface, the e-Tax Bureau system performs technical and business verification on the declaration message. If the verification fails, a declaration failure message is returned; if the verification passes, a declaration success message is returned.

[0064] Filing failure information may include error codes and text information describing the reason for the failure. For example, error codes may indicate the type of failure, such as different error codes for different failure types like parameter format errors or system exceptions. The text information describing the reason for the failure may be, for example, "Taxpayer identification number format error: should be 18 digits or uppercase English letters," or "Filing period format error: should be YYYYMM-YYYYMM," etc.

[0065] After obtaining the application failure information, the parameter mapping rules can be modified based on this information to obtain the revised parameter mapping rules. For example, based on the application failure information, the corresponding failure type can be determined, and then the parameter mapping rules can be modified using strategies related to the failure type to obtain the revised parameter mapping rules.

[0066] In some cases, the information on failed declarations, tax form data, the parameter mapping rules used, and the interface parameter specifications of the automated declaration interface can be input into the large language model to obtain rule correction instructions. Based on the rule correction instructions, the parameter mapping rules can be updated to obtain the corrected parameter mapping rules.

[0067] The parameter mapping rules used refer to the set of rules loaded and used by the dynamic rule engine to convert tax form data into parameters for the automated filing interface. The interface parameter specification refers to the technical specifications describing the interface parameter definitions, data types, format requirements, validation rules, and business logic of the automated filing interface. The corresponding interface parameter specification can be obtained by parsing the rule document.

[0068] The information on failed declarations, tax form data, the parameter mapping rules used, and the interface parameter specifications of the automated declaration interface can be used as context and input into a pre-trained large language model to obtain the corrected parameter mapping rules.

[0069] The large language model can understand the meaning of declaration failure information, compare the differences between the current parameter mapping rules and the interface parameter specifications, locate the root cause by combining the original tax form data, and generate rule correction instructions. These rule correction instructions are structured operation commands that guide how to modify the current parameter mapping rules. Then, the rule correction instructions can be executed to modify the pre-configured parameter mapping rules, resulting in the corrected parameter mapping rules.

[0070] Therefore, by inputting multi-dimensional information such as declaration failure information, original tax form data, current parameter mapping rules, and interface parameter specifications into the large language model, and utilizing the semantic understanding, logical reasoning, and rule generation capabilities of the large language model, intelligent and automated correction of parameter mapping rules is achieved.

[0071] In some cases, it is possible to record the tax form fields, the corresponding transformation parameters, and the target mapping rules in the tax form data, associate the tax form fields, the corresponding transformation parameters, and the target mapping rules to obtain the association relationship, and store the association relationship.

[0072] Here, when converting tax form data into conversion parameters that conform to the format specifications of the automated filing interface through the dynamic rule engine, the tax form fields, the corresponding conversion parameters, and the target mapping rules in the tax form data can be recorded simultaneously. The target mapping rules are the mapping rules used in the parameter mapping rules to convert tax form fields into conversion parameters.

[0073] Then, the tax form fields, their corresponding transformation parameters, and target mapping rules can be associated to obtain and store the relationships. For example, the obtained relationships can be represented as: Tax form field A → Transformation parameter B, based on parameter mapping rule C.

[0074] Relationships can be stored in a database, using a graph database to store entity relationships or a time-series database to store change tracings. Relationships can be used for tracing the origins of tax returns. For example, when a tax return is rejected by the e-tax system, relationship relationships can be used to quickly locate the problematic field and its corresponding parameter mapping rules. During tax audits, relationship relationships can be used to reconstruct the entire data transformation process. When parameter mapping rules need to be corrected, relationship relationships can be used to assess the historical impact of changes to parameter mapping rules.

[0075] Therefore, by storing the above-mentioned relationships, the entire process of tax form data conversion can be recorded and traceable relationships can be established, which facilitates subsequent tracing.

[0076] Figure 2 This is a schematic diagram illustrating the structure of a tax filing device based on a dynamic rule engine, shown under certain circumstances. For example... Figure 2 As shown, a tax filing device 200 based on a dynamic rule engine is provided. The tax filing device 200 based on a dynamic rule engine may include: Module 201 is configured to retrieve tax form data to be submitted; The conversion module 202 is configured to convert the tax form data into conversion parameters that conform to the format specifications of the automated filing interface based on pre-configured parameter mapping rules through a dynamic rule engine; wherein, the automated filing interface is an interface provided by the electronic tax bureau system, and the parameter mapping rules are used to describe the mapping relationship between the tax form fields and the parameters of the automated filing interface; The filling module 203 is configured to fill the conversion parameters into the parameter structure of the automated declaration interface to obtain the declaration message; The sending module 204 is configured to send the declaration message to the electronic tax bureau system through the automated declaration interface.

[0077] Optionally, the conversion module 202 is configured to: Based on the tax return data submitted in the previous period, the tax return data to be submitted is verified to obtain the verification results. If the verification result indicates that the tax form data to be declared has passed the verification, the tax form data is converted into conversion parameters that conform to the format specifications of the automated declaration interface through the dynamic rule engine based on the pre-configured parameter mapping rules.

[0078] Optionally, the conversion module 202 is configured to: Obtain the rule document for the automated declaration interface, wherein the rule document describes the interface parameter specifications of the automated declaration interface; Parse the rule document and extract the field metadata included in the rule document; Based on the field metadata, a mapping suggestion is generated using a large language model. The mapping suggestion includes the mapping relationship between the parameter field corresponding to the field metadata and the corporate tax form field, and the confidence level between the mapping relationship. The corporate tax form field is predicted by the large language model. Retrieve the set of tax table fields corresponding to the enterprise's tax table data; Based on the mapping hint information, each tax form field in the tax form field set is aligned with the parameter field to obtain the parameter mapping rule.

[0079] Optionally, the tax filing device 200 based on a dynamic rule engine further includes: The receiving module is configured to receive the declaration failure information returned by the electronic tax bureau system; The correction module is configured to correct the parameter mapping rules based on the application failure information to obtain the corrected parameter mapping rules.

[0080] Optionally, the correction module is configured to: The declaration failure information, the tax form data, the parameter mapping rules used, and the interface parameter specifications of the automated declaration interface are input into the large language model to obtain rule correction instructions. Based on the rule correction instructions, the parameter mapping rules are updated to obtain the corrected parameter mapping rules.

[0081] Optionally, the tax filing device 200 based on a dynamic rule engine further includes: The recording module is configured to record the tax form fields, the conversion parameters corresponding to the tax form fields, and the target mapping rules in the tax form data, wherein the target mapping rules are the mapping rules in the parameter mapping rules used to convert the tax form fields into the conversion parameters; The association module is configured to associate the tax form fields, the corresponding transformation parameters of the tax form fields, and the target mapping rules to obtain the association relationship and store the association relationship.

[0082] It should be understood that the execution logic of each functional module in the tax filing device 200 based on the dynamic rule engine has been explained in detail in the section on the tax filing method based on the dynamic rule engine, and can be referred to in the relevant description of the tax filing method based on the dynamic rule engine.

[0083] The following is for reference. Figure 3The diagram illustrates a structural schematic of an electronic device (e.g., a terminal device or a server) 600 suitable for implementing the above-described technical solutions. The terminal device may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Tablet Personal Computers), PMPs (Portable Media Players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs (Televisions), desktop computers, etc. Figure 3 The electronic device shown is merely an example and should not be construed as limiting its functionality or scope of use.

[0084] like Figure 3 As shown, electronic device 600 may include a processing unit (e.g., a central processing unit, a graphics processing unit, etc.) 601, which can perform various appropriate actions and processes according to a program stored in read-only memory (ROM) 602 or a program loaded from storage device 608 into random access memory (RAM) 603. The random access memory 603 also stores various programs and data required for the operation of electronic device 600. The processing unit 601, ROM 602, and RAM 603 are interconnected via bus 604. An input / output (I / O) interface 605 is also connected to bus 604.

[0085] Typically, the following devices can be connected to the input / output interface 605: input devices 606 including, for example, a touchscreen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; output devices 607 including, for example, a liquid crystal display (LCD), speaker, vibrator, etc.; storage devices 608 including, for example, magnetic tape, hard disk, etc.; and communication devices 609. Communication device 609 allows electronic device 600 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 3 An electronic device 600 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively.

[0086] In particular, depending on certain circumstances, the processes described in the flowchart above can be implemented as computer software programs. For example, a computer program product is provided, comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods shown in the flowchart. This computer program can be downloaded and installed from a network via communication device 609, or installed from storage device 608, or installed from read-only memory 602. When the computer program is executed by processing device 601, it performs the functions defined in the above-described methods.

[0087] It should be noted that the aforementioned computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium may be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM, or flash memory), optical fiber, portable compact disc read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In one case, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In another case, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. The transmitted data signal can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. The computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (Radio Frequency), etc., or any suitable combination thereof.

[0088] In some examples, communication can be conducted using any currently known or future-developed network protocol such as HTTP (Hypertext Transfer Protocol), and can be interconnected with digital data communication (e.g., communication networks) of any form or medium. Examples of communication networks include Local Area Networks (LANs), Wide Area Networks (WANs), Internets (e.g., the Internet), and peer-to-peer networks (e.g., ad-hoc peer-to-peer networks), as well as any currently known or future-developed networks.

[0089] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device.

[0090] The aforementioned computer-readable medium carries one or more programs that, when executed by the electronic device, cause the electronic device to: acquire tax form data to be declared; convert the tax form data into conversion parameters conforming to the format specification of the automated declaration interface based on pre-configured parameter mapping rules using a dynamic rule engine; wherein the automated declaration interface is an interface provided by the e-tax bureau system, and the parameter mapping rules are used to describe the mapping relationship between tax form fields and parameters of the automated declaration interface; fill the conversion parameters into the parameter structure of the automated declaration interface to obtain a declaration message; and send the declaration message to the e-tax bureau system through the automated declaration interface.

[0091] Computer program code for performing the above operations can be written in one or more programming languages ​​or a combination thereof. These programming languages ​​include, but are not limited to, object-oriented programming languages, as well as conventional procedural programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0092] The flowcharts and block diagrams in the accompanying figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products under various scenarios. In this respect, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the figures. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0093] The modules mentioned above can be implemented in software or hardware. In some cases, the name of a module does not necessarily limit the functionality of that module.

[0094] The functions described above can be performed, at least in part, by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: Field-Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), Application-Specific Standard Parts (ASSPs), Systems on Chips (SoCs), Complex Programmable Logic Devices (CPLDs), and so on.

[0095] In this context, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0096] The above description is merely illustrative and explains the technical principles employed. Those skilled in the art should understand that the scope of the technical solution is not limited to specific combinations of the above-described technical features, but also includes other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above concept. For example, technical solutions formed by substituting the above-described features with (but not limited to) technical features provided herein that have similar functions.

[0097] Furthermore, while the operations are described in a specific order, this should not be construed as requiring these operations to be performed in the specific order shown or in a sequential order. Multitasking and parallel processing may be advantageous in certain environments. Similarly, although some specific implementation details are included in the above discussion, these should not be interpreted as limitations on the scope of the technical solution. Certain features described in the context of a single example can also be implemented in combination in a single example. Conversely, various features described in the context of a single example can also be implemented individually or in any suitable sub-combination in multiple examples.

[0098] Although the technical solution has been described using language specific to structural features and / or methodological logic, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are merely illustrative examples of implementing the claims. Regarding the aforementioned apparatus, the specific manner in which each module performs its operation has already been described in detail in the section concerning the method, and will not be elaborated upon here.

Claims

1. A tax filing method based on a dynamic rule engine, characterized in that, include: Obtain the tax return data to be filed; The dynamic rule engine converts the tax form data into conversion parameters that conform to the format specifications of the automated filing interface based on pre-configured parameter mapping rules. The automated filing interface is an interface provided by the e-tax bureau system, and the parameter mapping rules are used to describe the mapping relationship between the tax form fields and the parameters of the automated filing interface. The conversion parameters are filled into the parameter structure of the automated declaration interface to obtain the declaration message; The declaration message is sent to the electronic tax bureau system through the automated declaration interface.

2. The tax declaration method according to claim 1, characterized in that, The process of converting the tax form data into conversion parameters that conform to the format specifications of the automated filing interface through a dynamic rule engine based on pre-configured parameter mapping rules includes: Based on the tax return data submitted in the previous period, the tax return data to be submitted is verified to obtain the verification results. If the verification result indicates that the tax form data to be declared has passed the verification, the tax form data is converted into conversion parameters that conform to the format specifications of the automated declaration interface through the dynamic rule engine based on the pre-configured parameter mapping rules.

3. The tax declaration method according to claim 1, characterized in that, The parameter mapping rules are obtained through the following steps: Obtain the rule document for the automated declaration interface, wherein the rule document describes the interface parameter specifications of the automated declaration interface; Parse the rule document and extract the field metadata included in the rule document; Based on the field metadata, a mapping prompt message is generated using a large language model. The mapping hint information includes the mapping relationship between the parameter field corresponding to the field metadata and the corporate tax form field and the confidence level between the mapping relationship, wherein the corporate tax form field is predicted by the big language model; Retrieve the set of tax table fields corresponding to the enterprise's tax table data; Based on the mapping hint information, each tax form field in the tax form field set is aligned with the parameter field to obtain the parameter mapping rule.

4. The tax declaration method according to claim 1, characterized in that, The method further includes: Receive the declaration failure information returned by the electronic tax bureau system; Based on the reported application failure information, the parameter mapping rules are modified to obtain the modified parameter mapping rules.

5. The tax declaration method according to claim 4, characterized in that, The step of modifying the parameter mapping rules based on the application failure information to obtain modified parameter mapping rules includes: The declaration failure information, the tax form data, the parameter mapping rules used, and the interface parameter specifications of the automated declaration interface are input into the large language model to obtain rule correction instructions. Based on the rule correction instructions, the parameter mapping rules are updated to obtain the corrected parameter mapping rules.

6. The tax declaration method according to any one of claims 1-5, characterized in that, The method further includes: Record the tax form fields, the corresponding conversion parameters, and the target mapping rules in the tax form data, wherein the target mapping rule is the mapping rule in the parameter mapping rules used to convert the tax form fields into the conversion parameters; The tax form fields, the corresponding conversion parameters, and the target mapping rules are associated to obtain the association relationship, and the association relationship is stored.

7. A tax filing device based on a dynamic rule engine, characterized in that, include: The acquisition module is configured to acquire tax form data to be submitted; The conversion module is configured to convert the tax form data into conversion parameters that conform to the format specifications of the automated filing interface based on pre-configured parameter mapping rules through a dynamic rule engine; wherein, the automated filing interface is an interface provided by the e-tax bureau system, and the parameter mapping rules are used to describe the mapping relationship between tax form fields and parameters of the automated filing interface; The filling module is configured to fill the conversion parameters into the parameter structure of the automated declaration interface to obtain the declaration message; The sending module is configured to send the declaration message to the electronic tax bureau system through the automated declaration interface.

8. A computer-readable medium having a computer program stored thereon, characterized in that, When executed by a processing device, the computer program performs the steps of the method according to any one of claims 1-6.

9. An electronic device, characterized in that, include: A storage device on which computer programs are stored; A processing device for executing the computer program in the storage device to implement the steps of the method according to any one of claims 1-6.

10. A computer program product, characterized in that, Includes a computer program, wherein when executed by a processor, the computer program implements the steps of the method according to any one of claims 1-6.

Images