A method for data drainage by aggregating and integrating the functions of third-party systems

Abstract

This invention discloses a method for data diversion from aggregating and integrating three-party systems. By accessing the invoice query platform, billing platform, accounting platform, reporting platform, and OCR recognition system of the finance and taxation cloud platform, while providing invoice, accounting, and tax reporting functions, it introduces, aggregates, and integrates third-party business data platforms. The aggregated and integrated data streams are then used to provide data diversion services to users based on preset rules. The preset rules are to package platform functional rights and interests into service commodities, map the service commodities with the rights and interests, and sell them through cooperating third-party business platforms.

Description

Technical Field

[0001] The present invention belongs to the field of tax management technology, and in particular relates to a method for data drainage by aggregating and integrating the functions of three-party systems. Background Art

[0002] In view of the current changes in the tax environment of the Golden Tax Phase IV, there are relatively few system platforms that can provide comprehensive services such as invoicing, accounting and declaration. Some systems that provide comprehensive services are only relatively complete in one certain service, and the service functions in other aspects cannot meet the current Golden Tax Phase IV all-electric business services.

[0003] With the launch of the all-electronic business of the Golden Tax Phase IV, various tax-related businesses are gradually entering the era of full electronic informationization, from corporate invoicing to financial and tax accounting, and from accounting to tax declaration. The market is currently in urgent need of comprehensive software services. Summary of the Invention

[0004] One of the embodiments of the present invention is a method for data drainage by aggregating and integrating the functions of third-party systems. Under the general environment of the fourth phase of the Golden Tax System, this method uses the financial and tax cloud platform system to interconnect enterprises with various rights and interests functions such as purchase and sales invoice channels, invoice pools, OCR intelligent invoice recognition channels, accounting, and declaration, and realizes customer and data drainage by cross-platform aggregation and integration of third-party system functions.

[0005] The cloud platform's aggregation and integration of third-party system functions adopts channels, orders, open interfaces, data drainage and other methods to aggregate and integrate third-party system functions, package various functional services into different types of products, and the functions correspond to user rights and interests, forming a closed-loop ecosystem of the three parties to achieve data and user drainage.

[0006] The beneficial effect of the present invention is that it solves the problem of supporting all-round services from invoice issuance to corporate financial and tax accounting to tax declaration in the Jinsi environment. By matching rights and interests with mature business cooperation platforms, aggregating and integrating their mature business functions, it realizes all-round business service functions, thereby attracting customers and achieving data drainage. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] The above and other objects, features and advantages of the exemplary embodiments of the present invention will become readily apparent by reading the following detailed description with reference to the accompanying drawings, in which several embodiments of the present invention are shown by way of example and not limitation, in which:

[0008] Figure 1 A schematic diagram of the basic process of data diversion by aggregating and integrating three-party systems according to one embodiment of the present invention.

[0009] Figure 2Schematic diagram of an aggregated integrated three-party system according to one embodiment of the present invention.

[0010] Figure 3 Schematic diagram of an aggregated integrated three-party system according to one embodiment of the present invention.

[0011] Figure 4 Schematic diagram of an aggregated integrated three-party system according to one embodiment of the present invention. DETAILED DESCRIPTION

[0012] According to one or more embodiments, a method for integrating and draining data from a three-party system is provided. Figure 1 As shown. By connecting to the invoice query platform, billing platform, accounting platform, declaration platform, and OCR recognition system of the financial and tax cloud platform, on the basis of providing invoice, accounting, and tax declaration functions, it introduces, aggregates, and integrates third-party business data platforms, aggregates and integrates data streams, and provides data diversion services for users according to preset rules.

[0013] The Finance and Taxation Cloud Platform integrates the mature invoicing capabilities of third-party enterprises that support the Golden Tax IV electronic invoicing system through an interface. Enterprises select the invoicing function on the cloud platform and enter the necessary information. The cloud platform then calls the invoicing interface to send the invoice information. After the callback interface returns the corresponding invoice download path, the invoice information is displayed. The program has made technical improvements and support for certain new features of the Golden Tax IV electronic invoicing system. Traditional invoicing, whether electronic or paper, ultimately relies on the tax disk and UKey. After successful invoicing, the specific invoice document information, stamped with the invoice stamp, is required for printing and delivery. Unlike traditional invoice delivery methods, electronic invoices are a data transmission medium, not a physical entity. After invoice issuance, the invoice information is stored in the digital tax accounts of both the issuer and the recipient, eliminating the need for printed and stamped invoice documents. The cloud platform also uses an open interface to call the OCR intelligent invoice recognition function of third-party systems that support electronic invoice recognition, automatically generating voucher information from the recognized invoice data for financial accounting. OCR intelligent invoice recognition returns detailed invoice data after uploading the scanned image file of the invoice. After receiving the data, the cloud platform processes it and generates accounting voucher information for storage.

