A customs declaration quality evaluation method for cross-border e-commerce

Abstract

This application provides a method for assessing the quality of customs declarations in cross-border e-commerce. Applied to the field of big data analytics, it extracts product attribute features and performs multi-condition searches to proactively generate a set of candidate declaration codes. Then, using the corresponding declaration supervision conditions and requirements for each candidate code, it differentiates and compliantly adjusts the user's original declaration data (marking missing documents and supplementing declaration elements). Based on the adjusted value information, it recalculates tariffs, forming multiple structured declaration schemes. Since each scheme is a feasible option that can pass customs review after supplementing the required materials, users can not only intuitively compare the tariff savings of each scheme with the list of additional materials required, but also make a quantitative trade-off between tariff costs and operational convenience. Under the premise of legality and compliance, it significantly improves the ability to optimize tax and fees in declarations and enhances the user's autonomy in decision-making.

Description

Technical Field

[0001] This application relates to the field of big data analytics, and in particular to a method for assessing the quality of customs declarations used in cross-border e-commerce. Background Technology

[0002] With the continuous expansion of cross-border e-commerce trade, enterprises need to process massive amounts of customs declaration data from different sellers simultaneously. Tariffs, commodity classification codes, and regulatory conditions of different destination countries are stored in multiple heterogeneous databases. How to quickly retrieve the classification code matching the declared goods from these databases and extract the corresponding regulatory requirements and declaration element specifications has become an urgent technical problem to be solved in the data processing stage.

[0003] Existing technology involves obtaining customs declaration information, performing field integrity and format compliance checks on the information, and determining whether the declared data meets the basic acceptance requirements of customs. If the checks pass, the customs declaration information is deemed valid. If the checks fail, the reasons for non-compliance are output, prompting the user to supplement or correct the relevant fields until the declared data meets the verification requirements.

[0004] However, in existing technologies, because only a single rule is used for verification, it is impossible to deconstruct commodity attributes under multiple conditions and retrieve data from the database. This makes it difficult to generate multiple candidate classification codes, and thus impossible to automatically calculate and compare the tariff rates corresponding to each candidate code. Consequently, it is impossible to provide users with a declaration adjustment scheme that saves tariffs while meeting basic compliance requirements. Ultimately, users can only passively accept the original declaration data and cannot make a better declaration choice based on quantitative comparison. Summary of the Invention

[0005] This application provides a method for assessing the quality of customs declarations in cross-border e-commerce. Its core features include: extracting identification features, commodity attribute features, and value features from valid declaration information; using identification features to match and obtain basic tariff information and calculate initial tariff results; simultaneously using commodity attribute features to perform multi-condition searches of the classification coding database to generate a set of candidate declaration codes; then extracting the corresponding declaration supervision conditions and declaration requirements for each candidate code; adjusting the valid declaration information to generate multiple declaration schemes associated with the target tariff results; comparing and outputting the differences in tax and compliance risks among the multiple schemes; after the user selects a target scheme and uploads materials, verifying the consistency of the material information based on the declaration requirements in the scheme; and finally outputting the declaration assessment results. This achieves a closed-loop assessment from single-rule verification to quantitative comparison and compliance adjustment of multiple schemes.

[0006] To achieve the above objectives, this application adopts the following technical solution:

[0007] This application provides a method for assessing the quality of customs declarations in cross-border e-commerce, the method including:

[0008] Obtain valid declaration information and extract the valid declaration information to obtain a feature dataset, wherein the feature dataset includes at least identification features, commodity attribute features and value features;

[0009] The identification features are matched with the preset destination country's tariff database to obtain basic tariff information;

[0010] The initial tariff result is obtained by calculating the value characteristics and the basic tariff information.

[0011] The product attribute features are compared with a preset classification coding database under multiple conditions to generate a set of candidate declaration codes;

[0012] Extract the candidate application code set to obtain the application requirement constraint information corresponding to each candidate application code. The application requirement constraint information includes application supervision conditions and application requirement conditions.

[0013] The valid declaration information is adjusted based on the declaration supervision conditions and the declaration requirements to generate adjusted declaration data. The target tariff result corresponding to each candidate declaration code is calculated based on the adjusted declaration data. The adjusted declaration data is then associated with the target tariff result to generate a declaration scheme corresponding to each candidate declaration code.

[0014] A comparative analysis of multiple application schemes is performed to generate a multi-scheme comparison result that includes differences in tax fees and compliance risks, and the multi-scheme comparison result is output.

[0015] Receive the target application plan selected by the user based on the multi-plan comparison results and the uploaded material information;

[0016] Based on the application requirements corresponding to the target application scheme, the consistency of the material information uploaded by the user is verified, and the verification result is obtained.

[0017] When the verification results are consistent, the final application evaluation result is output.

[0018] As can be seen from the above technical solution, this application has the following beneficial effects:

[0019] 1. This application proactively generates a set of candidate declaration codes by extracting commodity attribute features and performing multi-condition searches. Then, it uses the declaration regulatory conditions and declaration requirements corresponding to each candidate code to make differentiated compliance adjustments to the user's original declaration data (marking missing documents and supplementing declaration elements). Based on the adjusted value information, it recalculates tariffs to form multiple structured declaration schemes. Since each scheme is a feasible solution that can pass customs review after supplementing the required materials, users can not only intuitively compare the tariff savings of each scheme with the list of additional materials required, but also make a quantitative trade-off between tariff costs and operational convenience. This solves the pain point of existing technologies where users can only passively accept a single declaration result and cannot learn about better compliant declaration paths. Under the premise of legality and compliance, it significantly improves the ability to optimize tax and fees in declarations and the space for independent decision-making.

[0020] 2. This application calculates tax savings data by comparing the target tariff results with the initial tariff results of each scheme, and performs tariff difference calculations and compliance risk level classifications between schemes. It then integrates these calculations to generate a multi-scheme comparison result that includes both tax and compliance risk differences, allowing users to easily identify the lowest tariff scheme and its corresponding regulatory requirements. After a user selects a target scheme and uploads materials, the application uses the scheme's declaration requirements as the standard to perform item-by-item consistency checks on the uploaded documents and field data. This accurately identifies the types of deviations such as missing documents, format errors, or mismatches, and generates clear correction guidelines. Through closed-loop feedback, it guides users to complete the material corrections. This achieves a complete closed loop from scheme recommendation to automatic material verification, solving the problems of existing technologies that cannot quantify the differences between multiple schemes and users repeatedly submitting incorrect materials, significantly improving the declaration success rate and overall declaration efficiency. Attached Figure Description

[0021] The present application will be further described below with reference to the accompanying drawings.

