Electronic invoice issuing method and device, equipment, medium and program product

Abstract

The invention provides an electronic invoice issuing method and device, equipment, a medium and a program product, and the method comprises the steps: displaying a main page on a user interface of an application program, and enabling the user interface to comprise an invoice issuing control; in response to a trigger operation on the invoicing control, invoking an invoicing component integrated at the micro front end in the application program, and switching a home page on the user interface into an invoicing page; responding to an editing operation on the invoicing page, and displaying corresponding invoicing information in an information bar of the invoicing page; and generating an electronic invoice in response to an invoicing operation triggered on the invoicing page. According to the method, seamless switching from the homepage to the invoicing page of the invoicing component on the user interface is realized in a micro-front-end integration mode.

Description

Technical Field

[0001] The embodiments of the present application relate to the technical field of electronic invoices, and in particular to an electronic invoice issuance method, apparatus, device, medium and program product. Background Art

[0002] Electronic invoices are a product of the information age. With the continuous improvement of informatization, the application of electronic invoices has become more extensive and in-depth, bringing more convenience and benefits to tax management and economic development.

[0003] In order to adapt to the ever-changing and growing invoicing needs of users, the invoicing software is integrated into the enterprise resource planning (ERP) system, customer relationship management (CRM) system, e-commerce platform and other internal and external enterprise systems, so as to achieve real-time data capture, automatic invoicing, real-time feedback on invoice status, etc. The integration of invoicing software in various systems introduces modular design, and through the division and optimization of the code level, it can realize the dynamic expansion of specific scripts and elements of the page to a certain extent.

[0004] However, traditional modular design cannot achieve seamless integration of invoicing software pages within the internal and external systems of various enterprises. Summary of the invention

[0005] In view of this, the embodiments of the present application provide an electronic invoice issuance method, apparatus, device, medium and program product to at least solve or alleviate the above-mentioned problems.

[0006] According to a first aspect of an embodiment of the present application, a method for issuing an electronic invoice is provided, the method comprising:

[0007] Displaying a main page on a user interface of the application, wherein the user interface includes an invoicing control;

[0008] In response to a trigger operation on the invoicing control, calling an invoicing component integrated in the micro front-end in the application, and switching the main page on the user interface to an invoicing page;

[0009] In response to an editing operation on the invoicing page, displaying corresponding invoicing information in an information column on the invoicing page;

[0010] In response to the invoicing operation triggered on the invoicing page, an electronic invoice is generated.

[0011] According to a second aspect of an embodiment of the present application, there is provided an electronic invoice issuing device, the device comprising:

[0012] A display module, used to display a main page on a user interface of the application, wherein the user interface includes an invoicing control;

[0013] A switching module, configured to respond to a trigger operation on the invoicing control, call the invoicing component integrated in the micro front-end in the application, and switch the main page on the user interface to the invoicing page;

[0014] An editing module, configured to respond to an editing operation on the invoicing page and display corresponding invoicing information in the information column of the invoicing page;

[0015] A generating module is used to generate an electronic invoice in response to an invoicing operation triggered on the invoicing page.

[0016] According to a third aspect of an embodiment of the present application, there is provided an electronic device, comprising: a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface communicate with each other via the communication bus; the memory is used to store at least one executable instruction, and the executable instruction enables the processor to execute the electronic invoice issuance method provided in the first aspect above.

[0017] According to a fourth aspect of an embodiment of the present application, a computer storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the electronic invoice issuance method described in the first aspect above is implemented.

[0018] According to a fifth aspect of an embodiment of the present application, a computer program product is provided. The computer program product includes computer instructions, and the computer instructions instruct a computer device to execute the electronic invoice issuance method as described in the first aspect above.

[0019] According to the electronic invoice billing scheme provided by the embodiment of the present application, a main page including billing controls is displayed on the user interface. If billing services are required, the invoicing component integrated using micro-frontend technology can be called through the trigger operation on the invoicing control to achieve seamless switching of the home page on the user interface to the billing page. Furthermore, the invoicing information is edited on the invoicing page, and finally, the electronic invoice is generated through the invoicing operation on the invoicing page. This method realizes dynamic integration and jumps between different pages by integrating the billing component with the micro-frontend. It can switch from the main page to the billing page without opening a new page tab, realizing seamless integration of the billing component within the application. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the embodiments of the present application. For ordinary technicians in this field, other drawings can also be obtained based on these drawings.

