A dynamic arrangement invoicing method and invoicing system

Abstract

The present invention relates to the field of software development technology, and provides a dynamically orchestrated invoicing method and invoicing system, the method comprising: establishing a code-level atomic component library; encapsulating a corresponding process node component for each atomic component in a process editor, and providing a drag-and-drop atomic component orchestration process interface; implementing atomic component orchestration process precondition verification; generating a custom DSL for the atomic component orchestration process; implementing an invoicing process executor, which is responsible for parsing the DSL and calling and executing the atomic component according to the orchestration process; implementing a local invoicing coding interface and function, calling the invoicing process executor, and closing the invoicing transaction. The present invention provides a capability-based orchestration invoicing method that supports online editing. By utilizing a draggable process editing interface, the invoicing transaction process can be dynamically rearranged by simply adjusting the orchestration process of the atomic component online, effectively responding to the diversified configuration requirements of the invoicing transaction process.

Description

Technical Field

[0001] The present invention relates to the technical field of software development, and in particular to a dynamically arranged invoicing method and invoicing system. Background Art

[0002] The replacement of tax-controlled invoices with digital invoices is an inevitable trend in the digitalization of tax collection and management. Unlike tax-controlled invoices which rely on enterprises to purchase local tax-controlled equipment to issue invoices, digital invoices are issued after the enterprise's local digital system completes the invoice issuance and coding process, and then uploads the invoice data to the tax bureau through the national unified tax system (Leqi Service Platform), and then calls the tax system to obtain the uploaded invoice results.

[0003] Currently, digital invoicing products generally use a defined process for invoicing. However, during their rollout, they encountered diverse requirements regarding the timing of invoice delivery to customers and the timing of responses to invoicing requests from front-end business systems. For example, some customers require invoice data to be pushed after invoicing is complete, while others do not. Furthermore, to address business interruptions caused by instability in the tax system and the inability to issue invoices online, a rapid switch to offline invoicing is required.

[0004] The existing models are either customized for a single project and cannot be adjusted dynamically without service interruption, or they are based on a large number of built-in rules, with complex code structure and logic, and cannot effectively respond to the diverse configuration requirements of the invoicing process. Summary of the Invention

[0005] In order to solve the above technical problems, the present invention proposes a dynamic arrangement type invoicing method.

[0006] The present invention also proposes a dynamic arrangement type invoicing system.

[0007] The technical solution adopted in the present invention is as follows:

[0008] An embodiment of the present invention proposes a dynamically orchestrated invoicing method, comprising the following steps: establishing a code-level atomic component library, and setting a request-level data context to store and manage shared data used in a single invoicing request, wherein the atomic component library comprises: multiple atomic components, which constitute an invoicing process; integrating an open source process editor, encapsulating a corresponding process node component for each atomic component in the toolbox of the process editor, and providing a drag-and-drop atomic component orchestration process interface; presetting verification rules to implement atomic component orchestration process precondition verification; integrating LiteFlow (a rule engine framework) open source rule engine to generate an orchestration process DSL (Dynamic Script Language), and saving a custom DSL of the atomic component orchestration process that has passed the verification; implementing an invoicing process executor based on the LiteFlow open source rule engine, parsing the DSL through the invoicing process executor, and calling and executing the atomic component according to the orchestration process; implementing a local invoicing coding interface and function, calling the invoicing process executor after receiving the invoicing request, and closing the invoicing transaction.

[0009] The invoicing method proposed above may also have the following additional technical features:

