Multi-form output electronic invoice conversion method and system

Abstract

The invention is suitable for the field of financial electronic information, and provides a multi-form output electronic invoice conversion method and system, and the method comprises the following steps: obtaining an original electronic invoice file, and enabling an original electronic invoice to support a plurality of formats; analyzing the original electronic invoice file to obtain structured data in a unified format; an output format is selected according to requirements, a corresponding invoice template is called for data filling, and the invoice template is stored in a template library; and after the final invoice file is generated, pushing the invoice file to the financial system and returning the invoice file to the user. The compatibility problem caused by invoice format differences among different industries, regions and finance and taxation systems is effectively solved, and the automation degree and conversion efficiency of invoice processing are improved.

Description

Technical Field

[0001] The present invention relates to the field of financial electronic information, and in particular to a method and system for converting electronic invoices output in multiple forms. Background Art

[0002] An invoice is a document used to record the transaction details between two parties when selling goods or providing services. It is an important financial document in business activities.

[0003] With the nationwide promotion and popularization of electronic invoices, they are playing an increasingly important role in daily corporate financial processing, tax management, and personal expense reimbursement. Compared with traditional paper invoices, electronic invoices offer advantages such as convenient storage, efficient circulation, and low management costs.

[0004] However, in actual application, due to the large differences in the standards for electronic invoice formats among different industries, regions, and financial and taxation systems, invoices often face serious format incompatibility issues when circulated across platforms and systems. For example, the tax system may require the use of the OFD format, while the company's financial software only supports PDF or XML formats. This format diversity requires users to frequently use manual operations or third-party tools to convert formats, which not only reduces work efficiency but also easily causes problems such as information loss, formatting errors, and even invalid signatures, affecting the compliance and effectiveness of invoices. Therefore, a method and system for converting electronic invoices with multiple output formats is proposed to solve the above problems. Summary of the Invention

[0005] In view of the shortcomings of the existing technology, the purpose of the present invention is to provide an electronic invoice conversion method and system with multiple output formats to solve the problems existing in the above-mentioned background technology.

[0006] The present invention is implemented as follows: a method for converting electronic invoices output in multiple formats, the method comprising the following steps:

[0007] Obtaining an original electronic invoice file, where the original electronic invoice file is input from a user or an external system, and the original electronic invoice supports multiple formats;

[0008] Parse the original electronic invoice file to obtain structured data in a unified format, which is used to identify the information contained in the electronic invoice;

[0009] Select the output format according to the requirements and call the corresponding invoice template to fill in the data. The invoice template is stored in the template library;

[0010] After the final invoice file is generated, it is pushed to the financial system and returned to the user.

[0011] As a further solution of the present invention: the step of obtaining the original electronic invoice file specifically includes:

[0012] Utilize intelligent recognition technology to identify and receive original electronic invoice files, and obtain invoice information from different data sources;

[0013] Identify the format of the uploaded original electronic invoice file;

[0014] Perform integrity check on the original electronic invoice file based on predefined rules;

[0015] Invoices are checked based on the digital signature in the invoice to verify the authenticity of the invoice.

[0016] As a further solution of the present invention: the step of parsing the original electronic invoice file to obtain structured data in a unified format specifically includes:

[0017] Identify the format of the original electronic invoice file and call the corresponding parsing tool for parsing;

[0018] Identify and extract core fields from invoice content using a combination of natural language processing and rule matching technology;

[0019] Unify the naming, unit conversion and format normalization of the extracted core fields;

[0020] All processed core fields are organized into a unified intermediate format according to the preset data structure.

[0021] As a further solution of the present invention, the step of organizing all processed core fields into a unified intermediate format according to a preset data structure specifically includes:

[0022] Build a standardized data structure model based on the common fields and industry extension fields of electronic invoices;

[0023] Importing the core fields of the standardized invoice into the data structure model according to preset mapping rules;