[0021] Figure 1 This is a flow chart of a method for issuing electronic invoices according to an embodiment of the present application;

[0022] Figure 2 is a flow chart of a method for issuing electronic invoices according to another embodiment of the present application;

[0023] Figure 3 is a process diagram of an integrated invoicing component of an embodiment of the present application;

[0024] Figure 4 It is a schematic diagram of an electronic invoice issuing device according to an embodiment of the present application;

[0025] Figure 5 It is a schematic diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0026] The present application is described below based on embodiments, but the present application is not limited to these embodiments. In the detailed description of the present application below, some specific details are described in detail. It is possible for a person skilled in the art to fully understand the present application without the description of these details. In order to avoid confusing the essence of the present application, known methods, processes, and flows are not described in detail. In addition, the drawings are not necessarily drawn to scale.

[0027] First, some nouns or terms that appear in the process of describing the embodiments of the present application are subject to the following explanations.

[0028] The invoicing component is a component that implements the functions of electronic invoice generation, printing and data management in the software. It can collect transaction data from the enterprise's internal enterprise resource planning (ERP) system, customer relationship management (CRM) system, e-commerce platform and other source systems, automatically generate electronic invoice formats that comply with regulations, and embed digital signatures to ensure legal validity.

[0029] The invoicing component provided in the embodiments of the present application can be integrated into various systems and applications, thereby supporting the invocation of various usage forms such as various applications (Application, APP), mini-programs, quick applications, Software-as-a-Service (SaaS), etc. In the following multiple embodiments, the application of the invoicing component in the application is used to illustrate the detailed implementation process of the invoicing method.

[0030] Please refer to Figure 1 , which is a flow chart of an electronic invoice issuance method provided by an exemplary embodiment of the present application. The invoice issuance method is applied in an electronic device, and the steps are as follows:

[0031] Step 110: Display the main page on the user interface of the application, which includes an invoicing control.

[0032] An application is installed and running on the electronic device. The application uses a micro-front end to integrate an invoicing component. The main page is displayed on the user interface of the application. When the main page is displayed, an invoicing control is also displayed on the user interface. The invoicing control is used to trigger the application to call the invoicing component.

[0033] The application may include, but is not limited to: life applications, instant messaging applications, financial applications, tax applications, etc.

[0034] Step 120, in response to the trigger operation on the invoicing control, call the invoicing component integrated in the micro front end in the application, and switch the main page on the user interface to the invoicing page.

[0035] The electronic device receives a trigger operation on the invoicing control, responds to the trigger operation, calls the invoicing component integrated in the micro front end of the application, requests the invoicing component for data of the invoicing page, and after the invoicing component returns the data of the invoicing page to the application, switches the main page on the user interface of the application to the invoicing page.

[0036] Optionally, in response to a trigger operation on the invoicing control, the electronic device requests data of the invoicing page from the invoicing component through a routing mechanism; and switches the main page on the user interface to the invoicing page according to the data of the invoicing page.

[0037] Optionally, the above routing mechanism is front-end routing or back-end routing. Exemplarily, front-end routing is usually implemented using JavaScript, without server-side participation. When a trigger event on the invoicing control is received, the event is captured by JavaScript, and the default page jump behavior is prevented, and then the content or components of the page are updated, which can give the user a feeling of page jump.

[0038] Step 130: In response to the editing operation on the invoicing page, the corresponding invoicing information is displayed in the information column of the invoicing page.

[0039] The invoicing page includes one or more (ie, two or more) information columns, which are used to fill in invoicing-related information, such as company name, contact information, tax information, and the like.

[0040] The electronic device responds to the editing operation on the invoicing page and displays the edited invoicing information in the information column of the invoicing page. The editing operation can be text input, such as text input through an external device or text input on a touch screen; or it can be a selection operation of multiple options.