[0022] Figure 1 A flowchart of the first customs declaration quality assessment method for cross-border e-commerce provided for this application;

[0023] Figure 2 A flowchart for the second customs declaration quality assessment method for cross-border e-commerce provided in this application. Detailed Implementation

[0024] The terms "first," "second," and "third," etc., used in this application specification, claims, and drawings are used to distinguish different objects, not to limit a specific order.

[0025] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0026] Research has revealed that existing technologies, which rely on a single rule for verification, cannot perform multi-condition deconstruction and database retrieval of product attributes. This makes it difficult to generate multiple candidate classification codes, thus hindering the automated calculation and comparison of tariff differences for each candidate code. Consequently, it is impossible to provide users with tariff-saving adjustment schemes while meeting basic compliance requirements. Ultimately, users are forced to passively accept raw declaration data and are unable to make better declaration choices based on quantitative comparisons.

[0027] Example 1

[0028] To address the aforementioned issues, this application provides a method for assessing the quality of customs declarations used in cross-border e-commerce. Please refer to [link / reference]. Figure 1 .

[0029] It should be noted that the methods provided in this application are intended to help users assess the completeness, standardization, and potential for optimization of declaration data before formally submitting declarations to customs, thereby reducing compliance risks caused by information errors or improper classification. All declaration adjustment schemes are based on the current tariff schedules and regulatory requirements of the destination country. Users should comply with local laws and regulations when making actual declarations and are solely responsible for the final content of their declarations. This method does not involve any acts of evading tariffs, falsifying documents, or violating customs regulations, nor does it recommend that users adopt any illegal or irregular declaration strategies. Users must carefully select any adjustment schemes generated based on this method in light of their actual circumstances and bear the corresponding legal responsibilities.

[0030] S1. Obtain valid declaration information and extract the valid declaration information to obtain a feature dataset.

[0031] Before the user formally submits the declaration to customs, the system obtains the customs declaration information submitted by the user. This information includes the product description, classification code (temporarily filled in), price, quantity, and other content filled in by the user based on the transaction order.

[0032] Perform field integrity checks (e.g., check if required fields such as commodity code, product name, quantity, and value are empty) and format compliance checks (e.g., check if the date format, amount format, and unit of measurement comply with the customs requirements of the destination country) on the customs declaration information, and generate compliance verification results;

[0033] If the compliance verification result is compliant, the customs declaration information is determined to be valid declaration information; if it is non-compliant, the reason for non-compliance is output (such as missing commodity code or incorrect amount format), prompting the user to supplement or correct the corresponding fields until the user corrects and resubmits, generating compliant and valid declaration information.

[0034] After obtaining valid declaration information, at least three types of key feature data are parsed and extracted from various fields of the valid declaration information, specifically:

[0035] Extract identifying features, which include the first few digits of the commodity's customs code (such as the first 6 digits of the HS code), the company's customs code, country of origin, and other information used to uniquely identify the commodity and its trading entity.

[0036] Extract product attribute features, which include textual information describing the physical and functional attributes of the product, such as product name, specifications, material, use, function, and ingredient content.

[0037] Extract value features, which include declared unit price, declared total price, currency, quantity, unit of measurement, and other value and quantity information used to calculate customs duties.

[0038] The aforementioned feature dataset is stored in a structured format (e.g., JSON format or relational table) to provide standardized input for subsequent basic tariff matching, multi-condition retrieval, and tariff calculation.

[0039] To ensure clarity and conciseness in the description of the following embodiments, a brief introduction to the relevant terms is given first:

[0040] Customs declaration information refers to the declaration information filled in by the user, which includes fields such as commodity code, product name, quantity, value, date, and unit of measurement.

[0041] Valid declaration information refers to customs declaration information that has passed the field integrity and format standardization verification, meets the basic threshold for customs acceptance, and can be used for subsequent feature extraction and evaluation analysis.

[0042] Identification features refer to information extracted from valid declaration information that is used to uniquely identify commodities and their trading entities, including the first few digits of the commodity's customs code, the company's customs code, and the country of origin.

[0043] Commodity attribute characteristics refer to textual information extracted from valid declaration information that describes the physical and functional attributes of a commodity, including commodity name, specifications, material, use, function, and ingredient content.

[0044] Value characteristics refer to the value and quantity information extracted from valid declaration information used to calculate tariffs, including declared unit price, total declared price, currency, quantity, and unit of measurement.

[0045] A feature dataset is a collection of data obtained by structuring and encapsulating identification features, commodity attribute features, and value features. It is used for subsequent basic tariff matching, multi-condition retrieval, and tariff calculation.

[0046] The compliance verification result refers to the conclusion obtained after verifying the integrity of fields and the standardization of format of customs declaration information, including two states: compliant and non-compliant.

[0047] In some possible implementations, particularly in pre-declaration assessments for cross-border e-commerce, traditional methods only verify the completeness and format of the customs declaration information submitted by the user. Once approved, the declaration is considered valid, and the user passively accepts this single result. This approach ignores the multiple possible classifications of goods and the tariff differences corresponding to different classification codes. Users cannot know in advance whether there are lower-tax-rate classification paths, nor can they compare the tariff savings and compliance risks associated with different declaration schemes.

[0048] This step is designed to address this issue. It ensures that the declared data meets the minimum threshold for customs acceptance through basic verification, and then extracts structured features that can be used for subsequent intelligent retrieval and analysis. Among them, the identification features are used to quickly match the destination country's tariff database to obtain basic tariff information; the commodity attribute features serve as keywords for multi-condition retrieval, supporting the generation of candidate classification codes and laying the data foundation for discovering potential low-tax-rate codes; and the value features are directly used for the initial calculation of tariff amounts and the comparison of differences between schemes.

[0049] This step provides calculable and comparable data support for generating multiple declaration schemes (including schemes that apply different codes after adjusting product descriptions) and for quantitatively comparing the tax and compliance risks of each scheme.

[0050] S2, based on the feature dataset, matches the basic tariff information and calculates the initial tariff result.

[0051] Identification features and value features are extracted from the feature dataset generated by S1. The first few digits of the commodity customs code (e.g., the first 6 digits of the HS code), the enterprise customs code, and the country of origin are used as search keys for precise matching in a pre-defined destination country tariff database. This database pre-stores the basic tariff rates, tax types (e.g., most-favored-nation rates, generalized system of preferences rates, etc.), and applicable rules for ad valorem, specific, or compound taxes for different commodity codes in that country. Upon successful matching, the corresponding basic tariff information is retrieved, which includes at least the applicable tariff rate and the applicable rules for ad valorem, specific, or compound taxes.