[0010] According to one embodiment of the present invention, the atomic component library includes: an invoice upload component, which is used to upload the invoice data with local invoice coding in the data context to the tax system by calling the invoice upload interface of the tax system, and write the upload serial number fed back by the upload interface into the data context; an upload result acquisition component, which is responsible for reading the upload serial number from the data context, calling the invoice upload result acquisition interface of the tax system, obtaining the invoice upload status and writing it into the data context; a layout file generation component, which is used to provide the generation of three formats of OFD (Open Fixed-layout Document, a layout document format) / PDF (Portable Document Format, portable file format) / XML (Extensible Markup Language, extensible markup language) for various types of digital invoice layouts; a layout file archiving component, which is used to upload the generated invoice layout file to a designated file server or imaging platform; an invoice delivery push component, which is used to push the invoice file to the user; and an invoice result feedback component, which is used to feed back the invoice results and invoice data to the corresponding business system.

[0011] According to one embodiment of the present invention, after receiving the invoicing request, the invoicing process executor is called to close the invoicing transaction, which specifically includes: after receiving the invoicing request, calling the local invoicing coding public method to perform local invoicing coding; after the local invoicing coding is completed, the invoice number and the face element data are written into the data context, and at the same time, the invoicing process executor is triggered to parse the orchestration process DSL and execute the atomic component according to the orchestration process call.

[0012] According to one embodiment of the present invention, a local invoice coding public method is called to perform local invoice coding, specifically including: completing the assembly of the specified formatted invoice data and assigning an unused invoice number to the invoice from the pre-downloaded pre-coded segment.

[0013] An embodiment of the present invention also proposes an invoicing system, including: an atomic component library, the atomic component library including: multiple atomic components, the atomic components constituting the invoicing process; a request-level data context, the data context being used to store and manage shared data used in a single invoicing request; a process editor, the process editor being an open source process editor, being used to encapsulate the corresponding process node component for each atomic component, and providing a drag-and-drop atomic component orchestration process interface; preset verification rules, implementing atomic component orchestration process precondition verification; integrating the LiteFlow open source rule engine, generating an orchestration process DSL, and saving the custom DSL of the atomic component orchestration process that has passed the verification; an invoicing process executor, the invoicing process executor being used to parse the DSL based on the LiteFlow open source rule engine, and executing the atomic component according to the orchestration process call; an invoicing service interface, the invoicing service interface being used to implement the local invoicing coding interface and function, and calling the invoicing process executor after receiving the invoicing request to close the invoicing transaction.

[0014] The invoicing system of the present invention also has the following additional technical features:

[0015] According to one embodiment of the present invention, the atomic component library includes: an invoice upload component, which is used to upload the invoice data with local invoice coding in the data context to the tax system by calling the invoice upload interface of the tax system, and write the upload serial number fed back by the upload interface into the data context; an upload result acquisition component, which is responsible for reading the upload serial number from the data context, calling the invoice upload result acquisition interface of the tax system, obtaining the invoice upload status and writing it into the data context; a layout file generation component, which is used to provide the generation of OFD / PDF / XML format files of various types of digital invoice layouts; a layout file archiving component, which is used to upload the generated invoice layout file to a designated file server or image platform; an invoice delivery push component, which is used to push the invoice file to the user; and an invoice result feedback component, which is used to feed back the invoice results and invoice data to the corresponding business system.

[0016] According to one embodiment of the present invention, the invoicing service interface is specifically used to: after receiving the invoicing request, call the local invoicing coding public method to perform local invoicing coding; after the local invoicing coding is completed, write the invoice number and the face element data into the data context, and at the same time trigger the invoicing process executor to parse the orchestration process DSL and execute the atomic component according to the orchestration process call.

[0017] According to one embodiment of the present invention, the invoicing service interface is further configured to: complete the assembly of the specified formatted invoice data and assign an unused invoice number to the invoice from the pre-downloaded pre-coded segment.

[0018] Beneficial effects of the present invention:

[0019] The present invention provides an invoicing method based on capability orchestration that supports online editing. By abstracting atomic components to disassemble the invoicing transaction process, and using a draggable process editing interface, the invoicing transaction process can be dynamically re-arranged by simply adjusting the orchestration process of the atomic components online. The invoicing transaction process can be flexibly configured and adjusted according to the specific needs and business scenarios of the enterprise, thereby improving the adaptability and scalability of the system and effectively responding to the diversified configuration requirements of the invoicing transaction process. At the same time, it decouples the complex and lengthy invoicing transaction code logic, simplifies the code logic complexity, and saves the R&D cost of the second project. It is an efficient, flexible and effective invoicing implementation solution. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 This is a flow chart of a dynamic invoicing method according to an embodiment of the present invention.

[0021] Figure 2 This is a schematic diagram of the structure of a dynamic scheduling invoicing system according to one embodiment of the present invention;

[0022] Figure 3 FIG. 4 is a schematic diagram of verification rules according to an embodiment of the present invention. DETAILED DESCRIPTION

[0023] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments of the present invention without making any creative efforts shall fall within the scope of protection of the present invention.

[0024] Figure 1 is a flow chart of a dynamic scheduling invoicing method according to an embodiment of the present invention. Figure 1As shown, the method includes the following steps:

[0025] S1. Establish a code-level atomic component library and set a request-level data context to store and manage shared data used in a single invoicing request. The atomic component library includes: multiple atomic components, and the atomic components constitute the invoicing process.

[0026] In one embodiment of the present invention, Figure 2 As shown, the atomic component library includes: an invoice upload component, which is used to upload the invoice data with local invoice coding in the data context to the tax system by calling the invoice upload interface of the tax system, and write the upload serial number fed back by the upload interface into the data context; an upload result acquisition component, which is responsible for reading the upload serial number from the data context, calling the invoice upload result acquisition interface of the tax system invoice, obtaining the invoice upload status and writing it into the data context; a layout file generation component, which is used to provide the generation of OFD / PDF / XML formats of various types of digital invoice layouts; a layout file archiving component, which is used to upload the generated invoice layout file to the designated file server or image platform; an invoice delivery push component, which is used to push the invoice file to the user; and an invoice result feedback component, which is used to feed back the invoice result and invoice data to the corresponding business system.

[0027] The tax system is a dedicated system provided by the government to enterprises to provide the ability to issue and use invoices.

[0028] Specifically, a request-level data context is set (for example, using a global cache) to store and manage shared data used in a single invoicing request, avoiding complex data parameter transmission between atomic components and reducing implementation complexity; and avoiding repeated reading of the database to improve performance efficiency. After the local invoice is coded, the invoice data is written into the data context. The atomic component library is a refined decoupling encapsulation of the long invoicing transaction, abstracting six highly cohesive, relatively independent, and flexibly reusable code-level atomic components. The data interaction between atomic components is all passed through the data context, which simplifies the implementation and calling complexity of the atomic components and improves the flexibility of component use. It should be noted that in order to simplify the complexity of code implementation, all atomic components are implemented on the same standard interface, and the method does not need to provide input and output parameters. Data transmission in the process is achieved by reading / writing the data context.

[0029] S2 integrates an open source process editor. In the process editor's toolbox, each atomic component encapsulates the corresponding process node component and provides a drag-and-drop atomic component orchestration interface.

[0030] Specifically, an open-source front-end process editor with drag-and-drop support is introduced to enable visual orchestration of atomic components. Within the process editor's toolbox, a corresponding process node component is designed for each atomic component. Each process node component is assigned a Java class corresponding to the code atomic component. The process editor supports dragging and dropping, as well as connecting nodes, to edit the atomic component orchestration process. Users can drag and drop atomic components into the designated area to edit the atomic component orchestration process, meeting diverse invoicing needs.

[0031] S3, preset verification rules, implements pre-condition verification of atomic component orchestration process.

[0032] Implement a Java class for orchestration process verification, with built-in atomic component orchestration precondition constraint verification rules, for example Figure 3 As shown, the prerequisite for obtaining the upload results is uploading the invoice to the tax system. The common prerequisite for format file archiving and invoice delivery push is format file generation to ensure the logical correctness of the process arrangement.