[0041] Step 140: Generate an electronic invoice in response to the invoicing operation triggered on the invoicing page.

[0042] After completing the editing operation on the invoicing page, you can trigger the invoicing operation on the invoicing page to generate an electronic invoice through the invoicing component, and switch the invoicing page on the user interface to the electronic invoice display page.

[0043] Exemplarily, the invoicing component can provide a save function to store the electronic invoice. For example, after the invoicing component generates the electronic invoice, the electronic invoice is stored, and then after entering the invoicing page, a viewing control for the invoicing record is also displayed on the invoicing page. By triggering a viewing operation on the viewing control, the invoicing record is displayed, and the invoicing record corresponding to the above electronic invoice is found. Clicking the invoicing record will display the above electronic invoice.

[0044] Alternatively, the electronic invoice can be stored through the save function provided by the application. For example, after the invoicing component generates the electronic invoice, it feeds the electronic invoice back to the application, which stores the electronic invoice. Then, after entering the main page, a viewing control for the invoicing record is displayed on the main page. The invoicing record is displayed by triggering a viewing operation on the viewing control, and the invoicing record corresponding to the above electronic invoice is found. Clicking the invoicing record will display the above electronic invoice.

[0045] In summary, the electronic invoice issuance method provided in this embodiment displays a main page including an invoicing control on the user interface. If an invoicing service is required, the invoicing component integrated using the micro-frontend technology can be called through the trigger operation on the invoicing control to achieve seamless switching of the home page on the user interface to the invoicing page. Furthermore, the invoicing information is edited on the invoicing page, and finally, the electronic invoice is generated through the invoicing operation on the invoicing page. This method realizes dynamic integration and jump between different pages by integrating the invoicing component with the micro-frontend. It can switch from the main page to the invoicing page without opening a new page tab, realizing seamless integration of the invoicing component in the application.

[0046] In another possible implementation, the invoicing component has AI functions, including image recognition, voice recognition, text parsing, information extraction, channel switching, image processing, etc., and can automatically fill in the invoicing information in the information column of the invoicing page according to the relevant data uploaded by the user. Exemplarily, the above step 130 can be implemented as the following steps:

[0047] Step 132, in response to the upload operation on the invoicing page, upload relevant data.

[0048] The invoicing page includes an upload control for relevant data. The electronic device receives an upload operation on the upload control and uploads relevant data, which includes invoicing information.

[0049] Optionally, the relevant data includes at least one of the following: pictures; voice information; text information.

[0050] The invoicing component supports uploading and identifying images in multiple image formats, such as Bitmap (BMP) format, Joint Photographic Experts Group (JPEG) format, Portable Network Graphics (PNG) format, Tag Image File Format (TIFF), Graphics Interchange Format (GIF), etc. For example, the invoicing page includes an image upload control, which can be triggered to upload images.

[0051] The invoicing component supports voice recording and uploading. For example, the invoicing page includes a recording control. You can long press the recording control to record and upload real-time voice, or click the recording control to upload a voice file. The formats of voice files include but are not limited to: Waveform Audio File Format (WAV), Moving Picture Experts Group Audio Layer III (MP3), Advanced Audio Coding (AAC), Free Lossless Audio Codec (FLAC), Adaptive Multi-Rate audio codec (AMR), Microsoft Audio Format (WMA), etc.

[0052] The invoicing component also supports text input and upload. For example, the invoicing page includes an information bar, in which text can be typed; the invoicing page also includes a text upload control, which can trigger the text upload control to upload a text file. The formats of text files include but are not limited to: plain text (Text, TXT), document (Document, DOC), open XML Word document format (Document Word Open XML Format, DOCX), portable document format (Portable DocumentFormat, PDF), spreadsheet file format (Excel Open XML Spreadsheet, XLSX) and other formats, where XML is the abbreviation of Extensible Markup Language.

[0053] Step 134, in response to the automatic filling operation on the invoicing page, the automatic filling function of the invoicing component is called to extract the invoicing information from the relevant data.

