Dynamic arrangement type invoicing method and invoicing system

Abstract

The invention relates to the technical field of software development, and provides a dynamic arrangement type invoicing method and system, and the method comprises the steps: building a code-level atomic component library; packaging a corresponding flow node component for each atomic component in the flow editor, and providing a drag-and-drop atomic component arrangement flow interface; the atomic component arrangement process precondition verification is realized; generating a self-defined DSL of an atomic component arrangement process; the invoicing process executor is responsible for analyzing the DSL and calling and executing the atomic component according to an arrangement process; a local invoicing tagging interface and function are realized, an invoicing process executor is called, and an invoicing transaction is closed. The invention provides an invoicing mode which supports online editing and is based on capability arrangement, rearrangement of the invoicing transaction process can be dynamically realized only by adjusting the arrangement process of the atomic component online by utilizing the draggable process editing interface, and diversified configuration requirements of the invoicing transaction process are effectively met.

Description

Technical Field

[0001] The present invention relates to the technical field of software development, and particularly relates to a dynamic orchestration-based invoicing method and an invoicing system. Background Art

[0002] The replacement of tax control invoices with digital electronic invoices is an inevitable trend in the digitalization of tax collection and management. Different from tax control invoices that rely on enterprises to purchase local tax control devices for invoice issuance, digital electronic invoices are issued and encoded in the enterprise's local digital electronic system, and then the invoice data is uploaded to the tax bureau through the national unified tax system (Lucky Enterprise Service Platform), and then the tax system is called to obtain the upload result of the invoice.

[0003] Currently, digital electronic invoice products generally use a prescribed process for invoicing. However, during the promotion and application process, there are diverse requirements for the timing of delivering invoices to customers and the timing of feedback on invoicing requests from front-end business systems. For example, some customers need to push invoice data after invoicing is completed, while some customers do not need to push; and in order to cope with the business interruption caused by the instability of the tax system and the inability to issue invoices online normally, there is a need to quickly switch to the offline invoicing mode.

[0004] The existing mode is either to make customized modifications for a single project and cannot achieve dynamic adjustment without service interruption, or is based on a large number of built-in rule judgments, with a complex code structure and logic, and cannot effectively meet the diverse configuration requirements in the invoicing transaction process. Summary of the Invention

[0005] To solve the above technical problems, the present invention proposes a dynamic orchestration-based invoicing method.

[0006] The present invention also proposes a dynamic orchestration-based invoicing system.

[0007] The technical solution adopted by the present invention is as follows: An embodiment of the present invention provides a dynamic orchestration-based invoicing method, which includes the following steps: establishing a code-level atomic component library and setting up a request-level data context to store and manage the shared data used in a single invoicing request. Among them, the atomic component library includes: a plurality of atomic components that constitute the invoicing process; integrating an open-source process editor, in the toolbox of the process editor, encapsulating corresponding process node components for each atomic component and providing a drag-and-drop atomic component orchestration process interface; presetting verification rules to implement precondition verification for the atomic component orchestration process; integrating the LiteFlow (a rule engine framework) open-source rule engine to generate an orchestration process DSL (Dynamic Script Language), and saving the custom DSL of the atomic component orchestration process that passes the verification; based on the LiteFlow open-source rule engine, implementing an invoicing process executor, parsing the DSL through the invoicing process executor, and calling and executing the atomic components according to the orchestration process; implementing a local invoicing code assignment interface and function, and calling the invoicing process executor after receiving an invoicing request to close the invoicing transaction.

[0008] The invoicing method proposed above by the present invention may also have the following additional technical features: According to an embodiment of the present invention, the atomic component library includes: an invoice upload component, which is used to upload the invoice data of local invoicing code assignment in the data context to the tax system by calling the invoice upload interface of the tax system, and write the upload serial number feedback 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 (Open Fixed-layout Document, a layout document format) / PDF (Portable Document Format) / XML (Extensible Markup Language) three-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 specified file server or imaging platform; an invoice delivery push component, which is used to push the invoice file to the user; an invoicing result feedback component, which is used to feedback the invoicing result and invoice data to the corresponding business system.

[0009] According to an embodiment of the present invention, after receiving a billing request, the billing process executor is called to close the billing transaction, which specifically includes: after receiving the billing request, calling the local billing code assignment public method to perform local billing code assignment; after the local billing code assignment is completed, writing the invoice number and invoice face element data into the data context, and at the same time triggering the billing process executor to parse and arrange the process DSL, and calling and executing the atomic components according to the arranged process.