[0033] S4 integrates the LiteFlow open source rule engine to generate an orchestration process DSL and save the custom DSL of the atomic component orchestration process that has passed verification.

[0034] Specifically, the LiteFlow open source rule engine is introduced to provide the function of generating LiteFlow-supported DSL according to the orchestration process.

[0035] S5, based on the LiteFlow open source rule engine, implements the invoicing process executor. The invoicing process executor parses the DSL and calls and executes atomic components according to the orchestration process.

[0036] Specifically, a Java class is created to execute the invoicing process. It reads the custom DSL for the atomic component orchestration process generated by S4 from the database. The DSL is parsed and, according to the process orchestration, the atomic components in the code-level atomic component library abstracted in step S1 are sequentially invoked. It should be noted that the parsing and execution of the DSL is directly handled by the LiteFlow open-source rule engine.

[0037] S6 implements the local invoicing coding interface and functions, calls the invoicing process executor after receiving the invoicing request, and closes the invoicing transaction.

[0038] Specifically, the local invoicing coding interface and function are implemented. After the invoice data is saved in the database, the invoice data is first written into the data context set in step S1, and then the invoicing process executor in step S5 is called to close the entire invoicing transaction.

[0039] Thus, the invoicing process of a long transaction is finely divided into independent, single-responsibility code-level atomic components; a visual process editing component is introduced to implement an atomic component orchestration process editor, and a process node component is designed for each code atomic component, supporting the editing of the atomic component orchestration process by dragging and connecting nodes; built-in atomic component orchestration precondition constraint verification rules are implemented to ensure the rationality and effectiveness of the process orchestration; based on the graphical process orchestration, a specific DSL description language is generated; an invoicing process executor is implemented to parse the process DSL and call the code atomic components according to the process orchestration. Ultimately, in projects using this invention, it is only necessary to adjust the atomic component orchestration process online to dynamically realize the rearrangement of the invoicing transaction process, meeting diverse invoicing needs, including online / offline invoicing mode switching.

[0040] In one embodiment of the present invention, after receiving the invoicing request, the invoicing process executor is called to close the invoicing transaction, which specifically includes: after receiving the invoicing request, calling the local invoicing coding public method to perform local invoicing coding; after the local invoicing coding is completed, the invoice number and the face element data are written into the data context, and at the same time, the invoicing process executor is triggered to parse the orchestration process DSL and call and execute the atomic component according to the orchestration process.

[0041] Furthermore, in one embodiment of the present invention, a local invoice coding public method is called to perform local invoice coding, specifically including: completing the assembly of the specified formatted invoice data and assigning an unused invoice number to the invoice from the pre-downloaded pre-coded segment.

[0042] Specifically, after receiving the invoicing request, the local invoice coding public method is called first to complete the assembly of the formatted invoice data required by the tax bureau and assign an unused invoice number to the invoice from the pre-downloaded pre-coded segment. It supports online invoicing, offline invoicing and local invoice coding. After the local invoice coding is completed, the invoice number and the face element data are written into the data context, and the invoice process executor is triggered to parse and execute the orchestration process DSL. The orchestration process DSL allows users to select and arrange atomic components through a simple drag-and-drop operation on the visual orchestration process editor to form a complete set of business logic processes. When saving the process, the strong binding relationship of some atomic components in the invoicing transaction process needs to be verified. After the verification is passed, the DSL is generated according to the set standard format, and then the invoice process executor is called to parse the DSL. The atomic components are executed according to the orchestration process call to close the invoicing transaction.