[0054] In response to the automatic filling operation on the invoicing page, the electronic device calls the automatic filling function of the invoicing component, and first extracts the invoicing information from the relevant data through the AI ​​function of the invoicing component. Exemplarily, if the uploaded relevant data includes pictures, the picture recognition function of the invoicing component is called to identify the invoicing information from the pictures; if the uploaded relevant data includes text files, the text parsing function of the invoicing component is called to parse the invoicing information from the text; if the uploaded relevant data includes voice, the voice-to-text function of the invoicing component is first called to convert the voice into text, and then the invoicing information is extracted from the text through the information extraction function.

[0055] The invoicing component also has a translation function. If there is foreign language in the uploaded relevant data, the foreign language will be translated, and then information will be extracted from the translated text to obtain the invoicing information.

[0056] Step 136, the invoicing information is automatically filled into the corresponding information column of the invoicing page.

[0057] After extracting the invoicing information, the electronic device automatically fills in the corresponding information columns. For example, the extracted "XXX Company" is filled in the company name column; the number "********" is filled in the tax number column, etc.

[0058] To sum up, the electronic invoice issuance method provided in this embodiment can realize the intelligent and automatic extraction of invoicing information through the AI ​​functions such as voice recognition, image recognition, information extraction, and translation provided by the invoicing component, which greatly improves the accuracy and efficiency of information entry and reduces the time cost of users manually entering invoicing information.

[0059] In another possible implementation, the application itself has the function of issuing electronic invoices, and can independently call the AI ​​functions of the invoicing component, such as voice recognition, image recognition, information extraction, and translation, to automatically fill in the invoicing information. Figure 2 , which is a flow chart of an electronic invoice issuance method provided by another exemplary embodiment of the present application. The invoice issuance method is applied in an electronic device, and the steps are as follows:

[0060] Step 210: Display the main page on the user interface of the application.

[0061] An application is installed and running on the electronic device, and the application uses a micro front-end to integrate the AI ​​function of the invoicing component. The application may include but is not limited to: life applications, instant messaging applications, financial applications, tax applications, etc.

[0062] If the main page is a page for invoicing in the application, when the main page is displayed, the AI ​​control of the invoicing component can be deployed on the main page using micro-frontend technology, and the AI ​​control is used to trigger the application to call the AI ​​function of the invoicing component; the electronic device responds to the operation triggered on the AI ​​control and integrates the upload control and automatic filling function control for displaying relevant data on the main page. Alternatively, the upload control and automatic filling function control of relevant data are deployed on the main page using micro-frontend technology.

[0063] Step 220, in response to the upload operation on the main page, upload relevant data.

[0064] The electronic device responds to the upload operation triggered on the upload control and uploads the relevant data, wherein the relevant data includes the invoicing information. Optionally, the relevant data includes at least one of the following: pictures; voice information; text information.

[0065] The upload control supports uploading and identifying images in various image formats, such as BMP, JPEG, PNG, TIFF, GIF, etc. The upload control supports uploading text documents in various formats, such as TXT, DOC, DOCX, PDF, XLSX, etc. The upload control supports uploading audio files in various formats, such as WAV, MP3, AAC, FLAC, AMR, WMA, etc.

[0066] In addition, the main page also uses micro-frontend technology to deploy text editing controls for related data. If the related data is a text paragraph, the text paragraph can be directly copied into the text editing control. The invoicing component also uses micro-frontend technology to deploy a recording control, which can trigger voice recording and upload real-time voice.

[0067] Step 230, in response to the automatic filling operation triggered on the main page, the automatic filling function of the invoicing component is called to extract the invoicing information from the relevant data.

[0068] In response to the automatic filling operation on the automatic filling function control, the electronic device calls the automatic filling function of the invoicing component, and first extracts the invoicing information from the relevant data through the AI ​​function of the invoicing component. Exemplarily, if the uploaded relevant data includes pictures, the picture recognition function of the invoicing component is called to identify the invoicing information from the pictures; if the uploaded relevant data includes text files, the text parsing function of the invoicing component is called to parse the invoicing information from the text; if the uploaded relevant data includes voice, the voice-to-text function of the invoicing component is first called to convert the voice into text, and then the invoicing information is extracted from the text through the information extraction function.