[0024] Before the data structure model outputs results, the AI ​​anomaly detection mechanism is used to perform logical consistency checks on core fields to detect data anomalies in invoices;

[0025] Combine the data structure model output results into structured data output in a specified format.

[0026] As a further embodiment of the present invention, the method further comprises:

[0027] During the electronic invoice format conversion process, multi-dimensional operation log data is collected through the full-link log collection mechanism;

[0028] Unify the operation log data and generate standardized log files;

[0029] Storing the log file in a database;

[0030] Identify the user role of the operation based on the log file and set the corresponding access control permissions.

[0031] Another object of the present invention is to provide an electronic invoice conversion system with multiple output formats, the system comprising:

[0032] The invoice input module is used to obtain the original electronic invoice file, which is input from the user or an external system and supports multiple formats;

[0033] Invoice parsing module, used to parse the original electronic invoice file to obtain structured data in a unified format, used to identify the information contained in the electronic invoice;

[0034] A format conversion and filling module is used to select an output format according to requirements and retrieve the corresponding invoice template for data filling. The invoice template is stored in the template library.

[0035] The output module is used to push the invoice file to the financial system and return it to the user after the final invoice file is generated.

[0036] As a further solution of the present invention: the invoice input module includes:

[0037] An intelligent recognition unit, used to recognize and receive original electronic invoice files using intelligent recognition technology, and to obtain invoice information from different data sources;

[0038] Format recognition unit, used to identify the format of the uploaded original electronic invoice file;

[0039] An integrity check unit, used to perform integrity check on the original electronic invoice file based on predefined rules;

[0040] The digital verification unit is used to check the invoice based on the digital signature in the invoice to verify the authenticity of the invoice.

[0041] As a further solution of the present invention: the invoice parsing module includes:

[0042] The identification and response unit is used to identify the format of the original electronic invoice file and call the corresponding parsing tool for parsing and processing;

[0043] A content extraction unit, which is used to identify and extract core fields from the content of the invoice by combining natural language processing and rule matching technology;

[0044] The data processing unit is used to perform unified naming, unit conversion and format normalization on the extracted core fields;

[0045] The data organization unit is used to organize all processed core fields into a unified intermediate format according to the preset data structure.

[0046] Compared with the prior art, the present invention has the following beneficial effects:

[0047] The present invention obtains original electronic invoice files in various formats from users or external systems, parses them and converts them into structured data in a unified format, thereby achieving standardized expression of invoice content. This standardization not only simplifies the subsequent data processing process, but also ensures the consistency and accuracy of information. Subsequently, the target output format is selected according to actual needs, and the corresponding invoice template in the template library is called to complete data filling and format conversion. After the final invoice file is generated, it is pushed to the financial system and returned to the user, thereby effectively solving the compatibility issues caused by differences in invoice formats between different industries, regions and financial and taxation systems, improving the automation level and conversion efficiency of invoice processing, reducing the risks of information loss, layout errors and signature invalidation caused by manual intervention, and ensuring the compliance and integrity of invoices during cross-platform circulation. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] Figure 1 A flowchart of a method for converting electronic invoices to multiple output formats.

[0049] Figure 2 A flowchart for obtaining an original electronic invoice file in an electronic invoice conversion method for outputting multiple formats.

[0050] Figure 3 The present invention is a flowchart for parsing an original electronic invoice file to obtain structured data in a unified format in an electronic invoice conversion method for outputting multiple formats.

[0051] Figure 4 The invention relates to a flowchart for organizing all processed core fields into a unified intermediate format according to a preset data structure in an electronic invoice conversion method for outputting multiple forms.

[0052] Figure 5 Flowchart for setting access control permissions for an electronic invoice conversion method with multiple output formats.

[0053] Figure 6 A schematic diagram of the structure of an electronic invoice conversion system with multiple output formats.

[0054] Figure 7This is a structural diagram of the invoice input module in an electronic invoice conversion system with multiple output formats.