[0010] According to an embodiment of the present invention, calling the local billing code assignment public method to perform local billing code assignment specifically includes: completing the assembly of the specified formatted invoice data and allocating an unused invoice number for this invoice from the pre-downloaded pre-code segments.

[0011] An embodiment of the present invention also proposes a billing system, including: an atomic component library, the atomic component library includes: a plurality of atomic components, and the atomic components constitute a billing process; a request-level data context, the data context is used to store and manage the shared data used in a single billing request; a process editor, the process editor is an open-source process editor, which is used to encapsulate corresponding process node components for each atomic component and provide a drag-and-drop atomic component arrangement process interface; a preset verification rule to implement the precondition verification of the atomic component arrangement process; integrating the LiteFlow open-source rule engine to generate the arranged process DSL and save the custom DSL of the verified atomic component arrangement process; a billing process executor, the billing 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 arranged process; a billing service interface, the billing service interface is used to implement the local billing code assignment interface and function, and call the billing process executor after receiving the billing request to close the billing transaction.

[0012] The above-mentioned billing system of the present invention also has the following additional technical features: According to an embodiment of the present invention, the atomic component library includes: an invoice upload component, which is used to upload the invoice data of the local billing code assignment in the data context to the tax system by calling the invoice upload interface of the tax system, and write the upload serial number feedback 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 three formats of files for various types of digital electronic invoice layouts; a layout file archiving component, which is used to upload the generated invoice layout files to the specified file server or imaging platform; an invoice delivery push component, which is used to push the invoice files to the user; a billing result feedback component, which is used to feedback the billing result and invoice data to the corresponding business system.

[0013] According to an embodiment of the present invention, the invoicing service interface is specifically used for: after receiving the invoicing request, calling the local invoicing code assignment public method to perform local invoicing code assignment; after the local invoicing code assignment is completed, writing the invoice number and invoice face element data into the data context, and at the same time triggering the invoicing process executor to parse and orchestrate the process DSL, and calling and executing the atomic components according to the orchestration process.

[0014] According to an embodiment of the present invention, the invoicing service interface is further used for: completing the assembly of the specified formatted invoice data and allocating an unused invoice number from the pre-downloaded pre-coded segments to this invoice.

[0015] Advantages of the present invention: 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 drag-and-drop process editing interface, only by adjusting the orchestration process of the atomic components online, the re-orchestration of the invoicing transaction process can be dynamically realized. It can be flexibly configured and adjusted according to the specific needs and business scenarios of the enterprise, improving the adaptability and scalability of the system, effectively coping with the diverse configuration requirements of the invoicing transaction process, while decoupling the complex and lengthy invoicing transaction code logic, simplifying the code logic complexity, and also saving the R & D cost of the project's secondary development. It is an efficient, flexible and effective invoicing implementation solution. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 is a flowchart of a dynamic orchestration-based invoicing method according to an embodiment of the present invention Figure 2 is a schematic structural diagram of a dynamic orchestration-based invoicing system according to an embodiment of the present invention; Figure 3 is a schematic diagram of a verification rule according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0017] The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

[0018] Figure 1 is a flowchart of a dynamic orchestration-based invoicing method according to an embodiment of the present invention, as Figure 1 shown, the method includes the following steps: S1. Establish a code-level atomic component library and set up a request-level data context to store and manage the shared data used in a single invoicing request. Among them, the atomic component library includes: multiple atomic components, and the atomic components constitute the invoicing process.

[0019] In one embodiment of the present invention, as Figure 2 shown, the atomic component library includes: an invoice upload component, which is used to upload the invoice data with local invoicing code assignment 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 three-format files of various types of digital invoice layouts; a layout file archiving component, which is used to upload the generated invoice layout files to a specified file server or imaging platform; an invoice delivery push component, which is used to push the invoice files to users; an invoicing result feedback component, which is used to feedback the invoicing result and invoice data to the corresponding business system.

[0020] The tax system is a dedicated system officially provided for enterprises to connect and provide invoicing and ticket-using capabilities.

[0021] Specifically, set up a request-level data context (such as using a global cache) to store and manage the shared data used in a single invoicing request, avoid complex data parameter passing between atomic components, and reduce the implementation complexity; and avoid repeatedly reading the database to improve performance efficiency. After local invoicing code assignment, write the invoice data into the data context. The atomic component library is a fine-grained decoupling and encapsulation of long invoicing transactions, 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 call complexity of atomic components and also improves the flexibility of component use. It should be noted that to simplify the code implementation complexity, all atomic components are implemented in the same standard interface, and the method does not need to provide input and output parameters, and realizes data transfer in the process by reading / writing the data context.