[0069] The invoicing component also has a translation function. If there is foreign language in the uploaded relevant data, the foreign language will be translated, and then information will be extracted from the translated text to obtain the invoicing information.

[0070] Step 240, the invoicing information is automatically filled into the corresponding information column of the main page.

[0071] After extracting the invoicing information, the electronic device automatically fills in the corresponding information columns. For example, the extracted "XXX Company" is filled in the company name column; the number "********" is filled in the tax number column, etc.

[0072] Step 250, generating an electronic invoice in response to the invoicing operation triggered on the main page.

[0073] Exemplarily, a generation control is provided on the main page, and an electronic invoice can be generated in the application by triggering an invoicing operation on the generation control.

[0074] To sum up, the electronic invoice issuance method provided in this embodiment, if the application itself has the invoicing function, can also separately integrate the AI ​​function of the invoicing component in the application. Through the AI ​​functions such as voice recognition, image recognition, information extraction, and translation provided by the invoicing component, the intelligent and automatic extraction of invoicing information can be realized, which greatly improves the accuracy and efficiency of information entry and reduces the time cost of users manually entering invoicing information.

[0075] In this method, through the combination of modular design and micro-frontend technology, the invoicing component can be integrated into various front-end applications while maintaining a high degree of scalability and flexibility. If the front-end application does not have the invoicing function, it can be configured to call the invoicing function of the invoicing component. If the front-end application has the invoicing function, it can also be configured to call various functions provided by the invoicing component, bringing users a good intelligent invoicing experience.

[0076] Integrating the above-mentioned invoicing components in the front-end application is mainly divided into three modules: Figure 3 As shown:

[0077] (a) Registration module 310.

[0078] The registration module 310 completes the account registration on the invoicing component.

[0079] The electronic device calls the registration interface of the invoicing component through an application and obtains the data of the registration page from the invoicing component; based on the data on the registration page, the registration page is displayed on the user interface; in response to the filling operation of the registration information on the registration page, the registration information is displayed on the registration page, such as the company name, contact information, tax information and other information; in response to the registration operation on the registration page, the account registration is completed.

[0080] (ii) Authentication module 320.

[0081] After successful registration, the authentication module 320 verifies the legitimacy of calling the invoicing component. Only the successfully registered account has the authority to call the invoicing component.

[0082] The electronic device sends a call request to the invoicing component through the account token. If the token is verified, the invoicing component will feedback a signal of successful request to the application. At this time, the application can use various functions provided by the invoicing component.

[0083] In some other possible implementations, each time the billing component is called in the application, authentication is required, that is, calling the billing component integrated in the micro front-end in the application requires calling the billing component through the token of the account.

[0084] (iii) Invoicing component 330.

[0085] After completing the account registration, the electronic device obtains data of the setting page from the invoicing component through the interface between the electronic device and the invoicing component; displays the setting page on the user interface according to the data of the setting page; and completes the integration of the application with at least one function of the invoicing component in response to the setting operation on the setting page. Optionally, after successful authentication, the electronic device executes the above rule setting to complete the step of integrating at least one function of the invoicing component with the application.

[0086] The above-mentioned integrated functions include at least one of AI function and invoicing function.

[0087] When users integrate the invoicing component into the application, they can set rules on the setting page of the invoicing component according to their own needs, including rules for jumping to the page, functions displayed on the page, and page display effects. The subsequent invoicing component will integrate the various functions provided by the invoicing component into the application based on these rules to achieve personalized service settings.

[0088] Optionally, the application and the invoicing component can interact with each other through front-end information exchange or through a back-end interface. For example, the application can realize intelligent extraction of invoicing information through the invoicing component, and automatically issue invoices based on the extracted invoicing information, and send the electronic invoice back to the application through the back-end callback interface to ensure that the electronic invoice can be updated to the application in a timely manner.