[0055] Figure 8 This is a structural diagram of the invoice parsing module in an electronic invoice conversion system with multiple output formats. DETAILED DESCRIPTION

[0056] In order to make the purpose, technical solutions and advantages of the present invention clearer, the present invention is further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention.

[0057] The specific implementation of the present invention is described in detail below with reference to specific embodiments.

[0058] like Figure 1 As shown, an embodiment of the present invention provides a method for converting electronic invoices output in multiple formats, the method comprising the following steps:

[0059] S100, obtaining an original electronic invoice file, where the original electronic invoice file is input from a user or an external system, and the original electronic invoice supports multiple formats;

[0060] S200, parsing the original electronic invoice file to obtain structured data in a unified format for identifying information contained in the electronic invoice;

[0061] S300, selecting an output format according to requirements and retrieving a corresponding invoice template for data filling, wherein the invoice template is stored in a template library;

[0062] S400: After the final invoice file is generated, the invoice file is pushed to the financial system and returned to the user.

[0063] In an embodiment of the present invention, the present invention obtains original electronic invoice files in various formats from users or external systems, parses them and converts them into structured data in a unified format, thereby achieving standardized expression of invoice content. This standardization not only simplifies the subsequent data processing process, but also ensures the consistency and accuracy of the information. Subsequently, the target output format is selected according to actual needs, and the corresponding invoice template in the template library is called to complete data filling and format conversion. After the final invoice file is generated, it is pushed to the financial system and returned to the user, thereby effectively solving the compatibility issues caused by differences in invoice formats between different industries, regions and financial and taxation systems, improving the degree of automation and conversion efficiency of invoice processing, reducing the risks of information loss, layout errors and signature invalidation caused by manual intervention, and ensuring the compliance and integrity of invoices during cross-platform circulation.

[0064] It should be noted that the original invoices are in various formats, including PDF, XML, OFD and image formats. Due to the differences in file formats, there may be difficulties in identification, such as some conversion errors. The present invention converts the information of electronic invoices into a unified intermediate format, which is convenient for conversion to various formats. It can generate invoice files in various formats including but not limited to PDF, OFD, XML, etc.

[0065] like Figure 2 As shown, as a preferred embodiment of the present invention, the step of obtaining the original electronic invoice file specifically includes:

[0066] S101, using intelligent recognition technology to identify and receive original electronic invoice files, and to obtain invoice information from different data sources;

[0067] S102, identifying the format of the uploaded original electronic invoice file;

[0068] S103, performing integrity check on the original electronic invoice file based on predefined rules;

[0069] S104, verifying the invoice based on the digital signature in the invoice to verify the authenticity of the invoice.

[0070] In this embodiment of the present invention, when acquiring original electronic invoice files, intelligent recognition technology is first used to automatically identify and receive invoice information from various data sources, such as through web upload, API call, email attachment extraction, or cloud storage synchronization. The system then performs format recognition on the uploaded original electronic invoice file, determining its specific format type (e.g., PDF, XML, OFD, or image), ensuring that it can correctly process invoices of various formats. These files are then subjected to integrity checks based on a predefined set of rules, verifying the presence of key fields and the integrity of the files. For example, the system verifies the presence of necessary information such as the invoice code, invoice number, and invoice date. Finally, the system verifies the authenticity of the invoice based on the digital signature contained within it, ensuring that the invoice has not been tampered with and that it originates from the legitimate issuer. For example, when a user uploads an OFD-formatted invoice via the API, the system first identifies it as OFD, then checks that all required fields are included. Furthermore, the system verifies the authenticity and validity of the invoice by verifying the digital signature, thereby ensuring the accuracy and reliability of subsequent processing steps.

[0071] like Figure 3 As shown, as a preferred embodiment of the present invention, the step of parsing the original electronic invoice file to obtain structured data in a unified format specifically includes:

[0072] S201, identifying the format of the original electronic invoice file and calling the corresponding parsing tool for parsing;