[0043] In summary, the dynamically orchestrated invoicing method according to the embodiment of the present invention provides an invoicing method based on capability orchestration that supports online editing. By abstracting atomic components to disassemble the invoicing transaction process, and using a draggable process editing interface, the invoicing transaction process can be dynamically re-orchestrated by simply adjusting the orchestration process of the atomic components online. The invoicing transaction process can be flexibly configured and adjusted according to the specific needs and business scenarios of the enterprise, thereby improving the adaptability and scalability of the system and effectively responding to the diversified configuration requirements of the invoicing transaction process. At the same time, it decouples the complex and lengthy invoicing transaction code logic, simplifies the complexity of the code logic, and saves the R&D cost of the second project. It is an efficient, flexible and effective invoicing implementation solution.

[0044] Corresponding to the above-mentioned dynamic scheduling invoicing method, the present invention also provides a dynamic scheduling invoicing system. Since the system embodiment of the present invention corresponds to the above-mentioned method embodiment, any details not disclosed in the system embodiment can be referred to the above-mentioned method embodiment and will not be further described in this invention.

[0045] Figure 2 FIG. 1 is a schematic diagram of a dynamic invoicing system according to an embodiment of the present invention. Figure 2 As shown, the invoicing system includes: an atomic component library, a request-level data context, a process editor, an invoicing process executor, and an invoicing service interface.

[0046] Among them, the atomic component library includes: multiple atomic components, which constitute the invoicing process; the data context is used to store and manage the shared data used in a single invoicing request; the process editor is an open source process editor, which is used to encapsulate the corresponding process node component for each atomic component, and provide a drag-and-drop atomic component orchestration process interface; preset verification rules are used to implement the pre-condition verification of the atomic component orchestration process; the LiteFlow open source rule engine is integrated to generate the orchestration process DSL, and save the custom DSL of the atomic component orchestration process that has passed the verification; the invoicing process executor is used to parse the DSL based on the LiteFlow open source rule engine, and call and execute the atomic components according to the orchestration process; the invoicing service interface is used to implement the local invoicing coding interface and function, and call the invoicing process executor after receiving the invoicing request to close the invoicing transaction.

[0047] In one embodiment of the present invention, the atomic component library includes: an invoice upload component, which is used to upload the invoice data with local invoice coding in the data context to the tax system by calling the invoice upload interface of the tax system, and write the upload serial number fed back by the upload interface into the data context; an upload result acquisition component, which is responsible for reading the upload serial number from the data context, calling the invoice upload result acquisition interface of the tax system, obtaining the invoice upload status and writing it into the data context; a layout file generation component, which is used to provide the generation of OFD / PDF / XML format files of various types of digital invoice layouts; a layout file archiving component, which is used to upload the generated invoice layout file to a designated file server or image platform; an invoice delivery push component, which is used to push the invoice file to the user; and an invoice result feedback component, which is used to feed back the invoice results and invoice data to the corresponding business system.

[0048] According to one embodiment of the present invention, the invoicing service interface is specifically used to: after receiving an invoicing request, call the local invoice coding public method to perform local invoice coding; after the local invoice coding is completed, write the invoice number and the face element data into the data context, and at the same time trigger the invoicing process executor to parse the orchestration process DSL and call and execute the atomic component according to the orchestration process.

[0049] The invoicing service interface is further used to: complete the assembly of the specified formatted invoice data and assign an unused invoice number to the invoice from the pre-downloaded pre-assigned code segment.

[0050] In summary, the invoicing system according to the embodiment of the present invention provides an invoicing method based on capability orchestration that supports online editing. By abstracting atomic components to disassemble the invoicing transaction process, and using a draggable process editing interface, the invoicing transaction process can be dynamically re-orchestrated by simply adjusting the orchestration process of the atomic components online. The invoicing transaction process can be flexibly configured and adjusted according to the specific needs and business scenarios of the enterprise, thereby improving the adaptability and scalability of the system and effectively responding to the diversified configuration requirements of the invoicing transaction process. At the same time, it decouples the complex and lengthy invoicing transaction code logic, simplifies the complexity of the code logic, and saves the R&D cost of the second project. It is an efficient, flexible and effective invoicing implementation solution.