[0014] The cloud platform's accounting functions, invoicing, and OCR (Optical Character Recognition) generate accounting vouchers. By categorizing the voucher information, the difference between income and expenditure is calculated, generating basic financial statements. This financial statement processing utilizes a recursive statistical aggregation method based on subject categories. This provides the foundational data for constructing tax filing reports such as value-added tax, corporate income tax, and urban construction tax. Ultimately, the necessary tax filing reports are generated. Enterprises can choose to export these reports for manual filing or automatically file using the cloud platform's integrated third-party filing capabilities.

[0015] The cloud platform packages the mature business functions of the integrated third-party platforms into commodities. After being sold on the third-party platform, the order information is transmitted to the cloud platform through the message queue. The cloud platform opens an account for the enterprise that purchases the rights and initializes the configuration of the rights based on the order information. Considering that the enterprise has purchased different rights and interests multiple times, the page is displayed according to the function weight priority. For example, the invoicing business menu should be placed before the accounting business menu, and the accounting and other menu permissions should be placed before the declaration business menu button. According to the business priority weight, the system assigns a weight value to each function menu. When the enterprise logs in to the cloud platform to initialize the menu function list, the menu function array is recursively sorted according to the size of the weight, and the menu list is displayed in sequence. For details of the above business specific implementation process and data flow, please see the attachment. Figure 2 and attached Figure 3 .

[0016] The way of accessing related business functions is to distinguish between the Golden Tax Phase IV full electronic invoice business and the original normal business. The specific business process is that the full electronic invoice business uses the independent channel of the three-party system, and the original normal business uses the normal interface. Figure 4 .

[0017] The implementation methods of integrating three-party systems include adding a collection gateway, installing a host for the background management system, a PAAS platform server, installing a host for the third-party system, a data middle-end server, and a SAAS platform server. Using the cloud platform as a carrier, relevant functions such as the invoice pool for purchase and sales channels, intelligent invoice recognition and voucher generation, accounting and reporting functions are integrated to enable corporate customers to use the relevant functions while enjoying the data and functions brought about by the mutual communication of multiple rights and interests. The rights and interests between the systems of all parties are mapped to each other, and corporate customers can directly use the relevant functions of the integrated system to achieve data drainage. The integrated system can also sell the rights and interests of system-related functions as commodities, and the third-party cooperation platform will promote and sell the rights and interests products. After the customer purchases the product, the rights and interests are matched through mutual communication, and the corresponding rights and interests functions of the product are opened in the integrated system. The customer can directly log in to the integrated system to use the function, thereby achieving customer data drainage.

[0018] According to one or more embodiments, a method for aggregated and integrated three-party system data diversion includes:

[0019] The platform integrates various business functions used by corporate customers, including invoice issuance, purchase and sales invoice channels, invoice pools, OCR intelligent recognition of invoice face to generate vouchers, company accounting and tax declaration, as well as providing inquiry and solution services in related tax aspects.

[0020] When integrating various business functions, the system connects with established third-party platforms, integrating their mature business functions. Focusing on bookkeeping services, we connect the two independent business processes of invoicing and tax filing, creating a bridge between them. This streamlines the essential business processes from invoicing to bookkeeping and then to filing. This provides businesses with one-stop service, enabling them to access more than just the inherent business functions of a single system through system aggregation and integration of third-party systems.

[0021] There are many ways to realize the system aggregation and integration of the three-party system functions, including channels, orders, open interfaces, etc. The following is a detailed description of the business processes and data flows of invoices, OCR ticket recognition, declaration, and the connection of the three-party sales rights platform to the financial and tax cloud platform.

[0022] The embodiment of the present disclosure is developed using a microservice system architecture. Occasionally, network delays may occur in the interactive data transmission between businesses, resulting in timeouts and packet loss. Some business situations are solved using the message queue mode, but some businesses are not suitable for the message queue mode. We must ensure that 100% of business requests are sent to the target system, and repeated requests will only achieve one result, without causing adverse effects on other businesses or generating junk data. To solve this problem, we used the state machine idempotent mechanism and task scheduling xxl-job to achieve the situation where repeated requests return the same result. The implementation method is as follows: the record table records the request and sets the status, the task scheduling module scans the record table, and repeats the request for the request whose status is pending. After receiving the request, the target system completely processes the request according to the state machine idempotent mechanism, returns the result, and updates the record table to the completed status. The task scheduling module will exclude requests with a completed status in the next cycle scan. The implementation logic is as follows:

[0023] / / Task patrol method

[0024] RetryJobExecutor(){

[0025] / / Scan record table request status: 1 (pending request) data

[0026] List <requestrecord>requestRecordList=findRequestState("1");

[0027] / / Batch request

[0028] for(RequestRecord requestRecord:requestRecordList){

[0029] / / Record the number of requests and send email notifications when the maximum number of repeated requests is reached.

[0030] updateRequestCount(requestRecord);

[0031] Response response=RequertUtilsSDK.send(requestRecord);

[0032] if(reponse.isSuccess()){

[0033] / / After the request returns successfully, the record status is modified to: 2 (Completed)

[0034] updateRequestState(requestRecord);

[0035] }

[0036] / / The request fails or the returned data is not operated on, waiting for the next task scheduling

[0037] }

[0038] }

[0039] / / The target system receives the request and processes it