[0052] The declared unit price, total declared price, currency, quantity, and unit of measurement from the value characteristics are combined with the basic customs duty information for calculation. Specifically, based on the applicable rules for ad valorem, specific, or compound taxes in the basic customs duty information, the corresponding tax rate is applied to the declared total price (converted to the destination country's currency at the exchange rate of the day) in the value characteristics to calculate the preliminary customs duty amount, which serves as the initial customs duty result. For example, if it is an ad valorem tax, the declared total price is multiplied by the tax rate to obtain the customs duty amount; if it is a specific tax, the quantity is multiplied by the unit tax amount to obtain the customs duty amount.

[0053] Through the above processing, the basic tariff information and initial tariff results corresponding to the user's original declaration plan (i.e., the commodity code and declaration information initially filled in by the user) are obtained, which serve as the benchmark reference value for comparing tariff savings of subsequent candidate declaration plans.

[0054] To ensure clarity and conciseness in the description of the following embodiments, a brief introduction to the relevant terms is given first:

[0055] A pre-built destination country tariff database refers to a structured dataset that stores the applicable tariff rates, tax types, and applicable rules for ad valorem, specific, or compound taxes for different commodity codes in the destination country. It is used to match basic tariff information based on commodity identification features.

[0056] Basic tariff information refers to the tariff rules corresponding to the product identification characteristics, which are matched from the tariff database of the destination country. It includes at least the applicable tariff rate and the applicable rules for ad valorem, specific, or compound tariffs.

[0057] Ad valorem tax refers to the method of calculating customs duties by multiplying the total price of goods by the tax rate; specific tax refers to the method of calculating customs duties by multiplying the quantity of goods by the unit tax amount; compound tax refers to the calculation method that combines ad valorem tax and specific tax.

[0058] The initial tariff result refers to the preliminary tariff amount obtained by calculating the value characteristics (total declared price, quantity, currency, etc.) and basic tariff information. It serves as the tax base for the user's original declaration plan and is used for subsequent comparison of savings with candidate declaration plans.

[0059] The declared total price refers to the total value of the goods in the value characteristics, which is usually the product of the declared unit price and the quantity, and is used for customs duty calculation.

[0060] In some possible implementations, users typically only know the basic tariff information corresponding to the commodity code they entered, but cannot know the tariff differences under different classification codes. Traditional methods directly use the user-entered code for matching and calculating tariffs, leaving the user with only this single result. This step utilizes the identification features extracted in S1 to locate the basic tariff information corresponding to the user's current declaration scheme from the destination country's tariff database, and calculates the initial tariff result by combining it with value features. This initial tariff result will serve as the analytical benchmark for subsequent multi-scheme comparisons, used to measure the tariff savings of each candidate declaration scheme relative to the original scheme. By quantifying the tax benchmark of the original declaration, the system can provide quantifiable comparative evidence for generating a better declaration path, avoiding the subjectivity of purely qualitative judgments and improving the scientific rigor and persuasiveness of the evaluation.

[0061] S3 performs multi-condition retrieval based on the feature dataset to generate a set of candidate declaration codes.

[0062] Product attribute features are extracted from the feature dataset generated by S1. Product attribute features include textual information describing the physical and functional attributes of the product, such as product name, specifications, material, use, function, and ingredient content.

[0063] The product's attribute characteristics are deconstructed to extract classification elements. Classification elements include key attributes that can be used to determine the product's classification code, such as the product's purpose (e.g., parts used in automobile engines), structural characteristics (e.g., injection molding, metal material), and performance parameters (e.g., rated voltage, power, capacity).

[0064] The classification elements are mapped to generate corresponding attribute matching relationships, and search conditions are constructed based on these relationships. Search conditions must include at least usage matching conditions (e.g., usage includes "automobile"), structure matching conditions (e.g., material is "stainless steel"), and parameter range conditions (e.g., "voltage between 12V and 24V").

[0065] Based on the search criteria, the coding attributes in the preset classification coding database are matched and filtered. The preset classification coding database is a pre-built dataset that stores product classification codes and their corresponding product attribute descriptions (such as applicable scope, material, functional parameters, etc.). During filtering, the search criteria are matched with the attribute descriptions of each code in the database using fuzzy matching or rule matching to obtain one or more candidate codes that initially meet the criteria.

[0066] The candidate coding data is deduplicated (removing duplicate codes) and validity filtered (removing expired or inapplicable codes) to generate a set of candidate application codes.

[0067] This set contains all classification codes that technically match the product attributes input by the user, providing a data foundation for subsequently extracting the declaration requirement constraints corresponding to each code and generating multiple scheme comparisons.

[0068] To ensure clarity and conciseness in the description of the following embodiments, a brief introduction to the relevant terms is given first:

[0069] Feature deconstruction refers to the process of breaking down the description of product attributes in natural language into structured, searchable classification elements.

[0070] Classification elements refer to the key attributes extracted from the product's attribute characteristics to determine the product's classification code, including product use, structural characteristics, performance parameters, etc.

[0071] Condition mapping refers to the process of converting categorized elements into attribute matching relationships that can be recognized by the database, and generating search conditions accordingly.

[0072] Search criteria refer to the query conditions used for matching and filtering in the preset classification coding database, and include at least usage matching criteria, structure matching criteria, and parameter range criteria.

[0073] A pre-built classification coding database refers to a dataset that is pre-constructed and stores product classification codes and their corresponding product attribute descriptions (such as applicable scope, material, functional parameters, etc.).

[0074] Candidate coding data refers to one or more categorized coding records obtained through preliminary matching based on search criteria.

[0075] Deduplication refers to the operation of removing duplicate candidate codes.

[0076] Validity screening refers to the operation of removing expired or inapplicable codes and retaining usable codes.

[0077] The candidate declaration code set refers to the set of all classification codes that, after deduplication and validity screening, may technically match the product attributes input by the user.

[0078] The classification code (also known as the commodity classification code) is a unique identifier used by customs to classify and tax commodities. In this embodiment, it is used to retrieve the corresponding tariff and regulatory information in the database.

[0079] In some possible implementations, users often fill in the product classification code based on their own experience or a simple description. However, the same product may correspond to multiple compliant classification codes due to different emphasis in the attribute description. Traditional methods only accept a single code entered by the user, and even if that code is not the one with the optimal tax rate, the user has no way of knowing whether there are other compliant paths with lower tax rates. This step addresses this problem by using product attribute features to perform multi-condition retrieval, actively mining all possible matching classification codes to form a candidate set, providing a pool of selectable codes for subsequent scheme comparison.

[0080] By deconstructing natural language product descriptions into structured categorization elements (use, material, parameters, etc.) through feature deconstruction, and then generating machine-executable search conditions through condition mapping, the accuracy and coverage of cross-database searches can be significantly improved. Deduplication and validity filtering ensure the usability of the candidate code set and avoid processing invalid data in subsequent steps.

[0081] The core value of this step lies in expanding the user's single declaration path into multiple compliant and comparable declaration paths, enabling the user to choose from multiple candidate options with lower tariffs and more controllable risks. This solves the problem in existing technologies that can only passively accept user-filled codes and cannot actively recommend better codes.

[0082] S4. Extract the candidate application code set to obtain the application requirement constraint information corresponding to each candidate application code.

[0083] Retrieve each candidate declaration code (i.e., the candidate commodity classification code) from the candidate declaration code set generated by S3. Use each candidate declaration code as a search key to perform a related search in the preset regulatory conditions database and the preset declaration requirements database, where:

[0084] The pre-set regulatory conditions database stores regulatory conditions data corresponding to each classification code, such as access restriction information (whether an import license is required, whether it belongs to the prohibited or restricted import category) and inspection and quarantine requirements information (whether animal and plant quarantine, quality inspection, etc. are required).

[0085] The pre-defined declaration requirements database stores declaration requirements data corresponding to each classification code, such as accompanying document requirements (certificate of origin, packing list, contract, etc.) and declaration element filling requirements (commodity attribute fields that need to be filled in the customs declaration, such as brand, model, material, etc.).

[0086] The retrieved regulatory conditions data is analyzed to extract the regulatory conditions for declaration. The regulatory conditions for declaration include at least the information on access restrictions and the information on inspection and quarantine requirements. The retrieved declaration requirements data is analyzed to extract the declaration requirements. The declaration requirements include at least the requirements for accompanying documents and the requirements for filling in declaration elements.

[0087] The extracted regulatory conditions and application requirements are integrated to form the application requirement constraint information corresponding to each candidate application code.

[0088] Through the above processing, the compliance constraints corresponding to each candidate classification code are obtained (including which regulatory measures are applicable, which documents need to be prepared, and which elements must be filled in the customs declaration), providing a basis for subsequent adjustments to user declaration data and generation of compliance declaration schemes.

[0089] To ensure clarity and conciseness in the description of the following embodiments, a brief introduction to the relevant terms is given first:

[0090] The pre-built regulatory condition database refers to a pre-constructed database that stores regulatory condition data corresponding to each classification code, including at least access restriction information and inspection and quarantine requirements information.

[0091] The pre-built database of application requirements refers to a database that is pre-constructed and stores the application requirements data corresponding to each classification code, including at least the requirements for accompanying documents and the requirements for filling in application elements.

[0092] The declared regulatory conditions refer to the regulatory measures information corresponding to the classification code extracted from the pre-set regulatory conditions database, including at least access restriction information and inspection and quarantine requirements information.

[0093] The application requirements and conditions refer to the application specification information corresponding to the classification code extracted from the preset application requirements database, which includes at least the requirements for accompanying documents and the requirements for filling in application elements.

[0094] Application requirement constraint information refers to the complete set of constraints obtained by integrating application regulatory conditions and application requirement conditions, which is used to guide users to adjust application data.

[0095] Access restriction information refers to regulations related to access, such as whether an import license is required for a specific commodity classification code, and whether it belongs to the prohibited or restricted import categories.

[0096] Inspection and quarantine requirements refer to the regulations concerning whether a specific commodity classification code requires animal and plant quarantine, quality inspection, or other inspection and quarantine-related procedures.

[0097] Accompanying documentation requirements refer to the types of documents that need to be attached when making a declaration for a specific commodity classification code, such as certificate of origin, packing list, and contract.

[0098] The requirements for filling in declaration elements refer to the commodity attribute fields that must be filled in the customs declaration form for specific commodity classification codes, such as brand, model, and material.

[0099] In some possible implementation methods, the declaration requirements differ for different classification codes. For example, classification under code A may only require a contract and invoice, while classification under code B requires an additional certificate of origin or license. If a user selects code B based solely on tariffs but fails to prepare the corresponding documents, they will not pass customs inspection. Traditional methods only match the declaration requirements of a single code, and users cannot know in advance what additional materials are required after switching to other codes, resulting in situations where even if a more favorable tariff is discovered, it cannot be applied.

[0100] This step is designed to address this issue. By independently retrieving the corresponding regulatory conditions and application requirements for each code in the candidate application code set, the system can clearly list the gaps between each candidate solution and the information currently provided by the user. These gaps include: the types of documents that need to be supplemented, the fields of application elements that need to be filled in, and the permits or inspections that may be required.

[0101] In subsequent S5 updates, user-submitted data will be automatically adjusted based on these constraints (e.g., supplementing missing fields, prompting for uploaded documents) to generate a complete submission plan that meets the compliance requirements of this coding.

[0102] It should be noted that all generated declaration plans are feasible options that can pass customs review after the user supplements the required materials. The system does not assess the risk level of the plans, but rather quantifies the differences in tariff amounts and required additional materials for each plan, allowing users to make a choice based on a comprehensive trade-off between tariff savings and operational convenience. This design ensures the practicality of the plans, providing the possibility of lower tax rates while clearly defining the additional effort required to achieve compliance, thus preventing users from failing to submit their declarations due to incomplete materials.

[0103] S5 generates adjusted declaration data based on declaration requirement constraints, calculates the target tariff result for each candidate declaration code, and generates the declaration scheme for each candidate declaration code. Please refer to [link / reference]. Figure 2 .

[0104] Perform the following operations independently for each candidate application code:

[0105] S501, generate the adjusted declaration data.

[0106] Based on the regulatory conditions corresponding to the candidate declaration code, the valid declaration information is adjusted for compliance. For example, if the regulatory conditions require an import license for goods under this code, but the user's current valid declaration information does not include the license number, this field is marked as "to be supplemented," and the user is prompted to apply for and upload the license. If the regulatory conditions require specific quarantine, the corresponding quarantine declaration mark is added to obtain the first declaration data that meets the regulatory requirements.

[0107] Based on the application requirements corresponding to the candidate application code, the aforementioned first application data undergoes field supplementation and standardization. For example, if the application requirements specify application elements such as brand and model, and the user's current information is missing, the system generates blank fields for the user to fill in; if the accompanying documents require a certificate of origin, the system checks whether the user has already uploaded it; if not, it is marked as "to be supplemented." After completing the above supplementation and standardization, the resulting data is the second application data, which is then determined as the adjusted application data. This data represents complete application information that meets all compliance requirements for the candidate application code.

[0108] To ensure clarity and conciseness in the description of the following embodiments, a brief introduction to the relevant terms is given first:

[0109] The first declaration data refers to the intermediate data that meets regulatory requirements (such as access restrictions and inspection and quarantine) after the valid declaration information has been adjusted for compliance according to the declaration regulatory conditions.

[0110] The second application data refers to the complete data that meets the application requirements after supplementing and standardizing the fields of the first application data according to the application requirements, and this data is determined as the adjusted application data.

[0111] The adjusted application data refers to the complete application information that meets all compliance requirements of the candidate application code, and is the same as the second application data.

[0112] "To be supplemented" refers to the system marking missing essential information (such as license number, certificate of origin, declaration element fields, etc.) to prompt the user that it must be supplemented.

[0113] In some possible implementations, users provide only one set of initial declaration data. When the system generates multiple candidate classification codes, the regulatory conditions and declaration requirements for each code may differ, meaning the same original data cannot simultaneously meet the compliance requirements of all codes. For example, code A requires only basic documentation, while code B additionally requires a certificate of origin. Traditional methods cannot automatically adapt to this, and even if users are aware of the tariff differences, they cannot quickly generate compliant declaration data for each code.

[0114] This step is designed to solve this problem by using the application requirements and constraints of the candidate application code as the rule to differentiate and mark the original data, rather than making uniform modifications.

[0115] Specifically, the process begins by checking whether the original data meets regulatory requirements (access restrictions, quarantine requirements). If not, items are marked as needing supplementation, resulting in the first declaration data. Then, the missing fields are checked and supplemented according to the declaration requirements (accompanying documents, declaration elements), resulting in the second declaration data, which is used as the adjusted declaration data. During the process, only marking and prompting are made; no fabricated data is used, ensuring that the user's supplemented solution can pass customs review. The adjustment results differ for different codes, providing a basis for subsequently quantifying the operational convenience of each solution.

[0116] S502, calculate the target tariff result corresponding to the candidate declaration code.

[0117] After obtaining the adjusted declaration data corresponding to the candidate declaration code in S501, value characteristics (including total declared price, quantity, currency, etc.) are extracted from the adjusted declaration data, and at the same time, the tariff rate corresponding to the candidate declaration code and the applicable rules for ad valorem tax, specific tax or compound tax are obtained from the preset destination country tariff database.

[0118] The amount of customs duty shall be calculated according to the applicable rules for ad valorem, specific, or compound duties:

[0119] If it is an ad valorem tax, the adjusted total declared price (converted to the local currency of the destination country at the exchange rate on the day) is multiplied by the tax rate to obtain the tariff amount;

[0120] If it is a specific tax, the adjusted quantity is multiplied by the unit tax amount to obtain the customs duty amount;

[0121] If it is a compound tax, then both the ad valorem and specific portions are calculated and then summed.

[0122] The result obtained is the target tariff result corresponding to the candidate declaration code.

[0123] It should be noted that if the value information in the adjusted declaration data changes due to regulatory requirements (such as a change in the unit of measurement or price caliber), the adjusted value will be used for calculation.

[0124] To ensure clarity and conciseness in the description of the following embodiments, a brief introduction to the relevant terms is given first:

[0125] The target tariff result refers to the final amount of tariff payable calculated according to the tariff schedule of the destination country based on the adjusted declaration data for a specific candidate declaration code.

[0126] In some possible implementations, users may meet the regulatory requirements of a candidate code by adjusting the declared data (such as changing the unit of quantity or price caliber), but this also alters the value benchmark used for tariff calculation. For example, if a commodity is declared from "pieces" to "kilograms," both the declared total price and quantity will change. If the original initial value is still used for calculation, the tariff result will not match the actual declaration, affecting the accuracy of the comparison.

[0127] This step is designed to address this issue by using value information from the adjusted declaration data, rather than the original data. Specifically, it extracts the latest value characteristics from the adjusted declaration data output by S501, matches them with the corresponding tax rate and the applicable rules for ad valorem, specific, or compound taxes, and recalculates the customs duty. This ensures that the customs duty amount strictly corresponds to the final declaration content, providing a true and reliable basis for comparing tax differences in subsequent scenarios. Furthermore, when ad valorem or specific taxes are applied, the total price or quantity is used as the tax base, respectively, which conforms to the actual customs tax collection rules.

[0128] S503 generates the application scheme corresponding to each candidate application code.

[0129] The adjusted declaration data generated by S501 (i.e., complete declaration information that meets all compliance requirements of the code), the target tariff result calculated by S502, and the declaration requirement constraint information (including the list of documents and the list of declaration elements) corresponding to the code are structured and linked to form an independent declaration scheme.

[0130] The declaration scheme should include at least: the candidate declaration code, the adjusted complete declaration data, the target tariff amount, and a list of supplementary materials (i.e., the items marked "to be supplemented"). All declaration schemes corresponding to the candidate declaration codes together constitute a set of declaration schemes for subsequent multi-scheme comparative analysis.

[0131] To ensure clarity and conciseness in the description of the following embodiments, a brief introduction to the relevant terms is given first:

[0132] A declaration scheme refers to an independent scheme unit formed by structurally linking candidate declaration codes, adjusted declaration data, target tariff results, and declaration requirement constraints information (including document list and declaration element list) corresponding to the code.

[0133] The list of materials to be supplemented refers to the list of documents or information items that the user must supplement based on the "to be supplemented" mark in the application plan (such as import licenses, certificates of origin, missing application elements, etc.).

[0134] In some possible implementations, users face multiple candidate codes and their respective adjusted data and tariff results, making it difficult to directly compare the advantages and disadvantages of different options. For example, option A has lower tariffs but requires an additional certificate of origin, while option B has slightly higher tariffs but requires no supplementary materials. Traditional methods only output tariff figures and cannot provide information on differences in required documentation.

[0135] This step is designed to address this issue by aggregating the adjusted data, tariff amounts, and supplementary material lists associated with each candidate code into a single, complete solution unit. All solutions are stored using a unified data structure, facilitating subsequent quantitative comparisons in S6 (e.g., tariff savings, material complexity). Through this solution-based encapsulation, the system can clearly demonstrate to users the additional effort required and the tariff benefits gained from using different classification codes, enabling users to make informed decisions while maintaining compliance. Simultaneously, the solution fully retains the adjusted declaration data, allowing users to directly supplement any missing materials based on the solution and submit to customs, achieving a seamless transition from assessment to declaration.

[0136] S5 independently generates corresponding adjusted declaration data and target tariff results for each candidate declaration code, ultimately forming multiple structured declaration schemes. This achieves a closed-loop transformation from a set of candidate classification codes to a complete scheme that can be directly used for customs submission. Traditional technologies can only output a single declaration result or raw data, and users cannot know the actual tariff amount corresponding to different classification codes or the additional materials required.

[0137] Furthermore, S5 uses declaration requirement constraints to differentiate and adjust the user's original data, and recalculates tariffs based on the adjusted value information. This allows users to intuitively compare the specific tariff costs and supplementary material lists of each option, thereby enabling them to independently choose the optimal declaration path with the lowest total cost (tariff savings plus ease of operation) under the premise of complete legality and compliance. This significantly improves declaration efficiency and tax optimization capabilities, and solves the pain point of existing technologies where multiple candidate codes cannot automatically adapt to declaration requirements and quantitatively compare data.

[0138] S6 compares and analyzes multiple application schemes, generates and outputs the comparison results of multiple schemes.

[0139] The difference between the target tariff result for each declaration scheme and the initial tariff result is calculated to obtain the tariff savings amount of each declaration scheme relative to the original declaration, which is used as the tax and fee savings data of the declaration scheme relative to the original declaration. Furthermore, the differences between the target tariff results for each declaration scheme are calculated pairwise to obtain the tax and fee difference data between each declaration scheme.

[0140] It should be noted that "pairwise difference calculation" does not require a complete pairwise calculation for all options (e.g., options A and B, A and C, B and C, etc.), but rather aims to quantify the degree of tariff differences between options. In practice, one or more of the following methods can be selected:

[0141] (1) Sort all the target tariff results from low to high and calculate the difference between adjacent options;

[0142] (2) Calculate the difference (range) between the maximum and minimum tariff values ​​among all options;

[0143] (3) Using the lowest tariff scheme as a benchmark, calculate the difference between the other schemes and the lowest value.

[0144] The above methods clearly reflect the tax differences between the schemes and avoid unnecessary calculation costs. This embodiment does not limit the specific algorithm and can be flexibly selected according to the number of schemes.

[0145] Based on the regulatory conditions (including access restrictions and inspection and quarantine requirements) corresponding to each application scheme, the compliance of each application scheme is determined. For example, if the regulatory conditions for a certain application scheme include the requirement to obtain an import license, which the user has not yet obtained, the compliance risk of that scheme is relatively high; if there are no special restrictions in the regulatory conditions, the compliance risk is low.

[0146] Based on the judgment results, the compliance risk results corresponding to each application plan are generated, and the risk level of each application plan is divided into three levels (e.g., high risk, medium risk, and low risk), thus obtaining the compliance risk difference data between each application plan.

[0147] Data on tax savings, tax differences, and compliance risks are integrated to generate a multi-option comparison. This comparison is presented in a structured format (such as tables or lists) to allow users to intuitively compare the differences in tariff costs, savings, and compliance requirements among different declaration options.

[0148] Output the comparison results of multiple options, for example, by displaying them to the user through a display interface.

[0149] To ensure clarity and conciseness in the description of the following embodiments, a brief introduction to the relevant terms is given first:

[0150] Tax savings data refers to the difference between the target tariff result and the initial tariff result for each declaration scheme, representing the amount of tariff that can be saved by the scheme compared to the original declaration.

[0151] Tax and fee difference data refers to the difference in target tariff results between different declaration schemes, which is used to measure the tariff cost gap between different schemes.

[0152] Compliance risk outcome refers to the conclusion obtained after determining the compliance of each declaration scheme based on the corresponding declaration regulatory conditions, and is used to assess whether the scheme meets customs regulatory requirements.

[0153] Risk level refers to the classification of the application plan based on the compliance risk results, such as high risk, medium risk, and low risk, presenting the differences in compliance risk in a quantitative way.

[0154] Compliance risk difference data refers to the difference in risk level between various application schemes, which is used to help users identify the level of compliance risk of different schemes.

[0155] The multi-option comparison results refer to the comparative information formed by integrating tax and fee savings data, tax and fee difference data, and compliance risk difference data, which is used to help users choose the optimal declaration option.

[0156] In some possible implementations, users obtain multiple candidate declaration schemes through S5, each containing different classification codes, adjusted declaration data, target tariff results, and a list of required supplementary materials. However, simply providing a list of schemes is insufficient to help users make the optimal decision. Users need a clear understanding of the differences in tariff costs among the various schemes, as well as the level of compliance risk. Traditional methods only output a single result or raw data, preventing users from comparing the overall advantages and disadvantages of multiple schemes.

[0157] This step is designed to address this issue by quantifying tariff savings through comparing the target tariff results of multiple options with the initial tariff results; quantifying tariff differences by comparing the options themselves; and assessing compliance risks based on the regulatory requirements for each option, thus establishing risk level differences. Finally, the multi-dimensional comparative information is integrated into a unified multi-option comparison result, allowing users to clearly see "which option has lower tariffs, how much is saved, and what compliance risks are involved."

[0158] Furthermore, the tax savings data reflects the amount of customs duties that can be saved by adopting this scheme compared to the user's original declaration, thus incentivizing users to proactively optimize their declarations.

[0159] Tax difference data reflects the tariff competition between options, helping users quickly identify the option with the lowest tariff.

[0160] The compliance risk results will warn users that some solutions may involve licenses or special quarantine requirements, so as to avoid ignoring compliance risks by focusing only on tariffs.

[0161] By combining these three factors, users can make a reasonable trade-off between tariff savings and compliance convenience, and choose the declaration scheme that best suits their actual situation.

[0162] This step achieves a closed loop from generating multiple options to intelligent comparison and recommendation, solving the problems of existing technologies that cannot quantify the differences between multiple options and make it difficult for users to make comprehensive decisions, and significantly improving the practicality of application evaluation and user experience.

[0163] S7 receives the target scheme and material information selected by the user, performs consistency verification, and outputs the final application evaluation result.

[0164] The system receives the target declaration scheme selected by the user based on the multi-scheme comparison results output by S6, as well as the material information uploaded by the user according to the declaration requirements and constraints in the target declaration scheme. The material information includes electronic files or field data of accompanying documents (such as certificates of origin, licenses, contracts, packing lists, etc.).

[0165] Based on the application requirements and conditions corresponding to the target application plan (including the requirements for accompanying documents and the requirements for filling in application elements), the consistency of the material information uploaded by users is verified.

[0166] Specifically, the field data in the material information is matched and verified item by item with the application requirements. For example, it is checked whether the necessary document types are missing, whether the document format meets the requirements, and whether the application element fields (such as brand and model) are filled in completely and in the correct format. The matching results (consistent or inconsistent) of each verification item are obtained.

[0167] The matching results are summarized and processed. If all matching results are consistent, the verification result is consistent. At this time, the final declaration assessment result is generated, such as "The declaration information is complete and compliant and can be formally submitted to the customs". The final declaration assessment result is output (for example, displayed to the user through the display interface or exported as a declaration document).

[0168] If at least one of the matching results is inconsistent, then perform the following operation:

[0169] Identify the declaration requirements corresponding to the inconsistent verification items; based on the inconsistent verification items, locate the type of deviation between the corresponding material field data and the declaration requirements. The deviation type includes at least the following: missing field (e.g., no certificate of origin uploaded), incorrect field format (e.g., incorrect date format), or document mismatch (e.g., the uploaded document type does not meet the requirements).

[0170] Generate verification feedback information based on the deviation type (e.g., "Certificate of origin is missing, please supplement" or "Brand field format is incorrect, should be text"), and output the verification feedback information to prompt the user to correct or supplement the material information, and trigger a new consistency verification of the material information (i.e. return to this step to receive the corrected material information again).

[0171] The above process ensures that the final application materials submitted by the user fully comply with the customs compliance requirements of the target application plan, thus avoiding application failure due to incomplete materials or incorrect format.

[0172] To ensure clarity and conciseness in the description of the following embodiments, a brief introduction to the relevant terms is given first:

[0173] The target declaration plan refers to the declaration plan that the user selects from the comparison results of multiple plans and intends to actually implement. It includes information such as candidate declaration codes, adjusted declaration data, target tariff results, and a list of supplementary materials.

[0174] Material information refers to the electronic files of accompanying documents and the field data of application elements uploaded by users in accordance with the application requirements and constraints (accompanying document requirements and application element filling requirements) in the target application plan.

[0175] Consistency verification refers to the process of matching the field data in the materials uploaded by the user with the application requirements and conditions corresponding to the target application plan item by item to determine whether all compliance requirements are met.

[0176] The matching result refers to the conclusion obtained after comparing each verification item (such as document type, field completeness, and format standardization), including consistency and inconsistency.

[0177] The verification result refers to the conclusion obtained after summarizing all matching results. When all matching results are consistent, the verification result is consistent; otherwise, it is inconsistent.

[0178] Verification feedback information refers to the prompt information generated based on the deviation type when the verification result is inconsistent, which guides the user to correct or supplement the materials.

[0179] Deviation types include missing fields (required documents or declaration elements are not provided), incorrect field formats (the provided format does not conform to customs regulations), and document mismatch (the uploaded document type does not meet the requirements).

[0180] The final declaration assessment result refers to the conclusion generated after verification, confirming the completeness and compliance of the material information, and is used to guide users in formally submitting their declarations to customs.

[0181] In some possible implementations, users select the optimal declaration scheme via S6, but this scheme requires users to supplement specific materials (such as licenses, certificates of origin, or filling in specific declaration elements). Traditional methods only indicate "supplementation required" and cannot automatically verify whether the materials uploaded by the user meet the requirements, leading to users repeatedly submitting incorrect materials and affecting declaration efficiency.

[0182] This step is designed to address this issue. Using the application requirements of the target proposal as the verification standard, it automatically matches each item of the user-uploaded materials, accurately identifying missing, incorrectly formatted, or mismatched verification items, and generating clear correction guidelines. Through a closed-loop feedback mechanism, users can complete the material corrections under the system's guidance until full compliance is achieved.

[0183] Specifically, when the verification passes, the system outputs the final declaration assessment result, which the user can then formally submit to customs. When the verification fails, the system not only informs the user of "inconsistency," but also specifies which field is missing, which format is incorrect, or which type of document is mismatched, and provides correction suggestions. This ensures that the final declaration materials submitted by the user are completely consistent with the target declaration plan, avoiding declaration failure or rejection due to material issues.

[0184] This step establishes a complete closed loop from solution recommendation to material verification, solving the problem of existing technologies being unable to automatically verify the consistency between user-submitted materials and application requirements. It significantly reduces the cost of repeated modifications for users due to non-compliant application materials, and improves the application success rate and user experience.

[0185] This application proactively generates a set of candidate declaration codes by extracting commodity attribute features and performing multi-condition searches. Then, it uses the declaration regulatory conditions and declaration requirements corresponding to each candidate code to make differentiated compliance adjustments to the user's original declaration data (marking missing documents and supplementing declaration elements). Based on the adjusted value information, it recalculates tariffs, forming multiple structured declaration schemes. Since each scheme is a feasible solution that can pass customs review after supplementing the required materials, users can not only intuitively compare the tariff savings of each scheme with the list of additional materials required, but also make a quantitative trade-off between tariff costs and operational convenience. This solves the pain point of existing technologies where users can only passively accept a single declaration result and cannot learn about better compliant declaration paths. Under the premise of legality and compliance, it significantly improves the ability to optimize tax and fees in declarations and the space for independent decision-making.

[0186] This application calculates tax savings by comparing the target tariff results with the initial tariff results for each scheme, and performs tariff difference calculations and compliance risk level classifications between schemes. It then integrates these calculations to generate a multi-scheme comparison result that includes both tax and compliance risk differences, allowing users to easily identify the lowest tariff scheme and its corresponding regulatory requirements. Once a user selects a target scheme and uploads materials, the application uses the scheme's declaration requirements as the standard to perform item-by-item consistency checks on the uploaded documents and field data. This accurately identifies the types of deviations such as missing documents, format errors, or mismatches, and generates clear correction guidelines. Through closed-loop feedback, it guides users to complete the material corrections. This achieves a complete closed loop from scheme recommendation to automatic material verification, solving the problems of existing technologies that cannot quantify the differences between multiple schemes and users repeatedly submitting incorrect materials, significantly improving the declaration success rate and overall declaration efficiency.

[0187] It should be noted that the preset data involved in the above embodiments (including but not limited to preset destination country tariff database, preset classification code database, preset regulatory condition database, preset declaration requirement database, preset anomaly judgment threshold, preset status classification threshold range, preset location credibility threshold, etc.) are all pre-built based on the publicly released regulations, tariffs, classification standards and industry practices of various countries' customs, and do not involve any undisclosed or illegal data sources.

[0188] It should be further clarified that the assessment method provided in this application is only intended to help users verify the compliance of their declaration data, offer optional classification codes, and compare the tax differences and compliance requirements between different schemes before the user formally submits the declaration to customs. This aims to help users reduce the risk of declaration errors due to incomplete information or improper classification, and improve declaration efficiency and compliance. All generated declaration schemes and adjustment suggestions must be confirmed by the user in accordance with the laws and regulations of the destination country, and the user assumes corresponding responsibility. This application absolutely does not encourage, instigate, or guide users to engage in any illegal or irregular activities such as false declarations, underreporting prices, misreporting classifications, or evading customs duties. When making actual declarations, users must strictly abide by the laws and regulations of the customs of each country and truthfully, accurately, and completely fill in the declaration information. The technical solution in this application is only an auxiliary tool; the final declaration decision and legal responsibility are borne by the user.

[0189] The foregoing has shown and described the basic principles, main features, and advantages of this application. Those skilled in the art should understand that this application is not limited to the above embodiments. The embodiments and descriptions in the specification are merely illustrative of the principles of this application. Various changes and modifications can be made to this application without departing from the spirit and scope thereof, and all such changes and modifications fall within the scope of this application as claimed. The scope of protection of this application is defined by the appended claims and their equivalents.

Claims

1. A method for assessing the quality of customs declarations used in cross-border e-commerce, characterized in that, The method includes: Obtain valid declaration information and extract the valid declaration information to obtain a feature dataset, wherein the feature dataset includes at least identification features, commodity attribute features and value features; The identification features are matched with the preset destination country's tariff database to obtain basic tariff information; The initial tariff result is obtained by calculating the value characteristics and the basic tariff information. The product attribute features are compared with a preset classification coding database under multiple conditions to generate a set of candidate declaration codes; Extract the candidate application code set to obtain the application requirement constraint information corresponding to each candidate application code. The application requirement constraint information includes application supervision conditions and application requirement conditions. The valid declaration information is adjusted based on the declaration supervision conditions and the declaration requirements to generate adjusted declaration data. The target tariff result corresponding to each candidate declaration code is calculated based on the adjusted declaration data. The adjusted declaration data is then associated with the target tariff result to generate a declaration scheme corresponding to each candidate declaration code. A comparative analysis of multiple application schemes is performed to generate a multi-scheme comparison result that includes differences in tax fees and compliance risks, and the multi-scheme comparison result is output. Receive the target application plan selected by the user based on the multi-plan comparison results and the uploaded material information; Based on the application requirements corresponding to the target application scheme, the consistency of the material information uploaded by the user is verified, and the verification result is obtained. When the verification results are consistent, the final application evaluation result is output.

2. The method according to claim 1, characterized in that, The process of obtaining valid declaration information includes: Obtain customs declaration information and perform field integrity and format compliance checks on the customs declaration information to obtain compliance verification results; If the compliance verification result is compliant, the customs declaration information will be determined as valid declaration information; If the compliance verification result is non-compliant, output the reason for non-compliance.

3. The method according to claim 1, characterized in that, The step of performing a multi-condition search between the product attribute features and a preset classification coding database to generate a candidate declaration code set includes: The product attribute features are deconstructed to extract classification elements including product use, structural features, and performance parameters; The classification elements are mapped to obtain corresponding attribute matching relationships, and search conditions are generated based on the attribute matching relationships. The search conditions include at least usage matching conditions, structure matching conditions, and parameter range conditions. Based on the search criteria, the coding attributes in the preset classification coding database are matched and filtered to obtain candidate coding data; The candidate coding data is deduplicated and its validity is screened to generate a set of candidate application codes.

4. The method according to claim 3, characterized in that, The step of extracting the candidate application code set to obtain the application requirement constraint information corresponding to each candidate application code includes: Using each candidate application code in the candidate application code set as a retrieval key, a correlation retrieval is performed in the preset regulatory conditions database and the preset application requirements database to obtain the regulatory conditions data and application requirements data corresponding to each candidate application code. The regulatory conditions data are analyzed to extract the regulatory conditions for declaration, which include at least access restriction information and inspection and quarantine requirements information; The application requirement data is parsed to extract the application requirement conditions, which include at least the requirements for accompanying documents and the requirements for filling in application elements; The extracted application supervision conditions and application requirements are integrated to obtain the application requirement constraint information corresponding to each candidate application code.

5. The method according to claim 4, characterized in that, The process of adjusting the valid application information based on the application supervision conditions and the application requirements to generate adjusted application data includes: Based on the aforementioned regulatory conditions, the valid declaration information is adjusted for compliance to obtain first declaration data that meets regulatory requirements; Based on the aforementioned application requirements, the first application data is supplemented and standardized to obtain second application data that meets the application requirements. The second application data is then determined as the adjusted application data.

6. The method according to claim 5, characterized in that, The step of calculating the target tariff result for each candidate declaration code based on the adjusted declaration data, associating the adjusted declaration data with the target tariff result, and generating a declaration scheme for each candidate declaration code includes: Based on the candidate declaration code, the corresponding tariff rate is obtained from the preset destination country tariff database, and the tax is calculated on the second declaration data in combination with the value characteristics to obtain the corresponding target tariff result. The second declaration data is associated with the target tariff result to generate a declaration scheme corresponding to each candidate declaration code.

7. The method according to claim 6, characterized in that, The comparative analysis of multiple declaration schemes generates a multi-scheme comparison result that includes differences in tax fees and compliance risks, including: The difference between the target tariff result corresponding to each declaration scheme and the initial tariff result is calculated to obtain the tax and fee savings data of each declaration scheme relative to the original declaration. The differences between the target tariff results corresponding to each declaration scheme are calculated to obtain the tax and fee difference data between the declaration schemes. Based on the regulatory conditions corresponding to each application plan, the compliance of each application plan is determined, and the compliance risk results corresponding to each application plan are obtained. Based on the compliance risk results, the risk levels of each application plan are classified to obtain the compliance risk difference data between the application plans. The tax savings data, tax difference data, and compliance risk difference data are integrated to generate a multi-scheme comparison result.

8. The method according to claim 7, characterized in that, The process involves verifying the consistency of the uploaded materials based on the application requirements corresponding to the target application scheme, and obtaining the verification results, including: Based on the target application plan, obtain the application requirements and conditions in the target application plan; Analyze the material information uploaded by users and extract the material field data; The consistency of the material field data with the application requirements is verified to obtain the verification result.

9. The method according to claim 8, characterized in that, The step of verifying the consistency between the material field data and the application requirements to obtain the verification result includes: The material field data is matched and verified item by item with the application requirements to obtain the matching results of each verification item; The matching results are summarized and processed. If all matching results are consistent, the verification result is considered consistent.

10. The method according to claim 9, characterized in that, If at least one of the matching results is inconsistent, the method further includes: Determine the application requirements corresponding to the inconsistent verification items; Based on the aforementioned inconsistencies, the type of deviation between the corresponding material field data and the application requirements is identified. The deviation type includes at least field missing, field format mismatch, or document mismatch. Generate and output verification feedback information based on the deviation type. The verification feedback information is used to prompt the user to correct or supplement the material field data and trigger a new consistency verification of the material information.

Images