[0051] In the description of this specification, the reference terms "one embodiment," "some embodiments," "example," "specific example," or "some examples" mean that the specific features, structures, materials, or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described can be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art can combine and combine different embodiments or examples described in this specification and features of different embodiments or examples without contradiction.

[0052] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of the technical features being referred to. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In the description of the present invention, "plurality" means at least two, such as two, three, etc., unless otherwise specifically defined.

[0053] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, segment or portion of code comprising one or more executable instructions for implementing the steps of a custom logical function or process, and the scope of the preferred embodiments of the present invention includes alternative implementations in which functions may be performed out of the order shown or discussed, including performing functions in a substantially simultaneous manner or in the reverse order depending on the functions involved, which should be understood by those skilled in the art to which the embodiments of the present invention pertain.

[0054] The logic and / or steps represented in a flowchart or otherwise described herein, for example, can be considered a sequenced list of executable instructions for implementing the logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (e.g., a computer-based system, a system including a processor, or other system that can fetch and execute instructions from an instruction execution system, apparatus, or device). For purposes of this specification, a "computer-readable medium" is any device that can contain, store, communicate, propagate, or transport a program for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (not exhaustive) of computer-readable media include: an electrical connection with one or more wires (electronic devices), a portable computer disk cartridge (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and programmable read-only memory (EPROM or flash memory), fiber optic devices, and a portable compact disc read-only memory (CDROM). Furthermore, the computer-readable medium may even be paper or other suitable medium on which the program is printed, since the program may be obtained electronically, for example, by optically scanning the paper or other medium and then editing, interpreting or processing it in another suitable manner if necessary, and then storing it in a computer memory.

[0055] It should be understood that various components of the present invention may be implemented using hardware, software, firmware, or a combination thereof. In the aforementioned embodiments, multiple steps or methods may be implemented using software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented using hardware, as in another embodiment, any of the following technologies known in the art, or a combination thereof, may be used: a discrete logic circuit having logic gates for implementing logic functions on data signals, an application-specific integrated circuit having suitable combinational logic gates, a programmable gate array (PGA), a field-programmable gate array (FPGA), etc.

[0056] Those skilled in the art will understand that all or part of the steps in the method of the above embodiment can be completed by instructing related hardware through a program, and the program can be stored in a computer-readable storage medium. When the program is executed, it includes one or a combination of the steps of the method embodiment.

[0057] In addition, the functional units in the various embodiments of the present invention may be integrated into a single processing module, or each unit may exist physically separately, or two or more units may be integrated into a single module. The aforementioned integrated modules may be implemented in the form of hardware or in the form of software functional modules. If the integrated modules are implemented in the form of software functional modules and sold or used as independent products, they may also be stored in a computer-readable storage medium.

[0058] The storage medium mentioned above may be a read-only memory, a magnetic disk, or an optical disk, etc. Although the embodiments of the present invention have been shown and described above, it is understood that the above embodiments are exemplary and are not to be construed as limiting the present invention. Persons skilled in the art may make changes, modifications, substitutions, and variations to the above embodiments within the scope of the present invention.

Claims

1. A dynamic arrangement invoicing method, characterized in that: The following steps are included: Establish a code-level atomic component library and set a request-level data context to store and manage shared data used in a single invoicing request, wherein the atomic component library includes: multiple atomic components, and the atomic components constitute an invoicing process; Integrate an open source process editor. In the toolbox of the process editor, each atomic component encapsulates the corresponding process node component and provides a drag-and-drop atomic component process orchestration interface. Preset verification rules to implement pre-condition verification of atomic component orchestration process; Integrate the LiteFlow open source rule engine to generate the orchestration process DSL and save the custom DSL of the atomic component orchestration process that has passed verification; Based on the LiteFlow open source rule engine, an invoicing process executor is implemented. The invoicing process executor parses the DSL and calls and executes the atomic components according to the orchestration process. Implement the local invoicing coding interface and functions, call the invoicing process executor after receiving the invoicing request, and close the invoicing transaction.

2. The dynamic arrangement invoicing method according to claim 1, characterized in that: The atomic component library includes: The invoice upload component is used to upload the invoice data with local invoice coding in the data context to the tax system by calling the invoice upload interface of the tax system, and write the upload serial number fed back by the upload interface into the data context; The upload result acquisition component is responsible for reading the upload serial number from the data context, calling the invoice upload result acquisition interface of the tax system invoice, obtaining the invoice upload status and writing it into the data context; The layout file generation component is used to generate OFD / PDF / XML files of various types of digital invoice layouts; The format file archiving component is used to upload the generated invoice format file to the designated file server or imaging platform; Invoice delivery push component, used to push invoice files to users; The invoicing result feedback component is used to feed back the invoicing results and invoice data to the corresponding business system.

3. The dynamic invoicing method according to claim 1, characterized in that: After receiving the invoicing request, the invoicing process executor is called to close the invoicing transaction, including: After receiving the invoicing request, the local invoicing coding public method is called to perform local invoicing coding; After the local invoicing coding is completed, the invoice number and the face element data are written into the data context, and at the same time, the invoicing process executor is triggered to parse the orchestration process DSL and execute the atomic component according to the orchestration process call.

4. The dynamic arrangement invoicing method according to claim 3, characterized in that: Call the local invoice coding public method to perform local invoice coding, including: Complete the assembly of the specified formatted invoice data and assign an unused invoice number to this invoice from the pre-downloaded pre-coded segments.

5. A dynamic invoicing system, characterized by: include: An atomic component library, the atomic component library including: a plurality of atomic components, the atomic components constituting an invoicing process; Request-level data context, which is used to store and manage shared data used in a single invoicing request; The process editor is an open source process editor that encapsulates the corresponding process node component for each atomic component and provides a drag-and-drop atomic component orchestration process interface. It presets verification rules to implement pre-condition verification of atomic component orchestration processes. It integrates the LiteFlow open source rule engine to generate orchestration process DSL and saves the custom DSL of atomic component orchestration processes that have passed verification. An invoicing process executor, which is used to parse the DSL based on the LiteFlow open source rule engine and call and execute the atomic components according to the orchestration process; The invoicing service interface is used to implement the local invoicing coding interface and functions. After receiving the invoicing request, the invoicing process executor is called to close the invoicing transaction.

6. The dynamic arrangement invoicing system according to claim 5, characterized in that: The atomic component library includes: The invoice upload component is used to upload the invoice data with local invoice coding in the data context to the tax system by calling the invoice upload interface of the tax system, and write the upload serial number fed back by the upload interface into the data context; The upload result acquisition component is responsible for reading the upload serial number from the data context, calling the invoice upload result acquisition interface of the tax system, obtaining the invoice upload status, and writing it into the data context; The layout file generation component is used to generate OFD / PDF / XML files of various types of digital invoice layouts; The format file archiving component is used to upload the generated invoice format file to the designated file server or imaging platform; Invoice delivery push component, used to push invoice files to users; The invoicing result feedback component is used to feed back the invoicing results and invoice data to the corresponding business system.

7. The dynamic arrangement invoicing system according to claim 5, characterized in that: The invoicing service interface is specifically used to: After receiving the invoicing request, the local invoicing coding public method is called to perform local invoicing coding; After the local invoicing coding is completed, the invoice number and the face element data are written into the data context, and at the same time, the invoicing process executor is triggered to parse the orchestration process DSL and execute the atomic component according to the orchestration process call.

8. The dynamic arrangement invoicing system according to claim 7, characterized in that: The invoicing service interface is further used to: Complete the assembly of the specified formatted invoice data and assign an unused invoice number to this invoice from the pre-downloaded pre-coded segments.

Images