[0089] The invoicing component provided in the embodiment of the present application supports seamless integration of multiple platforms such as the World Wide Web (Web) terminal, the APP terminal, and the mini-program, which can satisfy users to choose the invoicing method that best suits them in different scenarios. At the same time, it also provides dynamic combination calls of SAAS interfaces to meet users' diverse needs for invoicing functions. Whether it is a large enterprise or an individual user, it can be integrated with its own products and enjoy the convenience and efficiency brought by AI invoicing.

[0090] In addition, it also achieves seamless page jump and display through micro-frontend integration. According to the rules of the invoicing component, the route of the jump page is centrally managed, and the components of each page can be dynamically displayed according to the request input, and then seamlessly integrated into the calling application or system. This seamless docking method greatly simplifies the integration process and reduces the technical threshold.

[0091] Corresponding to the above method embodiment, Figure 4 A schematic diagram of an electronic invoice issuing device is shown. Figure 4 As shown, the electronic invoice issuing device includes:

[0092] Display module 410, used to display the main page on the user interface of the application, the user interface including the invoicing control;

[0093] The switching module 420 is used to respond to the trigger operation on the invoicing control, call the invoicing component integrated in the micro front end in the application, and switch the main page on the user interface to the invoicing page;

[0094] The editing module 430 is used to respond to the editing operation on the invoicing page and display the corresponding invoicing information in the information column of the invoicing page;

[0095] The generating module 440 is used to generate an electronic invoice in response to an invoicing operation triggered on the invoicing page.

[0096] In a possible implementation, the switching module 420 calls the invoicing component integrated in the micro frontend in the application to update the main page on the user interface to the invoicing page, including:

[0097] Request data for the invoicing page from the invoicing component through the routing mechanism;

[0098] According to the data on the invoicing page, the main page on the user interface is switched to the invoicing page.

[0099] In a possible implementation, the editing module 430 displays corresponding invoicing information in the information column of the invoicing page in response to the editing operation on the invoicing page, including:

[0100] In response to the upload operation on the invoicing page, upload relevant data;

[0101] In response to the auto-fill operation on the invoicing page, the auto-fill function of the invoicing component is called to extract the invoicing information from the relevant data;

[0102] The billing information will be automatically filled into the corresponding information column on the billing page.

[0103] In a possible implementation, the relevant data includes at least one of the following: a picture; voice information; text information.

[0104] In a possible implementation, if the main page is a page for invoicing in the application, the editing module 430 is used to upload relevant data in response to an upload operation on the main page; in response to an automatic filling operation triggered on the main page, call the automatic filling function of the invoicing component to extract the invoicing information from the relevant data; and automatically fill the invoicing information into the corresponding information column on the main page;

[0105] The generating module 440 is used to generate an electronic invoice in response to the invoicing operation triggered on the main page.

[0106] In a possible implementation, the device further includes: a registration module 450;

[0107] The registration module 450 is used to call the registration interface of the invoicing component through the application, and obtain the data of the registration page from the invoicing component; display the registration page on the user interface according to the data of the registration page; display the registration information on the registration page in response to the filling operation of the registration information on the registration page; and complete the account registration in response to the registration operation on the registration page.

[0108] In a possible implementation, the device further includes: a setting module 460;

[0109] The setting module 460 is used to obtain the data of the setting page from the invoicing component through the interface between the invoicing component and the invoicing component after completing the account registration; display the setting page on the user interface according to the data of the setting page; and complete the integration of at least one function of the invoicing component by the application in response to the setting operation on the setting page.

[0110] In a possible implementation, the switching module 420 calls the billing component integrated in the micro frontend in the application, including: calling the billing component through the token of the account.

[0111] It should be noted that the electronic invoice issuing device of this embodiment is used to implement the corresponding electronic invoice issuing method in the aforementioned method embodiment, and has the beneficial effects of the corresponding method embodiment, which will not be described in detail here.

[0112] Figure 5 This is a schematic block diagram of an electronic device provided in an embodiment of the present application. The specific embodiment of the present application does not limit the specific implementation of the electronic device. Figure 5 As shown, the electronic device may include: a processor (processor) 902, a communication interface (Communications Interface) 904, a memory (memory) 906, and a communication bus 908. Among them:

[0113] The processor 902 , the communication interface 904 , and the memory 906 communicate with each other via a communication bus 908 .