[0022] S2. Integrate an open-source process editor. In the toolbox of the process editor, encapsulate corresponding process node components for each atomic component and provide a drag-and-drop atomic component orchestration process interface.

[0023] Specifically, an open source front-end process editor that supports drag-and-drop operations is introduced to achieve visual atomic component orchestration. In the toolbox of the process editor, a corresponding process node component is designed for each atomic component, and the Java class of the corresponding code atomic component is set for each process node component. The drag-and-drop and node connection methods are supported to edit the orchestration process of the atomic component. Users can drag the atomic component to the set area to edit the orchestration process of the atomic component according to their needs to meet the diverse invoicing needs.

[0024] S3, preset verification rules to implement pre-condition verification of atomic component orchestration process.

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

[0026] S4 integrates the LiteFlow open source rule engine, generates the orchestration process DSL, and saves the custom DSL of the atomic component orchestration process that has passed the verification.

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

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

[0029] Specifically, create a Java class for the invoicing process executor and read the custom DSL of the atomic component orchestration process generated by S4 from the database. Parse the DSL and call the atomic components in the abstract code-level atomic component library in step S1 in sequence according to the process orchestration. It should be noted that the parsing and execution of the DSL can be directly handled by the LiteFlow open source rule engine.

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

[0031] 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.

[0032] Therefore, the invoicing process of long transactions is finely grained and split into independent code-level atomic components with single responsibilities; a visual process editing component is introduced to implement an atomic component choreography process editor, and a process node component is designed for each code atomic component, supporting the editing of the atomic component choreography process in a way of dragging and connecting nodes; built-in precondition constraint verification rules for atomic component choreography are used to ensure the reasonableness and effectiveness of process choreography; a specific DSL description language is generated according to the graphical process choreography; an invoicing process executor is implemented to parse the process DSL and call the code atomic components according to the process choreography. Finally, in the project using this invention, only the choreography process of atomic components needs to be adjusted online to dynamically re-choreograph the invoicing transaction process, meeting diverse invoicing requirements, including the switching of online / offline invoicing modes.

[0033] In an embodiment of the present invention, after receiving an 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 code assignment public method to perform local invoicing code assignment; after the local invoicing code assignment is completed, writing the invoice number and invoice face element data into the data context, and at the same time triggering the invoicing process executor to parse the choreography process DSL and call and execute the atomic components according to the choreography process.

[0034] Further, in an implementation of the present invention, calling the local invoicing code assignment public method to perform local invoicing code assignment specifically includes: completing the assembly of the specified formatted invoice data and allocating an unused invoice number to this invoice from the pre-downloaded pre-code segments.

[0035] Specifically, after receiving the invoicing request, first call the local invoicing code assignment public method to complete the assembly of the formatted invoice data required by the tax bureau and allocate an unused invoice number to this invoice from the pre-downloaded pre-code segments, supporting online invoicing, offline invoicing, and local invoicing code assignment. After the local invoicing code assignment is completed, write the invoice number and invoice face element data into the data context, and at the same time trigger the invoicing process executor to parse and execute the choreography process DSL. The choreography process DSL is formed by the user selecting and arranging atomic components in a simple operation mode of dragging on the visual choreography process editor to form a complete business logic process. When saving the process, it is necessary to verify the strong constraint relationships of some atomic components in the invoicing transaction process. After passing the verification, generate the DSL in the set standard format, and then call the invoicing process executor to parse the DSL and call and execute the atomic components according to the choreography process to close the invoicing transaction.

[0036] In summary, the dynamic orchestration-based invoicing method according to the embodiments of the present invention provides an online-editable invoicing method based on capability orchestration. By abstracting atomic components to disassemble the invoicing transaction process and using a drag-and-drop process editing interface, the re-orchestration of the invoicing transaction process can be dynamically achieved by simply adjusting the orchestration process of the atomic components online. It can flexibly configure and adjust the invoicing transaction process according to the specific needs and business scenarios of enterprises, improve the adaptability and scalability of the system, effectively respond to the diverse configuration requirements of the invoicing transaction process, decouple the complex and lengthy invoicing transaction code logic, simplify the code logic complexity, and save the R & D cost of secondary development of the project. It is an efficient, flexible and effective invoicing implementation solution.

[0037] Corresponding to the above dynamic orchestration-based invoicing method, the present invention also proposes a dynamic orchestration-based invoicing system. Since the system embodiments of the present invention correspond to the above method embodiments, for the details not disclosed in the system embodiments, reference can be made to the above method embodiments, and they will not be elaborated herein.