[0073] S202, identifying and extracting core fields from the invoice content by combining natural language processing and rule matching technology;

[0074] S203, performing unified naming, unit conversion, and format normalization on the extracted core fields;

[0075] S204: Organize all processed core fields into a unified intermediate format according to a preset data structure.

[0076] In an embodiment of the present invention, when parsing raw electronic invoice files to obtain structured data in a unified format, the system first identifies the specific format of the original electronic invoice file (e.g., PDF, XML, OFD, or image) and, based on the identification results, invokes the corresponding parsing tool for processing. For example, PDF invoices are parsed using PDFBox or iText, while OFD invoices are parsed using the national standard OFD SDK to extract page elements. Subsequently, using a combination of natural language processing (NLP) and rule-matching techniques, core fields are identified and extracted from the invoice content, including but not limited to the invoice code, invoice number, invoice date, seller name and tax ID, buyer name and tax ID, itemized product information, and amount information. To ensure data consistency and comparability, the system then unifies the extracted core fields with unified naming, unit conversion, and format normalization. For example, all dates are standardized to "YYYY-MM-DD" and the currency unit is standardized. Finally, all standardized core fields are organized into a unified intermediate format, such as JSON or XML, according to a pre-set data structure. This serves as the basic data source for subsequent template filling and format conversion. For example, when processing a PDF invoice containing product details in multiple currencies, the system can not only accurately extract the name, quantity, unit price and amount of each product, but also convert its currency unit into RMB and organize this data according to a predefined structured model, thereby providing a basis for the subsequent generation of electronic invoices in different formats.

[0077] like Figure 4 As shown, as a preferred embodiment of the present invention, the step of organizing all processed core fields into a unified intermediate format according to a preset data structure specifically includes:

[0078] S214: Build a standardized data structure model based on the common fields and industry extension fields of electronic invoices;

[0079] S224, importing the core fields of the standardized invoice into the data structure model according to the preset mapping rules;

[0080] S234, before the data structure model outputs the results, the AI ​​anomaly detection mechanism is used to perform a logical consistency check on the core fields to detect data anomalies in the invoice;

[0081] S244: Combining the output results of the data structure model into structured data output in a specified format.

[0082] In an embodiment of the present invention, a standardized data structure model is first constructed based on the common fields and industry extension fields of the electronic invoice, and then the standardized core fields are filled into the data structure model according to the preset mapping rules to ensure that the positions of the fields are consistent and the semantics are clear. Of course, before outputting the results, the AI ​​anomaly detection mechanism will be used to perform a logical consistency check on the core fields to discover and mark any potential data anomalies, such as mismatched total amounts or incorrect date formats. Finally, the verified data structure model is combined into structured data in a specified format (such as JSON or XML) for subsequent template filling and format conversion. For example, when processing an invoice containing multiple commodity items, the system will not only ensure that the quantity, unit price and amount of each commodity are correct, but also use the AI ​​mechanism to check whether the total amount of these detailed items is consistent with the invoice total, thereby ensuring the accuracy and completeness of the data.

[0083] like Figure 5 As shown, as a preferred embodiment of the present invention, the method for converting electronic invoices output in multiple forms further includes:

[0084] S501: During the electronic invoice format conversion process, multi-dimensional operation log data is collected through the full-link log collection mechanism;

[0085] S502, uniformly processing the operation log data and generating a standardized log file;

[0086] S503, storing the log file in a database;

[0087] S504: Identify the user role of the operation according to the log file and set corresponding access control permissions.