[0114] The communication interface 904 is used to communicate with other electronic devices or servers.

[0115] The processor 902 is used to execute the program 910, and specifically can execute the relevant steps in any of the aforementioned electronic invoice issuance method embodiments.

[0116] Specifically, the program 910 may include program codes, which include computer operation instructions.

[0117] The processor 902 may be a central processing unit (CPU), or an application specific integrated circuit ASIC (Application Specific Integrated Circuit), or one or more integrated circuits configured to implement the embodiments of the present application. The one or more processors included in the smart device may be processors of the same type, such as one or more CPUs; or may be processors of different types, such as one or more CPUs and one or more ASICs.

[0118] RISC-V is an open source instruction set architecture based on the Reduced Instruction Set (RISC) principle. It can be applied to various aspects such as single-chip microcomputers and FPGA chips. Specifically, it can be applied to the fields of IoT security, industrial control, mobile phones, personal computers, etc., and because it is designed with small, fast, and low-power realities in mind, it is particularly suitable for modern computing devices such as warehouse-scale cloud computers, high-end mobile phones, and tiny embedded systems. With the rise of artificial intelligence Internet of Things (AIoT), the RISC-V instruction set architecture has also received more and more attention and support, and is expected to become the next generation of widely used CPU architecture.

[0119] The computer operation instructions in the embodiment of the present application may be computer operation instructions based on the RISC-V instruction set architecture, and correspondingly, the processor 902 may be designed based on the RISC-V instruction set. Specifically, the processor chip in the electronic device provided in the embodiment of the present application may be a chip designed with the RISC-V instruction set, and the chip may execute executable code based on the configured instructions, thereby implementing the electronic invoice issuance method in the above embodiment.

[0120] The memory 906 is used to store the program 910. The memory 906 may include a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.

[0121] The program 910 can be specifically used to enable the processor 902 to execute the electronic invoice issuance method in any of the aforementioned embodiments.

[0122] The specific implementation of each step in program 910 can refer to the corresponding description of the corresponding steps and units in any of the above-mentioned electronic invoice issuance method embodiments, which will not be repeated here. Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working process of the above-described devices and modules can refer to the corresponding process description in the above-mentioned method embodiments, which will not be repeated here.

[0123] Computer storage media

[0124] The present application also provides a computer-readable storage medium storing instructions for causing a machine to execute the electronic invoice issuance method as described herein. Specifically, a system or device equipped with a storage medium may be provided, on which a software program code for implementing the functions of any of the above embodiments is stored, and a computer (or CPU or MPU) of the system or device reads and executes the program code stored in the storage medium.

[0125] In this case, the program code read from the storage medium itself can implement the function of any one of the above embodiments, so the program code and the storage medium storing the program code constitute part of the present application.

[0126] The storage medium embodiments for providing the program code include a floppy disk, a hard disk, a magneto-optical disk, an optical disk (such as CD-ROM, CD-R, CD-RW, DVD-ROM, DVD-RAM, DVD-RW, DVD+RW), a magnetic tape, a non-volatile memory card, and a ROM. Alternatively, the program code can be downloaded from a server computer by a communication network.

[0127] Computer program product

[0128] An embodiment of the present application also provides a computer program product, including computer instructions, which instruct a computing device to perform any corresponding operation in the above-mentioned multiple method embodiments.

[0129] It should be pointed out that, according to the needs of implementation, the various components / steps described in the embodiments of the present application can be split into more components / steps, or two or more components / steps or partial operations of components / steps can be combined into new components / steps to achieve the purpose of the embodiments of the present application.

[0130] The above-mentioned method according to the embodiment of the present application can be implemented in hardware, firmware, or implemented as software or computer code that can be stored in a recording medium (such as a CD ROM, RAM, floppy disk, hard disk or magneto-optical disk), or implemented as a computer code originally stored in a remote recording medium or a non-temporary machine-readable medium downloaded through a network and to be stored in a local recording medium, so that the method described herein can be stored in such software processing on a recording medium using a general-purpose computer, a special-purpose processor or programmable or special-purpose hardware (such as an ASIC or FPGA). It can be understood that a computer, a processor, a microprocessor controller or programmable hardware includes a storage component (e.g., RAM, ROM, flash memory, etc.) that can store or receive software or computer code, and when the software or computer code is accessed and executed by a computer, a processor or hardware, the method described herein is implemented. In addition, when a general-purpose computer accesses the code for implementing the method shown here, the execution of the code converts the general-purpose computer into a special-purpose computer for executing the method shown here.