[0038] Figure 2 It is a schematic structural diagram of a dynamic orchestration-based invoicing system according to an embodiment of the present invention, as Figure 2 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.

[0039] Among them, the atomic component library includes: a plurality of atomic components, and the atomic components 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 corresponding process node components for each atomic component and provide a drag-and-drop atomic component orchestration process interface; preset verification rules are implemented to verify the preconditions 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 passes 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 code assignment interface and function, and call the invoicing process executor after receiving the invoicing request to close the invoicing transaction.

[0040] In an embodiment of the present invention, the atomic component library includes: an invoice upload component, which is used to upload the invoice data with local invoicing and code assignment 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 files to a specified file server or imaging platform; an invoice delivery and push component, which is used to push the invoice files to users; an invoicing result feedback component, which is used to feedback the invoicing result and invoice data to the corresponding business system.

[0041] According to an embodiment of the present invention, the invoicing service interface is specifically used for: after receiving an invoicing request, calling the local invoicing and code assignment public method to perform local invoicing and code assignment; after the local invoicing and code assignment is completed, writing the invoice number and ticket face element data into the data context, and at the same time triggering the invoicing process executor to parse and arrange the process DSL, and calling and executing atomic components according to the arranged process.

[0042] The invoicing service interface is further used for: completing the assembly of the specified formatted invoice data and allocating an unused invoice number from the pre-downloaded pre-assigned code segments to this invoice.

[0043] 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 drag-and-drop process editing interface, only by online adjusting the arrangement process of atomic components, the re-arrangement of the invoicing transaction process can be dynamically realized. It can flexibly configure and adjust the invoicing transaction process according to the specific needs and business scenarios of the enterprise, improve the adaptability and scalability of the system, effectively respond to the diverse configuration requirements of the invoicing transaction process, and at the same time decouple the complex and lengthy invoicing transaction code logic, simplify the code logic complexity, and also save the R & D cost of secondary development of the project. It is an efficient, flexible and effective invoicing implementation solution.

[0044] In the description of this specification, the descriptions referring to terms such as "one embodiment", "some embodiments", "examples", "specific examples", or "some examples", etc. mean that the specific features, structures, materials, or characteristics described in connection 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 may be combined in any one or more embodiments or examples in a suitable manner. In addition, without contradiction, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of different embodiments or examples.

[0045] In addition, the terms "first" and "second" are used for descriptive purposes only and cannot be construed as indicating or implying relative importance or implicitly specifying the quantity of the indicated technical features. Thus, the features defined with "first" and "second" may explicitly or implicitly include at least one of such features. In the description of the present invention, "a plurality of" means at least two, such as two, three, etc., unless otherwise specifically defined.

[0046] Any process or method description depicted in a flowchart or otherwise described herein may be understood to represent a module, segment, or portion of code including one or more executable instructions for implementing a customized logic function or process, and the scope of the preferred embodiments of the present invention includes additional implementations, where the functions may be executed in a substantially simultaneous manner or in an order opposite to that shown or discussed, according to the functions involved, which should be understood by those skilled in the art to which the embodiments of the present invention pertain.

[0047] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a definable list of executable instructions for implementing logical functions, and can be specifically implemented in any computer-readable medium for use by an instruction execution system, apparatus, or device (such as a computer-based system, a system including a processor, or other systems that can fetch and execute instructions from the instruction execution system, apparatus, or device), or used in conjunction with these instruction execution systems, apparatus, or devices. For the purposes of this specification, a "computer-readable medium" can be 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 (non-exhaustive list) of computer-readable media include the following: an electrical connection portion with one or more wirings (electronic device), a portable computer diskette (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). Additionally, the computer-readable medium can even be paper or other suitable media on which the program can be printed, as the program can be obtained electronically, for example, by optically scanning the paper or other media, followed by editing, interpretation, or otherwise processing as appropriate, and then storing it in a computer memory.

[0048] It should be understood that various parts of the present invention can be implemented by hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or a combination of the following techniques well known in the art can be used: discrete logic circuits having logic gate circuits for implementing logical functions on data signals, application specific integrated circuits having appropriate combinational logic gate circuits, programmable gate arrays (PGA), field programmable gate arrays (FPGA), etc.

[0049] Those of ordinary skill in the art of this technology can understand that all or part of the steps carried by the methods of the above embodiments can be completed by instructing relevant 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 embodiments.

[0050] In addition, in each embodiment of the present invention, each functional unit may be integrated into a processing module, may exist separately physically for each unit, or two or more units may be integrated into one module. The above-mentioned integrated module may be implemented in the form of hardware or in the form of a software functional module. When the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it may also be stored in a computer-readable storage medium.

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