[0088] In the embodiment of the present invention, a complete log record and authority management mechanism is also introduced in the process of electronic invoice format conversion. Specifically, in each link of the invoice conversion, the system automatically collects multi-dimensional operation log data including operation time, user identity, original file format, target file format, conversion status, call interface information, etc. through the full-link log collection mechanism. These log data will be processed in a unified manner and standardized log files will be generated according to the preset format to facilitate subsequent storage and analysis. The generated log files will be securely stored in the database to achieve long-term preservation and efficient retrieval. In addition, the user role performing the operation will be identified based on the log content, and access to the log will be controlled based on the role authority model to prevent unauthorized viewing or modification. For example, ordinary users can only view their own operation logs, while administrators have higher levels of audit authority. This mechanism not only improves the auditability and security of the system, but also provides data support for exception tracking, responsibility identification and compliance review.

[0089] like Figure 6 As shown, an embodiment of the present invention further provides an electronic invoice conversion system with multiple output formats, the system comprising:

[0090] The invoice input module 100 is used to obtain the original electronic invoice file, which is input from the user or an external system and supports multiple formats;

[0091] Invoice parsing module 200, used to parse the original electronic invoice file to obtain structured data in a unified format for identifying information contained in the electronic invoice;

[0092] The format conversion and filling module 300 is used to select the output format according to the requirements and call the corresponding invoice template for data filling. The invoice template is stored in the template library;

[0093] The output module 400 is used to push the final invoice file to the financial system and return it to the user after the final invoice file is generated.

[0094] In an embodiment of the present invention, the present invention obtains original electronic invoice files in various formats from users or external systems, parses them and converts them into structured data in a unified format, thereby achieving standardized expression of invoice content. This standardization not only simplifies the subsequent data processing process, but also ensures the consistency and accuracy of the information. Subsequently, the target output format is selected according to actual needs, and the corresponding invoice template in the template library is called to complete data filling and format conversion. After the final invoice file is generated, it is pushed to the financial system and returned to the user, thereby effectively solving the compatibility issues caused by differences in invoice formats between different industries, regions and financial and taxation systems, improving the degree of automation and conversion efficiency of invoice processing, reducing the risks of information loss, layout errors and signature invalidation caused by manual intervention, and ensuring the compliance and integrity of invoices during cross-platform circulation.

[0095] like Figure 7 As shown, as a preferred embodiment of the present invention, the invoice input module 100 includes:

[0096] An intelligent recognition unit 101 is used to recognize and receive original electronic invoice files using intelligent recognition technology, and to obtain invoice information from different data sources;

[0097] The format recognition unit 102 is used to recognize the format of the uploaded original electronic invoice file;

[0098] An integrity check unit 103 is configured to perform integrity check on the original electronic invoice file based on predefined rules;

[0099] The digital verification unit 104 is used to verify the invoice based on the digital signature in the invoice to verify the authenticity of the invoice.

[0100] like Figure 8 As shown, as a preferred embodiment of the present invention, the invoice parsing module 200 includes:

[0101] Identification and response unit 201, used to identify the format of the original electronic invoice file and call the corresponding parsing tool for parsing and processing;

[0102] Content extraction unit 202, for identifying and extracting core fields from the content of the invoice by combining natural language processing and rule matching technology;

[0103] The data processing unit 203 is used to perform unified naming, unit conversion and format normalization on the extracted core fields;

[0104] The data organizing unit 204 is configured to organize all processed core fields into a unified intermediate format according to a preset data structure.

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

[0106] It should be understood that, although the various steps in the flow chart of each embodiment of the present invention are shown in sequence according to the indication of the arrows, these steps are not necessarily performed in sequence according to the order indicated by the arrows. Unless otherwise specified herein, the execution of these steps is not strictly limited in order, and these steps can be performed in other orders. Moreover, at least a portion of the steps in each embodiment may include a plurality of sub-steps or a plurality of stages, and these sub-steps or stages are not necessarily performed at the same time, but can be performed at different times, and the execution order of these sub-steps or stages is not necessarily performed in sequence, but can be performed in turn or alternately with at least a portion of other steps or sub-steps or stages of other steps.

[0107] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program. The program can be stored in a non-volatile computer-readable storage medium. When the program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0108] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the disclosure in the specification and examples. This application is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered merely as exemplary, and the true scope and spirit of the present disclosure are indicated by the claims.