[0131] Those of ordinary skill in the art will appreciate that the units and method steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the embodiments of the present application.

[0132] The above implementation methods are only used to illustrate the embodiments of the present application, and are not limitations on the embodiments of the present application. Ordinary technicians in the relevant technical field can make various changes and modifications without departing from the spirit and scope of the embodiments of the present application. Therefore, all equivalent technical solutions also belong to the scope of the embodiments of the present application. The scope of patent protection of the embodiments of the present application should be limited by the claims.

Claims

1. A method for issuing electronic invoices, characterized in that: The method comprises: Displaying a main page on a user interface of the application, wherein the user interface includes an invoicing control; In response to a trigger operation on the invoicing control, calling an invoicing component integrated in the micro front-end in the application, and switching the main page on the user interface to an invoicing page; In response to an editing operation on the invoicing page, displaying corresponding invoicing information in an information column on the invoicing page; In response to the invoicing operation triggered on the invoicing page, an electronic invoice is generated.

2. The method according to claim 1, characterized in that The calling of the invoicing component integrated in the micro front-end in the application to update the main page on the user interface to the invoicing page includes: Requesting data of the invoicing page from the invoicing component through a routing mechanism; According to the data of the invoicing page, the main page on the user interface is switched to the invoicing page.

3. The method according to claim 1 or 2, characterized in that: In response to the editing operation on the invoicing page, the corresponding invoicing information is displayed in the information column of the invoicing page, including: In response to an upload operation on the invoicing page, uploading relevant data; In response to the automatic filling operation on the invoicing page, calling the automatic filling function of the invoicing component to extract the invoicing information from the relevant data; The billing information is automatically filled in the corresponding information column of the billing page.

4. The method according to claim 1 or 2, characterized in that: The method further comprises: Calling the registration interface of the invoicing component through the application program to obtain the data of the registration page from the invoicing component; Displaying the registration page on the user interface according to the data on the registration page; In response to a filling operation of registration information on the registration page, displaying the registration information on the registration page; In response to the registration operation on the registration page, the account registration is completed.

5. The method according to claim 4, characterized in that The method further comprises: After completing the account registration, obtaining data of the setting page from the invoicing component through the interface between the invoicing component and the invoicing component; Displaying the setting page on the user interface according to the data of the setting page; In response to the setting operation on the setting page, the integration of the application into at least one function of the invoicing component is completed.

6. The method according to claim 4, characterized in that The calling of the invoicing component integrated with the micro frontend in the application comprises: The invoicing component is called through the token of the account.

7. An electronic invoice issuing device, characterized in that: The device comprises: A display module, used to display a main page on a user interface of the application, wherein the user interface includes an invoicing control; A switching module, configured to respond to a trigger operation on the invoicing control, call the invoicing component integrated in the micro front-end in the application, and switch the main page on the user interface to the invoicing page; An editing module, configured to respond to an editing operation on the invoicing page and display corresponding invoicing information in an information column on the invoicing page; A generating module is used to generate an electronic invoice in response to an invoicing operation triggered on the invoicing page.

8. An electronic device, characterized in that: include: A processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface communicate with each other via the communication bus; The memory is used to store at least one executable instruction, and the executable instruction enables the processor to execute the electronic invoice issuance method according to any one of claims 1 to 6.

9. A computer storage medium, characterized in that The computer storage medium stores a computer program, and when the computer program is executed by the processor, the electronic invoice issuance method according to any one of claims 1 to 6 is implemented.

10. A computer program product, characterized in that The computer program product includes computer instructions, and the computer instructions instruct a computer device to execute the electronic invoice issuance method according to any one of claims 1 to 6.

Images