Claims

1. A dynamic orchestration-based invoicing method, characterized in that, Including the following steps; Establish a code-level atomic component library and set up a request-level data context to store and manage the shared data used in a single invoicing request. Among them, the atomic component library includes: multiple atomic components that constitute the invoicing process; Integrate an open-source process editor. In the toolbox of the process editor, encapsulate corresponding process node components for each atomic component and provide a drag-and-drop atomic component orchestration process interface; Preset verification rules to implement precondition verification for the atomic component orchestration process; Integrate the LiteFlow open-source rule engine to generate an orchestration process DSL and save the custom DSL of the atomic component orchestration process that passes the verification; Based on the LiteFlow open-source rule engine, implement an invoicing process executor. Through the invoicing process executor, parse the DSL and call and execute the atomic components according to the orchestration process; Implement a local invoicing and code assignment interface and function. After receiving an invoicing request, call the invoicing process executor to close the invoicing transaction.

2. The dynamic orchestration-based invoicing method according to claim 1, wherein The atomic component library includes: An invoice upload component, which is used to upload the invoice data of local invoicing and code assignment in the data context to the tax system by calling the invoice upload interface of the tax system, and write the upload serial number feedback 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 three formats of files for various types of digital invoice layouts; A layout file archiving component, which is used to upload the generated invoice layout file to a specified file server or imaging platform; An invoice delivery and push component, which is used to push the invoice file to the user; An invoicing result feedback component, which is used to feedback the invoicing result and invoice data to the corresponding business system.

3. The dynamic orchestration-based invoicing method according to claim 1, characterized in that, After receiving an invoicing request, call the invoicing process executor to close the invoicing transaction, specifically including: After receiving the invoicing request, call the local invoicing and code assignment public method to perform local invoicing and code assignment; After the local invoicing and code assignment is completed, write the invoice number and invoice 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 components according to the orchestration process.

4. The dynamic orchestration-based invoicing method according to claim 3, wherein Calling the local invoicing and code assignment public method to perform local invoicing and code assignment, specifically including: Complete the assembly of the specified formatted invoice data and allocate an unused invoice number for this invoice from the pre-downloaded pre-code segments.

5. A dynamic orchestration-based invoicing system, characterized in that, Including: An atomic component library, which includes: multiple atomic components that constitute the invoicing process; A request-level data context, which is used to store and manage the shared data used in a single invoicing request; Process Editor, which is an open-source process editor used to encapsulate corresponding process node components for each atomic component and provide a drag-and-drop atomic component orchestration process interface; preset verification rules to implement precondition verification for the atomic component orchestration process; integrate the LiteFlow open-source rule engine to generate an orchestration process DSL and save the custom DSL of the verified atomic component orchestration process. Invoice Issuing Process Executor, which is used to parse the DSL based on the LiteFlow open-source rule engine and call and execute the atomic component according to the orchestration process. Invoice Issuing Service Interface, which is used to implement the local invoice issuing and code assignment interface and functions, and call the invoice issuing process executor after receiving an invoice issuing request to close the invoice issuing transaction.

6. The dynamic orchestration-based invoicing system according to claim 5, wherein The atomic component library includes: Invoice Upload Component, which is used to upload the invoice data of local invoice issuing and code assignment in the data context to the tax system by calling the invoice upload interface of the tax system, and write the upload serial number feedback by the upload interface into the data context. 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 to obtain the invoice upload status and write it into the data context. Layout File Generation Component, which is used to provide the generation of OFD / PDF / XML format files of various types of digital invoice layouts. Layout File Archiving Component, which is used to upload the generated invoice layout file to a specified file server or imaging platform. Invoice Delivery and Push Component, which is used to push the invoice file to the user. Invoice Issuing Result Feedback Component, which is used to feedback the invoice issuing result and invoice data to the corresponding business system.

7. The dynamic choreography-based invoicing system according to claim 5, wherein, The invoice issuing service interface is specifically used for: After receiving the invoice issuing request, call the local invoice issuing and code assignment public method to perform local invoice issuing and code assignment. After local invoice issuing and code assignment is completed, write the invoice number and invoice face element data into the data context, and at the same time trigger the invoice issuing process executor to parse the orchestration process DSL and call and execute the atomic component according to the orchestration process.

8. The dynamic orchestration-based invoicing system according to claim 7, characterized in that, The invoice issuing service interface is further used for: Complete the assembly of the specified formatted invoice data and allocate an unused invoice number from the pre-downloaded pre-assigned code segment to this invoice.

Images