Claims

1. A method for converting electronic invoices into multiple output formats, characterized in that: The method comprises the following steps: Obtaining an original electronic invoice file, where the original electronic invoice file is input from a user or an external system, and the original electronic invoice supports multiple formats; Parse the original electronic invoice file to obtain structured data in a unified format, which is used to identify the information contained in the electronic invoice; Select the output format according to the requirements and call the corresponding invoice template to fill in the data. The invoice template is stored in the template library; After the final invoice file is generated, it is pushed to the financial system and returned to the user.

2. The method for converting electronic invoices into multiple output formats according to claim 1, characterized in that: The steps of obtaining the original electronic invoice file specifically include: Utilize intelligent recognition technology to identify and receive original electronic invoice files, and obtain invoice information from different data sources; Identify the format of the uploaded original electronic invoice file; Perform integrity check on the original electronic invoice file based on predefined rules; Invoices are checked based on the digital signature in the invoice to verify the authenticity of the invoice.

3. The method for converting electronic invoices into multiple output formats according to claim 1, characterized in that: The step of parsing the original electronic invoice file to obtain structured data in a unified format specifically includes: Identify the format of the original electronic invoice file and call the corresponding parsing tool for parsing; Identify and extract core fields from invoice content using a combination of natural language processing and rule matching technology; Unify the naming, unit conversion and format normalization of the extracted core fields; All processed core fields are organized into a unified intermediate format according to the preset data structure.

4. The method for converting electronic invoices into multiple output formats according to claim 3, characterized in that: The step of organizing all processed core fields into a unified intermediate format according to a preset data structure specifically includes: Build a standardized data structure model based on the common fields and industry extension fields of electronic invoices; Importing the core fields of the standardized invoice into the data structure model according to preset mapping rules; Before the data structure model outputs results, the AI ​​anomaly detection mechanism is used to perform logical consistency checks on core fields to detect data anomalies in invoices; Combine the data structure model output results into structured data output in a specified format.

5. The method for converting electronic invoices into multiple output formats according to claim 1, characterized in that: The method further comprises: During the electronic invoice format conversion process, multi-dimensional operation log data is collected through the full-link log collection mechanism; Unify the operation log data and generate standardized log files; Storing the log file in a database; Identify the user role of the operation based on the log file and set the corresponding access control permissions.

6. An electronic invoice conversion system with multiple output formats, characterized in that: The system comprises: The invoice input module is used to obtain the original electronic invoice file, which is input from the user or an external system and supports multiple formats; Invoice parsing module, used to parse the original electronic invoice file to obtain structured data in a unified format, used to identify the information contained in the electronic invoice; A format conversion and filling module is used to select an output format according to requirements and retrieve the corresponding invoice template for data filling. The invoice template is stored in the template library. The output module is used to push the invoice file to the financial system and return it to the user after the final invoice file is generated.

7. The electronic invoice conversion system with multiple output formats according to claim 6, characterized in that: The invoice input module includes: An intelligent recognition unit, used to recognize and receive original electronic invoice files using intelligent recognition technology, and to obtain invoice information from different data sources; Format recognition unit, used to identify the format of the uploaded original electronic invoice file; An integrity check unit, used to perform integrity check on the original electronic invoice file based on predefined rules; The digital verification unit is used to check the invoice based on the digital signature in the invoice to verify the authenticity of the invoice.

8. The electronic invoice conversion system with multiple output formats according to claim 6 is characterized in that: The invoice parsing module includes: The identification and response unit is used to identify the format of the original electronic invoice file and call the corresponding parsing tool for parsing and processing; A content extraction unit, which is used to identify and extract core fields from the content of the invoice by combining natural language processing and rule matching technology; The data processing unit is used to perform unified naming, unit conversion and format normalization on the extracted core fields; The data organization unit is used to organize all processed core fields into a unified intermediate format according to the preset data structure.

Images