[0040] BusinessExecution(RequestRecord requestRecord){

[0041] / / State machine idempotent mechanism, judging business execution status based on status

[0042] String businessState=requestRecord.getBusinessState();

[0043] String businessId=requestRecord.getBusinessId

[0044] BusinessInfo businessInfo=findBusinessInfo(businessId,businessState);

[0045] / / Determine whether the business has been executed based on the status and business unique id

[0046] if(ObjectUtils.isEmpty(businessInfo)){

[0047] / / The status of the business is empty, execute the business

[0048] renturn execute(requestRecord);

[0049] }else{

[0050] / / This business status exists and no operation is performed

[0051] return Response.success();

[0052] }

[0053] }

[0054] According to one or more embodiments, a data diversion system based on aggregating and integrating three-party systems includes:

[0055] 1. The system integrates various financial and tax functions to meet the needs of businesses for invoicing, bookkeeping, and tax filing in the context of the Golden Tax Phase IV all-electronic invoice rollout. By integrating comprehensive functionality and integrating with the mature services of various third-party cooperative system platforms, the integrated system maintains stable operation for Golden Tax Phase IV businesses, attracting and driving customer traffic.

[0056] 2. The system packages its own rights and benefits into various products, mapping the products to the rights and benefits. When the three-party cooperative platform sells the products, the system and the three-party cooperative platform activate the corresponding rights and benefits for the purchaser through the agreed rights and benefits configuration.

[0057] 3. The main functions of system integration include invoicing, invoice identification, invoice pool query and declaration. When enterprises use various functions, the purchase and sales data required for accounting and the declaration data gradually accumulate to form a data flow, providing the basic data flow for subsequent risk warning and other businesses for the enterprise.

[0058] 4. To meet the requirements of the fully electric, mature business systems of the Golden Tax Phase IV, the cloud platform simultaneously selects two third-party systems to provide business services for some business functions. For corporate customers, this only applies to a single business function. To provide higher-quality service, the platform simultaneously connects to two mature business systems, calling them based on priority. If the first business system fails, the second backup third-party business system will be immediately called.

[0059] Therefore, the beneficial effects of the present invention include

[0060] 1. All functions of the present invention can actually solve the practical problems of corporate customers in invoicing, accounting and declaration under the Golden Tax Phase IV all-electronic invoice business, continuously contribute value, and customers are attracted by the value, naturally forming a customer data flow.

[0061] 2. The solution of the present invention realizes the mapping relationship between business and data through the rights and interests matching between systems, realizes the reflux and accumulation of business data, and forms a data-level drainage function.

[0062] 3. The solution of the present invention provides a universal way to integrate and connect with third-party systems, and provides traversal conditions for matching third-party application access rights.

[0063] It is worth noting that although the foregoing content has described the spirit and principles of the present invention with reference to several specific embodiments, it should be understood that the present invention is not limited to the disclosed specific embodiments, and the division into various aspects does not mean that the features of these aspects cannot be combined. Such division is merely for the convenience of expression. The present invention is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.< / requestrecord>

Claims

1. A method for data drainage from aggregating and integrating three-party systems, characterized in that: By connecting to the invoice query platform, billing platform, accounting platform, declaration platform, and OCR recognition system of the financial and tax cloud platform, on the basis of providing invoice, accounting, and tax declaration functions, it introduces, aggregates, and integrates third-party business data platforms, aggregates and integrates data streams, and provides users with data diversion services according to preset rules; The preset rules are to package the platform functional rights and interests into service commodities, map the service commodities with the rights and interests, and sell them through the cooperating third-party business platform; The third-party business platform includes a service product sales platform and a declaration platform; The data diversion is based on the microservice system architecture. Under the microservice system architecture, the state machine idempotence mechanism is adopted, combined with the task scheduling xxl-job, to achieve repeated requests returning the same result; The process of achieving repeated requests returning the same result is, The record table records the request and sets the status. The task scheduling module scans the record table and repeats the request with the request status as pending. After receiving the request, the target system fully processes the request according to the state machine idempotent mechanism and returns the result. The record table updates the status to completed. The task scheduling module will exclude requests with a completed status during the next scan cycle.

2. The data drainage method according to claim 1, characterized in that: The third-party service platform includes at least one backup platform with different service call priorities.

3. The data drainage method according to claim 1, characterized in that: The program logic to implement repeated requests to return the same result includes: Using task patrol, the scan record table request status is: waiting for request; Initiate requests in batches, record the number of requests, and notify when the maximum number of repeated requests is reached; After the request returns successfully, the record status is modified to: Completed; If the request fails or the returned data is not operated on, wait for the next task scheduling.

4. The data drainage method according to claim 3, characterized in that: The program logic for returning the same result to repeated requests also includes: The target system receives the request and processes it, including using the state machine idempotent mechanism to judge the business execution status according to the status. Determine whether the business has been executed based on the status and business unique id. If the status business is empty, execute the business. If the service status exists, no operation is performed.

5. The data drainage method according to claim 1, characterized in that: The purchase and sales data and declaration data required for accounting are gradually accumulated to form a data flow, providing the basic data flow for the subsequent risk warning business for users.

Images